Answered Question asked by Billy Cheung

Why does Microsoft Scout say it hasn't been set up for my organisation?

The question

Hello Thanks for your detailed guide on Microsoft Scout. I tried 2 weeks to set up Microsoft Scout but I have no clue why it’s still not able to run on my laptop. I am new to Microsoft ecosystem and not a Tech background guy.

When I run Scout, here is the message: Ask your admin to enable Microsoft Scout Microsoft Scout hasn’t been set up for your organization yet. Once your admin has enabled it, come back here to get started.

Here is my situation: prerequisites: I have Microsoft 365 Copilot license, GitHub Copilot Enterprise license(trial), Microsoft Frontier program enrollment

Gate 1 - 100% sure all set; Gate 2 - a. Intune policy done. b. Attestation form submitted but no response yet c. GitHub Copilot license assignment (not sure if my set up is right or now). Is this a must to upgrade to Paid GitHub Enterprise license?

I am so frustrated and have no ideas how could I make this work.

It’s much appreciated if you could have a more detail guide for all the setup, or I could pay for a zoom tutorial set up session.

Thanks, Billy

The answer

Hi Billy,

Thanks for the detail — you’ve done the hard parts already, and you’re closer than it feels. One reframe first (it catches a lot of people, and your message exposed a gap in my own guide that I’ve just fixed — so thank you):

The error is the “organisation enabled” gate, and Scout signs in to Microsoft 365 before the GitHub step. So it most likely points to the Microsoft 365 / Frontier / Intune admin setup — not your GitHub license. To your direct question: no, you don’t need to rush to a paid GitHub Enterprise plan. Scout needs GitHub Copilot Business or Enterprise — Business is enough; the individual Free/Pro/Pro+ plans aren’t listed as qualifying. If your Enterprise trial has assigned that seat to the GitHub account you sign in with, it should work while the trial’s active (worth verifying the seat in your GitHub org’s Copilot settings). But that’s only checked later, at the separate “Sign in to GitHub” step — not where you’re stuck.

On the attestation — “no response yet” is expected. Microsoft’s docs describe that step as completing the form to record your opt-in; they don’t mention an approval reply coming back. So don’t treat “no response” as your blocker.

So where’s the real blocker? In order:

  1. Wait it out — the Copilot Frontier save takes up to ~3 hours to apply. Fully quit Scout and relaunch.
  2. Is your own account in scope? If you set Frontier to Specific users, your sign-in account must be in that list. Easiest while testing: switch to All users.
  3. M365 Copilot license on the exact account you sign in with.
  4. Did the Intune policy reach your PC? “Set in Intune” ≠ “applied on the device.” On the PC: Settings → Accounts → Access work or school → your account → Info → Sync, then relaunch Scout.
  5. Is your tenant Frontier-eligible? If Copilot Frontier doesn’t even appear under M365 admin → Copilot → Settings, the tenant isn’t in the Frontier program — that’s the root prerequisite.

Full write-up with steps: Troubleshooting “Ask your admin to enable Microsoft Scout”.

Honest heads-up: Scout access depends on tenant-level admin setup (Frontier + Intune + attestation) plus the right licenses, so it usually isn’t something an individual user can fully self-enable. If you’re solo on your own tenant, you’re wearing both hats — every gate has to be done by you. If you don’t actually have admin rights, that’s the first thing to sort.

Hope that unblocks you — and genuinely, thanks, your question made the guide better. — Sush