Microsoft traces Universal Print issues to Graph API code change

Source: Bleeping Computer

Microsoft says that an ongoing Universal Print sharing issue that prevents users from creating some printer shares is due to a Microsoft Graph API code change.

Universal Print is a cloud‑based print solution designed to replace on‑premises print server setups and provide Microsoft 365 customers with centralized print management capabilities.

After confirming the issue (tracked under UP1287359) on Tuesday, Microsoft said that affected users may intermittently see “Sharing Print Failed” errors in the Universal Print portal when creating printer shares in some scenarios.

Impact

• Users attempting to create printer shares with the “Allow all users in my organization” toggle enabled, or with specific users or groups selected on the share creation screen, are impacted.
• A code change to the Microsoft Graph API introduced an error that increased Entra ID directory replication latency and exposed a pre‑existing race condition in Universal Print’s share‑creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
• Microsoft has not disclosed which regions or how many users are affected, but the incident is flagged as a critical service issue.

Mitigation Procedure (13 steps)

1. Go to the Azure portal → Universal Print → Printers.
2. Select the printer you want to share.
3. Click “Printer Share” (or “Share Printer”).
4. Enter the share name.
5. Do NOT check “Allow all users in my organization.” Leave it unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click “Share Printer.”
8. Wait 30 seconds for the share to fully propagate.
9. Navigate to Universal Print → Printer Shares.
10. Select the newly created share.
11. Go to the “Members” tab (or “Access Control”).
12. Add users or security groups manually.
13. If all users need access, add an organization‑wide security group (e.g., “All Company”) from your Entra ID directory.

After applying the workaround, users should wait 1–2 minutes and retry if the share creation still fails.

Related Recent Updates

• Last month, Microsoft released out‑of‑band updates to fix broken sign‑ins with Microsoft accounts across multiple Microsoft apps.
• More recently, Microsoft reverted a service update that prevented some Teams users from launching the desktop client, and released emergency updates to address Windows Server issues causing security‑update installation problems and domain‑controller restart loops.