Is a safe Copilot rollout an identity problem first?

How to bound Copilot identity before a licence wave

1. Bound the licence assignment. In Microsoft 365 admin center → Billing → Licenses, assign Copilot only to a named pilot group. Unbounded assignment copies every other gap to more people.
2. Enforce MFA via Conditional Access. In Entra ID → Protection → Conditional Access, require MFA for the cloud apps Copilot uses (Office 365 / Microsoft 365). Per-user MFA in the legacy portal is not the same control: it does not cover guests the same way, does not support report-only, and Microsoft is retiring it. The policy must include the identities Copilot acts as.
3. Review guest access Copilot can retrieve. In Entra ID → Users → Guest users, and SharePoint sharing reports. Guests matter even without Copilot licences: they often still sit on ACLs that licensed users then retrieve through Copilot. Review both guest access to content and any guest identities that have Copilot.
4. Require PIM for privileged roles with Copilot. In Entra ID → Identity Governance → Privileged Identity Management, make Global Administrator, SharePoint Administrator and similar roles eligible rather than standing. A Global Administrator with a Copilot licence and standing access is a different blast radius from eligible-admin-via-PIM.
5. Record the decision. Write the pilot group, the Conditional Access policy name, the last guest review date and whether PIM is required into the Copilot governance file. Expansion is a treatment decision, not a success metric.

Identity is the blast radius. Oversharing is the fuel.

Oversharing answers what content exists. Identity answers who Copilot can be. A Global Administrator with a Copilot licence and standing privileges can retrieve a wider set of tenant content than a pilot analyst on MFA and Privileged Identity Management. The model did not become more capable. The identity did.

Conditional Access and MFA are the floor. Guests matter even when they are not Copilot-licensed: they often still sit on the ACLs that licensed users then retrieve through Copilot. Review both guest access to content and guest identities that have been given Copilot.

Guests without a Copilot licence still matter

The usual miss is “guests don’t have Copilot, so they are out of scope.” Copilot does not need the guest to hold a licence. It needs a licensed user who can already open what the guest can open. A partner on an Anyone link, a vendor in a Microsoft 365 group, a former contractor still in Entra as a guest — those ACLs become answers in a Copilot chat for every licensed colleague who shares the same access. Review guest access to content, then guest identities that have Copilot. They are two rows.

If you have not run an access review on guests in the last year, answer this questionnaire as not in place. A “we don’t invite guests” policy that was never checked against Entra is documentation, not a control.

Conditional Access MFA is not per-user MFA

Per-user MFA is a flag on an account in the legacy MFA portal. Conditional Access is a policy: which identities, which apps, which grant controls. Copilot runs as the signed-in work identity against Office 365 / Microsoft 365 cloud apps. If MFA is only per-user, guests, newly provisioned accounts and report-only testing are outside the story. Microsoft has been retiring per-user MFA as the enterprise control. For Copilot the distinction is operational, not pedantic: stolen or shared credentials widen what a prompt can retrieve.

A Conditional Access policy that requires MFA for the Copilot-relevant cloud apps, includes the pilot group (and guests if they can hold Copilot or sit on retrieved ACLs), and has been in report-only then enabled, is the control this questionnaire scores. “We have MFA” without naming the policy is not.

PIM is not optional for admins with Copilot

Standing privileged roles plus Copilot is a different information-security scenario from eligible-admin-via-PIM. If PIM is “we have it” but not required for the roles that hold Copilot, you have documentation, not a control. The Copilot prompt becomes an investigation shortcut over whatever that admin can already open — including SharePoint sites they only have because of the role.

How this score is calculated

Four questions, equal weight — 25% each: bounded Copilot pilot, Conditional Access MFA, guest access, Privileged Identity Management. Yes = 100, partly = 50, no or I’m not sure = 0. The overall is the simple average. A miss on PIM is the same size as a miss on the pilot. Flags name the gap; they do not add extra points. This quiz does not score DLP, labels, Flex Routing or the DPIA — use those assessments if that is the question.

A pilot is a control, not a phase-gate slide

Every other gap — Flex Routing, oversharing, missing DLP — is multiplied by the number of licensed users. A bounded Copilot pilot is how residual risk stays inside appetite while you remediate. Broad assignment on day one is a treatment decision: accept that every historical share is now faster to find. European organisations that treat licence count as a success metric reverse the order and spend the next year explaining chats.

Sources

• Conditional Access overview — Microsoft Learn
• What is Privileged Identity Management — Microsoft Learn
• B2B collaboration (guest access) — Microsoft Learn
• Assign Microsoft 365 Copilot licences — Microsoft Learn

Read first

• What to check before assigning Copilot licences

  A safe European rollout combines technical configuration, accountability documentation and organisational measures. The sequence matters.

FAQ

Other assessments — not the same questionnaire

• Copilot Oversharing: SharePoint, Labels and DLP

  Yes, if a licensed user can already open them. Copilot does not create a new SharePoint permission. It summarises existing ACLs — including Everyone, Anyone links and “except external users”. Sensitivity labels and Purview DLP only stop that if they are applied and if Microsoft 365 Copilot is a location in the policy.

• Microsoft 365 Copilot Readiness Assessment (EU)

  It can be, but not by turning the product on. Microsoft 365 Copilot GDPR compliance in 2026 depends on EU Data Boundary settings, Flex Routing, oversharing in SharePoint and OneDrive, identity, DLP, and a DPIA you actually hold. A tenant in Europe is not the same as Copilot staying in Europe. Use this pack when the board wants one score. Use the topic assessments for Flex Routing, EUDB, Foundry and DPIA detail.

• Is Microsoft’s Copilot DPIA Template Enough?

  Microsoft’s “Build your own” Microsoft 365 Copilot DPIA is a starting file, not the record. Article 35 still needs tenant facts the template cannot know: the Flex Routing value and whether extra-EU inferencing is a transfer, whether historically overshared SharePoint still grounds Copilot, whether DLP lists Microsoft 365 Copilot as a location, web grounding, Anthropic models, commercial vs consumer licensing, and a named owner. A score is not that file.