Microsoft 365

Microsoft 365 service health

Current service status and unresolved incidents and advisories for your tenant.

Service status

0Interrupted
5Needs attention
24Healthy or restored
0Other or unknown

Services needing attention appear first. Select a service with linked issues to read its updates below.

ServiceStatusActive issues
Exchange Online Service degradation A service or feature may be affected. No matching active issues
Microsoft 365 suite Service degradation A service or feature may be affected. 5 issues
Microsoft Intune Service degradation A service or feature may be affected. 1 issue
Microsoft Purview Service degradation A service or feature may be affected. 1 issue
Microsoft Teams Service degradation A service or feature may be affected. No matching active issues
Basic Mobility and Security Service operational No service issues have been identified. No matching active issues
Dynamics 365 Apps Service operational No service issues have been identified. No matching active issues
Microsoft 365 apps Service operational No service issues have been identified. No matching active issues
Microsoft 365 Copilot Chat Service operational No service issues have been identified. No matching active issues
Microsoft 365 for the web Service operational No service issues have been identified. No matching active issues
Microsoft Bookings Service operational No service issues have been identified. No matching active issues
Microsoft Clipchamp Service operational No service issues have been identified. No matching active issues
Microsoft Defender XDR Service operational No service issues have been identified. No matching active issues
Microsoft Entra Service operational No service issues have been identified. No matching active issues
Microsoft Forms Service operational No service issues have been identified. No matching active issues
Microsoft OneDrive Service operational No service issues have been identified. No matching active issues
Microsoft Power Automate Service operational No service issues have been identified. No matching active issues
Microsoft Power Automate in Microsoft 365 Service operational No service issues have been identified. No matching active issues
Microsoft Stream Service operational No service issues have been identified. No matching active issues
Microsoft Viva Service operational No service issues have been identified. No matching active issues
Planner Service operational No service issues have been identified. No matching active issues
Power Apps Service operational No service issues have been identified. No matching active issues
Power Apps in Microsoft 365 Service operational No service issues have been identified. No matching active issues
Power BI Service operational No service issues have been identified. No matching active issues
Project for the web Service operational No service issues have been identified. No matching active issues
SharePoint Online Service operational No service issues have been identified. No matching active issues
Sway Service operational No service issues have been identified. No matching active issues
Universal Print Service operational No service issues have been identified. No matching active issues
Windows Autopatch Service operational No service issues have been identified. No matching active issues

Unresolved issues

Open an issue's updates to read the information provided by Microsoft.

