Thursday, 14 August 2025

PSSO documentation flags a macOS 15+ configuration issue; PIM and Lifecycle Workflows guidance clarified

14 August was largely a documentation-maintenance day: all 12 recorded changes were updates, with no new items, removals, or Message Center announcements. The most consequential updates document a known macOS Platform Single Sign-On (PSSO) concurrency issue, sharpen Privileged Identity Management approval guidance, clarify a Logic App Lifecycle Workflows syntax requirement, and explicitly list certificate-based authentication as a multifactor authentication strength. The evidence does not establish a product launch, availability change, or service-wide default change.

• Entra ID · Troubleshooting

  macOS 15+ PSSO troubleshooting now documents configuration corruption and re-registration prompts

  The updated troubleshooting page identifies a known concurrency issue on macOS 15+ (Sequoia): simultaneous updates from the system AppSSOAgent and AppSSODaemon processes can corrupt the PSSO device configuration. That corruption can trigger the operating system's re-registration remediation flow and produce unexpected registration prompts. The supplied change does not specify a remediation.

• ID Governance · Governance

  PIM guidance emphasizes approval and clarifies the default approver fallback

  Updated PIM guidance recommends requiring approval for activation of eligible assignments, selecting at least one approver and preferably at least two. It also clarifies that when no specific approvers are selected, active Privileged Role Administrators and Global Administrators become the default approvers. This is documented configuration and security guidance, not evidence of a service-wide default change.

• ID Governance · Governance

  Lifecycle Workflows guidance corrects the Logic App Issuer format

  The Logic App Lifecycle Workflows instructions now explicitly say that the Issuer value must include the slash after the tenant ID. Owners configuring or checking this integration should validate that value; the evidence describes a configuration clarification rather than a feature release.

• Entra ID · Authentication

  Authentication Strengths documentation calls out certificate-based authentication as multifactor

  The Authentication Strengths update explicitly lists Microsoft Entra certificate-based authentication as “Multifactor.” No new availability, rollout, or policy behavior is stated, so the change should be treated as documentation clarification rather than evidence of a newly launched capability.

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