Starting mid-November 2026, Microsoft Entra ID will add risk-based CAPTCHA verification for SMS and voice MFA to prevent automated fraud. Some users may need to complete CAPTCHA before receiving codes or calls. Organizations should prepare help desks, notify users, and ensure network readiness, while continuing to adopt phishing-resistant methods.
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 →
Deprecated memberOf processing leaves groups stale as MemberOf Next becomes the migration path
The earlier memberOf preview ended on November 3, 2026: configurations using it stop updating and remain in their last known state. Microsoft’s documented route forward is MemberOf Next, alongside the preview of Transitive Reports To; both require Microsoft Entra ID Governance, Standard priority, and scheduled twice-daily processing. The period also brings risk-based CAPTCHA for SMS and voice MFA, preview coverage for the Windows App desktop client in Conditional Access app protection, and refreshed FIDO2 attestation data.
- The earlier memberOf preview has stopped updating configurations
Entra ID · General
Microsoft states that the earlier memberOf preview ended on November 3, 2026. Configurations using it stop updating and remain in their last known state; guidance directs administrators to migrate affected dynamic groups, administrative units, and entitlement management auto-assignment policies to MemberOf Next.
- MemberOf Next and Transitive Reports To are documented in preview
Entra ID · Monitoring
MemberOf Next flattens members from selected groups, while Transitive Reports To includes a manager’s full reporting hierarchy. Both support dynamic groups and administrative units and can scope governance controls. They require Microsoft Entra ID Governance, Standard priority, and scheduled twice-daily updates, so membership changes may not appear immediately.
- Risk-based CAPTCHA is being added to SMS and voice MFA
Entra ID · Authentication
Starting in mid-November 2026, Microsoft Entra ID will add risk-based CAPTCHA verification to SMS and voice MFA to counter automated fraud. Some users may need to complete CAPTCHA before receiving codes or calls, requiring help-desk preparation, user communications, network readiness, and continued adoption of phishing-resistant methods.
- Windows App desktop client joins Windows MAM preview guidance
Entra ID · Conditional Access
Conditional Access guidance now includes the Windows App desktop client as a preview target for Windows MAM and app protection policies, with links to configuration requirements and supported scenarios. Administrators evaluating the capability should review those requirements and environments before configuring policies.
- FIDO2 attestation data adds 18 security-key models
Entra ID · Authentication
The attestation table now references MDS version 297 instead of 285 and adds 18 FIDO2 security-key models with their AAGUIDs and capability indicators. The refreshed list supports eligibility and capability checks when evaluating keys.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
22 updates
Microsoft Entra ID
18 updatesThe attestation table now references MDS version 297 instead of 285 and adds 18 FIDO2 security key models with their AAGUIDs and capability indicators.
Choose Your Own Telephony Set Up
Doc updateThe page now recommends checking Marketplace geographic availability before purchasing a telephony provider, clarifies when to use the Function App dropdown versus a custom URL, and updates the fraud-protection link.
Phone Providers
Doc updateTwo links to guidance for using your own telephony provider now point to the updated `choose-your-own-telephony-fraud-protection.md` page.
Choose Your Own Telephony Reliability
Doc updateThe documentation link for protecting against telephony fraud now points to `choose-your-own-telephony-fraud-protection.md` instead of `choose-your-own-telephony-fraud-costs.md`.
Choose Your Own Telephony Troubleshoot
Doc updateThe troubleshooting documentation now links to the renamed telephony fraud protection article.
Deprecated memberOf preview for dynamic membership groups
RetirementAction requiredThe documentation now states that the earlier memberOf preview ended on November 3, 2026. Configurations using it stop updating and remain in their last known state, with guidance to move to MemberOf Next.
The documentation says the earlier memberOf preview was deprecated because it could slow tenant dynamic membership processing. MemberOf Next uses separate processing on a twice-daily schedule.
Groups Dynamic Rule Advanced
Doc updateThe documentation now specifies Microsoft Graph PowerShell modules version 2.41.2 or later and changes the script from exact-version to minimum-version imports.
The article date changed from August 13, 2026, to November 16, 2026. The displayed guidance to minimize `Match` and `Contains` remains included.
Groups Dynamic Rule Advanced
Doc updateThe MemberOf rule example now uses a different group object ID, and the TransitiveReportsTo rule-builder screenshot was removed.
Groups Dynamic Rule Member Of
Doc updateRemoved the “Overview” heading from the memberOf documentation page.
The documentation now includes the Windows App desktop client as a preview target for Windows MAM and app protection policies, with links to configuration requirements and supported scenarios.
The documentation now states that app protection policies support the Windows App desktop client in preview, alongside Microsoft Edge.
Groups Dynamic Rule Advanced
RetirementAction requiredThe page now links to retirement and migration guidance for the earlier MemberOf preview. Existing rules do not need rewriting; moving a group to MemberOf Next requires changing its priority. Rule-builder screenshots and prerequisite links were also added.
Groups Dynamic Rule Advanced
Doc updateAction requiredThe documentation now states that groups using MemberOf Next or Transitive Reports To cannot be created or saved unless they use Standard priority; an error prompts for the required setting.
Microsoft Defender for Cloud Apps is updating App Governance permissions for select Microsoft Entra roles with Unified RBAC support, rolling out December 2026. Cloud App Security Administrators gain policy management rights; Compliance Administrators and Compliance Data Administrators lose some permissions. Admins should review and update role assignments accordingly.
Documentation introduces MemberOf Next, which flattens members from selected groups, and Transitive Reports To, which includes a manager’s full reporting hierarchy. Both support dynamic groups and administrative units and can scope governance controls.
Microsoft Entra ID Governance
4 updatesResource Policy Concepts
Doc updateThe custom policy description now links “Rego” to Open Policy Agent’s policy-language documentation.
Resource Policy Overview
Doc updateThe resource policy overview now links “Rego” to Open Policy Agent’s policy language documentation when describing custom policies.
The documentation now includes detailed Microsoft Graph group-creation input, delegated caller context, member bindings, URI segments, and a `fetchAsPolicy()` example for retaining user owners during owner removal.
The quickstart now explains that other assignments can affect simulated requests and that the documented response fields apply only when no other assignment changes the result. It also clarifies how to distinguish report-only violations using `details[].appliedPolicyEffects`.
