Loading...

Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes

Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes

Microsoft is retiring SMS first-factor sign-in for Microsoft Entra ID workforce tenants worldwide starting February 1, 2027, to enhance security. Organizations must identify affected users, migrate them to phishing-resistant methods like passkeys, and update policies to avoid sign-in disruptions and comply with new requirements. To improve security and reduce reliance on vulnerable authentication methods, Microsoft is continuing the retirement of SMS first-factor sign-in in Microsoft Entra ID. Microsoft recommends phishing-resistant authentication methods, such as passkeys, as the preferred sign-in experience because they help reduce the risk of phishing, fraud, and account compromise associated with phone-based authentication. Microsoft previously retired SMS first-factor sign-in for Microsoft Entra ID Free tenants and stopped enabling SMS sign-in for newly created tenants. This communication provides an update on the next phase of the retirement effort and actions organizations should take to prepare. Microsoft has announced previous retirement actions in Message Center posts MC1426371, MC1448374, and MC1449181. This retirement applies only to Microsoft Entra ID workforce tenant authentication scenarios. It does not apply to Azure AD B2C or Microsoft Entra External ID customer identity scenarios. Rollout schedule Worldwide and GCC: Beginning February 1, 2027, SMS first-factor sign-in will be retired for Microsoft Entra ID tenants. Impact on your organization Who is affected Organizations that: Allow users to sign in using SMS first-factor authentication. Rely on SMS first-factor sign-in as a primary authentication method. Platforms and services Microsoft Entra ID SMS first-factor passwordless sign-in (SignInNoPassword) What will happen After February 1, 2027: Users will no longer be able to authenticate by using their phone number and an SMS one-time passcode as a primary sign-in method. Existing SMS first-factor sign-in configurations will no longer be honored. Management and configuration experiences for SMS first-factor sign-in will be removed from Microsoft administration experiences. Attempts to sign in by using a registered phone number and SMS one-time passcode will be blocked. Users who have another registered authentication method can continue signing in. Organizations that do not migrate affected users before the retirement date may experience sign-in disruptions. Action required and recommendations If your organization uses SMS first-factor sign-in, complete the following […]

The post Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Sales: Choose the data sources AI-powered Data Enrichment uses, including CRM notes

AI-powered Data Enrichment now lets admins choose which data sources the agent uses to enrich records. Outlook emails, Teams meetings, and the...

21 hours ago

Microsoft Teams: Pro Management portal Analytics & Reports Design Refresh

We are refreshing the way we organize the Analytics & Reports area in the Pro Management portal to make it more user-friendly. Product Mic...

21 hours ago

Copilot: Audio overviews on PDF Reteirement

Microsoft 365 Copilot mobile app’s Audio Overviews on PDFs, which create AI-generated podcast-style summaries for commercial users, will...

21 hours ago

Public CDN is becoming optional during Brand Center setup

Brand Center setup will no longer require enabling Public CDN by default, allowing organizations to use branding governance without it. Public...

21 hours ago

Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com

Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Mi...

21 hours ago

Outlook: Reply With a Template in Rules

New Outlook for Windows and Outlook on the web will let users create inbox rules that auto-reply with saved templates, automating routine resp...

22 hours ago

Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring

The Microsoft Graph AuditLogQuery API will be generally available in October 2026, replacing the Search-UnifiedAuditLog PowerShell cmdlet, whi...

22 hours ago

Dynamics 365 Sales – Information regarding the retirement of the Dynamics 365 Sales Insights standalone add-on

Starting November 1, 2026, Dynamics 365 Sales Insights as a standalone add-on will have reached end of support. Sales Insights is a legacy off...

22 hours ago

Work IQ: Updating documents in Office

Work IQ enables agents to create and edit Microsoft Office documents using organizational context, helping users produce and update content mo...

1 day ago

Microsoft Purview: Information Protection – Apply default SharePoint library labels to data at rest

Enables auto‑labeling of existing SharePoint files to match the default sensitivity label configured on their document library. This helps org...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.