The documentation now describes Every time strict, including its 10-second validity window, application session-management requirements, targeting guidance, and Office 365 warning. It also explains Global Secure Access reauthentication for sensitive private applications using a five-minute window.
Microsoft sets February 2027 retirement for Entra SMS and voice SSPR
Microsoft will retire its own SMS and voice authentication for self-service password reset beginning in February 2027, with each user group receiving a 50-day transition. Entra Private Access now has preview guidance for sign-in-every-time reauthentication, while new documentation covers customer-owned telephony setup, a Salesforce provisioning deadline, and an RHEL upgrade failure mode affecting Entra SSH sign-in. Most remaining changes were link, command, and procedure maintenance.
- Microsoft-provided SMS and voice SSPR authentication enters retirement
Entra ID · Conditional Access
Microsoft Entra ID will begin retiring Microsoft-provided SMS and voice authentication for SSPR in February 2027. Each user group has a 50-day transition, after which those methods will no longer be available for SSPR. Administrators should prepare alternative recovery methods.
- Private Access sign-in-every-time preview sets client and reauthentication requirements
Private Access · Conditional Access
The preview requires Conditional Access and the Global Secure Access Windows client version 2.34.222 or later. It uses a five-minute reauthentication window; administrators should account for supported clients and platform-specific exclusions when deploying it.
- Customer-owned telephony receives an end-to-end setup guide
Entra ID · Authentication
The new Microsoft Entra admin center guide covers purchasing and activating a telecom provider, deploying the Azure integration, configuring authentication method profiles, validating evaluation mode, and gradually rolling out SMS and voice delivery. It gives administrators a single procedure for reviewing the required Azure resources, tools, permissions, and tests.
- Salesforce provisioning guidance adds a December 1 permission deadline
Entra ID · Provisioning
The Salesforce provisioning guide now calls for SOAP API `login()` and the **Use Any API Auth** permission on the Admin Username account. It documents Salesforce’s December 1, 2026 requirement and related credential-validation failures, so the permission should be in place before that date.
- RHEL in-place upgrades can break Entra SSH sign-in
Entra ID · Authentication
The updated Linux guidance says an in-place upgrade from RHEL 8.x to 9.x can remove the `aadsshlogin` package and cause `Permission denied (publickey)`. If that occurs, administrators should uninstall and reinstall the AADSSHLoginForLinux extension.
Inventory users relying on Microsoft-provided SMS or voice for SSPR and plan alternative recovery methods around each group’s 50-day transition. For Private Access, verify the required Windows client and Conditional Access design. Teams using customer-owned telephony can follow the new end-to-end setup guide. Salesforce administrators should grant the documented permission before December 1, 2026, and Linux administrators should reinstall the AADSSHLoginForLinux extension if Entra SSH sign-in fails after an affected RHEL upgrade.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
30 updates by product
Microsoft Entra ID
26 updatesSystem Preferred Authentication
Doc updateThe table now lists External multifactor authentication as method 3, Certificate-based authentication as method 4, and Microsoft Authenticator notifications as method 5. The External MFA entry also has updated dash formatting.
Credential Management Api
Doc updateThe article now says the passkey sample demonstrates listing, registration, and deletion flows, and removes the previous Microsoft Graph deletion-flow warning.
Howto Vm Sign In Azure Ad Linux
Doc updateAction requiredThe documentation now explains that in-place upgrades from RHEL 8.x to 9.x can remove the `aadsshlogin` package, causing `Permission denied (publickey)` errors. It provides steps to uninstall and reinstall the AADSSHLoginForLinux extension.
Choose Your Own Telephony Set Up
Doc updateThe documentation now directs administrators through Function App → Functions → SendOtp → Invocations when checking the latest transaction and HTTP 200 result.
Phone Providers
Doc updateThe documentation now links Infobip’s Microsoft Security Store offer and directs administrators to the Microsoft Entra admin center setup guide instead of the API setup guide.
The documentation adds an end-to-end guide for purchasing and activating a telecom provider, deploying the Azure integration, configuring authentication method profiles, validating evaluation mode, and gradually rolling out SMS and voice delivery.
Choose Your Own Telephony Reliability
Doc updateThe article now links to instructions for setting up SMS and voice with your own telecom provider in the Microsoft Entra admin center instead of the API-based setup guide.
Choose Your Own Telephony Fraud Costs
Doc updateThe documentation now links to instructions for setting up SMS and voice with your own telecom provider in the Microsoft Entra admin center instead of the API-based setup guide.
Choose Your Own Telephony Troubleshoot
Doc updateThe troubleshooting page’s setup link was updated from API-based instructions to instructions for setting up SMS and voice with your own telecom provider in the Microsoft Entra admin center.
Set Up Sms Voice Api
Doc updateThe article describing CYOT provider purchase, Azure integration deployment, permissions, policy configuration, and testing is no longer documented at this location.
Group Source Of Authority Configure
Doc updateThe documentation now lists Microsoft Graph PowerShell commands to read and update a group’s `IsCloudManaged` state, and documents cloud-specific authentication options. It also notes that Graph Explorer isn’t supported in Azure China.
The guide now covers connecting with Microsoft Graph PowerShell, required permissions and cloud settings, troubleshooting consent, and the PowerShell command for changing a group’s source of authority.
User Source Of Authority Configure
Doc updateThe documentation now explains how to install and connect with Microsoft Graph PowerShell, select cloud environments, grant required permissions, and update a user’s source of authority with PowerShell.
User Source Of Authority Configure
Doc updateThe article now describes contacts as Outlook items, retains the required Contacts-OnPremisesSyncBehavior.ReadWrite.All permission, and uses a generic contact PATCH example. Detailed SOA read, transfer, verification, PowerShell, sovereign-cloud, and contact cmdlet guidance was removed.
User Source Of Authority Configure
Doc updateAction requiredThe documentation now lists Graph PowerShell commands for setting and reading user SOA, identifies the Hybrid Administrator role, and documents cloud-specific connection environments. It also notes that Graph Explorer isn't supported in Azure China.
User Source Of Authority Configure
Doc updateThe configuration article now links to Microsoft Graph PowerShell cmdlets for updating and retrieving a contact’s on-premises sync behavior.
Group Source Of Authority Configure
Doc updateThe page no longer includes the note that Graph Explorer is unsupported in Azure China or the instructions to use Microsoft Graph PowerShell for sovereign clouds.
User Source Of Authority Configure
Doc updateThe article adds Microsoft Graph API and PowerShell examples for transferring the source of authority (SOA) for organizational contacts synchronized from AD DS, including permissions, verification, and sovereign-cloud guidance.
Configure Salesforce Sandbox for automatic user provisioning with Microsoft Entra ID
Feature updateAction requiredThe tutorial adds requirements to enable SOAP API `login()` and grant the integration account API Enabled, Manage Users, and Use Any API Auth permissions. It also documents Salesforce’s December 1, 2026 requirement for Use Any API Auth and related credential errors.
Configure Salesforce for automatic user provisioning with Microsoft Entra ID
Feature updateAction requiredThe tutorial now requires SOAP API `login()` to be enabled and the Admin Username account to have **Use Any API Auth**. It also documents credential-validation troubleshooting and Salesforce’s December 1, 2026 requirement.
Group Source Of Authority Configure
Doc updateThe documentation changed the SOA-related resource table into a bulleted list while retaining the same three Microsoft Graph PowerShell links.
Group Source Of Authority Configure
Doc updateThe Update-MgGroupOnPremiseSyncBehavior and Get-MgGroupOnPremiseSyncBehavior links no longer include the graph-powershell-1.0 view parameter.
Microsoft Entra ID will retire Microsoft-provided SMS and voice authentication for self-service password reset (SSPR) starting February 2027, with a 50-day transition per user group. Organizations must prepare alternative recovery methods, as SMS/voice will no longer be available for SSPR after the transition.
User Source Of Authority Configure
Doc updateThe User Source of Authority configuration guide now links to the current Microsoft Graph PowerShell cmdlet pages without the `view=graph-powershell-1.0` version parameter.
Deployment Guide Token Protection Windows
Feature updateThe documentation now states that Office perpetual clients version 2024 and later support Token Protection, while versions earlier than 2024 aren't supported.
Microsoft Entra External ID
1 updateSign In With Passkey
Doc updateThe documentation now describes the sample as supporting passkey listing, registration, and deletion. It removes the separate deletion endpoint guidance and the warning about the sample using Microsoft Graph with high-privilege permissions and a client secret.
Microsoft Entra Private Access
3 updatesThe new page describes the preview sign-in-every-time capability, its Conditional Access dependency, Windows client requirement (version 2.34.222 or later), and five-minute reauthentication window.
Microsoft Entra Private Access documentation now explains how to configure, test, and deploy reauthentication for selected private applications using one Conditional Access policy and a pilot group. It requires Global Secure Access Windows client version 2.34.222 or later.
Private Access Sign In Every Time
Doc updateThe documentation now links to instructions for configuring sign-in every time for Microsoft Entra Private Access (preview).