Microsoft 365 suite (5)

  • Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile

    Service degradation

    MO1489432 · advisory · Origin: microsoft · Started 10/06/2026 11:45 · Updated 11/20/2026 14:16

    Affected feature: Portal / Access

    Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.

    Read Microsoft updates (23)

    11/20/2026 14:16

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’re progressing with deploying the code fix to repair the remaining affected contacts on a user basis. The deployment is ongoing and expected to complete by Tuesday, November 24, 2026. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component had incorrectly separated some PBCs from their associated profiles when specific contact information wasn't explicitly stored, causing affected contacts to appear as blank. Next update by: Tuesday, November 24, 2026, at 3:00 PM UTC

    11/13/2026 11:09

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’re proceeding to deploy a code fix to repair the remaining affected contacts on a user basis. The deployment is due to complete by Friday, November 20, 2026, and we’re continuing to monitor as the rollout progresses. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component had incorrectly separated some PBCs from their associated profiles when specific contact information wasn't explicitly stored, causing affected contacts to appear as blank. Next update by: Friday, November 20, 2026, at 3:00 PM UTC

    11/11/2026 10:50

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We're continuing to review affected contact details to determine if an additional fix would be effective in recovering the small amount of remaining impact. In parallel, we're reviewing additional diagnostic information to investigate why these contacts remain unrecovered and establish the additional mitigation steps needed to fully restore them. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component had incorrectly separated some PBCs from their associated profiles when specific contact information wasn't explicitly stored, causing affected contacts to appear as blank. Next update by: Friday, November 13, 2026, at 11:30 AM UTC

    11/09/2026 10:31

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We're reviewing affected contact details to determine if an additional fix would be effective in recovering the small amount of remaining impact. In parallel, we're also continuing to work with affected organizations to gather additional diagnostic information to investigate why these contacts remain unrecovered and establish the additional mitigation steps needed to fully restore them. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component had incorrectly separated some PBCs from their associated profiles when specific contact information wasn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, November 11, 2026, at 11:00 AM UTC

    11/05/2026 10:52

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We've completed the recovery process to address the original issue that caused contact records to become separated from their associated profiles, restoring visibility for the affected contacts. However, during this process, we identified a separate, underlying code issue that's preventing some affected contacts from being recovered. We're working with affected organizations to gather additional diagnostic information to investigate why these contacts remain unrecovered and establish the additional mitigation steps needed to fully restore them. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component had incorrectly separated some PBCs from their associated profiles when specific contact information wasn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, November 9, 2026, at 11:00 AM UTC

    11/04/2026 10:30

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We're working to identify the additional mitigation steps needed to fully resolve the issue for the remaining users who are still experiencing impact. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Thursday, November 5, 2026, at 11:00 AM UTC

    11/03/2026 09:35

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We're continuing to investigate why a number of users are still experiencing impact to determine what additional mitigations are required to fully resolve the issue. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, November 4, 2026, at 11:00 AM UTC

    11/03/2026 09:35

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We're continuing to investigate why a number of users are still experiencing impact to determine what additional mitigations are required to fully resolve the issue. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, November 4, 2026, at 11:00 AM UTC

    11/02/2026 10:40

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We've determined via our monitoring systems that over 99.5 percent of contacts have now been processed. We've received confirmation that the issue is resolved for the majority of affected users. We're investigating why a number of users are still experiencing impact to determine what additional mitigations are required to fully resolve the issue. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Tuesday, November 3, 2026, at 11:00 AM UTC

    10/30/2026 10:56

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: Further monitoring indicates that approximately 95 percent of affected contacts have now been processed. We expect most users to now experience relief from impact, and we’re continuing to monitor the remaining recovery before confirming that the issue is fully resolved. We estimate full resolution by our next scheduled update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, November 2, 2026, at 11:00 AM UTC

    10/28/2026 09:40

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: Further monitoring indicates that approximately 90 percent of affected contacts have now been processed. We expect most users to now experience relief from impact, and we’re continuing to monitor the remaining recovery before confirming that the issue is fully resolved. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Friday, October 30, 2026, at 11:00 AM UTC

    10/28/2026 09:40

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: Further monitoring indicates that approximately 90 percent of affected contacts have now been processed. We expect most users to now experience relief from impact, and we’re continuing to monitor the remaining recovery before confirming that the issue is fully resolved. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Friday, October 30, 2026, at 11:00 AM UTC

    10/26/2026 09:35

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve completed deployment of the additional fix and have begun processing the affected contacts to restore them. Our monitoring indicates that approximately 90 percent of affected contacts have now been processed. We expect most users to now experience relief from impact, and we’re continuing to monitor the remaining recovery before confirming that the issue is fully resolved. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, October 28, 2026, at 11:00 AM UTC

    10/22/2026 09:01

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve started to deploy the aforementioned additional fix to address the remaining impact and expect this to be complete by our next scheduled update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, October 26, 2026, at 10:00 AM UTC

    10/19/2026 08:46

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve completed deployment of our previous fix and determined that it only remediated impact for a small percentage of affected contacts. We’re validating an additional fix to address the remaining impact and, if successful, will begin deploying it to the affected environment. We anticipate to share a completion timeline by our next scheduled update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Thursday, October 22, 2026, at 10:00 AM UTC

    10/16/2026 09:48

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’re validating an additional fix in our internal environment to confirm its effectiveness before deploying it to the affected infrastructure. We’ll provide the deployment timeline once it becomes available. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, October 19, 2026, at 10:00 AM UTC

    10/14/2026 09:56

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We've confirmed that the fix should now have reached most affected users, and we're working with a subset of users to confirm its effectiveness and validate recovery. We've identified some cases where the issue persists and are working to implement additional fix. We'll provide an update once a deployment timeline for the additional fix is available. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Friday, October 16, 2026, at 10:00 AM UTC

    10/12/2026 09:20

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC

    10/12/2026 09:20

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC

    10/07/2026 09:26

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve completed validation of our fix in our internal testing environment and have begun deploying it across the affected environments. We’ve received confirmation from a subset of affected users that the fix successfully resolves the issue, and we’re continuing to monitor the broader deployment as it progresses. We expect the deployment to complete by Wednesday, October 14, 2026. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, October 12, 2026, at 10:00 AM UTC

    10/06/2026 18:49

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve begun deploying our fix to the internal environment to validate its effectiveness. Once this process has completed, we will provide a remediation timeline. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Wednesday, October 7, 2026, at 10:00 AM UTC

    10/06/2026 13:32

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve developed a fix and are deploying it to our internal environment to validate its effectiveness before deploying it to the affected environment. We expect to provide a deployment timeline and rollout trajectory in our next communication update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.

    10/06/2026 12:24

    Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: We’ve validated that a problem with a contact-processing component has incorrectly separated some Profile Based Contacts (PBCs) from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. We’re developing a fix to re-merge the affected contacts with their associated profiles and expect to provide deployment timeline by our next scheduled update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Tuesday, October 6, 2026, at 1:30 PM UTC
  • Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center

    Service degradation

    MO1535688 · advisory · Origin: microsoft · Started 11/02/2026 00:00 · Updated 11/03/2026 17:44

    Affected feature: Portal / Access

    Admins' Copilot and Copilot Chat usage reports were delayed by up to 24 hours in the Microsoft 365 admin center.

    Read Microsoft updates (3)

    11/03/2026 17:43

    Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center User impact: Admins' Copilot and Copilot Chat usage reports were delayed by up to 24 hours in the Microsoft 365 admin center. Final status: We've resolved the upstream pipeline degradation, and the affected reporting jobs have completed successfully. After monitoring the service, we've confirmed that Microsoft 365 Copilot and Copilot Chat usage reports have fully recovered across all affected regions. Scope of impact: Some admins' Copilot and Copilot Chat usage reports may have been delayed by up to 24 hours in the Microsoft 365 admin center. Start time: Monday, November 2, 2026, at 12:00 AM UTC End time: Tuesday, November 3, 2026, at 1:20 AM UTC Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot Chat usage reports caused impact. Next steps: We're investigating why the upstream data pipeline didn't function as intended to implement measures for preventing this problem from happening again in the future. This is the final update for the event.

    11/03/2026 01:31

    Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center User impact: Admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. Current status: We're continuing our efforts to resolve the pipeline degradation and restore reports. We anticipate this may complete by our next scheduled update. Scope of impact: Some admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. This section may be updated as the investigation progresses. Start time: Monday, November 2, 2026, at 12:00 AM UTC Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot chat usage reports is causing impact. Next update by: Tuesday, November 3, 2026, at 7:00 PM UTC

    11/02/2026 18:15

    Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center User impact: Admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. Current status: Our service telemetry has alerted us to ongoing data population delays of approximately 24 hours for Copilot and Copilot Chat usage reports to populate in the Microsoft 365 admin center. We're isolated that a degradation in the upstream data pipeline used to populate these reports is causing impact, and we're working to remediate the degradation to restore reports as soon as possible. Scope of impact: Some admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. This section may be updated as the investigation progresses. Start time: Monday, November 2, 2026, at 12:00 AM UTC Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot chat usage reports is causing impact. Next update by: Tuesday, November 3, 2026, at 3:00 AM UTC
  • Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs

    Service degradation

    MO1457843 · advisory · Origin: microsoft · Started 07/10/2026 14:05 · Updated 10/31/2026 00:04

    Affected feature: Administration / Company or User Administration

    Admins couldn't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.

    Read Microsoft updates (5)

    10/31/2026 00:04

    Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins couldn't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applied to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins who needed to identify who deleted a specific community or group during the affected period could have opened a Microsoft support case with the deletion date and group/community details so support could trace the initiating user through service-side logs. Final status: After identifying additional options to expedite remediation, we've confirmed that all three phases of our fix have deployed earlier than expected. We've validated its efficacy and ensured that users who delete Viva Engage or Microsoft 365 groups are now logged in Microsoft Entra ID audit logs. Scope of impact: This issue prevented all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. Start time: Friday, July 10, 2026, at 2:05 PM UTC End time: Wednesday, October 21, 2026, at 4:30 PM UTC Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams resulted in impact. Next steps: - We're continuing to consult user reports to identify problem-causing scenarios so that we can develop comprehensive feature changes that meet user needs. This is the final update for the event.

    10/01/2026 22:50

    Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We're deploying the first of three changes which we need to make for to ensure a comprehensive long-term solution. Due to the complexity of these changes, we currently anticipate remediation by Friday, January 30, 2027. We're continuing to monitor the progress of our deployment to identify any opportunities to expedite the process. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Start time: Friday, July 10, 2026, at 2:05 PM UTC Estimated time to resolve: We estimate that our three-phase improvement will be complete by January 30, 2027. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Friday, October 30, 2026, at 11:00 PM UTC

    09/16/2026 22:07

    Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We're progressing with our additional levels of validations so we can ensure that our solution returns admins ability to determine who deleted Viva Engage communities or its Microsoft 365 Group in Entra ID audit logs. We'll provide an updated timeline for the deployment of our fix and the remediation of the impact once our pre-deployment tests have concluded. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Start time: Friday, July 10, 2026, at 2:05 PM UTC Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Thursday, October 1, 2026, at 11:00 PM UTC

    09/02/2026 22:29

    Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We've determined that resolving this issue requires additional validation to ensure that our fix addresses the impact without introducing unintended effects to the service. We're continuing testing and validation efforts and will provide an updated deployment timeline once those activities are completed. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Wednesday, September 16, 2026, at 11:00 PM UTC

    08/19/2026 22:38

    Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We've identified an update to our Viva Engage communities that’s preventing admins from identifying users who deleted a Viva Engage community or its connected Microsoft 365 Group in Microsoft Entra ID audit logs. We've developed and are internally validating a fix to remediate the impact. We'll provide an updated timeline for the deployment of our solution and the remediation of the impact once it has become available. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Wednesday, September 2, 2026, at 11:00 PM UTC
  • Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps

    Service degradation

    MO1507859 · advisory · Origin: microsoft · Started 10/12/2026 20:48 · Updated 10/14/2026 20:22

    Affected feature: Portal / Access

    Users may have been missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps.

    Read Microsoft updates (2)

    10/14/2026 20:22

    Title: Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps User impact: Users may have been missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps. More info: This issue was occurring in the following Microsoft 365 apps: - Microsoft Teams desktop client - Microsoft Teams web client - Outlook on the web - Outlook desktop client The issue only occurred in standard Teams meetings, and live events, webinars, and town halls weren’t affected. Final status: We've validated with a subset of affected users that our rollback of the problematic tenant filter has remediated impact. Scope of impact: This issue impacted some users who may have been missing the "Meeting options” button when creating standard meetings using multiple Microsoft 365 apps. Start time: Monday, October 12, 2026, at 8:48 PM UTC End time: Wednesday, October 14, 2026, at 6:16 PM UTC Root cause: A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations. Next steps: - We're analyzing the problematic tenant filter to validate why it was applied broadly to further our understanding of how the issue was introduced and to evaluate what actions we can take to prevent similar impact scenarios from occurring in the future. This is the final update for the event.

    10/14/2026 19:04

    Title: Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps User impact: Users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps. More info: This issue is occurring in the following Microsoft 365 apps: - Microsoft Teams desktop client - Microsoft Teams web client - Outlook on the web - Outlook desktop client The issue only occurs in standard Teams meetings, and live events, webinars, and town halls aren’t affected. Current status: We've received reports from multiple organizations noting that some users are missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps as listed in the "More info" section of this communication. We've isolated that a tenant filter to disable the "Meetings option" button for a specific group of users was unintentionally applied broadly. We're rolling back the offending change, and we anticipate impact to be remediated by our next scheduled update. Scope of impact: This issue impacts some users who may be missing the "Meeting options” button when creating standard meetings using multiple Microsoft 365 apps. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 8:48 PM UTC Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Wednesday, October 14, 2026, at 9:00 PM UTC. Root cause: A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations. Next update by: Wednesday, October 14, 2026, at 9:00 PM UTC
  • Users may have been unable to sign into the OneNote Web Clipper

    Service degradation

    MO1447619 · advisory · Origin: microsoft · Started 07/24/2026 08:06 · Updated 08/06/2026 11:38

    Affected feature: Administration / Company or User Administration

    Users may have been unable to sign into the OneNote Web Clipper.

    Read Microsoft updates (9)

    08/06/2026 11:37

    Title: Users may have been unable to sign into the OneNote Web Clipper User impact: Users may have been unable to sign into the OneNote Web Clipper. More info: Users may have received an error when attempting to sign into the OneNote Web Clipper. Final status: We've completed the deployment of the fix, and service monitoring indicates that the impact has now been resolved. Scope of impact: Your organization was affected by this event, and any users attempting to sign in to OneNote Web Clipper were impacted. Start time: Friday, July 24, 2026, at 8:06 AM UTC End time: Thursday, August 6, 2026, at 10:20 AM UTC Root cause: A recent maintenance update intended to remove unnecessary components from the service inadvertently removed a required authentication component, resulting in impact. Next steps: - We're reviewing our service maintenance procedures and validation processes to help prevent this problem from happening again. This is the final update for the event.

    08/06/2026 10:20

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've completed the deployment of our fix to the majority of the affected environments and anticipate that most users will no longer be affected by the issue. We expect deployment to complete in the remaining affected infrastructure by our next scheduled update. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Thursday, August 6, 2026, at 12:30 PM UTC

    08/06/2026 05:11

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've completed validations on the new fix and have initiated its deployment. We're monitoring as it progresses to establish a completion timeline. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Thursday, August 6, 2026, at 10:30 AM UTC

    08/05/2026 20:38

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've completed the deployment of our fix to our internal testing environment; however, the fix did not resolve the issue as expected. We've prepared another fix which is being deployed to our testing environment. Once complete, we'll perform validations and confirm if we see impact remediation, after which we'll confirm a timeline for deployment to the affected environment. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Thursday, August 6, 2026, at 6:30 AM UTC

    08/05/2026 13:55

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've confirmed that the deployment is progressing as expected and anticipate sharing a completion timeline by our next scheduled update. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Wednesday, August 5, 2026, at 9:30 PM UTC

    08/05/2026 03:22

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've identified that the deployment of the fix is taking longer than initially anticipated, but we're monitoring its progress closely to ensure the deployment completes without encountering any complications. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Wednesday, August 5, 2026, at 2:00 PM UTC

    08/05/2026 00:52

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've completed creating the code fix, and we've initiated deployment to the imapcted environment. We expect the deployment will be complete and the issue resolved by our next scheduled update. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Wednesday, August 5, 2026, at 3:30 AM UTC

    08/04/2026 22:32

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We've identified that a recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication HTML, preventing users from signing into the OneNote Web Clipper. We're creating a code fix that will add this authentication HTML back into the service and remediate impact. Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper is impacted. This information may be updated as our investigation continues. Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper. Next update by: Wednesday, August 5, 2026, at 1:00 AM UTC

    08/04/2026 22:09

    Title: Users may be unable to sign into the OneNote Web Clipper User impact: Users may be unable to sign into the OneNote Web Clipper. More info: Users may receive an error when attempting to sign into the OneNote Web Clipper. Current status: We're investigating a potential issue with the OneNote Web Clipper and checking for impact to your organization. We'll provide an update within 30 minutes.

