Penn Computing
Computing Menu Computing A-Z
Computing Home Information Systems & Computing Penn

Microsoft's Incident Report for PennO365

Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this list. Additionally you can check Microsoft's status page for current service status messages. The last extract was taken on Fri May 23 04:45:11 2025.

TM1061513 - Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting

Status:serviceDegradation
Start Time:Thu Apr 24 12:10:33 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri May 23 01:47:17 2025
Root Cause:Changes within a recent regularly scheduled service update are resulting in impact.
Next Update:Friday, May 30, 2025, at 5:30 AM UTC

Details

Time:Fri May 23 01:47:17 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: There is a slight delay with the deployment. We're continuing to closely monitor the progress and anticipate that it will complete by Friday, May 30.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Friday, May 30, 2025, at 5:30 AM UTC
Time:Wed May 14 00:14:21 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: The deployment is continuing to progress to the affected environments and we anticipate it will complete by Monday, May 26th.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, May 27, 2025, at 5:30 AM UTC
Time:Wed Apr 30 00:48:50 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're continuing to monitor the deployment of our fix and projections indicate this will complete by Monday, May 26th.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Wednesday, May 14, 2025, at 5:30 AM UTC
Time:Tue Apr 29 06:13:30 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're monitoring the deployment and anticipate completion by Monday, May 26, 2025. However, we're continuing to assess whether additional actions can be taken to expedite the deployment.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Wednesday, April 30, 2025, at 5:30 AM UTC
Time:Tue Apr 29 01:34:14 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're continuing to monitor the deployment as it progresses throughout the affected service environment. In parallel, we're continuing to assess whether additional actions can be taken to expedite remediation. We'll provide an estimated completion time for full remediation once one becomes available.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, April 29, 2025, at 10:30 AM UTC
Time:Fri Apr 25 01:50:40 2025
Description:Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We've identified that changes within a recent regularly scheduled service update are resulting in impact. We've developed and begun deploying a fix to the affected service environment, and anticipate a portion of affected users may be fully remediated by our next update. In the interim, we're continuing with analysis of the impacting update to identify potential options to expedite remediation.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, April 29, 2025, at 7:00 AM UTC
Time:Thu Apr 24 13:06:18 2025
Description:Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Current status: We're analyzing HTTP Archive format (HAR) traces provided by a subset of affected users to better understand the root cause of impact and what steps we can take to address the issue.
Scope of impact: Your organization is affected by this event, and users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Next update by: Thursday, April 24, 2025, at 7:30 PM UTC
Time:Thu Apr 24 12:23:36 2025
Description:Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Current status: We're reviewing support case information and analyzing affected network traces to better understand the underlying issue and what steps we can take to address impact.
Scope of impact: Your organization is affected by this event, and users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Next update by: Thursday, April 24, 2025, at 5:30 PM UTC
Time:Thu Apr 24 12:12:08 2025
Description:Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1080701 - Some users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks

Status:falsePositive
Start Time:Thu May 22 19:53:57 2025
End Time:Thu May 22 23:55:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Fri May 23 00:09:02 2025
Root Cause:Recent updates to the affected web browsers to enhance security against third-party cookies are preventing the affected services from leveraging SafeLinks as expected, leading to impact.
Next Update:N/A

Details

Time:Thu May 22 23:56:53 2025
Description:Title: Some users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks
User impact: Users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks.
Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours.
This is the final update for the event.
Time:Thu May 22 20:27:35 2025
Description:Title: Some users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks
User impact: Users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks.
More info: This issue impacts URL links contained in the following Microsoft 365 services: - Microsoft Teams for the web - Outlook on the web - Microsoft 365 for the web
This impact is limited to users who have third-party cookies disabled in their web browser. While we work to resolve this issue, users can bypass the impact where possible by enabling third-party cookies in the web browser.
Current status: Our investigation has determined that recent updates to the affected web browsers to enhance security against third-party cookies are preventing the affected services from leveraging SafeLinks as expected, leading to impact. We're evaluating potential methods to resolve this issue and remediate the impact.
Scope of impact: Your organization is affected by this event, and users leveraging SafeLinks using a web browser with third-party cookies enabled in some browser-based Microsoft 365 services may be impacted.
Root cause: Recent updates to the affected web browsers to enhance security against third-party cookies are preventing the affected services from leveraging SafeLinks as expected, leading to impact.
Next update by: Saturday, May 24, 2025, at 1:00 AM UTC
Time:Thu May 22 20:02:40 2025
Description:Title: Some users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks
User impact: Users' links in multiple browser-based Microsoft 365 services may not be properly evaluated by SafeLinks.
More info: This issue impacts URL links contained in the following Microsoft 365 services: - Microsoft Teams for the web - Outlook on the web - Microsoft 365 for the web
This impact is limited to users who have third-party cookies disabled in their web browser. While we work to resolve this issue, users can bypass the impact where possible by enabling third-party cookies in the web browser.
Current status: We're investigating a potential issue affecting multiple Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1080700 - Users' links in Microsoft Copilot (Microsoft 365) in copilot.microsoft.com may not be properly evaluated by SafeLinks

Status:falsePositive
Start Time:Thu May 22 19:55:36 2025
End Time:Thu May 22 23:55:51 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Fri May 23 00:08:56 2025
Root Cause:Recent updates to the affected web browsers to enhance security against third-party cookies are preventing the Copilot service from leveraging SafeLinks as expected, leading to impact.
Next Update:N/A

Details

Time:Thu May 22 23:56:05 2025
Description:Title: Users' links in Microsoft Copilot (Microsoft 365) in copilot.microsoft.com may not be properly evaluated by SafeLinks
User impact: Users' links in Copilot web accessed through copilot.microsoft.com may not be properly evaluated by SafeLinks.
Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours.
This is the final update for the event.
Time:Thu May 22 20:28:06 2025
Description:Title: Users' links in Microsoft Copilot (Microsoft 365) in copilot.microsoft.com may not be properly evaluated by SafeLinks
User impact: Users' links in Copilot web accessed through copilot.microsoft.com may not be properly evaluated by SafeLinks.
More info: Affected users receive the following error: "The link could not be verified due to an internal error. We recommend that you try again later."
This impact is limited to users who have third-party cookies disabled in their web browser. While we work to resolve this issue, users can bypass the impact where possible by enabling third-party cookies in the web browser.
Current status: Our investigation has determined that recent updates to the affected web browsers to enhance security against third-party cookies are preventing the Copilot service from leveraging SafeLinks as expected, leading to impact. We're evaluating potential methods to resolve this issue and remediate the impact.
Scope of impact: Users accessing links in Copilot web through copilot.microsoft.com may be impacted.
Root cause: Recent updates to the affected web browsers to enhance security against third-party cookies are preventing the Copilot service from leveraging SafeLinks as expected, leading to impact.
Next update by: Saturday, May 24, 2025, at 1:00 AM UTC
Time:Thu May 22 20:02:39 2025
Description:Title: Users' links in Microsoft Copilot (Microsoft 365) in copilot.microsoft.com may not be properly evaluated by SafeLinks
User impact: Users' links in Copilot web accessed through copilot.microsoft.com may not be properly evaluated by SafeLinks.
More info: Affected users receive the following error: "The link could not be verified due to an internal error. We recommend that you try again later."
This impact is limited to users who have third-party cookies disabled in their web browser. While we work to resolve this issue, users can bypass the impact where possible by enabling third-party cookies in the web browser.
Current status: We're investigating a potential issue affecting the Copilot service and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1078664 - Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell

Status:serviceDegradation
Start Time:Tue May 20 16:24:23 2025
End Time:N/A
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Thu May 22 23:59:06 2025
Root Cause:A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next Update:Wednesday, May 28, 2025, at 5:00 AM UTC

Details

Time:Thu May 22 23:59:06 2025
Description:Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We've developed a fix for the issue and are validating it in our internal testing environments before beginning deployment to the affected environments. We anticipate having an update on the status of the validation and deployment by the next scheduled update time.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Wednesday, May 28, 2025, at 5:00 AM UTC
Time:Tue May 20 22:48:48 2025
Description:Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We're continuing to work on creating the aforementioned fix, and once we’ve completed this process we’ll begin preparing it for deployment. We anticipate that we’ll be able to provide a deployment timeline by our next scheduled update.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Friday, May 23, 2025, at 5:00 AM UTC
Time:Tue May 20 17:56:31 2025
Description:Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We've identified that a recent service update modified the GetMailboxTableInfo API causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact. We're creating a fix to correct this compatibility issue and remediate impact. We'll provide a timeline for this fix if one becomes available.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 3:00 AM UTC
Time:Tue May 20 16:59:29 2025
Description:Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
Current status: We're reviewing data provided by some reporting users to identify why admins can't see the details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Next update by: Tuesday, May 20, 2025, at 10:30 PM UTC
Time:Tue May 20 16:36:33 2025
Description:Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1074644 - Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams

Status:serviceDegradation
Start Time:Wed Apr 23 03:00:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu May 22 22:19:29 2025
Root Cause:A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next Update:Saturday, May 24, 2025, at 10:00 PM UTC

Details

Time:Thu May 22 22:19:29 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: Our secondary fix has been deploying as expected and is at 87 percent saturation. We're now finalizing our tertiary fix which we anticipate will be completed and subsequently deployed prior to our next scheduled update. Additionally, we aim to gather a remediation timeline once the aforementioned actions have taken place.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 24, 2025, at 10:00 PM UTC
Time:Tue May 20 20:32:19 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've validated that our secondary fix has been deploying as expected and is at 19 percent saturation. Some users may see impact alleviate as the fix progresses toward completion.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 23, 2025, at 4:00 AM UTC
Time:Tue May 20 13:38:00 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve completed our internal validations of our secondary fix to ensure that its deployment addresses the language configuration issue without introducing any unexpected problems to the service. We’ve initiated deployment of our secondary fix which we anticipate will finish saturation by the end of day on Thursday, May 22, 2025. We aim to provide updates on our timeline to mitigation as the incident progresses towards resolution.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Wednesday, May 21, 2025, at 2:00 AM UTC
Time:Mon May 19 13:05:27 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: Our preventive fix has completed deployment and our testing with affected users has verified that it prevents additional users from experiencing the problem. In parallel, we're internally validating our secondary fix to ensure that its deployment addresses the language configuration issue without introducing any unexpected problems to the service, and we're expecting that an estimated timeline for its deployment and the remediation of impact will be available by our next scheduled update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
Time:Sat May 17 14:25:19 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: The preventive fix has been deployed and is progressing as expected. Deployment of the secondary fix is underway, and we’re continuing to monitor both efforts to ensure full remediation. We’ll provide a resolution timeline once it’s available.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Monday, May 19, 2025, at 6:30 PM UTC
Time:Sat May 17 03:30:00 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve deployed the aforementioned preventive fix to the affected environments, and are continuing to monitor its progress. Additionally, we're at the final stages of validating our secondary fix to address currently broken sites for deployment and expect to provide deployment time line by our next scheduled update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 8:00 PM UTC
Time:Fri May 16 23:29:51 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve tested and validated both our fixes and are deploying the preventive fix to the affected environments, which we anticipate may be completed by our next scheduled update. In parallel, we’re preparing our secondary fix to address currently broken sites for deployment, which is taking longer than previously anticipated and is now expected to begin deploying by our next update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 7:30 AM UTC
Time:Fri May 16 16:58:13 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: The testing and validation of our fixes is ongoing. We expect that our fix to address currently broken sites will begin deployment by our next scheduled update, at which time we also expect to have a timeline for the deployment of the fix to ensure newly created sites aren't impacted by this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 4:00 AM UTC
Time:Fri May 16 15:13:40 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've completed the development of the fix to ensure newly created sites no longer see the issue, as well as the other to repair existing sites which are impacted. We're proceeding with our testing and validation of both fixes in our internal testing environment to confirm their efficacy.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 9:30 PM UTC
Time:Fri May 16 13:20:38 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: After the test of our initial fix, we've confirmed that the issue impacts different types of site creation templates, indicating our fix is not comprehensive enough to resolve the entirety of impact. We're developing two additional fixes as a result; one of which will correct site creation templates so newly created sites aren't impacted by this issue and another to repair existing sites experiencing impact.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 7:30 PM UTC
Time:Fri May 16 08:44:01 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're progressing with testing the fix with a subset of affected users. Once completed, we'll start the deployment to all affected environments.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 5:30 PM UTC
Time:Fri May 16 04:05:24 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're continuing the final testing of our fix with a subset of affected users. Once complete we'll begin deploying the fix to the remainder of the affected environment.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 3:00 PM UTC
Time:Fri May 16 01:28:22 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're finalizing the testing of our fix with a subset of affected users prior to its full deployment. We're aiming to complete our testing by our next scheduled update, at which point we'll move ahead to begin deploying the fix throughout the remainder of the affected environment.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 8:30 AM UTC
Time:Fri May 16 00:11:56 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've completed the internal validation of our expedited fix for the issue to prevent any further newly created channels from becoming impacted and are now working to test the fix with a subset of affected users before deploying it throughout the rest of the impacted environment. Additionally, we've identified that some users are reporting that impact still occurs within the Microsoft Teams web client, and our latest understanding of the underlying root cause indicates that any file viewing requests reliant on the same API leveraged for viewing files through Microsoft Teams may fail due to this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 7:00 AM UTC
Time:Thu May 15 21:21:03 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've investigated our reproduction logs and have developed an expedited fix aimed at addressing and preventing future impact from occurring. We're preparing this fix for deployment now, while in parallel, we're continuing to investigate the source of the impact and whether this is correlated with a recent change made to the affected service.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Friday, May 16, 2025, at 4:30 AM UTC
Time:Thu May 15 18:04:50 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've successfully reproduced the impact and confirmed that the issue is only reproducible in the Microsoft Teams desktop client; the web client is unaffected. We're reviewing logs captured from our reproduction and identified that requests to gather information are being misrouted as the sites themselves are created in English, rather than in the language of their organization's locale as intended. This results in requests to retrieve the document library failing due to the mismatch in languages. We're continuing to investigate our reproduction logs to determine why this is occurring and formulate potential remediation actions.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Friday, May 16, 2025, at 2:30 AM UTC
Time:Thu May 15 16:20:42 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: Our review of the provided HAR logs is ongoing. We suspect that a fix for a previous issue with similar impact didn't appropriately deploy to some components of infrastructure as expected, resulting in requests from the API to retrieve the Files tab content routing incorrectly. We're attempting to reproduce this impact in our internal testing environment to confirm precisely where the failure occurs and determine our next troubleshooting steps.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 10:30 PM UTC
Time:Thu May 15 14:20:28 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: Our initial review of the errors in the ULS logs suggests the issue may be due to the API responsible for providing the Files contents returning an incorrect string, resulting in impact. We're investigating why this string is being returned, and we've reached out to a subset of affected users to request a reproduction of impact while capturing HTTP Archive format (HAR) logs to assist our investigation into the source of the issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 8:30 PM UTC
Time:Thu May 15 12:14:14 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: We're reviewing Unified Logging Service (ULS) logs and are analyzing errors occurring during requests to retrieve contents from the Files tab to better understand how impact is manifesting and assist our investigation into the source of the issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 6:30 PM UTC
Time:Thu May 15 10:19:29 2025
Description:Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 4:30 PM UTC

TM1080717 - Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings

Status:serviceDegradation
Start Time:Thu May 8 12:22:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu May 22 21:05:24 2025
Root Cause:A recent standard service update contains a code change that is resulting in impact.
Next Update:Friday, May 23, 2025, at 6:00 PM UTC

Details

Time:Thu May 22 20:29:27 2025
Description:Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings.
Current status: We've identified a recent standard service update which contains a code change that's resulting in impact to the broadcast feed for attendees in Managed Mode meetings. We're working to develop, test, and validate a code fix in an effort to alleviate impact.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may be unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
Root cause: A recent standard service update contains a code change that is resulting in impact.
Next update by: Friday, May 23, 2025, at 6:00 PM UTC

CP1079827 - Users may notice delays with Copilot usage reports in the Microsoft 365 admin center

Status:serviceDegradation
Start Time:Wed May 21 21:58:18 2025
End Time:N/A
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Thu May 22 21:02:50 2025
Root Cause:An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next Update:Friday, May 23, 2025, at 6:30 PM UTC

Details

Time:Thu May 22 19:16:21 2025
Description:Title: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: The backlogged usage report data has nearly completed processing and we now expect that all data will be back up to date by our next scheduled communication.
Scope of impact: This issue may potentially impact any user attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Estimated time to resolve: Based on our current estimates, we expect that the usage report data will be back up to date by our next scheduled communication.
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Friday, May 23, 2025, at 6:30 PM UTC
Time:Thu May 22 12:10:26 2025
Description:Title: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We've completed our work to restore the upstream data source, which will fix the delays so that Copilot usage report data is up to date. Based on our current estimates, we expect that the usage report data will be up to date by our next scheduled communication.
Scope of impact: This issue may potentially impact any user attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Estimated time to resolve: Based on our current estimates, we expect that the usage report data will be back up to date by our next scheduled communication.
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Friday, May 23, 2025, at 1:00 AM UTC
Time:Wed May 21 22:42:02 2025
Description:Title: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We identified an issue with an upstream data source that assists in generating Copilot usage reports that is causing delays with the report data. We're working to restore the upstream data source to fix the delays and bring the Copilot usage report data up to date.
Scope of impact: This issue may potentially impact any user attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Thursday, May 22, 2025, at 6:00 PM UTC
Time:Wed May 21 22:07:19 2025
Description:Title: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Users may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1080635 - Admins may be unable to edit or create security operations cases in the Microsoft Defender portal

Status:serviceRestored
Start Time:Thu May 22 04:30:00 2025
End Time:Thu May 22 19:30:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Thu May 22 20:52:33 2025
Root Cause:A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was operating in a suboptimal state and caused impact.
Next Update:N/A

Details

Time:Thu May 22 20:52:33 2025
Description:Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may have been unable to edit or create security operations cases in the Microsoft Defender portal.
Final status: After performing an extended period of monitoring the service health telemetry, we've confirmed that impact has been remediated for all users.
Scope of impact: Any user who attempted to connect to Exchange Online from the classic Outlook desktop client may have been impacted.
Start time: Thursday, May 22, 2025, at 8:30 AM UTC
End time: Thursday, May 22, 2025, at 11:30 PM UTC
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was operating in a suboptimal state and caused impact.
Next steps: - We're continuing to investigate why the portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was performing below expected thresholds to ensure issues like this aren't replicated in the future.
This is the final update for the event.
Time:Thu May 22 19:36:00 2025
Description:Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal.
More info: While we’re focused on remediation, users that have access to Outlook on the web or the Outlook mobile apps may use these to bypass the impact.
Current status: The service health telemetry indicates that impact has been remediated for most affected users; however, impact may still be present for a portion of affected users. Additionally, after restarting the system services of the affected infrastructure we’ve noticed that impact is gradually recovering. We’re continuing to monitor telemetry, as well as looking for possible ways to expedite our remediating actions if possible.
Scope of impact: Any user attempting to connect to Exchange Online from the classic Outlook desktop client may be impacted.
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client is operating in a suboptimal state and causing impact.
Next update by: Friday, May 23, 2025, at 1:30 AM UTC
Time:Thu May 22 18:51:21 2025
Description:Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal.
More info: While we’re focused on remediation, users that have access to Outlook on the web or the Outlook mobile apps may use these to bypass the impact.
Current status: Our service health telemetry suggests that the impact is remediated for some affected users; however, impact may still be present for a portion of affected users. We're restarting system services on the affected infrastructure to restore the service.
Scope of impact: Any user attempting to connect to Exchange Online from the classic Outlook desktop client may be impacted.
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client is operating in a suboptimal state and causing impact.
Next update by: Thursday, May 22, 2025, at 11:30 PM UTC
Time:Thu May 22 18:44:01 2025
Description:Title: Admins can't create new security operations cases in the Microsoft Defender portal
User impact: Admins can't create new security operations cases in the Microsoft Defender portal.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1076917 - Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard

Status:serviceRestored
Start Time:Wed May 7 18:30:00 2025
End Time:Thu May 22 13:30:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Thu May 22 20:16:54 2025
Root Cause:A recent service change contained a configuration issue, which led to impact.
Next Update:N/A

Details

Time:Thu May 22 20:14:56 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may have seen a delay in the data present on the Copilot dashboard.
More info: Users may have seen May 5th, 2025 as the last working date. In addition, users may also have experienced delays in data from the Microsoft 365 Copilot adoption report.
Final status: We've confirmed that the issue has been resolved following our fix to roll back the offending configuration change, and the subsequent processing of the backlogged data.
Scope of impact: Any users may have seen a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
End time: Thursday, May 22, 2025, at 5:30 PM UTC
Root cause: A recent service change contained a configuration issue, which led to impact.
Next steps: - We're continuing to assess our service change procedures so we can better identify similar configuration issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
Time:Wed May 21 19:44:42 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: While a majority of affected users should be experiencing relief at this time, we're continuing to monitor as the remaining backlog of data finishes processing. Additionally, we're assessing if there's a way we can expedite this to remediate the issue as quickly as possible for all remaining users.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Friday, May 23, 2025, at 1:30 AM UTC
Time:Tue May 20 20:08:03 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: Our monitoring of the backlog of data processing is ongoing. We've confirmed that 75 percent of data has been processed, and we'll continue to monitor this processing to ensure impact has been fully resolved.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Thursday, May 22, 2025, at 1:30 AM UTC
Time:Mon May 19 19:41:53 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We're continuing to monitor the backlog of data as we work to fully process it. We anticipate having a timeline for its completion by our next scheduled communications update.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Wednesday, May 21, 2025, at 1:00 AM UTC
Time:Mon May 19 00:57:10 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We've successfully deployed the fix to roll back the configuration change and we've confirmed that this has mitigated the issue. We've identified a backlog of data that will need to finish processing before impact is fully remediated.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Tuesday, May 20, 2025, at 1:00 AM UTC
Time:Sun May 18 19:28:16 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We've investigated our service telemetry, along with any recent changes made to the service, and we suspect that a recent configuration change may be causing impact. We've deployed a fix to roll back this configuration change to assess whether this remediates impact, while we continue investigating the issue to see if any further changes may be needed.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Next update by: Monday, May 19, 2025, at 6:00 AM UTC
Time:Sun May 18 19:14:57 2025
Description:Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1077602 - Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center

Status:serviceDegradation
Start Time:Fri May 16 21:00:00 2025
End Time:N/A
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Thu May 22 17:04:09 2025
Root Cause:A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next Update:Friday, May 23, 2025, at 4:00 PM UTC

Details

Time:Thu May 22 17:00:11 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: The fix deployment is still at around 97 percent saturation. While we expect that this issue is no longer occurring for most affected users, we’re continuing to monitor and assess whether any additional steps will be required to fully resolve this issue for all affected users.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Friday, May 23, 2025, at 4:00 PM UTC
Time:Thu May 22 15:07:54 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re monitoring the fix deployment, which has progressed to 97 percent complete, while simultaneously assessing if any additional steps are necessary to fully resolve this issue.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 9:00 PM UTC
Time:Wed May 21 21:37:32 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Our validation process of the fix is complete and its deployment has begun. We're monitoring our solution as it begins to saturate the environment and will provide an update on the resolution timeline as one becomes available to us.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 7:00 PM UTC
Time:Wed May 21 14:50:11 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re continuing to validate our fix and making the necessary adjustments to prioritize the fixed build to remediate the impact as soon as possible. We anticipate having an estimation for the implementation of our fix and impact resolution by our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 3:00 AM UTC
Time:Wed May 21 01:40:25 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're performing our final internal validations before deploying our fix throughout the affected infrastructure. We anticipate that the validation process will be completed by our next scheduled update, at which point we're aiming to provide a remediation timeline if possible.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 7:00 PM UTC
Time:Tue May 20 19:06:37 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re making progress with the testing and validation of the fix in our internal test environment. Once our validation efforts are complete, we'll aim to provide a resolution timeline.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 7:00 AM UTC
Time:Tue May 20 17:43:37 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re continuing to test and validating our fix in our internal test environment to ensure once fully deployed our fix will mitigate impact for all users. We aim to provide an update on our timeline to deployment at the time of our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 12:30 AM UTC
Time:Tue May 20 14:21:52 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Validation of the fix is nearing completion and we’re reviewing whether any additional steps to add some retry logic to the affected scenario may be necessary to fully resolve this issue.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 10:30 PM UTC
Time:Tue May 20 08:43:29 2025
Description:Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're continuing to validate our fix to ensure its efficacy prior to deploying it to the affected infrastructure. We expect to provide a deployment timeline by our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
Time:Tue May 20 02:23:49 2025
Description:Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've developed a fix for the issue and need to perform further validation before implementing the changes. We expect that validation will complete by the next scheduled update time.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 1:00 PM UTC
Time:Mon May 19 15:28:39 2025
Description:Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've confirmed that a recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact. We're developing a fix to revert this change and resolve the issue. We're aiming to complete the development process by our next scheduled communications update, at which time we'll initiate deployment of the fix to the impacted service environment.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 7:00 AM UTC
Time:Mon May 19 14:18:40 2025
Description:Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Our investigation has identified a recent update to the authentication pathways responsible for facilitating access to the HVE service that may be contributing to impact. We're evaluating methods to revert this update to confirm our theory and potentially repair the issue, after which we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Next update by: Monday, May 19, 2025, at 7:30 PM UTC
Time:Mon May 19 13:38:04 2025
Description:Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're investigating a potential issue with the Exchange Online service and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1074773 - Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app

Status:serviceDegradation
Start Time:Thu May 15 13:52:54 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu May 22 14:42:56 2025
Root Cause:A recent app update contains a code regression, resulting in impact.
Next Update:Friday, May 23, 2025, at 7:00 PM UTC

Details

Time:Thu May 22 14:42:56 2025
Description:Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: The fix validation is taking longer than expected and we'll provide a deployment timeline once one is available.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Friday, May 23, 2025, at 7:00 PM UTC
Time:Thu May 15 13:59:28 2025
Description:Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: Our monitoring has identified an increase in delays or intermittent failures of the Walkie Talkie feature in the Microsoft Teams mobile apps. We've analyzed recent app updates and determined that a recent update contains a code regression, resulting in impact. We've developed a fix and are in the process of validating it before release. We expect to have a deployment timeline by the next scheduled update.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Thursday, May 22, 2025, at 8:00 PM UTC
Time:Thu May 15 13:54:51 2025
Description:Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: We're investigating a potential issue with Microsoft Teams Walkie Talkie and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1079868 - Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel

Status:serviceRestored
Start Time:Mon May 19 02:00:00 2025
End Time:Thu May 22 01:53:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Thu May 22 02:09:01 2025
Root Cause:A recent service deployment contained a code issue that was preventing the pairing functionality from working as expected.
Next Update:N/A

Details

Time:Thu May 22 02:08:06 2025
Description:Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may have been unable to connect or pair MTRA devices using the Teams touch panel.
More info: Users saw the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices was preventing users' ability to join meetings or take calls.
Final status: We've completed reverting the offending deployment and confirmed with several users who initially reported the issue that the impact is remediated. Additionally, if you have a device that's still impacted, you may need to perform a manual restart to experience remediation.
Scope of impact: Some users that attempted to connect, maintain connections, or pair MTRA devices were impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
End time: Thursday, May 22, 2025, at 5:53 AM UTC
Root cause: A recent service deployment contained a code issue that was preventing the pairing functionality from working as expected.
Next steps: - We're further reviewing the recent service deployment to understand how the code issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
Time:Thu May 22 00:50:49 2025
Description:Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may be unable to connect or maintain connections or pair MTRA devices using the Teams touch panel.
More info: Users see the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We're continuing to monitor the progress of reverting the offending deployment. Additionally, we're seeing significant improvement with error counts decreasing, and anticipate the majority of impacted users are already experiencing remediation. The remaining impacted users will experience remediation incrementally while the reversion progresses, which we anticipate will be complete and the issue will be fully resolved by our next scheduled communications update.
Scope of impact: Some users attempting to connect or maintain connections or pair MTRA devices are impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
Root cause: A recent service deployment contains a code issue that's preventing the pairing functionality from working as expected.
Next update by: Thursday, May 22, 2025, at 7:00 AM UTC
Time:Wed May 21 23:52:43 2025
Description:Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may be unable to connect or maintain connections or pair MTRA devices using the Teams touch panel.
More info: Users see the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We've received reports of an issue in which some users may be unable to pair MTRA devices and see that the touch panel is disconnecting. Our investigation determined that a recent service deployment contains a code issue that's preventing the pairing functionality from working as expected. We're reverting the recent deployment in order to remediate impact and restore service functionality.
Scope of impact: Some users attempting to connect or maintain connections or pair MTRA devices are impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
Root cause: A recent service deployment contains a code issue that's preventing the pairing functionality from working as expected.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
Time:Wed May 21 23:43:34 2025
Description:Title: Some users may be unable to pair Microsoft Teams Room for Android (MTRA) devices and the touch panel is disconnecting
User impact: Users may be unable to pair MTRA devices and the touch panel is disconnecting.
More info: Being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We're investigating a potential issue with MTRA devices and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1030180 - Users may see a new "Content Freshness" template option when creating pages in SharePoint Online

Status:serviceDegradation
Start Time:Wed Jan 15 19:00:00 2025
End Time:N/A
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Wed May 21 23:15:44 2025
Root Cause:A recent deployment incorrectly enabled this feature in the affected environment.
Next Update:Thursday, June 5, 2025, at 5:00 AM UTC

Details

Time:Wed May 21 23:15:44 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've encountered an issue with our long-term fix during our internal testing and validation process. We're working to debug the issue to prepare the fix for deployment and anticipate this may push back our timeline for remediation by four to five weeks, meaning users may not see our changes in effect until late July 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 5, 2025, at 5:00 AM UTC
Time:Wed May 7 23:24:45 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've begun the initial validation and internal testing of the aforementioned long-term fix, and this process remains on track to complete by our previously communicated mid-June 2025 estimation.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
Time:Wed Apr 23 23:00:43 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're focusing our efforts on developing and deploying a long-term fix to remove the incorrect inclusion of the "Content Freshness" template option, which remains on track to be completed by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 8, 2025, at 5:00 AM UTC
Time:Wed Apr 9 23:18:32 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've identified an issue with our previously developed near-term fix to remove the template option and determined its deployment needs to be suspended. While we continue to assess our options for potential expedited solutions, we're working on a long-term fix that we're projecting may be released by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
Time:Wed Mar 26 21:38:32 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 10, 2025, at 5:00 AM UTC
Time:Wed Mar 12 23:48:34 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC

IT1079222 - Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service

Status:serviceRestored
Start Time:Tue May 20 10:57:00 2025
End Time:Wed May 21 20:42:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Wed May 21 21:27:02 2025
Root Cause:A recent update to the Android platform contained a change to the device compliance calculation, which caused Android devices with strong integrity enabled to become non-compliant and resulted in impact.
Next Update:N/A

Details

Time:Wed May 21 21:27:02 2025
Description:Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, which prevented access to any Microsoft mobile service.
More info: This may have impacted any Microsoft mobile service protected by App Protection Policies.
Admins could have disabled strong integrity and removed the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Final status: We've completed the deployment of our code change fix to all impacted portions of infrastructure and confirmed through our telemetry that impact has been resolved.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may have been impacted.
Start time: Tuesday, May 20, 2025, at 2:57 PM UTC
End time: Thursday, May 22, 2025, at 12:42 AM UTC
Root cause: A recent update to the Android platform contained a change to the device compliance calculation, which caused Android devices with strong integrity enabled to become non-compliant and resulted in impact.
Next steps: - We're reviewing the impacted service infrastructure to understand what changes can be made to detect issues sooner and prevent similar impact in the future.
This is the final update for the event.
Time:Wed May 21 18:17:07 2025
Description:Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: We're continuing to deploy our code change to correct the compliance calculation compatibility issue and completely remediate impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform contains a change to the device compliance calculation, which is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Thursday, May 22, 2025, at 2:00 AM UTC
Time:Wed May 21 16:31:31 2025
Description:Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: We've determined that the fix that was deployed by our third-party partner corrected a code issue in a recently deployed Android platform update. While this fix corrected the issue for some, the Android platform update also introduced a change to the compliance calculations that isn’t compatible with Microsoft Intune, leaving some users impacted. We've created and are deploying a code change to correct the compliance calculation compatibility issue to completely remediate impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform contains a change to the device compliance calculation, which is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 11:30 PM UTC
Time:Wed May 21 14:03:30 2025
Description:Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: Our third-party partner created and deployed a fix that's expected to address the offending Android platform update, and we expect this will remediate impact. We're monitoring the affected environment to confirm if impact is remediated or if additional action is needed on our end to resolve the issue.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 9:00 PM UTC
Time:Wed May 21 11:44:50 2025
Description:Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: Admins can disable strong integrity to prevent their devices from being marked as non-compliant.
Current status: We've identified that a recent update to the Android platform may be causing Android devices with strong integrity enabled to become non-compliant, resulting in impact. Based on our improved understanding of what's causing this issue, we've clarified how this event may impact users within the Title, User impact, and Scope of impact fields of our communication. In order to address this impact, we're working with a third-party partner to create a fix that remediates impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 6:00 PM UTC
Time:Wed May 21 09:48:16 2025
Description:Title: Users are unable to access company resources due to non-compliance devices within Microsoft Intune
User impact: Users are unable to access company resources due to non-compliance devices within Microsoft Intune.
More Info: This impacts Android (personally-owned work profile) devices only.
As a workaround users may disable require "strong integrity".
Current status: We're reviewing recent changes made to the service that may be contributing to help locate the source of impact.
Scope of impact: Impact is specific to some users who are unable to access company resources due to non-compliance devices within Microsoft Intune.
Next update by: Wednesday, May 21, 2025 at 4:00 PM UTC
Time:Wed May 21 07:48:32 2025
Description:Title: Users are unable to access company resources due to non-compliance devices within Microsoft Intune
User impact: Users are unable to access company resources due to non-compliance devices within Microsoft Intune.
More Info: This impacts Android (personally-owned work profile) devices only.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event and impacts users attempting to access company resources due to non-compliance devices within Microsoft Intune.
Next update by: Wednesday, May 21, 2025 at 2:00 PM UTC

TM1050098 - Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac

Status:serviceDegradation
Start Time:Wed Apr 2 21:37:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed May 21 21:26:53 2025
Root Cause:As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next Update:Wednesday, May 28, 2025, at 3:00 AM UTC

Details

Time:Wed May 21 21:26:53 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've identified the saturation of the fix is currently approximately 50 percent complete. We anticipate the remaining saturation will complete and the impact will be remediated by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Wednesday, May 28, 2025, at 3:00 AM UTC
Time:Thu May 15 21:26:28 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've initialized the final stage of our deployment to re-enable video filtering features for the affected service environment. We're anticipating this process will complete by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Estimated time to resolve: We're anticipating the affected video filtering features will be fully re-enabled by Thursday, May 22, 2025, at 3:00 AM UTC.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Thursday, May 22, 2025, at 3:00 AM UTC
Time:Tue May 13 14:43:28 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: One deployment to re-enable the avatar feature for Microsoft Teams for Mac users has completed. Our deployment to re-enable video filtering has experienced a block that is delaying our full remediation of impact. We're addressing the block so our deployment can resume and expect an updated timeline for its re-enablement to be available by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, May 16, 2025, at 3:00 AM UTC
Time:Fri May 9 16:13:03 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’re continuing to monitor the re-enablement of the affected features. Deployment of the avatar-related portion has reached approximately 50 percent and remains on track to complete by Tuesday, May 13, 2025. The video filter portion is still in early stages of rollout and has not yet reached broader availability. We’ll provide further updates as timelines are confirmed.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, May 13, 2025, at 8:00 PM UTC
Time:Tue May 6 13:50:21 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’ve initiated the re-enablement process for the features and are monitoring the deployment as it progresses to ensure successful completion. Based on current estimates, we expect it to complete by Tuesday, May 13, 2025.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Estimated time to resolve: We estimate that the process to re-enable the features will be complete by Tuesday, May 13, 2025.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, May 9, 2025, at 8:30 PM UTC
Time:Mon Apr 28 14:10:12 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've confirmed the deployment of the fix is complete, and our testing of the re-enablement of the avatar and video filtering features is ongoing. We expect to begin re-enabling the features early next week.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, May 6, 2025, at 7:00 PM UTC
Time:Fri Apr 25 14:20:00 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We're continuing to monitor the deployment of the fix. In parallel, we're beginning the initial testing phases to evaluate the re-enablement of the avatar and video filtering features.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Monday, April 28, 2025, at 7:00 PM UTC
Time:Tue Apr 22 15:54:01 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: While the deployment of our fix is underway, both the avatar and video filtering features will need to be re-enabled following our fix's saturation. We're working to identify a remediation timeline, and we're in the initial stages of evaluating the re-enablement of these features within our testing environment.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 25, 2025, at 7:00 PM UTC
Time:Mon Apr 21 14:41:07 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’re continuing to assess our fix deployment strategy to safely and efficiently deploy the fix as soon as possible.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, April 22, 2025, at 8:00 PM UTC
Time:Fri Apr 18 14:46:49 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: Our final preparations to initiate the deployment of the fix are taking more time than expected. These preparations are critical to ensuring that our fix completely resolved the issue without introducing further problems.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Monday, April 21, 2025, at 7:00 PM UTC
Time:Thu Apr 17 19:34:26 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We're in the final stages of preparing to initiate the deployment of the fix, which we anticipate will start by our next scheduled update. Once the deployment has started, we'll aim to provide a resolution timeline.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 18, 2025, at 8:00 PM UTC
Time:Wed Apr 16 19:42:42 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: Our code fix has completed the development and validation phase and we're solidifying the final steps before deployment. Once deployment has begun and an timeline has been determined, we'll provide an update for full saturation.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 18, 2025, at 1:00 AM UTC
Time:Mon Apr 14 18:32:16 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've completed development and validation of the previously mentioned code fix, and we're preparing to initiate deployment to the impacted service environments. Once deployment begins, we'll provide a timeline for full saturation and remediation.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Thursday, April 17, 2025, at 1:00 AM UTC
Time:Mon Apr 7 15:50:20 2025
Description:Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users. We're developing a code fix which we intend to include in our next build update to permanently resolve the crashing issue. Once this code fix has deployed, we'll re-enable the avatar and video filtering features. We expect to have a timeline for the completion of fix development and the initiation of the fix deployment with our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, April 15, 2025, at 1:00 AM UTC

SP1074702 - Users may not receive any results for video analytics within Microsoft Stream on SharePoint

Status:serviceRestored
Start Time:Wed May 7 08:00:00 2025
End Time:Tue May 20 22:30:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Wed May 21 15:55:25 2025
Root Cause:A recent service update contained a code regression missing certain properties used to generate analytics, which resulted in impact.
Next Update:N/A

Details

Time:Wed May 21 00:45:01 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not have received any results for video analytics within Microsoft Stream on SharePoint.
Final status: We've confirmed through our service health telemetry that users have access to current video analytics results following the deployment of our fix.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may have been impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
End time: Tuesday, May 20, 2025, at 2:30 AM UTC
Root cause: A recent service update contained a code regression missing certain properties used to generate analytics, which resulted in impact.
Next steps: - We're reviewing our update testing and validation methods to better identify code regressions such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
Time:Tue May 20 13:47:11 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've completed the deployment of our fix to the affected environment, and we’re monitoring service health telemetry to ensure errors associated with impact cease as expected, confirming impact remediation.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 5:30 AM UTC
Time:Mon May 19 14:54:28 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've completed the deployment of our fix to a subset of infrastructure, where we’re in the process of performing internal validation to confirm that it fully remediates the issue as expected. In parallel, we’re monitoring as our fix’s deployment continues to saturate the affected environment.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Tuesday, May 20, 2025, at 7:00 PM UTC
Time:Fri May 16 13:58:17 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: Further analysis of recent service updates has identified a regression, which is missing certain properties used to generate analytics, resulting in impact. We've developed and validated a fix and are monitoring as it progresses. We'll provide a remediation timeline once one is available.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Monday, May 19, 2025, at 7:00 PM UTC
Time:Thu May 15 12:48:54 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've been unable to correlate impact to the suspected service update. We're reviewing service logs to identify the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Next update by: Friday, May 16, 2025, at 7:00 PM UTC
Time:Thu May 15 12:12:53 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've identified a code regression contained within a recent service update that we suspect is causing the impact. We're further reviewing the suspected service update to validate our hypothesis so we can determine our next steps.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Next update by: Thursday, May 15, 2025, at 6:30 PM UTC
Time:Thu May 15 12:00:20 2025
Description:Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We're investigating a potential issue with users not receiving results for video analytics within Microsoft Stream on SharePoint, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1079392 - Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint

Status:serviceRestored
Start Time:Wed May 21 00:00:00 2025
End Time:Wed May 21 10:43:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Wed May 21 13:05:18 2025
Root Cause:A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact.
Next Update:N/A

Details

Time:Wed May 21 13:05:18 2025
Description:Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may have received stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
Final status: We've monitored service health telemetry and confirmed that routing requests to healthy service infrastructure has remediated the impact.
Scope of impact: Any admin hosted in the West Europe region attempting to fetch vulnerabilities through APIs within Microsoft Defender for Endpoint may have been impacted.
Start time: Wednesday, May 21, 2025, at 4:00 AM UTC
End time: Wednesday, May 21, 2025, at 2:48 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact.
Next steps: - We’re analyzing performance data associated with the impacted service infrastructure so that we can better understand why it was performing below acceptable performance thresholds and prevent the impact from happening again.
This is the final update for the event.
Time:Wed May 21 11:20:17 2025
Description:Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
More info: While we work to resolve this issue, affected admins can fetch vulnerabilities within the Microsoft Defender for Endpoint admin portal as expected.
Current status: We've identified that a portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Threat Vulnerability Management flows is performing below acceptable service thresholds, resulting in impact. We've routed service requests to a portion of healthy service infrastructure, and we're monitoring service health telemetry to confirm if the issue is resolved.
Scope of impact: Any admin hosted in the West Europe region attempting to fetch vulnerabilities through APIs within Microsoft Defender for Endpoint may be impacted.
Start time: Wednesday, May 21, 2025, at 4:00 AM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows is performing below acceptable performance thresholds, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 5:30 PM UTC
Time:Wed May 21 11:04:03 2025
Description:Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
Current status: We're investigating a potential issue with admins receiving stale data when fetching vulnerabilities through any vulnerability related Application Programming Interface (API) within Microsoft Defender for Endpoint, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

SP1072852 - Users may not receive search results for REST API "/postquery" calls in SharePoint Online

Status:postIncidentReviewPublished
Start Time:Tue May 13 11:17:41 2025
End Time:Tue May 13 21:20:22 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Wed May 21 11:08:57 2025
Root Cause:A recent change, intended to create and use a new data code path for authentication tokens for SharePoint Online search requests, was deployed. The new code path did not work as expected in certain scenarios, resulting in incomplete or unsuccessful search result queries.
Next Update:N/A

Details

Time:Wed May 21 11:08:57 2025
Description:A post-incident report has been published.
Time:Tue May 20 19:23:52 2025
Description:A post-incident report has been published.
Time:Fri May 16 07:17:48 2025
Description:A post-incident report has been published.
Time:Tue May 13 21:21:05 2025
Description:Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may have not received search results for REST API "/postquery" calls in SharePoint Online.
More info: Some users may have received partial or incomplete results.
Final status: We isolated the cause of impact following our systemic examination into our SharePoint infrastructure. A recent change to a portion of search code path that processes authentication tokens became degraded and resulted in incomplete or unsuccessful search result queries. We’ve disabled the offending change and after a period of monitoring and user confirmations, we’ve determined the functionality has been restored successfully.
Scope of impact: This issue may have affected any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs if served through the affected infrastructure.
Start time: Tuesday, May 13, 2025, at 3:00 PM UTC
End time: Wednesday, May 14, 2025, at 12:30 AM UTC
Root cause: A recent change, intended to create and use a new data code path for authentication tokens for SharePoint Online search requests, was deployed. The new code path did not work as expected in certain scenarios, resulting in incomplete or unsuccessful search result queries.
SharePoint Online search gathers search results from background Store databases by opening a session with an internal service. When retrieving organization level search results, the type of session that needs to be opened with the internal service should be “System”. The recent change inadvertently changed the session type from “System” to “Best Access”, resulting in no search results being returned from the internal service, because the session type of “Best Access” is not configured to support the retrieval of organizational level data.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
A Post Incident Report (PIR) has been published for this event.
Time:Tue May 13 19:32:11 2025
Description:Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We've investigated several recent code updates, but no direct correlation was identified as the root cause. We're systematically examining an expanded set of additional code changes made to the service in an effort to identify the cause of impact, which we currently believe may be due to issues within the search code path. We'll continue to open any additional workstreams as necessary to expedite remediation and restore functionality.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Wednesday, May 14, 2025, at 1:30 AM UTC
Time:Tue May 13 17:29:41 2025
Description:Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We're continuing to investigate working and non-working scenarios to better understand the issue. Additionally, we've reproduced the issue, collected logs, and we're analyzing the search code path to identify potential causes of impact.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 11:30 PM UTC
Time:Tue May 13 15:29:53 2025
Description:Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We're currently investigating recent updates to identify any that may be contributing to impact. Additionally, we're working to collect correlation IDs from both a working and non-working scenario to better assist in our understanding of the issue.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 9:30 PM UTC
Time:Tue May 13 13:24:23 2025
Description:Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: From our review of available data, we've confirmed that this problem is specifically impacting REST API "/postquery" calls, which prevents users from receiving search results on SharePoint Online classic sites, SharePoint Framework and PnP PowerShell module search result web parts, and other custom search user interfaces (UIs). We've collected a correlation ID from a network trace and are reviewing search logs to identify the reason for the failure within our service.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 7:30 PM UTC
Time:Tue May 13 12:14:46 2025
Description:Title: Users may not receive search results in SharePoint Online
User impact: Users may not receive search results in SharePoint Online.
Current status: We're reviewing network traces captured while the problem is occurring and our internal service telemetry for this impact to determine what's causing the impact.
Scope of impact: This issue may affect any user performing searches in SharePoint Online.
Next update by: Tuesday, May 13, 2025, at 5:30 PM UTC
Time:Tue May 13 11:17:42 2025
Description:Title: Possible delays or problems when accessing SharePoint Online
User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

EX1072592 - Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox

Status:postIncidentReviewPublished
Start Time:Sun May 11 10:04:00 2025
End Time:Fri May 16 00:32:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Tue May 20 20:21:43 2025
Root Cause:A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next Update:N/A

Details

Time:Tue May 20 20:20:23 2025
Description:A post-incident report has been published.
Time:Fri May 16 17:14:32 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Final Status: We’ve concluded our testing effort and have determined that our fix is a viable solution for this issue. Representatives of organizations that would like us to re-forward any messages affected by this event are encouraged to contact Microsoft support and refer to this Service Health Dashboard post ID.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages users attempted to forward between 2:04 PM UTC on May 11, 2025, and 5:00 AM UTC May 16, 2025, will not be replayed automatically.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
End time: Friday, May 16, 2025, at 4:32 AM UTC
Preliminary Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that prevented some users from utilizing Exchange Online automatic forwarding.
We’ll produce a post-incident report within five business days.
Time:Fri May 16 11:53:03 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages received between 2:04 PM UTC on May 11, 2025 and 5:00 AM UTC May 16, 2025 may not be available until the conclusion of this event.
Current status: We're continuing our targeted recovery of affected messages within the impact timeframe. We've developed a fix to resubmit the affected messages and we're conducting testing to ensure this method produces the expected resolution. Once we've concluded this period of testing, and we're certain this method produces the expected resolution, we will apply this fix broadly to the remaining affected messages.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 9:00 PM UTC
Time:Fri May 16 03:57:08 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages received between 2:04 PM UTC on May 11, 2025 and 5:00 AM UTC May 16, 2025 may not be available until the conclusion of this event.
Current status: We've completed deploying our code fix to address the code regression which has resolved the issue for new messages. We’re starting a targeted recovery of messages within the impact timeframe and are working on a solution for a scalable rollout.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 5:00 PM UTC
Time:Thu May 15 23:50:05 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our code fix deployment for the regression is 99 percent complete. We anticipate this deployment may be complete by our next scheduled update. This will resolve the issue for any new messages; however, we’re still working to recover the messages that were sent during the impact timeframe.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 9:30 AM UTC
Time:Wed May 14 19:07:56 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: The deployment of our code fix to address the impacting code regression has begun its deployment. We're overseeing the progress to ensure it completes as expected. We'll provide a timeline to resolution as one becomes available.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 4:00 AM UTC
Time:Wed May 14 14:48:39 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our fix to address the isolated code regression has completed internal validations, and we're deploying the solution to the affected environment. We're expecting that an estimated timeline for the fix deployment and the remediation of impact will be available once the deployment has begun, and by our next scheduled update.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Thursday, May 15, 2025, at 12:00 AM UTC
Time:Tue May 13 16:14:15 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our network routing analysis has isolated an impacting code regression that is believed to be preventing users from utilizing automatic forwarding in Exchange Online. After halting the offending service deployment that introduced the regression to ensure additional users didn't run into the problem, we're developing a fix to address the code regression and to remediate the impact. We're expecting that a timeline for our fix deployment and the remediation of impact will be available by our next scheduled update.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Wednesday, May 14, 2025, at 10:00 PM UTC
Time:Tue May 13 11:46:39 2025
Description:Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: While our affected mailbox analysis progresses, we're further analyzing the network routing for automatic forwarding in Exchange Online as we isolate the source for this event so we can determine our next troubleshooting steps for remediating the impact.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 9:00 PM UTC
Time:Tue May 13 07:47:42 2025
Description:Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our investigation into the affected mailboxes is progressing as we work to identify the root cause of the issue. This will assist us in determining the appropriate troubleshooting steps to develop a mitigation plan.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 5:00 PM UTC
Time:Tue May 13 04:25:23 2025
Description:Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: We're continuing our review of the affected user mailboxes to identify the source of the issue, which will help us determine our next troubleshooting steps to reach a mitigation plan.
Scope of impact: Your organization is affected by this event, and the issue impacts some users utilizing automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 1:00 PM UTC
Time:Tue May 13 02:50:09 2025
Description:Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: We're reviewing the affected user mailboxes to identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue impacts some users utilizing automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 9:00 AM UTC
Time:Tue May 13 02:29:54 2025
Description:Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1077450 - Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams

Status:serviceRestored
Start Time:Sun May 18 06:00:00 2025
End Time:Mon May 19 14:00:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Tue May 20 13:59:15 2025
Root Cause:A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which was resulting in impact.
Next Update:N/A

Details

Time:Tue May 20 12:11:42 2025
Description:Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may have encountered delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may have encountered delays of up to 24 hours from the first time a person was contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
Final status: We've successfully deployed the fix to correct the misconfiguration, which has resolved the issue.
Scope of impact: Impact was specific to some users who contacted a person for the first time up to 24 hours prior.
Start time: Friday, April 18, 2025, at 10:00 AM UTC
End time: Monday, May 19, 2025, at 6:00 PM UTC
Root cause: A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which was resulting in impact.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Mon May 19 11:29:57 2025
Description:Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may encounter delays of up to 24 hours from the first time a person has been contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
Current status: We determined a change meant to improve the suggested people index generation efficiency introduced a misconfiguration which is resulting in impact. We're deploying a fix to correct this misconfiguration to resolve the issue.
Scope of impact: Impact is specific to some users who contacted a person for the first time up to 24 hours prior.
Start time: Friday, April 18, 2025, at 10:00 AM UTC
Root cause: A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which is resulting in impact.
Next update by: Tuesday, May 20, 2025, at 4:00 PM UTC
Time:Mon May 19 10:41:54 2025
Description:Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may encounter delays of up to 24 hours from the first time a person has been contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, May 19, 2025, at 5:00 PM UTC

EX1077227 - Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online

Status:serviceRestored
Start Time:Fri May 16 03:00:00 2025
End Time:Tue May 20 00:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Tue May 20 12:56:16 2025
Root Cause:A recent configuration change contained a regression that was preventing EMT reports from exporting content. As a result, EMT reports got stuck in an “InProgress” state and queued for completion within Exchange Online.
Next Update:N/A

Details

Time:Tue May 20 12:56:16 2025
Description:Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may have been stuck in an ''InProgress'' state in Exchange Online.
More info: The problem occurred in the Exchange admin center and when using PowerShell. As a workaround, some admins may have been able to utilize messageTraceV2, for message tracking-related data for the last 30 days.
As we worked to remediate the impact, affected admins could have worked around this problem by resubmitting reports.
Final status: Following our fix implementation and the processing of a backlogged group of EMT reports, our internal service telemetry has validated that impact has been remediated.
Scope of impact: The problem impacted admins running EMT reports from the Exchange admin center and PowerShell.
Start time: Friday, May 16, 2025, at 7:00 AM UTC
End time: Tuesday, May 20, 2025, at 4:00 AM UTC
Root cause: A recent configuration change contained a regression that was preventing EMT reports from exporting content. As a result, EMT reports got stuck in an “InProgress” state and queued for completion within Exchange Online.
Next steps: - We're further analyzing the isolated configuration change and the code regression it introduced, to help us improve our pre-deployment testing and validation processes in our efforts to prevent similar issues in the future.
This is the final update for the event.
Time:Mon May 19 17:57:51 2025
Description:Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: The problem occurs in the Exchange admin center and when using PowerShell. As a workaround, some admins may be able to utilize messageTraceV2, for message tracking-related data for the last 30 days.
Current status: We've developed and implemented a fix that corrected the configuration change and we expect has remediated impact. We're monitoring as the backlog of EMT reports are delivered to confirm impact is completely remediated.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Root cause: A recent configuration change contains a regression that’s preventing EMT reports from exporting content. As a result, EMT reports get stuck in an “InProgress” state and queue for completion within Exchange Online.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
Time:Mon May 19 08:48:25 2025
Description:Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: As a workaround, some admins may be able to utilize messageTraceV2, for message tracking related data for the last 30 days.
Current status: We've determined that a recent configuration change inadvertently contains a regression, which is resulting in impact. We're developing a fix in order to remediate impact.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Root cause: A recent configuration change inadvertently contains a regression, which is resulting in impact.
Next update by: Monday, May 19, 2025, at 11:00 PM UTC
Time:Mon May 19 05:24:34 2025
Description:Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: As a workaround, some admins may be able to utilize messageTraceV2, for message tracking related data for the last 30 days.
Current status: We're reviewing support provided information and service monitoring telemetry, to isolate the source of the issue and establish a fix.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Next update by: Monday, May 19, 2025, at 1:00 PM UTC
Time:Mon May 19 04:40:39 2025
Description:Title: Some admins' Extended Message Trace (EMT) reports are stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports are stuck in an ''InProgress'' state in Exchange Online.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Next update by: Monday, May 19, 2025, at 11:00 AM UTC

CR1065792 - Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor

Status:serviceRestored
Start Time:Thu Mar 20 20:00:00 2025
End Time:Mon May 19 17:00:00 2025
Service:Dynamics 365 Apps
Feature Group:Other
Classification:advisory
Last Updated:Mon May 19 19:25:28 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Mon May 19 19:25:28 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users experienced latency when replying to emails or when loading emails in the modern rich text editor.
Final Status: We have completed deployment of the fix and reviewed diagnostic analysis to confirm delays are no longer occurring.
This is the final update on the incident.
Preliminary Root Cause: A recent service update contained a code regression that impacted the modern rich text editor in Dynamics 365.
Next Steps: We're reviewing our deployment configuration procedures to find ways to prevent this problem from happening again.
Time:Mon May 12 19:23:49 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Some users may observe recovery as the hotfix progresses.
Current Status: Deployment of the hotfix is ongoing.
Next Update: Tuesday, May 20, 2025, at 1:00 AM UTC
Time:Mon May 5 19:17:01 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Current Status: Deployment of the hotfix is currently in progress.
Next Update: Tuesday, May 13, 2025, at 1:00 AM UTC
Time:Fri May 2 14:24:23 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Current Status: We have completed the development of the hotfix. Following our completion of validation testing, we will initiate the deployment of the hotfix to the portion of service infrastructure affected by the regression.
Next Update: Tuesday, May 6, 2025, at 1:00 AM UTC
Time:Wed Apr 30 19:59:06 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue is only occurring when the email is over 5 MB.
Current Status: Following our investigation, we identified that a recent service update contained a code regression that impacted the modern rich text editor in Dynamics 365. We are developing a hotfix to address the code regression and will perform validations prior to deploying it.
Next Update: Friday, May 2, 2025, at 8:00 PM UTC
Time:Wed Apr 30 19:39:02 2025
Description:Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue is only occurring when the email is over 5 MB.
Current Status: We are aware of an emerging issue where users are experiencing latency when replying to emails or when loading emails in the modern rich text editor. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

TM1074709 - Users may be unable to load some shared channel messages in Microsoft Teams

Status:serviceDegradation
Start Time:Thu May 15 12:19:46 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon May 19 16:54:39 2025
Root Cause:A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next Update:Friday, May 23, 2025, at 10:00 PM UTC

Details

Time:Mon May 19 16:54:39 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've scheduled our fix for deployment, and our current deployment timeline expects that it’ll finish and remediate the impact by our next scheduled update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Friday, May 23, 2025, at 10:00 PM UTC
Time:Fri May 16 17:16:36 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've completed the deployment of our fix to a subset of affected users and have confirmed it successfully resolves the issue. We're preparing to deploy the fix to the broader impacted environment and anticipate a timeline for the deployment will be available with our next scheduled update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Monday, May 19, 2025, at 10:00 PM UTC
Time:Thu May 15 14:37:51 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've initiated the expedited fix to a subset of affected users to confirm efficacy and expect it will complete by our next update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Friday, May 16, 2025, at 10:00 PM UTC
Time:Thu May 15 13:23:03 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We're in the process of developing an expedited fix to remediate impact for a subset of affected users that, if successful, should remediate impact prior to the original fix's timeline. Once validated, we'll proceed with broad deployment to all affected users to restore service.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Thursday, May 15, 2025, at 7:30 PM UTC
Time:Thu May 15 12:45:37 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've determined this event is related to a recent update that introduced a code regression which prevents valid user information from being retrieved, causing the shared channel pane to crash and resulting in impact. A fix to address the issue is currently deploying to a subset of affected users to confirm it resolves the issue as expected before deploying more broadly.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user information from being retrieved, causing the shared channel pane to crash and resulting in impact.
Next update by: Thursday, May 15, 2025, at 5:30 PM UTC
Time:Thu May 15 12:22:35 2025
Description:Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1077243 - Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel

Status:serviceRestored
Start Time:Mon May 19 03:30:00 2025
End Time:Mon May 19 07:00:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Mon May 19 10:03:15 2025
Root Cause:A section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays.
Next Update:N/A

Details

Time:Mon May 19 09:55:50 2025
Description:Title: Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel
User impact: Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel.
Final status: We've identified that a section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays. We've optimized the affected infrastructure, cleared a backlog of telemetry alerts and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, May 19, 2025, at 7:30 AM UTC
End time: Monday, May 19, 2025, at 11:00 AM UTC
Root cause: A section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays.
Next steps: - We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again.
This is the final update for the event.
Time:Mon May 19 05:04:34 2025
Description:Title: Admins may receive delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel
User impact: Admins may receive delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel.
Current status: We're reviewing service monitoring telemetry and system logs to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe.
Next update by: Monday, May 19, 2025, at 2:30 PM UTC

DZ1076377 - Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed

Status:serviceRestored
Start Time:Sat May 17 11:15:00 2025
End Time:Sun May 18 22:25:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Mon May 19 02:13:09 2025
Root Cause:A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts wasn't performing efficiently, which resulted in impact.
Next Update:N/A

Details

Time:Mon May 19 02:13:09 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may have been delayed.
More info: Admins may have received delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Final status: We've confirmed that the redirecting of telemetry traffic has completed and impact has been fully remediated.
Scope of impact: Impact may have occurred for any admin who attempted to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
End time: Monday, May 19, 2025, at 2:25 AM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts wasn't performing efficiently, which resulted in impact.
Next steps: - We're investigating the affected service infrastructure further to better understand what caused the sub-optimal performance and what changes can be made to prevent similar issues in the future.
This is the final update for the event.
Time:Sun May 18 07:49:49 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We’re continuing to oversee the redirecting of telemetry traffic to ensure full remediation.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Monday, May 19, 2025, at 12:00 PM UTC
Time:Sun May 18 02:32:22 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've completed our remediation efforts in the North America region and validated the impact is now alleviated for users in that region. Our process to oversee the redirecting of telemetry traffic is continuing in the remaining affected regions to ensure broad recovery.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Sunday, May 18, 2025, at 12:00 PM UTC
Time:Sat May 17 16:39:52 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. However, this process is taking longer than anticipated. We're continuing to monitor the telemetry redirection and will provide an updated resolution timeline once available.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Sunday, May 18, 2025, at 8:00 PM UTC
Time:Sat May 17 15:11:39 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. We're continuing to monitor the telemetry redirection and suspect the issue may be resolved by the next scheduled update.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 9:30 PM UTC
Time:Sat May 17 13:14:46 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. We're monitoring the process to ensure it leads to successful remediation.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 7:30 PM UTC
Time:Sat May 17 12:21:28 2025
Description:Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: Our monitoring system has identified that admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel may be delayed by up to 30 minutes. We've identified a portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently. We're analyzing system logs to identify a mitigation plan.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 5:30 PM UTC

MO1076013 - Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal

Status:serviceRestored
Start Time:Fri May 16 18:27:00 2025
End Time:Sat May 17 01:10:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Sat May 17 01:25:38 2025
Root Cause:The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that prevented authentication attempts from succeeding, leading to impact.
Next Update:N/A

Details

Time:Sat May 17 01:25:25 2025
Description:Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may have also impacted telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Final status: We monitored the environment after updating the responsible authentication component for the Microsoft Defender for Endpoint infrastructure to validate that the impact was remediated.
Scope of impact: This issue may have potentially impacted any admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal.
Start time: Friday, May 16, 2025, at 10:27 PM UTC
End time: Saturday, May 17, 2025, at 5:10 AM UTC
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that prevented authentication attempts from succeeding, leading to impact.
Next steps: - We analyzing our monitoring telemetry for the affected authentication component to find better ways to identify similar issues prior to them causing impact in the future.
This is the final update for the event.
Time:Fri May 16 23:46:38 2025
Description:Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We've updated the responsible authentication component for the Microsoft Defender for Endpoint infrastructure and are monitoring the recovery to ensure that the impact is remediated.
Scope of impact: This issue may potentially impact any admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal.
Start time: Friday, May 16, 2025, at 10:27 PM UTC
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 7:00 AM UTC
Time:Fri May 16 22:59:40 2025
Description:Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We're working to update the responsible authentication component for the Microsoft Defender for Endpoint infrastructure to remediate the impact. We expect that the updating process will take time to complete.
Scope of impact: Your organization is affected by this event, and admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal may be impacted.
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 5:00 AM UTC
Time:Fri May 16 20:52:27 2025
Description:Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: Our investigation has determined that the components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact. We're evaluating methods to resolve this error to restore the impacted telemetry and alerts as quickly as possible.
Scope of impact: Your organization is affected by this event, and admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal may be impacted.
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 3:00 AM UTC
Time:Fri May 16 20:43:20 2025
Description:Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We're investigating a potential issue with the Microsoft Defender for Endpoint service and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1047160 - Some users may see a draft chat message to a call queue in Microsoft Teams

Status:serviceRestored
Start Time:Mon Mar 17 22:13:00 2025
End Time:Wed May 14 14:04:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri May 16 17:24:01 2025
Root Cause:A recent update that addressed call disconnects introduced an issue with some call queue agents, which resulted in the impact.
Next Update:N/A

Details

Time:Fri May 16 17:24:01 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may have seen a draft chat message to a call queue in Microsoft Teams.
More info: This issue was specifically affecting users who were set up as call queue agents. The problem happened after completing calls. A draft of a chat message from the call queue or resource account appeared in the chat panel. The problem happened in both the Microsoft Teams desktop and web client.
Final status: The deployment of the fix has completed, and we've confirmed this has resolved impact for all users.
Scope of impact: The issue may have impacted some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
End time: Wednesday, May 14, 2025, at 6:04 PM UTC
Root cause: A recent update that addressed call disconnects introduced an issue with some call queue agents, which resulted in the impact.
Next steps: - We're reviewing our update policies to ensure similar issues are identified and addressed ahead of deployment, so this doesn't happen again.
This is the final update for the event.
Time:Fri May 9 17:08:41 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've resolved the issue blocking the continuation of our deployment, and the deployment is currently progressing. Based on our current estimates, we expect the deployment will complete to the affected environment, resolving impact for all users, by our next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 16, 2025, at 11:00 PM UTC
Time:Fri May 2 13:39:15 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: The deployment of our fix is ongoing, however, due to an unrelated issue affecting our deployment infrastructure, it's currently paused. We're working to clear the deployment blocker to resume the deployment of the fix.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 9, 2025, at 11:00 PM UTC
Time:Fri Apr 25 17:57:29 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We’ve initiated the deployment of the fix to the affected environments and are continuing to gather validation as it propagates to ensure successful remediation without adversely impacting other aspects of the service. We’ll provide a resolution timeline once it becomes available.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 2, 2025, at 11:00 PM UTC
Time:Mon Apr 21 17:25:28 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've identified that an unrelated pipeline issue prevented our final round of validations from completing by the previously communicated expected timeframe. We've since resolved the unrelated issue, and we've initiated the deployment of the fix to a subset of impacted users for additional validations to ensure it will successfully remediate impact without adversely impacting other aspects of the service. Once we receive positive feedback that the fix successfully resolves the underlying issue, we'll initiate the deployment to the remaining impacted environments, and we'll aim to provide a resolution timeline once available.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, April 25, 2025, at 11:00 PM UTC
Time:Fri Apr 11 17:51:20 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've initiated our final round of validation for this fix and expect to have a deployment timeline by the next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Monday, April 21, 2025, at 11:00 PM UTC
Time:Wed Apr 9 17:06:48 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: Our validation of the fix is ongoing, and we anticipate having a release timeline by the next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, April 11, 2025, at 11:30 PM UTC
Time:Mon Apr 7 16:38:14 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've completed the development of our code fix, and are beginning our initial testing and validation processes to ensure the efficacy of the fix.
Scope of impact: Your organization is affected by this event, and the issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Wednesday, April 9, 2025, at 10:00 PM UTC
Time:Wed Apr 2 19:35:48 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've identified a recent update addressing certain call disconnect issues which is causing problems with some users configured as call queue agents. We're working on a code fix to address the issue and prevent further draft chat messages from appearing for affected users.
Scope of impact: Your organization is affected by this event, and the issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Monday, April 7, 2025, at 10:00 PM UTC
Time:Wed Apr 2 19:05:04 2025
Description:Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1075049 - Admins may receive stale data for some reports within the Microsoft 365 admin center

Status:serviceRestored
Start Time:Thu May 15 14:20:00 2025
End Time:Thu May 15 20:00:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Fri May 16 12:21:34 2025
Root Cause:A recent configuration change to a data flow process resulted in impact.
Next Update:N/A

Details

Time:Fri May 16 12:03:38 2025
Description:Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
More info: The following reports may be impacted by this event:
-AggCompeteData -AggCompromiseReport -AggPolicyTrafficData -AggTlsDataReport -AggTopTrafficData -AggTrafficData -AggURLProtectionReport -BulkSenderInsightReport -BulkThresholdInsightReport -CampaignData -CampaignDataAzureES -CampaignDataKusto -CompeteMessageTrafficTypeMapping -ComplianceDetailData -CustomerDataRetentions -CustomerInsights -DlpSiDetectionsReport -DomainMxRecord -DynamicDistributionGroupData -EtrLastExecutionData -FeaturesRbacData -FeaturesRbacDataV2 -HotRecipientsData -IBReportAggData -IBReportDetailData -LoBAppData -MDOExternalDashboardCounts -MIPLabelAggData -MIPLabelDetailData -MailLatencySummaryReport -MailLatencySummaryReportAzureES -MailLatencySummaryReportKusto -MailLoopCustomerInsights -MailboxAutoForwardingData -MailflowStatusDLPData -MailflowStatusETRData -MDO UsageCardData -MessageTrafficTypeMapping -Non-Delivery Report (NDR) Data -NonAcceptedDomain -OutboundPoolData -OutboundSecurityData -OutboundSecuritySummary -PhishAggData -PhishAggDataEUDB -PhishAggDataV2 -PolicyBaselines -ReplyAllData -SCInsights -SecurityTrialUsageData -SecurityTrialUsageDataKusto -SmtpClientSubmission -SmtpClientSubmissionV2 -SpoofDetectionAggregationData -SpoofDetectionAggregationHSLData -SpoofDetectionAggregationSummaryData -SpoofDetectionAggregationSummaryHSLData -SupervisoryReviewReport -TABLAggData -TIGlobalAggregates -ThrottledAndBlockedMessagesData
Final status: We confirmed a recent configuration change to the data flow process was the source of impact. We've applied the code fix to the affected environments, and after monitoring the service, we've verified that this action successfully resolved the issue.
Scope of impact: Any admin who attempted to access the reports mentioned in the More info section in the Microsoft 365 admin center may have received stale data.
Start time: Thursday, May 15, 2025, at 6:20 PM UTC
End time: Friday, May 16, 2025, at 12:00 AM UTC
Root cause: A recent configuration change to a data flow process resulted in impact.
Next steps: - We're reviewing how the recent configuration change wasn't identified during our testing and validation process so we can prevent this problem from happening again.
This is the final update for the event.
Time:Thu May 15 22:11:24 2025
Description:Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
More info: The following reports may be impacted by this event:
-AggCompeteData -AggCompromiseReport -AggPolicyTrafficData -AggTlsDataReport -AggTopTrafficData -AggTrafficData -AggURLProtectionReport -BulkSenderInsightReport -BulkThresholdInsightReport -CampaignData -CampaignDataAzureES -CampaignDataKusto -CompeteMessageTrafficTypeMapping -ComplianceDetailData -CustomerDataRetentions -CustomerInsights -DlpSiDetectionsReport -DomainMxRecord -DynamicDistributionGroupData -EtrLastExecutionData -FeaturesRbacData -FeaturesRbacDataV2 -HotRecipientsData -IBReportAggData -IBReportDetailData -LoBAppData -MDOExternalDashboardCounts -MIPLabelAggData -MIPLabelDetailData -MailLatencySummaryReport -MailLatencySummaryReportAzureES -MailLatencySummaryReportKusto -MailLoopCustomerInsights -MailboxAutoForwardingData -MailflowStatusDLPData -MailflowStatusETRData -MDO UsageCardData -MessageTrafficTypeMapping -Non-Delivery Report (NDR) Data -NonAcceptedDomain -OutboundPoolData -OutboundSecurityData -OutboundSecuritySummary -PhishAggData -PhishAggDataEUDB -PhishAggDataV2 -PolicyBaselines -ReplyAllData -SCInsights -SecurityTrialUsageData -SecurityTrialUsageDataKusto -SmtpClientSubmission -SmtpClientSubmissionV2 -SpoofDetectionAggregationData -SpoofDetectionAggregationHSLData -SpoofDetectionAggregationSummaryData -SpoofDetectionAggregationSummaryHSLData -SupervisoryReviewReport -TABLAggData -TIGlobalAggregates -ThrottledAndBlockedMessagesData
Current status: We've identified a recent configuration change to a data flow process that may be resulting in impact. We're creating a code fix to validate if this is the root cause of the issue and in an effort to alleviate impact.
Scope of impact: Any admins who access the above-mentioned reports in Microsoft 365 admin center may receive stale data.
Start time: Thursday, May 15, 2025, at 6:20 PM UTC
Next update by: Friday, May 16, 2025, at 6:00 PM UTC
Time:Thu May 15 21:44:31 2025
Description:Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
Current status: We're investigating a potential issue in which, admins may receive stale data for some reports within the Microsoft 365 admin center. We'll provide an update within 30 minutes.

SP1070801 - Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center

Status:postIncidentReviewPublished
Start Time:Fri May 9 14:33:00 2025
End Time:Fri May 9 17:11:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Thu May 15 21:11:36 2025
Root Cause:A recent change to authentication protocols was deployed in two concurrent flights in order to reduce overall impact on the system. However, due to a configuration error in the flighting protocol, the two flights were not correctly linked. As a result, the logic required to parse id_tokens within authentication requests did not execute properly, which led to 503 errors for users attempting to access SharePoint Online or the SharePoint Online admin center.
Next Update:N/A

Details

Time:Thu May 15 21:07:07 2025
Description:A post-incident report has been published.
Time:Tue May 13 20:18:32 2025
Description:A post-incident report has been published.
Time:Fri May 9 18:00:54 2025
Description:Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may have been unable to access SharePoint Online or the SharePoint Online admin center.
Final status: We've identified that a recent authentication change was deployed before the service was prepared for it, resulting in authentication failures that prevented users and admins from accessing SharePoint Online and the SharePoint Online admin center. We've disabled this change and confirmed using our internal monitoring telemetry, along with reports from affected users, that impact is remediated.
Scope of impact: Any user or admin that attempted to access SharePoint Online or the SharePoint Online admin center may have been impacted.
Start time: Friday, May 9, 2025, at 6:33 PM UTC
End time: Friday, May 9, 2025, at 9:11 PM UTC
Root cause: A recent change to authentication protocols was deployed in two concurrent flights in order to reduce overall impact on the system. However, due to a configuration error in the flighting protocol, the two flights were not correctly linked. As a result, the logic required to parse id_tokens within authentication requests did not execute properly, which led to 503 errors for users attempting to access SharePoint Online or the SharePoint Online admin center.
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
Time:Fri May 9 17:12:02 2025
Description:Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
Current status: We're continuing to investigate the HAR and error logs to identify the root cause and a strategy that remediates impact.
Scope of impact: Any user or admin that attempts to access SharePoint Online or the SharePoint Online admin center may be impacted.
Next update by: Friday, May 9, 2025, at 11:30 PM UTC
Time:Fri May 9 16:44:50 2025
Description:Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
Current status: We're reviewing HTTP Archive format (HAR) logs to identify why users and admins can't access SharePoint Online or the SharePoint Online admin center.
Scope of impact: Any user or admin that attempts to access SharePoint Online or the SharePoint Online admin center may be impacted.
Next update by: Friday, May 9, 2025, at 10:30 PM UTC
Time:Fri May 9 16:23:56 2025
Description:Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1074435 - Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites

Status:serviceRestored
Start Time:Wed May 14 18:30:00 2025
End Time:Thu May 15 11:15:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Thu May 15 11:37:40 2025
Root Cause:A recent feature update, intended to introduce new service logic, contained a code regression that caused site rendering to fail and display a 500 error.
Next Update:N/A

Details

Time:Thu May 15 11:37:40 2025
Description:Title: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites
User impact: Users in Europe, Middle East, and Africa may have been unable to access some Microsoft 365 sites.
More info: Users may have seen 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites included, but were not limited to:
- https://www.microsoft.com/microsoft-365 - https://outlook.com - https://outlook.live.com - https://www.hotmail.com And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround, affected users may have been able to access Microsoft sites using the following URLs: For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365 For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Final status: We've completed deployment of the fix to correct the code regression and confirmed through internal testing that the impact is remediated.
Scope of impact: Impact was specific to some users who are based in the Europe, Middle East and Africa regions attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
End time: Thursday, May 15, 2025, at 3:15 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, contained a code regression that caused site rendering to fail and display a 500 error.
Next steps: - We're reviewing our feature update testing and validation procedures to identify and prevent similar code regressions in deployments moving forward.
This is the final update for the event.
Time:Thu May 15 09:52:26 2025
Description:Title: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites
User impact: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365 - https://outlook.com - https://outlook.live.com - https://www.hotmail.com And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs: For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365 For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We're continuing to deploy the fix to affected regions and initial testing indicates impact has been mitigated in regions that've already received the fix.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 5:30 PM UTC
Time:Thu May 15 08:13:15 2025
Description:Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365 - https://outlook.com - https://outlook.live.com - https://www.hotmail.com And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs: For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365 For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We've validated the fix and begun a deployment to the affected environment. We anticipate this process will be complete and impact remediated by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 3:30 PM UTC
Time:Thu May 15 05:40:57 2025
Description:Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365 - https://outlook.com - https://outlook.live.com - https://www.hotmail.com And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs: For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365 For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We've identified that a recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error. We're validating a fix to repair the regression and remediate impact.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 2:00 PM UTC
Time:Thu May 15 04:41:30 2025
Description:Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365 - https://outlook.com - https://outlook.live.com - https://www.hotmail.com And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs: For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365 For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Next update by: Thursday, May 15, 2025, at 11:00 AM UTC

MO1072938 - Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API

Status:serviceDegradation
Start Time:Tue May 13 13:22:33 2025
End Time:N/A
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Thu May 15 08:59:00 2025
Root Cause:A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next Update:Thursday, May 29, 2025, at 1:30 PM UTC

Details

Time:Thu May 15 08:59:00 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround admins can follow this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Current status: We've produced a fix which we're validating and testing before deploying to the affected environments. We anticipate that the fix will be fully deployed by Thursday, July 10 2025.
Scope of impact: Admins Graph API requests may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Estimated time to resolve: Thursday, July 10 2025
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, May 29, 2025, at 1:30 PM UTC
Time:Wed May 14 10:23:06 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We've identified that a recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API. We're exploring possible mitigation options to resolve impact for affected users.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, May 15, 2025, at 1:30 PM UTC
Time:Wed May 14 03:57:27 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We're continuing to examine errors in the URL to fully understand the origin of the impact and formulate a mitigation plan.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 2:30 PM UTC
Time:Wed May 14 00:13:45 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: Our analysis of the latest collected service logs supports the theory that a duplicated section of the URL provided to the Graph API is resulting in impact. We're proceeding with further analysis of the involved service components to gain additional insight into the underlying source of impact and inform our next steps.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 8:00 AM UTC
Time:Tue May 13 20:32:31 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We're continuing our investigation into recent service updates and REST logs to verify if a duplicated section of the URL provided to the Graph API may be causing impact, and to determine our next troubleshooting actions.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 6:00 AM UTC
Time:Tue May 13 16:39:55 2025
Description:Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We've validated that accepted and rejected senders are unable to be removed by users from Microsoft 365 groups when using the Graph API, and we've adjusted the "Title", "User impact", and "Scope of impact" sections of this communication accordingly. We're analyzing recent service updates to Exchange Online web services along with Representational State Transfer (REST) logs to verify if a duplicated section of the URL provided to the Graph API is the root cause of impact.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 2:00 AM UTC
Time:Tue May 13 14:46:04 2025
Description:Title: Some admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We're analyzing Representational State Transfer (REST) logs and Graph API calls to analyze a misconfigured Outlook URL that may point to the root cause of impact, and what steps we can take to address this issue.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Next update by: Tuesday, May 13, 2025, at 9:00 PM UTC
Time:Tue May 13 13:48:21 2025
Description:Title: Some admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We've verified after reviewing service health information that additional users may be affected by this incident and expanded this communication accordingly. We’re analyzing affected Graph API calls, returned 400 error codes, and Microsoft Graph service logs to better understand the underlying impact and what steps we can take to address this issue.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Next update by: Tuesday, May 13, 2025, at 7:00 PM UTC
Time:Tue May 13 13:23:48 2025
Description:Title: Admins can't remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins can't remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We're investigating a potential issue with admins removing accepted senders from Microsoft 365 groups using the Graph API and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1074194 - Some users may be unable to open PDF and image files in SharePoint Online and receive an error

Status:serviceRestored
Start Time:Wed May 14 14:35:00 2025
End Time:Wed May 14 22:25:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Wed May 14 23:45:21 2025
Root Cause:A recent feature update contained changes resulting in impact.
Next Update:N/A

Details

Time:Wed May 14 23:45:21 2025
Description:Title: Some users may be unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users may have been unable to open PDF and image files in SharePoint Online and received an error.
More info: Impacted users may have seen an error stating "Folder is empty".
Additionally, some users may have encountered similar impact for other file types, including .eml and .msg files.
Final status: We've fully disabled the offending changes and confirmed with a subset of affected users that impact is remediated.
Scope of impact: Some users attempting to open PDF and image files in SharePoint Online may have been impacted.
Start time: Wednesday, May 14, 2025, at 6:35 PM UTC
End time: Thursday, May 15, 2025, at 2:25 AM UTC
Root cause: A recent feature update contained changes resulting in impact.
Next steps: - We're reviewing our feature update testing and validation methods to better identify issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
Time:Wed May 14 23:25:20 2025
Description:Title: Some users may be unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users may be unable to open PDF and image files in SharePoint Online and receive an error.
More info: Impacted users may see an error stating "Folder is empty".
Current status: We've identified that a recent feature update contained changes resulting in impact. We've disabled the offending changes and are reaching out to a subset of affected users for final confirmation that impact is fully remediated.
Scope of impact: Some users attempting to open PDF and image files in SharePoint Online may be impacted.
Root cause: A recent feature update contained changes resulting in impact.
Next update by: Thursday, May 15, 2025, at 5:30 AM UTC
Time:Wed May 14 22:19:29 2025
Description:Title: Some users are unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users are unable to open PDF and image files in SharePoint Online and receive an error.
More info: Impacted users see an error stating "Folder is empty".
Current status: We're reviewing HTTP Archive format (HAR) trace logging and contextual details provided by affected users to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is affected by this event, and some users attempting to open PDF and image files in SharePoint Online are impacted.
Next update by: Thursday, May 15, 2025, at 4:00 AM UTC
Time:Wed May 14 21:58:55 2025
Description:Title: Possible delays or problems when accessing SharePoint Online
User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

EX1072812 - Some users may be unable to access the Outlook desktop and mobile apps

Status:serviceRestored
Start Time:Wed May 7 18:00:00 2025
End Time:Wed May 14 01:09:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Wed May 14 13:45:07 2025
Root Cause:A recent service update was blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next Update:N/A

Details

Time:Wed May 14 13:15:43 2025
Description:Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may have been unable to access the Outlook desktop and mobile apps.
More info: Users may have received an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' was disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps were unaffected.
Users could have enabled the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps; however, the app may have been automatically disabled and cause the impact to reoccur.
Final status: We've completed the reversion of the offending service update and confirmed through service health monitoring that the impact is remediated.
Scope of impact: This issue may have impacted some users attempting to access the Outlook desktop and mobile apps.
Start time: Wednesday, May 7, 2025, at 10:00 PM UTC
End time: Wednesday, May 14, 2025, at 5:09 AM UTC
Root cause: A recent service update was blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next steps: - We're reviewing our service update testing and validation procedures to identify and prevent similar misconfigurations in deployments moving forward.
This is the final update for the event.
Time:Tue May 13 20:22:40 2025
Description:Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may be unable to access the Outlook desktop and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps; however, the app may be automatically disabled and cause the impact to reoccur.
Current status: We’ve reverted the service update in our internal testing environment and confirmed that it resolves the issue without any adverse effects. We’re reverting the impacting update in the affected environment to address the impact, which we anticipate this process to complete and for the fix to reach desirable saturation levels by our next scheduled update.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Wednesday, May 14, 2025, at 7:00 PM UTC
Time:Tue May 13 14:15:18 2025
Description:Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may be unable to access the Outlook desktop and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps, but the app may be automatically disabled and cause the impact to reoccur.
Current status: We're continuing to revert the service update in an internal test environment to confirm if this resolves the issue without causing additional problems for the service. We expect this will complete by our next scheduled update.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Wednesday, May 14, 2025, at 1:00 AM UTC
Time:Tue May 13 13:06:22 2025
Description:Title: Some users may be unable to access the Outlook desktop client and mobile apps
User impact: Users may be unable to access the Outlook desktop client and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop client and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Current status: We've identified that a recent service update is blocking access to the Outlook desktop and mobile apps for some users that have the Microsoft Purview Information Protection app’s service principal disabled. We're reverting this service update in an internal test environment to confirm this resolves the issue without causing additional problems for the service. Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop client and mobile apps, but the app may be automatically disabled and cause the impact to reoccur.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop client and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Tuesday, May 13, 2025, at 8:00 PM UTC
Time:Tue May 13 09:29:23 2025
Description:Title: Some users are unable to access the Outlook desktop client and mobile app
User impact: Users are unable to access the Outlook desktop client and mobile app.
Current status: We suspect that a recent change to the service is resulting in impact we're investigating the suspected problematic code to verify the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users who are located or served through the affected infrastructure.
Next update by: Tuesday, May 13, 2025, at 5:00 PM UTC

TM1035246 - Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues

Status:serviceRestored
Start Time:Fri May 31 20:00:00 2024
End Time:Tue May 13 14:30:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed May 14 05:44:26 2025
Root Cause:A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupted transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, which resulted in impact.
Next Update:N/A

Details

Time:Wed May 14 05:39:55 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
Final status: We've confirmed that the fix has been fully deployed, and impact has been remediated after a period of monitoring service health.
Scope of impact: Impact was specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
End time: Tuesday, May 13, 2025, at 6:30 PM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupted transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, which resulted in impact.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Wed May 7 06:58:55 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The deployment of the fix continues to deploy through the affected infrastructure which we're monitoring to ensure it saturates as expected.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, May 14, 2025, at 11:00 AM UTC
Time:Wed Apr 30 05:46:01 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The deployment of the fix is taking longer than initially anticipated due to the complex nature of the issue. We're continuing to monitor the progress of the fix and expect to provide an estimated deployment timeline by our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, May 7, 2025, at 11:00 AM UTC
Time:Thu Apr 24 05:37:44 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We're continuing to monitor the progress of the fix. We're expecting the fix to complete by the time of our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, April 30, 2025, at 11:00 AM UTC
Time:Thu Apr 17 07:39:19 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We're monitoring the fix as it progresses and we expect to provide an estimated timeline for remediation by our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 24, 2025, at 12:00 PM UTC
Time:Thu Apr 3 07:27:50 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We've encountered some unexpected failures while deploying the fix, which has caused a delay. We've addressed the failures and have resumed deployment. We're monitoring the fix to ensure it resolves impact.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 17, 2025, at 12:00 PM UTC
Time:Wed Mar 19 07:46:34 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The fix is still on track to be successfully deployed by Thursday, April 3, 2025, and we'll endeavour to provide confirmation of deployment as part of our next scheduled update.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 3, 2025, at 12:00 PM UTC
Time:Tue Mar 18 12:21:02 2025
Description:Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We've identified that a code issue present in a SlimCore version utilized by Citrix VDI 2 that disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation. This results in an unoptimized environment, general service functionality delays, and media quality issues. We've created a code fix that is being prepared for deployment and is expected to remediate impact when it completes on Thursday, April 3, 2025.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, March 19, 2025, at 12:00 PM UTC
Time:Tue Mar 18 11:06:28 2025
Description:Title: Users on Citrix Virtual Desktop Infrastructure (VDI) 2 devices experience service quality issues in Microsoft Teams
User impact: Users on Citrix (VDI) 2 devices experience delays and video quality issues in the Microsoft Teams desktop client.
Current status: We're investigating a potential issue with the Microsoft Teams desktop client and are checking for impact to your organization. We'll provide an update within 30 minutes.

TM1072942 - Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams

Status:serviceRestored
Start Time:Mon Apr 28 12:31:00 2025
End Time:Tue May 13 18:45:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Wed May 14 01:49:53 2025
Root Cause:A recent infrastructure migration introduced a misconfiguration, which led to impact.
Next Update:N/A

Details

Time:Wed May 14 01:49:33 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may have seen "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may have seen "unknown presence" showing for some cross cloud users. Users in the same cloud had their presence showing accurately.
Final status: We've confirmed that the fix has successfully been deployed and impact has been remediated.
Scope of impact: Some users may have seen "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
End time: Tuesday, May 13, 2025, at 10:45 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which led to impact.
Next steps: - We're reviewing the affected infrastructure for changes we can make to our testing and detection systems to help prevent similar issues from occurring again in the future.
This is the final update for the event.
Time:Tue May 13 18:08:00 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We've completed development of the fix and initiated its deployment. We're monitoring as it progresses, and we expect it will complete by our next scheduled communication.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Wednesday, May 14, 2025, at 7:30 AM UTC
Time:Tue May 13 17:18:15 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We're in the process of developing a fix to correct the misconfiguration and resolve the issue. We expect an update on our progress with our next scheduled communication.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 11:30 PM UTC
Time:Tue May 13 15:25:19 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We've updated the Title, User impact, and Scope of impact sections to reflect that this impacts Microsoft Teams users and not Skype for Business users. We've determined that a recent infrastructure migration introduced a misconfiguration, which has led to impact. We're working to determine our next steps towards addressing the misconfiguration and resolving the issue.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 9:30 PM UTC
Time:Tue May 13 14:02:09 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We're reviewing service telemetry to isolate the cause of impact and develop a mitigation strategy.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
Next update by: Tuesday, May 13, 2025, at 7:30 PM UTC
Time:Tue May 13 13:33:12 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1068615 - Users may have experienced issues with multiple Microsoft 365 services

Status:postIncidentReviewPublished
Start Time:Tue May 6 09:00:00 2025
End Time:Tue May 6 10:43:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Tue May 13 19:42:55 2025
Root Cause:A small section underlying networking hardware in one of the Dallas regional data centers, used by Microsoft 365 services for Azure Front Door (AFD) routing infrastructure, entered a degraded state. A technical issue in the underlying hardware SKUs resulted in some background power throttling. When the throttling kicked in, the processing workloads on the impacted components were slowed down as the Central Processing Unit (CPU) frequency was reduced. This resulted in high CPU utilization and increased request latencies, eventually causing Border Gateway Protocol (BGP) flapping on the routing infrastructure and client disconnects.
Next Update:N/A

Details

Time:Tue May 13 19:42:08 2025
Description:A post-incident report has been published.
Time:Thu May 8 14:02:19 2025
Description:A post-incident report has been published.
Time:Tue May 6 11:24:53 2025
Description:Title: Users may have experienced issues with multiple Microsoft 365 services
User impact: Users may have experienced issues connecting to multiple Microsoft 365 services and features.
More info: Impacted services included, but were not limited to: - Microsoft Teams - SharePoint Online - Microsoft OneDrive
Final status: We've completed rerouting requests to alternate infrastructure to mitigate impact, and confirmed that the issue is resolved after an extended period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure in North America.
Start time: Tuesday, May 6, 2025, at 1:00 PM UTC
End time: Tuesday, May 6, 2025, at 2:43 PM UTC
Root cause: A small section underlying networking hardware in one of the Dallas regional data centers, used by Microsoft 365 services for Azure Front Door (AFD) routing infrastructure, entered a degraded state. A technical issue in the underlying hardware SKUs resulted in some background power throttling. When the throttling kicked in, the processing workloads on the impacted components were slowed down as the Central Processing Unit (CPU) frequency was reduced. This resulted in high CPU utilization and increased request latencies, eventually causing Border Gateway Protocol (BGP) flapping on the routing infrastructure and client disconnects.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Tue May 6 10:49:19 2025
Description:We've identified a section of AFD infrastructure is performing below acceptable thresholds. We're rerouting traffic to alternate infrastructure to mitigate impact.
Meanwhile, we're also taking mitigation actions to expedite recovery of the Microsoft Teams service.
This quick update is designed to give the latest information on this issue.
Time:Tue May 6 10:22:27 2025
Description:We're reviewing Azure Front Door (AFD) routing configurations and networking telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Time:Tue May 6 10:09:29 2025
Description:Title: Users may experience issues with multiple Microsoft 365 services
User impact: Users may experience issues connecting to multiple Microsoft 365 services and features.
More info: Impacted services include, but is not limited to: - Microsoft Teams
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in North America.
Next update by: Tuesday, May 6, 2025, at 4:30 PM UTC
Time:Tue May 6 10:01:49 2025
Description:Title: Users may experience issues with multiple Microsoft 365 services
User impact: Users may experience issues with multiple Microsoft 365 services.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1072005 - Some users may have seen "unknown presence" instead of an accurate presence for Skype for Business users

Status:serviceRestored
Start Time:Mon Apr 28 12:31:00 2025
End Time:Tue May 13 10:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Tue May 13 10:20:11 2025
Root Cause:A recent infrastructure migration introduced a misconfiguration, which caused impact to occur.
Next Update:N/A

Details

Time:Tue May 13 10:20:11 2025
Description:Title: Some users may have seen "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may have seen "unknown presence" instead of an accurate presence for Skype for Business users.
Final status: We've confirmed that the deployment has completed and that impact has been remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
End time: Tuesday, May 13, 2025, at 2:00 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which caused impact to occur.
Next steps: - We're reviewing our infrastructure migration procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Tue May 13 04:41:32 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: The fix continues to be deployed throughout the affected environments, and we estimate that the deployment will complete by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Estimated time to resolve: Tuesday, May 13, 2025
Root cause: A recent infrastructure migration introduced a misconfiguration, which is causing impact to occur.
Next update by: Tuesday, May 13, 2025, at 4:00 PM UTC
Time:Mon May 12 11:38:59 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: We've completed the development of our fix and have initiated its deployment. We're monitoring the saturation of the fix as it progresses, and some users may begin to experience relief as the deployment continues. We anticipate the deployment will complete, resolving the issue for all users, by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 10:00 AM UTC
Time:Mon May 12 09:32:16 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: We've identified that a recent infrastructure migration has inadvertently introduced a misconfiguration, which has led to impact. We're developing a fix to correct the misconfiguration and remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Monday, May 12, 2025, at 5:30 PM UTC
Time:Mon May 12 08:04:49 2025
Description:Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, May 12, 2025, at 2:00 PM UTC

EX1063822 - Some users' inbound email messages may be received with attachments in a scan in progress state

Status:serviceRestored
Start Time:Tue Apr 22 23:00:00 2025
End Time:Mon May 12 17:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Mon May 12 17:45:43 2025
Root Cause:A recent service update introduced a configuration issue that caused an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index was stale, the queries failed and attachments got stuck in an in-progress scan state.
Next Update:N/A

Details

Time:Mon May 12 17:45:26 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may have been received with attachments in a scan in progress state.
More info: Affected users may have seen a notification within an impacted email message stating that the scan of the attachment was in progress.
Final status: We've completed our validation and deployment of the previously mentioned fix, and we've monitored our service health telemetry to confirm that impact is remediated. Scope of impact: Some users receiving email messages intended to have attachments may have been impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
End time: Monday, May 12, 2025, at 9:00 PM UTC
Root cause: A recent service update introduced a configuration issue that caused an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index was stale, the queries failed and attachments got stuck in an in-progress scan state.
Next steps: - We're reviewing our Exchange Online service update procedures pertaining to the indexes responsible for facilitating the impacted queries to prevent similar impact in future updates. This is the final update for the event.
Time:Thu May 8 21:09:26 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We're in the final stages of our internal testing to validate that our solution will alleviate impact as expected without impeding other aspects of the service. When this process is complete, we’ll provide a timeline for resolution as one becomes available to us.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Monday, May 12, 2025, at 11:00 PM UTC
Time:Wed May 7 21:14:23 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We're making significant progress with our internal testing and validation process to ensure that our fix will alleviate impact as expected. Once the validation process is complete, we'll provide a deployment timeline as one becomes available.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 9, 2025, at 2:30 AM UTC
Time:Tue May 6 21:25:45 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: Our internal testing and validation process is ongoing. This process will allow us to ensure that our solution will alleviate impact as expected without hindering other aspects of the service. We'll provide a timeline for deployment as one becomes available.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 8, 2025, at 2:30 AM UTC
Time:Tue May 6 16:31:24 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: The internal testing of our solution is requiring more time than previously expected, and we're planning for an update on the testing to be available by our next scheduled update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Wednesday, May 7, 2025, at 2:30 AM UTC
Time:Mon May 5 15:46:04 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We've started deploying the fix to our internal testing environment for further validations to ensure it successfully remediates impact without impacting other aspects of the service.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Tuesday, May 6, 2025, at 9:30 PM UTC
Time:Fri May 2 16:40:04 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: Our preparations to deploy the previously mentioned fix are taking longer than expected. When this process is complete, we'll provide a timeline for deployment and remediation.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Monday, May 5, 2025, at 9:30 PM UTC
Time:Fri May 2 13:56:41 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We've completed our internal tests and validations and we're preparing to deploy the fix to the affected environment. We'll aim to provide a timeline for the deployment of the fix to begin by our next scheduled communications update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 2, 2025, at 9:30 PM UTC
Time:Thu May 1 13:22:59 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We're continuing with our internal tests and validations so we can assure that our solution remediates the impact without introducing any unexpected problems to the service.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 2, 2025, at 6:30 PM UTC
Time:Wed Apr 30 21:55:25 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: Our aforementioned validation process is ongoing, though it’s taking an extended time to complete. Once this process has completed, we anticipate that we’ll be able to provide a timeline for the deployment of our fix.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 1, 2025, at 6:30 PM UTC
Time:Wed Apr 30 16:00:25 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We’ve confirmed that our fix to address the configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale is still in the validation stages and it’s not been deployed as previously communicated. Once the fix is validated and deployed, we’ll migrate the affected mailboxes to an alternate portion of service infrastructure to allow for the index to update to the expected value and remediate the impact. We anticipate having an estimation for the timeline of the deployment and subsequent mitigative actions by our next update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 1, 2025, at 2:00 AM UTC
Time:Tue Apr 29 15:05:30 2025
Description:Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We've analyzed the logs gathered from our internal reproduction and identified that a recent service update introduced a configuration issue that’s causing an index our service utilizes for querying email messages and their associated attachments to become stale. Since the index is stale, the query fails, and attachments get stuck in an in progress state. We've developed and deployed a fix to address the configuration issue, and we're migrating the affected mailboxes to an alternate portion of service infrastructure to allow for the index to update to the expected value and remediate the impact. Note that we’ve updated the Title and User impact of this event to better align with the user experience.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index our service utilizes for querying email messages and their associated attachments to become stale. Since the index is stale, the query fails, and attachments get stuck in an in-progress state.
Next update by: Wednesday, April 30, 2025, at 8:30 PM UTC
Time:Tue Apr 29 08:55:25 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've identified a number of recent service updates containing changes which we believe may be causing the persistent impact. We're analyzing logs taken from a recent reproduction of the issue in our internal environments to correlate errors associated with the recent changes, to inform our next steps towards remediation.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 8:00 PM UTC
Time:Tue Apr 29 06:58:06 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We're continuing efforts to troubleshoot the reason for persistent impact alongside your representatives, while we progress with our analysis of the aforementioned diagnostic data. We've been provided additional sample affected network and submission IDs to supplement our analysis.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 1:00 PM UTC
Time:Tue Apr 29 04:57:41 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've received feedback from affected users that impact persists. We're analyzing the gathered additional data and logs in an effort to isolate the reason for the persistent impact. In parallel, we'll soon work directly with affected users to conduct a live troubleshooting sessions to find potential alternative means to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 11:00 AM UTC
Time:Mon Apr 28 21:30:53 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've reached out to a subset of affected users to help them gather additional data, logs, and to confirm whether the issue persists. While we await their response, we're continuing to investigate and analyze previously collected logs to better understand any other contributing factors.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 9:00 AM UTC
Time:Mon Apr 28 15:45:20 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: As we continue working to recover the remaining undelivered attachments, we're reaching out to a subset of affected users to gather additional contextual data as well as fresh message samples to aid our investigation into whether any additional factors are contributing to impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 2:00 AM UTC
Time:Mon Apr 28 14:01:08 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: Recovery of the remaining undelivered attachments is ongoing. We're also reviewing if any other factors may be contributing to the impact to ensure our efforts will totally remediate the impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Monday, April 28, 2025, at 8:00 PM UTC
Time:Mon Apr 28 11:53:48 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've confirmed a recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact. We've undone this change to mitigate the issue for new email messages containing attachments, and we're working on addressing the impact to the remaining undelivered attachments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Monday, April 28, 2025, at 6:00 PM UTC
Time:Mon Apr 28 09:41:19 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
Current status: We've determined that a section of service infrastructure, that facilitates attachment scans in Exchange Online has fallen below our manageable service performance thresholds, resulting in impact. We're working on implementing a fix to modify the feature we suspect is causing the issue, to remediate impact. Meanwhile, we're analyzing any recent changes made to the service to isolate the underlying root cause.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A section of service infrastructure, that facilitates attachment scans in Exchange Online has fallen below our manageable service performance thresholds.
Next update by: Monday, April 28, 2025, at 4:00 PM UTC
Time:Mon Apr 28 07:38:27 2025
Description:Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
Current status: We're reviewing support provided information, alongside service telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, April 28, 2025, at 2:00 PM UTC

EX1069669 - Users’ inbound email messages are quarantined in Exchange Online when they contain attachments

Status:serviceRestored
Start Time:Wed May 7 13:04:00 2025
End Time:Sat May 10 08:00:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:advisory
Last Updated:Mon May 12 16:01:35 2025
Root Cause:A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next Update:N/A

Details

Time:Mon May 12 16:01:35 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages were quarantined in Exchange Online when they contained attachments.
Final status: We've completed our restoration process and have recovered all possible email messages impacted by this event. Any email messages not released at this time were confirmed to be truly malicious and not removed from quarantine.
Scope of impact: Your organization was affected by this event, and some users were impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
End time: Saturday, May 10, 2025, at 12:00 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next steps: - We're investigating opportunities to improve impact detection when enabling signatures utilized by our machine learning model and better prevent similar future impact.
This is the final update for the event.
Time:Fri May 9 18:34:33 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: The email restoration process remains at 73 percent to completion. We’re validating to confirm the proper classification for the remaining affected messages to determine whether they’re truly malicious, or can be recovered.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Monday, May 12, 2025, at 9:00 PM UTC
Time:Fri May 9 15:50:59 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: The email restoration process is 73 percent complete and progressing well. We'll continue monitoring the progress to ensure no issues arise.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Saturday, May 10, 2025, at 12:00 AM UTC
Time:Thu May 8 19:40:22 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: The process of restoring email messages which were originally delivered to quarantine is progressing, though taking an extended period of time, and currently is 64 percent complete. We’re continuing our efforts to restore the affected messages in tandem with investigating ways to expedite our remediating actions.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Friday, May 9, 2025, at 9:00 PM UTC
Time:Thu May 8 16:06:46 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: The process of restoring email messages which were originally delivered to quarantine is ongoing, and currently is 55 percent complete. We anticipate the remaining impacted messages will be restored, and all impact resolved, by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Friday, May 9, 2025, at 1:00 AM UTC
Time:Thu May 8 14:43:35 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We've completed our validation and confirmed that false positive detections associated with the signature have ceased, confirming impact was successfully remediated. We've begun the process of restoring email messages which were originally delivered to quarantine and are working to determine a timeline for restoration completion.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Thursday, May 8, 2025, at 9:00 PM UTC
Time:Thu May 8 12:36:38 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We've further confirmed that a recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact. We've disabled the impacting signature and are validating that we no longer see messages triggering these false positive detections resulting in quarantine. In parallel, we're reviewing options to potentially release previously impacted email from quarantine.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Start time: Wednesday, May 7, 2025, at 5:04 PM UTC
Root cause: A recently enabled signature utilized by our machine learning model to detect malicious email messages contained a misconfiguration, resulting in impact.
Next update by: Thursday, May 8, 2025, at 7:00 PM UTC
Time:Thu May 8 10:52:43 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We are disabling the offending signature via a fix as a possible mitigation step. We anticipate this being complete within two hours.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving email messages containing attachments.
Next update by: Thursday, May 8, 2025, at 5:00 PM UTC
Time:Thu May 8 08:50:56 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We've received feedback from your representatives that adding the affected items to the allowed list has not resolved the issue. We're currently reviewing new Network Message IDs (NMIDs) to understand why email messages with attachments are being quarantined. Additionally, we've developed a potential fix to correct a signature issue that is used to detect malware.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Next update by: Thursday, May 8, 2025, at 3:00 PM UTC
Time:Thu May 8 00:58:41 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We're analyzing a sample of the affected quarantined email messages containing attachments to refine our understanding of the impacted scenario and cultivate our troubleshooting steps, which involves adding the affected items to an allow list to prevent them from being quarantined moving forward.
Scope of impact: Your organization is affected by this event, and some users are impacted when receiving messages containing attachments.
Next update by: Thursday, May 8, 2025, at 1:00 PM UTC
Time:Wed May 7 23:56:50 2025
Description:Title: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments
User impact: Users’ inbound email messages are quarantined in Exchange Online when they contain attachments.
Current status: We're investigating a potential issue Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1069509 - Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams

Status:serviceRestored
Start Time:Thu Apr 10 13:30:00 2025
End Time:Sat May 10 00:30:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon May 12 14:56:19 2025
Root Cause:A service update introduced a settings misconfiguration for town hall meetings, which resulted in impact.
Next Update:N/A

Details

Time:Mon May 12 14:52:13 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have had the option to use eCDN for town hall meetings in Microsoft Teams.
Final status: We've confirmed that our fix has fully deployed and remediated the issue.
Scope of impact: Some users without a Premium license may not have had the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
End time: Saturday, May 10, 2025, at 4:30 AM UTC
Root cause: A service update introduced a settings misconfiguration for town hall meetings, which resulted in impact.
Next steps: - We're reviewing our service update processes so we can better identify similar settings misconfigurations during our testing and development phases and avoid comparable impact to town hall meetings in the future.
This is the final update for the event.
Time:Fri May 9 19:04:23 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Current status: While our initial validations have proven successful, we're in the process of completing our final validations prior to broadly deploying our fix. We anticipate that our fix should deploy and fully resolve the issue by our next scheduled communications update.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Monday, May 12, 2025, at 8:00 PM UTC
Time:Thu May 8 18:17:16 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Current status: We're progressing with our internal validations so we can assure that our fix deployment restores eCDN usage in Microsoft Teams meetings without introducing any unexpected problems to the service. We'll provide an updated timeline for the deployment of our fix once these internal tests have completed.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Friday, May 9, 2025, at 11:30 PM UTC
Time:Thu May 8 15:12:39 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Current status: We've completed development of a code fix to correct the misconfigurations that are causing impact and are verifying its efficacy.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Thursday, May 8, 2025, at 11:30 PM UTC
Time:Wed May 7 19:29:05 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Current status: We’re continuing to review the aforementioned code as we further our efforts in creating corrections that will allow us to redeploy the fix without causing adverse effects. We anticipate that this process will be completed, and we’ll have begun our initial stages of internal validation, before deploying the code change throughout the affected infrastructure.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Thursday, May 8, 2025, at 8:00 PM UTC
Time:Wed May 7 18:01:10 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Current status: We've determined that the fix reported in TM1066722 corrected an issue in which users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams, but this caused additional unexpected impact to analytics. We've reverted the fix, reintroducing the aforementioned issue, and we're reviewing the code to create corrections that will allow us to redeploy it without the affecting users with the additional analytics impact scenario.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A standard service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Thursday, May 8, 2025, at 12:00 AM UTC

CP1070966 - Users may be erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365)

Status:serviceRestored
Start Time:Fri May 2 16:35:00 2025
End Time:Sun May 11 19:10:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Mon May 12 13:31:01 2025
Root Cause:A recent change to the Teams-specific public app ingestion process contained an issue that was resulting in impact.
Next Update:N/A

Details

Time:Mon May 12 13:31:01 2025
Description:Title: Users may be erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365)
User impact: Users may have been erroneously able to see and install Teams-specific public apps in Copilot.
More info: This issue may have allowed users to see and install Teams-specific public apps that were blocked by your organization's policies in the Microsoft Teams admin center, though line-of-business apps weren't impacted.
Final status: We've validated via internal service health telemetry and returned API calls that our targeted fix has been successfully implemented, and users are now unable to see and install Teams-specific public apps in Copilot in alignment with your organization's policies. To ensure mitigation, affected admins may need to restart their current session of the Microsoft Teams admin center to have the fix complete its saturation.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may have been erroneously able to see and install them in Copilot.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
End time: Sunday, May 11, 2025, at 11:10 PM UTC
Root cause: A recent change to the Teams-specific public app ingestion process contained an issue that was resulting in impact.
Next steps: - We're analyzing and reviewing the offending change to Teams-specific public applications ingestion process to better understand the underlying issue and what steps we can take to prevent similar impact from occurring in future. This will also help us to continue our ongoing efforts to improve the resilience of our service for all Copilot users.
This is the final update for the event.
Time:Sat May 10 14:38:55 2025
Description:Title: Users may be erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365)
User impact: Users may be erroneously able to see and install Teams-specific public apps in Copilot.
More info: This issue may allow users to see and install Teams-specific public apps that are blocked by your organization's policies in the Microsoft Teams admin center, though line-of-business apps aren't impacted.
Current status: We've implemented the targeted fix and our review of service health telemetry indicates a positive trend towards recovery. Affected admins may need to restart their current session to have the fix saturate. We're continuing to monitor the service to ensure the issue is resolved.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may be erroneously able to see and install them in Copilot.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
Root cause: A recent change to the Teams-specific public applications ingestion process is resulting in impact.
Next update by: Monday, May 12, 2025, at 6:30 PM UTC
Time:Fri May 9 21:50:02 2025
Description:Title: Users may be erroneously able to see and install Teams-specific apps in Microsoft Copilot (Microsoft 365)
User impact: Users may be erroneously able to see and install Teams-specific apps in Copilot.
More info: This issue may allow users to see and install Teams-specific public apps that are blocked by your organization's policies in Teams Admin Center, though line-of-business apps aren't impacted.
Current status: We've identified a recent change to the Teams-specific public applications ingestion process which is resulting in impact. We're applying a targeted fix to ensure the apps are filtered as intended.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may be erroneously able to see and install them in Copilot.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
Root cause: A recent change to the Teams-specific public applications ingestion process is resulting in impact.
Next update by: Saturday, May 10, 2025, at 8:00 PM UTC
Time:Fri May 9 21:11:03 2025
Description:Title: Users may be erroneously able to see and install Teams-specific apps in Microsoft Copilot (Microsoft 365)
User impact: Users may be erroneously able to see and install Teams-specific apps in Copilot.
More info: This issue may allow users to see and install apps that are blocked by your organization's policies.
Current status: We're investigating a potential issue where users may be erroneously able to see and install Teams specific apps in Microsoft Copilot (Microsoft 365). We'll provide an update within 30 minutes.

MO1070963 - Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint

Status:serviceRestored
Start Time:Fri May 2 16:35:00 2025
End Time:Sun May 11 19:10:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Mon May 12 13:28:47 2025
Root Cause:A recent change to the Teams-specific public applications ingestion process contained an issue that was resulting in impact.
Next Update:N/A

Details

Time:Mon May 12 13:28:47 2025
Description:Title: Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint
User impact: Users may have been erroneously able to install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint.
More info: Additionally, users may have been erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365).
This issue may have allowed users to see and install Teams-specific public apps that were blocked by your organization's policies, though line-of-business apps aren't impacted.
Final status: We've validated via internal service health telemetry and returned API calls that our targeted fix has been successfully implemented, and users are now unable to see and install Teams-specific public apps as expected in alignment with your organization's policies. To ensure mitigation, affected admins may need to restart their current session of the Microsoft Teams admin center to have the fix complete its saturation.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may have been erroneously able to see and install them in Outlook, Word, Excel, and PowerPoint.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
End time: Sunday, May 11, 2025, at 11:10 PM UTC
Root cause: A recent change to the Teams-specific public applications ingestion process contained an issue that was resulting in impact.
Next steps: - We're analyzing and reviewing the offending change to Teams-specific public applications ingestion process to better understand the underlying issue and what steps we can take to prevent similar impact from occurring in future. This will also help us to continue our ongoing efforts to improve the resilience of our service for all users of Microsoft products.
This is the final update for the event.
Time:Sat May 10 14:38:34 2025
Description:Title: Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint
User impact: Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint.
More info: Additionally, users may be erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365).
This issue may allow users to see and install Teams-specific public apps that are blocked by your organization's policies, though line-of-business apps aren't impacted.
Current status: We've implemented the targeted fix and our review of service health telemetry indicates a positive trend towards recovery. Affected admins may need to restart their current session to have the fix saturate. We're continuing to monitor the service to ensure the issue is resolved.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may be erroneously able to see and install them in Outlook, Word, Excel, and PowerPoint.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
Root cause: A recent change to the Teams-specific public applications ingestion process is resulting in impact.
Next update by: Monday, May 12, 2025, at 6:30 PM UTC
Time:Fri May 9 21:47:56 2025
Description:Title: Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint
User impact: Users may be erroneously able to see and install Teams-specific public apps in Outlook, Word, Excel, and PowerPoint.
More info: Additionally, users may be erroneously able to see and install Teams-specific public apps in Microsoft Copilot (Microsoft 365).
This issue may allow users to see and install Teams-specific public apps that are blocked by your organization's policies, though line-of-business apps aren't impacted.
Current status: We've identified a recent change to the Teams-specific public applications ingestion process which is resulting in impact. We're applying a targeted fix to ensure the apps are filtered as intended.
Scope of impact: Any user whose organization's polices block Teams-specific public apps in the Microsoft Teams admin center may be erroneously able to see and install them in Outlook, Word, Excel, and PowerPoint.
Start time: Friday, May 2, 2025, at 8:35 PM UTC
Root cause: A recent change to the Teams-specific public applications ingestion process is resulting in impact.
Next update by: Saturday, May 10, 2025, at 8:00 PM UTC
Time:Fri May 9 21:06:57 2025
Description:Title: Users may be erroneously able to see and install Teams-specific apps in Outlook, Word, Excel, and PowerPoint
User impact: Users may be erroneously able to see and install Teams-specific apps in Outlook, Word, Excel, and PowerPoint.
More info: This issue may allow users to see and install apps that are blocked by your organization's policies.
Current status: We're investigating a potential issue where users may be erroneously able to see and install Teams specific apps in Outlook, Word, Excel, and PowerPoint. We'll provide an update within 30 minutes.

MP1068460 - Admins may have been unable to see policies they’ve created in the Microsoft Purview Communication Compliance portal

Status:serviceRestored
Start Time:Mon May 5 15:00:00 2025
End Time:Sat May 10 14:00:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Mon May 12 03:37:04 2025
Root Cause:A recent update to improve functionality of the Communication Compliance portal was preventing admins from creating policies and viewing their active policies.
Next Update:N/A

Details

Time:Mon May 12 03:37:04 2025
Description:Title: Admins may have been unable to see policies they’ve created in the Microsoft Purview Communication Compliance portal
User impact: Admins may have been unable to see policies they’ve created in the Communication Compliance portal.
More info: Additionally, admins may have been unable to access or create policies within the Communication Compliance portal.
This only impacted the visibility of the policies within the portal. Existing policies are still in effect and continue to work as expected.
Final status: We've successfully reverted to a previous build and confirmed after an extended period of monitoring that impact has been remediated.
Scope of impact: The problem may have impacted any admin trying to view or create policies in the Communication Compliance portal.
Start time: Monday, May 5, 2025, at 7:00 PM UTC
End time: Saturday, May 10, 2025, at 6:00 PM UTC
Root cause: A recent update to improve functionality of the Communication Compliance portal was preventing admins from creating policies and viewing their active policies.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Wed May 7 14:00:51 2025
Description:Title: Some admins may be unable to see policies they’ve created in the Microsoft Purview Communication Compliance portal
User impact: Admins may be unable to see policies they’ve created in the Communication Compliance portal.
More info: Additionally, admins may be unable to access or create policies within the Communication Compliance portal.
This only impacts the visibility of the policies within the portal. Existing policies are still in effect and continue to work as expected.
Current status: Our previous communication indicated that we’ve reverted the affected infrastructure to a previous build. After further review, we’ve assessed that we’re in the process of reverting the impacting update on the affected infrastructure, which is expected to be completed by Monday, May 12, 2025. We’re monitoring the update reversion process to ensure it completes as expected and will subsequently review telemetry to validate impact remediation.
Scope of impact: The problem may impact any admin trying to view or create policies in the Communication Compliance portal.
Start time: Monday, May 5, 2025, at 7:00 PM UTC
Estimated time to resolve: We expected that the impacting update will be reverted and that the problem will be resolved by Monday, May 12, 2025.
Root cause: A recent update to improve functionality of the Communication Compliance portal is preventing admins from creating policies and viewing their active policies.
Next update by: Monday, May 12, 2025, at 11:00 AM UTC
Time:Tue May 6 04:58:25 2025
Description:Title: Some admins may be unable to see the list of policies they have created in the Communication Compliance portal
User impact: Admins may be unable to see the list of policies they have created in the Communication Compliance portal.
More info: Additionally, admins may be unable to access or create policies within the Communication Compliance portal.
This only impacts the visibility of the policies within the portal, and the policies are still in effect and continue to work as expected.
Current status: We've reverted the infrastructure to a previous build version to mitigate impact. We're monitoring service telemetry to confirm full remediation to the service, and anticipate this to be complete by the next update.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure.
Start time: Monday, May 5, 2025, at 7:00 PM UTC
Root cause: A recent update to improve the Communication Compliance portal functionality has causing impact to occur.
Next update by: Monday, May 12, 2025, at 11:00 AM UTC
Time:Tue May 6 03:03:38 2025
Description:Title: Some admins may be unable to see the list of policies they have created in the Communication Compliance portal
User impact: Admins may be unable to see the list of policies they have created in the Communication Compliance portal.
More info: Additionally, admins may be unable to access or create policies within the Communication Compliance portal.
This only impacts the visibility of the policies within the portal, and the policies are still in effect and continue to work as expected.
Current status: We've determined that a recent update to improve the Communication Compliance portal functionality has caused impact. We're reverting the update to mitigate impact.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure.
Start time: Monday, May 5, 2025, at 7:00 PM UTC
Root cause: A recent update to improve the Communication Compliance portal functionality has caused impact.
Next update by: Tuesday, May 6, 2025, at 9:00 AM UTC

MO1071626 - Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services

Status:serviceRestored
Start Time:Sun May 11 20:03:12 2025
End Time:Sun May 11 21:21:25 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Sun May 11 21:21:50 2025
Root Cause:A third-party networking issue occurred in the region, which prevented users from accessing Microsoft 365 services as expected.
Next Update:N/A

Details

Time:Sun May 11 21:21:50 2025
Description:Title: Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in the Japan region may have been unable to access Microsoft 365 services.
Final status: After monitoring, we confirmed that our service has returned to pre-incident thresholds and users can now access Microsoft 365 services as expected.
Scope of impact: Users in the Japan region may have been unable to access Microsoft 365 services.
Start time: Sunday, May 11, 2025, at 11:00 PM UTC
End time: Monday, May 12, 2025, at 1:00 AM UTC
Root cause: A third-party networking issue occurred in the region, which prevented users from accessing Microsoft 365 services as expected.
This is the final update for the event.
Time:Sun May 11 20:56:46 2025
Description:Title: Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services.
Current status: The service appears to be recovering and some users may already be experiencing relief. We're analyzing available service telemetry to identify what initially caused the issue, which we suspect may be network-related, and we're monitoring to confirm the impact doesn't reoccur.
Scope of impact: Users in the Japan region may be unable to access Microsoft 365 services.
Start time: Sunday, May 11, 2025, at 11:00 PM UTC
Next update: Monday, May 12, 2025, at 2:00 AM UTC
Time:Sun May 11 20:09:57 2025
Description:Title: Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in the Japan region may be unable to access Microsoft 365 services.
Current status: We're investigating ways to mitigate any Microsoft 365 user impact as the affected third-party networking service(s) continue investigating and mitigating their impact. We'll provide an update within 30 minutes.

DZ1066273 - Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint

Status:postIncidentReviewPublished
Start Time:Thu May 1 04:30:00 2025
End Time:Thu May 1 21:30:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:incident
Last Updated:Fri May 9 12:05:28 2025
Root Cause:An update was applied to the Microsoft Defender for Endpoint (MDE) client to facilitate the identification of a new critical vulnerability (CVE-2025-31324). This update included a change to an established production-tested component, which implements vulnerability identification using network scanning over standard protocols.
Next Update:N/A

Details

Time:Fri May 9 12:05:28 2025
Description:A post-incident report has been published.
Time:Tue May 6 16:44:33 2025
Description:A post-incident report has been published.
Time:Thu May 1 22:00:00 2025
Description:Title: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint
User impact: Users may have seen crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint.
Final status: We've received feedback from previously affected users who have received the update confirming that the impact is remediated. No action is necessary to receive the update, however any users still experiencing impact may restart their devices to help expedite remediation.
Scope of impact: Any user leveraging third-party apps in Microsoft Defender for Endpoint on Windows devices may have been impacted.
Start time: Thursday, May 1, 2025, at 8:42 AM UTC
End time: Friday, May 2, 2025, at 1:30 AM UTC
Root cause: An update was applied to the Microsoft Defender for Endpoint (MDE) client to facilitate the identification of a new critical vulnerability (CVE-2025-31324). This update included a change to an established production-tested component, which implements vulnerability identification using network scanning over standard protocols.
The vulnerability scanning module functioned by design and as intended, with limited memory, CPU and network resource consumption. In certain customer environments, line of business applications has demonstrated unexpected behaviors responding to this network traffic, which resulted in up-time and reliability impact to these apps specifically, no impact was observed outside the scope of these specific line of business apps.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Thu May 1 20:20:22 2025
Description:Title: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint
User impact: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint.
Current status: We're continuing to monitor our service health telemetry to ensure that the configuration change takes effect in all affected environments, after which we'll confirm with some impacted users that the impact is remediated. Users will continue to experience incremental relief as the fix approaches full saturation.
Scope of impact: Any user leveraging third-party apps in Microsoft Defender for Endpoint may be impacted.
Start time: Thursday, May 1, 2025, at 8:42 AM UTC
Root cause: A recent configuration change to the code pathways leveraged to facilitate third-party app functionality in Microsoft Defender for Endpoint introduced an error that's leading to impact.
Next update by: Friday, May 2, 2025, at 2:30 AM UTC
Time:Thu May 1 18:20:13 2025
Description:Title: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint
User impact: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint.
Current status: We've completed reverting the previously mentioned configuration change leading to impact, and we're monitoring while the change takes effect in all impacted environments to fully remediate the issue. We anticipate that this process will be complete by our next scheduled communications update, and some users may experience early relief as the fix takes effect in their environment.
Scope of impact: Any user leveraging third-party apps in Microsoft Defender for Endpoint may be impacted.
Start time: Thursday, May 1, 2025, at 8:42 AM UTC
Root cause: A recent configuration change to the code pathways leveraged to facilitate third-party app functionality in Microsoft Defender for Endpoint introduced an error that's leading to impact.
Next update by: Friday, May 2, 2025, at 12:30 AM UTC
Time:Thu May 1 16:33:23 2025
Description:Title: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint
User impact: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint.
Current status: We've identified that a recent configuration change to the code pathways leveraged to facilitate third-party app functionality in Microsoft Defender for Endpoint introduced an error that's leading to impact. We're reverting this change to repair the issue, after which we'll monitor our service health telemetry to confirm that the impacted third-party app functions are restored and impact is remediated.
Scope of impact: Any user leveraging third-party apps in Microsoft Defender for Endpoint may be impacted.
Start time: Thursday, May 1, 2025, at 8:42 AM UTC
Root cause: A recent configuration change to the code pathways leveraged to facilitate third-party app functionality in Microsoft Defender for Endpoint introduced an error that's leading to impact.
Next update by: Thursday, May 1, 2025, at 10:30 PM UTC
Time:Thu May 1 16:17:14 2025
Description:Title: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint
User impact: Users may experience crashes, freezes, or navigation errors in third-party apps in Microsoft Defender for Endpoint.
Current status: We're investigating a potential issue with the Microsoft Defender for Endpoint service and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1063758 - Users' searches in SharePoint Online may have returned no results

Status:serviceRestored
Start Time:Wed Apr 16 20:00:00 2025
End Time:Wed May 7 20:00:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Fri May 9 06:53:12 2025
Root Cause:A high number of app requests and retries to an API that facilitates SharePoint Online searches was resulting in the impact.
Next Update:N/A

Details

Time:Fri May 9 06:30:25 2025
Description:Title: Users' searches in SharePoint Online may have returned no results
User impact: Users' searches in SharePoint Online may have returned no results.
More info: The issue specifically impacted tenants created on or after Thursday, April 17, 2025.
Final status: We've developed and deployed the fix, which has remediated impact for the remaining affected users.
Scope of impact: Impact was specific to users in tenants created on or after Thursday, April 17, 2025, and the problem impacted users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
End time: Thursday, May 8, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online searches was resulting in the impact.
Next steps: We’re continuing our investigation to better understand the underlying cause of the higher-than-normal rate of app requests and retries on the affected API to prevent issues like this from occurring in the future.
This is the final update for the event.
Time:Wed May 7 04:57:20 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We’re developing a fix to address this unrelated issue to help mitigate impact for all remaining affected users.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Friday, May 9, 2025, at 11:00 AM UTC
Time:Mon May 5 13:47:47 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We’ve confirmed that our fix has reached the majority of the affected environment, and our telemetry indicates that the issue is largely no longer occurring for most affected users. We’ve determined that an unrelated issue is preventing the fix from reaching the remainder of the affected environment, and we’re reviewing options to address this unrelated issue to resume the fix implementation and resolve the issue for all remaining affected users.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Wednesday, May 7, 2025, at 10:00 AM UTC
Time:Thu May 1 21:19:07 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We're continuing our efforts to process the backlog of requests and have initiated the deployment of the code fix. We're monitoring as this saturates to determine a timeline for completion and ensure remediation.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Monday, May 5, 2025, at 7:00 PM UTC
Time:Wed Apr 30 20:56:05 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We've identified that restarting the service in specific impacted portions of infrastructure may aid in the processing of the backlogged requests. In tandem, we've identified that a code fix that's in the development and testing phase will need to saturate before the requests are able to be fully processed. We'll provide a timeline for these actions as one becomes available.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Friday, May 2, 2025, at 2:30 AM UTC
Time:Tue Apr 29 21:40:00 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We're continuing our review of potential mitigative actions to process the backlog and restore search functionality.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Thursday, May 1, 2025, at 2:30 AM UTC
Time:Tue Apr 29 17:56:34 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We've reviewed service health telemetry which indicates additional action will is required to process the backlog of accumulated requests. We're reviewing potential mitigative actions that can be implemented to process the backlog and restore the service to expected functionality.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Wednesday, April 30, 2025, at 3:00 AM UTC
Time:Tue Apr 29 13:11:18 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We’re monitoring the processing of the backlogged requests and reviewing telemetry in the affected environment to assess and determine whether any additional action is needed to fully resolve this issue.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Tuesday, April 29, 2025, at 10:30 PM UTC
Time:Mon Apr 28 14:42:02 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We've determined that our mitigation efforts for an unrelated service problem have produced a backlog of app requests and retries to an API that facilitates SharePoint Online search, resulting in search impact in SharePoint Online. We've implemented a change to increase processing throughput by reducing the number of retries to the affected API and we're processing the backlog of requests to remediate impact.
Scope of impact: Impact is specific users in tenants created on or after Thursday, April 17, 2025, and the problem impacts users performing searches in SharePoint Online.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Tuesday, April 29, 2025, at 6:00 PM UTC
Time:Mon Apr 28 05:12:23 2025
Description:Title: Users' searches in SharePoint Online may return no results
User impact: Users' searches in SharePoint Online may return no results.
More info: The issue specifically impacts tenants created on or after Thursday, April 17, 2025.
Current status: We've identified that a high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact. We're working to understand the root cause of the high app requests to mitigate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, April 17, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates SharePoint Online search is resulting in the impact.
Next update by: Monday, April 28, 2025, at 7:00 PM UTC

TM1070086 - Users may be unable to create or update sections in the left rail of any Microsoft Teams client

Status:serviceRestored
Start Time:Thu May 8 14:20:00 2025
End Time:Thu May 8 17:19:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu May 8 18:05:52 2025
Root Cause:A portion of the Microsoft Teams service infrastructure was performing below acceptable performance thresholds, resulting in impact.
Next Update:N/A

Details

Time:Thu May 8 17:58:01 2025
Description:Title: Users may be unable to create or update sections in the left rail of any Microsoft Teams client
User impact: Users may have been unable to create or update sections in the left rail of any Microsoft Teams client.
Final status: We've completed our review of service logs and identified that a portion of the Microsoft Teams service infrastructure was operating below acceptable performance thresholds, resulting in impact. We've implemented a fix to restore the affected infrastructure to expected functionality, and we confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any user hosted in the United States region attempting to create or update sections in the left rail of any Microsoft Teams client may have been impacted.
Start time: Thursday, May 8, 2025, at 6:20 PM UTC
End time: Thursday, May 8, 2025, at 9:19 PM UTC
Root cause: A portion of the Microsoft Teams service infrastructure was performing below acceptable performance thresholds, resulting in impact.
Next steps: - We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the underlying issue and better prevent similar impact in the future.
This is the final update for the event.
Time:Thu May 8 16:52:58 2025
Description:Title: Users may be unable to create or update sections in the left rail of any Microsoft Teams client
User impact: Users may be unable to create or update sections in the left rail of any Microsoft Teams client.
Current status: We're continuing to review service logs to identify the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any user hosted in the United States region attempting to create or update sections in the left rail of any Microsoft Teams client may be impacted.
Start time: Thursday, May 8, 2025, at 6:20 PM UTC
Next update by: Thursday, May 8, 2025, at 11:00 PM UTC
Time:Thu May 8 15:34:59 2025
Description:Title: Users may be unable to create or update sections in the left rail of any Microsoft Teams client
User impact: Users may be unable to create or update sections in the left rail of any Microsoft Teams client.
Current status: We're reviewing service logs to identify the root cause of the event, so we can determine our next troubleshooting steps.
Scope of impact: Any user hosted in the United States region attempting to create or update sections in the left rail of any Microsoft Teams client may be impacted.
Start time: Thursday, May 8, 2025, at 6:20 PM UTC
Next update by: Thursday, May 8, 2025, at 9:00 PM UTC
Time:Thu May 8 15:16:52 2025
Description:Title: Users may be unable to create or update sections in the left rail of any Microsoft Teams client
User impact: Users may be unable to create or update sections in the left rail of any Microsoft Teams client.
Current status: We're investigating a potential issue with users being unable to create or update sections in the left rail of any Microsoft Teams client, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

MV1069410 - Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage

Status:serviceRestored
Start Time:Tue May 6 14:52:00 2025
End Time:Wed May 7 18:30:00 2025
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Wed May 7 19:09:47 2025
Root Cause:The portion of affected infrastructure, responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Viva Engage, was operating in a suboptimal state.
Next Update:N/A

Details

Time:Wed May 7 19:09:47 2025
Description:Title: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage
User impact: Users weren't receiving worldwide notifications for storyline announcements and storyline posts in Viva Engage.
Final status: We've completed redirecting traffic to a healthy portion of infrastructure and confirmed that impact has been remediated.
Scope of impact: Any user expecting to receive worldwide notifications for storyline announcements and storyline posts in Viva Engage was impacted.
Start time: Tuesday, May 6, 2025, at 6:52 PM UTC
End time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: The portion of affected infrastructure, responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Viva Engage, was operating in a suboptimal state.
Next steps: - We're reviewing the portion of affected infrastructure to better understand how it entered a suboptimal state and identify what changes can be made to more quickly detect and prevent similar impact in the future.
This is the final update for the event.
Time:Wed May 7 17:26:18 2025
Description:Title: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage
User impact: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Viva Engage.
Current status: Our efforts to restore the portion of affected infrastructure did not remediate the impact as expected. We're redirecting traffic to a healthy portion of infrastructure as an alternate method to resolve the issue.
Scope of impact: Any user expecting to receive worldwide notifications for storyline announcements and storyline posts in Viva Engage is impacted.
Start time: Tuesday, May 6, 2025, at 6:52 PM UTC
Root cause: The portion of affected infrastructure, responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Viva Engage, is operating in a suboptimal state.
Next update by: Wednesday, May 7, 2025, at 11:30 PM UTC
Time:Wed May 7 15:24:20 2025
Description:Title: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage
User impact: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Viva Engage.
Current status: We're continuing to restore the portion of affected infrastructure and will provide a timeline for the restoration as one becomes available.
Scope of impact: Any user expecting to receive worldwide notifications for storyline announcements and storyline posts in Viva Engage is impacted.
Start time: Tuesday, May 6, 2025, at 6:52 PM UTC
Root cause: The portion of affected infrastructure, responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Viva Engage, is operating in a suboptimal state.
Next update by: Wednesday, May 7, 2025, at 9:30 PM UTC
Time:Wed May 7 14:17:50 2025
Description:Title: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage
User impact: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage.
Current status: We've identified that the portion of infrastructure responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage is operating in a suboptimal state. We're restoring the portion of affected infrastructure to remediate the impact.
Scope of impact: Any user expecting to receive worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage is impacted.
Start time: Tuesday, May 6, 2025, at 6:52 PM UTC
Root cause: The portion of affected infrastructure, responsible for facilitating worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage, is operating in a suboptimal state.
Next update by: Wednesday, May 7, 2025, at 7:30 PM UTC
Time:Wed May 7 14:07:57 2025
Description:Title: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage
User impact: Users aren't receiving worldwide notifications for storyline announcements and storyline posts in Microsoft Viva Engage.
Current status: We're investigating a potential issue with Microsoft Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1066722 - Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams

Status:serviceRestored
Start Time:Thu Apr 10 13:30:00 2025
End Time:Wed May 7 15:05:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed May 7 16:01:44 2025
Root Cause:A standard service update introduced a settings misconfiguration for town hall meetings, which was resulting in impact.
Next Update:N/A

Details

Time:Wed May 7 16:01:44 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have had the option to use eCDN for town hall meetings in Microsoft Teams.
More info: Some organizations who had the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may have experienced this issue during the town hall when non-Premium users scheduled a town hall.
Final status: We've completed both the validation and deployment of our fix and confirmed through our service health telemetry that impact was successfully remediated for all users.
Scope of impact: Some users without a Premium license may not have had the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
End time: Wednesday, May 7, 2025, at 7:05 PM UTC
Root cause: A standard service update introduced a settings misconfiguration for town hall meetings, which was resulting in impact.
Next steps: - We're reviewing our service update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
Time:Tue May 6 18:27:12 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
More info: Some organizations who have the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may experience this issue during the town hall when non-Premium users schedule a town hall.
Current status: Validation of the fix is nearing completion and we’re reviewing options to deploy the fix broadly to resolve this issue once the validation is complete. We’ll provide a timeline for the deployment of the fix to the affected environment when available.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A standard service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Wednesday, May 7, 2025, at 11:30 PM UTC
Time:Mon May 5 17:55:29 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
More info: Some organizations who have the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may experience this issue during the town hall when non-Premium users schedule a town hall.
Current status: We've completed the development of our fix, and are preparing to deploy it to our internal testing environment for our initial validation which will be complete by our next scheduled update. Following this, the fix will go through multiple other validation phases.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A standard service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Tuesday, May 6, 2025, at 11:30 PM UTC
Time:Fri May 2 18:33:40 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
More info: Some organizations who have the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may experience this issue during the town hall when non-Premium users schedule a town hall.
Current status: Our investigation has led us to determine that a service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact. We're in the initial stages of developing a fix to correct the issue, and we anticipate that our testing and validation phase should be underway by our next scheduled communications update.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 5:30 PM UTC
Root cause: A standard service update introduced a settings misconfiguration for town hall meetings, which is resulting in impact.
Next update by: Monday, May 5, 2025, at 11:30 PM UTC
Time:Fri May 2 12:30:39 2025
Description:Title: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams
User impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
More info: Some organizations who have the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may experience this issue during the town hall when non-Premium users schedule a town hall.
Current status: We're analyzing service telemetry as well as call IDs from a subset of affected users to help determine our next steps.
Scope of impact: Some users without a Premium license may not have the option to use eCDN for town hall meetings in Microsoft Teams.
Next update by: Friday, May 2, 2025, at 11:30 PM UTC
Time:Fri May 2 12:04:03 2025
Description:Title: Some users without a Premium license may not be able to schedule town hall meetings in Microsoft Teams
User impact: Users without a Premium license may not be able to schedule town hall meetings in Microsoft Teams.
More info: Some organizations who have toggled the 'Use Microsoft eCDN' and also have the Enterprise Content Delivery Network (eCDN) field updated with a third party eCDN in the 'Live events settings" page may experience issues when non-Premium users attempt to schedule a town hall.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1069414 - Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center

Status:serviceRestored
Start Time:Wed May 7 04:00:00 2025
End Time:Wed May 7 14:35:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Wed May 7 15:06:16 2025
Root Cause:A recent service update to a portion of the Microsoft XDR service infrastructure which supports the functionality of the Action center introduced an authentication issue into the service, resulting in impact.
Next Update:N/A

Details

Time:Wed May 7 15:06:16 2025
Description:Title: Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center
User impact: Admins may have been unable to approve or decline actions in the Microsoft Defender XDR security portal Action center.
Final status: We've completed the deployment of the fix and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any admin attempting to approve or decline actions in the Microsoft Defender XDR security portal Action center may have been impacted.
Start time: Wednesday, May 7, 2025, at 8:00 AM UTC
End time: Wednesday, May 7, 2025, at 6:35 PM UTC
Root cause: A recent service update to a portion of the Microsoft XDR service infrastructure which supports the functionality of the Action center introduced an authentication issue into the service, resulting in impact.
Next steps: - We're reviewing our update procedures to understand why impact to the Action center wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
Time:Wed May 7 14:46:42 2025
Description:Title: Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center
User impact: Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center.
Current status: We've identified that a recent service update to a portion of the Microsoft XDR service infrastructure which supports the functionality of the Action center has introduced an authentication issue into the service, resulting in impact. We've developed and validated a fix to address the authentication issue, which we've begun deploying to the affected environment. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Any admin attempting to approve or decline actions in the Microsoft Defender XDR security portal Action center may be impacted.
Start time: Wednesday, May 7, 2025, at 8:00 AM UTC
Root cause: A recent service update to a portion of the Microsoft XDR service infrastructure which supports the functionality of the Action center has introduced an authentication issue into the service, resulting in impact.
Next update by: Wednesday, May 7, 2025, at 9:00 PM UTC
Time:Wed May 7 14:29:15 2025
Description:Title: Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center
User impact: Admins may be unable to approve or decline actions in the Microsoft Defender XDR security portal Action center.
Current status: We're investigating a potential issue with admins being unable to approve or decline actions in the Action center of the Microsoft Defender XDR security portal, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

CP1066418 - Admins may experience delays when receiving certain Copilot reports from the Microsoft 365 admin center

Status:serviceRestored
Start Time:Sun Apr 27 20:00:00 2025
End Time:Mon May 5 01:00:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Tue May 6 22:14:05 2025
Root Cause:An issue with the pipeline for our upstream data source responsible for timely report data in the admin center was causing the above reports delays.
Next Update:N/A

Details

Time:Tue May 6 22:13:54 2025
Description:Title: Admins may experience delays when receiving certain Copilot reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain Microsoft Copilot (Microsoft 365) reports from the admin center.
Final status: We’ve finalized our efforts in rebalancing the data processing load across the affected infrastructure and confirmed that impact has been remediated after an extended period of monitoring. Scope of impact: Admins who attempted to receive the affected Copilot reports may have been impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
End time: Tuesday, May 6, 2025, at 5:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center was causing the above reports delays.
Next steps: - We're continuing to review the underlying cause of the issue with the pipeline for our upstream data source responsible for timely report data in the admin center that was causing the above reports delays to ensure that similar issues aren't replicated.
This is the final update for the event.
Time:Mon May 5 23:14:03 2025
Description:Title: Admins may experience delays when receiving certain Copilot reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain Microsoft Copilot (Microsoft 365) reports from the admin center.
More info: Users may see impact to the following reporting scenarios:
-Copilot usage report -Copilot Chat usage -Copilot readiness report -Copilot usage report (Graph API)
Current status: We’re continuing our final efforts at rebalancing the data processing load across the affected infrastructure to expedite recovery. Additionally, we anticipate that impact will be remediated by our next scheduled update.
Scope of impact: Admins attempting to receive the affected Copilot reports may be impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Wednesday, May 7, 2025, at 3:30 AM UTC
Time:Sat May 3 23:06:09 2025
Description:Title: Admins may experience delays when receiving certain Copilot reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain Microsoft Copilot (Microsoft 365) reports from the admin center.
More info: Users may see impact to the following reporting scenarios:
-Copilot usage report -Copilot Chat usage -Copilot readiness report -Copilot usage report (Graph API)
Current status: We've provided an expanded list of impacted reporting scenarios within the "More info" section of this communication. Our process to develop a solution to alleviate impact continues. In tandem, we're working to rebalance the data processing load across the affected infrastructure to expedite recovery.
Scope of impact: Admins attempting to receive the affected Copilot reports may be impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Tuesday, May 6, 2025, at 5:00 AM UTC
Time:Thu May 1 22:42:32 2025
Description:Title: Admins may experience delays when receiving Copilot Readiness reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving Copilot Readiness reports from the Microsoft 365 admin center.
Current status: We've identified that Microsoft Copilot (Microsoft 365) Readiness report data isn't being supplied to the Microsoft 365 admin center due to issues with the pipeline responsible for supplying the data. We're developing a fix to resolve the pipeline issue and remediate the impact.
Scope of impact: Admins attempting to receive Copilot Readiness reports are impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Sunday, May 4, 2025, at 5:00 AM UTC

MO1066415 - Admins may experience delays when receiving certain reports from the Microsoft 365 admin center

Status:serviceRestored
Start Time:Sun Apr 27 20:00:00 2025
End Time:Tue May 6 01:00:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Tue May 6 22:12:26 2025
Root Cause:An issue with the pipeline for our upstream data source responsible for timely report data in the admin center was causing the above reports delays.
Next Update:N/A

Details

Time:Tue May 6 22:09:14 2025
Description:Title: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center.
More info: Admins may have seen impact to the following reporting scenarios:
-SharePoint Online activity -SharePoint site usage -Mailbox usage -Microsoft 365 usage analytics -Microsoft 365 groups -Email activity -OneDrive user activity -OneDrive usage -Office activations -Skype for Business report -Microsoft Viva Engage activity -Viva Engage device usage -Viva Engage groups activity report -Microsoft 365 Active Users -Microsoft 365 Apps usage -Forms activity -Dynamics 365 Customer Voice activity -Adoption Score -Microsoft browser usage -Microsoft Teams team activity -TeamsAppApplication -TeamsAppUser -Microsoft Teams user activity -Teams Analytics -Integrated Apps -Project activity -Visio activity -Viva Goals activity -NewTeamsActivity -Teams Premium feature usage report
Final status: We’ve finalized our efforts in rebalancing the data processing load across the affected infrastructure and confirmed that impact has been remediated after an extended period of monitoring. Scope of impact: Admins who attempted to receive the affected reports are impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
End time: Tuesday, May 6, 2025, at 5:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center was causing the above reports delays.
Next steps: - We're continuing to review the underlying cause of the issue with the pipeline for our upstream data source responsible for timely report data in the admin center that was causing the above reports delays to ensure that similar issues aren't replicated.
This is the final update for the event.
Time:Mon May 5 23:13:30 2025
Description:Title: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center.
More info: Admins may see impact to the following reporting scenarios:
-SharePoint Online activity -SharePoint site usage -Mailbox usage -Microsoft 365 usage analytics -Microsoft 365 groups -Email activity -OneDrive user activity -OneDrive usage -Office activations -Skype for Business report -Microsoft Viva Engage activity -Viva Engage device usage -Viva Engage groups activity report -Microsoft 365 Active Users -Microsoft 365 Apps usage -Forms activity -Dynamics 365 Customer Voice activity -Adoption Score -Microsoft browser usage -Microsoft Teams team activity -TeamsAppApplication -TeamsAppUser -Microsoft Teams user activity -Teams Analytics -Integrated Apps -Project activity -Visio activity -Viva Goals activity -NewTeamsActivity -Teams Premium feature usage report
Current status: We’re continuing our final efforts at rebalancing the data processing load across the affected infrastructure to expedite recovery. Additionally, we anticipate that impact will be remediated by our next scheduled update.
Scope of impact: Admins attempting to receive the affected reports are impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Wednesday, May 7, 2025, at 3:30 AM UTC
Time:Sat May 3 22:59:02 2025
Description:Title: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving certain reports from the Microsoft 365 admin center.
More info: Admins may see impact to the following reporting scenarios:
-SharePoint Online activity -SharePoint site usage -Mailbox usage -Microsoft 365 usage analytics -Microsoft 365 groups -Email activity -OneDrive user activity -OneDrive usage -Office activations -Skype for Business report -Microsoft Viva Engage activity -Viva Engage device usage -Viva Engage groups activity report -Microsoft 365 Active Users -Microsoft 365 Apps usage -Forms activity -Dynamics 365 Customer Voice activity -Adoption Score -Microsoft browser usage -Microsoft Teams team activity -TeamsAppApplication -TeamsAppUser -Microsoft Teams user activity -Teams Analytics -Integrated Apps -Project activity -Visio activity -Viva Goals activity -NewTeamsActivity -Teams Premium feature usage report
Current status: We've provided an expanded list of impacted reporting scenarios within the "More info" section of this communication. Our process to develop a solution to alleviate impact continues. In tandem, we're working to rebalance the data processing load across the affected infrastructure to expedite recovery.
Scope of impact: Admins attempting to receive the affected reports are impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Tuesday, May 6, 2025, at 5:00 AM UTC
Time:Thu May 1 22:30:35 2025
Description:Title: Admins may experience delays when receiving Microsoft 365 app usage reports from the Microsoft 365 admin center
User impact: Admins may experience delays when receiving Microsoft 365 app usage reports from the Microsoft 365 admin center.
Current status: We've identified Microsoft 365 app usage data isn't being supplied to the Microsoft 365 admin center due to issues with the pipeline responsible for supplying the data. We're developing a fix to resolve the pipeline issue and remediate the impact.
Scope of impact: Admins attempting to receive Microsoft 365 app usage reports are impacted by this issue.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing the above reports delays.
Next update by: Sunday, May 4, 2025, at 5:00 AM UTC

MM1068817 - Users are intermittently unable to run flows or play apps that use Excel Online connectors in Microsoft Power Apps

Status:serviceRestored
Start Time:Sun May 4 19:30:00 2025
End Time:Tue May 6 15:08:00 2025
Service:Power Apps in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Tue May 6 16:07:27 2025
Root Cause:A portion of the Microsoft Power Apps application infrastructure supporting an API that served the Excel Online connectors experienced a period of resource exhaustion, leading to impact.
Next Update:N/A

Details

Time:Tue May 6 15:53:41 2025
Description:Title: Users are intermittently unable to run flows or play apps that use Excel Online connectors in Microsoft Power Apps
User impact: Users were intermittently unable to run flows or play apps that used Excel Online connectors in Microsoft Power Apps.
More info: This issue affected the following connectors:
-Excel Online (Business) -Excel Online (OneDrive)
Final status: We deployed a configuration fix to the affected environments to increase the connection threshold and resolve the impact. After monitoring the service, we confirmed that this action successfully remediated the issue.
Scope of impact: Your organization was affected by this event, and users were intermittently unable to run flows or play apps that used the Excel Online connectors in Microsoft Power Apps.
Start time: Sunday, May 4, 2025, at 11:30 PM UTC
End time: Tuesday, May 6, 2025, at 7:08 PM UTC
Root cause: A portion of the Microsoft Power Apps application infrastructure supporting an API that served the Excel Online connectors experienced a period of resource exhaustion, leading to impact.
Next steps: - We're investigating how the portion of the Microsoft Power Apps application infrastructure supporting an API that served the Excel Online connectors experienced a period of resource exhaustion to prevent this problem from happening again.
This is the final update for the event.
Time:Tue May 6 14:50:56 2025
Description:Title: Users are intermittently unable to run flows or play apps that use Excel Online connectors in Microsoft Power Apps
User impact: Users are intermittently unable to run flows or play apps that use Excel Online connectors in Microsoft Power Apps.
More info: This issue affects the following connectors:
- Excel Online (Business) - Excel Online (OneDrive)
Current status: Our monitoring systems identified a portion of the Microsoft Power Apps infrastructure, supporting an API that serves the Excel Online connectors, experienced a period of resource exhaustion, leading to impact. We're deploying a configuration change to increase the connection threshold and mitigate the issue.
Scope of impact: Your organization is affected by this event, and all users are intermittently unable to run flows or play apps that use the Excel Online connectors in Microsoft Power Apps.
Start time: Sunday, May 4, 2025, at 11:30 PM UTC
Root cause: A portion of the Microsoft Power Apps application infrastructure supporting an API that serves the Excel Online connectors experienced a period of resource exhaustion, leading to impact.
Next update by: Tuesday, May 6, 2025, at 8:00 PM UTC

PP1068772 - Users are intermittently unable to run flows or play apps that use the Excel Online connectors

Status:serviceRestored
Start Time:Sun May 4 19:30:00 2025
End Time:Tue May 6 15:00:00 2025
Service:Power Platform
Feature Group:Other
Classification:advisory
Last Updated:Tue May 6 15:43:27 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue May 6 15:43:27 2025
Description:Title: Users are intermittently unable to run flows or play apps that use the Excel Online connectors
User impact: Users were intermittently unable to run flows or play apps that use the Excel Online connectors.
More info: The following connectors were affected by this issue: • Excel Online (Business) • Excel Online (OneDrive)
Current Status: We have finished applying the necessary configuration changes and, following a period of monitoring, we have confirmed that functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: A portion of the application infrastructure supporting an API that serves the Excel Online connectors experienced a period of resource exhaustion.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
Time:Tue May 6 13:43:08 2025
Description:Title: Users are intermittently unable to run flows or play apps that use the Excel Online connectors
User impact: Users are intermittently unable to run flows or play apps that use the Excel Online connectors.
More info: The following connectors are affected by this issue: • Excel Online (Business) • Excel Online (OneDrive)
Impacted users may be unable to save flows that use the Excel Online connectors.
Current Status: Following our investigation, we determined that a portion of the application infrastructure supporting an API that serves the Excel Online connectors experienced a period of resource exhaustion, leading to impact. We are performing configuration changes to increase the available resources for the impacted portion of infrastructure and mitigate the issue.
Next Update: Tuesday, May 6, 2025, at 8:00 PM UTC
Time:Tue May 6 13:19:14 2025
Description:Title: Users are intermittently unable to run flows or play apps that use the Excel Online connectors
User impact: Users are intermittently unable to run flows or play apps that use the Excel Online connectors.
More info: The following connectors are affected by this issue: • Excel Online (Business) • Excel Online (OneDrive)
Impacted users may be unable to save flows that use the Excel Online connectors.
Current Status: We are aware of an emerging issue where users are unable to run flows or play apps that use the Excel connectors. We are investigating the issue and will provide another update within the next 30 minutes.

MO1068649 - Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI

Status:serviceRestored
Start Time:Tue May 6 09:05:00 2025
End Time:Tue May 6 12:10:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Tue May 6 12:49:59 2025
Root Cause:An unexpected spike in memory usage on a portion of Microsoft Fabric and Power BI infrastructure resulted in impact.
Next Update:N/A

Details

Time:Tue May 6 12:49:59 2025
Description:Title: Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI
User impact: Users experienced slow performance and delays when performing operations in Microsoft Fabric and Power BI.
Final status: After our previous action to reroute traffic to alternate infrastructure, we've taken additional action to provide general optimizations to the infrastructure to better handle processing traffic. After monitoring service health for a period of time, we've confirmed that the spike in memory usage has been mitigated, and impact to users resolved.
Scope of impact: Your organization was affected by this event, and users of Microsoft Fabric and Power BI were impacted.
Start time: Tuesday, May 6, 2025, at 1:05 PM UTC
End time: Tuesday, May 6, 2025, at 4:10 PM UTC
Root cause: An unexpected spike in memory usage on a portion of Microsoft Fabric and Power BI infrastructure resulted in impact.
Next steps: - We're continuing to investigate the source of the spike in memory usage to better understand and prevent similar future impact from occurring.
This is the final update for the event.
Time:Tue May 6 11:13:10 2025
Description:Title: Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI
User impact: Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI.
Current status: After reviewing service monitoring telemetry, we've identified that an unexpected spike in memory usage on a portion of Microsoft Fabric and Power BI infrastructure resulted in impact. We've rerouted operational traffic to alternate infrastructure; however, the issue is still occurring. We're investigating the underlying source of this spike in memory usage to better understand why it's occurring and formulate additional remediating actions.
Scope of impact: Your organization is affected by this event, and users of Microsoft Fabric and Power BI are impacted.
Start time: Tuesday, May 6, 2025, at 1:05 PM UTC
Next update by: Tuesday, May 6, 2025, at 5:30 PM UTC
Time:Tue May 6 10:32:15 2025
Description:Title: Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI
User impact: Users experience slow performance and delays when performing operations in Microsoft Fabric and Power BI.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Your organization is affected by this event, and users of Microsoft Fabric and Power BI are impacted.
Start time: Tuesday, May 6, 2025, at 1:05 PM UTC
Next update by: Tuesday, May 6, 2025, at 4:30 PM UTC

MF1068406 - Some users experience failures with flow triggers and actions that haven't been manually updated for six months

Status:serviceRestored
Start Time:Sat May 3 20:00:00 2025
End Time:Tue May 6 04:00:00 2025
Service:Microsoft Power Automate in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Tue May 6 12:38:44 2025
Root Cause:An authentication component misconfiguration was producing failures with flow triggers and actions that haven't been manually updated for six months.
Next Update:N/A

Details

Time:Tue May 6 12:38:44 2025
Description:Title: Some users experience failures with flow triggers and actions that haven't been manually updated for six months
User impact: Users experienced failures with flow triggers and actions that haven't been manually updated for six months.
Final status: We've confirmed that the authentication component that's utilized for flow triggers and actions had expired. After addressing the authentication component configuration, our internal service telemetry has validated that impact has been remediated.
Scope of impact: Your organization was affected by this event, and users who utilize flow triggers and actions that haven't been manually updated for six months were impacted.
Start time: Sunday, May 4, 2025, at 12:00 AM UTC
End time: Tuesday, May 6, 2025, at 8:00 AM UTC
Root cause: An authentication component misconfiguration was producing failures with flow triggers and actions that haven't been manually updated for six months.
Next steps: - We're further analyzing the affected authentication component's configurations to help us prevent similar problems in the future.
This is the final update for the event.
Time:Tue May 6 01:01:16 2025
Description:Title: Some users experience failures with flow triggers and actions that haven't been manually updated for six months
User impact: Users experience failures with flow triggers and actions that haven't been manually updated for six months.
Current status: Our initial investigation has identified that the authentication component utilized for flow triggers and actions has recently expired. We're currently in the process of saving the impacted flows in order to renew the affected component and resolve the issue.
Scope of impact: Your organization is affected by this event, and users who utilize flow triggers and actions that haven't been manually updated for six months are impacted.
Next update by: Tuesday, May 6, 2025, at 6:00 PM UTC
Time:Tue May 6 00:43:05 2025
Description:Title: Some users experience failures with flow triggers and actions that haven't been manually updated for six months
User impact: Users experience failures with flow triggers and actions that haven't been manually updated for six months.
We're investigating a potential issue with Microsoft Power Automate and checking for impact to your organization. We'll provide an update within 30 minutes.

FL1068390 - Power Automate – Flow triggers and actions that have not been updated for 6 months will fail

Status:serviceRestored
Start Time:Sun May 4 20:22:00 2025
End Time:Tue May 6 04:00:00 2025
Service:Microsoft Power Automate
Feature Group:Other
Classification:advisory
Last Updated:Tue May 6 04:26:24 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue May 6 04:26:24 2025
Description:Title: Power Automate – Flow triggers and actions that have not been updated for 6 months will fail
User impact: Users would have experienced failures with flow triggers and actions that have not been manually updated for 6 months.
More Info: As a mitigating workaround, users could manually save their flow and retry their triggers and actions.
Flows that were manually updated or created in the last 6 months are not impacted.
Final Status: We have completed resaving all impacted flows. Following further review of service diagnostic data, we confirmed that the issue with the expired certificate has been resolved and impact to flow triggers and actions is no longer occurring.
This is the final update on the incident.
Preliminary Root Cause: The authentication certificate utilized for flow triggers and actions had expired.
Next Steps: We are reviewing our configuration procedures to reduce detection time for certificates nearing expiration and prevent this problem from happening again.
Time:Tue May 6 02:52:56 2025
Description:Title: Power Automate – Flow triggers and actions that have not been updated for 6 months will fail
User impact: Users will experience failures with flow triggers and actions that have not been manually updated for 6 months.
More Info: As a mitigating workaround, users can manually save their flow and retry their triggers and actions.
Flows that were manually updated or created in the last 6 months are not impacted.
Current Status: We are continuing to resave all impacted flows to renew their authentication certificate.
Next Update: Tuesday, May 6, 2025, at 9:00 AM UTC
Time:Tue May 6 00:33:36 2025
Description:Title: Power Automate – Flow triggers and actions that have not been updated for 6 months will fail
User impact: Users will experience failures with flow triggers and actions that have not been manually updated for 6 months.
More Info: As a mitigating workaround, users can manually save their flow and retry their triggers and actions.
Flows that were manually updated or created in the last 6 months are not impacted.
Current Status: Our investigation identified that the authentication certificate utilized for flow triggers and actions has expired. We are working to save the impacted flows in order to renew the certificate and mitigate impact.
Next Update: Tuesday, May 6, 2025, at 7:00 AM UTC
Time:Tue May 6 00:02:02 2025
Description:Title: Power Automate – Flow triggers and actions that have not been updated for 6 months will fail
User impact: Users will experience failures with flow triggers and actions that have not been manually updated for 6 months.
More Info: As a mitigating workaround, users can manually save their flow and retry their triggers and actions.
Current Status: We are aware of an emerging issue where users will experience failures with flow triggers and actions that have not been manually updated for 6 months. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

WP1068307 - A small number of users may be unable to connect to the Windows 365 web app

Status:serviceRestored
Start Time:Mon May 5 19:00:00 2025
End Time:Mon May 5 21:00:00 2025
Service:Windows 365
Feature Group:End User
Classification:incident
Last Updated:Mon May 5 21:50:22 2025
Root Cause:A recent service change was resulting in impact.
Next Update:N/A

Details

Time:Mon May 5 21:50:22 2025
Description:Title: A small number of users may be unable to connect to the Windows 365 web app
User impact: Users may have been unable to connect to the Windows 365 web app.
Final status: After reverting the suspected service change and performing an extended period of time monitoring the service health telemetry, we've confirmed that impact has been remediated.
Scope of impact: A small number of users who attempted to connect to the Windows 365 web app may have been affected.
Start time: Monday, May 5, 2025, at 11:00 PM UTC
End time: Tuesday, May 6, 2025, at 1:00 AM UTC
Root cause: A recent service change was resulting in impact.
Next steps: - We're continuing to further investigate the offending service change to ensure issues like this aren't replicated.
This is the final update for the event.
Time:Mon May 5 20:33:59 2025
Description:Title: A small number of users may be unable to connect to the Windows 365 web app
User impact: Users may be unable to connect to the Windows 365 web app.
Current status: We've identified a recent service change which we suspect is resulting in impact. We're reverting this change and we're monitoring to confirm that this remediated the issue.
Scope of impact: A small number of users attempting to connect to the Windows 365 web app may be affected.
Start time: Monday, May 5, 2025, at 11:00 PM UTC
Next update by: Tuesday, May 6, 2025, at 2:00 AM UTC
Time:Mon May 5 20:07:59 2025
Description:Title: A small number of users may be unable to connect to the Windows 365 web app
User impact: Users may be unable to connect to the Windows 365 web app.
Current status: We're investigating a potential issue with users being unable to connect to the Windows 365 web app, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

MP1066110 - Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal

Status:serviceRestored
Start Time:Mon Apr 28 13:20:00 2025
End Time:Mon May 5 19:30:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Mon May 5 21:04:04 2025
Root Cause:A recent deployment aimed at resolving impact for a separate issue introduced compatibility issues, which led to impact.
Next Update:N/A

Details

Time:Mon May 5 21:04:04 2025
Description:Title: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal
User impact: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal.
More info: This issue specifically impacted admins with more than 100 events in a single alert within Activity Explorer.
Affected admins could utilize the export feature to view events outside Information Rights Management (IRM) as expected.
Final status: We completed development of the fix sooner than anticipated and have confirmed its deployment also completed. After a period of monitoring and previously impacted user reports, we've confirmed the impact was remediated.
Scope of impact: Any admin attempting to view events in Activity Explorer within the Microsoft Purview portal may have been impacted.
Start time: Monday, April 28, 2025, at 5:20 PM UTC
End time: Monday, May 5, 2025, at 11:30 PM UTC
Root cause: A recent deployment aimed at resolving impact for a separate issue introduced compatibility issues, which led to impact.
Next steps: - To help prevent similar impact in the future, we're further reviewing our deployment release procedures to identify compatibility issues before being initiated.
This is the final update for the event.
Time:Thu May 1 19:23:56 2025
Description:Title: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal
User impact: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal.
More info: This issue specifically impacts admins with more than 100 events in a single alert within Activity Explorer.
Affected admins can utilize the export feature to view events outside Information Rights Management (IRM) as expected.
Current status: Our investigation has determined a recent deployment aimed at resolving impact for a separate issue introduced compatibility issues, leading to impact. We're in the process of developing a fix and anticipate we will have completed its development by our next scheduled update.
Scope of impact: Any admin attempting to view events in Activity Explorer within the Microsoft Purview portal may be impacted.
Root cause: A recent deployment aimed at resolving impact for a separate issue introduced compatibility issues, leading to impact.
Next update by: Tuesday, May 6, 2025, at 2:00 AM UTC
Time:Thu May 1 15:37:23 2025
Description:Title: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal
User impact: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal.
More info: This issue specifically impacts admins with more than 100 events in a single alert within Activity Explorer.
Affected admins can utilize the export feature to view events outside Information Rights Management (IRM) as expected.
Current status: We're continuing to review HAR captures gathered from affected admins to identify the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any admin attempting to view events in Activity Explorer within the Microsoft Purview portal may be impacted.
Next update by: Friday, May 2, 2025, at 12:00 AM UTC
Time:Thu May 1 12:39:59 2025
Description:Title: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal
User impact: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal.
Current status: We're reviewing HTTP Archive format (HAR) captures provided by affected admins to assist in the investigation and determine our next steps.
Scope of impact: Any admin attempting to view events in Activity Explorer within the Microsoft Purview portal may be impacted.
Next update by: Thursday, May 1, 2025, at 10:00 PM UTC
Time:Thu May 1 12:21:13 2025
Description:Title: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal
User impact: Admins may be unable to see all events in Activity Explorer in the Microsoft Purview portal.
Current status: We're investigating a potential issue with Microsoft Purview Activity Explorer and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1067878 - Users' SharePoint Online links in Microsoft Teams and Exchange Online aren't being scanned by Safe Links

Status:serviceRestored
Start Time:Thu Apr 17 20:00:00 2025
End Time:Mon May 5 17:00:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Mon May 5 17:28:25 2025
Root Cause:A service deployment to address impact associated with an unrelated service problem produced an impacting network routing problem that prevented the Safe Links scanning of SharePoint Online links in Microsoft Teams and Exchange Online.
Next Update:N/A

Details

Time:Mon May 5 17:28:25 2025
Description:Title: Users' SharePoint Online links in Microsoft Teams and Exchange Online aren't being scanned by Safe Links
User impact: Users' SharePoint Online links in Microsoft Teams and Exchange Online weren't being scanned by Safe Links.
More info: This specifically impacted users with an E5 license.
Final status: Following our change reversion process, our internal service telemetry has validated that the network routing problems have been addressed, and that impact has been remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure and have an E5 license.
Start time: Friday, April 18, 2025, at 12:00 AM UTC
End time: Monday, May 5, 2025, at 9:00 PM UTC
Root cause: A service deployment to address impact associated with an unrelated service problem produced an impacting network routing problem that prevented the Safe Links scanning of SharePoint Online links in Microsoft Teams and Exchange Online.
Next steps: - We're further analyzing the offending service deployment to help us improve our deployed solutions and so we can help prevent similar problems in the future.
This is the final update for the event.
Time:Mon May 5 15:30:53 2025
Description:Title: Users' SharePoint Online links in Microsoft Teams and Exchange Online aren't being scanned by Safe Links
User impact: Users' SharePoint Online links in Microsoft Teams and Exchange Online aren't being scanned by Safe Links.
More info: This specifically impacts users with an E5 license.
Current status: Our additional analysis has determined that impact isn't specific to files or documents received through SharePoint Online and that any SharePoint Online link sent through Microsoft Teams or Exchange Online isn't being scanned by Safe Links. We've updated the Title, and User Impact portions of our communications to reflect this new understanding. We've identified a network routing problem that was introduced by the recent service update, and while exploring alternate options for addressing the network problems, we're continuing with our change reversion process in our efforts to remediate the impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and have an E5 license.
Next update by: Monday, May 5, 2025, at 10:00 PM UTC
Time:Mon May 5 13:36:39 2025
Description:Title: Users' files or documents received through SharePoint Online may not be scanned by Safe Links
User impact: Users' files or documents received through SharePoint Online may not be scanned by Safe Links.
More info: This specifically impacts users with an E5 license.
Current status: As we progress with our root cause analysis and confirm the source for this event, we're conducting our change reversion process for the isolated service update in our efforts to remediate the impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and have an E5 license.
Next update by: Monday, May 5, 2025, at 8:00 PM UTC
Time:Mon May 5 11:39:55 2025
Description:Title: Users' files or documents received through SharePoint Online may not be scanned by Safe Links
User impact: Users' files or documents received through SharePoint Online may not be scanned by Safe Links.
More info: This specifically impacts users with an E5 license.
Current status: Our analysis into networking logs has isolated a recent update to the service that we believe may be preventing files and documents received through SharePoint Online from being scanned by Safe Links. We're further analyzing the service update to confirm our findings, so we can determine our next steps for remediating the impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and have an E5 license.
Next update by: Monday, May 5, 2025, at 6:00 PM UTC
Time:Mon May 5 09:44:50 2025
Description:Title: Users' files or documents received through SharePoint Online may not be scanned by SafeLinks
User impact: Users' files or documents received through SharePoint Online may not be scanned by SafeLinks.
More info: This specifically impacts users with an E5 license.
Current status: We're reviewing network logs to isolate the root cause in order to mitigate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and have a E5 license.
Next update by: Monday, May 5, 2025, at 4:00 PM UTC
Time:Mon May 5 07:50:35 2025
Description:Title: Users' files or documents received through SharePoint Online may not be scanned by SafeLinks
User impact: Users' files or documents received through SharePoint Online may not be scanned by SafeLinks.
More info: This specifically impacts users with an E5 license.
Current status: We're reviewing service monitoring telemetry to isolate the root cause in order to mitigate impact and recover the service.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and hold an E5 license.
Next update by: Monday, May 5, 2025, at 2:00 PM UTC

PP1068079 - Service degradation affecting multiple scenarios

Status:serviceRestored
Start Time:Mon May 5 10:30:00 2025
End Time:Mon May 5 11:28:00 2025
Service:Power Platform
Feature Group:Other
Classification:advisory
Last Updated:Mon May 5 14:38:47 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Mon May 5 14:01:08 2025
Description:Title: Service degradation affecting multiple scenarios
User impact: Users experienced degraded service functionality affecting multiple scenarios.
More Info: The following scenarios were affected by this incident: • Management experiences Environment listing and management including lifecycle operations in Power Platform admin center (PPAC), Power Apps, and Power Automate portals. App and flow management (listing, creation, edit, API and connections management) PPAC tenant settings management • Power Apps Playing apps Getting User Consent • Power Automate Getting User Consent Power Automate for desktop sign-in • Microsoft Copilot Studio Getting the status of copilots Creating plug-ins
Final Status: Our internal monitoring alerted us to an issue in which users were experiencing degraded service functionality for multiple Power Platform services. Our investigation determined that a recent update led to a capacity constraint during peak service traffic on a portion of the infrastructure supporting Power Platform. We restored capacity within the affected infrastructure and confirmed via service health diagnostics that service functionality has been restored.
This is the final update for this incident.
Preliminary Root Cause: A recent update led to a capacity constraint during peak service traffic on a portion of the infrastructure supporting Power Platform.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.

EX1067552 - Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine

Status:serviceRestored
Start Time:Sun May 4 11:16:00 2025
End Time:Sun May 4 19:20:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Mon May 5 13:30:50 2025
Root Cause:A configuration issue with our machine learning (ML) classification model may have caused some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next Update:N/A

Details

Time:Mon May 5 12:31:20 2025
Description:Title: Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine
User impact: Users may have had potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Final status: Following the deployment of the corrected model and resubmission of all email impacted during this event through the corrected model, our internal telemetry has verified that our ML model configuration changes have remediated the impact.
Scope of impact: Some users whose email messages were processed through the offending ML model may have had potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Start time: Sunday, May 4, 2025, at 3:16 PM UTC
End time: Sunday, May 4, 2025, at 11:20 PM UTC
Root cause: A configuration issue with our machine learning (ML) classification model may have caused some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next steps: - We're further analyzing our ML classification model configuration procedures to identify how it entered this state and areas for improvement to help prevent similar problems in the future.
This is the final update for the event.
Time:Sun May 4 20:06:51 2025
Description:Title: Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine
User impact: Users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Current status: We're continuing to monitor the deployment of the corrected model that is still at 80 percent saturation, as it's taking longer than expected to complete. In parallel, we're working to resubmit affected messages to properly categorize them and resolve impact. We'll provide an update on the deployment and resubmission process during our next scheduled update.
Scope of impact: Some users whose email messages are processed through the offending ML model may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Start time: Sunday, May 4, 2025, at 3:16 PM UTC
Root cause: A configuration issue with our Machine Learning (ML) classification model may be causing some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next update by: Monday, May 5, 2025, at 6:00 PM UTC
Time:Sun May 4 17:40:58 2025
Description:Title: Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine
User impact: Users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Current status: The deployment of our corrected model is taking longer than anticipated and is currently at 80 percent saturation. We’re evaluating what actions we can take to expedite the remainder of our deployment, and we aim to provide an updated timeline to mitigation as one becomes available.
Scope of impact: Some users whose email messages are processed through the offending ML model may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Start time: Sunday, May 4, 2025, at 3:16 PM UTC
Root cause: A configuration issue with our Machine Learning (ML) classification model may be causing some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next update by: Monday, May 5, 2025, at 1:00 AM UTC
Time:Sun May 4 16:59:50 2025
Description:Title: Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine
User impact: Users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Current status: The deployment of our corrected model is taking longer than anticipated and is currently at sixty percent saturation. We’re evaluating what actions we can take to expedite the deployment. We aim to provide an updated timeline to mitigation as one becomes available.
Scope of impact: Some users whose email messages are processed through the offending ML model may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Start time: Sunday, May 4, 2025, at 3:16 PM UTC
Root cause: A configuration issue with our Machine Learning (ML) classification model may be causing some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next update by: Sunday, May 4, 2025, at 11:00 PM UTC
Time:Sun May 4 15:34:34 2025
Description:Title: Some users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine
User impact: Users may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Current status: We've identified via our automated monitoring system an issue with one of our Machine Learning (ML) models, which may be causing potential phishing email messages to be sent to users' Junk folder in Exchange Online instead of quarantine. We've determined this issue was caused by a configuration issue with a specific component with one of our ML models, which is responsible for labelling high-confidence phishing email messages, causing some potential phishing email messages to be sent to the Junk folder instead of being quarantined. We've adjusted and are in the process of deploying the corrected model to resolve the issue. We anticipate the impact to new messages will be resolved by the time of our next scheduled communications update, after which we’ll reprocess impacted messages to fully address the issue.
Scope of impact: Some users whose email messages are processed through the offending ML model may have potential phishing email messages sent to their Junk folder in Exchange Online instead of quarantine.
Start time: Sunday, May 4, 2025, at 3:16 PM UTC
Root cause: A configuration issue with our Machine Learning (ML) classification model may be causing some potential phishing email messages to be sent to the Junk folder instead of being quarantined.
Next update by: Sunday, May 4, 2025, at 9:00 PM UTC

DZ1067502 - Some users may be unable to access the Connected applications page in the Microsoft Defender portal

Status:serviceRestored
Start Time:Sun Apr 27 02:55:00 2025
End Time:Sun May 4 12:43:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Sun May 4 12:57:28 2025
Root Cause:A recent deployment for the Microsoft Defender portal contained a code misconfiguration which prevented users from being able to access the Connected applications page.
Next Update:N/A

Details

Time:Sun May 4 12:57:28 2025
Description:Title: Some users may be unable to access the Connected applications page in the Microsoft Defender portal
User impact: Users may have been unable to access the Connected applications page in the Microsoft Defender portal.
More info: Affected users were returned an error message when attempting to access the Connected Applications page that stated: "Failed to load data. Please try again later."
Final status: Our fix deployment to address the code misconfiguration preventing users from accessing the Connected applications page in the Microsoft Defender portal has completed faster than anticipated. After a period of monitoring user access requests, we've validated that user impact is resolved.
Scope of impact: Some users whose access requests were routed through affected portions of Microsoft Defender service infrastructure may have been unable to access the Connected applications page in the Microsoft Defender portal.
Start time: Sunday, April 27, 2025, at 6:55 AM UTC
End time: Sunday, May 4, 2025, at 4:43 PM UTC
Root cause: A recent deployment for the Microsoft Defender portal contained a code misconfiguration which prevented users from being able to access the Connected applications page.
Next steps: - We're analyzing and evaluating the service update which introduced the code misconfiguration to better understand why impact wasn’t caught during the update testing and validation phase. This is to help us ensure that similar impact doesn’t occur in future and identify what steps we can take to bolster the resilience of our service for all users of Microsoft Defender.
This is the final update for the event.
Time:Sun May 4 12:19:41 2025
Description:Title: Some users may be unable to access the Connected applications page in the Microsoft Defender portal
User impact: Users may be unable to access the Connected applications page in the Microsoft Defender portal.
More info: Affected users are returned an error message when attempting to access the Connected Applications page that states: "Failed to load data. Please try again later.".
Current status: We've received user reports indicating that some users may be unable to access the Connected applications page in the Microsoft Defender portal and are returned an error message. We've determined that a recent deployment for the Microsoft Defender portal contains a code misconfiguration which is preventing users from being able to access the Connected applications page. We're pushing a fix to address the code misconfiguration, and we aim to provide a timeline to mitigation as one becomes available.
Scope of impact: Some users whose access requests are routed through affected portions of Microsoft Defender service infrastructure may be unable to access the Connected applications page in the Microsoft Defender portal.
Start time: Sunday, April 27, 2025, at 6:55 AM UTC
Root cause: A recent deployment for the Microsoft Defender portal contains a code misconfiguration which is preventing users from being able to access the Connected applications page.
Next update by: Sunday, May 4, 2025, at 5:30 PM UTC

EX1057770 - Some users’ saved Outlook calendar views may not be preserved

Status:serviceRestored
Start Time:Thu Apr 3 16:22:00 2025
End Time:Thu May 1 11:00:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Fri May 2 16:38:39 2025
Root Cause:A recent service update contained a code issue that prevented the service from recognizing saved view calendar IDs.
Next Update:N/A

Details

Time:Fri May 2 16:38:39 2025
Description:Title: Some users’ saved Outlook calendar views may not be preserved
User impact: Users’ saved Outlook calendar views may have not been preserved.
More info: This issue may have impacted users who were leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Final status: We've confirmed the fix deployment has completed to all impacted infrastructure and validated remediation via internal testing.
Scope of impact: Any user may have been impacted by this event if they were using Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams and have saved Outlook calendar views.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
End time: Thursday, May 1, 2025, at 3:00 PM UTC
Root cause: A recent service update contained a code issue that prevented the service from recognizing saved view calendar IDs.
Next steps: - We're continuing our analysis of the code change responsible for impact to better identify and prevent similar impact in the future.
This is the final update for the event.
Time:Fri Apr 25 16:54:08 2025
Description:Title: Some users’ saved Outlook calendar views may not be preserved
User impact: Users’ saved Outlook calendar views may not be preserved.
More info: This issue may impact users who are leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Current status: We’ve completed our internal validation of a secondary fix that will address the problem for views that haven't been opened since April 3, 2025, and we’re preparing the fix for deployment. Based on our current estimates, we expect the deployment to complete by our next scheduled update.
Scope of impact: Any user may be impacted by this event if they're on Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams and have saved Outlook calendar views.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contains a code issue that's preventing the service from recognizing saved view calendar IDs.
Next update by: Friday, May 2, 2025, at 10:00 PM UTC
Time:Mon Apr 21 17:32:29 2025
Description:Title: Some users’ saved Outlook calendar views may not be preserved
User impact: Users’ saved Outlook calendar views may not be preserved.
More info: This issue may impact users who are leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Current status: After deploying our fix to prevent newly created saved views from becoming impacted, we're continuing to internally validate our secondary fix that will address the problem for views that haven't been opened since April 3, 2025. We'll provide an updated timeline for the deployment of our fix once it has become available.
Scope of impact: Any user may be impacted by this event if they're on Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams and have saved Outlook calendar views.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contains a code issue that's preventing the service from recognizing saved view calendar IDs.
Next update by: Friday, April 25, 2025, at 10:00 PM UTC
Time:Sat Apr 19 00:56:59 2025
Description:Title: Some users’ saved Outlook calendar views may not be preserved
User impact: Users’ saved Outlook calendar views may not be preserved.
More info: This issue may impact users who are leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Current status: We've completed the deployment of our fix to prevent newly created saved views from becoming impacted, although users may need to refresh their client to ensure they receive the change. In parallel, we're beginning the validation of our secondary fix to prevent views that haven't been opened since the issue began on Thursday, April 3, 2025, from being impacted.
Scope of impact: Any user may be impacted by this event if they're on Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams and have saved Outlook calendar views.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contains a code issue that's preventing the service from recognizing saved view calendar IDs.
Next update by: Monday, April 21, 2025, at 10:30 PM UTC
Time:Fri Apr 18 19:30:59 2025
Description:Title: Some users’ saved Outlook calendar views may not be preserved
User impact: Users’ saved Outlook calendar views may not be preserved.
More info: This issue may impact users who are leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Current status: We've developed and begun deploying a fix to prevent newly created saved views from becoming impacted, and anticipate this will take effect by our next update. In parallel, we're continuing to prepare a fix to restore the expected behavior to Outlook calendar saved views that have already been impacted.
Scope of impact: Any user may be impacted by this event if they're on Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams and have saved Outlook calendar views.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contains a code issue that's preventing the service from recognizing saved view calendar IDs.
Next update by: Saturday, April 19, 2025, at 6:30 AM UTC
Time:Fri Apr 18 13:16:48 2025
Description:Title: Some users may experience issues with their Outlook calendar saved views not being preserved
User impact: Users may experience issues with their Outlook calendar saved views not being preserved.
More info: This issue may impact users who are leveraging Outlook on the web, the new Outlook desktop client experience, or those who have the new Calendar enabled in Microsoft Teams.
Current status: Our work to develop and validate a fix to address the issue is ongoing.
Scope of impact: Any user may be impacted by this event if they're on Outlook on the web, the new Outlook desktop client, or using the new Calendar on Microsoft Teams.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contains a code issue that's causing the service to not recognize saved view calendar IDs.
Next update by: Saturday, April 19, 2025, at 1:00 AM UTC
Time:Fri Apr 18 02:26:45 2025
Description:Title: Some users may experience issues with their Outlook calendar saved views not being preserved
User impact: Users may experience issues with their Outlook calendar saved views not being preserved.
More info: This issue may impact users in Outlook on the web and New Outlook.
In addition, users who have New Calendar enabled in Microsoft Teams may also be impacted.
Current status: We received reports of an issue with Outlook calendar saved views. Our investigation identified a recent service update containing a code issue that's causing the service to incorrectly fail to recognize saved view calendar IDs, leading to impact. We're working to internally test and develop a fix for this issue to remediate impact.
Scope of impact: Users may be impacted by this event experience issues with their Outlook calendar saved views not being preserved.
Start time: Thursday, April 3, 2025, at 8:22 PM UTC
Root cause: A recent service update contained a code issue that's causing the service to incorrectly fail to recognize saved view calendar IDs, leading to impact.
Next update by: Friday, April 18, 2025, at 7:00 PM UTC

CP1053707 - Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)

Status:serviceRestored
Start Time:Wed Apr 9 12:34:00 2025
End Time:Fri May 2 11:00:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Fri May 2 15:59:09 2025
Root Cause:An issue with the navigation panel in Copilot caused the "Get agents" link to route incorrectly, which led to impact.
Next Update:N/A

Details

Time:Fri May 2 15:58:44 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to access the "Get agents" link in Copilot.
More info: Affected users may have seen an empty popup window after they clicked the "Get agents" link.
As an alternative while we were focused on mitigation, users could have navigated to https://www.microsoft365.com/chat and selected "Apps" from the left sidebar, then clicked the "Get more Apps" button in the upper righthand section, and, lastly, selected "Agents" in the "Featured" section in the Apps sidebar on the left to access agents.
Final status: We've confirmed that our fix has completed its deployment and we've verified that the issue has been resolved.
Scope of impact: This issue may have affected some users who accessed the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
End time: Friday, May 2, 2025, at 3:00 PM UTC
Root cause: An issue with the navigation panel in Copilot caused the "Get agents" link to route incorrectly, which led to impact.
Next steps: - We're continuing to analyze the navigation panel issue so we can more quickly identify similar routing problems and avoid comparable impact in the future.
This is the final update for the event.
Time:Mon Apr 28 16:27:01 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the "Featured" section in the Apps sidebar on the left to access agents.
Current status: Our fix deployment remains on track to complete by Friday, May 2, 2025. We continue to recommend that affected users utilize the workaround outlined in the "More info" section to avoid impact while the deployment progresses.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Estimated time to resolve: Our fix deployment timeline expects for this deployment to have completed by Friday, May 2, 2025.
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Friday, May 2, 2025, at 9:30 PM UTC
Time:Wed Apr 23 16:12:39 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the "Featured" section in the Apps sidebar on the left to access agents.
Current status: We've completed development of the fix for the remaining impacted users whose "Get agents" link isn’t working and have initiated deployment. Based on current estimates, we expect deployment to complete by Friday, May 2, 2025. We recommend that affected users continue using the workaround outlined in the "More info" section to avoid impact while the deployment progresses.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Monday, April 28, 2025, at 9:30 PM UTC
Time:Tue Apr 22 16:18:26 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the "Featured" section in the Apps sidebar on the left to access agents.
Current status: We’re continuing efforts to develop a fix for the remaining impacted users whose "Get agents" link isn’t working. Once available, we’ll share a resolution timeline. In the meantime, we recommend affected users follow the workaround outlined in the "More info" section to avoid the issue while we continue to work on a long-term solution.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Wednesday, April 23, 2025, at 9:30 PM UTC
Time:Mon Apr 21 16:36:09 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the "Featured" section in the Apps sidebar on the left to access agents.
Current status: We're continuing our efforts of developing a fix for the remaining impacted users whose "Get agents" link isn't working, and we'll aim to provide a resolution timeline when applicable. We recommend impacted users perform the workaround mentioned in the "More info" section of this communication to avoid the issue while we work on a long-term solution.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Tuesday, April 22, 2025, at 9:30 PM UTC
Time:Fri Apr 18 16:15:52 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We've confirmed that most users should no longer be affected by this issue following our previous mitigation actions. We're continuing to develop a fix for the subset of remaining users whose "Get agents" link isn't working.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Monday, April 21, 2025, at 9:30 PM UTC
Time:Thu Apr 17 21:11:37 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: Our fix to partially remediate impact has completed propagating through the affected environments and impact should be alleviated for some users. We’re now working on identifying a mitigation pathway to address the remaining impact and to fully resolve the issue.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Friday, April 18, 2025, at 9:30 PM UTC
Time:Thu Apr 17 14:49:51 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We’re continuing to monitor the deployment of the fix as it progresses through the affected environments. As it propagates, some users may begin to experience impact relief.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Friday, April 18, 2025, at 2:00 AM UTC
Time:Tue Apr 15 15:50:33 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We're monitoring the fix deployment as it progresses, and we'll provide an estimated time for completion as one becomes available.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: An issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Thursday, April 17, 2025, at 8:00 PM UTC
Time:Mon Apr 14 20:22:44 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We developed and are deploying a fix that will partially remediate the impact from the issue and are working on a mitigation pathway for any remaining impact.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Start time: Wednesday, April 9, 2025, at 4:34 PM UTC
Root cause: A issue with the navigation panel in Copilot is causing the "Get agents" link to route incorrectly, leading to impact.
Next update by: Tuesday, April 15, 2025, at 8:00 PM UTC
Time:Mon Apr 14 14:28:38 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We're continuing to analyze system logs to identify the root cause and a strategy that remediates impact.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Next update by: Tuesday, April 15, 2025, at 1:30 AM UTC
Time:Fri Apr 11 20:57:02 2025
Description:Title: Some users may be unable to access the "Get agents" link in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access the "Get agents" link in Copilot.
More info: Affected users may see an empty popup window after clicking the "Get agents" link.
As an alternative while we're focused on mitigation, users can navigate to https://www.microsoft365.com/chat and select "Apps" from the left sidebar, then click the "Get more Apps" button in the upper righthand section, and, lastly, select "Agents" in the Featured section in the Apps sidebar on the left to access agents.
Current status: We're analyzing system logs to understand why the link for "Get agents" isn't working as expected. We'll provide an update on our findings and any potential mitigation actions by the next scheduled update time.
Scope of impact: This issue may affect some users accessing the "Get agents" link in Copilot.
Next update by: Monday, April 14, 2025, at 7:30 PM UTC
Time:Fri Apr 11 19:51:42 2025
Description:Title: We're looking into a potential problem impacting Microsoft Copilot (Microsoft 365)
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.

OD1066143 - Some users may be unable to access Microsoft OneDrive through the app launcher

Status:serviceRestored
Start Time:Tue Apr 29 19:36:00 2025
End Time:Thu May 1 18:09:00 2025
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:advisory
Last Updated:Fri May 2 14:42:06 2025
Root Cause:A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that caused inconsistent user provisioning detection, which resulted in affected users being incorrectly redirected to a fallback page.
Next Update:N/A

Details

Time:Fri May 2 14:40:45 2025
Description:Title: Some users may be unable to access Microsoft OneDrive through the app launcher
User impact: Users may have been unable to access OneDrive through the app launcher.
More info: Users reported that they could have bypassed the issue by accessing OneDrive content via direct link.
Final status: We've confirmed with a subset of affected users that the issue has been resolved following our reversion of the offending change.
Scope of impact: Some users may have been unable to access OneDrive through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
End time: Thursday, May 1, 2025, at 10:09 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that caused inconsistent user provisioning detection, which resulted in affected users being incorrectly redirected to a fallback page.
Next steps: - We're reviewing our routine update procedures so we can better identify similar issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
Time:Thu May 1 18:55:32 2025
Description:Title: Some users may be unable to access Microsoft OneDrive through the app launcher
User impact: Users may be unable to access OneDrive through the app launcher.
More info: Users have reported that they can bypass the issue by accessing OneDrive content via direct link.
Current status: We’ve observed recovery after reverting the offending change, and we're reaching out to a subset of affected users to validate that impact was fully remediated.
Scope of impact: Some users may be unable to access OneDrive through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page.
Next update by: Friday, May 2, 2025, at 8:30 PM UTC
Time:Thu May 1 17:55:40 2025
Description:Title: Some users may be unable to access OneDrive for Business through the app launcher
User impact: Users may be unable to access OneDrive for Business through the app launcher.
More info: Users have reported that they can bypass the issue by accessing OneDrive for Business content via direct link.
Current status: We identified that a recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page. To remediate this, we’re reverting the offending change and monitoring the service to ensure successful remediation.
Scope of impact: Some users may be unable to access OneDrive for Business through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page.
Next update by: Friday, May 2, 2025, at 12:00 AM UTC
Time:Thu May 1 15:40:12 2025
Description:Title: Some users may be unable to access OneDrive for Business through the app launcher
User impact: Users may be unable to access OneDrive for Business through the app launcher.
More info: Users have reported that they can bypass the issue by accessing OneDrive for Business content via direct link.
Current status: We're continuing to review the provided traces and are also reproducing the issue internally to gather additional diagnostics that will support our investigation.
Scope of impact: Some users may be unable to access OneDrive for Business through the app launcher.
Next update by: Thursday, May 1, 2025, at 10:00 PM UTC
Time:Thu May 1 14:35:46 2025
Description:Title: Some users may be unable to access OneDrive for Business through the app launcher
User impact: Users may be unable to access OneDrive for Business through the app launcher.
More info: Users have reported that they can bypass the issue by accessing OneDrive for Business content via direct link.
Current status: We've received fiddler network traces capturing the reproduced impact from affected users and are reviewing them to isolate the source of the problem and determine appropriate remediation actions.
Scope of impact: Some users may be unable to access OneDrive for Business through the app launcher.
Next update by: Thursday, May 1, 2025, at 8:00 PM UTC
Time:Thu May 1 13:00:51 2025
Description:Title: Some users may be unable to access OneDrive for Business through the app launcher
User impact: Users may be unable to access OneDrive for Business through the app launcher.
More info: Users have reported that they can bypass the issue by accessing OneDrive for Business content via direct link.
Current status: We're unable to reproduce the problem and our review of service data hasn't successfully pinpointed the reported failures. We request that impacted users provide the steps to reproduce the problem and a network trace that captures the issue to assist with our investigation into the problem. We'll also continue our attempts to reproduce the issue within our environment to collect the necessary data to proceed with this investigation.
Scope of impact: Some users may be unable to access OneDrive for Business through the app launcher.
Next update by: Friday, May 2, 2025, at 6:00 PM UTC

SP1066091 - Some users may be unable to access SharePoint Online through the app launcher

Status:serviceRestored
Start Time:Tue Apr 29 19:36:00 2025
End Time:Thu May 1 18:09:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Fri May 2 14:41:53 2025
Root Cause:A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that caused inconsistent user provisioning detection, which resulted in affected users being incorrectly redirected to a fallback page.
Next Update:N/A

Details

Time:Fri May 2 14:40:18 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may have been unable to access SharePoint Online through the app launcher.
More info: Users reported that they could have bypassed the issue by accessing SharePoint Online sites via direct link.
Final status: We've confirmed with a subset of affected users that the issue has been resolved following our reversion of the offending change.
Scope of impact: Some users may have been unable to access SharePoint Online through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
End time: Thursday, May 1, 2025, at 10:09 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that caused inconsistent user provisioning detection, which resulted in affected users being incorrectly redirected to a fallback page.
Next steps: - We're reviewing our routine update procedures so we can better identify similar issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
Time:Thu May 1 18:56:21 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may be unable to access SharePoint Online through the app launcher.
More info: Users have reported that they can bypass the issue by accessing SharePoint Online sites via direct link.
Current status: We’ve observed recovery after reverting the offending change, and we're reaching out to a subset of affected users to validate that impact was fully remediated.
Scope of impact: Some users may be unable to access SharePoint Online through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page.
Next update by: Friday, May 2, 2025, at 8:30 PM UTC
Time:Thu May 1 17:54:31 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may be unable to access SharePoint Online through the app launcher.
More info: Users have reported that they can bypass the issue by accessing SharePoint Online sites via direct link.
Current status: We identified that a recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page. To remediate this, we’re reverting the offending change and monitoring the service to ensure successful remediation.
Scope of impact: Some users may be unable to access SharePoint Online through the app launcher.
Start time: Tuesday, April 29, 2025, at 11:36 PM UTC
Root cause: A recent routine update to a portion of the Microsoft 365 navigation service introduced an issue that causes inconsistent user provisioning detection, resulting in affected users being incorrectly redirected to a fallback page.
Next update by: Friday, May 2, 2025, at 12:00 AM UTC
Time:Thu May 1 15:40:02 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may be unable to access SharePoint Online through the app launcher.
More info: Users have reported that they can bypass the issue by accessing SharePoint Online sites via direct link.
Current status: We're continuing to review the provided traces and are also reproducing the issue internally to gather additional diagnostics that will support our investigation.
Scope of impact: Some users may be unable to access SharePoint Online through the app launcher.
Next update by: Thursday, May 1, 2025, at 10:00 PM UTC
Time:Thu May 1 14:35:33 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may be unable to access SharePoint Online through the app launcher.
More info: Users have reported that they can bypass the issue by accessing SharePoint Online sites via direct link.
Current status: We've received fiddler network traces capturing the reproduced impact from affected users and are reviewing them to isolate the source of the problem and determine appropriate remediation actions.
Scope of impact: Some users may be unable to access SharePoint Online through the app launcher.
Next update by: Thursday, May 1, 2025, at 8:00 PM UTC
Time:Thu May 1 11:48:00 2025
Description:Title: Some users may be unable to access SharePoint Online through the app launcher
User impact: Users may be unable to access SharePoint Online through the app launcher.
More info: Users have reported that they can bypass the issue by accessing SharePoint Online sites via direct link.
Current status: We're unable to reproduce the problem and our review of service data hasn't successfully pinpointed the reported failures. We request that impacted users provide the steps to reproduce the problem and a network trace that captures the issue to assist with our investigation into the problem. We'll also continue our attempts to reproduce the issue within our environment to collect the necessary data to proceed with this investigation.
Scope of impact: Some users may be unable to access SharePoint Online through the app launcher.
Next update by: Friday, May 2, 2025, at 6:00 PM UTC
Time:Thu May 1 11:10:04 2025
Description:Title: Possible delays or problems when accessing SharePoint Online
User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

EX1064599 - Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined

Status:serviceRestored
Start Time:Fri Apr 25 20:00:00 2025
End Time:Thu May 1 12:00:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Thu May 1 16:31:42 2025
Root Cause:Our ML processes, which safeguard Exchange Online against risky email messages, was incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which was resulting in impact.
Next Update:N/A

Details

Time:Thu May 1 16:31:42 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may have been incorrectly marked as spam and quarantined.
More info: While we focused on remediation, users and admins may have been able to create allow rules to prevent email messages from Gmail senders from going to the junk folder.
Final status: After a period of monitoring, we've confirmed through our service health telemetry that the completion of reverting to the previous ML model has successfully remediated impact.
Scope of impact: Some users that were expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may have been affected by this issue.
Start time: Saturday, April 26, 2025, at 12:00 AM UTC
End time: Thursday, May 1, 2025, at 4:00 PM UTC
Root cause: Our ML processes, which safeguard Exchange Online against risky email messages, was incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which was resulting in impact.
Next steps: - We're continuing to investigate opportunities to improve our ML detection process to reduce false positive detections and prevent similar future impact.
This is the final update for the event.
Time:Thu May 1 14:01:58 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
More info: While we're focused on remediation, users and admins may be able to create allow rules to prevent email messages from Gmail senders from going to the junk folder.
Current status: We’ve confirmed that we’re seeing the expected improvements to service telemetry after reverting the previous ML model and we’re continuing to monitor the mitigation to ensure the issue is no longer occurring.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Start time: Saturday, April 26, 2025, at 12:00 AM UTC
Root cause: Our ML processes, which safeguard Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Thursday, May 1, 2025, at 10:00 PM UTC
Time:Wed Apr 30 22:34:33 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
More info: While we're focused on remediation, users and admins may be able to create allow rules to prevent email messages from Gmail senders from going to the junk folder.
Current status: We reverted to our previous ML model; however, some impact persists. We've initiated deployment of an additional ML fix to update the data set for identifying spam, which we anticipate will remediate the remaining impact. Once the deployment completes, we'll monitor our telemetry to ensure the email messages are no longer marked as spam.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Start time: Saturday, April 26, 2025, at 12:00 AM UTC
Root cause: Our ML processes, which safeguard Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Thursday, May 1, 2025, at 6:30 PM UTC
Time:Wed Apr 30 18:22:51 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We're reverting to our previous ML model, and we're monitoring for mitigation as we rollback the model for all users. We aim to provide a timeline to mitigation as one becomes available.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Start time: Saturday, April 26, 2025, at 12:00 AM UTC
Root cause: Our ML model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Thursday, May 1, 2025, at 3:00 AM UTC
Time:Wed Apr 30 13:47:21 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We're working to batch release additional email messages incorrectly marked as spam that were provided by affected, which will assist with mitigating the impact while we work to understand why the additional messages were incorrectly quarantined.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Start time: Tuesday, April 29, 2025, at 5:23 AM UTC
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Thursday, May 1, 2025, at 12:00 AM UTC
Time:Wed Apr 30 06:18:55 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We've received feedback indicating that the issue with the provided email messages has been resolved. However, additional email messages have been marked as spam, and we are currently reviewing them to understand why they are quarantined.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Wednesday, April 30, 2025, at 6:30 PM UTC
Time:Wed Apr 30 00:11:39 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We’ve applied a targeted fix to the ML model which we anticipate has remediated impact, and we're reaching out to some affected users to confirm that the issue is resolved, and no additional actions will be required.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Wednesday, April 30, 2025, at 11:30 AM UTC
Time:Tue Apr 29 09:53:34 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We're continuing to develop a fix to remediate impact for affected users.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Wednesday, April 30, 2025, at 5:30 AM UTC
Time:Tue Apr 29 07:54:43 2025
Description:Title: Some users’ inbound Gmail email messages are being incorrectly marked as spam and quarantined
User impact: Users’ inbound Gmail email messages are being incorrectly marked as spam and quarantined.
Current status: We've identified that our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact. We're working on a fix to address the issue to resolve impact.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, is incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which is resulting in impact.
Next update by: Tuesday, April 29, 2025, at 2:00 PM UTC
Time:Tue Apr 29 05:55:43 2025
Description:Title: Some users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined
User Impact: Users’ inbound email messages sent from Gmail accounts may be incorrectly marked as spam and quarantined.
Current status: We’re reviewing log data provided by some affected users to determine our next troubleshooting steps.
Scope of impact: Some users that are expecting to receive email messages sent from Gmail domains in their Exchange Online inbox may be affected by this issue.
Next update by: Tuesday, April 29, 2025, at 12:00 PM UTC

EX1064611 - Some users may be unable to access calendar details in Exchange Online for meeting room devices

Status:serviceRestored
Start Time:Thu Apr 24 14:30:00 2025
End Time:Thu May 1 13:30:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Thu May 1 15:04:39 2025
Root Cause:A configuration issue introduced in a recent service update was causing impact to occur.
Next Update:N/A

Details

Time:Thu May 1 15:04:39 2025
Description:Title: Some users may be unable to access calendar details in Exchange Online for meeting room devices
User impact: Users may have been unable to access calendar details in Exchange Online for meeting room devices.
Final status: After a period of monitoring error rates associated with impact, we've validated that the rollback of the offending configuration issue has remediated impact and users can access calendar details in Exchange Online for meeting room devices.
Scope of impact: Some users attempting to access calendar details in Exchange Online for meeting room devices may have been impacted.
Start time: Thursday, April 24, 2025, at 6:30 PM UTC
End time: Thursday, May 1, 2025, at 5:30 PM UTC
Root cause: A configuration issue introduced in a recent service update was causing impact to occur.
Next steps: - We're evaluating and analyzing further the offending configuration change to better understand why potential impact wasn't caught during the update testing and validation phase. This will help to ensure similar impact does not occur in future and to continue our ongoing efforts to improve the resiliency of our service for all Exchange Online users.
This is the final update for the event.
Time:Wed Apr 30 14:17:36 2025
Description:Title: Some users may be unable to access calendar details in Exchange Online for meeting room devices
User impact: Users may be unable to access calendar details in Exchange Online for meeting room devices.
Current status: We're continuing to monitor and ensure errors associated with impact continue to decrease as expected. As this progresses, some users may experience relief. We expect that errors will be completely resolved by our next scheduled update, remediating impact for all users.
Scope of impact: Some users attempting to access calendar details in Exchange Online for meeting room devices may be impacted.
Start time: Thursday, April 24, 2025, at 6:30 PM UTC
Root cause: A configuration issue introduced in a recent service update is causing impact to occur.
Next update by: Thursday, May 1, 2025, at 8:00 PM UTC
Time:Wed Apr 30 08:17:05 2025
Description:Title: Some users may be unable to access calendar details in Exchange Online for meeting room devices
User impact: Users may be unable to access calendar details in Exchange Online for meeting room devices.
Current status: We've observed a significant drop in errors associated with the meeting calendar access issue following the revert of the service update. We're conducting an additional monitoring period to ensure impact to end users is entirely remediated.
Scope of impact: Some users attempting to access calendar details in Exchange Online for meeting room devices may be impacted.
Start time: Thursday, April 24, 2025, at 6:30 PM UTC
Root cause: A configuration issue introduced in a recent service update is causing impact to occur.
Next update by: Wednesday, April 30, 2025, at 8:00 PM UTC
Time:Tue Apr 29 13:30:59 2025
Description:Title: Some users may be unable to access calendar details in Exchange Online for meeting room devices
User impact: Users may be unable to access calendar details in Exchange Online for meeting room devices.
Current status: We've reverted the service update containing the impacting configuration change and we're monitoring service health telemetry to ensure the changes propagate. We anticipate the service will be fully recovered by our next scheduled communications update.
Scope of impact: Some users attempting to access calendar details in Exchange Online for meeting room devices may be impacted.
Start time: Thursday, April 24, 2025, at 6:30 PM UTC
Estimated time to resolve: We anticipate the changes will have saturated and the service recovered by Wednesday, April 30, 2025, at 1:00 PM UTC.
Root cause: A configuration issue introduced in a recent service update is causing impact to occur.
Next update by: Wednesday, April 30, 2025, at 1:00 PM UTC
Time:Tue Apr 29 06:25:28 2025
Description:Title: Some users may receive errors when accessing calendar details in Exchange Online for meeting room devices
User impact: Users may receive errors when accessing calendar details in Exchange Online for meeting room devices
Current status: We've identified that a configuration issue introduced in a recent service update is causing impact to occur. We're reverting the configuration change to mitigate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to access calendar details in Exchange Online for meeting room devices may be impacted.
Root cause: A configuration issue introduced in a recent service update is causing impact to occur.
Next update by: Tuesday, April 29, 2025, at 6:30 PM UTC

MO941162 - Users may be unable to access or use some Microsoft 365 services and features

Status:postIncidentReviewPublished
Start Time:Sun Nov 24 20:20:00 2024
End Time:Tue Nov 26 06:00:00 2024
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Apr 30 13:51:07 2025
Root Cause:Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and affected servers' processing capabilities, which led to impact. More details is provided within the Post-Incident Report.
Next Update:N/A

Details

Time:Wed Apr 30 13:51:07 2025
Description:A post-incident report has been published.
Time:Mon Mar 31 10:47:12 2025
Description:A post-incident report has been published.
Time:Fri Feb 28 16:02:19 2025
Description:A post-incident report has been published.
Time:Fri Jan 31 14:22:22 2025
Description:A post-incident report has been published.
Time:Tue Dec 31 13:22:31 2024
Description:A post-incident report has been published.
Time:Tue Dec 3 16:50:02 2024
Description:A post-incident report has been published.
Time:Mon Dec 2 13:33:40 2024
Description:A post-incident report has been published.
Time:Wed Nov 27 20:11:12 2024
Description:A post-incident report has been published.
Time:Tue Nov 26 14:51:32 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact scenarios were as follows:
Exchange Online - Users may have been unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may have experienced mail transport delays.
Microsoft Teams - Users may have been unable to create or update Virtual Events, including webinars and Town Halls. - Users may have been unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users may have been unable to create chat, add users and create or edited meetings. - Users may have been unable to create or modify new teams and channels. - Users may have been unable to update presence. - Users may have been unable to use the search function. - Users may not have seen an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may have been unable to access the Purview Portal, or Purview Solutions. - Users may have experienced delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may have been unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may have been unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may have been unable to use the search feature.
Microsoft Defender for Office365 and the XDR portal - Users may have been unable to create simulations, simulation payloads or end user notifications. - Users may have experienced issues with delivery for end user notifications and simulation messages. - Some users may have experienced failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may have experienced issues with viewing simulation reports, and content. - Users may have received a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may have been unable to Print via Universal Print. - Users may have been unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may have been unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may have experienced errors when running flows that utilize cloud connectors. Microsoft Bookings - Users may have been unable to access their bookings.
Microsoft Viva Engage - Users may have been unable to load topics in feeds and threads. - Users may have seen searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not have shown user names. - Users may not have been able to load their home feeds.
Microsoft Copilot - Users may have been unable to use the personal Copilot panel in meetings and post meetings. - Users may have been unable to see historic Copilot conversation history in meetings and post meetings. - Users may have been unable to load Copilot experiences within the Viva Engage service. - Users may have been unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may have received an apology or "at capacity" message.
Final Status: After a period of extended monitoring, we’ve confirmed through customer reports and service health telemetry that the issue is resolved.
Scope of impact: This issue could have impacted any user hosted globally; however, users experienced varying degrees of impact depending on how they were routed through the affected infrastructure and what action they were trying to perform. Impacted users who attempted to use the functionalities outlined in the More info section of this communication may have been affected by this event
Start time: Monday, November 25, 2024, at 1:20 AM UTC
End time: Tuesday, November 26, 2024, at 11:00 AM UTC
Root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and affected servers' processing capabilities, which led to impact. More details is provided within the Post-Incident Report.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The fifth update was provided on April 30, 2025. The next update will be provided by May 30, 2025.
Time:Tue Nov 26 12:57:25 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re continuing to conduct additional optimizations to further improve service availability, which remains in a healthy state. We're monitoring telemetry closely while this work progresses to ensure service availability is fully restored.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 8:00 PM UTC
Time:Tue Nov 26 10:58:10 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re conducting additional optimizations to further improve service availability, which remains healthy. We're closing in on a full mitigation to address any remaining impact and we're closely monitoring telemetry to ensure this trend continues.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 6:00 PM UTC
Time:Tue Nov 26 07:53:55 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re continuing our period of monitoring service telemetry, which shows the service availability has remained healthy.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 4:00 PM UTC
Time:Tue Nov 26 05:59:36 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: From monitoring service telemetry, most users should now experience relief. We’ve completed our optimizations and we're continuing our period of extended monitoring to ensure the availability remains stable.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 1:00 PM UTC
Time:Tue Nov 26 05:02:46 2024
Description:While we continue our period of extended monitoring, the availability of the Outlook on the Web service has reached expected availability levels. We’re continuing to optimize the environment to address the remaining impact.
This quick update is designed to give the latest information on this issue.
Time:Tue Nov 26 04:03:46 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We're still addressing the remaining impact to the Outlook on the web service that is affecting some users. We’ve applied mitigation actions to reduce the mail queues and we’re continuing the extended period of monitoring to ensure stability continues.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 11:00 AM UTC
Time:Tue Nov 26 03:04:35 2024
Description:We’ve isolated the cause of mail queue delays and have restarted the affected infrastructure to drain stalled queues. We’ll remain in an extended monitoring phase until this draining is completed and we can consider the incident fully recovered.
This quick update is designed to give the latest information on this issue.
Time:Tue Nov 26 00:04:19 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We're continuing to address lingering impact to the Outlook on the web service that is still affecting some users. In parallel, we're investigating some mail queuing delays that is resulting in mail taking longer than expected to be delivered. Due to the impact of this incident, we will enter a period of extended monitoring prior to declaring this issue resolved.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 9:00 AM UTC
Time:Mon Nov 25 23:32:26 2024
Description:Impact to core services have been restored with the exception of Outlook on the web, which we’ll continue to monitor and actively troubleshoot until full recovery.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 22:31:02 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We’ve successfully restored functionality for all previously impacted services and users with the exception of Outlook on the web, which is showing prolonged impact for a small number of users. We’ll continue carefully monitoring the service health and focus on troubleshooting this persisting impact to fully recover for the remaining affected users. We'll provide a new timeline within the next update.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 5:00 AM UTC
Time:Mon Nov 25 21:10:49 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experience issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: Our monitoring indicates that a large portion of affected users and services are seeing recovery following our mitigation efforts. We're working on addressing the lingering regions that are still seeing small impact to fully restore service availability, which we still expect to complete by Tuesday, November 26, 2024, at 3:00 AM UTC.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Estimated time to resolve: We estimate full recovery by Tuesday, November 26, 2024, at 3:00 AM UTC.
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 3:30 AM UTC
Time:Mon Nov 25 19:01:40 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels. - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature.
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: The service is continuing to incrementally recover. We're forecasting that impact will be fully remediated by Tuesday, November 26, 2024, at 3:00 AM UTC, though we're closely monitoring our progress and will provide an updated timeline should the estimate change.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Estimated time to resolve: We estimate full recovery by Tuesday, November 26, 2024, at 3:00 AM UTC.
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 2:00 AM UTC
Time:Mon Nov 25 17:09:45 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels within - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature within
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We identified a change in the environment that resulted in an influx in request retries routed through affected servers. Our optimizations, which enhanced the infrastructure's processing capabilities, continue to provide incremental relief. We're monitoring the service and continuing our work to perform any follow-up actions or opening additional workstreams needed to fully resolve the problem.
We understand the significant impact of this event to your organization, we're treating this issue with the highest priority, and we're working to provide relief as soon as possible.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change resulted in a portion of infrastructure not operating as expected.
Next update by: Tuesday, November 26, 2024, at 12:00 AM UTC
Time:Mon Nov 25 15:25:12 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels within - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature within
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Viva Engage - Users may be unable to load topics in feeds and threads. - Users may see searches or autocomplete fail for topic experiences. - Users’ Microsoft Teams Q&A experiences may not show user names. - Users may not be able to load their home feeds.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings. - Users may not be able to load Copilot experiences within the Viva Engage service. - Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: Services are showing significant signs of restoration following our infrastructure optimizations to redistribute traffic and restart affected servers, upwards of 90 percent recovery as we continue to increase processing capability. We're continuing to perform appropriate optimizations on the subset of remaining affected machines to resolve the issue for all users.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 10:00 PM UTC
Time:Mon Nov 25 14:52:51 2024
Description:We're continuing to redirect traffic and apply targeted remediation to impacted servers. We've observed initially positive results in some areas, and we're monitoring service health closely as our mitigation workstreams continue in parallel.
We understand the significant impact of this event to your organization, we're treating this issue with the highest priority, and we're working to provide relief as soon as possible.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 14:15:19 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels within - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature within
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: Our mitigative actions haven't provided relief as expected, and a portion of infrastructure remains in an unhealthy state. We determined that some of the targeted server restarts did not succeed due to processing issues, which are under investigation. We’re currently focused on spreading traffic to healthy infrastructure, and we're seeing some recovery.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 9:00 PM UTC
Time:Mon Nov 25 12:37:21 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online - Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS) - Users may experience mail transport delays.
Microsoft Teams - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric - Users may be unable to export content or set and view labels within - Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online - Users may be unable to use the search feature within
Microsoft Defender for Office365 - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop - Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings - Users may be unable to access their bookings.
Microsoft Copilot - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: We're continuing to reroute traffic to alternate infrastructure and have reinitiated targeted server restarts to ensure the fix takes effect as expected. We're monitoring to confirm the restarts proceed successfully. We don't yet have an estimated time to resolution; however, we'll provide one as soon as it becomes available.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 7:00 PM UTC
Time:Mon Nov 25 11:44:41 2024
Description:We're rerouting traffic to alternate infrastructure to expedite mitigation. In parallel, we're resolving complications leading to the delays in targeted server restarts.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 11:15:43 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams: - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview: - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365: - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content. - Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Users leveraging Universal Print may experience the following issues: - Users may be unable to Print via Universal Print. - Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade. - Users may be unable to Register Printers via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Users may be unable to use some Microsoft Copilot features including: - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: The fix which is addressing impact is continuing to deploy and has now reached 98 percent of the affected environment. Regarding recovery, we've encountered delays in our targeted restarts; however, we're identifying alternative options to expedite recovery of the affected infrastructure.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 5:30 PM UTC
Time:Mon Nov 25 11:02:35 2024
Description:The patch has deployed 90 percent, and according to telemetry, service availability is recovering. An estimated time to completion of the fix is not yet available. Targeted server restarts are underway to address routing service issues, with priority on customers who are currently in business hours or beginning their business day.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 09:27:54 2024
Description:We’re monitoring the progress of the fix, which has been deployed to approximately 60% of the affected environments. We’re continuing our manual restarts on the remaining impacted machines.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 08:58:32 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams: - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview: - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365. - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center. - Users may experiences issues with viewing simulation reports, and content.
Users may also be unable to print via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Users may be unable to use some Microsoft Copilot features including: - Users are unable to use the personal Copilot panel in meetings and post meetings. - Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: We’ve started to deploy the fix which is currently progressing through the affected environment. While this progresses, we’re beginning manual restarts on a subset of machines that are in an unhealthy state.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 4:00 PM UTC
Time:Mon Nov 25 08:30:08 2024
Description:We've isolated the root cause and have developed a patch, which we're testing on a subset of components before full deployment. We're making sure that once we deploy the script, we're able to ensure a full recovery.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 06:50:56 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams: - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview: - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365. - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Users may experiences issues with viewing simulation reports, and content. - Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
Users may also be unable to print via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Current status: We’ve identified a recent change which we believe has resulted in impact. We’ve begun to revert the change and are investigating what additional actions are required to mitigate the issue.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 2:00 PM UTC
Time:Mon Nov 25 05:35:21 2024
Description:Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams: - Users are unable to create or update Virtual Events, including webinars and Town Halls. - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. - Users are unable to create or modify new teams and channels. - Users may be unable to update presence. - Users may be unable to use the search function. - Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview: - Users may be unable to access the Purview Portal, or Purview Solutions. - Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365. - Users may be unable to create simulations, simulation payloads or end user notifications. - Users may experience issues with delivery for end user notifications and simulation messages - Users may experiences issues with viewing simulation reports, and content.
Current status: We’ve updated the More Info section to include a list of impacted services and scenarios. We’re continuing to investigate recent changes, service telemetry and the failure paths to determine the root cause of impact.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 12:00 PM UTC
Time:Mon Nov 25 03:54:09 2024
Description:Title: Users unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: While we’re continuing the restarts to improve service availability, we’re thoroughly analyzing recent changes and the specific failure path to determine the next steps required to resolve the issue.
Scope of impact: Some users may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 11:00 AM UTC
Time:Mon Nov 25 03:18:34 2024
Description:We are systematically restarting the affected components while continuing our investigation into the cause of the errors.
This quick update is designed to give the latest information on this issue.
Time:Mon Nov 25 02:21:19 2024
Description:Title: Users unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: Our ongoing service monitoring has determined that the issue is not limited to users in Asia Pacific, and instead that all users worldwide could be intermittently impacted. As such, we're expanding our restart efforts to ensure the issue is resolved for all users.
Scope of impact: Some users may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 9:00 AM UTC
Time:Mon Nov 25 00:46:21 2024
Description:Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We're continuing to work to restart the small subset of machines which have previously failed to restart. We're also continuing to add additional capacity to the affected environment to mitigate impact as quickly as possible. At this time, we expect the majority of users will experience relief from impact as we work to address the remaining issues.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 8:00 AM UTC
Time:Sun Nov 24 23:56:48 2024
Description:Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We've identified a small subset of machines which are failing to restart, resulting in persisting impact. We're further investigating what is causing the restarts to fail to determine our next steps.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 6:00 AM UTC
Time:Sun Nov 24 23:18:21 2024
Description:In addition to the infrastructure restarts, we're also working to add additional capacity to the affected environment to further assist in our impact mitigation efforts.
This quick update is designed to give the latest information on this issue.
Time:Sun Nov 24 22:50:26 2024
Description:Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We've determined via our internal telemetry that the impact to Microsoft Teams calendars has self-recovered. To fully resolve the issue, we initiated restarts on affected infrastructure and are monitoring further to determine whether additional steps are required. We're also continuing our investigation into the root cause of this issue.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Next update by: Monday, November 25, 2024, at 5:00 AM UTC
Time:Sun Nov 24 22:29:51 2024
Description:While we continue to investigate the source of the issue, we're restarting affected machines in an attempt to mitigate the user impact.
This quick update is designed to give the latest information on this issue.
Time:Sun Nov 24 22:00:50 2024
Description:Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: Here are the service impact scenarios affected:
Exchange Online may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Current status: Our automated systems alerted us to an issue in which some users may be intermittently unable to access their mailboxes in Exchange Online using any connection method or their calendar functionality in Microsoft Teams. We're analyzing a portion of Exchange Online infrastructure responsible for accessing mailboxes to understand the root cause of the issue and determine our next troubleshooting steps.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempt to use their calendar in Microsoft Teams.
Next update by: Monday, November 25, 2024, at 4:00 AM UTC

MP1060037 - Admins may have been unable to ingest data via data connectors within Microsoft Purview

Status:serviceRestored
Start Time:Fri Mar 28 07:30:00 2025
End Time:Tue Apr 29 02:30:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Wed Apr 30 06:19:01 2025
Root Cause:A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality was causing impact to occur.
Next Update:N/A

Details

Time:Wed Apr 30 06:19:01 2025
Description:Title: Admins may have been unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may have been unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may have not seen data ingested into Microsoft Purview from already established data connectors. This will have resumed once the required fix was complete.
Final status: We can confirm after a period of monitoring that impact has successfully been resolved.
Scope of impact: Your organization was affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview were impacted.
Start time: Friday, March 28, 2025 at 11:30 AM UTC
End time: Tuesday, April 29, 2025 at 6:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality was causing impact to occur.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for this event.
Time:Mon Apr 28 06:22:12 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We've determined that the fix has not fully resolved the issue for some admins. We're working on developing a further fix to address the data ingestion issue to fully resolve impact.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Wednesday, April 30, 2025, at 10:30 AM UTC
Time:Fri Apr 25 07:28:38 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We've successfully carried out the final validations for our fix, and commenced the final deployment phase. We anticipate at this point that some users will no longer observe the issue, and while the deployment progresses more users will gradually experience relief. We will provide an approximate remediation time as part of our next scheduled update.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Monday, April 28, 2025, at 10:30 AM UTC
Time:Thu Apr 24 06:14:13 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We're carrying out additional validations before we reach the final deployment of our fix to the affected environment to ensure that the issue is resolved once it's applied to the affected environment. We expect the validations to be complete, and for the final stage of the fix deployment to commence, by the time of our next scheduled update.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Friday, April 25, 2025 at 11:30 AM UTC
Time:Thu Apr 24 04:33:16 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We're progressing with the deployment of our short term fix, and expect to be able to provide a completion time as part of our next update.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Thursday, April 24, 2025 at 10:30 AM UTC
Time:Wed Apr 23 04:26:01 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We're continuing to deploy the short term fix to unblock ingestion, and are also identifying a long term mitigation solution.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Thursday, April 24, 2025 at 8:30 AM UTC
Time:Tue Apr 22 07:20:48 2025
Description:Title: Admins may be unable to ingest data via data connectors within Microsoft Purview
User impact: Admins may be unable to ingest data via data connectors within Microsoft Purview.
More info: Admins may not see data ingested into Microsoft Purview from already established data connectors. This will resume once the required fix is complete.
Current status: We've identified that a recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur. We're deploying a short term fix to unblock ingestion, and impacted admins may find that messages are ingested as individual messages in user mailboxes rather than as conversation threads until our long-term fix is implemented.
Scope of impact: Your organization is affected by this event, and admins attempting to ingest data via data connectors within Microsoft Purview are impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality is causing impact to occur.
Next update by: Wednesday, April 23, 2025, at 8:30 AM UTC

MO1042853 - Users may be visiting legacy content at the MicrosoftStream.com domain

Status:investigationSuspended
Start Time:Thu Mar 27 19:16:15 2025
End Time:Wed Apr 30 02:00:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Wed Apr 30 02:20:01 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Apr 30 02:20:01 2025
Description:Title: Users may be visiting legacy content at the MicrosoftStream.com domain
User impact: Users may be visiting legacy content at the MicrosoftStream.com domain.
Final Status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
Time:Thu Mar 27 23:31:10 2025
Description:Title: Users may be visiting legacy content at the MicrosoftStream.com domain
User impact: Users may be visiting legacy content at the MicrosoftStream.com domain.
As we have communicated previously Microsoft Stream (Classic) was retired in 2024 and as of March 2025, MicrosoftStream.com address no longer redirects users to their videos. We have noticed that some of your users are still accessing this address.
Going forward, users who visit MicrosoftStream.com will be redirected to the new combined landing page for Clipchamp and Stream. This new platform offers enhanced features and a more integrated experience for video creation and management.
We encourage you to tell your users to update their bookmarks and explore the new Clipchamp/Stream landing page and take advantage of its improved functionalities.
This communication will expire in fourteen days and is scheduled to remain active for the full duration.

MO1065113 - Some users may be unable to sign in to the Microsoft Defender XDR portal

Status:serviceRestored
Start Time:Tue Apr 29 13:35:00 2025
End Time:Wed Apr 30 00:21:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Apr 30 00:54:40 2025
Root Cause:A recent update to the authentication system that enabled access to the Microsoft Defender XDR portal contained a configuration issue, which was leading to impact.
Next Update:N/A

Details

Time:Wed Apr 30 00:54:40 2025
Description:Title: Some users may be unable to sign in to the Microsoft Defender XDR portal
User impact: Users may have been unable to sign in to the Microsoft Defender XDR portal.
Final status: We've completed the rollback process and confirmed through telemetry, as well as a subset of affected users, that impact has been successfully remediated.
Scope of impact: Any user may have been impacted and may have been unable to sign in to the Microsoft Defender XDR portal.
Start time: Tuesday, April 29, 2025, at 5:35 PM UTC
End time: Wednesday, April 30, 2025, at 4:21 AM UTC
Root cause: A recent update to the authentication system that enabled access to the Microsoft Defender XDR portal contained a configuration issue, which was leading to impact.
Next steps: - We're reviewing our update and testing processes to identify changes we can make to better identify and prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Tue Apr 29 23:16:59 2025
Description:Title: Some users may be unable to sign in to the Microsoft Defender XDR portal
User impact: Users may be unable to sign in to the Microsoft Defender XDR portal.
Current status: We're continuing to monitor the rollback of the previous update as it progresses. We expect this will remediate impact once completed.
Scope of impact: Any user may be impacted and may be unable to sign in to the Microsoft Defender XDR portal.
Start time: Tuesday, April 29, 2025, at 5:35 PM UTC
Root cause: A recent update to the authentication system that enables access to the Microsoft Defender XDR portal contains a configuration issue which is leading to impact.
Next update by: Wednesday, April 30, 2025, at 5:30 AM UTC
Time:Tue Apr 29 22:10:13 2025
Description:Title: Some users may be unable to sign in to the Microsoft Defender XDR portal
User impact: Users may be unable to sign in to the Microsoft Defender XDR portal.
Current status: We've investigated the affected service infrastructure and determined a recent update to the authentication system that enables access to the Microsoft Defender XDR portal contains a code issue which is leading to impact. We've initiated a rollback of this update to remediate the impact and we're continuing to analyze the service health to see if any additional actions may be required.
Scope of impact: Any user may be impacted and may be unable to sign in to the Microsoft Defender XDR portal.
Root cause: A recent update to the authentication system that enables access to the Microsoft Defender XDR portal contains a code issue which is leading to impact.
Next update by: Wednesday, April 30, 2025, at 3:30 AM UTC
Time:Tue Apr 29 21:39:54 2025
Description:Title: Some users may be unable to sign in to the Microsoft Defender XDR portal and get stuck in a loop
User impact: Users may be unable to sign in to the Microsoft Defender XDR portal and get stuck in a loop.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.

PP1064945 - Excel Online (Business) connector actions are intermittently failing

Status:serviceRestored
Start Time:Tue Apr 29 14:14:00 2025
End Time:Tue Apr 29 19:40:00 2025
Service:Power Platform
Feature Group:Other
Classification:advisory
Last Updated:Tue Apr 29 20:27:00 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Apr 29 20:27:00 2025
Description:Title: Excel Online (Business) connector actions are intermittently failing
User impact: Excel Online (Business) connector actions were intermittently failing.
More info: The below actions were impacted by this issue. -Add a row into a table -List rows present in table
Final Status: We restarted the impacted node. Following this, we reviewed service diagnostics and confirmed that API calls are no longer timing out, restoring connector functionality.
This is the final update on the incident.
Preliminary Root Cause: A node utilized in API calls entered an unhealthy state, resulting in request timeouts and impact.
Next Steps: We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar issues in the future.
Time:Tue Apr 29 18:43:05 2025
Description:Title: Excel Online (Business) connector actions are intermittently failing
User impact: Excel Online (Business) connector actions are intermittently failing.
More info: Failures will occur and produce a 504 error.
Impacted actions: -Add a row into a table -List rows present in table
Current Status: We have identified that a node utilized in the impacted API calls has entered an unhealthy state, leading to impact. We are working to restart the impacted node in order to mitigate the issue.
Next Update: Wednesday, April 30, 2025, at 1:00 AM UTC
Time:Tue Apr 29 16:48:57 2025
Description:Title: Excel Online (Business) connector actions are intermittently failing
User impact: Excel Online (Business) connector actions are intermittently failing.
More info: Failures will occur and produce a 504 error.
Impacted actions: -Add a row into a table -List rows present in table
Current Status: After our investigation, we identified that API calls are experiencing timeouts, leading to failures. We are reviewing the infrastructure configuration for the impacted actions to identify the cause of these timeouts.
Next Update: Tuesday, April 29, 2025, at 11:00 PM UTC
Time:Tue Apr 29 16:23:13 2025
Description:Title: Excel Online (Business) connector actions are intermittently failing
User impact: Excel Online (Business) connector actions are intermittently failing.
More info: Failures will occur and produce a 504 error.
Impacted actions: -Add a row into a table -List rows present in table
Current Status: We are aware of an emerging issue where Excel Online (Business) connector actions are intermittently failing. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

PP1065000 - excelonlinebusiness connector flows and apps failing

Status:serviceRestored
Start Time:Tue Apr 29 13:57:13 2025
End Time:Tue Apr 29 20:23:17 2025
Service:Power Platform
Feature Group:Service and web access issues
Classification:incident
Last Updated:Tue Apr 29 20:23:18 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Apr 29 20:23:18 2025
Description:Title: excelonlinebusiness connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the excelonlinebusiness connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using excelonlinebusiness connectors has recovered.
Preliminary Root Cause: The external service used by the excelonlinebusiness connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
Time:Tue Apr 29 17:51:08 2025
Description:Title: excelonlinebusiness connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the excelonlinebusiness connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the excelonlinebusiness connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.

TM1064032 - Users may be unable to start some apps within private channels in Microsoft Teams

Status:serviceRestored
Start Time:Thu Apr 10 16:11:00 2025
End Time:Mon Apr 28 20:44:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Apr 29 13:54:21 2025
Root Cause:A recent update to the Microsoft Teams client code base responsible for facilitating app functionality in private channels introduced an error that prevented some apps from initiating, leading to impact.
Next Update:N/A

Details

Time:Tue Apr 29 13:54:21 2025
Description:Title: Users may be unable to start some apps within private channels in Microsoft Teams
User impact: Users may have been unable to start some apps within private channels in Microsoft Teams.
More info: This impact was limited to the Microsoft Teams desktop and web clients. Where possible, affected users could bypass the impact by accessing apps in private channels using the Microsoft Teams mobile app.
Final status: Following our reversion of the recent service update our internal service telemetry has validated that impact has been resolved. Users who continue to experience any problems when starting apps within Microsoft Teams private channels should confirm they have the most recent fixed version of Teams (25040319113).
Scope of impact: This issue affected users leveraging some apps within private channels in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
End time: Tuesday, April 29, 2025, at 12:44 AM UTC
Root cause: A recent update to the Microsoft Teams client code base responsible for facilitating app functionality in private channels introduced an error that prevented some apps from initiating, leading to impact.
Next steps: - We're further analyzing the offending service update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
Time:Mon Apr 28 14:00:06 2025
Description:Title: Users may be unable to start some apps within private channels in the Microsoft Teams desktop or web client
User impact: Users may be unable to start some apps within private channels in the Microsoft Teams desktop or web client.
More info: This impact is limited to the Microsoft Teams desktop and web clients. Where possible, affected users can bypass the impact by accessing apps in private channels using the Microsoft Teams mobile app.
Current status: Our investigation has determined that a recent update to the Microsoft Teams client code base responsible for facilitating app functionality in private channels introduced an error that's preventing some apps from initiating, leading to impact. We're reverting this update to repair the issue. We anticipate that the reversion will be complete in all impacted environments by Wednesday, April 30, 2025, and some users may experience early relief as the fix saturates their environment.
Scope of impact: Your organization is affected by this event, and users leveraging some apps within private channels in Microsoft Teams are impacted.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
Root cause: A recent update to the Microsoft Teams client code base responsible for facilitating app functionality in private channels introduced an error that's preventing some apps from initiating, leading to impact.
Next update by: Tuesday, April 29, 2025, at 7:00 PM UTC
Time:Mon Apr 28 13:31:12 2025
Description:Title: Users may be unable to start some apps within private channels in Microsoft Teams
User impact: Users may be unable to start some apps within private channels in Microsoft Teams.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1056704 - Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)

Status:serviceRestored
Start Time:Sun Apr 13 20:00:00 2025
End Time:Sun Apr 27 19:30:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Tue Apr 29 13:23:37 2025
Root Cause:A high number of app requests and retries to an API that facilitates Outlook (classic) and the EAC were resulting in the impact.
Next Update:N/A

Details

Time:Tue Apr 29 13:23:37 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may have been unable to run Outlook (classic) in online mode and admins may have been unable to utilize the EAC.
More info: Some users may have received the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins may have been returned a "503 Service Unavailable” error. This could potentially have impacted any EAC related operation, including but not limited to mailbox provisioning. Admins who could leverage PowerShell to complete these tasks could’ve done so to avoid this issue.
Final status: We’ve confirmed from service telemetry that this issue is no longer occurring after reducing the retry traffic, and we’ve determined that this issue is resolved.
Scope of impact: Any user who attempted to start Outlook (classic) in online mode or any admin utilizing the EAC may have been impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
End time: Sunday, April 27, 2025, at 11:30 PM UTC
Root cause: A high number of app requests and retries to an API that facilitates Outlook (classic) and the EAC were resulting in the impact.
Next steps: - We’re continuing our investigation to better understand the underlying cause of the higher-than-normal rate of app requests and retries on the affected API to prevent issues like this from occurring in the future.
This is the final update for the event.
Time:Mon Apr 28 14:41:54 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: After reducing retry traffic, our service monitoring telemetry provides that impact has been resolved. We're testing with affected users to fully validate impact remediation.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Root cause: A high number of app requests and retries to an API that facilitates Outlook (classic) and the EAC are resulting in the impact.
Next update by: Tuesday, April 29, 2025, at 6:00 PM UTC
Time:Mon Apr 28 05:16:05 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: We've successfully reduced the retry traffic and monitoring service telemetry to ensure that impact is remediated.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Root cause: A high app requests and retries to an API that facilitates Outlook (classic) and the EAC are resulting in the impact.
Next update by: Monday, April 28, 2025, at 7:00 PM UTC
Time:Sun Apr 27 06:56:52 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: We're continuing to work on manually reducing the retry traffic in conjunction with analyzing service health telemetry to ensure that our actions to disable the offending auto-scaling feature haven't had any adverse effects.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Monday, April 28, 2025, at 12:00 PM UTC
Time:Sun Apr 27 02:19:30 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: Our work to manually reduce the retry traffic continues. In tandem, we're analyzing service health telemetry to ensure that our actions to disable the offending auto-scaling feature haven't had any adverse effects. This process is providing valuable data as we plan our broader next steps in the effort to alleviate impact.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Sunday, April 27, 2025, at 12:00 PM UTC
Time:Sat Apr 26 14:20:04 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: While our efforts to manually reduce the retry traffic are ongoing, We've disabled the offending auto-scaling feature in a portion of the affected infrastructure. Our review of service health telemetry indicates this change has had a positive effect towards returning the service to expected functionality, and we're performing additional validations within the portion of affected infrastructure prior to broadly implementing this change to ensure it has no adverse effects.. We anticipate the validation process will be complete by our next scheduled communications update.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Sunday, April 27, 2025, at 7:30 AM UTC
Time:Fri Apr 25 21:55:18 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: Our previously mentioned change continues to saturate. In the interim, we’re manually reducing the retry traffic for affected environments to alleviate impact to the affected API and expedite mitigation.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Saturday, April 26, 2025, at 12:00 PM UTC
Time:Fri Apr 25 19:54:42 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: We’ve applied a change to a portion of impacted service infrastructure that’s generating high app requests and retries to the aforementioned API to reduce the number of requests and improve the overall health of the service. We’re monitoring as this change saturates throughout the affected infrastructure to ensure it completes and addresses impact.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Saturday, April 26, 2025, at 2:00 AM UTC
Time:Fri Apr 25 17:59:32 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable." Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: We suspect high app requests and retries to an API that facilitates Outlook (classic) and the EAC are resulting in the impact. While we continue our analysis of stack logs and investigation into the identified connectivity and latency issues to confirm our suspicion, we're reviewing potential options to reduce this traffic and provide relief.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Saturday, April 26, 2025, at 12:00 AM UTC
Time:Fri Apr 25 14:25:51 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable." Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: We're continuing our review of the stack logs in parallel with our investigation into the identified connectivity and latency issues in the provisioning handler calls to progress our investigation into the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Friday, April 25, 2025, at 10:00 PM UTC
Time:Fri Apr 25 10:29:24 2025
Description:Title: Users may be unable to run Outlook (classic) in online mode or utilize the Exchange admin center (EAC)
User impact: Users may be unable to run Outlook (classic) in online mode or utilize the EAC.
More info: Some users may receive the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the EAC, admins are returned a "503 Service Unavailable” error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who are able to leverage PowerShell to complete these tasks can do so to avoid this issue.
Current status: Our analysis of call stack logs related to the workload management module and suitability verifier in the directory layer is ongoing. We're analyzing these stack logs to identify a potential correlation in the data, to aid in identifying the root cause and help developing a mitigation plan. We're continuing to investigate connectivity issues and high latency in provisioning handler calls, and its impact on service performance.
Scope of impact: Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Friday, April 25, 2025, at 8:00 PM UTC
Time:Fri Apr 25 08:13:46 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: We’re continuing our review of call stack logs related to the workload management module and suitability verifier in the directory layer, to identify the root cause before formulating a plan for remediation. We're also analyzing connectivity issues and high latency in provisioning handler calls, and its impact on service performance.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Next update by: Friday, April 25, 2025, at 2:30 PM UTC
Time:Fri Apr 25 04:20:22 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: Our analysis into the source of the high latency and timeout errors on the section of Exchange Online infrastructure is progressing, but is taking longer than expected due to the complexity and scope of the issue.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Next update by: Friday, April 25, 2025, at 12:30 PM UTC
Time:Fri Apr 25 01:47:19 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: Our analysis into the source of the high latency and timeout errors on the portion of Exchange Online infrastructure continues and is taking longer than expected due to the complexity and scope of the issue.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Next update by: Friday, April 25, 2025, at 8:30 AM UTC
Time:Thu Apr 24 23:53:02 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: We're continuing to investigate the source of the high latency and timeout errors on a portion of Exchange Online infrastructure to help with isolating the root cause.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Next update by: Friday, April 25, 2025, at 6:00 AM UTC
Time:Thu Apr 24 21:49:25 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: We've identified high latency and timeout errors on a portion of Exchange Online infrastructure responsible for EAC and Outlook (classic) functionality. We're further investigating the source of the latency and timeout errors to help with the root cause investigation.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Next update by: Friday, April 25, 2025, at 4:00 AM UTC
Time:Thu Apr 24 19:53:01 2025
Description:Title: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the Exchange admin center (EAC)
User impact: Users may see a 503 error when starting Outlook (classic) in online mode or utilizing the EAC.
More info: Some users intermittently may be unable to start Outlook (classic) when in working online mode and encounter the following error: "HTTP 503 Service Unavailable."
Additionally, when attempting to complete operations in the Exchange admin center (EAC), admins are returned a "503 Service Unavailable” error.
Current status: We've amended the Title, User impact, and More info sections of this communication to more fully capture the affected scenarios. We're further analyzing a portion of Exchange Online infrastructure responsible for EAC and Outlook (classic) functionality to help with understanding the root cause. Additionally, we're investigating if a possible networking issue could be contributing to the "503 Service Unavailable" errors to help with the underlying investigation.
Scope of impact: Any user who attempts to start Outlook (classic) when working in online mode or utilize the EAC may be impacted by this event.
Next update by: Friday, April 25, 2025, at 2:00 AM UTC
Time:Thu Apr 24 07:25:14 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, admins are returned a 503 “Service Unavailable” error.
Current status: We're continuing to proceed with further troubleshooting to rule out potential sources of impact and inform our next steps. As previously mentioned, it may take some additional time before we can locate a path to resolution.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Friday, April 25, 2025, at 6:00 AM UTC
Time:Wed Apr 23 23:37:09 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, users are returned a 503 “Service Unavailable” error.
Current status: Our review of the latest collected data has been inconclusive. We're proceeding with further troubleshooting to rule out potential sources of impact and inform our next steps. Due to the complexity of the issue, it may take some additional time before we can identify a path to remediation.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 24, 2025, at 11:30 AM UTC
Time:Wed Apr 23 19:56:20 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations" When attempting to complete operations in the Exchange admin center, users are returned a 503 “Service Unavailable” error.
Current status: We've completed the previously mentioned configuration change to a subset of Exchange Online directory infrastructure to assist us in evaluating the impact to the admin API, and we're investigating the data collected from this change to isolate the root cause of the issue and identify a new path to remediation.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 24, 2025, at 4:00 AM UTC
Time:Wed Apr 23 18:11:04 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, users are returned a 503 “Service Unavailable” error.
Current status: We're implementing a configuration change in a subset of Exchange Online directory infrastructure to test for impact to the admin API and to help us determine if a recent update to assist with onboarding virtual assistant to the Exchange admin center resulted in impact.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 24, 2025, at 1:00 AM UTC
Time:Wed Apr 23 16:45:27 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, users are returned a 503 “Service Unavailable” error.
Current status: We're analyzing recent updates to a subset of directory infrastructure for Exchange Online to determine if any updates correlate with the returned 503 errors. This will help us to confirm a potential root cause and what steps we can take to resolve the issue.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Wednesday, April 23, 2025, at 11:00 PM UTC
Time:Wed Apr 23 13:17:46 2025
Description:Title: Admins may be unable to utilize the Exchange admin center and are returned a 503 error
User impact: Admins may be unable to utilize the Exchange admin center and are returned a 503 error.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, users are returned a 503 “Service Unavailable” error.
Current status: We've confirmed that all functions within the Exchange admin center could be impacted and we’ve updated the “Title”, “User impact” and “More info” sections of this communication to reflect our new understanding of the impact scenario. We’re analyzing Admin API failures on a subset of directory and authentication service infrastructure, along with recent updates pertaining to the Exchange admin center, to better understand why 503 errors are returned and what steps we can take to resolve the issue.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Wednesday, April 23, 2025, at 9:00 PM UTC
Time:Tue Apr 22 12:35:52 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We've determined that reverting the service update hasn't remedied the issue when managing mailboxes. We've isolated and are further analyzing a group of errors occurring on a subset of directory and authentication service infrastructure to help us confirm the source for this event, along with our next troubleshooting steps for remediating the impact.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Wednesday, April 23, 2025, at 5:30 PM UTC
Time:Fri Apr 18 16:22:20 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We've identified a recent change intended to provide optimizations to our logging capabilities introduced a code issue which resulted in latency on the affected infrastructure, resulting in impact when attempting to process admins actions when managing mailboxes in the Exchange admin center. We're developing a fix for this issue which will undergo testing and validation, after which we'll deploy our fix to the impact environment. We'll provide an estimated timeline for completion of the fix deployment with our next scheduled update.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Start time: Wednesday, April 2, 2025, at 4:29 AM UTC
Root cause: A recent change intended to provide optimizations to our logging capabilities introduced a code issue which resulted in latency on the affected infrastructure, resulting in impact when attempting to process admins actions when managing mailboxes in the Exchange admin center.
Next update by: Tuesday, April 22, 2025, at 5:30 PM UTC
Time:Fri Apr 18 14:20:09 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We suspect that a recent change may be responsible for impact. We're reviewing recent changes to identify if any may potentially be responsible for impact and determine our next steps.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Friday, April 18, 2025, at 8:30 PM UTC
Time:Fri Apr 18 04:46:33 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: Our investigation into understanding the source of the spike in service latency errors from the LDAP to determine the underlying root cause is ongoing.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Friday, April 18, 2025, at 6:30 PM UTC
Time:Fri Apr 18 00:04:12 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We're continuing with our investigation into understanding the source of the spike in service latency errors from the LDAP to determine the underlying root cause.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Friday, April 18, 2025, at 9:00 AM UTC
Time:Thu Apr 17 15:59:43 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We're continuing our investigation into the previously mentioned spike in service latency errors from the LDAP to isolate the root cause of impact and identify a path to remediation.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Friday, April 18, 2025, at 5:30 AM UTC
Time:Thu Apr 17 12:55:28 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We’re analyzing a spike in service latency errors from the Lightweight Directory Access Protocol (LDAP) that may point to a potential root cause and what steps we can take to resolve the issue.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 17, 2025, at 9:30 PM UTC
Time:Thu Apr 17 11:26:27 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We’re continuing to analyze HAR logs provided by affected users along with spikes in service processing errors to better understand the underlying root cause and what steps we can take to address the issue.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 17, 2025, at 5:30 PM UTC
Time:Thu Apr 17 09:35:50 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: Our investigation thus far into service-side logs has been inconclusive, we're analyzing HTTP Archive format (HAR) file logs provided by affected users to determine our next troubleshooting steps.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 17, 2025, at 3:30 PM UTC
Time:Thu Apr 17 07:31:21 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We've applied performance optimization actions and restarted the aforementioned section of infrastructure, however, telemetry indicates this didn't provide the expected relief and mitigation. We're continuing our investigation into service-side logs to isolate the source of the previously mentioned leak, in order to develop an effective remediation plan.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 17, 2025, at 1:30 PM UTC
Time:Wed Apr 16 14:11:56 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
Current status: We've confirmed that packet loss is occurring within the call IDs provided and are analyzing them to determine the source and cause of the issue.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Thursday, April 17, 2025, at 11:30 AM UTC
Time:Wed Apr 16 12:17:00 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: Our analysis of the provided HAR captures has identified that a portion of infrastructure that facilitates Exchange admin center mailbox management is over-encumbered due to an errant process leak, resulting in impact. We're expanding our investigation to include service-side logs to isolate the source of the leak and develop a remediation strategy.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Wednesday, April 16, 2025, at 6:30 PM UTC
Time:Wed Apr 16 11:11:15 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We're continuing our analysis of provided HAR captures to better understand the impact scenario and determine our next steps.
Scope of impact: Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Next update by: Wednesday, April 16, 2025, at 4:30 PM UTC
Time:Wed Apr 16 10:50:50 2025
Description:Title: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message
User impact: Admins may be unable to manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1063967 - North America admins may encounter delays with Microsoft Teams usage activity report in the Microsoft 365 admin center

Status:serviceRestored
Start Time:Sun Apr 27 20:00:00 2025
End Time:Mon Apr 28 20:00:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Tue Apr 29 11:12:23 2025
Root Cause:A portion of infrastructure that facilitates the generation of Microsoft Teams usage activity reports wasn't processing requests as efficiently as expected, resulting in impact.
Next Update:N/A

Details

Time:Tue Apr 29 11:12:23 2025
Description:Title: North America admins may encounter delays with Microsoft Teams usage activity report in the Microsoft 365 admin center
User impact: Admins may have encountered delays with the Microsoft Teams usage activity report in the Microsoft 365 admin center.
Final status: We've completed processing the backlog of events and validated that this issue has been remediated using service telemetry.
Scope of impact: Impact was specific to a subset of admins hosted in the North America region accessing the Microsoft Teams usage activity report within the Microsoft 365 admin center.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
End time: Tuesday, April 29, 2025, at 12:00 AM UTC
Root cause: A portion of infrastructure that facilitates the generation of Microsoft Teams usage activity reports wasn't processing requests as efficiently as expected, resulting in impact.
Next steps: - We're continuing our analysis of the impacting change to better identify and prevent similar issues in the future.
This is the final update for the event.
Time:Mon Apr 28 12:52:02 2025
Description:Title: North America admins may encounter delays with Microsoft Teams usage activity report in the Microsoft 365 admin center
User impact: Admins may encounter delays with the Microsoft Teams usage activity report in the Microsoft 365 admin center.
Current status: Our monitoring has identified that a portion of infrastructure that facilitates the generation of Microsoft Teams usage activity reports wasn't processing requests as efficiently as expected. We've analyzed service telemetry and determined that some requests started to queue, resulting in impact. We've cleared affected jobs to remediate impact and are monitoring as the backlog of events are processed.
Scope of impact: Impact is specific to a subset of admins hosted in the North America region accessing the Microsoft Teams usage activity report within the Microsoft 365 admin center.
Start time: Monday, April 28, 2025, at 12:00 AM UTC
Estimated time to resolve: We expect the backlog of events to complete processing by 5:00 AM UTC on Wednesday, April 30, 2025.
Root cause: A portion of infrastructure that facilitates the generation of Microsoft Teams usage activity reports wasn't processing requests as efficiently as expected, resulting in impact.
Next update by: Wednesday, April 30, 2025, at 5:00 AM UTC
Time:Mon Apr 28 12:16:50 2025
Description:Title: North America admins may encounter delays with Microsoft Teams usage activity report in the Microsoft 365 admin center
User impact: Admins may encounter delays with the Microsoft Teams usage activity report in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1063763 - Some users may have encountered delays or failures searching in Outlook on the web

Status:serviceRestored
Start Time:Tue Apr 8 02:00:00 2025
End Time:Tue Apr 29 05:10:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Tue Apr 29 09:54:52 2025
Root Cause:Components of infrastructure, responsible for processing users search requests, were performing below acceptable performance thresholds and causing impact.
Next Update:N/A

Details

Time:Tue Apr 29 09:06:28 2025
Description:Title: Some users may have encountered delays or failures searching in Outlook on the web
User impact: Users may have encountered delays or failures searching in Outlook on the web.
More info: Users may have also seen issues searching in SharePoint Online.
Final status: We've confirmed after monitoring the telemetry for a period of time that impact has been fully remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to search.
Start time: Tuesday, April 8, 2025, at 6:00 AM UTC
End time: Tuesday, April 29, 2025, at 9:10 AM UTC
Root cause: Components of infrastructure, responsible for processing users search requests, were performing below acceptable performance thresholds and causing impact.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Tue Apr 29 07:29:17 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: We're continuing to monitor the progress of the deployment so that it fully mitigates impact for the remaining infrastructure.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to search.
Root cause: Components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact.
Next update by: Tuesday, April 29, 2025, at 1:30 PM UTC
Time:Tue Apr 29 05:30:55 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: We've initiated deploying our fix to the affected environment, which has remediated impact for most of the affected users. We're monitoring the progress of the deployment so that it fully mitigates impact for the remaining section of affected infrastructure.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to search.
Root cause: Components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact.
Next update by: Tuesday, April 29, 2025, at 11:30 AM UTC
Time:Mon Apr 28 23:05:52 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: Telemetry indicates that the service has remained at normal performance thresholds and some users may not be experiencing impact. We're in the final stages of validating short-term performance improvements, while also identifying additional optimization actions that may be needed to fully remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to search.
Root cause: Components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact.
Next update by: Tuesday, April 29, 2025, at 9:30 AM UTC
Time:Mon Apr 28 08:22:46 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: Our review of telemetry indicates that the service has returned to normal performance thresholds and users may be noticing relief. However, we're validating and deploying a fix to improve performance parameters in the short term while conducting a period of monitoring. In parallel, we're continuing to review telemetry data to determine whether additional optimization actions may be required to fully remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to search.
Root cause: Components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact.
Next update by: Tuesday, April 29, 2025, at 4:00 AM UTC
Time:Mon Apr 28 07:20:37 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: We've identified that components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact. We've restarted service instances on the infrastructure but this was unsuccessful in providing relief. We're reviewing performance parameters and data to determine our next steps towards remediation.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to search.
Root cause: Components of infrastructure, responsible for processing users search requests, are performing below acceptable performance thresholds and causing impact.
Next update by: Monday, April 28, 2025, at 1:30 PM UTC
Time:Mon Apr 28 05:21:26 2025
Description:Title: Some users may encounter delays or failures searching in Outlook on the web
User impact: Users may encounter delays or failures searching in Outlook on the web.
More info: Users may also see issues searching in SharePoint Online.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, April 28, 2025, at 11:30 AM UTC

EX1061148 - Admins may be unable to update Dynamic Distribution Group (DDG) memberships

Status:serviceRestored
Start Time:Mon Apr 21 11:44:00 2025
End Time:Fri Apr 25 19:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Mon Apr 28 17:38:06 2025
Root Cause:The piece of infrastructure responsible for updating DDG memberships wasn't included within a recent service update and resulted in impact.
Next Update:N/A

Details

Time:Mon Apr 28 17:36:58 2025
Description:Title: Admins may be unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins may have been unable to update DDG memberships.
Final status: We've confirmed through monitoring service health telemetry that reverting the impacting service update successfully resulted in the exception counts returning to expected values, and the impact is remediated.
Scope of impact: Admins that attempted to update DDG memberships and users that attempted to receive DDG automatic updates may have been impacted.
Start time: Monday, April 21, 2025, at 3:44 PM UTC
End time: Friday, April 25, 2025, at 11:00 PM UTC
Root cause: The piece of infrastructure responsible for updating DDG memberships wasn't included within a recent service update and resulted in impact.
Next steps: - We're further reviewing the recent service update testing and validation procedures to understand what prevented us from detecting that the piece of infrastructure responsible for updating DDG memberships wasn't targeted and therefore could result in this impact, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
Time:Fri Apr 25 17:29:24 2025
Description:Title: Admins may be unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins may be unable to update DDG memberships.
More info: Additionally, members of the DDG automatic updates are failing, even after forcing refresh with the '-ForceMembershipRefresh' switch.
Current status: We've completed the reversion of the impacting service update and we're monitoring service health telemetry to ensure the exception counts return to expected values. We anticipate the service will have fully recovered by our next scheduled communications update.
Scope of impact: Admins attempting to update DDG memberships and users attempting to receive DDG automatic updates may be impacted.
Start time: Monday, April 21, 2025, at 3:44 PM UTC
Estimated time to resolve: We anticipate the service will be fully recovered by Monday, April 28, 2025, at 11:00 PM UTC.
Root cause: The piece of infrastructure responsible for updating DDG memberships wasn't included within a recent service update, resulting in impact.
Next update by: Monday, April 28, 2025, at 11:00 PM UTC
Time:Thu Apr 24 19:21:31 2025
Description:Title: Admins may be unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins may be unable to update DDG memberships.
More info: Additionally, members of the DDG automatic updates are failing, even after forcing refresh with the '-ForceMembershipRefresh' switch.
Current status: Our analysis of the affected DDG configurations has determined that a small portion of infrastructure responsible for updating DDG memberships was not included in a recent service update. We're in the process of reverting the service to its most recently stable version to mitigate the issue. Additionally, we anticipate that a remediation timeline will be available by our next scheduled update.
Scope of impact: Admins attempting to update DDG memberships and users attempting to receive DDG automatic updates may be impacted.
Root cause: The piece of infrastructure responsible for updating DDG memberships wasn't included within a recent service update, resulting in impact.
Next update by: Friday, April 25, 2025, at 11:00 PM UTC
Time:Thu Apr 24 06:59:47 2025
Description:Title: Admins are unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins are unable to update DDG memberships.
More info: Additionally, members of the DDG automatic updates are failing, even after forcing refresh with the '-ForceMembershipRefresh' switch.
Current status: Our investigation into the root cause has so far been inconclusive. We're continuing our in depth analysis of DDG configurations, in order to identify the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and admins attempting to update DDG membership using the EAC are impacted.
Next update by: Friday, April 25, 2025, at 11:00 AM UTC
Time:Thu Apr 24 01:06:58 2025
Description:Title: Admins are unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins are unable to update DDG memberships.
More info: Additionally, members of the DDG automatic updates are failing, even after forcing refresh with the '-ForceMembershipRefresh' switch.
Current status: We're continuing our review of DDG configurations provided by some affected users as we continue to familiarize ourselves with the impacted scenario and ascertain our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and admins attempting to update DDG membership using the EAC are impacted.
Next update by: Thursday, April 24, 2025, at 12:00 PM UTC
Time:Wed Apr 23 22:57:00 2025
Description:Title: Admins are unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins are unable to update DDG memberships.
More info: Additionally, members of the DDG automatic updates are failing, even after forcing refresh with the '-ForceMembershipRefresh' switch.
Current status: We're reviewing DDG configurations settings provided by some affected users to aid in refining our understanding of the impacted scenario.
Scope of impact: Your organization is affected by this event, and admins attempting to update DDG membership using the EAC are impacted.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
Time:Wed Apr 23 22:30:16 2025
Description:Title: Admins are unable to update Dynamic Distribution Group (DDG) memberships
User impact: Admins are unable to update DDG memberships.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1060196 - Users may be unable to create an email address for a new Microsoft Teams channel and receive an error

Status:serviceRestored
Start Time:Thu Apr 17 13:40:00 2025
End Time:Fri Apr 25 12:25:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Apr 28 16:43:31 2025
Root Cause:A recent service update contained a code error that introduced a compatibility issue and prevented users from creating an email address for new Microsoft Teams channels.
Next Update:N/A

Details

Time:Mon Apr 28 16:40:16 2025
Description:Title: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error
User impact: Users may have been unable to create an email address for a new Microsoft Teams channel and received an error.
More info: When users selected "Get email address" for a newly created Microsoft Teams channel, they may have received an error that stated: "We couldn’t get the email address of this channel."
This issue didn't impact email addresses that had already been created for existing Teams channels.
Final status: We’ve confirmed through monitoring service telemetry that our code fix successfully remediated impact, and users are now able to create an email address for new Microsoft Teams channels as expected.
Scope of impact: Any user that attempted to create an email address for a new Microsoft Teams channel may have been impacted.
Start time: Thursday, April 17, 2025, at 5:40 PM UTC
End time: Friday, April 25, 2025, at 4:25 PM UTC
Root cause: A recent service update contained a code error that introduced a compatibility issue and prevented users from creating an email address for new Microsoft Teams channels.
Next steps: - We're further reviewing the service update to understand how the code error and compatibility issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
Time:Fri Apr 25 13:10:23 2025
Description:Title: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error
User impact: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error.
More info: When users select "Get email address" for a newly created Microsoft Teams channel, they may receive an error that states: "We couldn’t get the email address of this channel."
This issue doesn't impact email addresses that have already been created for existing Teams channels.
Current status: We’ve deployed the fix to all affected environments and are monitoring the service to ensure this action has successfully resolved the issue.
Scope of impact: Any user attempting to create an email address for a new Microsoft Teams channel may be impacted.
Start time: Thursday, April 17, 2025, at 5:40 PM UTC
Root cause: A recent regular service update contains a code issue and is causing impact.
Next update by: Monday, April 28, 2025, at 10:00 PM UTC
Time:Wed Apr 23 12:15:50 2025
Description:Title: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error
User impact: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error.
More info: When users select "Get email address" for a newly created Microsoft Teams channel, they may receive an error that states: "We couldn’t get the email address of this channel."
This issue doesn't impact email addresses that have already been created for existing Teams channels.
Current status: We've deployed the code fix to our internal test environment and validated it's efficacy in remediating the impact. We're preparing to deploy the fix to all affected environments, and we anticipate the deployment will begin by our next scheduled communications update.
Scope of impact: Any user attempting to create an email address for a new Microsoft Teams channel may be impacted.
Start time: Thursday, April 17, 2025, at 5:40 PM UTC
Root cause: A recent regular service update contains a code issue and is causing impact.
Next update by: Friday, April 25, 2025, at 5:30 PM UTC
Time:Tue Apr 22 14:19:11 2025
Description:Title: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error
User impact: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error.
More info: When users select "Get email address" for a newly created Microsoft Teams channel, they may receive an error that states: "We couldn’t get the email address of this channel."
This issue doesn't impact email addresses that have already been created for existing Teams channels.
Current status: We've identified a recent regular service update that contains a code issue and is causing impact. We've developed a code fix and are validating its efficacy before deploying.
Scope of impact: Any user attempting to create an email address for a new Microsoft Teams channel is impacted.
Start time: Thursday, April 17, 2025, at 5:40 PM UTC
Root cause: A recent regular service update contains a code issue and is causing impact.
Next update by: Wednesday, April 23, 2025, at 5:30 PM UTC
Time:Tue Apr 22 14:05:58 2025
Description:Title: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error
User impact: Users may be unable to create an email address for a new Microsoft Teams channel and receive an error.
More info: When users select "Get email address" for a newly created Microsoft Teams channel, they may receive an error that states: "We couldn’t get the email address of this channel."
This issue doesn't impact email addresses that have already been created for existing Teams channels.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1044931 - Some users' time zone and work hours may not have been appearing on their profile card in Microsoft Teams

Status:serviceRestored
Start Time:Sun Mar 2 23:33:00 2025
End Time:Mon Apr 28 02:32:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Apr 28 09:18:27 2025
Root Cause:A recent service change designed to improve the language translation function introduced a regression, which caused impact.
Next Update:N/A

Details

Time:Mon Apr 28 09:18:27 2025
Description:Title: Some users' time zone and work hours may not have been appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not have been appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may have been presented with a placeholder style "HH:00" input in the field.
Impact was specific to users that leveraged non-English languages.
Final status: We've confirmed the deployment to the remaining affected infrastructure has completed and impact is no longer occurring.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may have been impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
End time: Monday, April 28, 2025, at 6:32 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression, which caused impact.
Next steps: - We're reviewing our change procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Thu Apr 24 06:47:05 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We're anticipating that the deployment to the remaining affected infrastructure will be complete by Monday, April 28, 2025.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Monday, April 28, 2025, at 3:00 PM UTC
Time:Tue Apr 22 10:19:06 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
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 to be able to provide an approximate remediation time line for users served through the remaining affected infrastructure as part of our next scheduled update.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Thursday, April 24, 2025, at 3:00 PM UTC
Time:Mon Apr 14 10:25:59 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: The deployment of the fix to the remaining impacted service environments has reached the final stages of validation and deployment. We'll continue to monitor its progress to ensure impact is remediated as expected.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Tuesday, April 22, 2025, at 3:00 PM UTC
Time:Fri Apr 11 09:22:57 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We're in the final stages of deploying the fix, and expect to provide a completion timeline by our next scheduled update.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Monday, April 14, 2025, at 3:00 PM UTC
Time:Thu Apr 10 10:38:28 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We continue to review service telemetry as the deployed fix progresses, and continue to assess further actions to implement to expedite the process of mitigation.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Estimated time to resolve: We expect the deployment of the fix to complete by Monday, April 21, 2025.
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Friday, April 11, 2025, at 2:30 PM UTC
Time:Tue Apr 8 09:48:42 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We're continuing to monitor service telemetry as the deployed fix progresses, and are assessing further available actions to perform to expedite the process of mitigation.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Estimated time to resolve: We expect the deployment of the fix to complete by Monday, April 21, 2025.
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Thursday, April 10, 2025, at 2:30 PM UTC
Time:Wed Apr 2 10:15:17 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We're continuing to review options to expedite the completion of the deployment.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Estimated time to resolve: We expect the deployment of the fix to complete by Monday, April 21, 2025.
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Tuesday, April 8, 2025, at 3:00 PM UTC
Time:Tue Apr 1 11:39:26 2025
Description:Title: Some users' time zone and work hours may not be appearing on their profile card in the Microsoft Teams
User impact: Users' time zone and work hours may not be appearing on their profile card in the Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users may be presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We expect the deployment of the fix to complete by Monday, April 21, 2025, and we're reviewing options to expedite the completion of the deployment.
Scope of impact: Some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client may be impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Estimated time to resolve: We expect the deployment of the fix to complete by Monday, April 21, 2025.
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Wednesday, April 2, 2025, at 4:00 PM UTC
Time:Tue Apr 1 10:31:39 2025
Description:Title: Some users' time zone and work hours aren't appearing on their profile card in the Microsoft Teams
User impact: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users are presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We've validated the efficacy of the fix and have begun deployment, to correct the regression and remediate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client are impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Tuesday, April 1, 2025, at 5:00 PM UTC
Time:Mon Mar 31 15:40:09 2025
Description:Title: Some users' time zone and work hours aren't appearing on their profile card in the Microsoft Teams
User impact: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users are presented with a placeholder style "HH:00" input in the field.
Impact is specific to users that leverage non-English languages.
Current status: We've confirmed that a recent service change designed to improve the language translation function introduced a regression that's causing impact. We're validating the efficacy of a fix to correct the regression and expect to have a timeline for the deployment by the time of our next update.
Scope of impact: Your organization is affected by this event, and some users attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client are impacted.
Start time: Monday, March 3, 2025, at 4:33 AM UTC
Root cause: A recent service change designed to improve the language translation function introduced a regression that's causing impact.
Next update by: Tuesday, April 1, 2025, at 3:00 PM UTC
Time:Mon Mar 31 13:27:59 2025
Description:Title: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams
User impact: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams.
More info: Instead of seeing their actual hours with their time zone, users are presented with a placeholder style "HH:00" input in the field. Users can view the correct time zone and work hours on their profile card using the Microsoft Teams web client as a workaround.
Current status: While we await the profile card logs from your organization, we're continuing to investigate the provide trace logs. Our findings suggest that an issue with language translation is causing the impact, but we're continuing to validate this theory.
Scope of impact: Your organization is affected by this event, and any user attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client is impacted.
Next update by: Monday, March 31, 2025, at 7:30 PM UTC
Time:Mon Mar 31 12:06:56 2025
Description:Title: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams
User impact: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams.
More info: Users can view the correct time zone and work hours on their profile card using the Microsoft Teams web client as a workaround.
Current status: We're reaching out to your organization to collect profile card logs, so that we can review the request call flow and identify the source of the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view time zone and work hours on profile cards in the Microsoft Teams desktop client is impacted.
Next update by: Monday, March 31, 2025, at 5:30 PM UTC
Time:Mon Mar 31 11:52:13 2025
Description:Title: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams
User impact: Users' time zone and work hours are shown as HH:00 on their profile card in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1051999 - Admins may be unable to validate connectors from the Exchange admin center

Status:serviceRestored
Start Time:Tue Mar 25 20:57:00 2025
End Time:Fri Apr 25 15:18:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Fri Apr 25 17:07:47 2025
Root Cause:A recent framework change caused a configuration issue between the new and old framework that resulted in the impact.
Next Update:N/A

Details

Time:Fri Apr 25 16:27:42 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may have been unable to validate connectors from the Exchange admin center.
More info: Admins may have been able to validate the connectors when trying again after the first failed attempt.
Affected admins may have seen failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Final status: We've completed the deployment of the fix and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any admin may have been unable to validate connectors from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 1:57 AM UTC
End time: Friday, April 25, 2025, at 7:18 PM UTC
Root cause: A recent framework change caused a configuration issue between the new and old framework that resulted in the impact.
Next steps: - We're investigating the impacting framework change to establish what why and how it caused impact. The results of the investigation will help us improve our update processes and help establish ways to improve the service.
This is the final update for the event.
Time:Mon Apr 21 16:19:51 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: Our fix deployments have made progress but are taking longer than previously anticipated. We expect this issue will be resolved by our next scheduled update.
Scope of impact: Any admin may be unable to validate connectors initially from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 12:57 AM UTC
Root cause: A recent framework change caused a configuration issue between the new and old framework that’s resulting in the impact.
Next update by: Friday, April 25, 2025, at 9:00 PM UTC
Time:Thu Apr 17 15:47:53 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: Our fix deployments are progressing as expected and we continue to anticipate they will complete and remediate impact for all admins by Monday, April 21, 2025.
Scope of impact: Any admin may be unable to validate connectors initially from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 12:57 AM UTC
Root cause: A recent framework change caused a configuration issue between the new and old framework that’s resulting in the impact.
Next update by: Monday, April 21, 2025, at 9:00 PM UTC
Time:Mon Apr 14 16:15:11 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: We're continuing to monitor as the deployment of our fix progresses, and while it should have reached a majority of the affected environment by our next scheduled communications update, we anticipate that it may complete and resolve the issue for all admins by Monday, April 21, 2025, at the earliest. We'll provide a more precise resolution date once available.
Scope of impact: Any admin may be unable to validate connectors initially from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 12:57 AM UTC
Root cause: A recent framework change caused a configuration issue between the new and old framework that’s resulting in the impact.
Next update by: Thursday, April 17, 2025, at 9:00 PM UTC
Time:Fri Apr 11 15:40:45 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: Our deployment of the previously mentioned fix is taking longer than anticipated and has reached approximately sixty percent of the impacted service environment. We're continuing to monitor as the deployment progresses, and we're aiming to provide a new timeline to remediation in our next scheduled communications update.
Scope of impact: Any admin may be unable to validate connectors initially from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 12:57 AM UTC
Root cause: A recent framework change caused a configuration issue between the new and old framework that’s resulting in the impact.
Next update by: Monday, April 14, 2025, at 9:30 PM UTC
Time:Wed Apr 9 16:11:06 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: We’ve determined that a recent framework change caused a configuration issue between the new and old framework that's resulting in the impact. We’ve developed and are in the process of deploying a fix to correct the configuration problem, and we expect the deployment will reach all affected users to resolve this problem by our next scheduled update.
Scope of impact: Any admin may be unable to validate connectors initially from the Exchange admin center.
Start time: Wednesday, March 26, 2025, at 12:57 AM
Root cause: A recent framework change caused a configuration issue between the new and old framework that’s resulting in the impact.
Next update by: Friday, April 11, 2025, at 9:00 PM UTC
Time:Wed Apr 9 15:37:30 2025
Description:Title: Admins may be unable to validate connectors from the Exchange admin center
User impact: Admins may be unable to validate connectors from the Exchange admin center.
More info: Admins may be able to validate the connectors when trying again after the first failed attempt.
Affected admins may see failures from the Hybrid Configuration Wizard, which has dependency on the connector validation.
Current status: We're investigating a potential issue in which admins can’t validate connectors from the Exchange admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1062048 - Some users were unable to utilize auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams

Status:serviceRestored
Start Time:Fri Apr 25 06:35:00 2025
End Time:Fri Apr 25 07:26:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Apr 25 08:22:50 2025
Root Cause:A section of infrastructure that facilitates auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams was not performing as expected.
Next Update:N/A

Details

Time:Fri Apr 25 08:22:50 2025
Description:Title: Some users were unable to utilize auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams
User impact: Users were unable to utilize auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams.
Final status: We've determined that a section of infrastructure that facilitates auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams was not performing as expected. We've redirected user traffic to alternate infrastructure, which has remediated impact.
Scope of impact: Impact was specific to users who were served through the affected infrastructure.
Start time: Friday, April 25, 2025, at 10:35 AM UTC
End time: Friday, April 25, 2025, at 11:26 AM UTC
Root cause: A section of infrastructure that facilitates auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams was not performing as expected.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Fri Apr 25 07:16:20 2025
Description:Title: Some users may be unable to utilize auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams
User impact: Users may be unable to utilize auto attendant, voice mail, call queues and call recorder bot in Microsoft Teams.
Current status: We're are analyzing service telemetry to help us identify the root cause and next steps to remediate impact.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Next update by: Friday, April 25, 2025, at 1:30 PM UTC

EX1061527 - Users intermittently may be unable to access their mailboxes through any Exchange Online connection method

Status:serviceRestored
Start Time:Thu Apr 24 12:40:44 2025
End Time:Thu Apr 24 12:56:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Thu Apr 24 23:39:41 2025
Root Cause:A portion of mailbox infrastructure entered an unhealthy state, resulting in access issues for the mailboxes hosted on it.
Next Update:N/A

Details

Time:Thu Apr 24 13:30:02 2025
Description:Title: Users intermittently may be unable to access their mailboxes through any Exchange Online connection method
User impact: Users intermittently may have been unable to access their mailboxes through any Exchange Online connection method.
Final status: Our monitoring systems identified users intermittently may have been unable to access their mailboxes through any Exchange Online connection method. We've identified that a portion of mailbox infrastructure entered an unhealthy state, resulting in access issues for the mailboxes hosted on it. To remediate this issue, our automated service redirected affected traffic to an alternative infrastructure, and after monitoring the service, we've verified this action successfully resolved the problem.
Scope of impact: Impact may have intermittently occurred for any user attempting to access their mailboxes in Exchange Online.
Start time: Thursday, April 24, 2025, at 4:26 AM UTC
End time: Thursday, April 24, 2025, at 4:56 PM UTC
Root cause: A portion of mailbox infrastructure entered an unhealthy state, resulting in access issues for the mailboxes hosted on it.
Next steps: - We're investigating why the mailbox infrastructure entered an unhealthy state to prevent this problem from happening again in the future.
This is the final update for the event.
Time:Thu Apr 24 12:41:53 2025
Description:Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.

IT1061733 - Users can't enroll, check-in, or update managed devices in Microsoft Intune

Status:serviceRestored
Start Time:Thu Apr 24 11:50:00 2025
End Time:Thu Apr 24 22:48:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:incident
Last Updated:Thu Apr 24 23:28:19 2025
Root Cause:Some components of the Microsoft Intune infrastructure responsible for authenticating service requests encountered an error that caused those components to enter a transient inoperative state and resulted in impact.
Next Update:N/A

Details

Time:Thu Apr 24 23:26:34 2025
Description:Title: Some users may be unable to enroll, check-in, or update managed devices in Microsoft Intune
User impact: Users may have been unable to enroll, check-in, or update managed devices in Microsoft Intune.
More info: Affected users were able to sign in to the Microsoft Intune service, but operations performed within Microsoft Intune after sign-in consistently failed.
Final status: We’ve completed deploying our fix to all the impacted components and have confirmed with our telemetry that the service is healthy again.
Scope of impact: Some users who attempted to enroll, check-in, or update managed devices in Microsoft Intune were impacted.
Start time: Thursday, April 24, 2025, at 3:50 PM UTC
End time: Friday, April 25, 2025, at 2:48 AM UTC
Root cause: Some components of the Microsoft Intune infrastructure responsible for authenticating service requests encountered an error that caused those components to enter a transient inoperative state and resulted in impact.
Next steps: - We’re performing an in-depth root cause analysis to better understand how an error caused the affected components to enter a transient inoperative state so that we can identify potential preventive measures to ensure similar impact doesn’t occur in the future.
This is the final update for this event.
Time:Thu Apr 24 22:49:16 2025
Description:Title: Some users may be unable to enroll, check-in, or update managed devices in Microsoft Intune
User impact: Users may be unable to enroll, check-in, or update managed devices in Microsoft Intune.
More info: Affected users can sign in to the Microsoft Intune service, but operations performed within Microsoft Intune after sign-in consistently fail.
Current status: Our previously mentioned change is nearly done deploying to all the impacted components. Based on its progress, we anticipate deployment will complete and the issue will be fully remediated prior to our next scheduled update.
Scope of impact: Some users attempting to enroll, check-in, or update managed devices in Microsoft Intune are impacted.
Start time: Thursday, April 24, 2025, at 3:50 PM UTC
Root cause: Some components of the Microsoft Intune infrastructure responsible for authenticating service requests encountered an error that caused those components to enter a transient inoperative state, resulting in impact.
Next update by: Friday, April 25, 2025, at 5:00 AM UTC
Time:Thu Apr 24 20:02:28 2025
Description:Title: Some users may be unable to enroll, check-in, or update managed devices in Microsoft Intune
User impact: Users may be unable to enroll, check-in, or update managed devices in Microsoft Intune.
More info: Affected users can sign in to the Microsoft Intune service, but operations performed within Microsoft Intune after sign-in consistently fail.
Current status: Our investigation has determined that some components of the Microsoft Intune infrastructure responsible for authenticating service requests encountered an error that caused those components to enter a transient inoperative state, resulting in impact. We're deploying a change to the impacted components to route the impacted traffic through healthy infrastructure and repair this issue, after which we'll monitor our service health telemetry to determine whether further remediating actions will be required.
Scope of impact: Some users attempting to enroll, check-in, or update managed devices in Microsoft Intune may be impacted.
Start time: Thursday, April 24, 2025, at 3:50 PM UTC
Root cause: Some components of the Microsoft Intune infrastructure responsible for authenticating service requests encountered an error that caused those components to enter a transient inoperative state, resulting in impact.
Next update by: Friday, April 25, 2025, at 3:00 AM UTC
Time:Thu Apr 24 19:30:17 2025
Description:Title: Users can't enroll, check-in, or update managed devices in Microsoft Intune
User impact: Users can't enroll, check-in, or update managed devices in Microsoft Intune.
More info: Affected users can sign in to the Microsoft Intune service, but operations performed within Microsoft Intune after sign-in consistently fail.
Current status: We're investigating a potential issue with the Microsoft Intune service and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1046723 - Users' SharePoint Online pages may be failing to generate thumbnails of webparts

Status:serviceRestored
Start Time:Wed Apr 2 07:35:59 2025
End Time:Tue Apr 15 13:40:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Thu Apr 24 18:09:55 2025
Root Cause:A feature deployment to improve SharePoint Online data management produced an impacting code issue that was preventing users' SharePoint Online pages from generating thumbnails of webparts.
Next Update:N/A

Details

Time:Thu Apr 24 18:09:55 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may have been failing to generate thumbnails of webparts.
More info: Impacted webparts included but weren't limited to: - Hero - News - Quick links - Highlighted content
Final status: We've completed the deployment of the fix and confirmed through testing with affected users that the impact has been remediated.
Scope of impact: Impact was specific to users served through the affected infrastructure expecting thumbnails to be generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
End time: Tuesday, April 15, 2025, at 5:40 PM UTC
Root cause: A feature deployment to improve SharePoint Online data management produced an impacting code issue that was preventing users' SharePoint Online pages from generating thumbnails of webparts.
Next steps: - We're reviewing our feature update testing and validation methods to better identify the potential for impact to thumbnail generation prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
Time:Thu Apr 10 19:35:53 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may be failing to generate thumbnails of webparts.
More info: Impacted webparts include, but aren't limited to: - Hero - News - Quick links - Highlighted content
Current status: We've completed validating the previously mentioned fix for efficacy, and we're initiating deployment to the impacted service environment. We're forecasting that the fix will take until early May 2025 to complete, though we're aiming to confirm the timeline for full deployment and remediation in our next scheduled communications update.
Scope of impact: Impact is specific to users served through the affected infrastructure expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Root cause: A feature deployment to improve SharePoint Online data management has produced an impacting code issue that’s preventing users' SharePoint Online pages from generating thumbnails of webparts.
Next update by: Thursday, April 24, 2025, at 11:30 PM UTC
Time:Wed Apr 9 18:00:57 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may be failing to generate thumbnails of webparts.
More info: Impacted webparts include but aren't limited to: - Hero - News - Quick links - Highlighted content
Current status: Our additional analysis into the extended logging has helped us isolate a feature deployment that has produced an impacting code issue, which we believe is preventing users' SharePoint Online pages from generating thumbnails of webparts. We're internally validating a fix to address the code problem and remediate the impact.
Scope of impact: Impact is specific to users served through the affected infrastructure expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Root cause: A feature deployment to improve SharePoint Online data management has produced an impacting code issue that’s preventing users' SharePoint Online pages from generating thumbnails of webparts.
Next update by: Thursday, April 10, 2025, at 11:30 PM UTC
Time:Mon Apr 7 16:54:11 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may be failing to generate thumbnails of webparts.
More info: Impacted webparts include but aren't limited to: - Hero - News - Quick links - Highlighted content
Current status: While our review of extended logging we've gathered from a reproduction of the issue is progressing, we need additional time to isolate a new potential root cause and identify a path to remediation.
Scope of impact: Impact is specific to users served through the affected infrastructure expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Wednesday, April 9, 2025, at 10:30 PM UTC
Time:Fri Apr 4 15:00:49 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may be failing to generate thumbnails of webparts.
More info: Impacted webparts include but aren't limited to: - Hero - News - Quick links - Highlighted content
Current status: We've completed our reversion of the previously mentioned change that we suspected was leading to impact; however, our testing indicates that the impact is ongoing. We're proceeding with a review of the extended logging we've gathered from a reproduction of the issue to isolate a new potential root cause and identify a path to remediation.
Scope of impact: Impact is specific to users served through the affected infrastructure expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Monday, April 7, 2025, at 10:30 PM UTC
Time:Thu Apr 3 19:42:48 2025
Description:Title: Users' SharePoint Online pages may be failing to generate thumbnails of webparts
User impact: Users' SharePoint Online pages may be failing to generate thumbnails of webparts.
More info: Impacted webparts include but aren't limited to:
- Hero - News - Quick links - Highlighted content
Current status: While our testing and subsequent analysis of gathered data is ongoing to confirm the underlying root cause of this issue, we're in the process of reverting a change which we suspect is contributing to the impact.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Friday, April 4, 2025, at 8:30 PM UTC
Time:Thu Apr 3 15:21:36 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include but aren't limited to:
- Hero - News - Quick links - Highlighted content
Current status: We're reverting a recent service update in our test environment which may be responsible for impact to assist in isolating the underlying cause and develop a remediation strategy.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Friday, April 4, 2025, at 12:00 AM UTC
Time:Wed Apr 2 20:15:20 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include but aren't limited to:
- Hero - News - Quick links - Highlighted content
Current status: We’re attempting to create an environment using a previous build that doesn’t contain the isolated data mismatch so that we can compare it to our other environment that contains the reproduction of the issue. The results of this investigation will help point to the origin of the data mismatch and aid in identifying an effective solution.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Thursday, April 3, 2025, at 8:30 PM UTC
Time:Wed Apr 2 16:36:18 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include but aren't limited to:
- Hero - News - Quick links - Highlighted content
Current status: We're progressing with our investigation into the data mismatch that was isolated between a group of our third-party partners as we work to isolate the source for this event. In parallel, we're analyzing recent updates to the service that could have introduced the data mismatch to help us determine the troubleshooting steps for remediating the impact.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Start time: Wednesday, March 12, 2025, at 12:00 PM UTC
Next update by: Thursday, April 3, 2025, at 1:30 AM UTC
Time:Wed Apr 2 14:36:10 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include but aren't limited to:
- Hero - News - Quick links - Highlighted content
Current status: As we continue our analysis into service monitoring and diagnostic data, we've isolated a data mismatch that’s occurring between a collection of our third-party partners and may be associated with the thumbnail problems. We're further analyzing this data mismatch to help us confirm our findings, and so we can confirm our next steps for remediating the impact.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Next update by: Wednesday, April 2, 2025, at 9:00 PM UTC
Time:Wed Apr 2 09:59:59 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include, but aren't limited to:
- Hero - News - QuickLinks - Highlighted content
Current status: We're continuing to review diagnostic data from our service monitoring telemetry to identify the underlying root cause and formulate a mitigation plan.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Next update by: Wednesday, April 2, 2025, at 7:00 PM UTC
Time:Wed Apr 2 07:45:40 2025
Description:Title: Users' SharePoint Online pages may be failing to generate webparts thumbnails
User impact: Users' SharePoint Online pages may be failing to generate webparts thumbnails.
More info: Impacted webparts include, but aren't limited to:
- Hero - News - QuickLinks - Highlighted content
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, expecting thumbnails generated for webparts in SharePoint Online pages.
Next update by: Wednesday, April 2, 2025, at 2:00 PM UTC

EX1026017 - Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows

Status:serviceRestored
Start Time:Tue Dec 10 08:38:00 2024
End Time:Mon Apr 21 16:00:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Thu Apr 24 13:48:47 2025
Root Cause:An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows was causing impact.
Next Update:N/A

Details

Time:Thu Apr 24 13:48:47 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may have seen an error and couldn't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact included but wasn't limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Microsoft Loop components - Microsoft Copilot (Microsoft 365) output
Affected users may have received the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we worked to remediate this issue, affected users could have attached these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Final status: We've received confirmation from previously affected users that impact was fully resolved after the deployment of our fix completed.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may have been affected.
Start time: Tuesday, December 10, 2024, at 1:38 PM UTC
End time: Monday, April 21, 2025, at 8:00 PM UTC
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows was causing impact.
Next steps: - We're investigating how the misconfiguration was introduced to better understand and prevent similar future impact.
This is the final update for the event.
Time:Tue Apr 22 13:33:20 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Microsoft Loop components - Microsoft Copilot (Microsoft 365) output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We’ve completed deployment of the fix to all affected environments. Some users may need to restart the new Outlook for Windows application to experience relief. We’re monitoring the service and awaiting verification from affected users to confirm full resolution.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Start time: Tuesday, December 10, 2024, at 1:38 PM UTC
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Thursday, April 24, 2025, at 7:30 PM UTC
Time:Thu Apr 17 14:07:31 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We’ve progressed the incremental deployment of the fix to 50 percent of the affected environment, and we’re seeing continued signs of improvement to service health. We anticipate starting the deployment to 100 percent of the environment today and will monitor its progress to ensure it completes as expected to resolve this issue by our next scheduled update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Start time: Tuesday, December 10, 2024, at 1:38 PM UTC
Estimated time to resolve: We anticipate the fix deployment should complete to resolve this issue by Tuesday, April 22, 2025.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Tuesday, April 22, 2025, at 8:00 PM UTC
Time:Wed Apr 16 18:19:43 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We continue to see positive progress on the fix saturation, though we're still working on calculating a timeline for when it may complete. We anticipate having this information by our next communication update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Start time: Tuesday, December 10, 2024, at 1:38 PM UTC
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Thursday, April 17, 2025, at 8:00 PM UTC
Time:Wed Apr 16 13:35:02 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Our fix has been deployed to approximately 10 percent of the impacted environment. As it progresses, users may begin to experience relief. We're continuing to monitor as it saturates and will provide updates on the deployment progress, and a timeline for completion, with our next scheduled update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Start time: Tuesday, December 10, 2024, at 1:38 PM UTC
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Wednesday, April 16, 2025, at 8:00 PM UTC
Time:Tue Apr 15 22:22:00 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We've initiated the fix deployment and anticipate it will complete by April 24, 2025, or sooner. We're monitoring as it progresses and will provide an updated timeline when one becomes available.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Wednesday, April 16, 2025, at 8:00 PM UTC
Time:Mon Apr 7 13:57:58 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We're making the final preparations for the deployment of the fix, which we expect will begin in the next several days, and we’ll provide an ETA for the completion of the deployment, if available, after assessing its progress until our next scheduled update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Wednesday, April 16, 2025, at 8:00 PM UTC
Time:Mon Mar 31 13:48:25 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes but isn’t limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We're continuing our testing and validation of a fix and expect the fix to start deployment by the next scheduled update. Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using the new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Monday, April 7, 2025, at 8:00 PM UTC
Time:Thu Mar 27 13:46:40 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Our operation to validate the previously mentioned code fix for efficacy is in its final stages. We anticipate that the process will be complete by our next scheduled communications update, at which time we'll prepare the fix for deployment to the impacted service environment.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Monday, March 31, 2025, at 6:30 PM UTC
Time:Mon Mar 24 13:27:21 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required." While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Our efforts to validate and review the efficacy of our code fix before initiating deployment are ongoing. We'll provide a timeline for deployment and remediation as it becomes available.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Thursday, March 27, 2025, at 7:30 PM UTC
Time:Wed Mar 19 14:26:25 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We're continuing to validate and review the efficacy of our code fix before potential deployment to affected users. Due to the complexity of the aforementioned code fix designed to correct the authentication configuration, additional time is needed to verify the code fix will resolve all reported impact scenarios for affected tenants.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Monday, March 24, 2025, at 7:00 PM UTC
Time:Mon Mar 17 15:46:50 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Due to the complexity of the aforementioned code fix designed to correct the authentication configuration, additional time is needed to complete its development. We expect to have a timeline for its completion by the time of our next update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Wednesday, March 19, 2025, at 8:00 PM UTC
Time:Thu Mar 13 13:36:44 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following: - OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including: - Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Development of our potential code fix is progressing as expected. In parallel, we're continuing our investigation into the previously mentioned authentication issue that we suspect is leading to impact to assist us in confirming our root cause theory.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Monday, March 17, 2025, at 9:00 PM UTC
Time:Mon Mar 10 17:53:36 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users may see the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: We've identified an authentication issue on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows. We're developing a code fix to resolve the underlying issue while simultaneously further reviewing the authentication issue to understand how it was introduced.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Thursday, March 13, 2025, at 7:00 PM UTC
Time:Fri Mar 7 18:06:36 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users are seeing the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web - Classic Outlook - Outlook desktop clients - Outlook mobile
Current status: Our initial review of support case information indicates that an authentication issue is preventing requests from completing as expected. We're working with affected users to gather additional browser captures of the issue in progress to develop a remediation strategy.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Monday, March 10, 2025, at 10:30 PM UTC
Time:Fri Mar 7 17:22:36 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content - SharePoint Online site links - Loop components - Copilot output
Affected users are seeing the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- classic Outlook on the web - Outlook desktop clients - Outlook mobile
Current status: We're reviewing support case details to better understand the impact scenario and determine our next steps.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Friday, March 7, 2025, at 11:30 PM UTC
Time:Fri Mar 7 16:55:57 2025
Description:Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1060756 - Users intermittently may be unable to load the app launcher or navigation elements from some SharePoint Online sites

Status:serviceRestored
Start Time:Tue Apr 22 00:00:00 2025
End Time:Wed Apr 23 14:45:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Thu Apr 24 12:34:14 2025
Root Cause:A service update produced a traffic configuration issue for a subset of SharePoint Online service infrastructure, which intermittently prevented users from loading the app launcher or navigation elements from some SharePoint Online sites.
Next Update:N/A

Details

Time:Thu Apr 24 12:18:36 2025
Description:Title: Users intermittently may be unable to load the app launcher or navigation elements from some SharePoint Online sites
User impact: Users intermittently were unable to load the app launcher or navigation elements from some SharePoint Online sites.
More info: Users may not have seen the gear icon to open the Settings pane on some SharePoint Online sites and may not have been able to conduct searches via the search box on some sites.
Final status: We've completed the reversion of the offending change and verified with affected users that this action successfully remediated the problem.
Scope of impact: Any user who attempted to load the app launcher or navigation elements from some SharePoint Online sites may have been intermittently impacted.
Start time: Tuesday, April 22, 2025, at 4:00 AM UTC
End time: Wednesday, April 23, 2025, at 6:45 PM UTC
Root cause: A service update produced a traffic configuration issue for a subset of SharePoint Online service infrastructure, which intermittently prevented users from loading the app launcher or navigation elements from some SharePoint Online sites.
Next steps: - We're investigating how the service update produced a traffic configuration issue for a subset of SharePoint Online service infrastructure, which intermittently prevented users from loading the app launcher or navigation elements from some sites, in order to prevent this problem from happening again.
This is the final update for the event.
Time:Wed Apr 23 15:44:50 2025
Description:Title: Users intermittently may be unable to load the app launcher or navigation elements from some SharePoint Online sites
User impact: Users intermittently may be unable to load the app launcher or navigation elements from some SharePoint Online sites.
More info: Users may not see the gear icon to open the Settings pane on some SharePoint Online sites, and users may not be able to conduct searches on some sites via the search box.
Current status: Our additional analysis into the exception has identified a traffic configuration problem occurring for a subset of SharePoint Online service infrastructure that is intermittently preventing expected elements from loading on some SharePoint Online sites. We've isolated a recent service update that has produced the traffic configuration problem, and we've conducted our change reversion process to remediate the impact. As we further analyze the offending change, we're testing with affected users to confirm that impact has been remediated.
Scope of impact: Any user attempting to load the app launcher or navigation elements from some SharePoint Online sites may be intermittently impacted.
Root cause: A service update has produced a traffic configuration issue for a subset of SharePoint Online service infrastructure, intermittently preventing users from loading the app launcher or navigation elements from some SharePoint Online sites.
Next update by: Thursday, April 24, 2025, at 6:00 PM UTC
Time:Wed Apr 23 13:29:05 2025
Description:Title: Users intermittently can't load the app launcher or navigation elements from some SharePoint Online sites
User impact: Users intermittently can't load the app launcher or navigation elements from some SharePoint Online sites.
More info: Users don’t see the gear icon to open the Settings pane on some SharePoint Online sites, and users can’t conduct searches on some sites via the search box.
Current status: Our additional analysis into the problem has determined that in addition to problems with loading the app launcher from some SharePoint Online sites, users may also be unable to launch navigation elements from those sites. In addition, users don’t see the gear icon to open the Settings pane some SharePoint Online sites and they also can’t conduct searches via the search box. We've updated the Title, User Impact, More Info, and Scope in Impact portions of our communications to reflect this new understanding. As we confirm the source for the isolated logging exception, we're further analyzing a group of recent updates to the service to identify the source for the event and determine our next troubleshooting steps for remediating the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to load the app launcher or navigation elements from some SharePoint Online sites is impacted.
Next update by: Wednesday, April 23, 2025, at 8:00 PM UTC
Time:Wed Apr 23 11:51:57 2025
Description:Title: Users intermittently can't load the app launcher from some SharePoint Online sites
User impact: Users intermittently can't load the app launcher from some SharePoint Online sites.
Current status: After collecting the necessary network trace and console logs from your representatives, we're further analyzing an isolated logging exception to help us identify the source for this event, and so the next steps for remediating the impact can be determined.
Scope of impact: Your organization is affected by this event, and any user attempting to load the app launcher from some SharePoint Online sites is impacted.
Next update by: Wednesday, April 23, 2025, at 6:00 PM UTC
Time:Wed Apr 23 09:55:51 2025
Description:Title: Users intermittently can't load the app launcher from some SharePoint Online sites
User impact: Users intermittently can't load the app launcher from some SharePoint Online sites.
Current status: We previously communicated this event under SP1060315, but we were unable to proceed with our investigation due to not being provided the additional trace logs. We're now working with your representative to gather the additional trace logs to help us with our investigation.
Scope of impact: Your organization is affected by this event, and any user attempting to load the app launcher from some SharePoint Online sites is impacted.
Next update by: Wednesday, April 23, 2025, at 4:00 PM UTC

EX1061430 - Users may have been unable to access alerts for Adobe URLs as it was generating false "malicious URL click"

Status:serviceRestored
Start Time:Tue Apr 22 09:24:00 2025
End Time:Thu Apr 24 10:15:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Thu Apr 24 11:04:30 2025
Root Cause:Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, was incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which was resulting in impact.
Next Update:N/A

Details

Time:Thu Apr 24 10:50:42 2025
Description:Title: Users may have been unable to access alerts for Adobe URLs as it was generating false "malicious URL click"
User impact: Users may have been unable to access alerts for Adobe URLs as it was generating false "malicious URL click".
Final status: We've determined our machine learning (ML) model, which safeguards Exchange Online against risky email messages, was incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which was resulting in impact. To fix the issue we initiated Replay Time Travel (RTT) on the affected URLs to fully remediate impact.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Tuesday, April 22, 2025, at 1:24 PM UTC
End time: Thursday, April 24, 2025, at 2:15 PM UTC
Root cause: Our machine learning (ML) model, which safeguards Exchange Online against risky email messages, was incorrectly identifying legitimate email messages as spam due to their similarity to email messages used in spam attacks, which was resulting in impact.
Next steps: - We’ve implemented and are creating additional mitigation’s to improve our machine-learning logic to lower the false positive rate and ensure that legitimate email messages aren’t inaccurately classified as spam and not delivered.
This is the final update for this event.
Time:Thu Apr 24 09:21:46 2025
Description:Title: Users may be unable to access alerts for Adobe URLs as its generating false "malicious URL click"
User impact: Users may be unable to access alerts for Adobe URLs as its generating false "malicious URL click".
Current status: We're analyzing recent trends in diagnostic service telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Next update by: Thursday, April 24, 2025, at 3:30 PM UTC

TM1046914 - Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams

Status:serviceRestored
Start Time:Tue Feb 18 11:15:00 2025
End Time:Thu Apr 24 01:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Apr 24 01:47:36 2025
Root Cause:Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams were failing if the presented token, leveraged to facilitate authentication between users and the service, was invalidated based on CAE that occurred due to conditional access policies applied to these users. After this, the authentication processes then failed to properly request a new token.
Next Update:N/A

Details

Time:Thu Apr 24 01:47:36 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may have been unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still saw voicemail notifications appear but couldn't access these new voicemails. As a workaround, affected users could access their voicemail from Outlook. Conditional access policies were enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Final status: Our fix deployment has completed, and we've confirmed after a period of monitoring and receiving reports from previously affected users that impact was remediated.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE couldn't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
End time: Thursday, April 24, 2025, at 5:00 AM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams were failing if the presented token, leveraged to facilitate authentication between users and the service, was invalidated based on CAE that occurred due to conditional access policies applied to these users. After this, the authentication processes then failed to properly request a new token.
Next steps: - To help prevent similar impact in the future, we're further reviewing the underlying cause of the latent code issue.
This is the final update for the event.
Time:Wed Apr 23 13:50:47 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: Our fix deployment is ongoing and has reached 95 percent saturation. We’ve received reports from some users that our deployment has resolved the issue and we’re continuing to monitor its progress as it completes. We aim to provide an updated timeline to mitigation as one becomes available.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Thursday, April 24, 2025, at 6:30 AM UTC
Time:Tue Apr 22 13:17:46 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We’ve initiated the deployment of the fix and confirmed that service health is improving; however, the deployment is moving slower than anticipated. The fix deployment is ongoing and we’re monitoring its progress to ensure it completes to resolve this issue by our next scheduled update.
We're continuing our validation procedures to prepare the fix for deployment, and we currently anticipate it will be deployed by Tuesday, April 22, 2025.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Wednesday, April 23, 2025, at 6:30 PM UTC
Time:Wed Apr 16 13:27:07 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We're continuing our validation procedures to prepare the fix for deployment, and we currently anticipate it will be deployed by Tuesday, April 22, 2025.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Tuesday, April 22, 2025, at 6:30 PM UTC
Time:Fri Apr 11 12:37:06 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: Our internal testing and validation procedures are ongoing while we work to confirm the efficacy of our fix. We anticipate this will complete by our next scheduled update; after which we'll provide a timeline for deployment of the fix to the affected environment.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Wednesday, April 16, 2025, at 6:30 PM UTC
Time:Thu Apr 10 12:56:01 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We've developed a code fix to correct the authentication process and are validating its efficacy through internal testing.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Friday, April 11, 2025, at 6:30 PM UTC
Time:Wed Apr 9 21:19:34 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We've started developing a code fix that will undergo internal testing before being deployed to the impacted environments. Once the development and testing are complete, we'll aim to provide a resolution timeline.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Thursday, April 10, 2025, at 7:00 PM UTC
Time:Wed Apr 9 12:45:36 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We're continuing to explore our available options for addressing the isolated latent code issue, so we can determine if a code fix deployment will be necessary. We're also exploring if any short-term solutions for addressing the code problem will be viable, in our efforts to expedite impact remediation.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Tuesday, February 18, 2025, at 4:15 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Thursday, April 10, 2025, at 1:30 AM UTC
Time:Mon Apr 7 12:33:26 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We've further identified that, due to the previously mentioned latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on conditional access evaluation that occurs as a result of conditional access policies applied to these users; and the authentication processes fails to properly request a new token. We're developing a code fix to ensure the conditional access evaluation process will process and retry tokens correctly as expected.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Monday, February 24, 2025, at 8:02 PM UTC
Root cause: Due to a latent code issue, authentication checks which occur when users request access to their voicemail in Microsoft Teams are failing if the presented token, which is leveraged to facilitate authentication between users and the service, is invalidated based on CAE that occurs due to conditional access policies applied to these users. After this, the authentication processes then fail to properly request a new token.
Next update by: Wednesday, April 9, 2025, at 6:00 PM UTC
Time:Wed Apr 2 12:36:52 2025
Description:Title: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams
User impact: Users with some conditional access policies applied may be unable to retrieve new voicemails in Microsoft Teams.
More info: Affected users still see voicemail notifications appear but can't access these new voicemails. As a workaround, affected users can access their voicemail from Outlook. Conditional access policies are enabled by admins through Microsoft Entra and relate to continuous access evaluation (CAE).
Current status: We've received reports that users with specific access policy configurations may be unable to retrieve new voicemails in Microsoft Teams. We've identified a code issue that's resulting in voicemail retrieval failures. We're evaluating a potential code fix to remediate impact.
Scope of impact: Users with some conditional Microsoft Entra access policies related to CAE can't retrieve new voicemails in Microsoft Teams.
Start time: Monday, February 24, 2025, at 8:02 PM UTC
Next update by: Monday, April 7, 2025, at 6:00 PM UTC

EX1058997 - Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online

Status:serviceRestored
Start Time:Tue Apr 15 04:59:00 2025
End Time:Wed Apr 23 16:17:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:advisory
Last Updated:Wed Apr 23 21:01:28 2025
Root Cause:A recent update to the Exchange Online service contained an incorrect authentication configuration for the Microsoft Graph API “createUploadSession” used to upload files, which resulted in users being unable to upload attachments larger than 2 MB in Exchange Online.
Next Update:N/A

Details

Time:Wed Apr 23 21:01:28 2025
Description:Title: Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online
User impact: Users couldn't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online.
More info: The provided article details the MB range for messages affected and more details on the Microsoft Graph API “createUploadSession” being utilized: https://learn.microsoft.com/en-us/graph/api/attachment-createuploadsession?view=graph-rest-1.0&tabs=http
Final status: We've completed reverting the offending changes and have confirmed after a period of monitoring that impact was remediated.
Scope of impact: Your organization was affected by this event, and all users couldn't upload attachments larger than 2 MB with Microsoft Graph API’s “createUploadSession” in Exchange Online.
Start time: Tuesday, April 15, 2025, at 8:59 AM UTC
End time: Wednesday, April 23, 2025, at 8:17 PM UTC
Root cause: A recent update to the Exchange Online service contained an incorrect authentication configuration for the Microsoft Graph API “createUploadSession” used to upload files, which resulted in users being unable to upload attachments larger than 2 MB in Exchange Online.
Next steps: - To help prevent similar impact in the future, we're further reviewing our update release procedures to identify authentication configuration issues before being deployed.
This is the final update for the event.
Time:Tue Apr 22 21:23:32 2025
Description:Title: Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online
User impact: Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online.
More info: The provided article details the MB range for messages affected and more details on the Microsoft Graph API “createUploadSession” being utilized: https://learn.microsoft.com/en-us/graph/api/attachment-createuploadsession?view=graph-rest-1.0&tabs=http
Current status: We've rolled back the offending changes throughout the bulk of the affected service environment and are monitoring to ensure impact is broadly remediated.
Scope of impact: Your organization is affected by this event, and all users can't upload attachments larger than 2 MB with Microsoft Graph API’s “createUploadSession” in Exchange Online.
Root cause: A recent update to the Exchange Online service contained an incorrect authentication configuration for the Microsoft Graph API “createUploadSession” used to upload files, which results in users being unable to upload attachments larger than 2 MB in Exchange Online.
Next update by: Thursday, April 24, 2025, at 3:00 AM UTC
Time:Sun Apr 20 13:01:26 2025
Description:Title: Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online
User impact: Users can't upload attachments larger than 2 MB with Microsoft Graph API in Exchange Online.
More info: The provided article details the MB range for messages affected and more details on the Microsoft Graph API “createUploadSession” being utilized: https://learn.microsoft.com/en-us/graph/api/attachment-createuploadsession?view=graph-rest-1.0&tabs=http
Current status: We've determined that a recent update to the Exchange Online service contained an incorrect authentication configuration for the Microsoft Graph API “createUploadSession” used to upload files, which results in users being unable to upload attachments larger than 2 MB in Exchange Online. We've halted the deployment of the offending update and are reverting the update for portions of Exchange Online infrastructure that have already updated to the incorrect configuration. We anticipate this process will be completed by Tuesday, April 22, 2025, and at that time we aim to test for resolution of customer impact.
Scope of impact: Your organization is affected by this event, and all users can't upload attachments larger than 2 MB with Microsoft Graph API’s “createUploadSession” in Exchange Online.
Root cause: A recent update to the Exchange Online service contained an incorrect authentication configuration for the Microsoft Graph API “createUploadSession” used to upload files, which results in users being unable to upload attachments larger than 2 MB in Exchange Online.
Next update by: Wednesday, April 23, 2025, at 3:00 AM UTC

MV1061020 - Users can’t access the Q&A feature after joining town hall meetings in Microsoft Viva Engage

Status:serviceRestored
Start Time:Wed Apr 23 12:38:00 2025
End Time:Wed Apr 23 18:25:00 2025
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Wed Apr 23 19:06:52 2025
Root Cause:A recent change intended to optimize a town hall meeting authentication process resulted in impact.
Next Update:N/A

Details

Time:Wed Apr 23 19:06:52 2025
Description:Title: Users can’t access the Q&A feature after joining town hall meetings in Microsoft Viva Engage
User impact: Users couldn't access the Q&A feature after joining town hall meetings in Viva Engage.
Final status: We've identified that a recent change intended to optimize a town hall meeting authentication process resulted in impact. We've rolled back the offending change throughout the affected environment to resolve the issue and confirmed through telemetry that impact is fully remediated.
Scope of impact: Any user may have been unable to access the Q&A feature after joining town hall meetings in Microsoft Viva Engage.
Start time: Wednesday, April 23, 2025, at 4:38 PM UTC
End time: Wednesday, April 23, 2025, at 10:25 PM UTC
Root cause: A recent change intended to optimize a town hall meeting authentication process resulted in impact.
Next steps: - We're reviewing our update testing and validation methods to better identify code issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
Time:Wed Apr 23 17:55:06 2025
Description:Title: Users can’t access the Q&A feature after joining townhall meetings in Microsoft Viva Engage
User impact: Users can’t access the Q&A feature after joining townhall meetings in Viva Engage.
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Any user may be unable to access the Q&A feature after joining townhall meetings in Microsoft Viva Engage.
Next update by: Wednesday, April 23, 2025, at 11:30 PM UTC
Time:Wed Apr 23 17:36:12 2025
Description:Title: Users can’t access the Q&A feature after joining townhall meetings in Microsoft Viva Engage
User impact: Users can’t access the Q&A feature after joining townhall meetings in Viva Engage.
Current status: We're investigating a potential issue in which users can’t access the Q&A feature after joining townhall meetings in Viva Engage, and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1056087 - Admins are unable to access the Microsoft 365 admin center

Status:postIncidentReviewPublished
Start Time:Tue Apr 15 13:10:00 2025
End Time:Tue Apr 15 15:05:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Tue Apr 22 19:49:41 2025
Root Cause:A failure occurred within the installation process of a backend component that is required to support telemetry delivery and other activities in the Microsoft 365 admin center. As a result, the component was not correctly installed in all the service instances within the infrastructure supporting Microsoft 365 admin center activity that is routed through the Western US data center. When the Microsoft 365 admin center attempted to access the incorrectly installed component, an error message was generated, resulting in impact.
Next Update:N/A

Details

Time:Tue Apr 22 19:40:54 2025
Description:A post-incident report has been published.
Time:Thu Apr 17 19:19:26 2025
Description:A post-incident report has been published.
Time:Tue Apr 15 15:34:10 2025
Description:Title: Admins are unable to access the Microsoft 365 admin center
User impact: Admins may have been unable to access the Microsoft 365 admin center.
Final status: We've verified by monitoring telemetry that redirecting traffic to healthy infrastructure has successfully remediated the issue.
Scope of impact: Admins routed through the affected infrastructure in the US West region may have been unable to access the Microsoft 365 admin center.
Start time: Tuesday, April 15, 2025, at 5:10 PM UTC
End time: Tuesday, April 15, 2025, at 7:05 PM UTC
Root cause: A failure occurred within the installation process of a backend component that is required to support telemetry delivery and other activities in the Microsoft 365 admin center. As a result, the component was not correctly installed in all the service instances within the infrastructure supporting Microsoft 365 admin center activity that is routed through the Western US data center. When the Microsoft 365 admin center attempted to access the incorrectly installed component, an error message was generated, resulting in impact.
Next steps: -For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document
Time:Tue Apr 15 14:51:17 2025
Description:Title: Admins are unable to access the Microsoft 365 admin center
User impact: Admins may be unable to access the Microsoft 365 admin center.
Current status: We've identified a portion of service infrastructure in the West US region that is performing below acceptable thresholds. We're taking the unhealthy infrastructure out of rotation and allowing traffic to flow to healthy infrastructure as a potential mitigation.
Scope of impact: Admin activity routed through the affected infrastructure in the US West region may be unable to access the Microsoft 365 admin center.
Next update by: Tuesday, April 15, 2025, at 8:00 PM UTC
Time:Tue Apr 15 14:18:52 2025
Description:Title: Admins are unable to access the Microsoft 365 admin center
User impact: Admins may be unable to access the Microsoft 365 admin center.
Current status: We're reviewing available diagnostic data and reproducing the issue internally to determine our next steps.
Scope of impact: All admins may be unable to access the Microsoft 365 admin center.
Next update by: Tuesday, April 15, 2025, at 7:30 PM UTC
Time:Tue Apr 15 14:12:09 2025
Description:Title: Admins are unable to access the Microsoft 365 admin center
User impact: Admins may be unable to access the Microsoft 365 admin center.
We're investigating a potential issue with access to the Microsoft 365 admin center and are checking for impact to your organization. We'll provide an update within 30 minutes.

TM1055900 - Users may have been unable to share new files or view previously shared files within Microsoft Teams

Status:postIncidentReviewPublished
Start Time:Tue Apr 15 05:45:00 2025
End Time:Tue Apr 15 09:53:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Tue Apr 22 18:21:14 2025
Root Cause:We were deploying a configuration change, intended to improve the File Preview feature within Microsoft Teams, through our Safe Deployment Processes. The rollout had gone through a staged rollout through our internal rings and had reached a section of public preview/TAP environment, where it had been paused from advancing further whilst we monitored for an extended period and performed further validations. The configuration change was working as expected without any issues and had been active within the public preview/TAP environment for an extended period of time.
Next Update:N/A

Details

Time:Tue Apr 22 18:21:14 2025
Description:A post-incident report has been published.
Time:Thu Apr 17 14:08:19 2025
Description:A post-incident report has been published.
Time:Tue Apr 15 11:03:37 2025
Description:Title: Users may have been unable to share new files or view previously shared files within Microsoft Teams
User impact: Users may have been unable to share new files or view previously shared files within Microsoft Teams.
More info: - Users attempting to share new files may have received the errors 'Oops, something happened with the editor. Reload'. - Users attempting to view previous Teams Chat/Channel messages that contained a shared file may have received the error 'Error encountered while rendering this message' for that specific message.
As a workaround during the issue, users were able to view/access previously uploaded files when accessing from the 'Shared' tab within all Teams clients. Additionally, users were able to upload new files directly into Chats/Channels, or view previously uploaded Files directly from Chats/Channels when using the Teams iOS app.
Final status: After reverting the configuration change, we’ve received multiple reports from previously impacted users that the issue is no longer occurring. Additionally, monitoring telemetry shows error rates have fallen to expected levels.
Scope of impact: Impact was specific to users who were currently configured on public preview or part of the Technology Adoption Program (TAP).
Start time: Tuesday, April 15, 2025, at 9:45 AM UTC
End time: Tuesday, April 15, 2025, at 1:53 PM UTC
Root cause: We were deploying a configuration change, intended to improve the File Preview feature within Microsoft Teams, through our Safe Deployment Processes. The rollout had gone through a staged rollout through our internal rings and had reached a section of public preview/TAP environment, where it had been paused from advancing further whilst we monitored for an extended period and performed further validations. The configuration change was working as expected without any issues and had been active within the public preview/TAP environment for an extended period of time.
On Tuesday, April 15, we started the process to resume the deployment to the remaining sections of the public preview/TAP environment. During the process of reactivating the rollout, there was a manual error that inadvertently changed a specific rollout parameter format. The deployment system generated an error due to this identified parameter format change, and the assumption was made that deployment reactivation process did not continue. However, due to an unexpected behavior of the deployment system, the rollout did in fact go through with configuration change that included incorrect parameter format.
As the specific File parameter was now in a different format (a string, rather than an array), a validation check, made by the Teams client for any request related to File content sharing, failed because the Teams client expected the previous parameter format and was unable to process the result, causing impact.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Tue Apr 15 10:16:22 2025
Description:We've reverted the change and internal testing indicates that the issue is mitigated. Once a user's client gathers the new configuration settings within the next hour, the issue will resolve. We recommend users restart their clients to trigger a configuration refresh and mitigate impact sooner.
This quick update is designed to give the latest information on this issue.
Time:Tue Apr 15 09:59:58 2025
Description:Title: Users may be unable to share new files or view previously shared files within Microsoft Teams
User impact: Users may be unable to share new files or view previously shared files within Microsoft Teams.
More info: - Users attempting to share new files may receive the errors 'Oops, something happened with the editor. Reload'. - Users attempting to view previous Teams Chat/Channel messages that contained a shared file may receive the error 'Error encountered while rendering this message' for that specific message.
As a workaround, users are able to view/access previously uploaded files when accessing from the 'Shared' tab within all Teams clients. Additionally, users are able to upload new files directly into Chats/Channels, or view previously uploaded Files directly from Chats/Channels when using the Teams iOS app.
Current status: We’ve identified a recent change that is likely the cause of the issue as the deployment timelines match with the impact occurring. We’re halting the deployment and we’re starting the process to revert the change.
Scope of impact: Impact is specific to users who are currently configured on public preview or part of the Technology Adoption Program (TAP).
Next update by: Tuesday, April 15, 2025, at 3:30 PM UTC
Time:Tue Apr 15 09:32:36 2025
Description:We've confirmed that users are able to view/access previously uploaded files when accessing from the 'Shared' tab within all Teams clients.
Additionally, users are able to upload new files directly into Chats/Channels, or view previously uploaded Files directly from Chats/Channels when using the Teams iOS app.
This quick update is designed to give the latest information on this issue.
Time:Tue Apr 15 08:14:09 2025
Description:Title: Users may be unable to share new files or view previously shared files within Microsoft Teams
User impact: Users may be unable to share new files or view previously shared files within Microsoft Teams.
More info: - Users attempting to share new files may receive the errors 'Oops, something happened with the editor. Reload'. - Users attempting to view previous Teams Chat/Channel messages that contained a shared file may receive the error 'Error encountered while rendering this message' for that specific message.
Current status: We’re reviewing recent changes made to the File Sharing features to isolate a potential root cause. In parallel, we’re reproducing the issue to gather additional telemetry logs to assist our investigation.
Scope of impact: Impact is specific to a subset of users who are attempting to share files within Microsoft Teams.
Next update by: Tuesday, April 15, 2025, at 2:00 PM UTC
Time:Tue Apr 15 07:38:15 2025
Description:Title: Users may be unable to share new files or view previously shared files within Microsoft Teams
User impact: Users may be unable to share new files or view previously shared files within Microsoft Teams.
More info: - Users attempting to share new files may receive the errors 'Oops, something happened with the editor. Reload' - Users attempting to view previous Teams Chat/Channel messages that contained a shared file may receive the error 'Error encountered while rendering this message' for that specific message.
Current status: We're reviewing service health telemetry to help identify the cause of impact and formulate a remediation plan.
Scope of impact: Impact is specific to a subset of users who are attempting to share files within Microsoft Teams.
Next update by: Tuesday, April 15, 2025, at 1:30 PM UTC
Time:Tue Apr 15 06:56:40 2025
Description:Title: Users may be unable to share new files or view previously shared files within Microsoft Teams
User impact: Users may be unable to share new files or view previously shared files within Microsoft Teams.
More info: - Users attempting to share new files may receive the errors 'Oops, something happened with the editor. Reload' - Users attempting to view previous Teams Chat/Channel messages that contained a shared file may receive the error 'Error encountered while rendering this message' for that specific message.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

MO1059197 - Admins may have experienced delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center

Status:serviceRestored
Start Time:Sun Apr 20 20:00:00 2025
End Time:Tue Apr 22 00:00:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Tue Apr 22 05:19:00 2025
Root Cause:A portion of infrastructure responsible for populating usage reports from the Microsoft 365 admin center became degraded and stopped processing requests as expected.
Next Update:N/A

Details

Time:Tue Apr 22 05:17:05 2025
Description:Title: Admins may have experienced delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center
User impact: Admins may have experienced delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center.
Final status: We've processed the backlog of usage report data and confirmed that impact has been remediated.
Scope of impact: Any admin attempting to receive Microsoft 365 apps usage reports from the Microsoft 365 admin center may have been impacted.
Start time: Monday, April 21, 2025, at 12:00 AM UTC
End time: Tuesday, April 22, 2025, at 4:00 AM UTC
Root cause: A portion of infrastructure responsible for populating usage reports from the Microsoft 365 admin center became degraded and stopped processing requests as expected.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Mon Apr 21 23:30:35 2025
Description:Title: Admins may experience delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center
User impact: Admins may experience delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center.
Current status: We've implemented a fix to improve request processing and are monitoring the usage report data backlog to ensure it catches up. We expect processing to complete by the next scheduled update.
Scope of impact: Any admin attempting to receive Microsoft 365 apps usage reports from the Microsoft 365 admin center may be impacted.
Start time: Monday, April 21, 2025, at 12:00 AM UTC
Root cause: A portion of infrastructure responsible for populating usage reports from the Microsoft 365 admin center became degraded and stopped processing requests as expected.
Next update by: Tuesday, April 22, 2025, at 11:00 AM UTC
Time:Sun Apr 20 23:59:16 2025
Description:Title: Admins may experience delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center
User impact: Admins may experience delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center.
Current status: We've identified an issue in which admins may experience delays in receiving Microsoft 365 apps usage reports from the Microsoft 365 admin center. We've determined that a portion of infrastructure responsible for populating usage reports from the Microsoft 365 admin center became degraded and stopped processing requests as expected. We've deployed a fix to improve how the portion of infrastructure processes the requests and are monitoring as an increase in backlogged data is repopulated to ensure all previous and current usage reports are up to date. We anticipate the backlogged data may be processed and the impact resolved by our next scheduled update.
Scope of impact: Any admin attempting to receive Microsoft 365 apps usage reports from the Microsoft 365 admin center may be impacted.
Start time: Monday, April 21, 2025, at 12:00 AM UTC
Root cause: A portion of infrastructure responsible for populating usage reports from the Microsoft 365 admin center became degraded and stopped processing requests as expected.
Next update by: Tuesday, April 22, 2025, at 5:00 AM UTC

IT1051473 - Some users' managed devices may have been unable to receive configurations, apps, and policies from Microsoft Intune

Status:serviceRestored
Start Time:Mon Apr 7 14:00:00 2025
End Time:Wed Apr 9 03:09:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Mon Apr 21 17:35:25 2025
Root Cause:A recent change made to a portion of Microsoft Intune service infrastructure associated with device check-ins caused impact.
Next Update:N/A

Details

Time:Wed Apr 9 03:34:54 2025
Description:Title: Some users' managed devices may have been unable to receive configurations, apps, and policies from Microsoft Intune
User impact: Users' managed devices may have been unable to receive configurations, apps, and policies from Microsoft Intune.
More info: Additionally, affected devices may have been unable to receive updates to their configuration from Microsoft Intune, or their report compliance status.
Final status: We've successfully implemented the aforementioned fix and received confirmation from your representatives that impact is mitigated.
Scope of impact: Some users who are serviced by the affected infrastructure may have been impacted by this event.
Start time: Monday, April 7, 2025, at 6:00 PM UTC
End time: Wednesday, April 9, 2025, at 7:09 AM UTC
Root cause: A recent change made to a portion of Microsoft Intune service infrastructure associated with device check-ins caused impact.
Next steps: - We're analyzing our Microsoft Intune change processes and procedures, in order to help prevent this problem from happening again.
This is the final update for the event.
Time:Wed Apr 9 02:26:42 2025
Description:Title: Some users' managed devices may be unable to receive configurations, apps, and policies from Microsoft Intune
User impact: Users' managed devices may be unable to receive configurations, apps, and policies from Microsoft Intune.
More info: Additionally, affected devices may be unable to receive updates to their configuration from Microsoft Intune, or their report compliance status.
Current status: We've received customer reports indicating that there's an issue in which some users' managed devices may be unable to receive configurations, apps, and policies from Microsoft Intune. We've identified a recent change made to a portion of Microsoft Intune service infrastructure associated with device check-ins which is causing impact. We're implementing a solution to address the impacting change to mitigate the impact.
Scope of impact: Some users who are serviced by the affected infrastructure may be impacted by this event.
Root cause: A recent change made to a portion of Microsoft Intune service infrastructure associated with device check-ins is causing impact.
Next update by: Wednesday, April 9, 2025, at 8:30 AM UTC

IT1056135 - Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise

Status:serviceRestored
Start Time:Sat Apr 12 18:00:00 2025
End Time:Fri Apr 18 15:00:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Mon Apr 21 17:32:52 2025
Root Cause:A recent service change uncovered a latent code issue, causing impact.
Next Update:N/A

Details

Time:Mon Apr 21 17:32:52 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may have been offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we worked to address the issue, admins in impacted organizations may have been able to circumvent impact by pausing Windows Feature Updates until the code fix was deployed.
The following article has the steps that impacted users could've followed: https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
We've previously deployed a fix to ensure further devices don't encounter impact. Devices which hadn't yet reached the In Progress, Update state with the Install started substate were not impacted. These states could've been checked in "Organization report" if devices were enabled to share diagnostic telemetry.
Final status: We’ve confirmed from service telemetry that this issue is no longer occurring. We advise that previously affected admins remove the pause the on Windows Feature Updates gradually, rather than all at once, to experience full impact remediation, and contact a support representative should any issues persist.
Scope of impact: Some users that leverage Windows desktop devices may have been impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
End time: Friday, April 18, 2025, at 7:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next steps: - We’re reviewing our service change validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
Time:Fri Apr 18 16:37:29 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
We've previously deployed a fix to ensure further devices don't encounter impact. Devices which haven't yet reached the In Progress, Update state with the Install started substate will not be impacted. These states can be checked in "Organization report" if devices are enabled to share diagnostic telemetry.
Current status: We've confirmed that after the repair job, no new devices are expected to install unintended Windows 11 updates. We recommend that admins remove the pause on Windows Feature Updates for a few devices to ensure that it's working as expected, before removing the pause for the remaining devices. Devices that already received the upgrade instruction may need intervention by the admin. In Parallel, we're continuing to monitor our Windows update telemetry to ensure that the impact is remediated as expected.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Monday, April 21, 2025, at 10:00 PM UTC
Time:Fri Apr 18 12:26:18 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
We've previously deployed a fix to ensure further devices don't encounter impact. Devices which haven't yet reached the In Progress, Update state with the Install started substate will not be impacted. These states can be checked in "Organization report" if devices are enabled to share diagnostic telemetry.
Current status: We've completed the deployment of the repair job and are monitoring our service health telemetry to confirm that the impact is remediated.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Friday, April 18, 2025, at 10:00 PM UTC
Time:Thu Apr 17 20:50:16 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
We've previously deployed a fix to ensure further devices don't encounter impact. Devices which have not yet reached the In Progress, Update state with the Install started substate will not be impacted. These states can be checked in "Organization report" if devices are enabled to share diagnostic telemetry.
Current status: We validated that the repair job is remediating the impact for affected users. We've initiated the deployment of the fix for the remaining impacted infrastructure and are monitoring its progress to validate it completes successfully.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Friday, April 18, 2025, at 6:00 PM UTC
Time:Thu Apr 17 15:14:39 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
We've previously deployed a fix to ensure further devices don't encounter impact. Devices which have not yet reached the In Progress, Update state with the Install started substate will not be impacted. These states can be checked in "Organization report" if devices are enabled to share diagnostic telemetry.
Current status: We've initiated our repair job to a subset of affected users for additional validation. We're monitoring as this repair job continues, and will reach out to a subset of users to confirm we're seeing remediation as expected before proceeding with the broader repair.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Friday, April 18, 2025, at 2:00 AM UTC
Time:Thu Apr 17 02:22:10 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
Note that devices which have already erroneously received the Windows 11 upgrade will need to be manually rolled back to the correct Windows version.
Current status: We're continuing to work on preparing a repair job to restore devices that were previously affected by this issue. Due to the complexity of the involved configuration, we're anticipating it may take some additional time before we can provide a timeline for its deployment.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Thursday, April 17, 2025, at 8:00 PM UTC
Time:Wed Apr 16 12:30:05 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
Note that devices which have already erroneously received the Windows 11 upgrade will need to be manually rolled back to the correct Windows version.
Current status: We've completed the deployment of our fix to ensure further devices don’t become impacted by this issue. Having deployed this fix, we're now preparing a repair job for devices which were targeted despite being excluded by Microsoft Intune policies to ensure they no longer receive the offer. Reiterating what’s been noted in the more info section of this communication, devices which have already upgraded to the Windows 11 upgrade will need to be manually rolled back to the correct Windows version.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Thursday, April 17, 2025, at 8:00 AM UTC
Time:Wed Apr 16 00:47:20 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
Note that devices which have already erroneously received the Windows 11 upgrade will need to be manually rolled back to the correct Windows version.
Current status: We've completed the development, testing and validation process for our targeted code fix and are deploying it in an effort to prevent additional impact and resolve the code issue.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Wednesday, April 16, 2025, at 6:00 PM UTC
Time:Tue Apr 15 22:33:33 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
More info: While we work to address the issue, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates until the code fix has been developed, tested, and deployed.
The following article has the steps that impacted users can follow:
https://learn.microsoft.com/en-us/intune/intune-service/protect/windows-10-update-rings#pause
Current status: We're continuing our efforts to develop and validate a targeted code fix for this issue. In the interim, admins in impacted organizations may be able to circumvent impact by pausing Windows Feature Updates as detailed in the "More info" section of this communication.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Wednesday, April 16, 2025, at 7:00 AM UTC
Time:Tue Apr 15 20:57:48 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
Current status: Our analysis of the recent change that is resulting in impact is ongoing. This process will allow us to pinpoint the most expedient way to develop, test and implement a code fix.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Wednesday, April 16, 2025, at 6:00 AM UTC
Time:Tue Apr 15 18:33:20 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
Current status: We've identified a recent service change uncovered a latent code issue, causing impact. We're continuing to analyze the recent change, so that we can determine the next steps in developing a code fix.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Start time: Saturday, April 12, 2025, at 10:00 PM UTC
Root cause: A recent service change uncovered a latent code issue, causing impact.
Next update by: Wednesday, April 16, 2025, at 1:00 AM UTC
Time:Tue Apr 15 16:47:51 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
Current status: While we continue to review recent services changes, we're analyzing the request traffic flow to narrow down the source of the impact.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Next update by: Tuesday, April 15, 2025, at 11:00 PM UTC
Time:Tue Apr 15 15:16:46 2025
Description:Title: Some users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise
User impact: Users' devices may be offered a Windows 11 upgrade despite Microsoft Intune policies being configured otherwise.
Current status: We're reviewing recent service changes to determine whether any may be contributing to the impact.
Scope of impact: Some users that leverage Windows desktop devices may be impacted.
Next update by: Tuesday, April 15, 2025, at 9:00 PM UTC

EX1052961 - Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online

Status:serviceRestored
Start Time:Fri Apr 4 04:00:00 2025
End Time:Sat Apr 19 22:10:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Sat Apr 19 22:31:43 2025
Root Cause:A recent change intended to assign identities to users who utilized the dependent API contained a bug which resulted in the code failing to parse the user agent stream, which then resulted in an error.
Next Update:N/A

Details

Time:Sat Apr 19 22:31:43 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may have been unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may have been able to bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Final status: We've validated through our service health telemetry that our code fix has completed its deployment and has alleviated impact as expected.
Scope of impact: Impact was specific to admins who were served through the affected infrastructure and who were attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
End time: Sunday, April 20, 2025, at 2:10 AM UTC
Root cause: A recent change intended to assign identities to users who utilized the dependent API contained a bug which resulted in the code failing to parse the user agent stream, which then resulted in an error.
Next steps: - We're analyzing the recent change to the API to determine how to bolster our update practices to avoid impact like this in the future.
This is the final update for the event.
Time:Wed Apr 16 22:41:06 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Current status: The ongoing fix deployment has saturated 60 percent of the affected environment, and we expect that some users may begin to experience remediation incrementally as it nears completion. Additionally, we anticipate that the saturation process will be completed by our next scheduled update.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Estimated time to resolve: We anticipate that impact will be remediated by Sunday, April 20, 2025, at 4:00 AM UTC.
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Sunday, April 20, 2025, at 4:00 AM UTC
Time:Sun Apr 13 09:27:44 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Current status: We’ve internally validated the fix and anticipate it’ll complete deployment by Wednesday, April 16, 2025.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Thursday, April 17, 2025, at 4:00 AM UTC
Time:Sat Apr 12 21:16:44 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Current status: Our internal build deployment process is ongoing. Once we've deployed the fix to our internal environments and completed a thorough validation thereof to ensure no adverse effects, we'll proceed with its deployment to the broader impacted environment. We'll provide an updated completion timeline as one becomes available.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Sunday, April 13, 2025, at 3:00 PM UTC
Time:Sat Apr 12 10:26:04 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Current status: We’re continuing to deploy our fix to our internal testing environment to validate its efficacy and anticipate its completion by our next scheduled update.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Sunday, April 13, 2025, at 3:00 AM UTC
Time:Fri Apr 11 21:59:50 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
More info: Affected admins may bypass the impact by running the Get-FederatedOrganizationIdentifier cmdlet.
Current status: We’re working on deploying our fix to our internal testing environment to validate its efficacy. We’re aiming to provide a timeline for deployment by our next scheduled update. In the meantime, affected admins can run the Get-FederatedOrganizationIdentifier cmdlet as a workaround while our fix undergoes testing and validation.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Saturday, April 12, 2025, at 3:00 PM UTC
Time:Fri Apr 11 11:27:56 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Current status: We've further confirmed that a recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error. We're developing a code fix to resolve the issue, which will be deployed to our internal testing environment for validation to confirm efficacy. We anticipate this testing will complete by our next scheduled update, at which time we expect to have a timeline for the deployment to the affected environment.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Start time: Friday, April 4, 2025, at 8:00 AM UTC
Root cause: A recent change to the API, intended to assign identities to users utilizing the API and assign a "user agent" to them, contains a bug which results in code failing to parse the user agent stream, resulting in an error.
Next update by: Saturday, April 12, 2025, at 3:00 AM UTC
Time:Fri Apr 11 00:02:34 2025
Description:Title: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins may be unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Current status: We've identified that a recent change to an API utilized by the specific cmdlet may be resulting in impact. We're moving to roll out a targeted fix to restore the expected API flow and will provide a timeline for remediation as it becomes available.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Next update by: Friday, April 11, 2025, at 4:00 PM UTC
Time:Thu Apr 10 23:11:43 2025
Description:Title: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Current status: We're continuing to review the contextual details provided by your organization to better understand the impacted scenario and determine our next investigative steps.
Scope of impact: Your organization is affected by this event, and admins attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online are impacted.
Next update by: Friday, April 11, 2025, at 5:30 AM UTC
Time:Thu Apr 10 22:17:23 2025
Description:Title: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Current status: We're reviewing details provided in your organization's support case to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is affected by this event, and admins attempting to run the Get-FederationInformation PowerShell cmdlet in Exchange Online are impacted.
Next update by: Friday, April 11, 2025, at 3:30 AM UTC
Time:Thu Apr 10 22:06:09 2025
Description:Title: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online
User impact: Admins are unable to run the Get-FederationInformation PowerShell cmdlet in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

MP1057231 - Admins experience delayed webhook notifications when using the Office 365 Management API

Status:serviceRestored
Start Time:Sun Mar 23 20:00:00 2025
End Time:Thu Apr 17 11:15:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Fri Apr 18 01:34:28 2025
Root Cause:A number of duplicate records contained within a portion of service infrastructure that facilitates the functionality of Office 365 Management API were causing impact.
Next Update:N/A

Details

Time:Fri Apr 18 01:34:28 2025
Description:Title: Admins experience delayed webhook notifications when using the Office 365 Management API
User impact: Admins experienced delayed webhook notifications when using the Office 365 Management API.
More info: This issue affected admins to a different degree. Some admins may have had minimal delays in receiving webhook notifications while others may not have received any webhook notification generated after Monday, March 24, 2025. While there was a delay in receiving these webhook notifications, as a workaround, affected admins could have used the API to directly call back records that were available for download.
Final status: We've verified through internal monitoring and testing with affected admins that impact is remediated.
Scope of impact: Your organization was affected by this event, and admins attempting to receive Office 365 Management API webhook notifications were impacted.
Start time: Monday, March 24, 2025, at 12:00 AM UTC
End time: Thursday, April 17, 2025, at 3:15 PM UTC
Root cause: A number of duplicate records contained within a portion of service infrastructure that facilitates the functionality of Office 365 Management API were causing impact.
Next steps: - We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the underlying issue and identify changes we can implement to better prevent similar impact in the future.
This is the final update for the event.
Time:Thu Apr 17 16:11:40 2025
Description:Title: Admins experience delayed webhook notifications when using the Office 365 Management API
User impact: Admins experience delayed webhook notifications when using the Office 365 Management API.
More info: This issue affects admins to a different degree. Some admins may have minimal delays in receiving webhook notifications while others may not be receiving any webhook notification generated after Monday, March 24, 2025. While there is a delay in receiving these webhook notifications, as a workaround, affected admins can use the API to directly call back records that are available for download.
Current status: We're continuing to test with affected admins to validate if our fix has fully remediated the impact.
Scope of impact: Your organization is affected by this event, and admins attempting to receive Office 365 Management API webhook notifications are impacted.
Root cause: A number of duplicate records contained within a portion of service infrastructure that facilitates the functionality of Office 365 Management API are causing impact.
Next update by: Friday, April 18, 2025, at 7:00 AM UTC
Time:Thu Apr 17 12:59:38 2025
Description:Title: Admins experience delayed webhook notifications when using the Office 365 Management API
User impact: Admins experience delayed webhook notifications when using the Office 365 Management API.
More info: This issue affects admins to a different degree. Some admins may have minimal delays in receiving webhook notifications while others may not be receiving any webhook notification generated after Monday, March 24, 2025. While there is a delay in receiving these webhook notifications, as a workaround, affected admins can use the API to directly call back records that are available for download.
Current status: We've identified a number of duplicate records contained within a portion of service infrastructure that facilitates the functionality of Office 365 Management API that are causing webhook notifications to be delayed. We've deployed our fix to address the duplicate records, and we're testing with affected admins to confirm if the issue is resolved.
Scope of impact: Your organization is affected by this event, and admins attempting to receive Office 365 Management API webhook notifications are impacted.
Root cause: A number of duplicate records contained within a portion of service infrastructure that facilitates the functionality of Office 365 Management API are causing impact.
Next update by: Thursday, April 17, 2025, at 9:00 PM UTC
Time:Thu Apr 17 07:22:07 2025
Description:Title: Some admins in North America may experience delayed notifications when using Office 365 Management API webhooks
User impact: Admins using Office 365 Management API may experience delayed Webhook notifications.
More info: While there is a delay in receiving these webhook notifications, as a workaround, admins can use the API to directly call back records that are available for download.
Current status: We're validating a fix that we intend to deploy to the affected infrastructure by the time of our next scheduled update.
Scope of impact: Admins using Office 365 Management API webhooks may be impacted by this event.
Next update by: Thursday, April 17, 2025, at 5:00 PM UTC
Time:Thu Apr 17 05:21:33 2025
Description:Title: Some admins in North America may experience delayed notifications when using Office 365 Management API webhooks
User impact: Admins using Office 365 Management API may experience delayed Webhook notifications.
More info: While there is a delay in receiving these webhook notifications, as a workaround, admins can use the API to directly call back records that are available for download.
Current status: We're investigating an issue causing delays to Webhook notifications for some admins using Office 365 Management API. We've identified a latency build up and are working on remediating the issue.
Scope of impact: Admins using Office 365 Management API webhooks may be impacted by this event.
Next update by: Thursday, April 17, 2025, at 12:30 PM UTC