Wednesday, 13 August 2025

Microsoft Entra adds HR-provisioning guidance and clarifies URI/SAML semantics

The 13 August record is primarily Microsoft Learn documentation maintenance rather than a product-release bulletin. The clearest substantive items are new SuccessFactors and Workday expression-mapping references, an Identifier URI protection-state check, and a SAML `unique_name` clarification; External ID native-authentication guidance was also updated. The supplied evidence does not claim a new feature, preview, GA milestone, changed service behavior, or capability retirement. The two Zero Trust pages are each marked both New and Removed on the same date, so that evidence is insufficient to call them retirements.

• Entra ID · Provisioning

  SuccessFactors expression mapping functions: new Entra provisioning reference

  A new Microsoft Entra ID provisioning guide documents commonly used expression functions for transforming SuccessFactors data into target user attributes. It adds configuration reference material; the record does not claim a new connector, new function availability, or changed provisioning behavior.

• Entra ID · Provisioning

  Workday expression mapping functions: new provisioning reference

  A new guide covers expression functions for Workday provisioning to on-premises Active Directory and Microsoft Entra ID, including data transformation and attribute creation. This is new mapping documentation, not evidence of a provisioning-service rollout or changed defaults.

• Entra ID · Security

  Identifier URI Restrictions adds a way to verify protection state

  The updated Entra ID security page points administrators to a method for checking whether Identifier URI protection is enabled in their organization. This supports verification of tenant state, but does not show that protection was automatically enabled or that enforcement behavior changed.

• Entra ID · Standards

  SAML token guidance clarifies the limits of `unique_name`

  The updated SAML token documentation describes `unique_name` as human-readable, not guaranteed unique within a tenant, and intended for display only. Integrations should therefore not use this claim as their uniqueness key; this is a standards and documentation clarification, not a token-format change.

• External ID · Authentication

  External ID native authentication setup guidance updated

  The Native authentication page was updated around setup, user-interface customization for mobile and desktop apps, and the sign-in experience. The supplied record does not specify a new capability, preview or GA status, or mandatory configuration change; treat it as implementation guidance for teams using native authentication.

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