Microsoft Intune (1)

  • Some users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune

    Service degradation

    IT1549049 · advisory · Origin: microsoft · Started 11/11/2026 16:34 · Updated 11/18/2026 01:01

    Affected feature: Microsoft Intune / Microsoft Intune

    Users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune.

    Read Microsoft updates (4)

    11/12/2026 01:18

    Title: Some users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune User impact: Users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune. More info: A recent Windows security update, MSRC144654, can cause a single device check in to fail during installation. Affected devices receive pending changes at their next successful check in. Users can check in manually after the update finishes instead of waiting for the next scheduled check in. Current status: We’ve confirmed that a recent Windows security update, MSRC144654, can cause a single check in to fail during installation. We’re developing a fix to address this issue and anticipate its release for early December 2026. We’ll provide a better estimate for the delivery of our fix when available. Scope of impact: Some users with Windows devices enrolled in Microsoft Intune may experience delays receiving policies, apps, and other changes while their devices install Windows security update MSRC144654. This information may be updated as our investigation continues. Root cause: A recent Windows security update, MSRC144654, can cause a single check in to fail during installation. Next update by: Wednesday, November 25, 2026, at 2:30 AM UTC

    11/11/2026 19:48

    Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours. More info: While we're working to remediate impact, affected users can perform a manual check-in. Current status: We've confirmed that a component introduced in a recent Windows update is causing the issue and are developing a fix. We'll provide an estimated release timeline once one is available. Scope of impact: Any user with a Microsoft Intune enrolled Windows device may be affected. This information may be updated as our investigation continues. Root cause: A recent Windows update contains a code issue affecting Intune's ability to perform an initial check-in, resulting in impact. Next update by: Thursday, November 12, 2026, at 2:30 AM UTC

    11/11/2026 16:57

    Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours. More info: While we're working to remediate impact, affected users can perform a manual check-in. Current status: This event is a continuation of the issue previously communicated via IT1547988. Our monitoring has identified an increase in delays affecting check-ins for Microsoft Intune-enrolled Windows devices. Our investigation indicates that an issue in a recent Windows update is causing initial device check-in attempts to fail, while subsequent automated and manual attempts remain unaffected. We're continuing to analyze the changes introduced in the recent Windows update to isolate the specific root cause and determine an appropriate remediation strategy. Scope of impact: Any user with a Microsoft Intune enrolled Windows device may be affected. This information may be updated as our investigation continues. Next update by: Wednesday, November 11, 2026, at 8:00 PM UTC

    11/11/2026 16:37

    Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours. Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

