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 Tue May 13 02:00:12 2025.
CR1065792 - Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
| Status: | restoringService |
|---|
| Start Time: | Thu Mar 20 20:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Dynamics 365 Apps |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 12 19:23:49 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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.
|
|---|
|
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.
|
|---|
|
TM1072005 - Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
| Status: | serviceDegradation |
|---|
| Start Time: | Mon May 12 07:54:30 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon May 12 11:38:59 2025 |
|---|
| Root Cause: | A recent infrastructure migration introduced a misconfiguration, which has led to impact. |
|---|
| Next Update: | Tuesday, May 13, 2025, at 10:00 AM UTC |
|---|
|
Details
| 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
|
|---|
|
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.
|
|---|
|
SP1070801 - Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
| Status: | serviceRestored |
|---|
| 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: | Fri May 9 18:10:44 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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
Preliminary root cause: 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'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| 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.
|
|---|
|
TM1047160 - Some users may see a draft chat message to a call queue in Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Mar 17 22:13:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 9 17:08:41 2025 |
|---|
| Root Cause: | A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact. |
|---|
| Next Update: | Friday, May 16, 2025, at 11:00 PM UTC |
|---|
|
Details
| 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.
|
|---|
|
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: | Fri May 9 16:17:04 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: | Tuesday, May 13, 2025, at 8:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
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.
|
|---|
|
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: | Thu May 8 14:02:19 2025 |
|---|
| Root Cause: | A small section of AFD infrastructure started to perform below acceptable thresholds. We have identified high Central Processing Unit (CPU) utilization as a potential contributing factor that resulted in impact. Further investigations are ongoing and more detail will be provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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 of AFD infrastructure started to perform below acceptable thresholds. We have identified high Central Processing Unit (CPU) utilization as a potential contributing factor that resulted in impact. Further investigations are ongoing and more detail will be provided within the Post-Incident Report.
Next steps:
- We're isolating the source of the high CPU utilization so that action items can be identified to prevent impact reoccurring.
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.
|
|---|
|
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 7 23:24:45 2025 |
|---|
| Root Cause: | A recent deployment incorrectly enabled this feature in the affected environment. |
|---|
| Next Update: | Thursday, May 22, 2025, at 5:00 AM UTC |
|---|
|
Details
| 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
|
|---|
|
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.
|
|---|
|
TM1035246 - Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Mar 18 10:38:30 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 7 06:58:55 2025 |
|---|
| 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: | Wednesday, May 14, 2025, at 11:00 AM UTC |
|---|
|
Details
| 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.
|
|---|
|
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: | OneDrive for Business |
|---|
| 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.
|
|---|
|
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: | Wed Apr 30 00:48:50 2025 |
|---|
| Root Cause: | Changes within a recent regularly scheduled service update are resulting in impact. |
|---|
| Next Update: | Wednesday, May 14, 2025, at 5:30 AM UTC |
|---|
|
Details
| 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.
|
|---|
|
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
|
|---|
|
TM1040294 - Users may be unable to upload some background images during Microsoft Teams meetings
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 17 22:13:00 2025 |
|---|
| End Time: | Thu Apr 17 13:55:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Apr 17 17:28:47 2025 |
|---|
| Root Cause: | A recent change instituted a restriction on image size for background image uploads in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Apr 17 17:25:24 2025 |
|---|
| Description: | Title: Users may be unable to upload some background images during Microsoft Teams meetings
User impact: Users may have been unable to upload some background images during Microsoft Teams meetings.
More info: When attempting to upload a background image where one of the dimensions exceeded 1800 pixels, users received an error message stating, "invalid image size" and the upload failed. For example, an image sized 1920x1080 would encounter this issue, an image sized 1080x1920 was also impacted, but an image sized 1750x1750 wasn’t affected. Users could've avoided this issue by resizing the desired image to below 1800 pixels on either dimension.
Final status: We've confirmed that the fix has completed deployment, and after monitoring the service, we've verified that this action has successfully remediated the problem
Scope of impact: This issue may have affected any user attempting to upload a background image where one of the dimensions exceeded 1800 pixels during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
End time: Thursday, April 17, 2025, at 5:55 PM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next steps:
- We're investigating how the recent change that restricted background image uploads in Microsoft Teams introduced a code regression that wasn’t caught during pre-deployment testing, and we're working to improve our validation processes to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 15 16:56:10 2025 |
|---|
| Description: | Title: Users may be unable to upload some background images during Microsoft Teams meetings
User impact: Users may be unable to upload some background images during Microsoft Teams meetings.
More info: When attempting to upload a background image where one of the dimensions exceeds 1800 pixels, users receive an error message stating, "invalid image size" and the upload fails. For example, an image sized 1920x1080 will encounter this issue, an image sized 1080x1920 is also impacted, but an image sized 1750x1750 is not affected. Users can avoid this issue by resizing the desired image to below 1800 pixels on either dimension.
Current status: The monitoring of our fix has determined that its deployment will require a bit longer than previously expected to complete; however, a majority of impacted environments and most users should no longer be impacted. Our updated fix deployment timeline expect that the deployment will have completed and for impact to be remediated by our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image where one of the dimensions exceeds 1800 pixels during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Thursday, April 17, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Apr 14 16:48:39 2025 |
|---|
| Description: | Title: Users may be unable to upload some background images during Microsoft Teams meetings
User impact: Users may be unable to upload some background images during Microsoft Teams meetings.
More info: When attempting to upload a background image where one of the dimensions exceeds 1800 pixels, users receive an error message stating, "invalid image size" and the upload fails. For example, an image sized 1920x1080 will encounter this issue, an image sized 1080x1920 is also impacted, but an image sized 1750x1750 is not affected. Users can avoid this issue by resizing the desired image to below 1800 pixels on either dimension.
Current status: We've resolved the unrelated issue within our deployment pipeline and have resumed the deployment of the fix to the remaining impacted environments. We anticipate the deployment will complete and the impact will be remediated by our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image where one of the dimensions exceeds 1800 pixels during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Tuesday, April 15, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Apr 10 17:47:52 2025 |
|---|
| Description: | Title: Users may be unable to upload some background images during Microsoft Teams meetings
User impact: Users may be unable to upload some background images during Microsoft Teams meetings.
More info: When attempting to upload a background image where one of the dimensions exceeds 1800 pixels, users receive an error message stating, "invalid image size" and the upload fails. For example, an image sized 1920x1080 will encounter this issue, an image sized 1080x1920 is also impacted, but an image sized 1750x1750 is not affected. Users can avoid this issue by resizing the desired image to below 1800 pixels on either dimension.
Current status: We've verified that the fix has completed deployment in the majority of impacted environments and most users should no longer be affected. However, for the remaining affected users, we've identified an unrelated issue within our deployment pipeline, which we're working to resolve before the fix can continue propagating. Once resolved, we’ll provide an updated resolution timeline.
Scope of impact: This issue may affect any user attempting to upload a background image where one of the dimensions exceeds 1800 pixels during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, April 14, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Apr 9 17:55:58 2025 |
|---|
| Description: | Title: Users may be unable to upload some background images during Microsoft Teams meetings
User impact: Users may be unable to upload some background images during Microsoft Teams meetings.
More info: When attempting to upload a background image where one of the dimensions exceeds 1800 pixels, users receive an error message stating, "invalid image size" and the upload fails. For example, an image sized 1920x1080 will encounter this issue, an image sized 1080x1920 is also impacted, but an image sized 1750x1750 is not affected. Users can avoid this issue by resizing the desired image to below 1800 pixels on either dimension.
Current status: We've updated the Title, User impact, More info, and Scope of impact sections to accurately reflect the exact impact scenario. Although it's taking a bit longer than previously anticipated, the deployment of the fix is 80 percent complete and most users should be experiencing remediation at this time. We expect it will complete deployment by our next scheduled communications update, at which time we'll test to confirm that impact is remediated.
Scope of impact: This issue may affect any user attempting to upload a background image where one of the dimensions exceeds 1800 pixels during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Thursday, April 10, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Apr 8 17:41:08 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: We've initiated the deployment for our previously mentioned fix. We anticipate that the deployment will be complete by our next scheduled communications update, at which time we'll test to confirm that impact is remediated.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Wednesday, April 9, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Apr 7 17:14:17 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: We've resolved the issues blocking the deployment of our fix and are preparing to begin the deployment. We anticipate being able to provide a timeline for the completion of the fix deployment, and impact resolution, with our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Tuesday, April 8, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Apr 3 17:11:20 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: Our work to address the issues preventing deployment of our fix is ongoing, and we expect we'll have these cleared by our next scheduled update, allowing the deployment to begin.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, April 7, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Apr 2 17:15:21 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: We're continuing to address issues unrelated to this impact which are preventing the deployment of our fix. Once these issues have been addressed, we'll provide a timeline for the deployment of our fix.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Thursday, April 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Apr 1 17:21:58 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: While we've partially addressed the issues preventing the deployment of the fix from initiating, we're continuing to address the remaining issue so our deployment can progress.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Wednesday, April 2, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 31 17:40:02 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating, "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: We've identified an unrelated issue is preventing the deployment of the fix from initiating. We're working to resolve the unrelated issue and anticipate the fix will be ready for deployment by our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Tuesday, April 1, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Mar 26 16:37:58 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: Our fix to revert the strict size check logic has been validated and we're expecting deployment to start by Monday, March 31, 2025, which is when we anticipate providing an updated timeline for impact remediation.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, March 31, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 25 17:17:10 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We're completing the final testing and validations of our fix before initiating its deployment. We expect to provide a timeline for the fix deployment with our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Wednesday, March 26, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 17:48:04 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We've developed a fix for the solution to remove the restriction on background image size in order to remediate impact for all users. We're working to confirm a timeline for our fix deployment to provide with our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Tuesday, March 25, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 15:52:14 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We've identified a recent change instituted a restriction on image size for background image uploads in Microsoft Teams. While we work towards developing a fix for the issue, impacted users can manually resize their background images to "1800x1800" height and width dimensions, or smaller, for the upload to complete successfully.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, March 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 13:36:42 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
Current status: We're reviewing user reports of the problem while collecting internal service data for this scenario to isolate what may be causing the impact.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Next update by: Monday, March 24, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 12:38:39 2025 |
|---|
| Description: | Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
DZ1052047 - Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 24 16:28:00 2025 |
|---|
| End Time: | Wed Apr 9 21:02:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Apr 17 12:16:37 2025 |
|---|
| Root Cause: | A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Apr 17 12:16:37 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may have seen an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may have been shown as "Unknown" and User Submissions may have been shown as "Not submitted to Microsoft"
Final status: We've reconfirmed that the completion of our fix deployment successfully remediated impact for all new submissions.
Scope of impact: Impact may have occurred for some users that attempted to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
End time: Thursday, April 10, 2025, at 1:02 AM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next steps:
- We're reviewing our change 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: | Wed Apr 16 12:49:19 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may be shown as "Unknown" and User Submissions may be shown as "Not submitted to Microsoft"
Current status: Following the deployment of our fix, we've determined that the problem is no longer occurring for new submissions by admins; however, the subset of submissions that are showing an unexpected status will require processing before impact has been remediated. We're monitoring this process, which we're expecting will have completed and remediated the impact by our next scheduled update.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Thursday, April 17, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Apr 14 12:21:09 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may be shown as "Unknown" and User Submissions may be shown as "Not submitted to Microsoft"
Current status: Due to delays, our fix has completed testing and validation in our internal testing environment but hasn’t yet completed deployment to the broader impacted environment. We anticipate that the fix will complete by our next scheduled update, and we’re monitoring its progress as it continues.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Wednesday, April 16, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 11 12:56:56 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may be shown as "Unknown" and User Submissions may be shown as "Not submitted to Microsoft"
Current status: Deployment of the fix has been halted and limited to our testing infrastructure for further validation prior to its deployment to the impacted environment, which we expect will begin and complete over the weekend and should resolve this issue for all affected users by Monday, April 14, 2025.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Monday, April 14, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Apr 10 14:46:21 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may be shown as "Unknown" and User Submissions may be shown as "Not submitted to Microsoft"
Current status: We've completed the release of a fix to prevent future impact and initiated processing of affected submissions to fully remediate this issue. We expect to have a mitigation timeline by the next scheduled update.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Friday, April 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Apr 10 10:37:23 2025 |
|---|
| Description: | Title: Some users may see an unexpected status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unexpected status for submissions in Microsoft Defender for Office 365.
More info: Admin Submissions status' may be shown as "Unknown" and User Submissions may be shown as "Not submitted to Microsoft"
Current status: We’re continuing to work on reprocessing the affected submission alerts from the impact window to fully resolve the impact and anticipate to have a remediation timeline by our next scheduled update.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Thursday, April 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Apr 10 00:32:04 2025 |
|---|
| Description: | Title: Some users may see an unknown status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unknown status for submissions in Microsoft Defender for Office 365.
Current status: Our fix has completed propagating, and our service health telemetry indicates that the affected environments are healthy, thus resuming the submission processing. We’re now working on reprocessing the affected submission alerts from the impact window to fully resolve the impact and are aiming to provide a timeline for this by our next scheduled update.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Thursday, April 10, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Apr 9 16:49:14 2025 |
|---|
| Description: | Title: Some users may see an unknown status for submissions in Microsoft Defender for Office 365
User impact: Users may see an unknown status for submissions in Microsoft Defender for Office 365.
Current status: Our monitoring alert systems identified an issue where some users may see an unknown status for submissions in Microsoft Defender for Office 365. Upon investigation, we determined that a recent service change to update a portion of the infrastructure supporting submissions resulted in impact. We've developed a fix that is currently propagating through the affected environments. As it progresses, some users may begin to see improvement. Once the fix is fully applied, we'll reprocess all submission alerts that were affected during the impact window.
Scope of impact: Impact may occur for some users that attempt to make submissions in Microsoft Defender for Office 365.
Start time: Monday, March 24, 2025, at 8:28 PM UTC
Root cause: A recent service change to update a portion of infrastructure that supports submissions in Microsoft Defender for Office 365 resulted in impact.
Next update by: Thursday, April 10, 2025, at 6:00 AM UTC
|
|---|
|
EX1056984 - Users may experience intermittent errors when leveraging REST to connect to Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 16 19:20:00 2025 |
|---|
| End Time: | Wed Apr 16 21:13:20 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 21:15:21 2025 |
|---|
| Root Cause: | A recent authentication change intended to improve connections leveraging REST caused impact to Exchange Online. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 21:13:33 2025 |
|---|
| Description: | Title: Users may experience intermittent errors when leveraging REST to connect to Exchange Online
User impact: Users may have experienced intermittent errors when leveraging REST to connect to Exchange Online.
Final status: We identified that a recent authentication change intended to improve connections leveraging Representational State Transfer (REST) caused intermittent impact to Exchange Online. We confirmed through our monitoring that the telemetry recovered and that the impact was remediated.
Scope of impact: This issue may have intermittently impacted any user utilizing REST to connect to Exchange Online.
Start time: Wednesday, April 16, 2025, at 11:20 PM UTC
End time: Wednesday, April 16, 2025, at 11:40 PM UTC
Root cause: A recent authentication change intended to improve connections leveraging REST caused impact to Exchange Online.
Next steps:
- We're reviewing our change rollout process to find ways to prevent similar impact from occurring during future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 16 19:48:19 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.
|
|---|
|
EX1056390 - Some users may see the file name of email attachments appear incorrectly in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 16 00:42:10 2025 |
|---|
| End Time: | Wed Apr 16 14:05:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 20:18:59 2025 |
|---|
| Root Cause: | A recent change intended to optimize the process of fetching file names resulted in incorrect files names being returned. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 14:52:39 2025 |
|---|
| Description: | Title: Some users may see the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users may have seen the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments could've appeared as random letters and numbers.
Final status: We’ve successfully reverted the offending change and confirmed from service telemetry that this issue is resolved.
Start time: Monday, April 14, 2025, at 4:00 PM UTC
End time: Wednesday, April 16, 2025, at 6:05 PM UTC
Scope of impact: Some users' email attachments in Outlook on the web may have been impacted.
Root cause: A recent change intended to optimize the process of fetching file names resulted in incorrect files names being returned.
Next steps:
- We’re reviewing our 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: | Wed Apr 16 13:45:35 2025 |
|---|
| Description: | Title: Some users are seeing the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users are seeing the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments may appear as random letters and numbers.
Current status: We’ve determined that a recent change intended to optimize the process of fetching file names resulted in incorrect files names being returned. We're reverting the offending change to remediate the impact and expect this process to complete to resolve this issue by our next scheduled update.
Start time: Monday, April 14, 2025, at 4:00 PM UTC
Scope of impact: Your organization is affected by this event, and some users' email attachments in Outlook on the web are impacted.
Root cause: A recent change intended to optimize the process of fetching file names resulted in incorrect files names being returned.
Next update by: Wednesday, April 16, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 16 05:01:18 2025 |
|---|
| Description: | Title: Some users are seeing the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users are seeing the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments may appear as random letters and numbers.
Current status: We're continuing our analysis of network trace logs provided by affected users to isolate the root cause and determine a remediation plan.
Scope of impact: Your organization is affected by this event, and some users' email attachments in Outlook on the web are impacted.
Next update by: Wednesday, April 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Apr 16 01:39:16 2025 |
|---|
| Description: | Title: Some users are seeing the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users are seeing the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments may appear as random letters and numbers.
Current status: We're continuing to analyze the Fiddler trace logs to aid in the root cause investigation and help establish a fix.
Scope of impact: Your organization is affected by this event, and some users' email attachments in Outlook on the web are impacted.
Next update by: Wednesday, April 16, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Apr 16 01:00:37 2025 |
|---|
| Description: | Title: Some users are seeing the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users are seeing the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments may appear as random letters and numbers.
Current status: We're reviewing Fiddler trace logs provided by your representatives to assist with the investigation and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users' email attachments in Outlook on the web are impacted.
Next update by: Wednesday, April 16, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Apr 16 00:49:23 2025 |
|---|
| Description: | Title: Some users are seeing the file name of email attachments appear incorrectly in Outlook on the web
User impact: Users are seeing the file name of email attachments appear incorrectly in Outlook on the web.
More info: Specifically, the file name of attachments may appear as random letters and numbers.
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.
|
|---|
|
EX1051697 - Admins may be unable to access the Exchange admin center (EAC)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Apr 9 05:50:00 2025 |
|---|
| End Time: | Wed Apr 9 11:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Apr 16 14:28:19 2025 |
|---|
| Root Cause: | For the impacted URL (admin.exchange.microsoft.com), a specific Data Protection Key (DPK), used to encrypt and decrypt the token cookies, was inadvertently removed from Azure Blob Storage. This was caused by an accidental miss within the scoping process mechanism when attempting to remove the DPK from a test environment as part of routine engineering actions. This miss meant that the DPK was inadvertently also removed from part of the production environment. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 14:28:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Apr 11 13:37:45 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Apr 9 12:58:10 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may have been unable to access the Exchange admin center (EAC).
More info: Admins may have received the following error "HTTP Error 500".
As a workaround, admins were able to access the EAC using https://admin.cloud.microsoft/exchange#/.
Final status: We've verified by monitoring telemetry that our corrective steps to re-direct the impacted URL traffic to a working URL have successfully remediated the issue.
Scope of impact: This issue could have affected any admin accessing the Exchange admin center.
Start time: Wednesday, April 9, 2025, at 9:50 AM UTC
End time: Wednesday, April 9, 2025, at 3:30 PM UTC
Root cause: For the impacted URL (admin.exchange.microsoft.com), a specific Data Protection Key (DPK), used to encrypt and decrypt the token cookies, was inadvertently removed from Azure Blob Storage. This was caused by an accidental miss within the scoping process mechanism when attempting to remove the DPK from a test environment as part of routine engineering actions. This miss meant that the DPK was inadvertently also removed from part of the production environment.
As the DPK was removed, request tokens could not be decrypted, this caused the authentication request to EAC to fail, resulting in 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: | Wed Apr 9 12:00:25 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may be unable to access the Exchange admin center (EAC).
More info: Admins may receive the following error "HTTP Error 500".
As a workaround, we've confirmed admins are able to access the EAC using https://admin.cloud.microsoft/exchange#/.
Current status: We've identified a potential authentication issue in a specific URL path that is resulting in impact. We've deployed a configuration change to re-direct the impacted URL traffic to a working URL and are monitoring telemetry to confirm mitigation.
Scope of impact: This issue may affect any admin accessing the Exchange admin center.
Next update by: Wednesday, April 9, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 9 11:47:16 2025 |
|---|
| Description: | We've identified a potential authentication issue in a specific URL path and are working to mitigate the issue by re-directing the impacted URL traffic to a working URL.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Apr 9 10:58:13 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may be unable to access the Exchange admin center (EAC).
More info: Admins may receive the following error "HTTP Error 500".
As a workaround, we've confirmed some admins are able to access the EAC using https://admin.cloud.microsoft/exchange#/.
Current status: We’re currently investigating routing logs to identify the root cause as well as testing a potential mitigation by re-routing user requests to working URLs.
Scope of impact: The scope is under investigation, but at this time appears to be a global issue.
Next update by: Wednesday, April 9, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Apr 9 09:26:55 2025 |
|---|
| Description: | We've reproduced the issue internally and gathered additional diagnostic data to assist our troubleshooting.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Apr 9 09:06:38 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may be unable to access the Exchange admin center (EAC).
More info: Admins may receive the following error "HTTP Error 500".
We've received reports that admins are able to access the EAC using https://admin.cloud.microsoft/exchange#/ as a workaround. We're still verifying this and will provide validation on this shortly.
Current status: We've identified increases in error spikes and are investigating these further. Additionally, we're reviewing recent changes made to the service as a potential root cause.
Scope of impact: The scope is under investigation, but at this time appears to be a global issue.
Next update by: Wednesday, April 9, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Apr 9 07:59:30 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may be unable to access the Exchange admin center (EAC).
More info: Admins may receive the following error "HTTP Error 500".
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 admins who are served through the affected infrastructure.
Next update by: Wednesday, April 9, 2025, at 2:00 PM UTC
|
|---|
|
IT1055411 - Admins may see inactive devices showing as active in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 10 08:30:00 2025 |
|---|
| End Time: | Wed Apr 16 11:28:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 13:28:59 2025 |
|---|
| Root Cause: | An increase in device deactivations had caused a section of Microsoft Intune infrastructure to perform below manageable performance thresholds, causing update requests for the device status in the Microsoft Intune admin center to queue, which gave the impression that the devices were still active, when in fact they weren't. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 13:28:59 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may have seen inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacted devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The affected devices weren’t active, but they were appearing as active in the Microsoft Intune admin center.
Final status: Following our processing throughput increase and reprocessing of the affected devices, we've internally validated that impact has been remediated.
Scope of impact: Impact was specific to some admins who were served through the affected infrastructure and checking the status of devices in the Microsoft Intune admin center that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Start time: Monday, March 10, 2025, at 12:30 PM UTC
End time: Wednesday, April 16, 2025, at 3:28 PM UTC
Root cause: An increase in device deactivations had caused a section of Microsoft Intune infrastructure to perform below manageable performance thresholds, causing update requests for the device status in the Microsoft Intune admin center to queue, which gave the impression that the devices were still active, when in fact they weren't.
Next steps:
- We're further analyzing the affected subset of lower-than-expected performance levels for the subset of affected Intune service infrastructure to help us isolate the source for the problem, and to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 16 11:56:16 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices aren’t active though and are reported as active in the Microsoft Intune admin center.
Current status: Our reprocessing of the affected devices continues to progress, and our updated timeline estimates it will have completed and remediated the impact by our next scheduled update.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure, checking the status of devices in the Microsoft Intune admin center. The problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Start time: Monday, March 10, 2025, at 12:30 PM UTC
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Wednesday, April 16, 2025, at 6:00 PM UT
|
|---|
|
| Time: | Wed Apr 16 06:52:31 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices aren’t active though and are reported as active in the Microsoft Intune admin center.
Current status: We're proceeding to reprocess the backlog of devices, and expect this to be completed by our next scheduled update.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure, checking the status of devices in the Microsoft Intune admin center. The problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Wednesday, April 16, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Apr 15 09:00:59 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices aren’t active though and are reported as active in the Microsoft Intune admin center.
Current status: We're continue to reprocess of the backlog of devices, and we're continuing to monitor until completion.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure, checking the status of devices in the Microsoft Intune admin center, and the problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Wednesday, April 16, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Apr 15 06:55:37 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices aren’t active though and are reported as active in the Microsoft Intune admin center.
Current status: We're reaching the final stages of the processing of the backlog of devices, and are monitoring until completion.
Scope of impact: Impact is specific to admins checking the status of devices in the Microsoft Intune admin center in the Northern Europe region, and the problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Tuesday, April 15, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Apr 14 16:56:38 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices aren’t active though are reported as active in the Microsoft Intune admin center.
Current status: We're continuing to monitor as the backlog of devices are processed and expect to have a remediation timeline by the next scheduled update.
Scope of impact: Impact is specific to admins checking the status of devices in the Microsoft Intune admin center in the Northern Europe region, and the problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Tuesday, April 15, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Apr 14 15:35:09 2025 |
|---|
| Description: | Title: Admins may see inactive devices showing as active in the Microsoft Intune admin center
User impact: Admins may see inactive devices showing as active in the Microsoft Intune admin center.
More info: This impacts devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025. The devices are not active though report as active in the Microsoft Intune admin center.
Current status: We've identified that an increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center. We've increased processing throughput on the affected infrastructure to withstand the sudden increase of deactivations and we’re monitoring the backlog of queued requests to ensure it’s processed in full. Once the backlog has been processed, devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025 will reflect their inactive status in the Microsoft Intune admin center. We’ll provide a remediation timeline once one is available.
Scope of impact: Impact is specific to admins checking the status of devices in the Microsoft Intune admin center in the Northern Europe region, and the problem impacts some devices that were inactive between Saturday, March 22, 2025, and Wednesday, April 9, 2025.
Root cause: An increase in device deactivations has caused a section of Microsoft Intune infrastructure to perform below acceptable performance thresholds, causing requests to update the device status in the Microsoft Intune admin center to queue, which gives the impression that the devices are still active in the Microsoft Intune admin center, when in fact they aren't.
Next update by: Monday, April 14, 2025, at 11:30 PM UTC
|
|---|
|
MF1056723 - Users may experience several-hour delays in receiving approval email from Microsoft Power Automate
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 16 05:00:00 2025 |
|---|
| End Time: | Wed Apr 16 11:13:00 2025 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 12:55:01 2025 |
|---|
| Root Cause: | A recent change intended to update email templates in Microsoft Power Automate contained an issue that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 12:22:03 2025 |
|---|
| Description: | Title: Users may experience several-hour delays in receiving approval email from Microsoft Power Automate
User impact: Users may have experienced several-hour delays in receiving approval email from Microsoft Power Automate.
More info: Users could manage approval requests through Microsoft Teams or the Microsoft Power Automate maker portal to bypass the issue while we worked on addressing the impact
Final status: We've completed reverting the offending change, and after monitoring the service, we've verified that this action has successfully remediated the problem.
Scope of impact: All users may have experienced several-hour delays in receiving approval email from Microsoft Power Automate.
Start time: Wednesday, April 16, 2025, at 9:00 AM UTC
Root cause: A recent change intended to update email templates in Microsoft Power Automate contained an issue that resulted in impact.
Next steps:
- We're investigating how the recent change intended to update email templates in Microsoft Power Automate contained an issue that resulted in impact to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 16 11:24:18 2025 |
|---|
| Description: | Title: Users may experience several-hour delays in receiving approval email from Microsoft Power Automate
User impact: Users may experience several-hour delays in receiving approval email from Microsoft Power Automate.
More info: Users can manage approval requests through Microsoft Teams or the Microsoft Power Automate maker portal to bypass the issue while we work on addressing the impact.
Current status: We've received reports that users may experience several-hour delays in receiving approval email from Microsoft Power Automate. After assessing the issue, we've identified that a recent change intended to update email templates in Microsoft Power Automate contains an issue that’s resulting in impact. We're reverting the offending change to remediate this issue, and once available, we'll provide a resolution timeline.
Scope of impact: All users may experience several-hour delays in receiving approval email from Microsoft Power Automate.
Start time: Wednesday, April 16, 2025, at 9:00 AM UTC
Root cause: A recent change intended to update email templates in Microsoft Power Automate contains an issue that’s resulting in impact
Next update by: Wednesday, April 16, 2025, at 4:30 PM UTC
|
|---|
|
FL1056688 - Users are experiencing delays with approval email delivery
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 16 05:00:00 2025 |
|---|
| End Time: | Wed Apr 16 11:13:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 12:07:12 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 12:07:12 2025 |
|---|
| Description: | Title: Users are experiencing delays with approval email delivery
User impact: Users were experiencing delays with approval email delivery.
Final Status: We completed rolling back the service update and, following a period of monitoring service health diagnostics, we confirmed that approval email delivery is no longer delayed.
This is the final update on the incident.
Preliminary Root Cause: A regression contained within a recent service update for a dependency.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Wed Apr 16 10:40:50 2025 |
|---|
| Description: | Title: Users are experiencing delays with approval email delivery
User impact: Users are experiencing delays with approval email delivery.
Current Status: After our investigation, we identified a regression which was introduced as part of a recent service update for a dependency as the source of impact. To mitigate the issue, we are rolling back the service update.
Next Update: Wednesday, April 16, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Apr 16 10:23:38 2025 |
|---|
| Description: | Title: Users are experiencing delays with approval email delivery
User impact: Users are experiencing delays with approval email delivery.
Current Status: We are aware of an emerging issue where users are experiencing delays with approval email delivery. 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.
|
|---|
|
DZ1056437 - Admins' Automated Investigations may have been delayed by up to five hours within the Microsoft Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 15 00:00:00 2025 |
|---|
| End Time: | Wed Apr 16 06:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 16 07:51:20 2025 |
|---|
| Root Cause: | An unexpected increase in Automated Investigations caused a section of infrastructure that facilitates Automated Investigations to perform below acceptable performance thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 16 07:51:20 2025 |
|---|
| Description: | Title: Admins' Automated Investigations may have been delayed by up to five hours within the Microsoft Defender portal
User impact: Admins' Automated Investigations may have been delayed by up to five hours within the Microsoft Defender portal.
Final status: The backlog of historical investigations has completely drained and impact has been resolved.
Scope of impact: Your organization was affected by this event, and any admin attempting to view Automated Investigations in the Microsoft Defender portal may have been impacted.
Start time: Tuesday, April 15, 2025, at 4:00 AM UTC
End time: Wednesday, April 16, 2025, at 10:30 AM UTC
Root cause: An unexpected increase in Automated Investigations caused a section of infrastructure that facilitates Automated Investigations to perform below acceptable performance thresholds.
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: | Wed Apr 16 02:58:48 2025 |
|---|
| Description: | Title: Admins' Automated Investigations may be delayed by up to five hours within the Microsoft Defender portal
User impact: Admins' Automated Investigations may be delayed by up to five hours within the Microsoft Defender portal.
Current status: We've identified that an increase in Automated Investigations has caused a section of infrastructure to perform below acceptable performance thresholds and result in impact. We've optimized performance parameters on the affected infrastructure to mitigate impact for new investigations and we're awaiting for a backlog of historical investigations to drain for impact to be fully remediated.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Automated Investigations in the Microsoft Defender portal may be impacted.
Start time: Tuesday, April 15, 2025, at 4:00 AM UTC
Root cause: An increase in Automated Investigations has caused a section of infrastructure to perform below acceptable performance thresholds.
Next update by: Wednesday, April 16, 2025, at 12:30 PM UTC
|
|---|
|
IT1056095 - Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Thu Apr 10 08:20:00 2025 |
|---|
| End Time: | Tue Apr 15 20:05:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 15 21:18:03 2025 |
|---|
| Root Cause: | A code issue was causing our service to not relay the information needed to correctly update the device status as compliant for the affected iOS and Android devices. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 15 21:15:21 2025 |
|---|
| Description: | Title: Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
User impact: Users may have seen their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune.
Final status: We've successfully completed the deployment of our fix, and we've confirmed that this has remediated the issue through testing and service telemetry. Those with iOS and Android devices affected by this issue will need to ensure that their device sends a heartbeat to the service, as this will trigger our fix to take effect. This can be accomplished through manually opening the Microsoft Defender for Endpoint app on the device.
Scope of impact: Some users who were attempting to view their iOS or Android devices in Microsoft Intune may have been impacted and saw that the devices were incorrectly marked as non-compliant.
Start time: Thursday, April 10, 2025, at 12:20 PM UTC
End time: Wednesday, April 16, 2025, at 12:05 AM UTC
Root cause: A code issue was causing our service to not relay the information needed to correctly update the device status as compliant for the affected iOS and Android devices.
Next steps:
- We're continuing to analyze the impacting code issue to better understand how it was introduced so we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 15 18:56:23 2025 |
|---|
| Description: | Title: Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
User impact: Users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune.
Current status: We've addressed the issue inhibiting our fix's deployment, and we're in the final stages of preparing our solution for deployment.
Scope of impact: Some users who are attempting to view their iOS or Android devices in Microsoft Intune may be impacted and see that they're incorrectly marked as non-compliant.
Start time: Thursday, April 10, 2025, at 12:20 PM UTC
Root cause: A code issue is causing our service to not relay the information needed to correctly update the device status as compliant for the affected iOS and Android devices.
Next update by: Wednesday, April 16, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Apr 15 16:25:31 2025 |
|---|
| Description: | Title: Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
User impact: Users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune.
Current status: Our investigation has determined that a code issue is causing our service to not relay the information needed to correctly update the device status as compliant for the affected iOS and Android devices. We've developed a fix to correct the problem with the code, and we're troubleshooting a deployment issue inhibiting us from immediately deploying our solution. We'll provide a resolution timeline once the deployment is underway.
Scope of impact: Some users who are attempting to view their iOS or Android devices in Microsoft Intune may be impacted and see that they're incorrectly marked as non-compliant.
Start time: Thursday, April 10, 2025, at 12:20 PM UTC
Root cause: A code issue is causing our service to not relay the information needed to correctly update the device status as compliant for the affected iOS and Android devices.
Next update by: Tuesday, April 15, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Apr 15 14:54:15 2025 |
|---|
| Description: | Title: Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
User impact: Users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune.
Current status: We're investigating available service telemetry and data from some affected users to identify the source of this issue and determine the most effective mitigation strategy.
Scope of impact: Some users who are attempting to view their iOS or Android devices in Microsoft Intune may be impacted and see that they're incorrectly marked as non-compliant.
Next update by: Tuesday, April 15, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Apr 15 14:26:08 2025 |
|---|
| Description: | Title: Some users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune
User impact: Users may see their iOS and Android devices incorrectly marked as non-compliant in Microsoft Intune.
Current status: We're investigating a potential issue with some users seeing their iOS and Android devices incorrectly marked as non-compliant, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
Scope of impact: Some users who are attempting to view their iOS or Android devices in Microsoft Intune may be impacted and see that they're incorrectly marked as non-compliant.
|
|---|
|
CP1055509 - Admins may have encountered delays for multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 13 20:00:00 2025 |
|---|
| End Time: | Mon Apr 14 14:11:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 15 09:40:43 2025 |
|---|
| Root Cause: | An upstream data source wasn't processing report data as expected, due to a section of its infrastructure performing below acceptable performance thresholds and resulting in usage report delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 15 06:13:58 2025 |
|---|
| Description: | Title: Admins may have encountered delays for multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center
User impact: Admins may have encountered delays for multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center.
More info: Affected reports include:
- Microsoft 365 Copilot readiness report
- Microsoft 365 Copilot usage report
- Microsoft 365 Copilot Chat usage
Final status: We've identified that an upstream data source wasn't processing report data as expected, due to a section of its infrastructure performing below acceptable performance thresholds and resulting in the aforementioned usage report delays. While we were in the process of analyzing diagnostic data to determine the root cause of impact, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Impact was specific to users who were served through the affected infrastructure attempting to view multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
End time: Tuesday, April 14, 2025, at 6:11 PM UTC
Root cause: An upstream data source wasn't processing report data as expected, due to a section of its infrastructure performing below acceptable performance thresholds and resulting in usage report delays.
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 14 18:40:58 2025 |
|---|
| Description: | Title: Admins may encounter delays for multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center
User impact: Admins may encounter delays for multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center.
More info: Affected reports include:
- Microsoft 365 Copilot readiness report
- Microsoft 365 Copilot usage report
- Microsoft 365 Copilot Chat usage
Current status: We've identified that upstream data delays are inadvertently causing impact and we're reviewing available mitigation options to resolve impact.
Scope of impact: Impact is specific to users who are served through the affected infrastructure attempting to view multiple Microsoft 365 Copilot reports in the Microsoft 365 admin center.
Start time: Monday, April 14, 2025, at 12:00 AM UTC
Root cause: Upstream data delays are inadvertently causing impact.
Next update by: Tuesday, April 15, 2025, at 10:00 AM UTC
|
|---|
|
MP1043942 - Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Fri Mar 28 07:30:00 2025 |
|---|
| End Time: | Sun Apr 13 19:47:00 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 15 00:47:29 2025 |
|---|
| Root Cause: | A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 15 00:47:11 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may have been unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins were unable to set up new data connectors within Purview and may not have seen data ingested into Microsoft Purview from already established data connectors.
Final status: We have successfully deployed the fix to restore data connector functionality within Microsoft Purview. We appreciate your patience and understanding while we focused on efforts on resolving this incident.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may have been impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
End time: Sunday, April 13, 2025, at 11:47 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next steps:
- We’re reviewing our Microsoft Purview monitoring and alerting systems, to identify gaps so that we detect and address the impact sooner.
- We’re adding additional layers of validation and a more gradual roll out of changes to ensure any errors are highlighted earlier.
- We’re optimizing our recovery processes to implement better component restart functionality at scale, to reduce impact times in the future.
|
|---|
|
| Time: | Sat Apr 12 00:32:53 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Administrators can now import .PST files normally. Additionally, we’ve restored functionality for existing signal and configuration connectors.
Current status: We’re making significant progress in restoring the data connector functionality within Microsoft Purview. Our internal infrastructure monitoring and telemetry indicate positive performance results. We’ll continue to closely monitor performance metrics as we expand the deployment globally, which we anticipate completing by early next week. Thank you once again for your patience as we work to fully resolve this issue.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted. The previously communicated impact on .PST file imports has been resolved.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Tuesday, April 15, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Apr 11 01:54:19 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Administrators can now import .PST files normally. Additionally, we’ve restored functionality for existing signal and configuration connectors.
Current status: We’ve confirmed that the fix for restoring data connector functionality within Microsoft Purview has entered the final testing phase within our internal infrastructure. We’re continuing our analysis to verify it meets all performance requirements. Once final validation is completed, we’ll proceed with the global deployment, which we anticipate completing by early next week.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted. The previously communicated impact on .PST file imports has been resolved.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Saturday, April 12, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Apr 10 01:53:40 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Admins can import .PST files normally. We’ve also restored functionality for existing signal and configuration connectors.
Current status: We’ve confirmed that the fix designed to restore data connector functionality within Microsoft Purview is successfully progressing through our internal testing environment. This fix has passed some critical milestones, demonstrating the capability for resolving identified issues. Currently, we are conducting a thorough analysis of its performance within our infrastructure to ensure it meets all operational standards. This step is crucial to guarantee that the fix will perform reliably under various conditions.
Once we’ve validated its effectiveness, we’ll proceed towards a global deployment. Thank you for your cooperation and patience as we take these necessary steps to restore service while minimizing the potential for further disruptions.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted. The previously communicated impact on .PST file imports has been resolved.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Friday, April 11, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Wed Apr 9 02:36:58 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Admins can import .PST files normally.
Current status: We’ve successfully restored functionality for signal and configuration connectors. Additionally, we’ve developed and validated a potential solution to restore data connector functionality within Microsoft Purview. We are now moving closer to the final stages of confirming the effectiveness of this mitigation to ensure performance meets expectations. We will continue testing the solution within our internal infrastructure to optimize its performance and reliability before full deployment. We’re grateful for your patience as we take steps to ensure there are no further disruptions.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted. The previously communicated impact on .PST file imports has been resolved.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Thursday, April 10, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Apr 8 18:43:55 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Admins can import .PST files normally.
Current status: We’ve developed a potential solution to restore the data connector functionality within Microsoft Purview. We're currently validating the fix before deploying it to a subset of our internal infrastructure for further testing to confirm the efficacy of the mitigation and to ensure no further impact will occur.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted. The previously communicated impact on .PST file imports has been resolved.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Wednesday, April 9, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Apr 7 14:48:33 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: Admins are unable to set up new data connectors within Purview and may not see data ingested into Microsoft Purview from already established data connectors.
The previously communicated impact on .PST file imports has been resolved, and the backlog of imports has been processed. Admins can import .PST files normally.
Current status: We’ve completed the restoration of .PST import functionality and successfully processed the backlog of import jobs. In parallel, we’re continuing our work to restore the data connector functionality within Microsoft Purview and we'll provide a detailed update on our progress at the next scheduled update. We understand the impact this incident may have on your organization and we're continuing to address it with high urgency.
Scope of impact: Any admin attempting to set up new data connectors or reviewing ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Tuesday, April 8, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Sat Apr 5 01:27:30 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We’ll continue our monitoring of the backlog as we continue to apply service enhancements to increase processing rate. We’ll provide an update as soon as its available.
Concurrently, we’re focused on restoring the data connector functionality within Microsoft Purview, which we hope to have a more detailed update after Monday, April 7, 2025.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Monday, April 7, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 4 13:52:50 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: Following the deployment of our fix for .PST import functionality, we've confirmed that there is a backlog of import requests that are still being processed, resulting in users observing unexpected delays with import jobs. We've applied service enhancements to improve the processing rate of the backlog, and expect affected import requests to be processed by Monday, April 7, 2025.
We are also continuing to work on restoring data connector functionality within Microsoft Purview and will provide an update on this workstream as soon as possible.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Saturday, April 5, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Apr 3 01:37:21 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We have successfully deployed the fix to our Worldwide environment and confirmed that .PST import functionality has been restored. We are continuing to deploy the fix to the remaining impacted environments which we expect to be completed by our next scheduled update. In parallel, we're working on restoring data connector functionality within Microsoft Purview.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Saturday, April 5, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Apr 2 01:51:04 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We're continuing to perform additional validations to ensure that the fix is effective at mitigating the issue. Based on our current progress, we now expect our testing to completed by our next update. If successful, we will deploy the fix to the impacted service infrastructure. We understand the impact this incident may have on your organization and we're continuing to treat it with the highest urgency.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Thursday, April 3, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Apr 1 13:41:24 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We've developed and deployed a fix to our internal infrastructure and are currently conducting comprehensive tests to confirm our solution will remediate impact. We expect to complete testing by our next scheduled update, at which point we will start to deploy the solution throughout the affected service environment.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Wednesday, April 2, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Apr 1 03:25:58 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We're working on a fix to restore the import service. At this time, we're unable to provide an ETA.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Tuesday, April 1, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Mar 31 13:56:40 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: Details of a proposed fix are not yet available as we're further analyzing the offending service improvements that were enabled for the affected subset of Microsoft Purview service infrastructure to further isolate the source of this event and identify a remediation pathway.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Tuesday, April 1, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Mar 31 01:56:03 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We're continuing our efforts of identifying an efficient remediation plan and anticipate being able to provide details of our proposed fix by our next scheduled update.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Monday, March 31, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sun Mar 30 12:01:03 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We're continuing to review our potential mitigation options to resolve the impact felt by affected admins.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Start time: Friday, March 28, 2025, at 11:30 AM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Monday, March 31, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Sun Mar 30 05:42:41 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We've determined that a recent update intended to improve a section of infrastructure responsible for Purview functionality, inadvertently contains a code regression and is resulting in impact. We're reviewing potential mitigation options to resolve impact for affected users.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Sunday, March 30, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Mar 29 16:09:42 2025 |
|---|
| Description: | Title: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview
User impact: Admins may be unable to import .PST files or set up new data connectors within Microsoft Purview.
More info: This also impacts .PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Additionally, admins may not see data ingested into Microsoft Purview from already established data connectors.
Current status: We're reviewing service logging to identify the root cause of this event, so we can determine our next steps regarding impact remediation.
Scope of impact: Any admin attempting to import .PST files, set up new data connectors, or review ingested data from established data connectors within Microsoft Purview may be impacted.
Next update by: Sunday, March 30, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Sat Mar 29 15:54:49 2025 |
|---|
| Description: | Title: Admins may be unable to import Personal Storage Table (PST) files within Microsoft Purview
User impact: Admins may be unable to import PST files within Microsoft Purview.
More info: This also impacts PST file imports that are already in progress. Admins will need to restart these imports once service is resolved.
Current status: We're investigating a potential issue with admins being unable to import PST files within Microsoft Purview, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1055333 - Admins may be unable to run PowerShell cmdlets in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 14 13:18:33 2025 |
|---|
| End Time: | Mon Apr 14 15:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 14 15:43:17 2025 |
|---|
| Root Cause: | A code error was introduced in a recent update applied to infrastructure that handles PowerShell cmdlet functionality in Exchange Online. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Apr 14 15:43:17 2025 |
|---|
| Description: | Title: Admins may be unable to run PowerShell cmdlets in Exchange Online
User impact: Admins may have been unable to run PowerShell cmdlets in Exchange Online.
More info: Admins running cmdlets, such as Get-MailboxFolderStatistics for example, encountered an Internal Server Error.
Final status: We've completed reverting the previously mentioned update leading to impact, and we've confirmed with some previously affected admins that the impact is remediated.
Scope of impact: This issue may have affected any admin running PowerShell cmdlets in Exchange Online.
Start time: Tuesday, April 8, 2025, at 11:00 AM UTC
End time: Monday, April 14, 2025, at 7:00 PM UTC
Root cause: A code error was introduced in a recent update applied to infrastructure that handles PowerShell cmdlet functionality in Exchange Online.
Next steps:
- We're reviewing our Exchange Online infrastructure update procedures pertaining to the components responsible for facilitating the impacted cmdlet functionality to prevent similar impact is future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon Apr 14 14:10:13 2025 |
|---|
| Description: | Title: Admins may be unable to run PowerShell cmdlets in Exchange Online
User impact: Admins may be unable to run PowerShell cmdlets in Exchange Online.
More info: Admins running cmdlets, such as Get-MailboxFolderStatistics as an example, encounter an Internal Server Error.
Current status: We've identified faulty code in a recent update that has introduced the problem and initiated the process of reverting the update within the affected environment. Some customers may no longer be experiencing impact, while we anticipate the remaining customers will be addressed by our next communication update.
Scope of impact: This issue may affect any admin running PowerShell cmdlets in Exchange Online.
Start time: Tuesday, April 8, 2025, at 11:00 AM UTC
Root cause: A code error was introduced in a recent update applied to infrastructure that handles PowerShell cmdlet functionality in Exchange Online.
Next update by: Tuesday, April 15, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 14 13:19:35 2025 |
|---|
| Description: | Title: Admins can't run the Get-MailboxFolderStatistics PowerShell cmdlet in Exchange Online
User impact: Admins can't run the Get-MailboxFolderStatistics 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 60 minutes.
|
|---|
|
CP1052692 - Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 8 20:00:00 2025 |
|---|
| End Time: | Fri Apr 11 20:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 14 14:16:22 2025 |
|---|
| Root Cause: | A code issue within a recent service change was causing a conflation of unlicensed Copilot users with licensed users within Copilot usage reports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Apr 14 14:16:22 2025 |
|---|
| Description: | Title: Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may have seen inflated active user numbers in the Copilot usage report.
More info: Admins with Microsoft 365 Copilot licenses may have seen inflated active user numbers in the Microsoft 365 admin center and in the Readiness tab of the Copilot Dashboard in Viva Insights.
Final status: Our testing with affected users has validated that our targeted fix has addressed the isolated code issue, and that impact has been remediated.
Scope of impact: Impact may have occurred for some admins with Copilot licenses accessing the Copilot usage report in the Microsoft 365 admin center or the Readiness tab of the Copilot Dashboard in Viva Insights.
Start time: Wednesday, April 9, 2025, at 12:00 AM UTC
End time: Saturday, April 12, 2025, at 12:00 AM UTC
Root cause: A code issue within a recent service change was causing a conflation of unlicensed Copilot users with licensed users within Copilot usage reports.
Next steps:
- We're further analyzing the offending service update to help us better isolate similar issues during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri Apr 11 14:09:37 2025 |
|---|
| Description: | Title: Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see inflated active user numbers in the Copilot usage report.
More info: Admins with Microsoft 365 Copilot licenses may see inflated active user numbers in the Microsoft 365 admin center and in the Readiness tab of the Copilot Dashboard in Viva Insights.
Current status: We've developed and deployed a targeted fix, and confirmed that it prevents future Copilot usage reports from having an inflated active user count. We're reimplementing historical reporting data to provide accurate active user numbers for previously affected reports. We expect this will complete and remediate impact by our next scheduled update.
Scope of impact: Impact may occur for some admins with Copilot licenses accessing the Copilot usage report in the Microsoft 365 admin center or the Readiness tab of the Copilot Dashboard in Viva Insights.
Start time: Sunday, April 6, 2025, at 8:00 AM UTC
Root cause: A code issue within a recent service change is causing a conflation of unlicensed Copilot users with licensed users within usage reports.
Next update by: Monday, April 14, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Apr 10 20:54:33 2025 |
|---|
| Description: | Title: Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see inflated active user numbers in the Copilot usage report.
More info: Admins with Microsoft 365 Copilot licenses may see inflated active user numbers in the Microsoft 365 admin center and in the Readiness tab of the Copilot Dashboard in Viva Insights.
Current status: We've determined that a code issue within a recent service change is causing a conflation of unlicensed Copilot users with licensed users within usage reports. We're in the process of developing a targeted fix for this issue, and we anticipate beginning its deployment and providing an estimated completion timeline by the next scheduled update.
Scope of impact: Impact may occur for some admins with Copilot licenses accessing the Copilot usage report in the Microsoft 365 admin center or the Readiness tab of the Copilot Dashboard in Viva Insights.
Start time: Sunday, April 6, 2025, at 8:00 AM UTC
Root cause: A code issue within a recent service change is causing a conflation of unlicensed Copilot users with licensed users within usage reports.
Next update by: Friday, April 11, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Apr 10 14:42:53 2025 |
|---|
| Description: | Title: Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see inflated active user numbers in the Copilot usage report.
More info: Admins with Microsoft 365 Copilot licenses may see inflated active user numbers in the Microsoft 365 admin center and in the Readiness tab of the Copilot Dashboard in Viva Insights.
Current status: We're continuing our assessment of service telemetry to isolate the source of this issue and identify a remediation pathway.
Scope of impact: Impact may occur for some admins with Copilot licenses accessing the Copilot usage report in the Microsoft 365 admin center or the Readiness tab of the Copilot Dashboard in Viva Insights.
Next update by: Friday, April 11, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Apr 10 13:49:24 2025 |
|---|
| Description: | Title: Some admins may see inflated active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see inflated active user numbers in the Copilot usage report.
More info: Admins with Microsoft 365 Copilot licenses may see inflated active user numbers in the Microsoft 365 admin center and in the Readiness tab of the Copilot Dashboard in Viva Insights.
Current status: Our monitoring system has identified that some admins with Microsoft 365 Copilot licenses may see inflated active user numbers in the Microsoft 365 admin center and Copilot dashboard in Viva Insights. We're assessing service telemetry to isolate the source of this issue and identify a remediation pathway.
Scope of impact: Impact may occur for some admins with Microsoft 365 Copilot licenses accessing the Copilot usage report in the Microsoft 365 admin center or Copilot dashboard in Viva Insights.
Next update by: Thursday, April 10, 2025, at 7:00 PM UTC
|
|---|
|
EX1050095 - Some users are intermittently unable to see installed apps or add-ins within any Outlook connection method
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 6 11:15:00 2025 |
|---|
| End Time: | Fri Apr 11 12:36:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Apr 11 19:49:11 2025 |
|---|
| Root Cause: | A recent change to optimize traffic throughout for an API that displays the list of apps and add-ins within Outlook caused an increase in traffic that our systems intermittently processed inefficiently, which caused the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Apr 11 19:49:11 2025 |
|---|
| Description: | Title: Some users are intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users were intermittently unable to see installed apps or add-ins within any Outlook connection method.
Final status: After the process of increasing our service's ability to handle large amounts of traffic completed, we performed an extended period of monitoring service telemetry to ensure that the aforementioned change didn't bring about any adverse effects and later confirmed that the issue has been resolved.
Scope of impact: Your organization was affected by this event, and some users who attempted to view installed apps or add-ins within any Outlook connection method were intermittently impacted.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
End time: Friday, April 11, 2025, at 4:36 PM UTC
Root cause: A recent change to optimize traffic throughout for an API that displays the list of apps and add-ins within Outlook caused an increase in traffic that our systems intermittently processed inefficiently, which caused the impact.
Next steps:
- We're reviewing this recent service optimization to understand why impact wasn’t identified prior to implementing the change so that we can better understand the underlying issue and improve our change management practices.
This is the final update for the event.
|
|---|
|
| Time: | Thu Apr 10 19:56:22 2025 |
|---|
| Description: | Title: Some users are intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users are intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: While we've confirmed that the issue has been largely mitigated with the completion of our solution's deployment, we're continuing to monitor the service as our efforts to increase our service's ability to handle large amounts of traffic completes and fully remediates the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to view installed apps or add-ins within any Outlook connection method are intermittently impacted.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Saturday, April 12, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 9 20:24:42 2025 |
|---|
| Description: | Title: Some users are intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users are intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: We’re continuing our best efforts to increase our service’s ability to handle large amounts of traffic, though this process is taking an extended period of time. In parallel, our previously mentioned solution has begun deploying to the affected partitions of the service infrastructure. Based on our current estimations, we anticipate our solutions will have completed and resolved the issue by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to view installed apps or add-ins within any Outlook connection method are intermittently impacted.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Friday, April 11, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Apr 8 19:19:41 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: Our efforts to increase our service's ability to handle large amounts of traffic, is ongoing. In tandem, our solution to disable the offending portion of the impacting change is in the final stages of development and testing. We'll provide a timeline for impact remediation as one becomes available.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Thursday, April 10, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Apr 8 17:16:17 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: While we've observed that impact reoccurred during peak hours, we're continuing our efforts to increase our service's ability to handle large amounts of traffic, and to prepare our solution for deployment. In parallel, we're still assessing if there are more expedient methods to remediate the issue and ensure impact doesn't reoccur.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Wednesday, April 9, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 7 21:26:26 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
More info: While we've confirmed that impact isn't actively occurring, as of Monday, April 7, 2025, at 5:10 PM UTC, we're pursuing a solution to ensure this issue doesn't reoccur.
Current status: We're continuing to prepare our solution for deployment and we're assessing if there may be more expedient and effective methods for remediating the issue. In parallel, we're working to increase the service's ability to handle the large amount of traffic, which should help prevent this issue from occurring.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Wednesday, April 9, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 7 18:22:11 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
More info: While we've confirmed that impact isn't actively occurring, as of Monday, April 7, 2025, at 5:10 PM UTC, we're pursuing a solution to ensure this issue doesn't reoccur.
Current status: We've developed a solution which will allow us to disable the offending portion of the impacting change, and we're in the final stages of preparing this for deployment. Once deployment begins, we'll be better able to identify a resolution timeline.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
Start time: Sunday, April 6, 2025, at 3:15 PM UTC
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Tuesday, April 8, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Apr 7 16:14:13 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: We've identified a recent change to optimize our service which introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method. While we've confirmed that impact isn't actively occurring, as of Monday, April 7, 2025, at 5:10 PM UTC, we're working to develop a solution to ensure that this issue doesn't reoccur. We'll share a resolution timeline once available.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
Root cause: A recent change to optimize our service has introduced an issue that resulted in an inordinate amount of traffic volume, causing users to be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Next update by: Monday, April 7, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Apr 7 15:43:39 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to see installed apps or add-ins within any Outlook connection method
User impact: Users may be intermittently unable to see installed apps or add-ins within any Outlook connection method.
Current status: We're investigating a potential issue with users being unable to see installed apps or add-ins within any Outlook connection method, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
Scope of impact: Some users attempting to view installed apps or add-ins within any Outlook connection method may be intermittently affected.
|
|---|
|
TM1037538 - Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 5 07:00:00 2025 |
|---|
| End Time: | Tue Apr 8 20:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Apr 11 15:37:53 2025 |
|---|
| Root Cause: | A recent update contains a code regression, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Apr 11 15:37:53 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users experienced failures when attempting to join channel meetings.
More info: Impact was specific to users on the desktop client or web app that were joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users weren't seeing an error, the action simply failed.
While we were working to remediate impact, affected users could still join channel meetings using the classic Teams calendar, the Teams mobile apps, or by joining the meeting directly through the channel.
Final status: We've confirmed that the fix as completed deployment and validated remediation using service telemetry.
Scope of impact: Your organization was affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients was impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
End time: Wednesday, April 9, 2025, at 12:00 AM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next steps:
- We're continuing our analysis of the impacting change to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 8 14:51:35 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar, the Teams mobile apps, or by joining the meeting directly through the channel.
Current status: Deployment of the fix has resumed and we’re monitoring its progress to provide an estimation for its completion by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Friday, April 11, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Apr 4 11:43:30 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar, the Teams mobile apps, or by joining the meeting directly through the channel.
Current status: We're addressing some issues within our deployment pipeline that have halted the deployment of the fix. We anticipate the issues within our pipeline will be addressed, and the deployment resumed by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Tuesday, April 8, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 31 14:24:23 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar or the Teams mobile apps.
Current status: The deployment of our fix has been initiated, and we anticipate the deployment will complete to resolve the impact by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Friday, April 4, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Mar 20 16:11:33 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar or the Teams mobile apps.
Current status: We've completed the development of the fix and have initiated the validation process. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Monday, March 31, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Mar 20 14:55:25 2025 |
|---|
| Description: | Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar or the Teams mobile apps.
Current status: Our monitoring has identified an increase in join failures for channel meetings in Microsoft Teams. We've reviewed recent service updates and identified that a code regression is resulting in impact. We're in the process of validating a fix to remediate this issue.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Thursday, March 20, 2025, at 9:00 PM UTC
|
|---|
|
TM1051786 - Admins' user migrations from Skype for Business to Microsoft Teams may fail
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 09:30:00 2025 |
|---|
| End Time: | Fri Apr 11 11:10:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Apr 11 13:58:54 2025 |
|---|
| Root Cause: | A recent service update contained a code change to the encryption service that wasn't processing user information as expected, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Apr 11 13:58:54 2025 |
|---|
| Description: | Title: Admins' user migrations from Skype for Business to Microsoft Teams may fail
User impact: Admins' user migrations from Skype for Business to Microsoft Teams may have failed.
Final status: We've completed the previously mentioned reversion of the impacting code change, and we've monitored our service health telemetry to confirm that impact is remediated.
Scope of impact: Impact was specific to admins attempting to migrate users from Skype for Business to Microsoft Teams.
Start time: Monday, April 7, 2025, at 1:30 PM UTC
End time: Friday, April 11, 2025, at 3:10 AM UTC
Root cause: A recent service update contained a code change to the encryption service that wasn't processing user information as expected, resulting in impact.
Next steps:
- We're reviewing our Microsoft Teams service update procedures pertaining to the components of the encryption service responsible for processing user information to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu Apr 10 14:46:59 2025 |
|---|
| Description: | Title: Admins' user migrations from Skype for Business to Microsoft Teams may fail
User impact: Admins' user migrations from Skype for Business to Microsoft Teams may fail.
Current status: We're monitoring the rollback of the impacting code change which is taking longer than initially anticipated. We expect the rollback will complete and the impact remediated by our next scheduled communications update.
Scope of impact: Impact is specific to admins attempting to migrate users from Skype for Business to Microsoft Teams.
Start time: Monday, April 7, 2025, at 1:30 PM UTC
Estimated time to resolve: We anticipate the impacting code change will be rolled back by Friday, April 11, 2025, at 7:30 PM UTC.
Root cause: A recent service update contains a code change to the encryption service that isn't processing user information as expected, resulting in impact.
Next update by: Friday, April 11, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Apr 9 12:04:00 2025 |
|---|
| Description: | Title: Admins' user migrations from Skype for Business to Microsoft Teams may fail
User impact: Admins' user migrations from Skype for Business to Microsoft Teams may fail.
Current status: We've identified that a recent service update contains a code change to the encryption service that isn't processing user information as expected, resulting in impact. We're rolling back this change and expect impact will be remediated by our next scheduled update.
Scope of impact: Impact is specific to admins attempting to migrate users from Skype for Business to Microsoft Teams.
Start time: Monday, April 7, 2025, at 1:30 PM UTC
Root cause: A recent service update contains a code change to the encryption service that isn't processing user information as expected, resulting in impact.
Next update by: Thursday, April 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Apr 9 10:20:09 2025 |
|---|
| Description: | Title: Users may be encountering issues when migrating from Skype for Business to Microsoft Teams
User impact: Users may be encountering issues when migrating from Skype for Business to Microsoft Teams.
More info: Affected users specifically experience issues with user move functionality.
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.
Next update by: Wednesday, April 9, 2025, at 4:30 PM UTC
|
|---|
|
EX1052522 - Admins may have been unable to access the Exchange admin center (EAC)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Apr 10 06:40:00 2025 |
|---|
| End Time: | Thu Apr 10 07:23:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Apr 10 08:12:06 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Apr 10 08:10:33 2025 |
|---|
| Description: | Title: Admins may have been unable to access the Exchange admin center (EAC)
User impact: Admins may have been unable to access the Exchange admin center (EAC).
More info: Admins may have received the following error "HTTP Error 500".
Final status: During the rollout of a new mitigation strategy for the issue resolved on Wednesday, April 9, 2025, communicated under EX1051697, we deployed a different mitigation strategy to a small amount of infrastructure in the North America region. The new mitigation strategy did not have the expected results, and caused impact to reoccur. We have reverted the service to use the previous remediation strategy and confirmed that the impact is no longer occurring.
Scope of impact: This issue could have affected any admin accessing the Exchange admin center located in the North America region.
Start time: Thursday, April 10, 2025, at 10:40 AM UTC
End time: Thursday, April 10, 2025, at 11:23 AM UTC
Preliminary root cause: An authentication issue within a specific URL path caused HTTP 500 errors resulting in impact.
Next steps:
- We're reassessing our service monitoring of this impact scenario to implement improvements for detecting similar events and reduce the time to identify and address this type of impact.
This is the final update for the event.
|
|---|
|
TM1051778 - Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 9 10:13:48 2025 |
|---|
| End Time: | Wed Apr 9 11:10:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 9 13:21:57 2025 |
|---|
| Root Cause: | A portion of infrastructure that facilitates the functionality of an API that the Microsoft Teams admin center depends on was experiencing increased latency, which resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 9 13:21:57 2025 |
|---|
| Description: | Title: Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center
User impact: Admins may have experienced timeout errors or delays in accessing some sections of the Microsoft Teams admin center.
More info: This issue affected sections of the Microsoft Teams admin center dependent on the affected API, such as management of users, policies, apps, call queues, and resources accounts. This also affected the use of PowerShell to manage these features.
Final status: The rebalancing operations have completed, and we've validated that this issue has been remediated using service telemetry.
Scope of impact: This issue may have affected any admin accessing the affected Microsoft Teams admin center pages or using PowerShell to manage the affected features.
Start time: Wednesday, April 9, 2025, at 1:20 PM UTC
End time: Wednesday, April 9, 2025, at 3:10 PM UTC
Root cause: A portion of infrastructure that facilitates the functionality of an API that the Microsoft Teams admin center depends on was experiencing increased latency, which resulting in impact.
Next steps:
- We're continuing our analysis of service telemetry to isolate the underlying cause of the increased latency to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 9 11:34:35 2025 |
|---|
| Description: | Title: Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center
User impact: Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center.
More info: This issue affects sections of the Microsoft Teams admin center dependent on the affected API, such as management of users, policies, apps, call queues, and resources accounts. This also affects the use of PowerShell to manage these features.
Current status: Our investigation has identified that a portion of infrastructure that facilitates access to the Microsoft Teams admin center is experiencing increased latency, resulting in some requests from not completing as expected. We're in the process of rebalancing requests to alternate infrastructure to remediate this issue.
Scope of impact: This issue may affect any admin accessing the affected Microsoft Teams admin center pages or using PowerShell to manage the affected features.
Start time: Wednesday, April 9, 2025, at 1:20 PM UTC
Root cause: A portion of infrastructure that facilitates access to the Microsoft Teams admin center is experiencing increased latency, resulting in impact.
Next update by: Wednesday, April 9, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Apr 9 11:04:56 2025 |
|---|
| Description: | Title: Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center
User impact: Admins may be unable to access or may experience delays in accessing some sections of the Microsoft Teams admin center.
More info: This issue affects sections of the Microsoft Teams admin center dependent on the affected API, such as management of users, policies, apps, call queues, and resources accounts. This also affects the use of PowerShell to manage these features.
Current status: We've identified errors originating from an API that certain pages and features within Microsoft Teams admin center is dependent on, which we're further investigating to identify the source of the impact.
Scope of impact: This issue may affect any admin accessing the affected Microsoft Teams admin center pages or using PowerShell to manage the affected features.
Start time: Wednesday, April 9, 2025, at 1:20 PM UTC
Next update by: Wednesday, April 9, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Apr 9 10:13:49 2025 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
CP1050656 - Admins may have seen stale data for multiple Microsoft Copilot (Microsoft 365) reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 20:00:00 2025 |
|---|
| End Time: | Wed Apr 9 00:55:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Apr 9 05:37:12 2025 |
|---|
| Root Cause: | An upstream service configuration issue was causing impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Apr 9 05:37:12 2025 |
|---|
| Description: | Title: Admins may have seen stale data for multiple Microsoft Copilot (Microsoft 365) reports in the Microsoft 365 admin center
User impact: Admins may have seen stale data populating for multiple Copilot reports in the Microsoft 365 admin center.
More info: Admins may have experienced delays with the following reports:
- Microsoft 365 Copilot readiness report
- Microsoft 365 Copilot usage report
- Microsoft 365 Copilot Chat usage report
Final status: We've confirmed that an upstream service configuration issue was causing impact to occur. We've fixed the configuration issue and confirmed that impact has been remediated after a period of monitoring.
Scope of impact: This issue may have affected any admin viewing Copilot reports in the Microsoft 365 admin center.
Start time: Tuesday, April 8, 2025, at 12:00 AM UTC
End time: Wednesday, April 9, 2025, at 4:55 AM UTC
Root cause: An upstream service configuration issue was causing impact to occur.
Next steps:
- We're reviewing our upstream service configuration procedures to help prevent this issue from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 8 11:11:08 2025 |
|---|
| Description: | Title: Admins may see stale data for multiple Microsoft Copilot (Microsoft 365) reports in the Microsoft 365 admin center
User impact: Admins may see stale data populating for multiple Copilot reports in the Microsoft 365 admin center.
More info: Users may experience delays with the following reports:
- Microsoft 365 Copilot readiness report
- Microsoft 365 Copilot usage report
- Microsoft 365 Copilot Chat usage report
Current status: We've identified that a latency was introduced into the data source which generates the reporting data. We're investigating the source of this latency while we formulate potential remediating actions.
Scope of impact: This issue may affect any admin viewing Copilot reports in the Microsoft 365 admin center.
Start time: Tuesday, April 8, 2025, at 12:00 AM UTC
Next update by: Wednesday, April 9, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Apr 8 10:57:52 2025 |
|---|
| Description: | Title: Admins may see stale data for multiple Microsoft Copilot (Microsoft 365) reports in the Microsoft 365 admin center
User impact: Admins may see stale data populating for multiple Copilot reports in the Microsoft 365 admin center.
More info: Users may experience delays with the following reports:
- Microsoft 365 Copilot readiness report
- Microsoft 365 Copilot usage report
- Microsoft 365 Copilot Chat usage report
Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1050632 - Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 8 04:30:00 2025 |
|---|
| End Time: | Tue Apr 8 15:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 8 23:18:11 2025 |
|---|
| Root Cause: | A recent update to some dependent services caused failures for admins when they refreshed their session, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 8 23:18:11 2025 |
|---|
| Description: | Title: Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center
User impact: Admins may have been unable to access or may have encountered delays while using the Microsoft Teams admin center.
Final status: We've received confirmation from some previously impacted admins that our actions of reverting the offending change alleviated impact as expected.
Scope of impact: This issue may have affected any admin accessing the Microsoft Teams admin center and served through the affected infrastructure in the Asia-Pacific, Australia, Canada, India, Japan, and North America regions.
Start time: Tuesday, April 8, 2025, at 8:30 AM UTC
End time: Tuesday, April 8, 2025, at 7:00 PM UTC
Root cause: A recent update to some dependent services caused failures for admins when they refreshed their session, which resulted in impact.
Next steps:
- We're analyzing the recent update and its interaction with the dependent services to better understanding how to avoid impact like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 8 15:27:32 2025 |
|---|
| Description: | Title: Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center
User impact: Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center.
More info: We recommend that admins who aren't currently affected to refrain from refreshing their active session in the Microsoft Teams admin center, as this issue arises upon refreshing the page.
Current status: We've confirmed that the reversion of the offending update has completed, and all admins should be experiencing relief according to our testing. We're reaching out to some affected admins to further validate that the issue has been remediated.
Scope of impact: This issue may affect any admin accessing the Microsoft Teams admin center and is served from the affected infrastructure. This issue affects infrastructure in the Asia-Pacific, Australia, Canada, India, Japan, and North America regions.
Start time: Tuesday, April 8, 2025, at 8:30 AM UTC
Root cause: A recent update to the back-end services that support the Microsoft Teams admin center is causing failures for admins when they refresh their session, which is causing this impact.
Next update by: Wednesday, April 9, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Tue Apr 8 11:27:28 2025 |
|---|
| Description: | Title: Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center
User impact: Admins may be unable to access or may encounter delays while using the Microsoft Teams admin center.
More info: We recommend that admins who aren't currently affected to refrain from refreshing their active session in the Microsoft Teams admin center, as this issue arises upon refreshing the page.
Current status: We've received reports that admins may be unable to access or encounter delays while using the Microsoft Teams admin center. We've identified a recent deployment to the back-end services that support the Microsoft Teams admin center that's causing failures for admins when they refresh their session. We're in the process of reverting this update and we anticipate that admins will progressively experience relief as this update is reverted.
Scope of impact: This issue may affect any admin accessing the Microsoft Teams admin center and is served from the affected infrastructure. This issue affects infrastructure in the Asia-Pacific, Australia, Canada, India, Japan, and North America regions.
Start time: Tuesday, April 8, 2025, at 8:30 AM UTC
Root cause: A recent update to the back-end services that support the Microsoft Teams admin center is causing failures for admins when they refresh their session, which is causing this impact.
Next update by: Tuesday, April 8, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Apr 8 10:32:19 2025 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
SP1042262 - Some users' published articles may not show in the News web part within SharePoint Online sites
| Status: | investigationSuspended |
|---|
| Start Time: | Thu Mar 27 04:20:06 2025 |
|---|
| End Time: | Tue Apr 8 17:22:56 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Tenant Admin |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 8 17:30:22 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 8 17:23:19 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Affected users can change their webpart local settings to English-US as a workaround to avoid this issue until a permanent fix is available.
Final status: We’ve received reports from affected users that this problem is no longer occurring. While we’ve been unable to determine the cause of this issue, should the issue persist, please contact one of our support representatives and we’ll resume our investigation.
Scope of impact: Some users viewing the News web part in managed property filter within SharePoint Online sites may be impacted.
This is the final update for the event.
|
|---|
|
| Time: | Mon Apr 7 21:44:28 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Affected users can change their webpart local settings to English-US as a workaround to avoid this issue until a permanent fix is available.
Current status: Our investigation is ongoing, and we're continuing our efforts to validate with a subset of affected users whether impact persists, as we've received reports that the issue has resolved for some customers.
Scope of impact: Some users viewing the News web part in managed property filter within SharePoint Online sites may be impacted.
Next update by: Tuesday, April 8, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Apr 7 15:39:26 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Affected users can change their webpart local settings to English-US as a workaround to avoid this issue until a permanent fix is available.
Current status: We’re completing the final rounds of validations for our deployment of a change to allow for more robust logging surrounding the API leveraged in the impact scenario, which we intend to be complete by the time of our next scheduled update. This will allow us to further our investigation and better understand the underlying root cause. Additionally, we’re validating with a subset of affected users if impact is still ongoing as we’ve received customer reports of the issue being potentially resolved.
Scope of impact: Some users viewing the News web part in managed property filter within SharePoint Online sites may be impacted.
Next update by: Tuesday, April 8, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Apr 4 15:37:17 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Affected users can change their webpart local settings to English-US as a workaround to avoid this issue until a permanent fix is available.
Current status: Our root cause investigation is ongoing, and we’re readying the deployment of a change to allow for more robust logging surrounding the API leveraged in the impact scenario to further our investigation. Additionally, we’ve confirmed that affected users can change their webpart local settings to "English-US" as a workaround to avoid this issue until a permanent fix is available.
Scope of impact: Some users viewing the News web part in managed property filter within SharePoint Online sites may be impacted.
Next update by: Monday, April 7, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Apr 3 17:38:26 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Current status: We're analyzing recent changes to determine if any may be contributing to the impact. Additionally, we're awaiting network traces for the working and non-working scenarios, which we've requested from affected organizations, to help us more quickly isolate the underlying root cause of this issue.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Friday, April 4, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Apr 2 17:14:35 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Current status: We're continuing to await the results of testing by some affected users to confirm if the suspected configuration issue is solely responsible for the impact. Additionally, if the issue is persistent, we request that affected organizations collect network traces for the working and non-working scenarios so we can investigate further.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Monday, April 7, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 31 16:48:18 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Current status: Our additional analysis into the problem has isolated a news filter property configuration issue that we believe is causing published articles to not appear in the News web part within SharePoint Online sites. We've provided guidance for updating the news filter property and are awaiting testing by affected users to confirm if impact has been remediated.
Scope of impact: Your organization is affected by this event, and some users viewing the News web part in managed property filter, within SharePoint Online sites are impacted.
Next update by: Wednesday, April 2, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Mar 28 15:31:34 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Current status: Our analysis of the gathered web part configuration and logs indicates that a certain component isn't recognizing an entry as provided by the configured property tags which we suspect is causing impact. We're continuing our investigation to isolate the underlying cause of the impact.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Monday, March 31, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Mar 27 21:24:34 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to a web part in managed property filter, within SharePoint Online sites.
Current status: Our analysis of the web part configuration and recent service updates has yet to provide conclusive results regarding our root cause theory. However, we're continuing our best efforts to validate our aforementioned findings and develop a mitigation strategy.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Friday, March 28, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Mar 27 16:43:29 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to web part in managed property filter, within SharePoint Online sites.
Current status: We’re continuing to analyze the web part configuration and recent service updates to validate our findings and determine the appropriate mitigation plan to address the impact
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Friday, March 28, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Mar 27 13:04:32 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to web part in managed property filter, within SharePoint Online sites.
Current status: Our HAR log analysis has isolated a potential News web part configuration issue using managed property filters that we believe may be preventing published articles from appearing in the News web part within SharePoint Online sites. We're further analyzing the web part configuration along with recent updates to the service to help us confirm our findings and so we can determine the appropriate mitigation action plan for remediating the impact.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Thursday, March 27, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Mar 27 08:02:32 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to web part in managed property filter, within SharePoint Online sites.
Current status: We're analyzing HTTP Archive format (HAR) logs provided by some affected users, to help isolate the root cause and develop a mitigation plan.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Thursday, March 27, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Mar 27 06:14:23 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to web part in managed property filter, within SharePoint Online sites.
Current status: We're continuing to review support provided information to isolate the root cause and develop a mitigation plan.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Thursday, March 27, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Mar 27 04:22:07 2025 |
|---|
| Description: | Title: Some users' published articles may not show in the News web part within SharePoint Online sites
User impact: Users' published articles may not show in the News web part within SharePoint Online sites.
More info: Impact is specific to web part in managed property filter, within SharePoint Online sites.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users viewing the News web part in managed property filter, within SharePoint Online sites may be impacted.
Next update by: Thursday, March 27, 2025, at 10:30 AM UTC
|
|---|
|
EX1042577 - Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 27 14:30:00 2025 |
|---|
| End Time: | Mon Apr 7 15:38:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 8 13:33:30 2025 |
|---|
| Root Cause: | A framework change was causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which was resulting in impact. |
|---|
| Next Update: | Tuesday, April 8, 2025, at 7:00 PM UTC |
|---|
|
Details
| Time: | Tue Apr 8 13:33:30 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may have been unable to view or access some public folders in the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may have been unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Final status: We’ve determined that our sync process is complete and our monitoring confirms that this issue is resolved.
Scope of impact: The problem may have impacted some users trying to view, access, create, or delete public folders.
Start time: Monday, January 27, 2025, at 6:30 PM UTC
End time: Tuesday, April 7, 2025, at 7:38 PM UTC
Root cause: A framework change was causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which was resulting in impact.
Next steps:
- We’re reviewing our validation and framework changing procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Apr 7 13:37:04 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may be unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We've identified that some affected folders are still syncing after the impacted infrastructure was restarted. We're continuing to monitor while waiting for the sync process to complete to ensure impact is completely resolved.
Scope of impact: The problem may impact some users trying to view, access, create, or delete public folders.
Start time: Monday, January 27, 2025, at 6:30 PM UTC
Root cause: A framework change is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which is resulting in impact.
Next update by: Tuesday, April 8, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Apr 4 13:37:41 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may be unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We've completed reverting the affecting change, and have restarted the impacted infrastructure. We're monitoring the affected infrastructure to ensure impact is completely resolved for all users as expected.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, January 27, 2025, at 6:30 PM UTC
Root cause: A framework change is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which is resulting in impact.
Next update by: Monday, April 7, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Apr 4 08:01:04 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may be unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We're continuing to revert the aforementioned migration change. Once completed, we will then perform a manual restart on the affected infrastructure and anticipate its completion by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, January 27, 2025, at 6:30 PM UTC
Root cause: A framework change is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which is resulting in impact.
Next update by: Friday, April 4, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 31 07:27:22 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may be unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We've determined that a framework change is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which is resulting in impact. We're reverting the aforementioned migration change and will then perform a manual restart on the affected infrastructure and anticipate its completion by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, January 27, 2025, at 6:30 PM UTC
Root cause: A framework change is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures, which is resulting in impact.
Next update by: Friday, April 4, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Mar 28 06:52:54 2025 |
|---|
| Description: | Title: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users may be unable to view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users may be unable to create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We're manually restarting the affected infrastructure and continuing to work through our hierarchy sync logs to confirm if disabling the aforementioned change has taken effect, in order to validate our hypothesis of the underlying root cause.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, March 31, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Mar 28 00:23:21 2025 |
|---|
| Description: | Title: Some users can't view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users can't view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users can't create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: Our previously mentioned review isolated a Netcore service migration change that we suspect is causing an increase in connection limit exceeded errors and public folder hierarchy sync failures. We’ve disabled the suspected change to mitigate the impact and are working to confirm with our hierarchy sync logs that our action has addressed the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to view or access some public folders within the Outlook desktop client or Outlook on the web are impacted.
Next update by: Friday, March 28, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Mar 27 16:23:53 2025 |
|---|
| Description: | Title: Some users can't view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users can't view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users can't create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We're continuing to review service logs in parallel with error logs to identify the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Your organization is affected by this event, and some users attempting to view or access some public folders within the Outlook desktop client or Outlook on the web are impacted.
Next update by: Friday, March 28, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Mar 27 15:00:37 2025 |
|---|
| Description: | Title: Some users can't view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users can't view or access some public folders within the Outlook desktop client and Outlook on the web.
More info: Additionally, affected users can't create new or delete some existing public folders within the Outlook desktop client and Outlook on the web.
Current status: We're reviewing service logs to identify the root cause of this event, so we can determine our next steps.
Scope of impact: Your organization is affected by this event, and some users attempting to view or access some public folders within the Outlook desktop client or Outlook on the web are impacted.
Next update by: Thursday, March 27, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Mar 27 14:37:45 2025 |
|---|
| Description: | Title: Some users can't view or access some public folders within the Outlook desktop client and Outlook on the web
User impact: Users can't view or access some public folders within the Outlook desktop client and Outlook on the web.
Current status: We're investigating a potential issue with some users being unable to view or access some public folders within the Outlook desktop client and Outlook on the web, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1050275 - Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 09:37:00 2025 |
|---|
| End Time: | Tue Apr 8 00:10:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Apr 8 00:32:38 2025 |
|---|
| Root Cause: | An issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports was causing delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Apr 8 00:32:13 2025 |
|---|
| Description: | Title: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center
User impact: Admins may have seen delays with compliance and device configuration reports in the Microsoft Intune admin center.
More info: The affected reports could potentially have been delayed up to 12 hours.
Final status: We deployed a fix to correct the processing request delays and validated in our telemetry that the impact was remediated.
Scope of impact: This issue may have potentially impacted any admins viewing compliance and device configuration reports in the Microsoft Intune admin center.
Start time: Monday, April 7, 2025, at 1:37 PM UTC
End time: Tuesday, April 8, 2025, at 4:10 AM UTC
Root cause: An issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports was causing delays.
Next steps:
- We’re analyzing performance data associated with the impacted infrastructure so that we can better understand why traffic wasn’t processing efficiently and prevent the impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon Apr 7 22:30:32 2025 |
|---|
| Description: | Title: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center
User impact: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center.
More info: The affected reports could potentially be delayed up to 12 hours.
Current status: We’ve identified an issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports which is causing delays. We're deploying a fix for the issue and will monitor the reports to ensure this resolves the problem.
Scope of impact: This issue may potentially impact any admins viewing compliance and device configuration reports in the Microsoft Intune admin center.
Start time: Monday, April 7, 2025, at 1:37 PM UTC
Root cause: An issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports is causing delays.
Next update by: Tuesday, April 8, 2025, at 6:00 AM UTC
|
|---|
|
EX1030895 - Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun Mar 9 08:07:00 2025 |
|---|
| End Time: | Mon Mar 24 15:06:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 7 17:45:28 2025 |
|---|
| Root Cause: | We determined that email messages contained a small number of mail properties that were formatted in a legacy pattern that the service was unable to process. As the service was unable to handle the format the property was configured in, email messages were delayed, and the logic triggered an NDR. The additional mail properties that used the legacy formatting strings were not common parameters such as subject, body or recipient, but instead, related to less common scenarios such as add-ins used. We’re continuing to investigate why these legacy patterns were introduced. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 31 20:03:31 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 26 20:04:13 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 24 16:42:07 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may have encountered NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may have received an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may have intermittently received calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may have been able to send affected messages by attempting to resend.
Final status: We've completed our work to replay affected email messages and confirmed through service telemetry that NDR failure rates have returned to pre-incident thresholds; the service is maintaining a 99.99 percent success rate. If your organization continues to experience NDRs when sending email messages, we recommend contacting your support representative for further assistance.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may have been affected, although impact is limited to a small subset of messages.
Start time: Monday, March 3, 2025, at 12:00 AM UTC
End time: Monday, March 24, 2025, at 7:06 PM UTC
Root cause: We determined that email messages contained a small number of mail properties that were formatted in a legacy pattern that the service was unable to process. As the service was unable to handle the format the property was configured in, email messages were delayed, and the logic triggered an NDR. The additional mail properties that used the legacy formatting strings were not common parameters such as subject, body or recipient, but instead, related to less common scenarios such as add-ins used. We’re continuing to investigate why these legacy patterns were introduced.
Next steps:
-Please see the PIR for more comprehensive information regarding Next steps.
|
|---|
|
| Time: | Mon Mar 24 09:30:13 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're proceeding with reviewing and monitoring the email replay process to validate that impact has been successfully remediated. However, we're also assessing potential options to expedite the remaining remediation actions.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 24 03:09:59 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We've observed that the email replay process is ongoing and that most email messages have been resent at this time. We're continuing to monitor the progress until completion. In parallel, we're investigating potential options to expedite the remaining remediation actions.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 00:56:06 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We've initiated the process to resend all remaining affected email messages. While the email replay process is ongoing, we've determined that these steps have not yet occurred for all of the remaining impacted infrastructure. We're continuing to monitor the progress in the affected environment to address any unforeseen issue that may arise.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Sun Mar 23 19:30:20 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We've determined that resending email messages for a limited set of customers has been successful. We're now preparing the remaining affected infrastructure to apply the same steps. Once preparation is complete, we'll proceed with resending all remaining affected messages.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Sun Mar 23 17:13:29 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Due to our solution saturating the majority of our internal infrastructure, we're resending affected messages directed to internal and external recipients for a limited set of customers. We estimate this will take a couple hours to complete, and once we've validated its success we'll proceed with resending affected messages for all other customers. If a recipient didn't receive a message previously, they will receive it as a new email. In instances of previously sent email that was delivered to some but not all recipients, users that previously received the email will be sent a duplicate copy. Upon completion, we'll validate if any email is routed through the small subset of infrastructure that has yet to receive the fix, and we'll resubmit email destined for internal recipients within affected customer tenants to ensure they're delivered as expected.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Root cause: Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Mar 22 17:58:45 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The roll out of our updated solution has saturated across the vast majority of our internal infrastructure, and we've confirmed that there's no additional impact and the issue no longer occurs. We're continuing the deployment to the affected environment to restore service and are monitoring its progress to determine an estimated timeline to resolution.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 23, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Mar 21 17:52:42 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We discovered our initial fix unintentionally caused duplicate messages to be sent to external users. We stopped the initial fix and are rolling out the updated solution to our internal infrastructure to validate there is no additional impact. We’ll provide an estimated deployment timeline once one becomes available.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 22, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Mar 20 18:11:55 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The fix to address the underlying issues is in the final stages of validation in our internal environment, and we anticipate that this process will complete by our next scheduled update. We'll aim to provide an estimated deployment timeline at this time.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Friday, March 21, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Mar 19 21:48:38 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re making steady progress with the development of the change to address the underlying issues. The fix has been developed and is currently being tested in our internal environment to monitor its effectiveness and minimize potential impact. Once we confirm that the fix is optimized to fully remediate the issue, we’ll proceed with a broader deployment.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Thursday, March 20, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Mar 19 16:01:28 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're investigating a change to background caching logic as a potential underlying cause of impact. While our current mitigations have effectively eliminated the impact from this issue, we’re creating an additional change to address the underlying problem, which is expected to completely remediate the issue. We’ll continue to provide updates on the build progress and closely monitor the service environment.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Thursday, March 20, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Mar 19 06:06:46 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: While we continue our investigation into the root cause of the impact, we’re monitoring the volume of intermittent failing messages, which continues to gradually decrease, and applying additional settings changes as required. We will continue to closely monitor the service for an extended period to ensure the fix is mitigating the issue for all impacted users.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Wednesday, March 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Mar 18 20:10:51 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The configuration changes we’ve made are having the intended effect of reducing the volume of intermittent message failures. We’re continuing to apply some additional settings changes in the impacted infrastructure to further stabilize the environment. We’ll remain in a period of extended close monitoring of the service.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Wednesday, March 19, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Mar 18 14:56:17 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re continuing to see a sustained reduction in NDR errors as our fix has reached 99.4% saturation. We've observed a small number of intermittent message failures post fix deployment, and we're working to adjust some additional backend configurations to prevent this from occurring. We’ll continue to carefully monitor service performance and open any necessary workstreams to fully remediate the impact.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Wednesday, March 19, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Mar 18 09:54:48 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're continuing to monitor the deployment of the fix as it progresses throughout the affected environment and the current saturation level is at 99.3%. While the majority of impact is mitigated, users may still see some NDRs until the fix is fully deployed across the infrastructure. We'll keep this notification active and provide an immediate update should there be a substantial change in service performance, otherwise the next update will be provided at 7:30 PM UTC.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Mar 18 00:48:01 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We have confirmed that the deployment of the fix is progressing as expected. In parallel, we have exhausted manual efforts to safely expedite the deployment and expect the remaining affected infrastructure to take an extended period to complete. We still remain confident that a majority of the impact has been mitigated. If your organization continues to see high impact related to this event, please work with your support representative to gather the relevant diagnostic data so we may explore avenues to address the impact being experienced.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Wednesday, March 19, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 21:13:52 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our worldwide patch has exceeded well above 95 percent saturation across the affected infrastructure and our internal testing continues to affirm that the fix is addressing the issue as expected. We’ll continue monitoring the saturation of the fix as it continues its progression, and we’ll provide updates as they become available.
In addition, our reproductions of impact have been helpful in our investigation to identify a potential root cause. We’ll continue working on this investigation in parallel with our monitoring.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Mar 17 17:58:22 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The worldwide patch is moving along as anticipated and has saturated to over 90% of environments. Our telemetry indicates that the fix is working as expected. We predict that there may be certain portions of the affected infrastructure that may still take several hours to receive the fix. We’ll continue to closely monitor the impacted environments while the patch deployment completes.
In parallel we’re continuing to focus on internal reproductions of impact in order to isolate the root cause of the incident.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 17 14:53:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: After some additional validations, we’ve begun a worldwide rollout of our patch and anticipate it will take up to twelve hours to fully saturate all environments. We expect users to experience relief from impact as they receive the fix. We’ll continue to closely monitor the service health during this rollout.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 11:38:52 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’ve deployed the secondary fix via an emergency patch to a small portion of production infrastructure and have validated that email replay is successful as expected and that NDR errors have been eliminated in this environment. We're now preparing to release this fix more broadly.
Additionally, we’ve gathered additional trace logs from internal reproductions that we are analyzing to isolate a potential root cause.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 06:22:41 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The targeted deployment has completed; however, a separate issue has been highlighted with a code path for a specific property which is also contributing to the NDR failures. We’re testing a fix for this issue internally and are conducting thorough checks to ensure full recovery.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 04:30:37 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're continuing targeted deployments to address residual NDRs, which is completing as expected. To understand the more recent increasing NDRs, we’re reproducing the issue internally to get a better understanding of the next steps required to resolve the NDRs.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Mar 17 01:53:44 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our targeted deployment efforts are progressing steadily and safely across the remaining impacted infrastructure as a result of prioritization efforts. Concurrently, we’ve received reports of an increase in NDRs that may be causing additional impact. We’re investigating these reports and available telemetry to develop a new mitigation strategy.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Mar 16 19:33:12 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re continuing to perform targeted deployments of the fix to the remaining affected service infrastructure. We'll be treating this process with the highest priority and urgency to ensure that users are no longer impacted by this event. If your organizations continue to experience impact, please file a support ticket so we can work directly work with your representatives and address the issue. We deeply appreciate your organization’s continued patience while we progress the deployments of the fix.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Sun Mar 16 15:03:49 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our fix has saturated 98 percent of all affected regions, and a majority of customers should be experiencing relief. Users who received NDR messages should now be able to resend them. For the remaining two percent of the affected infrastructure, we’re reviewing our targeted deployment options to determine if we can help to expedite the process to fully resolve the impact. We understand the impact this has on your organization and appreciate your patience while we focus on our fix.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Sat Mar 15 22:56:10 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re continuing our monitoring of the fix deployment. We've seen a substantial surge in the fix’s saturation of the environment within the last few hours, as we're now above 80 percent deployment across all regions, which is much sooner than expected. In addition, our telemetry also shows an increase in service health and reduced error rates, which corresponds to our deployment efforts. We're closely monitoring error rates to ensure continued recovery and readiness for any necessary mitigation actions.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 19:22:48 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're closely monitoring the propagation of the fix, which remains steadily on track with our original estimation towards full saturation. In addition, our telemetry aligns with the fix path and continues to show improvement in the error rate trajectory.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 17:17:29 2025 |
|---|
| Description: | Our deployment is in progress and has reached approximately 26 percent saturation to affected infrastructure.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sat Mar 15 12:26:20 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our main fix deployment has completed on a limited portion of the infrastructure and is showing a marked improvement in the error rate. We have started expanding this deployment to the rest of the affected infrastructure and expect this will propagate over the next day.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 00:19:42 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The fix deployment continues to saturate within our internal infrastructure, and telemetry data remains positive. Additionally, we're identifying infrastructure optimized for fix integration to enhance opportunities for seamless implementation. We’ll continue to monitor the status of all deployments, identify opportunities for enhancements, and provide status updates as they become available.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 22:20:53 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix has successfully reached over 30 percent saturation across our internal infrastructure. Telemetry data continues to indicate that the deployment is healthy and error-free. Concurrently, we're assessing the effectiveness of additional fixes, isolating potential errors, and making refinements to address identified issues. We’ll maintain the momentum of all rollouts and deployments and keep you informed with updates as they become available.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 20:26:47 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix is 22 percent saturated within our internal infrastructure. Our telemetry indicates no errors associated with NDRs from our internal infrastructure with the potential fix. Our parallel deployment of the potential fix to a subset of service infrastructure is 60 percent saturated. Collecting trace data of the failures continues to be a challenge. We plan to continue our rollout of the potential fix as our deployments complete, if telemetry indicates the infrastructure with the fix is in a healthy state.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 18:26:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix has reached ten percent saturation within our internal infrastructure. We're continuing to monitor telemetry and use trace data to determine the root cause. We've had difficulty collecting trace data of the failures due to the transient nature of this incident. We've started deploying the potential fix to a subset of service infrastructure to help with collecting this trace data to assist our investigation.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 16:29:58 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We've expanded deploying our potential fix to our entire internal infrastructure and continue to monitor targeted restarts of machines with the fix to ensure relief is resilient. Concurrently, we've deployed updates to our tooling that provide us with additional telemetry which we're using with additional NDR trace data to continue to investigate and provide a more detailed diagnosis of the root cause.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Friday, March 14, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 13:07:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Current status: We're continuing to verify the effectiveness of the potential fix deployed to an isolated section of our internal infrastructure. We're conducting multiple targeted restarts of machines containing the fix to ensure the expected relief is achieved. Additionally, we're closely monitoring our diagnostic telemetry data to isolate the root cause of the issue, and we're reviewing the overall service health during this process. Once we've determined the effectiveness of the fix, we'll begin deploying it to the wider environment.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 11:34:51 2025 |
|---|
| Description: | We've completed the deployment of the fix within an isolated section of our internal infrastructure. We're now conducting targeted restarts of machines containing the fix to verify its effectiveness. Early indications suggest the fix is producing the desired effect but we're closely monitoring our diagnostic telemetry to ensure impact is being fully mitigated. Once we're satisfied the fix is providing the expected relief, we'll begin deploying the fix to the wider environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 10:29:55 2025 |
|---|
| Description: | We're closely monitoring the deployment of the fix within an isolated section of our internal infrastructure, and it is nearing completion. Once the deployment completes, we'll conduct targeted reboots of machines containing the fix as part of the process to verify the effectiveness of the fix. As previously mentioned, if effective, the fix will then be deployed to the wider environment. Additionally, we're continuing to analyze telemetry data to isolate the root cause of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 09:12:12 2025 |
|---|
| Description: | We're continuing to analyze diagnostic telemetry data to isolate the root cause of the issue. In parallel, we've developed a fix and we're currently testing the effectiveness of the fix within an isolated section of our internal infrastructure to ensure the it provides the expected relief from impact. If effective, the fix will be deployed to the wider environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 08:25:27 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Current status: In addition to our other work streams, we believe a recent update that contains a code issue is causing the message delivery failures, due to the content not being processed as expected. To aid our mitigation efforts, we’ve halted the update to prevent additional users from becoming affected by the issue. We’re continuing to analyze diagnostic data to validate the root cause of the issue.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 00:03:27 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've identified that impact is not limited to users sending IRM protected email as we previously communicated. We've updated the title, user impact, more info and scope of impact sections of this communication to reflect that new information. Our previously stated fix will continue deploying to affected infrastructure while we continue monitoring its efficacy as it progresses. Concurrently, we’ve shifted attention to our reproduction efforts and deeper log analysis to further isolate the cause of impact and identify new mitigation strategies.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 21:36:07 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've developed and subsequently deployed the aforementioned potential fix and are monitoring the affected service environment while reaching out to some affected users for testing to ensure that it has the desired results and to determine whether any additional mitigating actions are required.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 19:32:36 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: Although our efforts to reproduce this issue have been inconclusive so far, we're in the process of developing a potential fix for this issue which will undergo our internal validation tests before being applied throughout the affected environments. Additionally, we're attempting to gather dump logs which we anticipate will aid in expediting our understanding of the underlying cause of impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Friday, March 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Mar 13 17:13:36 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've determined this is impacting email messages protected by IRM, and we've updated the Title, User impact, More info, and Scope of impact sections to reflect this. We're continuing our efforts to reproduce this issue to help us further our investigation into the root cause of impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 15:57:24 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving some email messages in Exchange Online
User impact: Users may encounter failures when sending or receiving some email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've identified that a recent update may have introduced inaccurate content conversion logic which is preventing some email from being sent or received. We're attempting to reproduce this issue so we can test a potential code fix to this logic that we expect will remediate impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Mar 13 13:31:38 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving some email messages in Exchange Online
User impact: Users may encounter failures when sending or receiving some email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We're reviewing Non-Delivery Reports (NDRs) gathered from impacted users to identify why users may encounter failures when sending or receiving some email messages in Exchange Online.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 7:30 PM UTC
|
|---|
|
MO1040235 - Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
| Status: | serviceRestored |
|---|
| Start Time: | Sat Mar 22 20:00:00 2025 |
|---|
| End Time: | Mon Apr 7 15:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 7 16:45:37 2025 |
|---|
| Root Cause: | A discrepancy in the time zone database configuration was leading to mismatches in the Daylight saving time (DST) end date for the Asuncion time zone. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Apr 7 16:14:25 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may have seen an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may have included the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
Final status: We've confirmed that the deployment of the fix completed and validated with some users who initially reported the issue that the impact is remediated.
Scope of impact: Users in Paraguay may have seen an incorrect time that was one hour ahead of the current time in multiple Microsoft 365 apps and services.
Start time: Sunday, March 23, 2025, at 12:00 AM UTC
End time: Monday, April 7, 2025, at 7:00 PM UTC
Root cause: A discrepancy in the time zone database configuration was leading to mismatches in the Daylight saving time (DST) end date for the Asuncion time zone.
Next steps:
- We're further reviewing the time zone database configuration to understand how the discrepancy 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 time zone changes.
This is the final update for the event.
|
|---|
|
| Time: | Fri Apr 4 16:18:39 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365:
https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: While the deployment of our fix is progressing more slowly than initially anticipated, we've confirmed that it's approximately 70 percent complete, and we expect that it should have completed, or be close to completion, by our next scheduled communications update.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Start time: Sunday, March 23, 2025, at 12:00 AM UTC
Root cause: A discrepancy in the time zone database configuration is leading to mismatches in the Daylight saving time (DST) end date for the Asuncion time zone.
Next update by: Monday, April 7, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Apr 1 16:55:13 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365:
https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: The deployment of the fix is progressing, and our updated fix deployment timeline expects the patch deployment will have completed, and for impact to be remediated, by our next scheduled update.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Start time: Sunday, March 23, 2025, at 12:00 AM UTC
Estimated time to resolve: Our fix deployment timelines expect that the deployment for this event will have completed by Friday, April 4, 2025.
Root cause: A discrepancy in the time zone database configuration is leading to mismatches in the Daylight saving time (DST) end date for the Asuncion time zone.
Next update by: Friday, April 4, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Mar 28 16:45:08 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365:
https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: The patch deployment is taking longer than initially expected to complete. We're continuing to monitor the deployment as it progresses and we'll provide a timeline if one becomes available.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Tuesday, April 1, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 17:51:30 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365:
https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We’ve determined that a nation-wide decision regarding the time zone was implemented and the patch to accommodate this change, while being deployed, hasn’t completed its deployment to align with this change. We’re monitoring the ongoing deployment of the patch to address this issue and expect that it should complete to resolve this problem by our next update.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Friday, March 28, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 14:17:06 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365:
https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We're continuing to analyze the impact scenario to better understand the underlying issue. We’re also reviewing recent updates to Microsoft 365 to verify if impact could be caused by a recent update or change. In addition, we’ve verified that affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact and we've provided documentation in the "More info" section of this communication on how to change your time zone in Microsoft 365.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 24 12:21:49 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following:
- Outlook on the web
- Microsoft Teams web client
- SharePoint Online web client
- Microsoft Word web client
- Myaccount.microsoft.com
Users located in Paraguay maye see their time as one hour ahead of the current time. While we’re focused on remediation, users that have access to the affected services’ desktop apps can use these to bypass the impact.
Current status: We're reviewing support case information to better understand the underlying impact scenario along with reviewing recent updates to the Microsoft 365 suite to verify if impact could be caused by a recent update or change.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Mar 24 11:20:04 2025 |
|---|
| Description: | Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected apps may include the following:
- Outlook on the web
- Microsoft Teams web client
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We've received reports from multiple users in Paraguay that users see an incorrect time in multiple Microsoft 365 apps and services. We're validating with affected users the list of apps affected to better understand the underlying root cause and what steps we can take to resolve impact as swiftly as possible.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 4:30 PM UTC
|
|---|
|
TM1049822 - Some users may be unable to see Call Queues or Auto Attendants in the Microsoft Teams admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 08:00:00 2025 |
|---|
| End Time: | Mon Apr 7 11:20:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 7 12:43:36 2025 |
|---|
| Root Cause: | A subset of service infrastructure that helps facilitate Call Queues and Auto Attendants in the Microsoft Teams admin center has dropped below our manageable service performance thresholds, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Apr 7 12:43:36 2025 |
|---|
| Description: | Title: Some users may be unable to see Call Queues or Auto Attendants in the Microsoft Teams admin center
User impact: Users may have been unable to see Call Queues or Auto Attendants in the Microsoft Teams admin center.
Final status: Our service telemetry analysis has isolated a subset of service infrastructure that helps facilitate Call Queues and Auto Attendants in the Microsoft Teams admin center which had dropped below our manageable service performance thresholds, resulting in impact. After routing affected service traffic to alternate available service infrastructure, our internal service telemetry has validated that impact has been remediated.
Scope of impact: Impact was specific to some users who are located in North America, and Canada.
Start time: Monday, April 7, 2025, at 12:00 PM UTC
End time: Monday, April 7, 2025, at 3:20 PM UTC
Root cause: A subset of service infrastructure that helps facilitate Call Queues and Auto Attendants in the Microsoft Teams admin center has dropped below our manageable service performance thresholds, resulting in impact.
Next steps:
- We're further analyzing the affected subset of Teams service infrastructure to help us isolate the source for the lower-than-expected service performance levels, and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Apr 7 09:53:58 2025 |
|---|
| Description: | Title: Some users may be unable to see Call Queues or Auto Attendants in the Microsoft Teams admin center
User impact: Users may be unable to see Call Queues or Auto Attendants in the Microsoft Teams admin center.
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 located in North America.
Start time: Monday, April 7, 2025, at 12:00 PM UTC
Next update by: Monday, April 7, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Apr 7 09:17:02 2025 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
TM1049655 - Some users may have experienced delays when loading some online images within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 03:10:00 2025 |
|---|
| End Time: | Mon Apr 7 04:38:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Apr 7 06:07:23 2025 |
|---|
| Root Cause: | A recent configuration change, intended to improve general service operations, inadvertently resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Apr 7 06:07:23 2025 |
|---|
| Description: | Title: Some users may have experienced delays when loading some online images within Microsoft Teams
User impact: Users may have experienced delays when loading some online images within Microsoft Teams.
Final status: We've determined that a recent configuration change, intended to improve general service operations, inadvertently resulted in impact. We've reverted aforementioned change and confirmed after a period of monitoring that impact has been resolved.
Scope of impact: Impact is specific to users hosted in North America.
Start time: Monday, April 7, 2025, at 7:10 AM UTC
End time Monday, April 7, 2025, at 8:38 AM UTC
Root cause: A recent configuration change, intended to improve general service operations, inadvertently resulted in impact.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This the final update for this event.
|
|---|
|
| Time: | Mon Apr 7 04:44:02 2025 |
|---|
| Description: | Title: Some users may experience delays when loading some online images within Microsoft Teams
User impact: Users may experience delays when loading some online images within Microsoft Teams.
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 users hosted in North America.
Start time: Monday, April 7, 2025, at 7:10 AM UTC
Next update by: Monday, April 7, 2025, at 11:00 AM UTC
|
|---|
|
|
