Status Page

2026-05-19	Status	Description
02:40 PM		DetailsTitle: Users may be unable to access or may experience delays when accessing Microsoft Fabric User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric. Current status: Our service health monitoring has alerted us to increased failures occurring when users attempt to access Microsoft Fabric. We're investigating the call requests to the portion of service infrastructure responsible for facilitating access to Microsoft Fabric to identify the source of the failures. Start time: Monday, May 18, 2026, at 12:24 PM UTC Next update by: Monday, May 18, 2026, at 4:30 PM UTC
02:39 PM		DetailsTitle: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot. Current status: We've determined that a recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot. We're rolling back this recent service update to remediate impact. Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted. Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot. Next update by: Monday, May 18, 2026, at 8:30 PM UTC
02:38 PM		Impacted servicesMicrosoft Copilot (Microsoft 365) DetailsTitle: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center. More info: Specifically, admins in the North America and the Asia-Pacific regions attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted by delays. While impact was ongoing, the latest refresh date shown may have been outdated since May 11, 2026. Final status: We've resolved the upstream delays that were leading to impact and have since validated through analyzing service health telemetry that this has successfully remediated all impact. Scope of impact: Admins in the North America and the Asia-Pacific regions attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted. Start time: Saturday, May 16, 2026, at 12:00 AM UTC End time: Monday, May 18, 2026, at 12:24 PM UTC
02:18 PM		Impacted services 365 Copilot Chat DetailsTitle: Users may be unable to access Copilot Voice in 365 Copilot Chat or conduct voice conversations User impact: Users may be unable to access Copilot Voice in Copilot Chat or conduct voice conversations. Current status: Our internal service monitoring has identified an issue that may be preventing users from accessing Copilot Voice in Copilot Chat or conducting voice conversations. We're analyzing recent service updates as we isolate the source for the issue and determine our next troubleshooting steps for remediating the impact. Scope of impact: This issue may prevent any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations. Start time: Sunday, May 17, 2026, at 3:30 AM UTC Next update by: Monday, May 18, 2026, at 12:00 AM UTC
01:30 PM		DetailsTitle: Some users may see repeated location prompts in Teams for Mac User impact: Users may see repeated location prompts in Teams for Mac. More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.": "Teams Modulehost would like to use your current location" Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting. Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in TM1315837. This communication will expire in 24 hours.
01:28 PM		DetailsTitle: Some users may see that some Viva Engage message posting operations are failing User impact: Users may have see that some Viva Engage message posting operations were failing. Final status: We've determined that a recent deployment introduced a compatibility issue between message posting operations that resulted in impact. We've deployed a code change to resolve the compatibility issue, and we've confirmed with internal monitoring and testing that the issue is resolved. Scope of impact: Some users that performed Viva Engage message posting operations may have been affected. Start time: Saturday, May 16, 2026, at 10:00 PM UTC End time: Tuesday, May 19, 2026, at 12:05 AM UTC Root cause: A recent deployment introduced a compatibility issue between message posting operations that resulted in impact
01:27 PM		DetailsTitle: Users may be unable to edit pages using SharePoint Designer User impact: Users may be unable to edit pages using SharePoint Designer. More info: Due to issues with the SharePoint Online Designer API, impacted users will need to utilize the following steps for updating SharePoint Online pages: 1. Ensure the DenyACP aka NoScript security protection is currently off for the site 2. Download the ASPX file 3. Make edits to the aspx file as necessary using a text editor other than SP Designer or Visual Studio. 4. Upload the ASPX file Please note that step four will be impacted by the Support for Content Security Policy (CSP) in SharePoint Online, of which more details can be found at the following link: https://learn.microsoft.com/en-us/sharepoint/dev/spfx/content-securty-policy-trusted-script-sources Final status: We've determined that the API that allows editing within SharePoint Online Designer entered a problematic configuration state preventing us from restoring it. Users will need to utilize the steps outlined in the More Info portion of this communication for updating SharePoint Online pages. Users continuing to encounter problems editing SharePoint Online pages should contact one of our support representatives so we can continue our investigation into the problem. Scope of impact: This issue may prevent any user from editing SharePoint Online pages using SharePoint Designer. Start time: Wednesday, May 13, 2026, at 6:01 PM UTC
11:51 AM		DetailsTitle: Some users may see repeated location prompts in Teams for Mac User impact: Users may see repeated location prompts in Teams for Mac. More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.": "Microsoft Teams Modulehost would like to use your current location" Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting. Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication. Scope of impact: This issue impacts some Teams for Mac users who have location access enabled in Teams settings. Start time: Monday, May 11, 2026, at 12:00 AM UTC Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC
11:39 AM		DetailsTitle: Some users with Technical Preview access may have been unable to modify existing webinars in Teams User impact: Users with Technical Preview access may have been unable to modify existing webinars in Teams. Final status: We've completed reverting the aforementioned update and confirmed impact is no longer occurring after a period of monitoring. Scope of impact: Impact was specific to some users who had early release or technical preview access, attempting to update existing webinars in Virtual Events powered by Teams. Start time: Friday, May 08, 2026, at 8:44 AM UTC End time: Thursday, May 14, 2026, at 3:49 PM UTC
11:37 AM		DetailsTitle: Some users may see repeated location prompts in Teams for Mac User impact: Users may see repeated location prompts in Microsoft Teams for Mac. More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.": "Teams Modulehost would like to use your current location" Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting. Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’ve reported this issue to Apple and are working with them to better understand the change and identify a resolution. Scope of impact: This issue impacts some Teams for Mac users who have location access enabled in Teams settings. Start time: Monday, May 11, 2026, at 12:00 AM UTC Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. Next update by: Tuesday, May 19, 2026, at 2:30 PM UTC