Microsoft Purview (1)

  • Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit

    Service degradation

    MP1507695 · advisory · Origin: microsoft · Started 10/14/2026 16:14 · Updated 11/19/2026 04:45

    Affected feature: Microsoft Purview / General

    Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit.

    Read Microsoft updates (7)

    11/19/2026 04:45

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected admins may encounter delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Specifically, admins may experience various latency ranges before all of the Audit log data is available for search in the Purview portal. Current status: The processing of the backlog of affected events is taking an extended period to complete and we're continuing to monitor it as it steadily progresses. Scope of impact: Any admin attempting to access audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, November 26, 2026, at 6:30 AM UTC

    11/12/2026 05:08

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected admins may encounter delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Specifically, admins may experience various latency ranges before all of the Audit log data is available for search in the Purview portal. Current status: The processing of the aforementioned backlog is steadily progressing and users should see relief as it continues to progress. We'll continue to monitor it to ensure it successfully completes and issue is resolved. Scope of impact: Any admin attempting to access audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, November 19, 2026, at 6:30 AM UTC

    11/05/2026 05:58

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Current status: The processing of the backlog of affected events is progressing as expected and we'll continue to monitor it along with relevant telemetry to ensure the service is recovering. Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, November 12, 2026, at 6:30 AM UTC

    10/29/2026 05:11

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Current status: Our efforts to process the backlog of affected events are ongoing. In parallel, we're monitoring relevant telemetry to verify improvement in system health. However, due to the complexity of this issue, more time will be required to confirm a timeline for remediation. Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, November 5, 2026, at 7:30 AM UTC

    10/22/2026 04:55

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Current status: We're continuing to monitor the backlog of affected events as they're processed. Due to the complexity of the issue, we're anticipating it may take some additional time before we're able to confirm a timeline for full remediation. Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, October 29, 2026, at 6:30 AM UTC

    10/21/2026 17:42

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview portal, Microsoft Graph API, or PowerShell. Current status: Our monitoring of the queued backlog continues to report reduced delays when accessing audit log data results in Microsoft Purview. We're continuing to monitor the events that require processing and expect clarity into the timeline for it completing by our next scheduled communication update. Scope of impact: Any admin accessing audit log data from Microsoft Purview may be affected. This information may be updated as our investigation continues. Next update by: Thursday, October 22, 2026, at 6:30 AM UTC

    10/14/2026 16:46

    Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview portal, Microsoft Graph API, or PowerShell. Current status: Our monitoring identified an increase in processing latency with Microsoft Purview audit log data. We've analyzed service telemetry and determined that a dependent service isn't processing requests as efficiently as expected, resulting in impact. We've taken action to rebalance load and improve throughput. While most users should see relief, we're continuing to monitor as the remaining backlog of events are processed, and we'll provide a complete remediation timeline once available. Scope of impact: Any admin accessing audit log data from Microsoft Purview may be affected. Next update by: Wednesday, October 21, 2026, at 6:00 PM UTC

For the Microsoft portal, open the Microsoft 365 admin center and select Health > Service health.