Clear attribute values
Doc updateThe page title and headings for clearing attribute values no longer include “(Preview).”
Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The most consequential update clarifies the stated behavior of an ID Protection managed policy left in Report-only: it will automatically enable itself on the communicated schedule, while naming its security group and excluding tenants with an enabled customer-managed user-risk policy. External ID guidance adds TOTP setup detail, cross-tenant synchronization guidance specifies role-assignable group mapping, and Zendesk provisioning guidance flags an API-token restriction and OAuth timing.
The updated Conditional Access page names the managed policy’s security group, excludes tenants with an enabled customer-managed user-risk policy, and says the policy automatically enables itself on the communicated schedule if it remains in Report-only. Administrators should review the policy and security group before that schedule; no mandatory action is specified.
The MFA in external tenants guidance now describes time-based one-time passwords as an MFA method, including QR-code registration and verification codes from Microsoft Authenticator or supported third-party authenticator apps. Administrators can use these documented steps when configuring TOTP as a second factor for customer users.
The updated preview guidance explains how to synchronize role-assignable groups by enabling the target setting and mapping isAssignableToRole during group creation. Source role assignments are not copied, and the mapping must be completed before assigning role-assignable groups.
The setup article now states that Zendesk restricted new API-token creation beginning October 27, 2026, provides an exception process, and targets OAuth client-credentials support for mid-December 2026. Administrators starting new provisioning integrations may need to request an API-token exception until OAuth support is available.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The page title and headings for clearing attribute values no longer include “(Preview).”
The page describes how Microsoft Entra provisioning can clear target values, including supported inbound integrations, single-valued attribute limits, prerequisites, and the two-gate opt-in configuration.
The article now states that Zendesk restricted new API-token creation starting October 27, 2026, provides an exception process, and targets OAuth client-credentials support for mid-December 2026.
The documentation explains how to synchronize a group’s role-assignability using a direct `isAssignableToRole` mapping during target-group creation. Role assignments remain separate, and existing non-role-assignable groups aren’t converted.
The November 2026 entry documents creating role-assignable groups across tenants in the same cloud, including inbound settings, a creation-only attribute mapping, and target-group verification.
The policy now names its security group, excludes tenants with an enabled customer-managed user-risk policy, and automatically enables itself on the communicated schedule if left in Report-only.
The architecture diagram was removed, along with a placeholder GitHub download URL. The integration-flow step now simply instructs readers to download the ZIP package.
The guide now covers email OTP, SMS, and TOTP, with steps to enable Microsoft Authenticator and third-party authenticator apps.
The documentation now describes time-based one-time passwords (TOTP) as an MFA method, including registration by QR code and verification codes from Microsoft Authenticator or supported third-party apps.
The supported-features table now lists time-based one-time password (TOTP) as an MFA authentication method for customers.
The documentation now identifies TOTP and passkey (FIDO2) as MFA methods for external tenants, including how users use each method.
Documentation now explains how to synchronize role-assignable groups, including enabling the target setting and mapping `isAssignableToRole` during group creation. Source role assignments are not copied.