Microsoft Graph API Change Disrupts Universal Print Share Creation for M365 Customers
What Happened — A recent Microsoft Graph API code change introduced a latency bug in Entra ID directory replication, exposing a race condition in the Universal Print share‑creation flow. The bug causes intermittent “Sharing Print Failed” errors when users attempt to create printer shares, especially when the “Allow all users in my organization” option is used.
Why It Matters for TPRM —
- Service‑level interruptions in a core SaaS offering can affect business continuity for any organization relying on cloud‑based printing.
- The issue highlights the risk of undocumented code changes in shared cloud APIs that many third‑party solutions depend on.
- Mitigation requires manual work‑arounds and close monitoring of Microsoft’s remediation timeline.
Who Is Affected — Enterprises across all sectors that use Microsoft 365 Universal Print (cloud‑hosted printing service).
Recommended Actions —
- Review your vendor risk register for dependencies on Universal Print and assess the impact on critical printing workflows.
- Apply Microsoft’s 13‑step mitigation immediately and test share creation in a controlled environment.
- Monitor Microsoft’s incident page (UP1287359) for status updates and confirm the corrective code deployment.
Technical Notes — The fault stems from a Graph API code change that increased Entra ID replication latency, triggering a race condition in Universal Print’s share‑creation retry logic. No CVE or data breach is reported. Source: BleepingComputer