02:40 PM

DetailsTitle: Users may be unable to access or may experience delays when accessing Microsoft Fabric

User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.

Current status: Our service health monitoring has alerted us to increased failures occurring when users attempt to access Microsoft Fabric. We're investigating the call requests to the portion of service infrastructure responsible for facilitating access to Microsoft Fabric to identify the source of the failures.

Start time: Monday, May 18, 2026, at 12:24 PM UTC

Next update by: Monday, May 18, 2026, at 4:30 PM UTC

02:39 PM

DetailsTitle: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot

User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.

Current status: We've determined that a recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot. We're rolling back this recent service update to remediate impact.

Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.

Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.

Next update by: Monday, May 18, 2026, at 8:30 PM UTC

02:38 PM

Impacted servicesMicrosoft Copilot (Microsoft 365)

DetailsTitle: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center

User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center.

More info: Specifically, admins in the North America and the Asia-Pacific regions attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted by delays. While impact was ongoing, the latest refresh date shown may have been outdated since May 11, 2026.

Final status: We've resolved the upstream delays that were leading to impact and have since validated through analyzing service health telemetry that this has successfully remediated all impact.

Scope of impact: Admins in the North America and the Asia-Pacific regions attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted.

Start time: Saturday, May 16, 2026, at 12:00 AM UTC

End time: Monday, May 18, 2026, at 12:24 PM UTC

02:18 PM

Impacted services 365 Copilot Chat

DetailsTitle: Users may be unable to access Copilot Voice in 365 Copilot Chat or conduct voice conversations

User impact: Users may be unable to access Copilot Voice in Copilot Chat or conduct voice conversations.

Current status: Our internal service monitoring has identified an issue that may be preventing users from accessing Copilot Voice in Copilot Chat or conducting voice conversations. We're analyzing recent service updates as we isolate the source for the issue and determine our next troubleshooting steps for remediating the impact.

Scope of impact: This issue may prevent any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations.

Start time: Sunday, May 17, 2026, at 3:30 AM UTC

