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.
“Some users attempting to create printer shares created with the ‘Allow all users in my organization’ toggle enabled or with specific users or groups selected on the share creation screen are impacted,” Microsoft explained.
“We’ve isolated a code change to Microsoft Graph API that introduced a code error, which 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.”
Although Microsoft has yet to share which regions or how many users are affected by this ongoing issue, it tagged it as an incident, a flag commonly used to describe critical service issues with noticeable user impact.
Microsoft is now deploying a code change to correct the code error and shared a 13-step mitigation procedure that can help affected users work around the issue until it’s fixed:
- Go to the Azure portal, then Universal Print, then Printers
- Select the printer you want to share
- Click “Printer Share” (or “Share Printer”)
- Enter the share name
- Do NOT check “Allow all users in my organization.” Leave this unchecked.
- Do NOT select any specific users or groups at this step.
- Click “Share Printer”
- Wait 30 seconds for the share to fully propagate
- Navigate to Universal Print, then Printer Shares
- Select the newly created share
- Go to the “Members” tab (or “Access Control”)
- Add users or security groups manually
- 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 are advised to wait 1 to 2 minutes and retry if the share creation still fails.
Last month, Microsoft also released out-of-band updates to fix broken sign-ins with Microsoft accounts across multiple Microsoft apps.
More recently, on Friday, Microsoft reverted a service update that was preventing some Microsoft Teams users from launching the desktop client, and released a set of emergency updates over the weekend to address known Windows Server issues causing security update installation problems and domain controllers entering a restart loop.
AI chained four zero-days into one exploit that bypassed both renderer and OS sandboxes. A wave of new exploits is coming.
At the Autonomous Validation Summit (May 12 & 14), see how autonomous, context-rich validation finds what’s exploitable, proves controls hold, and closes the remediation loop.
