Find notable cyber news and cases, enriched with sources, timelines, and signals.
Home Browse News Feed Stats Watchlists Beta About Contact

Microsoft Universal Print share-creation disruption

Service Disruption
First reported
Last updated
Happening score
H score 13
1 unique sources, 1 articles

Summary

Hide ▲

Microsoft Universal Print is experiencing an ongoing share-creation disruption that can prevent printer shares from completing and leave users with "Sharing Print Failed" errors. The issue was traced to a Microsoft Graph API code change that increased Entra ID directory replication latency and triggered a pre-existing race condition. Microsoft is deploying a fix and has provided a 13-step workaround for affected users.

Related Happenings

Microsoft Teams on macOS repeated location-prompt service disruption

Service Disruption
First: 19.05.2026 19:10 Last: 19.05.2026 19:10 Sources 1

About this happening: Microsoft confirmed a **Microsoft Teams on macOS** service disruption that causes **non-dismissible location prompts** for some users, interrupting normal app use for those who en...

Open Happening

Azure AD Graph API authentication failure security flaw (CVE-2025-55241)

Vulnerability
First: 19.09.2025 16:47 Last: 19.09.2025 16:47 Sources 1

About this happening: **CVE-2025-55241** is a **critical** token validation failure in **Microsoft Entra ID** and the legacy **Azure AD Graph API** that could let an attacker impersonate users, includi...

Open Happening

Timeline

  1. 22.04.2026 13:15 2 articles · 1mo ago

    Microsoft confirms Universal Print share-creation disruption

    Technical Analysis Update

    Microsoft confirmed an ongoing Universal Print disruption in which some Microsoft 365 customers may intermittently see "Sharing Print Failed" errors while creating printer shares, including shares created with "Allow all users in my organization" enabled or with specific users or groups selected. Microsoft traced the problem to a Microsoft Graph API code change that increased Entra ID directory replication latency and exposed a pre-existing race condition in the share-creation flow, and it is deploying a code change while providing a 13-step workaround that delays retry and adds members manually after the share propagates.

    Show sources
    Open in new tab