Friday, 7 November 2025

Number-matching documentation changed; guest-review licensing and External ID monitoring guidance were clarified

7 November was primarily a documentation-maintenance period: the supplied record contains no new items or message-center notices, and one page was removed. The most substantive updates concern Microsoft Entra ID number matching, ID Governance licensing for guest-scoped access reviews, External ID monitoring setup, and ID Protection logging guidance. The evidence does not establish a new general-availability release, a capability retirement, or a broad tenant configuration change.

• Entra ID · Authentication

  Entra ID Authentication: same-device number-matching guidance was updated

  The Microsoft Authenticator article was updated to cover improvements to same-device number matching. The supplied record provides no configuration instructions, rollout stage, or availability claim, so it does not establish a tenant-side change or a new release.

• Entra ID · Authentication

  Entra ID Authentication: the MFA number-match preview page was removed

  The MFA Number Match Preview documentation page was removed from Microsoft Learn. The record does not say whether the underlying capability was retired, made generally available, or otherwise changed; the page removal alone should not be treated as a product-lifecycle announcement.

• ID Governance · Governance

  ID Governance: guest-scoped access-review creation has a stated licensing constraint

  Updated licensing guidance states that new access reviews scoped to guest users cannot be created when any of the article's listed features are selected. This is a concrete constraint to check during access-review design, although the supplied excerpt does not identify the individual features.

• External ID · Monitoring

  External ID: Azure Monitor setup fields are clarified as read-only

  In the Review step before adding settings, Subscription and Resource group appear as read-only fields. To change them, the documented procedure is to remove the existing service-provider information and restart the wizard. This is a workflow clarification, not evidence of a new monitoring capability.

• ID Protection · Architecture

  ID Protection: centralized Log Analytics collection is recommended

  The updated analysis guidance describes a Log Analytics workspace for collecting data from Azure and non-Azure resources and applications, and recommends sending all log data to one workspace. This is architecture guidance rather than a stated product requirement or behavior change.

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