Next update by: Monday, May 18, 2026, at 12:00 AM UTC

01:30 PM

DetailsTitle: Some users may see repeated location prompts in Teams for Mac

User impact: Users may see repeated location prompts in Teams for Mac.

More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":

"Teams Modulehost would like to use your current location"

Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.

Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in TM1315837. This communication will expire in 24 hours.

01:28 PM

DetailsTitle: Some users may see that some Viva Engage message posting operations are failing

User impact: Users may have see that some Viva Engage message posting operations were failing.

Final status: We've determined that a recent deployment introduced a compatibility issue between message posting operations that resulted in impact. We've deployed a code change to resolve the compatibility issue, and we've confirmed with internal monitoring and testing that the issue is resolved.

Scope of impact: Some users that performed Viva Engage message posting operations may have been affected.

Start time: Saturday, May 16, 2026, at 10:00 PM UTC

End time: Tuesday, May 19, 2026, at 12:05 AM UTC

Root cause: A recent deployment introduced a compatibility issue between message posting operations that resulted in impact

01:27 PM

DetailsTitle: Users may be unable to edit pages using SharePoint Designer

User impact: Users may be unable to edit pages using SharePoint Designer.

More info: Due to issues with the SharePoint Online Designer API, impacted users will need to utilize the following steps for updating SharePoint Online pages:

1. Ensure the DenyACP aka NoScript security protection is currently off for the site

2. Download the ASPX file

3. Make edits to the aspx file as necessary using a text editor other than SP Designer or Visual Studio.

4. Upload the ASPX file

Please note that step four will be impacted by the Support for Content Security Policy (CSP) in SharePoint Online, of which more details can be found at the following link:

https://learn.microsoft.com/en-us/sharepoint/dev/spfx/content-securty-policy-trusted-script-sources

Final status: We've determined that the API that allows editing within SharePoint Online Designer entered a problematic configuration state preventing us from restoring it. Users will need to utilize the steps outlined in the More Info portion of this communication for updating SharePoint Online pages. Users continuing to encounter problems editing SharePoint Online pages should contact one of our support representatives so we can continue our investigation into the problem.

Scope of impact: This issue may prevent any user from editing SharePoint Online pages using SharePoint Designer.

Start time: Wednesday, May 13, 2026, at 6:01 PM UTC

11:51 AM

DetailsTitle: Some users may see repeated location prompts in Teams for Mac

User impact: Users may see repeated location prompts in Teams for Mac.

More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":

"Microsoft Teams Modulehost would like to use your current location"

Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.

Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication.

Scope of impact: This issue impacts some Teams for Mac users who have location access enabled in Teams settings.

Start time: Monday, May 11, 2026, at 12:00 AM UTC

Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.

Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC

11:39 AM

DetailsTitle: Some users with Technical Preview access may have been unable to modify existing webinars in Teams

User impact: Users with Technical Preview access may have been unable to modify existing webinars in Teams.

Final status: We've completed reverting the aforementioned update and confirmed impact is no longer occurring after a period of monitoring.

Scope of impact: Impact was specific to some users who had early release or technical preview access, attempting to update existing webinars in Virtual Events powered by Teams.

Start time: Friday, May 08, 2026, at 8:44 AM UTC

End time: Thursday, May 14, 2026, at 3:49 PM UTC

11:37 AM

DetailsTitle: Some users may see repeated location prompts in Teams for Mac

User impact: Users may see repeated location prompts in Microsoft Teams for Mac.

More info: Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":

"Teams Modulehost would like to use your current location"

Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Teams" and "Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.

Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’ve reported this issue to Apple and are working with them to better understand the change and identify a resolution.

Scope of impact: This issue impacts some Teams for Mac users who have location access enabled in Teams settings.

Start time: Monday, May 11, 2026, at 12:00 AM UTC

Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.

Next update by: Tuesday, May 19, 2026, at 2:30 PM UTC