← Previous day

Keep up with Microsoft Entra

Daily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →

Day in brief

MFA puts SMS and voice behind stronger methods ahead of February 2027 retirement

Microsoft Entra MFA flows are being changed to prioritize more secure non-telephony methods, while SMS and voice remain available under “Show more verification methods.” Microsoft says no configuration change is required, but users should expect a resend waiting period and administrators should plan for the stated February 2027 SMS and voice retirement. The other significant operational change is a GoTo provisioning migration deadline; most remaining updates are lower-impact documentation maintenance, including terminology and consent clarifications.

  • The Message Center notice says SMS and voice remain available under “Show more verification methods,” but more secure non-telephony methods are prioritized in MFA flows. It describes an October 2026 rollout, requires no configuration changes, and warns of a resend waiting period and planned SMS and voice retirement in February 2027.

  • The GoTo automatic-provisioning guidance 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 user and group synchronization may stop, while SSO remains unaffected.

  • The provisioning known-issues guidance says 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. Administrators should wait for that cycle before restarting.

  • The developer guidance now explicitly states that the App registrations and Enterprise applications portal experiences do not know about dynamic consent permissions at consent time. This clarifies how administrators should interpret permission information when reviewing admin-consent scenarios.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.

14 updates

10

Plan for resiliency and high availability

Doc update

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

Howto Vm Sign In Azure Ad Linux

Feature update

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

Howto Vm Sign In Azure Ad Linux

Feature update

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.

2

Configure GoTo for automatic user provisioning with Microsoft Entra ID

RetirementAction required

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.

1

Admin Consent Workflow Faq

Doc update

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

1

Consent Types Developer

Doc update

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

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…