Blog Post

FastTrack Blog
11 MIN READ

Why identity is the Copilot unlock

AuzinAhmadi's avatar
AuzinAhmadi
Icon for Microsoft rankMicrosoft
Jul 15, 2026

The readiness work nobody talks about: scaling AI in healthcare

This is Part 2 of a three-part series. Part 1 mapped the people who decide whether your AI program ships. This one is for the Microsoft 365 admins and CIOs whose Copilot is paid for but not “on.” Part 3 will cover agent governance.
Who this is for: M365 admins and CIOs whose Copilot is bought but not "on."

“We bought Copilot. Why can’t we turn it on?”
Maybe you’ve said this yourself. You have the licenses. You’re ready to assign them. Months later, Copilot still isn’t in front of a single clinician. The budget cleared. Leadership is asking for the productivity story they were promised, but the deployment is stuck.

The answer is not a license problem or a Copilot problem, but an identity problem. The identity foundation underneath isn’t ready. In healthcare, that foundation is harder to move than anywhere else I’ve worked. Get it right and two things turn on: a Copilot the clinician trusts at the bedside and the control plane for every agent that comes after. 

Why identity is the gate, not a checkbox

Microsoft 365 Copilot authenticates users through Microsoft Entra ID. Every Copilot interaction honors the permissions of the signed-in user through Microsoft Graph, so the question “What can this person see?” is answered by your identity layer, not by Copilot. One of the great things about Copilot is it has access to everything you have access to — this is also one of the concerning things about Copilot.

Two different controls play a role here. Identity decides who is at the door and how far you trust the sign-in. Data governance decides what they can reach once inside. Copilot leans on both, and Entra is the first of the two. It is the one that decides whether you can safely turn Copilot on at all. That is why a responsible admin won’t flip Copilot on until the identity foundation holds. They need multifactor authentication everywhere, Conditional Access that actually evaluates risk, and a least-privilege model they trust. All three live in Entra.

Plenty of the health systems I work with authenticate through 3rd-party identity providers. Microsoft 365 still sits on Entra underneath, the directory it’s built on, but the front door is brokered elsewhere. When the primary authentication layer is 3rd-party, Entra still authorizes Microsoft 365 access.

What changes is the signal Entra gets to see: 

  • MFA may be satisfied by a federated claim from elsewhere rather than evaluated by Entra.

  • Sign-in risk telemetry gets thinner on the Entra side, because Entra never sees the credential go in. The 3rd-party identity provider is evaluating risk at its own front door, but those signals do not become Entra risk that Conditional Access and Entra ID Protection can act on. Some detections still fire offline. Atypical travel is one example, though the IP Entra logs can be a 3rd-party egress rather than the clinician’s. Leaked-credential detection still works, but it is the one Entra ID Protection signal that depends on password hash sync.

  • Device-compliance signals reach Conditional Access only if your devices are registered in Entra. Federated, non-Entra-joined devices also never get an Entra device-bound Primary Refresh Token, so token protection stays dark.

Risk-based Conditional Access and Entra ID Protection then miss the full picture. You are running the front door of your AI program on one system and governing Copilot’s data access on another. That gap is the gate. 

Two ways to close the gap, on two different timetables

The “fast” option keeps the 3rd-party identity provider but moves the Microsoft 365 sign-in to Entra. You defederate the Microsoft 365 domain to managed authentication and register the 3rd party as an external authentication method for MFA. Entra now runs primary sign-in and Conditional Access, so it evaluates device state and risk directly, while the 3rd party still handles the MFA challenge and remains the portal your users know for everything else. You are not ripping out other MFA providers. You are moving one domain’s sign-in to Entra so the signals reach it.

This is the correct path when leadership wants the Copilot productivity story this quarter and a full identity migration is a multi-year mountain you cannot climb first. External authentication methods are generally available as the supported successor to Custom Controls (requiring Entra ID P1). Custom Controls is on a deprecation path, with new configuration blocked and full retirement staged across 2026 into 2027, so confirm the current dates in Microsoft’s documentation before you plan around them.

The “strategic” option consolidates identity on Entra outright. It is the harder path but the one that closes the gap completely. Full consolidation is also what lights up device-bound token protection everywhere, because federated, non-Entra-joined devices never get an Entra Primary Refresh Token. Consolidate when 3rd-party identity providers are mostly doing single sign-on. Keep them as the identity provider for other apps when they are load-bearing across the estate and pulling them out buys you a second migration you don't need.

Either way, the signals must reach Entra before Copilot goes on. If you take the fast path, that managed cutover still runs through the readiness gate and the downtime discipline below. You just skip the full-consolidation mechanics. And if any Microsoft 365 sign-in stays truly federated to a 3rd party, treat it as interim: the thinner Entra telemetry and the absent token protection above stay in force until you close them, so pair it with compensating controls.

