In an October–November 2026 pilot, replacing a legacy third-party MFA custom control with an external authentication method in Microsoft Entra ID proved to be more than a simple policy edit. The challenge is coordinating policy scope, method registration, and provider-side configuration so that users remain protected throughout the transition.
Pilot architecture
Use a dedicated pilot group and scope the external MFA method to the group. Configure the third-party provider integration according to the official documentation. Create a Conditional Access policy scoped to the pilot that requires multifactor authentication. Check that pilot identities are excluded from the legacy custom-control policy at the approved migration step.
The exclusion and inclusion must be coordinated. Leaving both policies in scope may lead to unexpected prompts or requirements. Excluding the old policy before the new method and enforcement are ready can create a protection gap.
Test cases
| Test | Expected result |
|---|---|
| User outside pilot | Existing MFA behavior unchanged |
| Pilot user with external method registered | Required MFA is satisfied using an eligible external method |
| Pilot user without registration | Supported registration or recovery path is available |
| Provider rejects authentication | Access is denied |
| Number matching | Provider policy and prompt behavior match the design |
External MFA methods currently cannot satisfy Conditional Access authentication strength requirements; use the standard Require multifactor authentication grant when migrating this flow, and check for applications whose policies require authentication strengths. Do not assume an external MFA method satisfies every sensitive-access requirement. Verify the requirements and available methods for sensitive applications. Confirm emergency access and recovery arrangements before rollout.
Troubleshooting number matching
In proof-of-concept testing, an initial push used a simple approval prompt rather than the intended number-matching experience. The relevant provider-side policy mapping required correction. This is a useful reminder that successful federation does not prove that the intended MFA experience is configured.
Inspect Entra sign-in logs, authentication details and Conditional Access outcomes, then correlate with provider logs. Confirm the actual prompt and validation result rather than relying on configuration alone.
Rollout and rollback
Roll out in small waves with helpdesk guidance and monitoring. Verify method eligibility, registration and policy scope before moving each wave. Maintain an authorised rollback procedure that restores the known working enforcement configuration without leaving accounts unprotected.
References
Scope verification before migration
For each wave, compare the group assigned to the External MFA authentication method with the users included in the new Conditional Access policy. Explicitly exclude that wave from the legacy Duo custom-control policy only after the new policy, method eligibility, provider-side integration and recovery processes have been verified. A user present in neither enforcement scope is a security gap; a user in both may experience incompatible requirements or duplicate prompts.
Use the Entra sign-in logs to confirm the applied Conditional Access policy and authentication method, then validate the actual challenge and denial behavior in Duo. Maintain an emergency-access plan that does not rely solely on the transitioning provider.