The article replaces “telecom provider” with “telephony provider” across its title, guidance, table, and support references. Related link labels and the FAQ and Security Store links were also updated.

Microsoft Entra ID updates MFA flows to prioritize more secure non-telephony methods over SMS and voice, which remain available under "Show more verification methods." The rollout occurs in October 2026, with no configuration changes required. Users should prepare for a resend waiting period and plan for SMS/voice retirement in February 2027.

The page consistently replaces “telecom provider” with “telephony provider” across descriptions, architecture guidance, responsibilities, and related setup, fraud, resiliency, and cost links.

The guide now uses “telephony provider” terminology, updates setup labels and links, and adds guidance to choose a nearby Azure region and Flex Consumption plan with one always-ready instance for performance.

The resiliency article now consistently uses “telephony provider” instead of “telecom provider” and updates related headings, anchors, links, and sample-resource labels.

The article replaces “telecom provider” with “telephony provider,” updates related resource titles and links, and adds an anchor for the previous heading.

The documentation now lists AlmaLinux 10, Debian 13, openSUSE Leap 16, Oracle Linux 10, Rocky Linux 10, SLES 16, and Ubuntu through 26.04.

The supported versions now include Debian 13, Oracle Linux 10, and Rocky Linux 10.

The documentation no longer lists Debian 13, Oracle Linux 10, or Rocky Linux 10 as supported versions. Debian 9–12, Oracle Linux 8–9, and Rocky Linux 8–9 remain listed.

The Linux VM sign-in article received a minor formatting edit, with one line removed.

The article now explains that passwordless users can change their cloud password from Security info after secure sign-in, supporting legacy applications that still require passwords. The rollout notice was removed.

The documentation now explains that users who sign in with a passkey can change a forgotten password without entering the current password. It also distinguishes passkey loss, which requires account recovery or administrator-issued recovery credentials to register a new passkey.

Microsoft Entra updates the passkey registration in My Sign-ins for Microsoft Authenticator users, adding a checkbox, updated link text, and guided steps to start registration. If direct registration fails, users are directed to WebAuthn flow. Rollout is mid-November 2026 to end-November 2027. Inform users accordingly.

The FAQ now specifies that the two admin consent requests represent static consent permissions and dynamic consent permissions.

The documentation now explains that unsupported properties can be saved while processing is paused, but trigger a Processing error when processing resumes. During that error, membership remains at the last successful evaluation and no new members are added.

The documentation now states that membership does not automatically update when a child group is deleted; affected users or devices remain members until the rule is modified. The reference to members removed from a child group was removed.

The tutorial now directs administrators to create an OAuth client and configure Client Credentials Grant because Authorization Code Grant is being retired. Migration is required by March 31, 2027; otherwise provisioning may stop, affecting user and group synchronization, while SSO remains unaffected.

Users removed from a cross-tenant synchronization job’s scope aren’t deleted from the target tenant if the job is restarted before the next synchronization cycle.

The SAP provisioning guidance now explicitly identifies the associated Microsoft Entra agents as Microsoft Entra provisioning agents.

The documentation now states that each plan supports up to 100 rules and each tenant supports up to 100 plans. It also streamlines guidance for Global Secure Access and agent access scenarios.

The guidance now explicitly states that the App registrations and Enterprise applications portal experiences do not know about dynamic consent permissions at consent time.

The SAP documentation now notes that Joule, SAP’s AI assistant, works across connected SAP applications and links to SAP guidance for enabling it in Cloud Identity Services.

The documentation now describes how signed-in users can update existing passwords through the Microsoft Entra External ID credential management API, including the required delegated permissions and JSON request format.

The JavaScript, React, and single-page application entries now link to samples labeled “List, register, and delete passkeys.” The previous warning about high-privilege deletion permissions and client secrets in browser code was removed.

The passkey sign-in documentation no longer lists a configured custom URL domain as a prerequisite.

The release notes document 24-hour CPU and memory history, improved health reporting, interface-specific DNS support, trace rotation, expanded event-log capacity, better error messages, TCP keepalive, memory management, and local log and file security.