Healthcare’s identity constraints are not like other industries

In a normal enterprise, an identity migration is a weekend of change windows and a week of help-desk tickets. In a hospital, the same project touches patient safety. Four constraints make it different:

  1. Electronic health record (EHR) single sign-on dependencies. The EHR is the center of gravity. It integrates with your identity provider, often through a tap-and-go layer, so a clinician can badge into a shared workstation in a second or two. Change the identity provider and you may change badge tap, workstation sign-in, EHR launch, e-prescribing, medication administration, and chart access. You cannot do that blindly.

  2. Round-the-clock, 24/7 care-continuity. There is no maintenance window. The health system runs every hour of every day. An identity change that would be a minor outage at a bank is, in an emergency department, a clinician who cannot open a chart during a trauma intake. The tolerance for downtime is not low. It is zero for anything on the critical path.  

  3. Clinician friction tolerance. Clinicians will accept a badge tap and a biometric. They will not accept a multi-step login at the bedside. Add ten seconds to a workflow they run eighty times a shift and they will route around it. Now your security control is theater. This is where the stakeholders from Part 1 hold their veto as the clinical leaders who own care-continuity risk. 
  4. The regulatory audit trail. HIPAA expects access controls and a record of who reached protected health records and when. Whatever you build has to keep that trail intact through the migration, not reconstruct it afterward. 

None of these are reasons to stay on a fragmented identity model. They are the reasons to migrate carefully rather than quickly.

The Electronic Health Record (EHR) coordination problem

Of the four constraints, EHR integration is the one most likely to stall your migration. The single most common mistake I see is treating it as a pure IT project and looping in the EHR vendor late. The EHR is not a bystander here. It authenticates against your identity provider. The vendor has a say in how that integration changes. 

I watched one system set a hard cutover date before it talked to its EHR vendor. Three weeks out, it learned the tap-and-go integration had to be re-certified against the new identity provider. The date slipped by a month, and the fix was not technical. It was a conversation that should have happened at the start. 

Coordination effort varies by platform. Use this table to start the vendor conversation. Do not use it to set a cutover date.

EHR platform 

Entra integration path 

Coordination load 

Watch for 

Epic 

Federation to Entra supported; SAML / OIDC, SMART on FHIR for app-to-EHR authorization 

Moderate 

Hyperdrive SSO behavior; SMART on FHIR app registrations; Imprivata or tap-and-go path; test real clinical workstation flows in non-prod 

Oracle Health (Cerner) 

SSO via SAML; tap-and-go middleware (Imprivata) common 

Moderate to high 

Middleware re-point is its own workstream; validate proximity-badge flows 

Meditech 

Vendor-assisted SSO; middleware common 

Higher 

Plan added lead time for vendor coordination; confirm supported Entra patterns early 

The pattern across all three: the identity team cannot set the cutover date alone. The EHR vendor and the tap-and-go middleware owner are on the critical path with you. Bring them in while the plan is still a draft, not when you have a date to defend. 

The readiness gate: don’t start until these are true 

If the left column is true, do not put Copilot in front of clinicians until the right column is done. Hand this to your identity and access lead and ask for your system’s version. It turns “Are we ready?” into a list someone owns. 

If this is true 

Do not enable Copilot for clinical users until 

3rd-party identity provider enforces MFA but Entra risk policies are not active

You have an Entra-led Conditional Access plan or a documented compensating control 

EHR SSO depends on tap-and-go middleware 

The EHR vendor and the middleware owner have tested the flow in non-prod 

Shared clinical workstations are in scope 

Badge tap, biometric, EHR launch, and chart access are validated by role 

Rollback needs daytime engineering support 

The wave is not approved 

Overshared or unlabeled sensitive sites remain 

The Copilot pilot scope is constrained to clean data 

The phased migration playbook

