Free Microsoft Entra impact check

Is your Entra rollout ready?

Check likely impact, then score six practical rollout controls. No sign-in or tenant access.

For affected public-cloud users: passkey defaults begin 1 September 2026 and Microsoft-provided SMS and voice delivery ends 1 February 2027.

Step 1 of 2 · Check likely impact

Enter a company website.

We use public Microsoft sign-in information to look for an Entra tenant and visible branding. This cannot inspect your users, methods, policies, or Conditional Access.

Public sign-in information only. Nothing connects to or changes a Microsoft tenant.

Step 2 of 2 · Self-assess the rollout

How much of the last-mile work is already done?

Tick only what is complete and evidenced today. Your score is a planning aid, not a security certification.

Six controls for a managed transition Affected users are inventoried You know who relies on Microsoft-provided SMS/voice and who needs another method. Passkey policy and providers are defined Pilot scope, allowed providers, attestation choices, and registration policy are documented. The real device journey has been piloted iPhone, Android, Windows, hardware-key, cross-device, and recovery paths are tested where relevant. Employees and the help desk are prepared People will recognise the prompt, follow their device guide, and know where to get safe support. Enforcement is rehearsed safely Conditional Access is report-only first, with emergency access and recovery paths protected. Ownership, dates, and measures are agreed The rollout has an accountable owner, staged cohorts, success measures, and a decision cadence.

Turn these gaps into a rollout plan.

Preview the administrator playbooks, employee guides and email drafts with your organisation's branding.

Preview my kit →

Sources and scope

The February change concerns Microsoft-provided SMS and voice delivery in Entra ID public-cloud tenants. Microsoft documents customer-managed telecom as an alternative. SetupPasskeys is an independent product and is not affiliated with or endorsed by Microsoft. Guidance reviewed 27 July 2026.