You do not migrate a hospital’s identity in one cutover. You move in stages, prove each one, and keep a way back at every step. Once those readiness gates are owned, the work becomes a migration sequence. The first five steps are identity work. The sixth is where identity readiness becomes Copilot readiness. These steps hold up across most migrations to Entra I have seen:

  1. Pilot a low-risk department. Pick a non-clinical or low-acuity group first — finance or a back-office function, not the ED. Prove the end-to-end flow where a failure is an inconvenience, not a safety event. 
  2. Coordinate with the EHR vendor before you touch clinical users. Validate the EHR SSO and the tap-and-go path in a test environment with the vendor in the room. This is the step teams skip and regret.
  3. Cut over in waves, by care setting. Move ambulatory before inpatient and scheduled before emergent, though infusion and urgent care are ambulatory in name only. Sequence by real acuity, not by building. In practice, the first clinical wave is a low-acuity outpatient clinic of twenty or thirty providers, then med-surg, then the ED and ICU last. Each wave is small enough to roll back inside one shift.
  4. Validate against the real workflow, not a checklist. Confirm badge tap, biometric, EHR launch, and chart access for an actual clinician on an actual workstation. A green status page is not validation. A nurse opening a chart is.
  5. Enforce Conditional Access in report-only first. With identity consolidated on Entra, model MFA, device compliance, session controls, and risk-based access before you block anyone. Then enforce by wave once clinical workflows pass. This is the moment the security posture improves.

  6. Turn on the Purview controls Copilot will lean on. Start with sensitivity labels, audit, and an oversharing review, then add Data Loss Prevention. The Microsoft 365 Copilot location in Purview DLP is generally available for sensitivity-label-based blocking. Newer controls, like SIT-based prompt blocking, web-search restrictions, and DLP for Copilot Studio agents, are still rolling out or in preview depending on your tenant, so confirm what you have before the rollout depends on them.

Downtime is a patient-safety issue, not an IT metric 

The framing that changes how this project gets run: in a hospital, identity downtime is a clinical event. Treat it that way and the rest of the plan falls into place. A useful test for every mitigation is what I call the 2 a.m. trauma intake. Not “does this pass in a maintenance window,” but “does this hold when a trauma comes through the door at two in the morning and a clinician has to open a chart right now.” If your rollback story only works during business hours with the full team online, it is not a rollback story.

Run the project on the safest assumption: something will go wrong at the worst possible time. Plan for that time. A cutover safety check before any wave goes live: 

  • Failover path tested, not assumed. Know exactly what happens to authentication if the new path fails. Prove it in test. 
  • Rollback measured in minutes, not hours. If you cannot reverse a wave in about fifteen minutes, it is not ready to cut over during a shift when someone is mid-chart. Every wave needs a named owner who can make the call.
  • Downtime procedures clinicians already know. The EHR’s read-only or downtime mode is part of the plan. The floor has practiced it.
  • Validated at the worst hour, not the easy one. Sign-off includes an off-hours, high-acuity test, because that is when it will actually matter.
  • Help desk and clinical informatics briefed per wave. The people who answer the 2 a.m. call know a migration wave is live and what to do. 

What identity unlocks (and the bridge to agents) 

Here is what turns on: a clinician badges in once and Copilot is right there, scoped to exactly what that person is cleared to see, safe to use in front of a patient. That is the payoff. The control plane underneath is what makes it safe to leave on. 

With Entra as the foundation, the liability ownership and the access controls the CISO need are finally yours to run. Identity secures the perimeter. Most of what follows is the data-governance work it is now safe to start. Here is what to enable after the migration and where each control lives.

Post-migration control 

What it unlocks for Copilot and agents 

Where it lives 

Healthcare watch-out 

Conditional Access, Copilot-scoped 

Real-time access decisions on user risk, device health, and location 

Microsoft Entra 

Start report-only; enforce by care-setting wave 

Sensitivity labels 

Label-aware responses; protected content stays protected 

Microsoft Purview 

Label ePHI and research data before broad enablement 

Oversharing review 

Stops Copilot surfacing overshared sites and files 

Purview / SharePoint 

Run clinical and research SharePoint first 

Audit 

Full trail of Copilot activity for Legal and the CISO 

Microsoft Purview 

Keep the HIPAA ePHI access trail intact through cutover 

DLP for Microsoft 365 Copilot 

Restricts sensitive content from Copilot grounding and prompts 

Microsoft Purview 

Confirm which controls are GA in your tenant 

Every agent you build acts as an identity or on behalf of it. You cannot govern what an agent can reach if you cannot govern who the agent is. After this migration, you can. 

Identity is the gate. It is also the most underestimated project in a healthcare AI program, because it looks like plumbing and behaves like patient safety. Get the identity foundation right and Copilot can turn on without the security story degrading. Data hygiene, oversharing, and clinical adoption still matter, but the gate is open. You are ready for the harder question: not whether you can deploy an agent, but which agents should exist, whose identity they run under, what they can reach, and who can shut them off. 

Part 3, “Agent Governance Is Organizational Readiness,” closes the series. Governance is not the brake on agents. It is what allows you to say yes to them.

Product names, availability, and timelines reflect Microsoft guidance at the time of writing and can change. Verify current state against official Microsoft documentation for your tenant. 

Charles Wallace is a Senior FastTrack Architect at Microsoft. He works on Microsoft 365 Copilot and agent adoption across healthcare and life sciences. His focus is the security, identity, and governance foundations that decide whether AI deployments actually succeed. 

 

 

 

 

 

Updated Jul 30, 2026
Version 4.0
No CommentsBe the first to comment