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 Sat Nov 29 13:30:10 2025.
DZ1190663 - Admins may be unable to access the Deep Analysis functionality within the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Nov 20 08:00:00 2025 |
|---|
| End Time: | Thu Nov 27 19:40:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 28 18:32:00 2025 |
|---|
| Root Cause: | A recent deployment aimed at enhancing our services introduced a faulty error handling logic regression that caused critical APIs to return 404 errors, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 28 18:32:00 2025 |
|---|
| Description: | Title: Admins may be unable to access the Deep Analysis functionality within the Microsoft Defender XDR portal
User impact: Admins may have been unable to access the Deep Analysis function in the Microsoft Defender XDR portal.
Final status: We determined that this issue was caused by a recent deployment that introduced a faulty error handling logic regression, which caused critical APIs to return 404 errors. We completed a reversion of this deployment and have since confirmed this remediated impact.
Scope of impact: This event may have impacted some admins from being unable to access the Deep Analysis function in the Microsoft Defender XDR portal.
Start time: Thursday, November 20, 2025, at 1:00 PM UTC
End time: Friday, November 28, 2025, at 12:40 AM UTC
Root cause: A recent deployment aimed at enhancing our services introduced a faulty error handling logic regression that caused critical APIs to return 404 errors, which resulted in impact.
Next steps:
- We're reviewing our deployment processes to better understand how we might detect and prevent similar service incidents from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 28 18:06:11 2025 |
|---|
| Description: | Title: Admins may be unable to access the Deep Analysis functionality within the Microsoft Defender XDR portal
User impact: Admins may have been unable to access the Deep Analysis function in the Microsoft Defender XDR portal.
Current status: We've investigated a problem in which Global Admins may have been unable to access the Deep Analysis functionality within the Microsoft Defender XDR portal and received an error. We've confirmed that service is now restored and will provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
|
|---|
|
MO1176905 - Some admins or users may be unable to access multiple Microsoft 365 services
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Oct 21 09:50:39 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 28 10:22:24 2025 |
|---|
| Root Cause: | A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact. |
|---|
| Next Update: | Friday, December 5, 2025, at 3:30 PM UTC |
|---|
|
Details
| Time: | Fri Nov 28 10:22:24 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've deployed a part of the fix and have also successfully tested the remaining part of the fix which is being deployed to the affected infrastructure. We anticipate that this should complete by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Estimated time to resolve: Friday, December 5, 2025
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, December 5, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 10:22:19 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've validated a part of the fix which is ready to be deployed, and the remaining part of the fix is under review to be tested prior to deploying it to the affected infrastructure. We anticipate to provide the estimated deployment time line by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 28, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 14 09:09:32 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've developed the aforementioned fix to address the impact. We're now conducting a validation and testing process to ensure the effectiveness of the fix prior to deploying it to the affected infrastructure. We expect to share an estimated deployment time line by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 21, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 09:03:02 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We’re proceeding to develop a fix to address the impact and will begin testing once development is complete to ensure effectiveness before deployment. We expect to share an estimated completion time by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 14, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 09:42:15 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: Our development of the fix in ongoing and we'll share a completion timeline when one becomes available. Whilst we work on developing our fix to update the SecurityEnabled property from False to True, admins can continue using the cmdlets shared in the "More info" section to remediate the impact.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 7, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Oct 27 11:01:02 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We're continuing to develop and validate our fix, designed to update the SecurityEnabled property from False to True, and we expect the validations and deployment to complete in two to three weeks. We'll provide an updated deployment timeline as one becomes available. While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can use the cmdlets shared in the "More info" section to remediate the impact.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, November 3, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Oct 24 06:12:49 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We’ve developed a potential fix to update SecurityEnabled from False to True for the remaining affected groups. The fix is currently undergoing internal validation to ensure it fully mitigates the issue before deployment to the affected environments.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, October 27, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 01:42:58 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We're continuing to explore options for updating the SecurityEnabled to True from False for the remaining affected groups. Additionally, our ongoing monitoring indicates that new properties are unaffected.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, October 24, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Oct 22 01:58:14 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We've received confirmation that reverting the offending change which caused to the Group SecurityEnabled property to change to False as default completed, and new properties are no longer being set to False by default. Additionally, we're exploring options on how to update the SecurityEnabled to True from False for the remaining affected groups to ensure the underlying issue is fully resolved.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Thursday, October 23, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 09:52:20 2025 |
|---|
| Description: | Title: Admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the Microsoft 365 Group SecurityEnabled changed to false.
Current status: We've identified that a recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact. We've reverted the aforementioned change, and we're working with affected users to verify that impact has been fully resolved.
Scope of impact: Your organization is affected by this event, and any admin or users attempting to access any Microsoft 365 services with Microsoft 365 Group SecurityEnabled set to false is impacted.
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Wednesday, October 22, 2025, at 7:00 AM UTC
|
|---|
|
IT1188607 - Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Tue Nov 11 14:25:00 2025 |
|---|
| End Time: | Thu Nov 27 13:02:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 27 14:45:54 2025 |
|---|
| Root Cause: | A supporting process that Intune utilizes for propagating reporting workflows in Data Warehouses was degraded and caused a backlog of requests. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 27 14:45:54 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experienced delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may have seen that some Data Warehouse reports were missing data, causing reports to have been incomplete or to fail. Additionally, some device compliance policy and setting state summaries may have experienced failures.
Affected users may have been missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Final status: We've confirmed after monitoring that our Data Warehouse remediation operation has completed. Service health telemetry indicates that impact was successfully remediated for all users.
Scope of impact: Admins who were attempting to utilize a subset of reporting workflows in Microsoft Intune may have been impacted.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
End time: Thursday, November 27, 2025, at 6:02 PM UTC
Root cause: A supporting process that Intune utilizes for propagating reporting workflows in Data Warehouses was degraded and caused a backlog of requests.
Next steps:
- We're investigating what caused the supporting process to be degraded to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 26 19:41:30 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: Our monitoring indicates that the Data Warehouse remediation operation is progressing and is nearly fifty percent complete. We'll continue monitoring the process to ensure the report data becomes up to date and remediates impact.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A supporting process that Intune utilizes for propagating reporting workflows in Data Warehouses was degraded and caused a backlog of requests.
Next update by: Friday, November 28, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Nov 26 01:33:13 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: We're continuing to monitor the progress of the Data Warehouse remediation operation to ensure it completes as expected. In parallel, we're continuing our investigation of the service health metrics and the high volume of requests to determine what additional mitigation steps may be needed to fully resolve the impact.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Next update by: Thursday, November 27, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Nov 25 21:13:27 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: We've verified that our Data Warehouse remediation operation is progressing in line with expectations, and anticipate this process may complete by the time of our next scheduled update. However, our internal metrics indicate that a continually high volume of requests is contributing to some persisting impact. We're continuing with further investigation and troubleshooting to determine our next steps towards full remediation.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Next update by: Wednesday, November 26, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Nov 25 14:10:38 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: Our Data Warehouse reporting data recovery is progressing, and our internal service telemetry validates that workflow reporting is starting to reflect accurate data. We'll provide an updated timeline for our mitigations and when testing with affected admins will be possible once it is available.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Wednesday, November 26, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Nov 24 14:29:00 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: The recovery of the reporting data for Data Warehouse continues to progress, and some admins will see their workflow reporting begin to reflect accurately. We're monitoring as this process continues to ensure it completes in a timely manner.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Tuesday, November 25, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 10:31:30 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: The process of recovering the reporting data for Data Warehouse is ongoing and we expect admins will see accurate reporting workflows in Microsoft Intune incrementally while our recovery efforts progress.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Monday, November 24, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Sun Nov 23 21:41:08 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: We're continuing the process of recovering the reporting data for Data Warehouse and we expect admins will see accurate reporting workflows in Microsoft Intune incrementally while our recovery efforts progress.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Monday, November 24, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Sun Nov 23 11:14:08 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Affected users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports.
Current status: During our analysis of the ongoing processing of reporting data for Data Warehouse, we isolated two additional impact scenarios for a subset of users. We've determined that a subset of users may be missing up to 13 hours of reporting data for Device Compliance and Device Configuration reports. We've outlined this additional impact scenario in the "More Info" section of this communication and expanded communications to additional affected admins. While we continue to recover reporting data for Date Warehouse, we're analyzing the additional affected portions of Intune service infrastructure to determine what actions we can take to recover missing data and expedite recovery for affected admins.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Monday, November 24, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Sat Nov 22 12:21:15 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: We've gotten approximately 75 percent of the reporting data for Data Warehouse up to date and processing at the desired speed. We'll aim to provide a timeline for all Data Warehouse reporting data to be updated by our next scheduled communications update.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Monday, November 24, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Nov 21 20:42:56 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data Warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: The process of manually copying data for previous days completed successfully. We're continuing to work on getting the new reporting data for Data Warehouses up to date and processing at the desired speed. We'll provide an update on our progress by the next scheduled update time.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Saturday, November 22, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 12:57:44 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: Our efforts to rebalance the affected infrastructure are successfully progressing. Additionally, the jobs to manually copy data for previous days are running successfully, and as this process continues, some users may begin to see their older reporting data populate. We’ll provide a remediation timeline once available.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Saturday, November 22, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Nov 20 22:00:20 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: We’re continuing our efforts at rebalancing the affected infrastructure to remediate the issue in the near term, in tandem with manually backfilling missing data in the Data warehouse to completely mitigate impact. Additionally, we anticipate that we’ll have a full remediation timeline by our next scheduled update.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Friday, November 21, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 20:14:26 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: We’ve determined that a recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact. We’ve identified the component responsible for increased resource utilization and we’re in the process of rebalancing the affected infrastructure to remediate impact.
Scope of impact: Admins who are attempting to utilize a subset of reporting workflows in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 7:25 PM UTC
Root cause: A recent service update is resulting in an unexpected volume of traffic to the components of infrastructure responsible for facilitating the affected reporting workflows, which is resulting in impact.
Next update by: Friday, November 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Nov 20 19:40:23 2025 |
|---|
| Description: | Title: Some admins experience delays, stale data, or failures when attempting to use reporting workflows in Microsoft Intune
User impact: Admins experience delays, stale data, or failures when attempting to use some reporting workflows in Microsoft Intune.
More info: Affected users may see that some Data warehouse reports are missing data, causing reports to be incomplete or to fail. Additionally, some device compliance policy and setting state summaries may experience failures.
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1189359 - Users may be unable to open Excel files attached to email messages in new Outlook and receive an error
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Nov 23 21:33:31 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 27 14:20:42 2025 |
|---|
| Root Cause: | An encoding error within Excel file names is resulting in this impact. |
|---|
| Next Update: | Monday, December 1, 2025, at 8:00 PM UTC |
|---|
|
Details
| Time: | Mon Nov 24 16:40:09 2025 |
|---|
| Description: | Title: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error
User impact: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error.
More info: Users receive an error stating: "Try opening the file again later."
This issue impacts attachments that contain non-ASCII characters. As a way to avoid impact, users can utilize Outlook on the web or download the file locally to manually open Excel files.
Current status: We've developed a fix to address the missing encoding in the requests used to open files. We're validating this deployment while we work to understand why this encoding error is occurring.
Scope of impact: Any user may be unable to open Excel files attached to email messages in the new Outlook client if the attachment contains non-ASCII characters.
Root cause: An encoding error within Excel file names is resulting in this impact.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 15:04:29 2025 |
|---|
| Description: | Title: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error
User impact: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error.
More info: Users receive an error stating: "Try opening the file again later."
This issue impacts attachments that contain non-ASCII characters. As a way to avoid impact, users can utilize Outlook on the web or download the file locally to manually open Excel files.
Current status: We've discovered an encoding error within the file names that's resulting in impact. We've developed a fix to resolve the encoding error and are validating and testing the solution prior to initiating deployment, while simultaneously working to understand the source of this encoding error.
Scope of impact: Any user may be unable to open Excel files attached to email messages in the new Outlook client if the attachment contains non-ASCII characters.
Root cause: An encoding error within Excel file names is resulting in this impact.
Next update by: Monday, November 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Sun Nov 23 22:13:59 2025 |
|---|
| Description: | Title: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error
User impact: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error.
More info: Users receive an error stating: "Try opening the file again later."
This issue impacts attachments that contain non-ASCII characters. As a way to avoid impact, users can utilize Outlook on the web or download the file locally to manually open Excel files.
Current status: We're reviewing the provided HTTP Archive format (HAR) logs and errors to identify the underlying cause of impact, which will help to inform our next troubleshooting steps.
Scope of impact: Any user may be unable to open Excel files attached to email messages in the new Outlook client if the attachment contains non-ASCII characters.
Next update by: Monday, November 24, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Sun Nov 23 21:48:49 2025 |
|---|
| Description: | Title: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error
User impact: Users may be unable to open Excel files attached to email messages in new Outlook and receive an error.
More info: Users receive an error stating: "Try opening the file again later."
This issue impacts attachments that contain non-ASCII characters. As a way to avoid impact, users can utilize Outlook on the web or download the file locally to manually open Excel files.
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.
|
|---|
|
DZ1189564 - Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Nov 24 12:23:28 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 27 07:21:16 2025 |
|---|
| Root Cause: | A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events. |
|---|
| Next Update: | Sunday, November 30, 2025, at 12:00 PM UTC |
|---|
|
Details
| Time: | Thu Nov 27 07:21:16 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: After our review of diagnostic data we estimate that the backlog of data should complete by Sunday, November 30, 2025. We're continuing our efforts in exploring ways in which we can expedite this process.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Estimated time to resolve: Sunday, November 30, 2025
Root cause: A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events.
Next update by: Sunday, November 30, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Nov 27 05:15:53 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're reviewing diagnostic data to confirm that the backlog of data will still complete by Thursday, November 27, 2025.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Root cause: A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events.
Next update by: Thursday, November 27, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Nov 26 05:02:22 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're progressing with our efforts to process the backlog of data and anticipate that this will complete by Thursday, November 27, 2025. Additionally, we're exploring ways in which we can expedite this process.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Estimated time to resolve: Thursday, November 27, 2025
Root cause: A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events.
Next update by: Thursday, November 27, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Nov 25 04:55:18 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're continuing to process the backlog of data and anticipate that this will complete by Thursday, November 27, 2025.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Estimated time to resolve: Thursday, November 27, 2025
Root cause: A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events.
Next update by: Wednesday, November 26, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Nov 24 15:42:47 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We've identified a misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events. We've corrected the misconfiguration and expect that the backlog will complete by out next update; however, we're exploring options to expedite the completion.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Root cause: A misconfiguration within the portion of service infrastructure responsible for communicating data from Entra ID which caused the impact and resulted in a backlog of unprocessed Entra ID sign-in events.
Next update by: Tuesday, November 25, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Nov 24 14:07:12 2025 |
|---|
| Description: | Title: Some admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to seven days delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: Our investigation of the routing events is ongoing to isolate the source of the impact and develop a remediation plan.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Next update by: Monday, November 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 12:53:05 2025 |
|---|
| Description: | Title: Some admins may encounter up to two-hour delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to two-hour delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We've identified that a portion of infrastructure responsible for routing events within our service is operating in a suboptimal state. We're continuing to investigate this affected infrastructure to isolate the root cause and determine the next steps to remediate the impact.
Scope of impact: Some admins viewing one of the affected scenarios for Microsoft Entra ID sign-in events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Monday, November 24, 2025, at 3:05 AM UTC
Next update by: Monday, November 24, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 12:37:18 2025 |
|---|
| Description: | Title: Some admins may encounter up to two-hour delays for sign-in events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter up to two-hour delays for sign-in events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft Entra ID sign-in event scenarios include but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're investigating a potential issue with Microsoft Defender for Cloud Apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1188100 - Multiple issues within Microsoft 365 related to data classification and sensitivity service
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Nov 19 02:15:00 2025 |
|---|
| End Time: | Wed Nov 19 20:25:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 27 02:48:33 2025 |
|---|
| Root Cause: | A network access policy implementation issue was preventing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs). |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 26 19:37:02 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 26 19:36:13 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 19 21:34:32 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services included, but were not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview, including the Microsoft Purview browser extension
- Purview DLP Agent
Final status: We’ve confirmed recovery efforts were successful, and service health has been fully restored.
Scope of impact: Impact was specific to some users who were served by sections of infrastructure located in North America and Europe and were attempting to leverage Data Classification and Sensitivity labeling services such as those identified in the More info section above.
Start time: Wednesday, November 19, 2025, at 7:15 AM UTC
End time: Thursday, November 20, 2025, at 1:25 AM UTC
Root cause: A network access policy implementation issue was preventing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next steps:
- We're reviewing our policy implementation procedures to prevent similar issues from occurring in the future.
A preliminary post incident report will be published within 2 business days of this post's closure, followed by a finalized post incident report published within 5 business days of closure.
|
|---|
|
| Time: | Wed Nov 19 19:22:01 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services include, but are not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview, including the Microsoft Purview browser extension
- Purview DLP Agent
Current status: We're continuing to observe gradual service health recovery as we restart the dependent VMs to facilitate the acceptance of the healthy network access policy.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to leverage Data Classification and Sensitivity labeling services such as those identified in the More info section above.
Root cause: A network access policy implementation issue is preventing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next update by: Thursday, November 20, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 17:27:34 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services include, but are not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview
- Purview DLP Agent
Current status: We've determined a network access policy implementation issue is preventing the service from accessing the dependent VMs. We're restoring this policy to a previously known healthy state and are observing gradual service recovery across the affected environments.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to leverage Data Classification and Sensitivity labeling services such as those identified in the More info section above.
Root cause: A network access policy implementation issue is preventing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next update by: Thursday, November 20, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 15:22:27 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services include, but are not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview
- Purview DLP Agent
Current status: We're comprehensively reviewing policy changes and networking configurations supporting the dependent load balancing infrastructure to isolate any coinciding issues responsible for impact. In parallel, we're assessing the effectiveness of applying a targeted networking configuration change to redirect DCS traffic to alternate available load balancing infrastructure as a potential mitigation action.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to leverage Data Classification and Sensitivity labeling services such as those identified in the More info section above.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 13:44:25 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services include, but are not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview
- Purview DLP Agent
Current status: We've identified that load-balancing infrastructure is routing requests to a small amount of processing infrastructure, and not to other healthy components within the environment. We're reviewing health monitoring mechanisms used by the load balancing infrastructure, networking routing configurations and recent changes to isolate the source of the issue.
Scope of impact: Impact is specific to some users located in North America and Europe.
Next update by: Wednesday, November 19, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 12:40:29 2025 |
|---|
| Description: | Title: Multiple issues within Microsoft 365 related to data classification and sensitivity service
User impact: Multiple issues within Microsoft 365 related to Data Classification and Sensitivity labelling services.
More info: Impacted services include, but are not limited to:
- Exchange Data Loss Prevention (DLP) and Autolabeling
- Endpoint DLP
- OneDrive for Business and SharePoint Online DLP and Autolabeling
- Copilot grounding
- Microsoft Defender for Cloud Apps
- Inline DLP
- Microsoft Purview
- Purview DLP Agent
Current status: We’ve determined that the Data Classification Service (DCS), which multiple services leverage for actions such as Sensitivity labelling, Data Loss Prevention (DLP) policy applications and Copilot grounding, is not routing requests to active components correctly, resulting in impact. We’re currently investigating why this is occurring and developing a mitigation strategy.
Scope of impact: Impact is specific to some users located in North America and Europe.
Next update by: Wednesday, November 19, 2025, at 7:30 PM UTC
|
|---|
|
CP1188020 - Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Nov 19 02:15:00 2025 |
|---|
| End Time: | Wed Nov 19 20:23:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Nov 27 02:48:21 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 26 19:37:09 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 26 19:35:51 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Nov 21 19:19:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 19 21:22:15 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to perform any action on files within Copilot.
Final status: We’ve confirmed recovery efforts were successful, and service health has been fully restored.
Scope of impact: Impact was specific to some users who were served by sections of infrastructure located in North America and Europe and were attempting to perform any action on files within Copilot.
Start time: Wednesday, November 19, 2025, at 7:15 AM UTC
End time: Thursday, November 20, 2025, at 1:23 AM UTC
Preliminary root cause: A network access policy implementation issue was disallowing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next steps:
- We're reviewing our policy implementation procedures to prevent similar issues from occurring in the future.
A preliminary post incident report will be published within 2 business days of this post's closure, followed by a finalized post incident report published within 5 business days of closure.
|
|---|
|
| Time: | Wed Nov 19 21:08:59 2025 |
|---|
| Description: | We've confirmed that the service has recovered. We're continuing to monitor for a period before declaring the issue is fully resolved.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Nov 19 20:13:57 2025 |
|---|
| Description: | Our telemetry indicates 50% recovery. We’re continuing to monitor the service to ensure our mitigative actions fully saturate throughout the affected environments.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Nov 19 19:21:51 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We're continuing to observe gradual service health recovery as we restart the dependent VMs to facilitate the acceptance of the healthy network access policy.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to perform any action on files within Copilot.
Start time: Wednesday, November 19, 2025, at 2:00 AM UTC
Preliminary root cause: A network access policy implementation issue is disallowing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next update by: Thursday, November 20, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 18:42:12 2025 |
|---|
| Description: | Our work to restore the network access policy to a previously known healthy state is ongoing. We're manually restarting the dependent VMs to ensure they accept the policy and successfully reconnect to the service. As this work progresses, we're continuing to observe gradual service health recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Thursday, November 20, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 17:26:32 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We've determined a network access policy implementation issue is disallowing the service from accessing the dependent VMs. We're restoring this policy to a previously known healthy state and are observing gradual service recovery across the affected environments.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to perform any action on files within Copilot.
Preliminary root cause: A network access policy implementation issue is disallowing the Data Classification Service (DCS) from accessing the dependent virtual machines (VMs).
Next update by: Thursday, November 20, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 16:54:18 2025 |
|---|
| Description: | Since the impact is continuing after our targeted networking configuration change, we've determined the impact isn't originating from the load balancing processes. Further investigation has revealed a potential access policy configuration issue on the networking level which coincides with the impact. We're working to identify the necessary corrective actions.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 15:51:40 2025 |
|---|
| Description: | Our initial tests indicate the aforementioned targeted networking configuration change is successfully mitigating the impact across a sample of affected infrastructure and is therefore a potentially viable mitigation action. We're conducting further tests on additional sections of infrastructure to validate these efforts.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 15:13:46 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We're comprehensively reviewing policy changes and networking configurations supporting the dependent load balancing infrastructure to isolate any coinciding issues responsible for impact. In parallel, we're assessing the effectiveness of applying a targeted networking configuration change to redirect DCS traffic to alternate available load balancing infrastructure as a potential mitigation action.
Scope of impact: Impact is specific to some users who are served by sections of infrastructure located in North America and Europe and are attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 13:44:01 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We've identified that load-balancing infrastructure is routing requests to a small amount of processing infrastructure, and not to other healthy components within the environment. We're reviewing health monitoring mechanisms used by the load balancing infrastructure, networking routing configurations and recent changes to isolate the source of the issue.
Scope of impact: Impact is specific to some users located in North America and Europe, attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 12:12:08 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We’ve confirmed that increasing the timeout thresholds did not provide relief. We’ve determined that the Data Classification Service (DCS), which Copilot services leverage to determine if a user has the relevant permissions for a file, is not routing requests to active components correctly, resulting in impact. We’re currently investigating the underlying platform infrastructure to identify why this is occurring and developing a mitigation strategy.
Scope of impact: Impact is specific to some users located in North America and Europe, attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 10:53:19 2025 |
|---|
| Description: | We've confirmed that the internal service-to-service requests are timing out. We're implementing a configuration change to increase the thresholds before a request times out, to validate if this provides relief.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, November 19, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 10:18:13 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We’ve identified errors within a specific internal service-to-service request, which gathers users details to determine if they have access to the file. Due to the failure, the service defaults to the status that the user does not have permissions to the file, causing the request to fail. We’re focusing on this service-to-service request and reviewing if there were recent changes made within this area of the service.
Scope of impact: Impact is specific to some users located in North America and Europe, attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 09:12:52 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: From telemetry, we've confirmed that the client-side services are submitting the file related queries to the backend infrastructure as expected. We've identified errors within the responses returned from the backend processing infrastructure and are investigating these further.
Scope of impact: Impact is specific to some users located in North America and Europe, attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 08:35:29 2025 |
|---|
| Description: | We've reproduced the issue internally and are gathering additional diagnostic logs for error analysis.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, November 19, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 08:18:43 2025 |
|---|
| Description: | We're continuing to review service telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, November 19, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 08:01:23 2025 |
|---|
| Description: | Title: Users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to perform any action on files within Copilot.
Current status: We're reviewing support provided information, alongside service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users located in North America and Europe, attempting to perform any action on files within Copilot.
Next update by: Wednesday, November 19, 2025, at 3:30 PM UTC
|
|---|
|
IT1190248 - Users are unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Nov 26 19:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 26 21:03:35 2025 |
|---|
| Root Cause: | An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM. |
|---|
| Next Update: | Monday, December 1, 2025, at 9:00 PM UTC |
|---|
|
Details
| Time: | Wed Nov 26 21:03:35 2025 |
|---|
| Description: | Title: Users are unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users are unable to utilize the EPM readiness dashboard.
Current status: We encountered an unexpected issue with the EPM readiness dashboard in Intune that is allowing policy creation for users who are not licensed for EPM. We've identified a fix for the issue and are temporarily disabling the EPM readiness dashboard while we implement the fix. We anticipate that the EPM readiness dashboard will be fixed and available by the next scheduled update time.
Scope of impact: This issue will impact any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM.
Next update by: Monday, December 1, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Nov 26 20:51:29 2025 |
|---|
| Description: | Title: Users are unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users are unable to utilize the EPM readiness dashboard.
Current status: We're investigating a potential issue with the Intune service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1188132 - Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Nov 17 12:11:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 26 13:38:23 2025 |
|---|
| Root Cause: | An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact. |
|---|
| Next Update: | Monday, December 1, 2025, at 8:00 PM UTC |
|---|
|
Details
| Time: | Wed Nov 26 13:38:23 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our fix has reached 93 percent saturation in the affected environments and we are monitoring service availability as our fix saturates to confirm service is restored for affected users.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Start time: Monday, November 17, 2025, at 5:11 PM UTC
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Nov 25 18:29:38 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our fix has not progressed past approximately 92 percent of its deployment. Though the pace of this rollout is slower than anticipated, we're actively monitoring its saturation to the service to ensure it completes successfully. A small subset may continue to experience intermittent impact during these final stages of deployment.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Start time: Monday, November 17, 2025, at 5:11 PM UTC
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Wednesday, November 26, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Nov 25 15:39:16 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our fix has completed approximately 92 percent of its deployment, with a majority of users no longer impacted. As the remaining impacted users decrease, a small subset may continue to experience intermittent impact while our fix completes saturation. Our estimated timeline projects that the impact for all users will be remediated by our next scheduled communication update.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Start time: Monday, November 17, 2025, at 5:11 PM UTC
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Wednesday, November 26, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Nov 24 15:58:11 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We've deployed a fix that has relieved issue for the majority of impacted users and we’re continuing to monitor the rollout of this fix while also investigating the subset of users still experiencing impact. We'll provide a timeline for full mitigation of this impact by our next scheduled update.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Tuesday, November 25, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 19:38:56 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: From our analysis into the service health telemetry errors and reports of impact from a subset of users, we suspect there may be a code issue within the affected service infrastructure that’s contributing to the persistent impact. We’re investigating further into this potential code issue to pinpoint what’s causing the behavior and to identify a solution that addresses the remaining impact.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Monday, November 24, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 15:34:41 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: While many users gave feedback that the impact has been resolved for them, some may experience persisting impact. Our analysis into the remaining impact is ongoing, and we're analyzing service health telemetry errors in conjunction with reports of impact from a subset of users to identify why our solution hasn't fully resolved this issue for them.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Saturday, November 22, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Nov 21 10:54:32 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: While some users have reported recovery after we applied the changes to correct the indexing issue, we've received reports from some users that impact persists. We're continuing to review to identify if it's relating to the indexing issue or whether other factors may be contributing to the impact.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Friday, November 21, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 07:57:29 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We've received confirmation from some users stating that they experience remediation. We're continuing to await further verification from more impacted users to confirm that the issue is fixed.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Start time: Friday, November 20, 2025, at 1:25 PM UTC
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Friday, November 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 05:19:39 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We've identified that an indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact. We've corrected the indexing issue within the affected infrastructure and are awaiting verification from some impacted users to confirm if the issue is mitigated.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Root cause: An indexing issue within a section of mailbox database infrastructure responsible for providing access to Exchange Online mailboxes caused mailbox state invalidations and client disconnections, resulting in impact.
Next update by: Friday, November 21, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Nov 20 20:24:14 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our analysis so far has identified some connectivity issues and backlogs of requests. While our investigation to identify the precise origin of these issues is ongoing, we've applied some changes to the service which appear to have had a positive effect on service health. We're continuing to investigate to identify the underlying root cause of impact and construct a long-term fix solution.
Scope of impact: This issue appears to be intermittently impacting a small subset of users, though potentially any user accessing Exchange Online may be intermittently affected.
Next update by: Friday, November 21, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Nov 20 18:23:27 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our investigation into the CPU utilization on the affected databases is delayed due to an unrelated issue accessing logs specific to the errors. We're working to resolve the access issue and continue the root cause investigation.
Scope of impact: This issue appears to be intermittently impacting a small subset of users in customer tenants, though potentially any user access Exchange Online may be intermittently affected.
Next update by: Friday, November 21, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Nov 20 16:23:00 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: Our analysis of provided logs and telemetry indicates that some databases that facilitate Exchange Online mailbox access are experiencing excessive CPU utilization causing some requests to fail, resulting in impact. We're expanding our investigation to identify the specific processes responsible for impact and determine a mitigation strategy.
Scope of impact: This issue appears to be intermittently impacting a small subset of users in customer tenants, though potentially any user access Exchange Online may be intermittently affected.
Next update by: Thursday, November 20, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Nov 20 15:37:04 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We're continuing our analysis of provided logs to assist in the investigation and isolate the underlying cause of impact.
Scope of impact: Your organization is impacted by this event, and a subset of users are unable to access their mailbox through all Exchange Online connection methods.
Next update by: Thursday, November 20, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 02:02:26 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We reviewed the error codes and suspect that the issue is related to specific API calls failing. We're reviewing the affected API calls and whether there have been any recent changes to better understand the source of the errors, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and a subset of users are unable to access their mailbox through all Exchange Online connection methods.
Next update by: Thursday, November 20, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 21:28:48 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We’ve identified that 500-error codes are being returned in the HAR traces provided by your representatives. We're further investigating the source of the error codes to help with isolating the root cause.
Scope of impact: Your organization is impacted by this event, and a subset of users are unable to access their mailbox through all Exchange Online connection methods.
Next update by: Thursday, November 20, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Wed Nov 19 14:44:44 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using any connection method
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using any connection method.
Current status: We’ve received reports from your organization that a subset of users are unable to access their mailbox through any Exchange Online connection method. We're reviewing HTTP Archive format (HAR) traces and error logs to isolate the cause of this problem and determine an appropriate remediation action.
Scope of impact: Your organization is impacted by this event, and a subset of users are unable to access their mailbox through all Exchange Online connection methods.
Next update by: Thursday, November 20, 2025, at 3:00 AM UTC
|
|---|
|
MV1097445 - Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 17 22:47:38 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 25 21:32:31 2025 |
|---|
| Root Cause: | A conflict between two SharePoint web parts which render on the same page is resulting in impact. |
|---|
| Next Update: | Wednesday, December 10, 2025, at 3:00 AM UTC |
|---|
|
Details
| Time: | Tue Nov 25 21:32:31 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to complete the fix for this issue and prepare it for deployment. We're still aiming to have the issue fully remediated by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, December 10, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 20:57:44 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Work on the fix is continuing though progress is slow due to the complexity of the issue. We anticipate that deployment of the fix will start in December 2025 and complete by the end of the calendar year. We'll provide updates on the timeline and ETA as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 26, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Oct 28 21:01:53 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is ongoing, and due to the complexity of the issue, we're still anticipating deployment will start in December 2025. We'll provided an updated timeline and ETA once one becomes available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Oct 14 20:20:21 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop the fix and still anticipate the fix, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 30 20:40:02 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is taking longer than previously anticipated. We now anticipate that the fix will be completed, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 15, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 16 21:27:28 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is nearly completed. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 2 20:38:12 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to progress in our development of the fix. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 17, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 12 21:05:16 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare the fix, which we still anticipate will be ready for deployment by early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 3, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 29 20:26:29 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The preparation of the fix deployment is ongoing. We're still projecting that the full release of the fix will complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, August 13, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 15 20:24:52 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare our fix for deployment. We're currently projecting its full release may complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, July 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 1 20:30:42 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop a code fix for the conflicting SharePoint web parts. We anticipate that the fix and subsequent deployment will take an extended time to complete. We'll provide updates on the status as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 16, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 17 22:53:13 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've identified an issue where users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page, and we've determined this issue stems from a conflict between two SharePoint web parts which render on the same page. Due to the complexity of their interaction, a code-level resolution is required to ensure that impact is fully alleviated. We're working to develop this solution and will provide updates as its development progresses.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 2:00 AM UTC
|
|---|
|
EX1189908 - Some users may be unable to search or see free/busy status of others in, or connect to classic Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Fri Nov 21 12:40:00 2025 |
|---|
| End Time: | Tue Nov 25 15:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Nov 25 17:28:27 2025 |
|---|
| Root Cause: | Multiple Exchange Online endpoint URLs were missing, which resulted in impact and the newly enabled code path which added the missing endpoint URLs was mistakenly not applied to a subset of service infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 25 17:28:27 2025 |
|---|
| Description: | Title: Some users may be unable to search or see free/busy status of others in, or connect to classic Outlook desktop client
User impact: Users may have been unable to search or see free/busy status of others in, or connect to classic Outlook desktop client.
More info: Impacted scenarios included the following:
- Search
- Seeing free/busy status of others
- Connecting to Exchange Online mailboxes
- Setting Out of Office (OOF) status
Final status: We've isolated that multiple Exchange Online endpoint URLs were missing, which resulted in impact and the newly enabled code path which added the missing endpoint URLs wasn't applied to a subset of service infrastructure. We've enabled the new code path for affected infrastructure and validated after monitoring service health telemetry that impact is resolved.
Scope of impact: Impact was specific to some users attempting to search or see free/busy status of others in, or connect to classic Outlook desktop client.
Start time: Friday, November 21, 2025, at 5:40 PM UTC
End time: Tuesday, November 25, 2025, at 8:30 PM UTC
Root cause: Multiple Exchange Online endpoint URLs were missing, which resulted in impact and the newly enabled code path which added the missing endpoint URLs was mistakenly not applied to a subset of service infrastructure.
Next steps:
- We're discussing internally why affected service infrastructure wasn't included in our new code path. This discussion and analysis will allow us to determine what changes we can implement to our deployment procedures to ensure similar impact doesn't occur in future.
This is the final update for the event.
|
|---|
|
MV1179108 - Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jun 30 20:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 25 14:55:25 2025 |
|---|
| Root Cause: | A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact. |
|---|
| Next Update: | Monday, December 1, 2025, at 10:00 PM UTC |
|---|
|
Details
| Time: | Tue Nov 25 14:55:25 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We're continuing to monitor as the events are getting processed and will provide a remediation timeline once available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Monday, December 1, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 20:54:25 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We're continuing to repopulate the remaining subset of affected data; however, due to a setback on the repopulating process, more time is needed to complete the process.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 25, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 19:28:22 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We’ve identified that the majority of missing data has been populated and is available, but the repopulation is ongoing for a subset of the affected data. We now anticipate that the remaining missing data will be available by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 25, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 19:30:05 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We’ve determined that our previous estimates were inaccurate, and after reassessing, we now anticipate that the missing data will be available by the end of Thursday, November 19, 2025.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, November 20, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 03:35:16 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: The completion of the fix is taking longer than anticipated due to unforeseen circumstances. The process is actively ongoing and, provided there are no further blockers, we expect it to be completed by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, November 13, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Nov 3 20:35:43 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: The completion of the aforementioned fix is taking longer than previously anticipated. We’ll provide a timeline for completion as one becomes available to us.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Monday, November 10, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Oct 31 06:50:13 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We anticipate that the completion of the fix should be fully deployed by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 4, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 23:28:22 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We've developed a fix to restore the missing data and are preparing to initiate its deployment. We'll provide a completion timeline when one becomes available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Friday, October 31, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 14:35:52 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We’re continuing our evaluation of possible pathways to restore the missing data and achieve full resolution. Once confirmed, we’ll provide a resolution timeline.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Oct 27 17:25:08 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We've deployed a fix designed to adjust the code for event-based logic and confirmed that this allows the Copilot data to be accessed and passed to the Microsoft Viva Insights portal. This ensures that all new data is available, and we're evaluating possible options to restore the missing data.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Wednesday, October 29, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 15:35:59 2025 |
|---|
| Description: | Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This metric does not feed into Copilot Assisted Hours or Copilot Assisted Value.
Current status: We've identified that a change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, which is resulting in impact. We're in the process of validating and releasing a fix and will provide a mitigation timeline when available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Friday, October 31, 2025, at 8:00 PM UTC
|
|---|
|
EX1183224 - Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Nov 5 15:53:41 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 25 12:47:39 2025 |
|---|
| Root Cause: | A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins. |
|---|
| Next Update: | Monday, December 1, 2025, at 6:00 PM UTC |
|---|
|
Details
| Time: | Tue Nov 25 12:47:39 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we continue to review the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to isolate the source of the cache issue, we've rolled back the offending Admin API change to mitigate impact. We're reaching out to a subset of affected users to validate if this action successfully resolved impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Monday, December 1, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 10:16:37 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing to review the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to help us isolate the source of the mailbox cache issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Tuesday, November 25, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 17:27:13 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're reviewing the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to help us isolate the source of the mailbox cache issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Monday, November 24, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 15:19:06 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we continue to review the code flows, we're requesting Graph Explorer data and PowerShell outputs for Organization apps and add-ins from a subset of reporting users to aid in our investigation.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Friday, November 21, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 13:27:42 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our efforts to pinpoint exactly which flow is causing the values to be missing or mismatched, so that we can determine a strategy to remediate the impact on a broad scale.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Friday, November 21, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Nov 20 12:04:26 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re continuing to analyze the recent offending change to the Admin API, to pinpoint the code in the recent change that's resulting in the cache problem, as this data will aid us in determining our next steps to resolve impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Friday, November 21, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 13:33:22 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've validated that the recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache and is resulting in this issue. We're pinpointing the code in recent change that's resulting in the cache problem as this data will aid us in determining our next steps to resolve impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Root cause: A recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache, and is resulting in the missing Outlook add-ins.
Next update by: Thursday, November 20, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 06:31:12 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re suspecting that a recent change in Admin API may be causing a cache corruption in user mailboxes, leading to missing add-ins across multiple clients. We're reverting the change to validate our theory and are conducting in depth analysis to identify the origin of cache corruption.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 19, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 05:07:15 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re currently validating the commands that your organization's admins can use to reset the impacted add-ins. We anticipate being able to share these commands by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 19, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Nov 17 14:20:26 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Further review of the HAR trace logs confirmed that both add-ins are syncing within Exchange Online as expected. While we continue to review the HAR trace logs to progress our root cause investigation, we're preparing a set of commands that can be run by your organization's admins to reset both of the impacted add-ins, which has proven successful in remediating similar instances of impact in the past. We'll aim to provide a timeline for the commands to be prepared and validated by our next scheduled communications update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, November 18, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Nov 14 13:56:53 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We believe that the My Templates and Viva Insights Outlook add-ins may not have been properly synced in Exchange Online, resulting in impact. We're reviewing the sync process for these add-ins to substantiate this theory and identify a fix that remediates impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, November 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Nov 13 13:05:17 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Our comparative analysis of HAR trace logs from affected and unaffected users is ongoing and is an essential action to determine our next troubleshooting steps.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 14, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 17:58:11 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're conducting a deeper comparative analysis of HAR trace logs from affected and unaffected users to aid our root cause investigation. We're continuing to review possible temporary mitigation strategies to help restore functionality while we develop a permanent solution.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 13, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 16:27:47 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our comparative analysis of HAR trace logs from affected and unaffected users to aid our investigation into this issue's root cause. We're also reviewing possible temporary mitigation strategies to help restore functionality while we develop a permanent solution.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:30:27 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're reviewing HAR trace logs from affected and unaffected users for comparative analysis to identify this issue's root cause. We've confirmed that the set of commands we provided and attempted with a subset of impacted users was unsuccessful in alleviating impact, and we’re working to develop other possible remediation strategies while we continue this root cause investigation.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Nov 11 13:28:25 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While our review of the request IDs and HAR trace from a subset of affected users is underway, we're requesting a HAR trace from an unaffected user for comparative analysis in an effort to identify the source of the impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 10 16:46:46 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We've collected request IDs and a HTTP Archive format (HAR) trace from a subset of impacted users and we're analyzing the provided logging to isolate potential failures to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, November 11, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 16:31:43 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We've received feedback that the manifest file download and subsequent command execution didn't allow the deploy add-ins action as we had anticipated. We've requested that the subset of users who tested this action collect logs from another attempt so that we can analyze them and pinpoint the origin of this issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, November 10, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Nov 6 14:44:18 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: After restarting an affected user's mailbox, we've confirmed impact persists. We've provided the testing subset of users a manifest file to be downloaded and a command to be run afterwards, with the intent that these two will allow the deployment of add-ins as needed as our investigation into the root cause of the issue continues.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 7, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Nov 6 12:23:33 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We received confirmation that the series of commands didn't alleviate impact as expected. We're restarting an affected user's mailbox to see if this has any effect in remediating the impact while we continue to progress our investigation into the potential synchronization issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Nov 6 09:54:23 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: Our investigation into a potential synchronization issue is still in progress. In parallel, we're collaborating with the aforementioned users to execute a series of commands that we expect will resolve the problem.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses
Next update by: Thursday, November 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Nov 6 01:18:30 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: As we continue our investigation into whether a synchronization issue may be responsible for the impact, we’re reaching out to a subset of impacted users with a set of commands which we anticipate may resolve the issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 20:46:02 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: Our investigation into whether a synchronization issue may be responsible for the impact is ongoing. Better understanding of how the add-ins have been synced to the mailboxes will help streamline our next investigative actions and determine the best path toward remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Nov 5 19:28:15 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We don't expect that the issue is the result the add-in deployment process and we're moving forward with investigating whether a sync issue may be responsible for the impact and to determine our next steps towards expedient remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Nov 5 17:22:03 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're observed a discrepancy in the number of add-ins present in the mailboxes experiencing this impact and the ones functioning as expected. We're investigating the deployment of these add-ins, through further analysis of the provided screenshots and screen recordings of impact, to uncover further details about root cause and determine next steps toward remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Nov 5 16:20:36 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're investigating documentation of this impact including screenshots, logs, and error message details from a subset of impacted users to determine the next steps in our remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 5, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 5 15:57:05 2025 |
|---|
| Description: | Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 30 minutes.
|
|---|
|
EX1183677 - Users may be unable to delete a user from the contact list within Outlook on the web
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Nov 7 03:27:45 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 25 05:57:25 2025 |
|---|
| Root Cause: | The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web. |
|---|
| Next Update: | Monday, December 8, 2025, at 11:00 AM UTC |
|---|
|
Details
| Time: | Tue Nov 25 05:57:25 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve identified that the Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web. We've developed a fix to address the issue, which we're testing and validating in our internal environment prior to deploying it to the affected infrastructure. We expect to provide deployment time line by our next scheduled update.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Root cause: The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web.
Next update by: Monday, December 8, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Nov 11 06:03:05 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve identified that the issue relates to how certain email address formats are being processed. To help us better understand and resolve this, we’ve made changes to improve our diagnostic data and are waiting for these updates to fully apply across the service. This will allow us to obtain more detailed information to isolate the cause of impact and determine the next steps toward a fix.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Tuesday, November 25, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 06:22:52 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to review the aforementioned logs to help with the root cause investigation and to determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Tuesday, November 11, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 00:01:59 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We've received the fresh HAR network trace logs and are analyzing them to help with the root cause investigation and to determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Sun Nov 9 22:57:22 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to wait for the fresh HTTP Archive format (HAR) network trace logs to help with the root cause investigation.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Nov 7 20:55:59 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to reach out to a subset of impacted users to gather further HTTP Archive format (HAR) network trace logs and contextual details to assist us in gaining further insight into the impacted scenario and determining our next investigative steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Nov 7 15:53:42 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve requested HTTP Archive format (HAR) traces from affected users and reproduction logs to aid our ongoing investigation into the cause of this issue and to help isolate potential remediation actions.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Saturday, November 8, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Nov 7 05:30:22 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’re acquiring HAR (HTTP Archive) logs from your representatives for us to identify the source of the issue and formulate a mitigation plan.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Friday, November 7, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 03:42:31 2025 |
|---|
| Description: | Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’re reviewing associated support case details to understand more about the issue, and determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Friday, November 7, 2025, at 10:30 AM UTC
|
|---|
|
EX1184307 - Some users who are scheduling meetings may not receive accurate declined email messages in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Nov 10 01:15:12 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 25 01:47:42 2025 |
|---|
| Root Cause: | A recent deployment implemented a design change that's preventing the Organizers' details from reflecting properly when a meeting invitation is declined by a resource room. |
|---|
| Next Update: | Tuesday, December 2, 2025, at 8:00 AM UTC |
|---|
|
Details
| Time: | Tue Nov 25 01:47:42 2025 |
|---|
| Description: | Title: Some users who are scheduling meetings may not receive accurate declined email messages in Exchange Online
User impact: Users who are scheduling meetings may not receive accurate declined email messages in Exchange Online.
More info: Specifically, when users send a meeting invitation that is declined by a resource room, the email response may be missing the Organizer's details.
While we're focused on remediation, impacted users may be able to avoid impact by utilizing the Auto Room Booking feature, which would show up automatically if they have an active Copilot license when scheduling meetings through the new Outlook desktop client, Outlook on the web, or Microsoft Teams. After adding attendees and selecting a time for the meeting, organizers with this feature available see a "Add room with Copilot" button which will enable Auto Room Booking. Once this is enabled, users will see "Copilot Managed" and "Copilot will rebook if the room declines or the meeting is rescheduled". Additionally, when viewing the "Places finder", it should also show this feature as enabled, and when users click "Add a room or location", then "Browse all rooms", users will see "Rebook declined rooms" toggled on.
In order to enable this feature, users must have an active Copilot license and be scheduling meetings using the Outlook (new), Outlook on the web or Microsoft Teams.
Current status: Our fix deployment throughout our internal testing environment is 95% complete, and we’re continually seeing that the fix is remediating impact. Subsequently, we’ve deployed the fix throughout the affected service environment, and we’re monitoring as it saturates the affected infrastructure. Additionally, we anticipate that a remediation timeline will be provided by our next scheduled update.
Scope of impact: Some users who are scheduling meetings that are being declined by a resource room may be impacted.
Start time: Monday, October 27, 2025, at 12:00 AM UTC
Root cause: A recent deployment implemented a design change that's preventing the Organizers' details from reflecting properly when a meeting invitation is declined by a resource room.
Next update by: Tuesday, December 2, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Nov 18 01:45:29 2025 |
|---|
| Description: | Title: Some users who are scheduling meetings may not receive accurate declined email messages in Exchange Online
User impact: Users who are scheduling meetings may not receive accurate declined email messages in Exchange Online.
More info: Specifically, when users send a meeting invitation that is declined by a resource room, the email response may be missing the Organizer's details.
While we're focused on remediation, impacted users may be able to avoid impact by utilizing the Auto Room Booking feature, which would show up automatically if they have an active Copilot license when scheduling meetings through the new Outlook desktop client, Outlook on the web, or Microsoft Teams. After adding attendees and selecting a time for the meeting, organizers with this feature available see a "Add room with Copilot" button which will enable Auto Room Booking. Once this is enabled, users will see "Copilot Managed" and "Copilot will rebook if the room declines or the meeting is rescheduled". Additionally, when viewing the "Places finder", it should also show this feature as enabled, and when users click "Add a room or location", then "Browse all rooms", users will see "Rebook declined rooms" toggled on.
In order to enable this feature, users must have an active Copilot license and be scheduling meetings using the Outlook (new), Outlook on the web or Microsoft Teams.
Current status: We've determined our fix deployment throughout our internal testing environment is roughly halfway complete, and our preliminary validations indicate the fix is successful in remediating impact. We're aiming to begin deployment of the fix throughout the primary impacted environment by our next scheduled communications update.
Scope of impact: Some users who are scheduling meetings that are being declined by a resource room may be impacted.
Start time: Monday, October 27, 2025, at 12:00 AM UTC
Root cause: A recent deployment implemented a design change that's preventing the Organizers' details from reflecting properly when a meeting invitation is declined by a resource room.
Next update by: Tuesday, November 25, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 01:47:01 2025 |
|---|
| Description: | Title: Some users who are scheduling meetings may not receive accurate declined email messages in Exchange Online
User impact: Users who are scheduling meetings may not receive accurate declined email messages in Exchange Online.
More info: Specifically, when users send a meeting invitation that is declined by a resource room, the email response may be missing the Organizer's details.
As a way to avoid impact, users can enable Auto Room Booking for the event. To enable this feature, once the users add attendees and select the correct time, there is an "Add room with Copilot" button which will enable Auto Room Booking. Once this is enabled, users will see "Copilot Managed" and "Copilot will rebook if the room declines or the meeting is rescheduled". Additionally, when viewing the "Places finder", it will also show this feature enabled once users click "Add a room or location", then "Browse all rooms", users will see "Rebook declined rooms" toggled on.
In order to enable this feature, users must have an active Copilot license and be scheduling meetings using the Outlook (new), Outlook on the web or Microsoft Teams.
Current status: We’ve identified a recent deployment implemented a design change that's preventing the Organizers details from reflecting properly when a meeting invitation is declined by a resource room. We're developing a fix to restore the Organizers details when meeting invitations are declined by a resource room, which will undergo validations and internal testing before deploying it to the impacted environment. We'll aim to provide a deployment timeline once available.
Scope of impact: Some users who are scheduling meetings that are being declined by a resource room may be impacted.
Start time: Monday, October 27, 2025, at 12:00 AM UTC
Root cause: A recent deployment implemented a design change that's preventing the Organizers details from reflecting properly when a meeting invitation is declined by a resource room.
Next update by: Tuesday, November 18, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 01:16:10 2025 |
|---|
| Description: | Title: Some users who are scheduling meetings aren't receiving accurate declined email messages in Exchange Online
User impact: Users who are scheduling meetings aren't receiving accurate declined email messages in Exchange Online.
More info: Specifically, when users send a meeting invitation that is declined by a resource room, the email response is missing the Organizers details.
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.
|
|---|
|
SP1187718 - Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 10 19:36:00 2025 |
|---|
| End Time: | Mon Nov 24 01:38:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 24 14:27:37 2025 |
|---|
| Root Cause: | A recent change intended to update the authentication flow mistakenly removed a necessary authentication component, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 24 14:27:37 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may have been unable to load pages with custom apps or webparts in SharePoint Online and got an error.
More info: The following error may have been encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Final status: We've completed the deployment of our fix and confirmed that impact has been fully resolved for all users.
Scope of impact: Some users may have been unable to load pages with custom apps or webparts in SharePoint Online and got an error.
Start time: Tuesday, November 11, 2025, at 12:36 AM UTC
End time: Monday, November 24, 2025, at 6:38 AM UTC
Root cause: A recent change intended to update the authentication flow mistakenly removed a necessary authentication component, resulting 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: | Fri Nov 21 14:48:24 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Current status: The deployment of the fix is nearing completion, and we’ve confirmed that some affected users are already experiencing impact resolution. We’ll continue monitoring the deployment to ensure the issue is fully resolved for all affected users by our next scheduled update.
Scope of impact: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 12:36 AM UTC
Root cause: A recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact.
Next update by: Monday, November 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 15:12:55 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Current status: We're continuing to monitor the deployment of the fix, and we'll aim to provide a timeline for it to complete by our next scheduled communications update.
Scope of impact: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error. This section may be updated as our investigation continues.
Start time: Tuesday, November 11, 2025, at 12:36 AM UTC
Root cause: A recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact.
Next update by: Friday, November 21, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 15:43:06 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Current status: We've initiated the deployment of the fix to the impacted environment and we’re monitoring its progress to determine an estimation for its completion.
Scope of impact: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error. This section may be updated as our investigation continues.
Root cause: A recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact.
Next update by: Thursday, November 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Nov 18 13:54:18 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Current status: We've completed development of and are deploying a code fix to correct the authentication issue. We'll provide a timeline for impact remediation as one becomes available.
Scope of impact: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error. This section may be updated as our investigation continues.
Root cause: A recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact.
Next update by: Wednesday, November 19, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Nov 18 13:21:15 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
Current status: We've determined that a recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact. We're developing a fix to address this issue.
Scope of impact: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error. This section may be updated as our investigation continues.
Root cause: A recent change intended to update the authentication flow has mistakenly removed a necessary authentication component, resulting in impact.
Next update by: Tuesday, November 18, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 13:02:04 2025 |
|---|
| Description: | Title: Some users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error
User impact: Users may be unable to load pages with custom apps or webparts in SharePoint Online and get an error.
More info: The following error may be encountered by users when attempting to load an affected page:
An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.SharePoint.IdentityModel.SPAuthFlightController' does not contain a definition for 'IsRemoveRedirectWithProofTokenOnSignInPageEnabled'
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.
|
|---|
|
EX1177461 - Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 1 21:00:00 2025 |
|---|
| End Time: | Mon Nov 24 12:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 24 14:24:30 2025 |
|---|
| Root Cause: | A code issue in a recent update meant to improve the function of PowerShell cmdlets was preventing admins from removing migration batches in Exchange Online.
Next steps: |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 24 14:23:53 2025 |
|---|
| Description: | Title: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online
User impact: Admins may have been unable to remove and view the latest status changes of migration batches in Exchange Online.
Final status: Our monitoring has confirmed that the fix has completed deployment, and we validated with affected admins that this issue has been remediated.
Scope of impact: Admins attempting to remove and view the latest status changes for migration batches in Exchange Online may have been impacted.
Start time: Thursday, October 2, 2025, at 1:00 AM UTC
End time: Monday, November 24, 2025, at 5:30 PM UTC
Root cause: A code issue in a recent update meant to improve the function of PowerShell cmdlets was preventing admins from removing migration batches in Exchange Online.
Next steps:
- We're continuing our analysis of the service update to better identify and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 17 13:24:23 2025 |
|---|
| Description: | Title: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online
User impact: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online.
Current status: The deployment process is taking longer than expected to complete, but progress continues. additionally, we're continuing to reach out to a subset of affected admins to test whether they're able to remove the status changes from migration batches.
Scope of impact: Admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Root cause: A code issue in a recent update meant to improve the function of PowerShell cmdlets is preventing admins from removing migration batches in Exchange Online.
Next update by: Monday, November 24, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 10 13:53:29 2025 |
|---|
| Description: | Title: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online
User impact: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online.
Current status: While the services are restored for most admins, it's taking an extended period of time for the deployment to saturate to the remaining affected admins. We're continuing to monitor the deployment as it completes, and are reaching out to a subset of affected admins to test whether they're able to remove the status changes from migration batches.
Scope of impact: Admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Root cause: A code issue in a recent update meant to improve the function of PowerShell cmdlets is preventing admins from removing migration batches in Exchange Online.
Next update by: Monday, November 17, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 17:54:03 2025 |
|---|
| Description: | Title: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online
User impact: Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online.
Current status: Our deployment of the fix is saturating the affected environment and we're continuing to monitor and reach out to a subset of admins to validate that the solution successfully resolves impact. Please note that this event specifically impacts admins' ability to remove and view the latest status changes of migration batches. Previous communications indicating that this impacted the ability to migrate mailboxes were disproven.
Scope of impact: Admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Root cause: A code issue in a recent update meant to improve the function of PowerShell cmdlets is preventing admins from removing migration batches in Exchange Online.
Next update by: Monday, November 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 14:26:22 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We're continuing to wait for the deployment to reach the remaining affected users while reaching out to a subset of users to determine whether the impact is remediated as expected.
Scope of impact: Any admin attempting to provision new Exchange Online mailboxes may be impacted.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Root cause: An authentication component misconfiguration is preventing admins from provisioning new Exchange Online mailboxes.
Next update by: Monday, November 3, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Oct 31 14:36:00 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: Our deployment is approaching completion and the majority of affected users have received the fix. While we wait for the deployment to reach the remaining affected users, we're reaching out to a subset of users to determine whether the impact is remediated as expected.
Scope of impact: Any admin attempting to provision new Exchange Online mailboxes may be impacted.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Root cause: An authentication component misconfiguration is preventing admins from provisioning new Exchange Online mailboxes.
Next update by: Monday, November 3, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 14:31:59 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We're completing internal validations on the fix ahead of deployment initialization, and we anticipate these will complete and the fix will be deployed by the end of the week. Once deployment is underway, we expect the fix will reach the affected environment by early November 2025. We'll provide an updated timeline for remediation as one becomes available.
Scope of impact: Any admin attempting to provision new Exchange Online mailboxes may be impacted.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Root cause: An authentication component misconfiguration is preventing admins from provisioning new Exchange Online mailboxes.
Next update by: Friday, October 31, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 19:37:41 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We've confirmed our code fix to update the configuration is slated for deployment and we're working to expedite this process to remediate impact.
Scope of impact: Any admin attempting to provision new Exchange Online mailboxes may be impacted.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Root cause: An authentication component misconfiguration is preventing admins from provisioning new Exchange Online mailboxes.
Next update by: Thursday, October 23, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 08:35:57 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: After reviewing the additional service logs, we identified a code snippet that is throwing an exception and causing a null object reference. We are analysing the exception message to determine the root cause of the null reference and to develop an appropriate mitigation plan.
Scope of impact: Any admin attempting to provision new Exchange Online mailboxes may be impacted.
Next update by: Wednesday, October 22, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 05:08:35 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We're continuing to work with your representatives to gather and analyze additional service logs to help further our investigation into identifying a mitigation plan and root cause analysis.
Scope of impact: Any admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Next update by: Wednesday, October 22, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Wed Oct 22 01:43:34 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We're continuing our review of the impacted batches and contextual details provided by your representatives. In parallel, we're working to gather and analyze additional service logs we're anticipating will help us confirm the underlying source of impact and determine our options for remediation.
Scope of impact: Any admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Next update by: Wednesday, October 22, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Oct 22 01:15:21 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches in Exchange Online.
Current status: We're reviewing impacted batches and contextual 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: Any admins attempting to remove and view the latest status changes for migration batches in Exchange Online may be impacted.
Next update by: Wednesday, October 22, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Oct 22 00:57:42 2025 |
|---|
| Description: | Title: Admins may be unable to remove migration batches in Exchange Online
User impact: Admins may be unable to remove migration batches 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.
|
|---|
|
SP1189527 - Some users may be unable to open SharePoint Online libraries or recycle bin from navigation library links
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 19 14:30:00 2025 |
|---|
| End Time: | Mon Nov 24 11:21:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 24 11:55:22 2025 |
|---|
| Root Cause: | The latest Service Worker build was deployed asynchronously from the latest version of the manifest, which introduced a mismatch and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 24 11:55:22 2025 |
|---|
| Description: | Title: Some users may be unable to open SharePoint Online libraries or recycle bin from navigation library links
User impact: Users may have been unable to open SharePoint Online libraries or recycle bin from navigation library links.
More info: When opening the library or recycle bin from navigation library links, a redirect occurred to an xml page instead of the library content, but a page refresh displayed the content as expected.
Final status: We determined the latest Service Worker build was deployed asynchronously from the latest version of the manifest, which introduced a mismatch and resulted in impact. We've pushed the Service Worker build to 100 percent to align with the latest manifest and confirmed with a subset of affected users that this resolved the issue.
Scope of impact: Impact was specific to some users who were attempting to open SharePoint Online libraries or recycle bin from navigation library links.
Start time: Wednesday, November 19, 2025, at 7:30 PM UTC
End time: Monday, November 24, 2025, at 4:21 PM UTC
Root cause: The latest Service Worker build was deployed asynchronously from the latest version of the manifest, which introduced a mismatch and resulted in impact.
Next steps:
- We're reviewing our update release procedures to ensure similar dependencies are identified and taken into account when being deployed to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 24 09:53:18 2025 |
|---|
| Description: | Title: Some users may be unable to open SharePoint Online libraries from navigation library links
User impact: Users may be unable to open SharePoint Online libraries from navigation library links.
More info: When opening the library link from navigation, a redirects occurs to an xml page instead of the library content but a page refresh displays the content as expected.
Current status: We're reviewing support provided information to determine our next troubleshooting steps 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 attempting to open SharePoint Online libraries from navigation library links.
Next update by: Monday, November 24, 2025, at 5:00 PM UTC
|
|---|
|
MO1186276 - Some organizers may have seen that mandatory labeling wasn’t applying when creating new meetings
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 16 01:30:00 2025 |
|---|
| End Time: | Fri Nov 21 11:25:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 24 11:13:17 2025 |
|---|
| Root Cause: | The quick compose form was lacking a check for this scenario where mandatory labeling was enabled but no default one was applied. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 24 09:28:27 2025 |
|---|
| Description: | Title: Some organizers may have seen that mandatory labeling wasn’t applying when creating new meetings
User impact: Organizers may have seen that mandatory labeling wasn’t applying when creating new meetings.
More info: Impact was specific to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact was specific to admins who had a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees saw that there was no sensitivity label applied, but they could still access and attend the meeting without complications. Users with access to the Outlook desktop client could use that method to avoid this issue.
Final status: We’ve confirmed that the issue is resolved following the deployment of the fix.
Scope of impact: Some organizers who were creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may have been impacted.
Start time: Thursday, January 16, 2025, at 6:30 AM UTC
End time: Friday, November 21, 2025, at 4:25 PM UTC
Root cause: The quick compose form was lacking a check for this scenario where mandatory labeling was enabled but no default one was applied.
Next steps:
-We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 24 06:55:35 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: The fix has been fully deployed across the affected environments. We’re in the process of confirming that the issue has been fully resolved.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Root cause: The quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied.
Next update by: Monday, November 24, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Nov 20 07:30:40 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: We’ve completed validation of the fix and we're rolling it out to the affected environments.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Root cause: The quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied.
Next update by: Monday, November 24, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 03:19:54 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: We’ve developed a fix and are in the final stages of validation before rolling it out to the affected environments. A detailed deployment timeline will be shared in our next update.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Root cause: The quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied.
Next update by: Thursday, November 20, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 04:49:26 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: We're continuing to develop and test a possible fix to mitigate impact.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Root cause: The quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied.
Next update by: Wednesday, November 19, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Nov 17 06:28:39 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: We've identified that the quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied. We're developing and testing a fix to enable a check, in order to mitigate impact.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Root cause: The quick compose form is lacking a check for this scenario where mandatory labelling is enabled but no default one is applied.
Next update by: Tuesday, November 18, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Nov 14 15:54:25 2025 |
|---|
| Description: | Title: Some organizers may see that mandatory labeling isn't applying when creating new meetings using the Quick Compose pop-up
User impact: Organizers may see that mandatory labeling isn't applying when creating new meetings using the Quick Compose pop-up.
More info: Impact is to meetings created using the Microsoft Teams calendar and Outlook on the web using the Quick Compose pop-up. Additionally, impact is specific to admins who have a policy applied where sensitivity labels are mandatory, and there's no default label configured.
Attendees will see that there's no sensitivity label applied, but they can still access and attend the meeting without complications. Users with access to the Outlook desktop client can use that method to avoid this issue.
Current status: We've received reports of an issue in which some organizers may see that mandatory labeling isn't applying to some meetings that are created using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web. We're investigating service side logs to help with isolating the root cause and determining a remediation plan.
Scope of impact: Some organizers who are creating meetings using the Quick Compose pop-up in Microsoft Teams calendar and Outlook on the web may be impacted.
Next update by: Monday, November 17, 2025, at 11:30 AM UTC
|
|---|
|
DZ1189321 - Some may users see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Nov 23 14:58:02 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 24 05:20:30 2025 |
|---|
| Root Cause: | A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025. |
|---|
| Next Update: | Monday, 8 December 2025, at 10:30 AM UTC |
|---|
|
Details
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some may users see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some may users see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
PB1185904 - Users see that Power BI Desktop files (PBIX) don't refresh when stored on Microsoft OneDrive with specific settings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 29 17:47:00 2025 |
|---|
| End Time: | Sun Nov 23 18:49:00 2025 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Nov 23 20:00:01 2025 |
|---|
| Root Cause: | A recent code change contained a misconfiguration that caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Nov 23 20:00:01 2025 |
|---|
| Description: | Title: Users see that Power BI Desktop files (PBIX) don't refresh when stored on Microsoft OneDrive with specific settings
User impact: Users saw that PBIX didn't refresh when stored on OneDrive with specific settings.
More info: The error only occurred when a specific setting "OneDrive refresh" was turned on.
While the OneDrive UI notes the refreshes didn't succeed, we've confirmed through testing with affected users that the refreshes were completing as expected, and the issue solely lied with the OneDrive UI returning false errors.
In addition, users trying to refresh Excel and .csv files with OneDrive would have also seen the failure message.
Final status: We've validated and deployed the code fix to address the impact, and after monitoring the deployment, we've confirmed that impact has been successfully remediated.
Scope of impact: Your organization was affected by this event, and the issue impacted any user with the OneDrive refresh setting turned on.
Start time: Wednesday, October 29, 2025, at 9:47 PM UTC
End time: Sunday, November 23, 2025, at 11:49 PM UTC
Root cause: A recent code change contained a misconfiguration that caused impact.
Next steps:
- We're reviewing our code change testing and validation methods to better identify the potential for impact to the service prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 14 17:04:10 2025 |
|---|
| Description: | Title: Users see that Power BI Desktop files (PBIX) don't refresh when stored on Microsoft OneDrive with specific settings
User impact: Users see that PBIX don't refresh when stored on OneDrive with specific settings.
More info: The error only occurs when a specific setting "OneDrive refresh" is turned on.
While the OneDrive UI notes the refreshes didn't succeed, we've confirmed through testing with affected users that the refreshes are completing as expected, and the issue solely lies with the OneDrive UI returning false errors.
In addition, users trying to refresh Excel and .csv files with OneDrive will also see the failure message.
Current status: We've updated the More Info section of this communication as testing with affected users has confirmed the refreshes are completing as expected. The issue solely lies with the OneDrive UI returning false error messages.
We're deploying the fix to our internal test environment prior to broad deployment to ensure the impact is remediated once deployed. We estimate the fix will be deployed to all affected users by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and the issue impacts any user with the OneDrive refresh setting turned on.
Start time: Wednesday, October 29, 2025, at 9:47 PM UTC
Estimated time to resolve: We anticipate the fix will be deployed to all affected users by Monday, November 24, 2025, at 2:00 AM UTC.
Root cause: A recent code change contains a misconfiguration that's causing impact.
Next update by: Monday, November 24, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 21:14:28 2025 |
|---|
| Description: | Title: Users see that Power BI Desktop files (PBIX) don't refresh when stored on Microsoft OneDrive with specific settings
User impact: Users see that PBIX don't refresh when stored on Microsoft OneDrive with specific settings.
More info: The error only occurs when a specific setting "OneDrive refresh" is turned on.
In addition, users trying to refresh Excel and .csv files with OneDrive will also see failures.
While we're focused on remediation, users may be able to circumvent the issue by manually refreshing.
Current status: We're continuing our development and validation of the code fix to address the misconfiguration. Once validated, we'll prepare the fix deployment to the affected environment.
Scope of impact: Your organization is affected by this event, and the issue impacts any user with the OneDrive refresh setting turned on.
Start time: Wednesday, October 29, 2025, at 9:47 PM UTC
Root cause: A recent code change contains a misconfiguration that's causing impact.
Next update by: Friday, November 14, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Nov 13 18:41:34 2025 |
|---|
| Description: | Title: Users can't publish or refresh Power BI Desktop (PBIX) files from Microsoft OneDrive
User impact: Users can't publish or refresh PBIX files from Microsoft OneDrive.
More info: As a way to circumvent this issue, users can manually refresh or publish the files from Power BI Desktop.
Current status: We've identified a recent code change that contains a misconfiguration that's causing impact. We're developing a code fix to correct the configuration and remediate the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to publish or refresh PBIX files from OneDrive is impacted.
Start time: Wednesday, October 29, 2025, at 9:47 PM UTC
Root cause: A recent code change contains a misconfiguration that's causing impact.
Next update by: Friday, November 14, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 18:37:20 2025 |
|---|
| Description: | Title: Users can't publish or refresh Power BI Desktop (PBIX) files from Microsoft OneDrive
User impact: Users can't publish or refresh PBIX files from Microsoft OneDrive.
More info: As a workaround, users can manually refresh or publish the files from Power BI Desktop.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
FL1181388 - Users are experiencing failures across multiple Power Automate scenarios
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Oct 29 11:45:00 2025 |
|---|
| End Time: | Wed Oct 29 19:38:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Nov 23 14:50:00 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Nov 23 14:50:00 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Nov 4 11:50:29 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 19:44:10 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users were experiencing failures across multiple Power Automate scenarios.
More Info: The following scenarios were impacted:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Running Power Automate desktop flows
-Loading Power Automate integrations
-Performing approvals
-Accessing Microsoft Copilot Studio (http://copilotstudio.preview.microsoft.com)
Final Status: We have confirmed via service health diagnostics that all affected scenarios have recovered and that impact has been remediated.
A Post Incident Report will be published within five days.
Preliminary Root Cause: An Azure Front Door service outage resulted in impact.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Wed Oct 29 19:13:04 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: The following scenarios have fully recovered:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Running Power Automate desktop flows
-Loading Power Automate integrations
-Accessing Microsoft Copilot Studio (http://copilotstudio.preview.microsoft.com)
Users may still experience intermittent failures with the following scenarios:
-Performing approvals
Current Status: We are continuing to monitor service health to confirm sustained mitigation for the impacted scenarios.
Next Update: Thursday, October 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 16:56:36 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: The following scenarios have fully recovered:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Running Power Automate desktop flows
-Loading Power Automate integrations
-Accessing Microsoft Copilot Studio (http://copilotstudio.preview.microsoft.com)
Users may still experience intermittent failures with the following scenarios:
-Performing approvals
Current Status: We have determined that the email approval scenario is still recovering. We will continue to monitor service health to confirm sustained mitigation for other impacted scenarios.
Next Update: Thursday, October 30, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 15:13:50 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: The following scenarios have fully recovered:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Running Power Automate desktop flows
-Loading Power Automate integrations
-Accessing Microsoft Copilot Studio (http://copilotstudio.preview.microsoft.com)
Users may still experience intermittent failures with the following scenarios:
-Performing approvals
Current Status: We completed the failovers to healthy redundant infrastructure and have confirmed that impacted services are now trending toward recovery. We are continuing to monitor service health to confirm sustained mitigation.
Next Update: Wednesday, October 29, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:48:55 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: Users may experience failures with the following scenarios:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Performing approvals
-Running Power Automate desktop flows
-Loading Power Automate integrations
As a workaround for the Power Automate portal, we recommend accessing the service via https://make.powerautomate.com
Current Status: We completed the failovers to healthy redundant infrastructure and have confirmed that impacted services are now trending toward recovery. We are continuing to monitor service health to confirm sustained mitigation.
Next Update: Wednesday, October 29, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:11:53 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: Users will experience failures with the following scenarios:
-Accessing the Power Automate portal (https://make.powerautomate.com)
-Performing approvals
-Running Power Automate desktop flows
-Loading Power Automate integrations
Current Status: After our investigation, we identified an outage for that the Azure Front Door service as the source of impact. To mitigate the issue, we are performing failovers to healthy redundant infrastructure.
Next Update: Wednesday, October 29, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:05:50 2025 |
|---|
| Description: | Title: Users are experiencing failures across multiple Power Automate scenarios
User impact: Users are experiencing failures across multiple Power Automate scenarios.
More Info: Users will experience failures with the following scenarios:
-Accessing the Power Automate portal (https://powerautomate.microsoft.com)
-Performing approvals
-Running Power Automate desktop flows
-Loading Power Automate integrations
Current Status: We are aware of an emerging issue where users are unable to access the Power Automate portal, running desktop flows, loading Power Automate integrations, and are experiencing failures in multiple other scenarios. 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.
|
|---|
|
IT1189146 - Users intermittently may be unable to complete Mobile Application Management (MAM) enrollment and access MAM enabled app
| Status: | serviceRestored |
|---|
| Start Time: | Sat Nov 22 13:29:19 2025 |
|---|
| End Time: | Sat Nov 22 18:20:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Nov 22 20:50:12 2025 |
|---|
| Root Cause: | A resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune had resulted in intermittent failures for MAM enrollment and check in workflows. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Nov 22 20:46:30 2025 |
|---|
| Description: | Title: Users intermittently may be unable to complete Mobile Application Management (MAM) enrollment and access MAM enabled apps
User impact: Users intermittently may have been unable to complete MAM enrollment and access MAM enabled apps.
More info: Affected users may have also experienced delays receiving app protection policies.
Final status: The change to disable the impacting process has fully saturated across the affected portion of service infrastructure and we’ve monitored our service telemetry to validate that the remaining errors have been resolved, confirming that the issue is fully remediated.
Scope of impact: Impact may have occurred for any user attempting to complete MAM enrollment or access MAM enabled apps.
Start time: Saturday, November 22, 2025, at 6:00 AM UTC
End time: Saturday, November 22, 2025, at 11:20 PM UTC
Root cause: A resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune had resulted in intermittent failures for MAM enrollment and check in workflows.
Next steps:
-We’re investigating further into the affected portion of the Mobile Application Management workflow infrastructure to better understand what caused the resource contention and load balance issue, along with how this issue caused impact to MAM enrollment and access to MAM enabled apps so that we can avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Nov 22 19:54:48 2025 |
|---|
| Description: | Title: Users may intermittently experience Mobile Application Management (MAM) enrollment issues and MAM enabled app failures
User impact: Users may intermittently experience MAM enrollment issues and MAM enabled app failures.
More info: Affected users may experience delays receiving app protection policies and may be unable to access MAM enabled apps.
Current status: We’ve disabled the aforementioned impacting process for the affected portion of service infrastructure and have observed from our service telemetry that the majority of impact is remediated. We’re monitoring as this disabled process fully saturates across the affected portion to address the remaining impact.
Scope of impact: Impact may occur for any user attempting to complete MAM enrollment or access MAM enabled apps.
Start time: Saturday, November 22, 2025, at 6:00 AM UTC
Root cause: A resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune has resulted in intermittent failures for MAM enrollment and check in workflows.
Next update by: Sunday, November 23, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Sat Nov 22 16:58:36 2025 |
|---|
| Description: | Title: Users may intermittently experience Mobile Application Management (MAM) enrollment issues and MAM enabled app failures
User impact: Users may intermittently experience MAM enrollment issues and MAM enabled app failures.
More info: Affected users may experience delays receiving app protection policies and failures accessing MAM enabled apps.
Current status: We’re continuing our efforts to disable the process that was repeatedly restarting a component of the workflow to allow it to complete successfully and remediate the issue in full. Once available we’ll provide a resolution timeline.
Scope of impact: Impact may occur for any user attempting to complete MAM enrollment or access MAM enabled apps.
Start time: Saturday, November 22, 2025, at 6:00 AM UTC
Root cause: A resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune has resulted in intermittent failures for MAM enrollment and check in workflows.
Next update by: Sunday, November 23, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Nov 22 15:20:47 2025 |
|---|
| Description: | Title: Users may intermittently experience Mobile Application Management (MAM) enrollment issues and MAM enabled app failures
User impact: Users may intermittently experience MAM enrollment issues and MAM enabled app failures.
More info: Affected users may experience delays receiving app protection policies and failures accessing MAM enabled apps.
Current status: We’ve identified that a resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune has resulted in intermittent failures for MAM enrollment and check in workflows. To remediate this issue, we’re disabling a process that was repeatedly restarting a component of the workflow, allowing it to complete successfully, and we’re monitoring the service to ensure successful resolution.
Scope of impact: Impact may occur for any user attempting to complete MAM enrollment or access MAM enabled apps.
Start time: Saturday, November 22, 2025, at 6:00 AM UTC
Root cause: A resource contention and load balance issue within a portion of the Mobile Application Management workflow infrastructure in Microsoft Intune has resulted in intermittent failures for MAM enrollment and check in workflows.
Next update by: Saturday, November 22, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Sat Nov 22 14:09:49 2025 |
|---|
| Description: | Title: Users may intermittently experience Mobile Application Management (MAM) enrollment issues and MAM enabled app failures
User impact: Users may intermittently experience MAM enrollment issues and MAM enabled app failures.
More info: Affected users may experience delays receiving app protection policies and failures accessing MAM enabled apps.
Current status: Our monitoring systems identified an issue where users may intermittently experience delays receiving app protection policies and failures accessing MAM enabled apps in Microsoft Intune. To assess this issue, we're reviewing service telemetry to isolate the source of impact and determine an appropriate remediation action.
Scope of impact: Impact may occur for any user attempting to complete MAM enrollment or access MAM enabled apps.
Next update by: Saturday, November 22, 2025, at 8:30 PM UTC
|
|---|
|
CP1187825 - Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 17 19:00:00 2025 |
|---|
| End Time: | Thu Nov 20 16:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 21 17:40:14 2025 |
|---|
| Root Cause: | A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 21 17:38:30 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may have seen Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting was disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Final status: We've confirmed that the fix has completed release and validated this issue has been remediated via internal testing and service telemetry.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
End time: Thursday, November 20, 2025, at 9:00 PM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next steps:
- We're continuing our analysis of the impacting configuration change to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 21 13:24:07 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: The deployment is complete, and users should start seeing relief for this impact, though we're working to validate that the service has returned to a healthy state to ensure full remediation.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Saturday, November 22, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Nov 20 21:39:07 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’re continuing to monitor the deployment progression for the Microsoft Teams fix as it nears completion. We anticipate this deployment process will complete and the issue will be fully resolved by our next scheduled communications update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Friday, November 21, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 15:02:23 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’ve verified that the fix to address the impact in Exchange Online has completed successfully, and users will experience impact relief in Exchange Online. Additionally, we’ve initiated the secondary phase to address the impact in Microsoft Teams, and we’re monitoring the fix progression to ensure successful completion. Once available, we’ll provide a resolution timeline.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Friday, November 21, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Nov 19 21:59:21 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’ve halted the deployment of the fix in order to perform additional validations to ensure it successfully remediates impact. Additionally, we've identified that the fix will be released in two separate deployment phases. The first phase will address the impact in Exchange Online, which we anticipate will be fully deployed and the issue resolved by our next scheduled update. When that deployment is complete, we’ll initiate our deployment of the secondary phase to address the impact in Microsoft Teams, and we'll aim to provide a resolution timeline once available.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Thursday, November 20, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Nov 19 16:07:33 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We’ve validated the fix and initiated deployment to the affected environments. As the deployment progresses, some users may begin to see impact relief. Based on current estimates, we expect the deployment to complete by our next scheduled update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Thursday, November 20, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Nov 18 22:16:36 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We're finalizing the validation of our fix in preparation for its deployment to the affected environment. We're anticipating this deployment should be underway, and may complete by the time of our next scheduled update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 17:22:19 2025 |
|---|
| Description: | Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We’ve identified that a misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online. We've developed and are internally validating a configuration fix to confirm it resolves the issue before deploying it to the affected environment. We anticipate that this fix will begin deployment to the affected environments on Wednesday, November 19, 2025.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in the some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Wednesday, November 19, 2025, at 5:00 AM UTC
|
|---|
|
MO1188691 - Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 19 01:22:00 2025 |
|---|
| End Time: | Fri Nov 21 10:27:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 21 13:57:43 2025 |
|---|
| Root Cause: | A recent Content Delivery Network (CDN) related ingestion infrastructure configuration change had resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 21 13:45:40 2025 |
|---|
| Description: | Title: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store
User impact: Users may have been unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store.
Final status: We've identified that a recent Content Delivery Network (CDN) ingestion infrastructure configuration change had resulted in impact. To remediate this, we reverted the offending configuration change and reprocessed all previously affected apps and completed the backlog of ingestion data. After monitoring the service, we verified that the issue has been successfully resolved.
Scope of impact: This issue impacted users attempting to publish Apps that had screenshot URL in the Microsoft Teams App Store and the Microsoft Copilot (Microsoft 365) Agent Store via the Partner Center.
Start time: Wednesday, November 19, 2025, at 6:22 AM UTC
End time: Friday, November 21, 2025, at 3:27 PM UTC
Root cause: A recent Content Delivery Network (CDN) related ingestion infrastructure configuration change had resulted in impact.
Next steps:
- We’re investigating how the recent Content Delivery Network (CDN) related ingestion infrastructure configuration change had resulted in impact to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 21 06:58:50 2025 |
|---|
| Description: | Title: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store
User impact: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store.
Current status: We're completed reverting the change and we're performing testing to validate that impact has been remediated before we start processing the backlog of ingestion data.
Scope of impact: This issue impacts users attempting to publish Apps that have screenshot URL in the Microsoft Teams App Store and the Microsoft Copilot (Microsoft 365) Agent Store via the Partner Center.
Start time: Wednesday, November 19, 2025, at 6:22 AM UTC
Root cause: A recent ingestion infrastructure change has inadvertently caused impact to occur.
Next update by: Friday, November 21, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 04:45:44 2025 |
|---|
| Description: | Title: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store
User impact: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store.
Current status: We've determined that a recent ingestion infrastructure change has inadvertently caused impact to occur. We're reverting the change and once complete we'll start processing the backlog of ingestion data.
Scope of impact: This issue impacts users attempting to publish Apps that have screenshot URL in the Microsoft Teams App Store and the Microsoft Copilot (Microsoft 365) Agent Store via the Partner Center.
Start time: Wednesday, November 19, 2025, at 6:22 AM UTC
Root cause: A recent ingestion infrastructure change has inadvertently caused impact to occur.
Next update by: Friday, November 21, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Nov 21 02:56:31 2025 |
|---|
| Description: | Title: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store
User impact: Users may be unable to publish Apps in the Microsoft Teams App Store and the Microsoft Copilot Agent Store.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: This issue impacts users attempting to publish Apps that have screenshots in the Microsoft Teams App Store and the Microsoft Copilot (Microsoft 365) Agent Store via the Partner Center.
Next update by: Friday, November 21, 2025, at 10:00 AM UTC
|
|---|
|
TM1185553 - Users may have seen their suggested replies in Microsoft Teams in English despite existing language settings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 5 18:30:00 2025 |
|---|
| End Time: | Thu Nov 20 22:15:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 21 05:56:44 2025 |
|---|
| Root Cause: | A regression with the language detection functionality for smart replies in Microsoft Teams impacted the language for suggested replies in Microsoft. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 21 05:56:44 2025 |
|---|
| Description: | Title: Users may have seen their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may have seen their suggested replies in Microsoft Teams in English despite existing language settings.
Final status: We've confirmed that the fix has been fully deployed and that impact has been remediated.
Scope of impact: Any user may have been affected by this event, and the issue may have impacted users viewing suggested replies in Microsoft Teams.
Start time: Wednesday, November 5, 2025, at 11:30 PM UTC
End time: Friday, November 21, 2025, at 3:15 AM UTC
Root cause: A regression with the language detection functionality for smart replies in Microsoft Teams impacted the language for suggested replies in Microsoft.
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: | Thu Nov 20 01:40:20 2025 |
|---|
| Description: | Title: Users may see their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may see their suggested replies in Microsoft Teams in English despite existing language settings.
Current status: We've successfully identified and developed a fix for the regression. We've initiated the deployment of the fix which has reached an estimated 70 percent of the impacted service environments. Some users may see impact remediation as the fix fully saturates. We'll continue to monitor the fix deployment to ensure it fully completes and remediates impact as expected.
Scope of impact: Any user may be affected by this event, and the issue may impact users viewing suggested replies in Microsoft Teams. This section may be updated as our investigation continues.
Root cause: A regression with the language detection functionality for smart replies in Microsoft Teams is impacting the language for suggested replies in Microsoft.
Next update by: Friday, November 21, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 01:34:34 2025 |
|---|
| Description: | Title: Users may see their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may see their suggested replies in Microsoft Teams in English despite existing language settings.
Current status: We identified a regression with the language detection functionality for smart replies in Microsoft Teams is impacting the language for suggested replies. We're working to understand the source of the regression and develop a fix to remediate the impact. Due to the complexity of the language detection models, the fix and implementation will take time to complete.
Scope of impact: Any user may be affected by this event, and the issue may impact users viewing suggested replies in Microsoft Teams. This section may be updated as our investigation continues.
Root cause: A regression with the language detection functionality for smart replies in Microsoft Teams is impacting the language for suggested replies in Microsoft.
Next update by: Thursday, November 20, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 01:30:44 2025 |
|---|
| Description: | Title: Users may see their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may see their suggested replies in Microsoft Teams in English despite existing language settings.
Current status: We identified a regression with the language detection functionality for smart replies in Microsoft Teams is impacting the language for suggested replies. We're working to understand the source of the regression and develop a fix to remediate the impact. Due to the complexity of the language detection models, the fix and implementation will take time to complete.
Scope of impact: Any user may be affected by this event, and the issue may impact users viewing suggested replies in Microsoft Teams. This section may be updated as our investigation continues.
Root cause: A regression with the language detection functionality for smart replies in Microsoft Teams is impacting the language for suggested replies in Microsoft.
Next update by: Thursday, November 20, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 00:07:50 2025 |
|---|
| Description: | Title: Users may see their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may see their suggested replies in Microsoft Teams in English despite existing language settings.
Current status: We're analyzing system logs to help identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: Any user may be affected by this event, and the issue may impact users viewing suggested replies in Microsoft Teams. This section may be updated as our investigation continues.
Next update by: Thursday, November 13, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 23:40:13 2025 |
|---|
| Description: | Title: Users may see their suggested replies in Microsoft Teams in English despite existing language settings
User impact: Users may see their suggested replies in Microsoft Teams in English despite existing language settings.
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.
|
|---|
|
MV1188552 - Some users may be unable to use search in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Thu Nov 20 16:47:11 2025 |
|---|
| End Time: | Thu Nov 20 17:33:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 20 17:48:35 2025 |
|---|
| Root Cause: | A section of infrastructure responsible for facilitating search requests wasn't performing as expected, which resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 20 17:48:35 2025 |
|---|
| Description: | Title: Some users may be unable to use search in Microsoft Viva Engage
User impact: Users may have been unable to use search in Microsoft Viva Engage.
Final status: We've confirmed after monitoring service health telemetry that routing the traffic to healthy infrastructure has resolved the issue.
Scope of impact: Some users in North America attempting to use search in Microsoft Viva Engage may have been affected.
Start time: Thursday, November 20, 2025, at 9:05 PM UTC
End time: Thursday, November 20, 2025, at 10:33 PM UTC
Root cause: A section of infrastructure responsible for facilitating search requests wasn't performing as expected, which resulted in the impact.
Next steps:
- We're continuing to analyze the affected infrastructure to better understand how it got into an unhealthy state so we can address any shortcomings and ensure this doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Nov 20 17:28:56 2025 |
|---|
| Description: | Title: Some users may be unable to use search in Microsoft Viva Engage
User impact: Users may be unable to use search in Microsoft Viva Engage.
Current status: Our initial investigation has determined a section of infrastructure responsible for facilitating search requests isn't performing as expected, resulting in the impact. We're routing traffic to healthy infrastructure to remediate the issue.
Scope of impact: Some users in North America attempting to use search in Microsoft Viva Engage may be affected. This section may be updated as our investigation continues.
Start time: Thursday, November 20, 2025, at 9:05 PM UTC
Root cause: A section of infrastructure responsible for facilitating search requests isn't performing as expected, resulting in the impact.
Next update by: Friday, November 21, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Nov 20 17:04:09 2025 |
|---|
| Description: | Title: Some users may be unable to use search in Microsoft Viva Engage
User impact: Users may be unable to use search 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.
|
|---|
|
EX1185322 - Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Nov 6 08:41:00 2025 |
|---|
| End Time: | Tue Nov 18 22:41:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Nov 20 15:26:00 2025 |
|---|
| Root Cause: | A recent HTTP3 configuration change for the QUIC feature in the Exchange Online client access path resulted in intermittent mail delivery failures for a limited number of native iOS Mail clients. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 20 14:50:15 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may have been unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users could have authenticated without issue, but they received the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Final status: We've confirmed with affected users that disabling the offending change has remediated impact. This confirms that a recent HTTP3 configuration change for the QUIC feature in the Exchange Online client access path resulted in impact.
Scope of impact: Impact may have occurred for some users, where they couldn't send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Start time: Thursday, November 6, 2025, at 1:41 PM UTC
End time: Wednesday, November 19, 2025, at 3:41 AM UTC
Root cause: A recent HTTP3 configuration change for the QUIC feature in the Exchange Online client access path resulted in intermittent mail delivery failures for a limited number of native iOS Mail clients.
Next steps:
- We're reviewing our QUIC feature change validation process to improve the detection and prevention of similar HTTP3 configuration issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 19 17:45:23 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We've received feedback from some users that the issue has been remediated by our actions to disable an offending change to the QUIC feature. We're reaching out to other impacted users to confirm if this solution worked for them as well in order to validate fully that this was the root cause of this issue.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Thursday, November 20, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 13:50:25 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We’ve identified a potential source of impact where a recent HTTP3 configuration change for the QUIC feature in the Exchange Online client access path may be resulting in intermittent mail delivery failures for a limited number of native iOS Mail clients. We’ve disabled this change in the affected environments and are currently requesting impacted users test while we await confirmation that this action has successfully resolved the issue, which would validate our findings.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Thursday, November 20, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Nov 18 22:33:33 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: From our analysis of the networking code path, we suspect that a recent update may be leading to closed connections in our service logs and causing the failed connection when attempting to refresh email messages in the native iOS Mail app. We're rolling back this update and we'll test with a subset of affected users to determine whether impact still persists or not.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Wednesday, November 19, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 16:14:34 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: Our analysis of the networking code path leveraged when attempting to connect to Exchange Online through EAS is ongoing and is essential to identifying potential failures to determine our next troubleshooting steps.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Wednesday, November 19, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Tue Nov 18 14:46:13 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We're analyzing new network traces provided by a subset of users along with reviewing the networking code path leveraged when attempting to connect to Exchange Online through EAS to identify potential failures to determine our next troubleshooting steps.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Tuesday, November 18, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Nov 17 19:50:08 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We’re requesting further data from a subset of impacted users to assist with our troubleshooting efforts. In parallel, we're narrowing down our investigation into the root cause as we gain a more thorough understanding of the nuances of this impact.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Tuesday, November 18, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Nov 17 17:57:29 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We’re continuing to test with affected users by requesting they update the EAS URLs on their affected devices to confirm whether the issue still occurs after the change, which will help guide our next troubleshooting steps. Additionally, we’re analyzing some fresh network trace logs captured from impacted users to isolate the underlying cause of the problem.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Tuesday, November 18, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Nov 17 16:03:30 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: The process of collecting additional networking logs and traces from affected users to further our investigation into the underlying cause of this issue is ongoing. Additionally, we're continuing to reach affected users to try updating the EAS URL on affected devices as a test to help determine whether this remediates the impact, which will help determine our next troubleshooting steps.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Monday, November 17, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Nov 17 13:58:44 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We’re continuing to work with affected users to collect some additional network trace logs to further our understanding of the impacting scenario. Additionally, we’re testing with some affected users to try updating the EAS URL on affected devices to confirm whether this resolves the issue.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Monday, November 17, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Nov 14 16:16:16 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We're continuing our analysis of service-side telemetry while working with affected users to gather additional logs of the issue in progress and develop a remediation strategy.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Monday, November 17, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Nov 13 23:26:49 2025 |
|---|
| Description: | Title: Some users can't send or receive Exchange Online email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users can't send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We reviewed the provided Fiddler trace logs from an impacted device, along with Exchange Active Sync (EAS) logs, but couldn't identify any failures present in them. We've requested additional Fiddler traces logs from a subset of affected users that includes failures to help isolate the underlying root cause of impact.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Friday, November 14, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Nov 13 18:31:35 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh email messages in the Mail app.
Current status: We've gathered the Fiddler trace from an impacted device which we're reviewing to progress our root cause investigation, so we can determine our next troubleshooting steps.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Friday, November 14, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Nov 13 13:41:02 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: We're working with affected users to collect a Fiddler trace from an impacted device to assist with our troubleshooting analysis and to determine our next steps.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Friday, November 14, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 22:37:15 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: We’ve investigated the aforementioned error found in the routing of request traffic to the service and determined it’s not the culprit behind the impact as the affected requests were delegated to a portion of EAS service infrastructure where it was properly handled. We’re working with affected users to request that a Networking trace capturing the impact be collected from your organization so that we confirm whether the service is working as expected.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Thursday, November 13, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 18:02:25 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: We're working to determine whether the error we discovered in the routing of request traffic is the underlying source of this impact in order to develop effective next steps towards expedient remediation.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Thursday, November 13, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 17:21:16 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: While investigating the provided logs, we discovered an error in the routing of request traffic to the service and are developing a strategy to mitigate this error and restore service.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Thursday, November 13, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 15:24:38 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: Our review of the EAS logs gathered with affected users is ongoing as we explore this issue from the client front end to gather further information about the source of this impact and determine our next steps toward remediation.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Wednesday, November 12, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:10:43 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
Current status: We're currently reviewing the EAS logs gathered from affected users to identify the source of this impact and determine our next steps toward remediation.
Scope of impact: Impact may occur for some users, where they can’t send or receive Exchange Online email messages through the native iOS Mail app using EAS.
Next update by: Wednesday, November 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 13:51:58 2025 |
|---|
| Description: | Title: Some users may be unable to send or receive email messages through the iOS Mail app using Exchange ActiveSync (EAS)
User impact: Users may be unable to send or receive Exchange Online email messages through the native iOS Mail app using EAS.
More info: The impacted users can authenticate without issue, but they receive the error "Cannot Get Mail. The connection to the server failed." when trying to refresh in their email app.
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.
|
|---|
|
FL1188501 - Users may experience failures with flow management operations
| Status: | serviceRestored |
|---|
| Start Time: | Thu Nov 20 08:15:00 2025 |
|---|
| End Time: | Thu Nov 20 13:40:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 20 14:04:13 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 20 14:04:13 2025 |
|---|
| Description: | Title: Users may experience failures with flow management operations
User impact: Users may have experienced failures with flow management operations.
Final Status: After a period of service health diagnostics monitoring, we confirmed that functionality has been restored.
This is the final update on this incident.
Preliminary Root Cause: A portion of the supporting service infrastructure experienced high CPU utilization.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Nov 20 13:32:55 2025 |
|---|
| Description: | Title: Users may experience failures with flow management operations
User impact: Users may experience failures with flow management operations.
More Info: Users may be experiencing failures with manually triggered flows and with Admin consent scenarios.
Current Status: We have performed a failover to healthy service infrastructure and are monitoring service health diagnostics to determine if further mitigating actions are warranted.
Next Update: Thursday, November 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 12:54:40 2025 |
|---|
| Description: | Title: Users may experience failures with flow management operations
User impact: Users may experience failures with flow management operations.
More Info: Users may be experiencing failures with manually triggered flows and with Admin consent scenarios.
Current Status: We identified that a portion of the supporting infrastructure is experiencing high CPU utilization, resulting in impact. We are investigating to determine the appropriate actions to mitigate the impact.
Next Update: Thursday, November 20, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 12:33:51 2025 |
|---|
| Description: | Title: Users may experience failures with flow management operations
User impact: Users may experience failures with flow management operations.
More Info: Users may be experiencing failures with manually triggered flows and with Admin consent scenarios.
Current Status: We are aware of an emerging issue where users may be experiencing failures with flow management operations, manually triggered flows, and Admin consent scenarios. 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.
|
|---|
|
PP1188497 - Microsoft Copilot Studio - Users are unable to perform actions and experience increased latency
| Status: | serviceRestored |
|---|
| Start Time: | Thu Nov 20 10:47:00 2025 |
|---|
| End Time: | Thu Nov 20 13:35:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 20 13:57:19 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 20 13:57:19 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Users are unable to perform actions and experience increased latency
User impact: Users were unable to perform actions and experienced increased latency.
Final Status: We completed the failovers to healthy redundant infrastructure and, following a period of monitoring service health diagnostics, we confirmed that service functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: High resource utilization within a portion of our internal resource provider infrastructure.
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: | Thu Nov 20 13:37:24 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Users are unable to perform actions and experience increased latency
User impact: Users unable to perform actions and experience increased latency.
Current Status: After our investigation, we identified high resource utilization within a portion of our internal resource provider infrastructure, leading to impact. To mitigate the issue, we have scaled out this infrastructure and, in parallel, have initiated traffic failovers to healthy redundant infrastructure.
Next Update: Thursday, November 20, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Nov 20 12:35:41 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Users are unable to perform actions and experience increased latency
User impact: Users unable to perform actions and experience increased latency.
Current Status: We are continuing to investigate an issue in which users are unable to perform actions and experience increased latency.
Next Update: Thursday, November 20, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Nov 20 12:21:35 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Users are unable to perform actions and experience increased latency
User impact: Users unable to perform actions and experience increased latency.
Current Status: We are aware of an emerging issue where users are unable to perform actions and experience increased latency. 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.
|
|---|
|
DZ1188185 - Some users may have seen intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 19 07:00:00 2025 |
|---|
| End Time: | Wed Nov 19 20:20:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 20 05:44:02 2025 |
|---|
| Root Cause: | A configuration issue within an upstream dependent service was causing a section of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to operate below acceptable thresholds, which resulted in intermittent delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 20 05:29:57 2025 |
|---|
| Description: | Title: Some users may have seen intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
User impact: Users may have seen intermittent delays receiving new commands and configurations in Microsoft Defender for Endpoint.
Final status: We've confirmed after a period of monitoring service health, that the deployment of the fix has completed and the issue is no longer occurring.
Scope of impact: Impact was specific to users expecting to receive new commands and configurations in Microsoft Defender for Endpoint.
Start time: Wednesday, November 19, 2025, at 12:00 PM UTC
End time: Thursday, November 20, 2025, at 1:20 AM UTC
Root cause: A configuration issue within an upstream dependent service was causing a section of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to operate below acceptable thresholds, which resulted in intermittent 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: | Wed Nov 19 20:50:40 2025 |
|---|
| Description: | Title: Some users may experience intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
User impact: Users may experience intermittent delays receiving new commands and configurations in Microsoft Defender for Endpoint.
Current status: As our change continues to deploy, we can see from our telemetry metrics that it’s having the intended effect and the service is on its way to recovery. We anticipate this deployment will be completed and impact will be fully remediated by our next scheduled communications update.
Scope of impact: Impact may occur for some users where intermittent delays receiving new commands and configurations may occur in Microsoft Defender for Endpoint.
Start time: Wednesday, November 19, 2025, at 12:00 PM UTC
Root cause: A configuration issue within an upstream dependent service is causing a portion of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to operate below acceptable thresholds, resulting in intermittent delays.
Next update by: Thursday, November 20, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 20:20:02 2025 |
|---|
| Description: | Title: Some users may experience intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
User impact: Users may experience intermittent delays receiving new commands and configurations in Microsoft Defender for Endpoint.
Current status: We’ve monitored the upstream service as it restarted the affected infrastructure and while we’ve observed some improvements from this action, it wasn’t enough to fully remediate the problem. Additionally, we’re deploying a change to decrease our time out threshold to alleviate pressure on the affected infrastructure and improve service responsiveness. We’re monitoring our service telemetry to validate that our additional action is helping to remediate the issue.
Scope of impact: Impact may occur for some users where intermittent delays receiving new commands and configurations may occur in Microsoft Defender for Endpoint.
Start time: Wednesday, November 19, 2025, at 12:00 PM UTC
Root cause: A configuration issue within an upstream dependent service is causing a portion of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to operate below acceptable thresholds, resulting in intermittent delays.
Next update by: Thursday, November 20, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 18:18:07 2025 |
|---|
| Description: | Title: Some users may experience intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
User impact: Users may experience intermittent delays receiving new commands and configurations in Microsoft Defender for Endpoint.
Current status: We’ve identified that the intermittent delays relate to a configuration issue within an upstream dependent service, which has affected a portion of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to perform below acceptable thresholds, resulting in impact. The upstream service is restarting the affected infrastructure, and we're monitoring the service to validate that this action will remediate the problem.
Scope of impact: Impact may occur for some users where intermittent delays receiving new commands and configurations may occur in Microsoft Defender for Endpoint.
Start time: Wednesday, November 19, 2025, at 12:00 PM UTC
Root cause: A configuration issue within an upstream dependent service is causing a portion of Microsoft Defender for Endpoint infrastructure that distributes commands and configurations to operate below acceptable thresholds, resulting in intermittent delays.
Next update by: Thursday, November 20, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Nov 19 17:06:20 2025 |
|---|
| Description: | Title: Some users may experience intermittent delays receiving commands and configurations in Microsoft Defender for Endpoint
User impact: Users may experience intermittent delays receiving new commands and configurations in Microsoft Defender for Endpoint.
Current status: Our monitoring systems have identified impact where some users may experience delays receiving new commands and configurations in Microsoft Defender for Endpoint. After assessment, we've identified that a portion of Microsoft Defender for Endpoint infrastructure that facilitates distributing commands and configurations to clients using streamlined connectivity is operating below acceptable thresholds, resulting in impact. We're validating potential remediation pathways.
Scope of impact: Impact may occur for some users where intermittent delays receiving new commands and configurations may occur in Microsoft Defender for Endpoint.
Start time: Wednesday, November 19, 2025, at 12:00 PM UTC
Root cause: A portion of Microsoft Defender for Endpoint infrastructure that facilitates distributing commands and configurations to clients using streamlined connectivity is operating below acceptable thresholds, resulting in impact.
Next update by: Wednesday, November 19, 2025, at 11:30 PM UTC
|
|---|
|
SP1030180 - Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
| Status: | extendedRecovery |
|---|
| 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 Nov 19 22:08:05 2025 |
|---|
| Root Cause: | A recent deployment incorrectly enabled this feature in the affected environment. |
|---|
| Next Update: | Thursday, December 4, 2025, at 6:00 AM UTC |
|---|
|
Details
| Time: | Wed Nov 19 22:08:05 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 continuing to monitor as the fix completes saturating throughout the affected environment to confirm it remains stable.
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, December 4, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 23:52:50 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: While the fix deployment is taking longer than previously anticipated to complete, our service health telemetry indicates that the impact is resolved for the affected users. We’re continuing to monitor as the remainder of the fix propagates throughout the affected environment and to ensure that the impact is fully remediated.
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, November 20, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Oct 22 23:43: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: The fix deployment has nearly completed and we anticipate that the issue is no longer occurring for affected users. We’re monitoring the remainder of the deployment to confirm that the environment remains stable and the impact is fully remediated prior to our next scheduled update.
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, October 30, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Oct 16 00:20: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. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: Our telemetry indicates that the fix has nearly completed. We're continuing to monitor as it progresses and anticipate providing a completion timeline at our next scheduled update.
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, October 23, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Oct 8 21:09:03 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: Our fix deployment is ongoing; however, we've yet to establish an updated completion timeline. We're continuing to monitor to ensure remediation and provide a timeline once one becomes available.
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, October 16, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Sep 10 22:48:35 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: The fix deployment is ongoing and we're continuing to monitor as it progresses to establish a completion timeline.
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, October 9, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Aug 27 23:40:52 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: The fix deployment has encountered a delay and won't complete by our initial anticipated projection. We're continuing to monitor as it progresses and will provide an updated timeline when one becomes available.
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, September 11, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Aug 13 22:53:06 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: The fix deployment is ongoing and we're continuing to monitor as it progresses. We now anticipate it will have completed by the end of August 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, August 28, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Aug 6 22:19:57 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: The fix deployment is taking longer than anticipated, but is ongoing. We'll provide an updated completion timeline when one becomes available.
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, August 14, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jul 16 23:58:02 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: The fix deployment is ongoing, and we continue to estimate that it will complete by late July 2025, or early August 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, August 7, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jul 2 23:32:10 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: The fix is deploying to the impacted environments, and our monitoring indicates that the majority of affected tenants should be experiencing remediation. We estimate that the remainder of the deployment will complete by late July 2025, or early August 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, July 17, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jun 18 22:51:25 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 completed deploying the fix to our internal testing environment and validated that it successfully remediates impact. We've started deploying the fix to the impacted environments, and anticipate the deployment may complete by late July 2025, or early August 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, July 3, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jun 4 22:59:19 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 completed the development of our updated fix for the issue and are finalizing its validation within our internal testing environment in preparation for its widespread deployment.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 19, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 21 23:15:44 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've encountered an issue with our long-term fix during our internal testing and validation process. We're working to debug the issue to prepare the fix for deployment and anticipate this may push back our timeline for remediation by four to five weeks, meaning users may not see our changes in effect until late July 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 5, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 7 23:24:45 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've begun the initial validation and internal testing of the aforementioned long-term fix, and this process remains on track to complete by our previously communicated mid-June 2025 estimation.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 23 23:00:43 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're focusing our efforts on developing and deploying a long-term fix to remove the incorrect inclusion of the "Content Freshness" template option, which remains on track to be completed by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 8, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 9 23:18:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've identified an issue with our previously developed near-term fix to remove the template option and determined its deployment needs to be suspended. While we continue to assess our options for potential expedited solutions, we're working on a long-term fix that we're projecting may be released by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 26 21:38:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 10, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 23:48:34 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
|
|---|
|
TM1186997 - Some users may be unable to join teams in Microsoft Teams when using a join code
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 12 17:00:00 2025 |
|---|
| End Time: | Tue Nov 18 16:50:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 19 16:36:45 2025 |
|---|
| Root Cause: | A recent update for Microsoft Teams contained a code issue that was impacting join code functionality. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 19 16:36:45 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may have been unable to join teams in Microsoft Teams when using a join code.
More info: Users saw a specific error that translated to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users could’ve sent a link to join the team to bypass using the join code.
Final status: Our fix deployment is complete and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: This problem may have intermittently impacted any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
End time: Tuesday, November 18, 2025, at 9:50 PM UTC
Root cause: A recent update for Microsoft Teams contained a code issue that was impacting join code functionality.
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: | Tue Nov 18 19:47:20 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We've confirmed that the fix has been successfully deployed to the bulk of the impacted environment. The final stage of our fix deployment, to a subset of users located in the Eastern United States region, is expected to complete by the time of our next scheduled update.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Root cause: A recent update for Microsoft Teams contained a code issue that is impacting join code functionality.
Next update by: Wednesday, November 19, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Nov 18 14:35:44 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We’ve confirmed that the fix deployment is complete to a portion of the affected environment and that some users may already be noticing signs of impact remediation. We’re continuing to monitor the ongoing deployment as it reaches the remaining affected environment to ensure the issue is fully resolved as expected by our next scheduled update.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Root cause: A recent update for Microsoft Teams contained a code issue that is impacting join code functionality.
Next update by: Wednesday, November 19, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Nov 17 21:21:26 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We deployed and validated the fix in our internal environment. We've initiated the deployment of the fix to the affected environment and will continue monitoring the progress. We estimate that the deployment will have reached the majority of the affected environment by the next scheduled update time.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Root cause: A recent update for Microsoft Teams contained a code issue that is impacting join code functionality.
Next update by: Tuesday, November 18, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Nov 17 16:46:03 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We're monitoring the deployment of the fix to our internal test environment, which we anticipate will complete by our next scheduled communications update.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Next update by: Tuesday, November 18, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Nov 17 14:39:29 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We're working to validate the fix internally before releasing it more broadly. We expect to have a deployment timeline by the next scheduled update.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Next update by: Monday, November 17, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Nov 17 13:14:22 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: Our reversion isn't progressing as expected due to an unrelated issue. We're in the process of rolling forward a fix to remediate impact and will provide a mitigation timeline once available.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Next update by: Monday, November 17, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Nov 17 05:31:46 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We're reverting the aforementioned change in our test environment to validate that it resolves the issue. Once confirmed, we'll proceed with reverting the change across all affected environments.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Next update by: Monday, November 17, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Nov 17 03:31:55 2025 |
|---|
| Description: | Title: Some users may be unable to join teams in Microsoft Teams when using a join code
User impact: Users may be unable to join teams in Microsoft Teams when using a join code.
More info: Users may get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
As workaround, users can send a link to join the team to bypass using the join code.
Current status: We believe a recent update to the middle-tier code may be contributing to the issue. Specifically, the request URI for fetching group owners is missing the required select property to include the "accountEnabled" field, which may explain the unexpected behaviour. Our team is conducting a detailed analysis to validate this hypothesis.
Scope of impact: This problem may intermittently impact any user attempting to join teams in Microsoft Teams when using a join code.
Start time: Wednesday, November 12, 2025, at 10:00 PM UTC
Next update by: Monday, November 17, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Nov 17 02:01:18 2025 |
|---|
| Description: | Title: Users are unable to join teams in Microsoft Teams when using a join code
User impact: Users are unable to join teams in Microsoft Teams when using a join code.
More info: Users get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
Current status: We're continuing our analysis of the case details, as well as reviewing details from an internal reproduction of the issue and logs from the impacted service, to help isolate the underlying cause of impact.
Scope of impact: Your organization is impacted by this event, and users are unable to join teams in Microsoft Teams when using a join code, and get a specific error. This section may be updated as our investigation continues.
Next update by: Monday, November 17, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Nov 17 00:58:10 2025 |
|---|
| Description: | Title: Users are unable to join teams in Microsoft Teams when using a join code
User impact: Users are unable to join teams in Microsoft Teams when using a join code.
More info: Users get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
Current status: We're continuing to review the provided case details and screenshots to help inform our next troubleshooting steps for identifying the cause of impact.
Scope of impact: Your organization is impacted by this event, and users are unable to join teams in Microsoft Teams when using a join code, and get a specific error. This section may be updated as our investigation continues.
Next update by: Monday, November 17, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Nov 17 00:00:13 2025 |
|---|
| Description: | Title: Users are unable to join teams in Microsoft Teams when using a join code
User impact: Users are unable to join teams in Microsoft Teams when using a join code.
More info: Users get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
Current status: We're reviewing the provided case details and screenshots to help understand the cause of impact and inform our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and users are unable to join teams in Microsoft Teams when using a join code and get a specific error.
Next update by: Monday, November 17, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sun Nov 16 23:31:23 2025 |
|---|
| Description: | Title: Users are unable to join teams in Microsoft Teams when using a join code
User impact: Users are unable to join teams in Microsoft Teams when using a join code.
More info: Users get a specific error that translates to “Couldn't join this team with that code. Double-check the code or try another one”.
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.
|
|---|
|
SP1177145 - Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 13 14:50:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 19 15:21:08 2025 |
|---|
| Root Cause: | A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. |
|---|
| Next Update: | Monday, December 1, 2025, at 8:00 PM UTC |
|---|
|
Details
| Time: | Wed Nov 19 15:20:35 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We’ve successfully deployed a fix that addresses the underlying issue and prevents additional folders, files, and list items from being impacted. To address folders, files, and list items that are still impacted by this event, we're validating an automated repair process that identifies and corrects impacted items. While initial indications are that the process to address and corrected impacted items will take an extended period of time, we’ll communicate the status of this long-term mitigation strategy and provide an updated remediation timeline as this event progresses.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:25:25 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The removal of the errors isolated during our internal tests and validations requires additional time, and we'll provide an updated timeline for our fix validations once it’s available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 14:08:43 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: During the validation process of our fix, we isolated additional errors that needed to be addressed prior to beginning a broad deployment to the affected environment. We’re working to eliminate all additional errors, and we aim to provide a timeline to deployment as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:10:06 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We're continuing to prepare the fix for broad deployment to the affected environment and we'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 13:44:02 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've completed our internal validation of the completed portion of our fix and confirmed it successfully remediates impact. For any users experiencing impact at this time, your organization may raise a support case to have this fix manually run to repair affected items. With our internal validation completed, we're continuing to prepare the fix for a future deployment so that the repair job runs proactively to fully remediate impact. We're working to estimate a timeline for this deployment and overall impact resolution.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 29, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 16:04:16 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: Development of the remaining necessary portions of the overall solution is progressing as we continue internal testing of the completed portion to verify its efficacy to correct the issue. We'll continue to provide updates as we near the completion of this process and provide a remediation timeline when possible.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, October 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 15:19:56 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: While we've finalized a portion of the necessary code fixes to address the issue, and are validating the effectiveness of this portion, we're still developing several other portions of overall solution. All portions of the full fix will need to be completed and validated before we begin our deployment process as they are dependent on each other. Once complete, we'll provide a timeline for deployment and impact remediation as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Friday, October 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 23:10:34 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've made progress in the development of a portion of code fixes to address the issue. We're working to further finalize our remaining code fixes needed to address the full impact before we can provide a full deployment timeline.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 19:49:39 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We're continuing the development and internal testing of our code fix, and anticipate we may be able to provide an estimated timeline for its deployment by our next scheduled update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:44:25 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've identified a recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. We're developing a code fix that will undergo internal testing and validations, and we'll aim to provide a resolution timeline once available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:18:27 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Current status: We're investigating a potential issue with OneDrive and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OD1177143 - Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 13 11:50:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 19 15:16:59 2025 |
|---|
| Root Cause: | A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. |
|---|
| Next Update: | Monday, December 1, 2025, at 8:00 PM UTC |
|---|
|
Details
| Time: | Wed Nov 19 15:16:59 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We’ve successfully deployed a fix that addresses the underlying issue and prevents additional folders, files, and list items from being impacted. To address folders, files, and list items that are still impacted by this event, we're validating an automated repair process that identifies and corrects impacted items. While initial indications are that the process to address and corrected impacted items will take an extended period of time, we’ll communicate the status of this long-term mitigation strategy and provide an updated remediation timeline as this event progresses.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:25:52 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The removal of the errors isolated during our internal tests and validations requires additional time, and we'll provide an updated timeline for our fix validations once it’s available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 14:08:46 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: During the validation process of our fix, we isolated additional errors that needed to be addressed prior to beginning a broad deployment to the affected environment. We’re working to eliminate all additional errors, and we aim to provide a timeline to deployment as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:09:50 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We're continuing to prepare the fix for broad deployment to the affected environment, and we'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 13:42:19 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've completed our internal validation of the completed portion of our fix and confirmed it successfully remediates impact. For any users experiencing impact at this time, your organization may raise a support case to have this fix manually run to repair affected items. With our internal validation completed, we're continuing to prepare the fix for a future deployment so that the repair job runs proactively to fully remediate impact. We're working to estimate a timeline for this deployment and overall impact resolution.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 29, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 16:02:53 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: Development of the remaining necessary portions of the overall solution is progressing as we continue internal testing of the completed portion to verify its efficacy to correct the issue. We'll continue to provide updates as we near the completion of this process and provide a remediation timeline when possible.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, October 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 15:16:24 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: While we've finalized a portion of the necessary code fixes to address the issue, and are validating the effectiveness of this portion, we're still developing several other portions of overall solution. All portions of the full fix will need to be completed and validated before we begin our deployment process as they are dependent on each other. Once complete, we'll provide a timeline for deployment and impact remediation as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Friday, October 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 23:11:51 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've made progress in the development of a portion of code fixes to address the issue. We're working to further finalize our remaining code fixes needed to address the full impact before we can provide a full deployment timeline.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 19:49:45 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We're continuing the development and internal testing of our code fix, and anticipate we may be able to provide an estimated timeline for its deployment by our next scheduled update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:42:05 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've identified a recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. We're developing a code fix that will undergo internal testing and validations, and we'll aim to provide a resolution timeline once available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:16:01 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Current status: We're investigating a potential issue with OneDrive and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP1186186 - Users may have been unable to install Microsoft 365 desktop apps on Windows devices
| Status: | serviceRestored |
|---|
| Start Time: | Tue Nov 11 13:00:00 2025 |
|---|
| End Time: | Tue Nov 18 16:00:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Nov 18 17:10:51 2025 |
|---|
| Root Cause: | A newly released set of authentication components contained a misconfiguration that prevented users from installing Microsoft 365 desktop apps on Windows devices. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 18 17:10:51 2025 |
|---|
| Description: | Title: Users may have been unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may have been unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacted users who attempted to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Final status: We’ve confirmed that the fixed build is fully deployed and available and we’ve determined that users are now able to install Microsoft 365 desktop apps on Windows devices as expected.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may have been impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
End time: Tuesday, November 18, 2025, at 9:00 PM UTC
Root cause: A newly released set of authentication components contained a misconfiguration that prevented users from installing Microsoft 365 desktop apps on Windows devices.
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: | Tue Nov 18 13:50:54 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: The fix has been deployed to the majority of impacted users, and we're performing final validations to confirm that the deployment completes for all affected users and remediates the impact.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Tuesday, November 18, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Nov 17 21:35:47 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: The deployment of the secondary build for version 2507 is taking an extended period of time. As we continue to monitor its progress we’re working to gather a remediation timeline, which we anticipate will be provided by our next scheduled update.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Tuesday, November 18, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Nov 17 18:59:18 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: The deployment of the secondary build for version 2507 is taking longer than initially anticipated, and we now expect it to be complete by our next scheduled update.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Tuesday, November 18, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Nov 17 16:18:54 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: We've confirmed that the deployment of the secondary build for version 2507 has been initiated, and we anticipate the deployment will be complete and the impact remediated by our next scheduled update.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Tuesday, November 18, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Nov 17 13:48:50 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: The build for version 2508 completed deployment and we confirmed with affected users that impact is partially resolved. Our secondary build for version 2507 has validated and is being prepared for deployment. We expect this fix deployment should start and complete by our next update.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Monday, November 17, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Nov 14 17:49:26 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: We're continuing to develop a set of two builds that address the authentication component misconfigurations, with the build for version 2508 validated and in the process of deploying. We anticipate that our second build for version 2507 will be ready for final validation by our next scheduled update, after which we'll deploy to fully remediate impact.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Monday, November 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Nov 14 15:28:44 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: We're continuing to reconfigure the affected authentication components and will subsequently redeploy them after a period of internal validation to confirm our fix remediates impact.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Saturday, November 15, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Nov 14 11:29:12 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
More info: This only impacts users who attempt to install version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294) of the Microsoft 365 desktop apps.
Current status: We've determined that a newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices. We're reconfiguring and will subsequently redeploy these components to remediate impact.
Scope of impact: Any user attempting to install Microsoft 365 desktop apps on Windows devices may be impacted.
Start time: Tuesday, November 11, 2025, at 6:00 PM UTC
Root cause: A newly released set of authentication components contain a misconfiguration that prevents users from installing Microsoft 365 desktop apps on Windows devices.
Next update by: Friday, November 14, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Nov 14 11:12:33 2025 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 desktop apps on Windows devices
User impact: Users may be unable to install Microsoft 365 desktop apps on Windows devices.
Current status: We're investigating a potential issue with Microsoft 365 desktop apps, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1187642 - Some users may be unable to interact with bots or agents within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Nov 18 09:00:00 2025 |
|---|
| End Time: | Tue Nov 18 10:19:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 18 11:03:13 2025 |
|---|
| Root Cause: | An unexpected increase in user traffic caused our service infrastructure responsible for managing bot and agent interactions within Microsoft Teams to have a drop in availability. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 18 11:03:13 2025 |
|---|
| Description: | Title: Some users may be unable to interact with bots or agents within Microsoft Teams
User impact: Users may have been unable to interact with bots or agents within Microsoft Teams.
Final status: We've isolated an unexpected increase in user traffic that caused our service infrastructure responsible for managing bot and agent interactions within Microsoft Teams to drop in availability. This resulted in users located in North and South America possibly being unable to interact with bots and agents within Microsoft Teams. We implemented performance optimizations to process the increased traffic and after completing our monitoring period, we confirmed our actions have restored service.
Scope of impact: Impact was specific to some users located in North and South America, attempting to interact with bots or agents within Microsoft Teams.
Start time: Tuesday, November 18, 2025, at 2:00 PM UTC
End time: Tuesday, November 18, 2025, at 3:19 PM UTC
Root cause: An unexpected increase in user traffic caused our service infrastructure responsible for managing bot and agent interactions within Microsoft Teams to have a drop in availability.
Next steps:
- We're analyzing the spike in user traffic to understand what additional enhancements we can implement to our Microsoft Teams service infrastructure to improve the resilience of our service and to ensure similar impact doesn't occur in future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 18 10:21:57 2025 |
|---|
| Description: | Title: Some users may be unable to interact with bots or agents within Microsoft Teams
User impact: Users may be unable to interact with bots or agents within Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and establish a fix.
Scope of impact: Impact is specific to some users located in North and South America, attempting to interact with bots or agents within Microsoft Teams.
Next update by: Tuesday, November 18, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Nov 18 09:32:09 2025 |
|---|
| Description: | Title: Some users may experience limited access to certain Microsoft Teams features
User impact: Users may experience limited access to certain Microsoft Teams features.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: This issue may impact any user within your organization that is accessing the service from the affected region(s): United States. This information may be updated as our investigation continues.”
Next update by: Tuesday, November 18, 2025, at 5:00 PM UTC
|
|---|
|
PP1184679 - Power Pages - Lookup fields for Power Pages management display a 'No Name' message
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 17 05:00:00 2025 |
|---|
| End Time: | Sat Nov 15 03:00:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 17 19:26:01 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 17 19:26:01 2025 |
|---|
| Description: | Title: Power Pages - Lookup fields for Power Pages management display a 'No Name' message
User impact: Lookup fields for Power Pages management displayed a 'No Name' message.
Final Status: We have completed reverting the change. Our diagnostic analysis and testing have confirmed that lookup field functionality has been restored.
This is the final update on the incident.
Preliminary Root Cause: Impact occurred following a recent code change that was deployed.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Wed Nov 12 19:11:13 2025 |
|---|
| Description: | Title: Power Pages - Lookup fields for Power Pages management display a 'No Name' message
User impact: Lookup fields for Power Pages management display a 'No Name' message.
Current Status: Reversion of the change is ongoing. As this operation progresses, some users may observe recovery.
Next Update: Tuesday, November 18, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Nov 11 19:11:03 2025 |
|---|
| Description: | Title: Power Pages - Lookup fields for Power Pages management display a 'No Name' message
User impact: Lookup fields for Power Pages management display a 'No Name' message.
Current Status: We are continuing the process of reverting the offending change in order to mitigate the issue.
Next Update: Thursday, November 13, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Nov 10 22:47:49 2025 |
|---|
| Description: | Title: Power Pages - Lookup fields for Power Pages management display a 'No Name' message
User impact: Lookup fields for Power Pages management display a 'No Name' message.
Current Status: After our investigation, we identified that impact occurred following a recent code change that was deployed. We are reverting this code change to mitigate impact.
Next Update: Wednesday, November 12, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Nov 10 22:30:16 2025 |
|---|
| Description: | Title: Power Pages - Lookup fields for Power Pages management display a 'No Name' message
User impact: Lookup fields for Power Pages management display a 'No Name' message.
Current Status: We are aware of an emerging issue where lookup fields for Power Pages management display a 'No Name' message. 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.
|
|---|
|
MP1186383 - Users may be unable to view Microsoft Purview eDiscovery in-progress exports
| Status: | serviceRestored |
|---|
| Start Time: | Fri Nov 14 19:08:21 2025 |
|---|
| End Time: | Sat Nov 15 02:30:00 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 17 17:40:02 2025 |
|---|
| Root Cause: | A recent code update for the Purview service introduced an issue that impacted the visibility of in-progress eDiscovery exports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 17 17:40:02 2025 |
|---|
| Description: | Title: Users may be unable to view Microsoft Purview eDiscovery in-progress exports
User impact: Users may have been unable to view eDiscovery in-progress exports.
More info: Exports were viewable once they were completed.
Final status: We've completed deployment of our code fix and confirmed after internal testing that the impact is remediated.
Scope of impact: Any user attempting to view eDiscovery in-progress exports may have been impacted.
Start time: Monday, November 10, 2025, at 12:00 AM UTC
End time: Saturday, November 15, 2025, at 7:30 AM UTC
Root cause: A recent code update for the Purview service introduced an issue that impacted the visibility of in-progress eDiscovery exports.
Next steps:
- We're reviewing our code update testing and validation procedures to identify and prevent similar export visibility issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 14 19:46:10 2025 |
|---|
| Description: | Title: Users may be unable to view Microsoft Purview eDiscovery in-progress exports
User impact: Users may be unable to view eDiscovery in-progress exports.
More info: Exports are viewable once they complete.
Current status: We identified that a recent code update for the Purview service introduced an issue that’s impacting the visibility of in-progress eDiscovery exports. We've developed a code fix for the issue and are deploying it to the affected environment to remediate the impact.
Scope of impact: This issue may potentially impact any user attempting to view eDiscovery in-progress exports.
Start time: Monday, November 10, 2025, at 12:00 AM UTC
Root cause: A recent code update for the Purview service introduced an issue that’s impacting the visibility of in-progress eDiscovery exports.
Next update by: Tuesday, November 18, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Nov 14 19:14:10 2025 |
|---|
| Description: | Title: Users may be unable to view Microsoft Purview eDiscovery in-progress exports
User impact: Users may be unable to view eDiscovery in-progress exports.
Current status: We're investigating a potential issue with Microsoft Purview and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1183805 - Users may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward
| Status: | serviceRestored |
|---|
| Start Time: | Fri Nov 7 15:53:14 2025 |
|---|
| End Time: | Fri Nov 14 20:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 17 12:49:32 2025 |
|---|
| Root Cause: | An issue with our data importer for Microsoft Teams clients and admin center analytics was preventing it from efficiently ingesting data, which caused updates for Teams channel reports to be delayed since October 24, 2025. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 17 12:49:32 2025 |
|---|
| Description: | Title: Users may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward
User impact: Users may not have had Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward.
More info: This impacted both users and admins. The problem occurred in the Microsoft Teams admin center as well as within the Manage team Analytics tab, found within Microsoft Teams clients.
Final status: We confirmed that the remaining portion of the backlogged data completed processing, and that this successfully remediated all impact.
Scope of impact: The problem impacted all admins trying to access Microsoft Teams clients and admin center channel analytics in the admin center, as well as users that accessed content in the Manage team Analytics tab found within Microsoft Teams clients. Data starting from Friday, October 24, 2025, was impacted.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
End time: Saturday, November 15, 2025, at 1:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams clients and admin center analytics was preventing it from efficiently ingesting data, which caused updates for Teams channel reports to be delayed since October 24, 2025.
Next steps:
- We're further analyzing the issue with our data importer for Microsoft Teams to determine more efficient methods of detecting data delays and prevent similar service incidents from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Nov 14 13:21:20 2025 |
|---|
| Description: | Title: Users may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward
User impact: Users may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward.
More info: This impacts both users and admins. The problem occurs in the Microsoft Teams admin center as well as within the Manage team Analytics tab found within Microsoft Teams clients.
Current status: We've processed a portion of the backlogged data and are continuing to monitor the remaining backlog to ensure successful completion and full remediation. Based on our current estimates, we expect all remaining data to complete processing by our next scheduled update.
Scope of impact: The problem impacts all admins trying to access Microsoft Teams clients and admin center channel analytics in the admin center, as well as users accessing content in the Manage team Analytics tab found within Microsoft Teams clients. Data starting from Friday, October 24, 2025, is impacted.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams clients and admin center analytics is preventing it from efficiently ingesting data and causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Monday, November 17, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Nov 13 15:52:01 2025 |
|---|
| Description: | Title: Admins may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward
User impact: Admins may not have Microsoft Teams clients and admin center channel analytics data from October 24, 2025, onward.
Current status: We've confirmed that this impact is also occurring within the Manage team Analytics tab found within Microsoft Teams clients, and we've updated the Title, User impact, Scope of impact, and Root cause fields of this communication to reflect this change. Regarding the status of mitigating the impact, we're still processing the remaining backlogged data, which is still expected to complete by our next scheduled update.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams clients and admin center analytics is preventing it from efficiently ingesting data and causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Friday, November 14, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Nov 11 20:51:40 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: Processing the remaining backlog of data is taking longer than anticipated due to unrelated complications. We're continuing our efforts of processing the remaining data and anticipate the majority of remaining data will have been processed by our next scheduled update.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is preventing it from efficiently ingesting data and causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Friday, November 14, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Nov 11 14:46:19 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We've applied our fix for our data importer and our service health telemetry indicates that the channel analytics data is now processing as expected. We expect the remaining backlog of unprocessed data to be available to admins by the time of our next update.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is preventing it from efficiently ingesting data and causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Wednesday, November 12, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 14:59:45 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We're continuing to develop the potential fix for the data importer, which will undergo validations before deploying it to ensure that the channel analytics data becomes up to date. We anticipate being able to provide more details on the proposed fix by our next scheduled update.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Tuesday, November 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 20:29:34 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We've developed a potential fix for the data importer. Once implemented, we'll monitor our telemetry to ensure that the channel analytics data becomes up to date.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Start time: Friday, October 24, 2025, at 12:00 AM UTC
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Monday, November 10, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 18:28:21 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We're continuing to troubleshoot the importer problems in order to develop and evaluate remediation strategies.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Saturday, November 8, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Nov 7 16:32:47 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We've identified an issue with our data importer for Microsoft Teams admin center analytics, which is causing updates for Microsoft Teams channel reports to be delayed for October 24, 2025, and onward. We're working to fix this issue with our importer to remediate impact, as well as determining options for backfilling the data.
Scope of impact: All admins may not have channel analytics data available to them in the Microsoft Team admin center since October 24, 2025.
Root cause: An issue with our data importer for Microsoft Teams admin center analytics is causing updates for Teams channel reports to be delayed since October 24, 2025.
Next update by: Friday, November 7, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 15:59:06 2025 |
|---|
| Description: | Title: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward
User impact: Admins may not have channel analytics data in the Microsoft Teams admin center from October 24, 2025, onward.
Current status: We're investigating a potential issue in with the Microsoft Teams admin center. We're checking for impact to your organization and will provide an update within 30 minutes.
|
|---|
|
FL1176909 - Users are unable to run cloud and desktop flows or manage flows
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Oct 21 07:50:00 2025 |
|---|
| End Time: | Tue Oct 21 11:43:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Nov 16 11:48:38 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Nov 16 11:48:38 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 21 12:11:57 2025 |
|---|
| Description: | Title: Users are unable to run cloud and desktop flows or manage flows
User impact: Users were unable to run cloud and desktop flows or manage flows.
More info: The following scenarios were also affected:
-Turn on/turn off flow
-List flows
-Load flow properties
-Flow run history
Final Status: After restoring connectivity to the affected storage infrastructure, we have confirmed that flow management and runtime functionality has been restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the storage infrastructure responsible for processing flow management and runtime operations experienced a network connectivity disruption.
Next Steps: We're reviewing our monitoring services to reduce detection time and more quickly restore service.
|
|---|
|
| Time: | Tue Oct 21 10:33:41 2025 |
|---|
| Description: | Title: Users are unable to run cloud and desktop flows or manage flows
User impact: Users are unable to run cloud and desktop flows or manage flows.
Current Status: Our investigation has determined that a portion of the storage infrastructure responsible for processing flow management and runtime operations has experienced a network connectivity disruption. We are working to restore connectivity to the affected infrastructure to restore flow runtime and management functionality.
Next Update: Tuesday, October 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 10:18:33 2025 |
|---|
| Description: | Title: Users are unable to run cloud and desktop flows or manage flows
User impact: Users are unable to run cloud and desktop flows or manage flows.
Current Status: We are aware of an emerging issue where users are experiencing failures when attempting to create, edit, delete, or save flows, and when attempting to run desktop and cloud flows. 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.
|
|---|
|
CP1186191 - Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
| Status: | serviceRestored |
|---|
| Start Time: | Fri Nov 14 01:30:00 2025 |
|---|
| End Time: | Sat Nov 15 09:05:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Nov 15 11:14:08 2025 |
|---|
| Root Cause: | A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat was preventing it from efficiently handling requests and was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Nov 15 11:09:01 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may have been missing results or experienced delays when using Copilot Search or Copilot Chat.
More info: Impact occurred for any app that featured Copilot search or Copilot chat. Users may have also received poor quality of data when they received search results.
Final status: We've confirmed through monitoring service health telemetry that the performance optimizations we've implemented have remediated the impact.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may have been impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
End time: Saturday, November 15, 2025, at 2:05 PM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat was preventing it from efficiently handling requests and was causing impact.
Next steps:
- We're reviewing our update procedures to understand why impact to Copilot Search and Copilot Chat 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: | Sat Nov 15 04:31:10 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
More info: Impact occurs for any app that features Copilot search or Copilot chat. Users may also receive poor quality of data when they do receive search results.
Current status: We've actioned some service performance optimizations in an attempt to mitigate the remaining impact. We're continuing to monitor service telemetry to identify why impact is still occurring.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may be impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat is preventing it from efficiently handling requests and is causing impact.
Next update by: Saturday, November 15, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Nov 14 22:03:25 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
Current status: While the service has nearly returned to a fully healthy state after reversing the offending change, we’re investigating why some impact is still occurring to determine our next steps toward expedient remediation.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may be impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat is preventing it from efficiently handling requests and is causing impact.
Next update by: Saturday, November 15, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Nov 14 17:17:37 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
More info: Impact occurs for any app that features Copilot search or Copilot chat. Users may also receive poor quality of data when they do receive search results.
Current status: We observed that the service hasn't returned to a fully healthy state after reversing the offending change. We're investigating why this issue is still occurring to determine our next steps toward expedient remediation.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may be impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat is preventing it from efficiently handling requests and is causing impact.
Next update by: Saturday, November 15, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Nov 14 12:29:20 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
More info: Impact occurs for any app that features Copilot search or Copilot chat. Users may also receive poor quality of data when they do receive search results.
Current status: We're continuing to reverse the offending change to restore the services.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may be impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat is preventing it from efficiently handling requests and is causing impact.
Next update by: Saturday, November 15, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Nov 14 11:28:12 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
More info: Impact occurs for any app that features Copilot search or Copilot chat. Users may also receive poor quality of data when they do receive search results.
Current status: We've identified a recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat, which is preventing it from efficiently handling requests and is causing impact. We're reversing this service change to remediate the impact.
Scope of impact: Any user attempting to use Copilot Search or Copilot chat may be impacted.
Start time: Friday, November 14, 2025, at 6:30 AM UTC
Root cause: A recent service change that increased request traffic to the portion of infrastructure responsible for facilitating Copilot search and Copilot chat is preventing it from efficiently handling requests and is causing impact.
Next update by: Friday, November 14, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Nov 14 11:22:52 2025 |
|---|
| Description: | Title: Users may not see results or experience delays using Microsoft Copilot (Microsoft 365) or Copilot Chat
User impact: Users may be missing results or experience delays when using Copilot Search or Copilot Chat.
More info: Impact occurs for any app that features Copilot search or Copilot chat. Users may also receive poor quality of data when they do receive search results.
Current status: We're investigating a potential issue with Copilot Search and Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1186252 - Users may see some parts of the Outlook UI in English instead of their non-English selected language
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 10 11:00:00 2025 |
|---|
| End Time: | Fri Nov 14 17:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 14 17:48:28 2025 |
|---|
| Root Cause: | A recent update was causing some parts of the UI in Outlook on the web and new Outlook desktop client to show in English instead of the intended, non-English language selected by users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 14 17:44:55 2025 |
|---|
| Description: | Title: Users may see some parts of the Outlook UI in English instead of their non-English selected language
User impact: Users may have seen some parts of the Outlook UI in English instead of their non-English selected language.
Final status: We've reverted the offending update and confirmed through monitoring service health telemetry that the impact has been remediated. Affected users will need to restart their Outlook desktop client or Outlook on the web browser to have the changes take effect.
Scope of impact: This issue may have affected any user whose language was set to a non-English language and was using Outlook on the web or the new Outlook desktop client.
Start time: Monday, November 10, 2025, at 4:00 PM UTC
End time: Friday, November 14, 2025, at 10:00 PM UTC
Root cause: A recent update was causing some parts of the UI in Outlook on the web and new Outlook desktop client to show in English instead of the intended, non-English language selected by users.
Next steps:
- We're reviewing our update procedures to understand why impact to the Outlook UI 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: | Fri Nov 14 14:02:01 2025 |
|---|
| Description: | Title: Users may see some parts of the UI in English instead of their non-English selected language
User impact: Users may see some parts of the UI in English instead of their non-English selected language.
Current status: We've confirmed that a recent update is causing some parts of the UI in Outlook on the web and new Outlook desktop client to show in English instead of the intended, non-English language selected by users. We're reverting this build to remediate impact.
Scope of impact: This issue may affect any user who's language is set to a non-English language and is using Outlook on the web or the new Outlook desktop client.
Root cause: A recent update is causing some parts of the UI in Outlook on the web and new Outlook desktop client to show in English instead of the intended, non-English language selected by users.
Next update by: Saturday, November 15, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Nov 14 13:53:57 2025 |
|---|
| Description: | Title: Users may see some parts of the UI in English instead of their non-English selected language
User impact: Users may see some parts of the UI in English instead of their non-English selected language.
Current status: We're investigating a potential issue where users with non-English languages selected as their default language may see some parts of Outlook on the web and the new Outlook experience in English, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1173754 - Users may see that composed text is rendered in a different font once sent in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 15 11:30:00 2025 |
|---|
| End Time: | Fri Nov 14 13:36:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Nov 14 16:18:54 2025 |
|---|
| Root Cause: | A recent service update to facilitate additional fonts contained a code error and caused Microsoft Teams to incorrectly assign the font, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 14 15:58:05 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may have seen that composed text was rendered in a different font once sent in Microsoft Teams.
More info: Users reported that impact was occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seemed to be specific to text using SimSun fonts.
Final status: We confirmed our fix deployment saturated across the entire affected infrastructure and remediated impact.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may have been affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
End time: Friday, November 14, 2025, at 6:36 PM UTC
Root cause: A recent service update to facilitate additional fonts contained a code error and caused Microsoft Teams to incorrectly assign the font, which resulted in impact.
Next steps:
- We're reviewing our service update processes to better inform how we can detect code errors and prevent similar incidents from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 12 17:04:11 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: We’ve determined that the deployment of our fix has reached 25 percent of the remaining affected infrastructure and we’ll continue to monitor it’s progress to confirm an estimation for its completion when available.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Friday, November 14, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Nov 11 15:56:29 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: While the fix has completed release to most environments, we've encountered a release blocker within a subset of infrastructure which is preventing further rollout. We're working to isolate the cause of the blockage and will provide an updated remediation timeline once available.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Wednesday, November 12, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Nov 10 14:45:20 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: We’ve confirmed reports from some affected users that this issue is resolved, and we’re continuing to monitor the fix deployment to ensure that it reaches all affected users to fully resolve this problem.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Tuesday, November 11, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 13:24:22 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: We've begun deploying our fix to the affected infrastructure, and we anticipate the deployment will complete by our next scheduled communications update.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Estimated time to resolve: We anticipate the fix will complete deployment by Monday, November 10, 2025, at 8:00 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Monday, November 10, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 20 13:54:14 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: We've completed development and validation of a fix to address the code error, and we're now preparing for deployment. We anticipate this fix will complete deployment in early November 2025. We'll provide an updated timeline as one becomes available.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Friday, November 7, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Oct 16 14:10:43 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Impact seems to be specific to text using SimSun fonts.
Current status: We've identified that a recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact. We're in the process of developing a fix and expect to have a remediation timeline by the next scheduled communications update.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Start time: Monday, September 15, 2025, at 3:30 PM UTC
Root cause: A recent service update to facilitate additional fonts contains a code error causing Microsoft Teams to incorrectly assign the font, resulting in impact.
Next update by: Monday, October 20, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Oct 16 11:29:11 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Current status: We're analyzing the composing box code base to determine why the font is being changed once sent to Microsoft Teams. This analysis will help us to determine our next troubleshooting steps to isolate a potential root cause of impact.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Next update by: Thursday, October 16, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Oct 16 11:09:15 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
More info: Users report that impact is occurring on the Microsoft Teams web client (Version: 25227.203.3915.2444) and the desktop client (Version: 25255.703.3978.7153).
Current status: We're reviewing data within support cases to verify our understanding of the current impact scenario and to determine our next troubleshooting steps.
Scope of impact: Any user sending SimSun font text from Microsoft Teams web client version 25227.203.3915.2444 and desktop client version 25255.703.3978.7153 may be affected.
Next update by: Thursday, October 16, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 10:43:47 2025 |
|---|
| Description: | Title: Users may see that composed text is rendered in a different font once sent in Microsoft Teams
User impact: Users may see that composed text is rendered in a different font once sent in Microsoft Teams.
Current status: We're investigating a potential issue in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1185063 - Some users may be unable to successfully enroll some new Android devices into Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 17:45:00 2025 |
|---|
| End Time: | Thu Nov 13 19:00:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Nov 14 00:34:10 2025 |
|---|
| Root Cause: | A network authentication component misconfiguration was causing the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 14 00:19:57 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll some new Android devices into Microsoft Intune
User impact: Users may be unable to successfully enroll some new Android devices into Microsoft Intune.
More info: This issue specifically affected users who attempted to enroll AOSP (Android Open Source Project) or Android Personal Work Profile devices.
Affected users may have also experienced device check-in failures for any Android device.
Final status: The impacted infrastructure has been fully restarted and after an extended period of time of monitoring the service health telemetry, we’ve confirmed that impact has been remediated.
Scope of impact: Some users who were attempting to enroll some Android devices into Microsoft Intune may have been impacted.
Start time: Monday, November 3, 2025, at 10:45 PM UTC
End time: Friday, November 14, 2025, at 2:30 AM UTC
Root cause: A network authentication component misconfiguration was causing the impact.
Next steps:
- We’re reviewing the network authentication component misconfiguration to determine how it was introduced so we can ensure issues like this aren’t replicated.
This is the final update for the event.
|
|---|
|
| Time: | Thu Nov 13 20:32:20 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll some new Android devices into Microsoft Intune
User impact: Users may be unable to successfully enroll some new Android devices into Microsoft Intune.
More info: This issue specifically affects users attempting to enroll AOSP (Android Open Source Project) or Android Personal Work Profile devices.
Affected users may also experience device check-in failures for any Android device.
Current status: We're continuing to restart the impacted infrastructure to ensure our fix is successfully applied and saturated. We've observed significant improvements in internal telemetry and expect the majority of users are already experiencing remediation. We anticipate the remaining impacted users will receive the fix and be able to successfully enroll their new devices by our next scheduled update.
Scope of impact: Some users who are attempting to enroll some Android devices into Microsoft Intune may be impacted.
Start time: Monday, November 3, 2025, at 10:45 PM UTC
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Friday, November 14, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Nov 13 17:44:02 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll some new Android devices into Microsoft Intune
User impact: Users may be unable to successfully enroll some new Android devices into Microsoft Intune.
More info: This issue specifically affects users attempting to enroll AOSP (Android Open Source Project) or Android Personal Work Profile devices.
Affected users may also experience device check-in failures for any Android device.
Current status: Our mitigation testing has proven successful, and we're rebooting the affected infrastructure to remediate impact and will provide a mitigation timeline once one is available.
Scope of impact: Some users who are attempting to enroll some Android devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Friday, November 14, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Nov 13 13:58:16 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll some new Android devices into Microsoft Intune
User impact: Users may be unable to successfully enroll some new Android devices into Microsoft Intune.
More info: This issue specifically affects users attempting to enroll AOSP (Android Open Source Project) or Android Personal Work Profile devices.
Affected users may also experience device check-in failures for any Android device.
Current status: We've updated the Title and User impact sections as further review has confirmed enrollment of Android Personal Work Profile devices is also impacted. We've additionally updated the More info section of this communication as the error codes noted were specific to AOSP devices.
Our previous manual mitigation efforts were unsuccessful in remediating the impact, and we're testing an alternative mitigation within a subset of the affected infrastructure prior to broad deployment.
Scope of impact: Some users who are attempting to enroll some new Android devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Friday, November 14, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 21:49:36 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: Our efforts to manually apply the mitigation to the affected infrastructure are ongoing as we continue to investigate the aforementioned errors which are halting the expedition of our remediation efforts.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Thursday, November 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 20:22:24 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: Our efforts to manually apply the mitigation to the affected infrastructure are ongoing, but we're experiencing suboptimal delays through this method. We're thoroughly investigating the errors that we're still seeing in the service to understand why they’re persisting and determine our next steps to expedite this ongoing mitigation.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Thursday, November 13, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 18:56:41 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: Our efforts to manually apply the mitigation to the affected infrastructure are ongoing. In parallel, we're determining whether there are any viable options to expedite this process and remediate the issue.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Thursday, November 13, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 17:01:11 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: Our manual application of the mitigation to the affected infrastructure is progressing and we’re monitoring the service health telemetry to ensure our efforts are alleviating impact as expected.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Thursday, November 13, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 14:36:13 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: We're observing the rate of failures beginning to decrease as we continue to manually apply the mitigation to the affected sections of infrastructure. We'll continue to monitor service health telemetry as our mitigation efforts progress to ensure the impact is fully remediated.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Wednesday, November 12, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 12:34:55 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: We've developed and are manually applying a mitigation to safely address the authentication component misconfiguration in the affected environment.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing the impact.
Next update by: Wednesday, November 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 10:27:02 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: We're progressing with our review of mitigation options to safely mitigate impact.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing impact to occur.
Next update by: Wednesday, November 12, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 08:32:17 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: We're continuing to review our mitigation options to help identify the best path to impact resolution.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing impact to occur.
Next update by: Wednesday, November 12, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 06:27:47 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll non-Microsoft Teams AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Users may also experience device check-in failures.
Current status: We’ve determined that a network authentication component misconfiguration is causing impact to occur. We're reviewing our mitigation options to identify the best path to impact resolution.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Root cause: A network authentication component misconfiguration is causing impact to occur.
Next update by: Wednesday, November 12, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 01:25:16 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new Microsoft Teams AOSP devices into Microsoft Intune.
Users who are attempting to enroll non-Microsoft Teams AOSP devices into Microsoft Intune may encounter a 20018 or 20019 error and be asked to factory reset.
Current status: We’re continuing our analysis of the aforementioned materials to familiarize ourselves with the underlying cause of impact in order to cultivate our troubleshooting steps.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Next update by: Wednesday, November 12, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 00:05:47 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
More info: Affected users may encounter a 20018 or 20019 error and be forced to sign out when attempting to enroll new AOSP devices into Microsoft Intune.
Current status: We're reviewing service side telemetry, an internal reproduction of impact, and network trace logs provided by a subset of users to familiarize ourselves with the underlying cause of impact.
Scope of impact: Some users who are attempting to enroll new AOSP devices into Microsoft Intune may be impacted.
Next update by: Wednesday, November 12, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Nov 11 23:43:04 2025 |
|---|
| Description: | Title: Some users may be unable to successfully enroll new AOSP (Android Open Source Project) devices into Microsoft Intune
User impact: Some users may be unable to successfully enroll new AOSP devices into Microsoft Intune.
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1183800 - Some users may experience delays in loading images and attachments in Exchange Online email messages
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 11:31:00 2025 |
|---|
| End Time: | Thu Nov 13 13:15:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 13 13:52:35 2025 |
|---|
| Root Cause: | A recent update to an authentication component of attachment logging introduced a regression which was causing the portion of service infrastructure responsible for loading signature add-in images to operate in a suboptimal state. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 13 13:52:35 2025 |
|---|
| Description: | Title: Some users may experience delays in loading images and attachments in Exchange Online email messages
User impact: Users may have experienced delays in loading images and attachments in Exchange Online email messages.
More info: Delays may have been up to ten seconds. Some users' signature add-in images may have also been affected.
Final status: We’ve confirmed that our fix deployment has reached the vast majority of the affected environment and determined from monitoring service telemetry that this issue is no longer occurring.
Scope of impact: Some users may have experienced delays in loading images and attachments in Exchange Online email messages.
Start time: Monday, November 3, 2025, at 4:31 PM UTC
End time: Thursday, November 13, 2025, at 6:15 PM UTC
Root cause: A recent update to an authentication component of attachment logging introduced a regression which was causing the portion of service infrastructure responsible for loading signature add-in images to operate in a suboptimal state.
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: | Tue Nov 11 14:07:51 2025 |
|---|
| Description: | Title: Some users may experience delays in loading images and attachments in Exchange Online email messages
User impact: Users may experience delays in loading images and attachments in Exchange Online email messages.
More info: Delays may be up to ten seconds. Some users' signature add-in images may also be affected.
Current status: Our internal service telemetry continues to report improved service performance as our reversion removes the offending code regression and repairs the affected service infrastructure. Our updated reversion timelines estimates that the process will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Some users may experience delays in loading images and attachments in Exchange Online email messages. This section may be updated as our investigation continues.
Start time: Monday, November 3, 2025, at 4:31 PM UTC
Root cause: A recent update to an authentication component of attachment logging introduced a regression which is causing the portion of service infrastructure responsible for loading signature add-in images to operate in a suboptimal state.
Next update by: Thursday, November 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Nov 10 15:51:41 2025 |
|---|
| Description: | Title: Some users may experience delays in loading images and attachments in Exchange Online email messages
User impact: Users may experience delays in loading images and attachments in Exchange Online email messages.
More info: Delays may be up to ten seconds. Some users' signature add-in images may also be affected.
Current status: The reversion of the offending update is nearing completion, and our service health telemetry indicates that the portion of affected infrastructure is now operating in an optimal state. We're continuing to monitor the completion of the reversion before testing with a subset of users whether the impact is remediated.
Scope of impact: Some users may experience delays in loading images and attachments in Exchange Online email messages. This section may be updated as our investigation continues.
Start time: Monday, November 3, 2025, at 4:31 PM UTC
Root cause: A recent update to an authentication component of attachment logging introduced a regression which is causing the portion of service infrastructure responsible for loading signature add-in images to operate in a suboptimal state.
Next update by: Tuesday, November 11, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Nov 7 17:41:17 2025 |
|---|
| Description: | Title: Some users may experience delays in loading images and attachments in Exchange Online email messages
User impact: Users may experience delays in loading images and attachments in Exchange Online email messages.
More info: Delays may be up to ten seconds. Some users' signature add-in images may also be affected.
Current status: We've confirmed the reversion of the impacting update has completed across 41 percent of the affected environment, and we'll provide a timeline for remediation as one becomes available.
Scope of impact: Some users may experience delays in loading images and attachments in Exchange Online email messages. This section may be updated as our investigation continues.
Start time: Monday, November 3, 2025, at 4:31 PM UTC
Root cause: A recent update to an authentication component of attachment logging introduced a regression which is resulting in impact.
Next update by: Monday, November 10, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Nov 7 15:39:22 2025 |
|---|
| Description: | Title: Some users may experience delays of up to ten seconds loading signature add-in images in Exchange Online
User impact: Users may experience delays of up to ten seconds loading signature add-in images in Exchange Online.
Current status: We've determined that a recent update to an authentication component of attachment logging introduced a regression which is resulting in impact. We're reverting this update to resolve the issue.
Scope of impact: Some users may experience delays of up to ten seconds loading images in Exchange Online. This section may be updated as our investigation continues.
Start time: Monday, November 3, 2025, at 4:31 PM UTC
Root cause: A recent update to an authentication component of attachment logging introduced a regression which is resulting in impact.
Next update by: Monday, November 10, 2025, at 10:30 PM UTC
|
|---|
|
SP1184976 - Users may be unable to utilize site search in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Tue Nov 11 10:00:00 2025 |
|---|
| End Time: | Wed Nov 12 19:30:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Search and Delve |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Nov 13 00:04:13 2025 |
|---|
| Root Cause: | A recent build deployment contained a change which caused issues with the functionality of the site search bar. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 13 00:04:13 2025 |
|---|
| Description: | Title: Users may be unable to utilize site search in SharePoint Online
User impact: Users may have been unable to utilize site search in SharePoint Online.
More info: When users attempted to interact with the site search box, the box may not have reacted or performed any searches.
Final status: We've confirmed the full deployment of our fix and verified with a subset of impacted users that impact is remediated.
Scope of impact: This issue may have affected users attempting to perform site searches in SharePoint Online.
Start time: Tuesday, November 11, 2025, at 3:00 PM UTC
End time: Thursday, November 13, 2025, at 12:30 PM UTC
Root cause: A recent build deployment contained a change which caused issues with the functionality of the site search bar.
Next steps:
- We're reviewing our update testing and validation methods to better identify issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 11 18:29:53 2025 |
|---|
| Description: | Title: Users may be unable to utilize site search in SharePoint Online
User impact: Users may be unable to utilize site search in SharePoint Online.
More info: When users attempt to interact with the site search box, the box may not react or perform any searches.
Current status: We've completed the fix preparation and deployed our fix to roll back the impacting change to remediate impact for all users. The change is saturating throughout the affected environment, and users may begin to experience relief as it progresses. We anticipate the issue will be resolved by our next scheduled communication update.
Scope of impact: This issue may affect users attempting to perform site searches in SharePoint Online.
Start time: Tuesday, November 11, 2025, at 3:00 PM UTC
Root cause: A recent build deployment contained a change which broke functionality of the site search bar.
Next update by: Thursday, November 13, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Nov 11 18:10:03 2025 |
|---|
| Description: | Title: Users may be unable to utilize site search in SharePoint Online
User impact: Users may be unable to utilize site search in SharePoint Online.
More info: When users attempt to interact with the site search box, the box may not react or perform any searches.
Current status: We've identified that a recent change resulted in impact. While we confirm additional details about the change, including what it was intended to do and why it resulted in impact, we're preparing a fix to roll back this change to remediate impact for users.
Scope of impact: This issue may affect users attempting to perform site searches in SharePoint Online.
Next update by: Wednesday, November 12, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Nov 11 17:53:51 2025 |
|---|
| Description: | Title: Users may be unable to utilize site search in SharePoint Online
User impact: Users may be unable to utilize site search in SharePoint Online.
More info: When users attempt to interact with the site search box, the box may not react or perform any searches.
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.
|
|---|
|
PB1185289 - Some users experience failures with artifacts that rely on SQL connections in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 12 10:57:48 2025 |
|---|
| End Time: | Wed Nov 12 21:15:00 2025 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 12 22:47:10 2025 |
|---|
| Root Cause: | A portion of the SQL infrastructure was performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 22:33:24 2025 |
|---|
| Description: | Title: Some users experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe and East US experienced failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: Affected users may have experienced degraded performance or failures when using Dataflows Gen2, executing SQL queries, or creating or opening artifacts that rely on SQL connections in Microsoft Fabric.
Final status: After restarting affected portions of infrastructure and rebalancing the service across the affected environment, the failures have been eliminated and we've confirmed through monitoring that the impact was remediated.
Scope of impact: Impact may have occurred for some users in North Europe and East US who may have experienced failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Start time: Wednesday, November 12, 2025, at 2:40 PM UTC
End time: Thursday, November 13, 2025, at 2:15 AM UTC
Root cause: A portion of the SQL infrastructure was performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric.
Next steps:
- We're continuing our analysis of loading balancing and request behavior on the affected infrastructure to better understand the cause of the SQL connectivity issues, which will help us in preventing the impact from reoccurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 12 20:28:24 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: Affected users may experience degraded performance or failures when using Dataflows Gen2, executing SQL queries, or creating or opening artifacts that rely on SQL connections in Microsoft Fabric.
Current status: We're continuing our analysis of the load behavior and network latency within the affected service during requests to help us determine our next troubleshooting steps.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Start time: Wednesday, November 12, 2025, at 2:40 PM UTC
Root cause: A portion of the SQL infrastructure is performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric.
Next update by: Thursday, November 13, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 18:03:08 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: Affected users may experience degraded performance or failures when using Dataflows Gen2, executing SQL queries, or creating or opening artifacts that rely on SQL connections in Microsoft Fabric.
Current status: We’ve restarted the affected infrastructure; however, this action didn't restore service functionality. We’re now investigating load behavior and network latency within the affected service to identify an appropriate mitigation pathway to restore SQL connectivity and resolve the problem successfully.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Start time: Wednesday, November 12, 2025, at 2:40 PM UTC
Root cause: A portion of the SQL infrastructure is performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric.
Next update by: Thursday, November 13, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 15:28:49 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: Affected users may experience degraded performance or failures when using Dataflows Gen2, executing SQL queries, or creating or opening artifacts that rely on SQL connections in Microsoft Fabric.
Current status: We’re continuing our efforts to restart the affected infrastructure as a remediation action and are monitoring progress to ensure this action successfully restores service functionality.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Start time: Wednesday, November 12, 2025, at 2:40 PM UTC
Root cause: A portion of the SQL infrastructure is performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric.
Next update by: Wednesday, November 12, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 13:16:59 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: This issue also impacts the ability to create or open artifacts that rely on SQL connections within Microsoft Fabric.
Current status: We’ve identified that a portion of the SQL infrastructure is performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric. To remediate this issue, we’re restarting the affected infrastructure and monitoring progress to ensure this action successfully resolves the problem.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Start time: Wednesday, November 12, 2025, at 2:40 PM UTC
Root cause: A portion of the SQL infrastructure is performing below acceptable thresholds, resulting in failures when creating or opening artifacts within Microsoft Fabric.
Next update by: Wednesday, November 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 12:32:18 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
More info: This issue also impacts the ability to create or open artifacts that rely on SQL connections within Microsoft Fabric.
Current status: We’re continuing our review of service telemetry and SQL error logs to determine the source of the problem and identify a mitigation path.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Next update by: Wednesday, November 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Nov 12 11:27:54 2025 |
|---|
| Description: | Title: Some users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric
User impact: Users in North Europe experience failures with artifacts that rely on SQL connections in Microsoft Fabric.
Current status: Our monitoring system has identified impact where users may experience failures when using Dataflows Gen2 in Microsoft Fabric. We're reviewing service telemetry to isolate the source of this issue and identify appropriate mitigation actions.
Scope of impact: Impact may occur for some users in North Europe who may experience failures when using Dataflows Gen2 in Microsoft Fabric or when attempting to create or open artifacts that rely on SQL connections in Microsoft Fabric.
Next update by: Wednesday, November 12, 2025, at 5:30 PM UTC
|
|---|
|
CP1185345 - Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 12 15:18:51 2025 |
|---|
| End Time: | Wed Nov 12 19:55:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 12 21:27:13 2025 |
|---|
| Root Cause: | A recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot app catalog and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 21:26:34 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may have been unable to access suggested agents from the Copilot Agent Store page.
Final status: We've completed deploying the additional fix and monitored our internal telemetry to confirm that access to the service is restored and the impact is remediated.
Scope of impact: Any user that attempted to view suggested agents from the Copilot Agent Store page was impacted.
Start time: Wednesday, November 12, 2025, at 5:30 PM UTC
End time: Thursday, November 13, 2025, at 12:55 AM UTC
Root cause: A recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot app catalog and resulted in impact.
Next steps:
- We're further reviewing the recent service update to the portion of the Copilot infrastructure to understand what specifically caused the code regression to be introduced, and to prevent similar impact scenarios from reoccurring in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 12 20:16:29 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may be unable to access suggested agents from the Copilot Agent Store page.
Current status: We've identified an additional deployment is needed to ensure the healthy version of the Copilot app is fixed, and functionality to the service is restored. We've initiated the deployment of the secondary fix and anticipate it will be fully deployed and the impact remediated by our next scheduled update.
Scope of impact: Any user attempting to view suggested agents from the Copilot Agent Store page is impacted.
Start time: Wednesday, November 12, 2025, at 5:30 PM UTC
Root cause: A recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot app catalog, resulting in impact.
Next update by: Thursday, November 13, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 18:32:01 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may be unable to access suggested agents from the Copilot Agent Store page.
Current status: We've redeployed the healthy version of the Copilot app catalog and we're monitoring service health telemetry to ensure the impact has been remediated.
Scope of impact: Any user attempting to view suggested agents from the Copilot Agent Store page is impacted.
Start time: Wednesday, November 12, 2025, at 5:30 PM UTC
Root cause: A recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot app catalog, resulting in impact.
Next update by: Thursday, November 13, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Nov 12 16:50:16 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may be unable to access suggested agents from the Copilot Agent Store page.
Current status: We've identified that a recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot App catalog, resulting in impact. We've reverted the offending service update, and we're re-deploying the previous healthy version of the Copilot app catalog to fully resolve the issue.
Scope of impact: Any user attempting to view suggested agents from the Copilot Agent Store page is impacted.
Start time: Wednesday, November 12, 2025, at 5:30 PM UTC
Root cause: A recent service update to a portion of the Copilot infrastructure introduced a code regression into the Copilot app catalog, resulting in impact.
Next update by: Thursday, November 13, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 15:40:55 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may be unable to access suggested agents from the Copilot Agent Store page.
Current status: We're reviewing service logs to identify the root cause of this event, so we can determine our next troubleshooting steps.
Scope of impact: Any user attempting to view suggested agents from the Copilot Agent Store page is impacted.
Next update by: Wednesday, November 12, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 15:24:23 2025 |
|---|
| Description: | Title: Users may be unable to access suggested agents from the Microsoft Copilot (Microsoft 365) Agent Store page
User impact: Users may be unable to access suggested agents from the Copilot Agent Store page.
Current status: We're investigating a potential issue with users being unable to access suggested agents from the Copilot Agent Store page, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP1135993 - Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 10 20:00:00 2025 |
|---|
| End Time: | Wed Nov 12 19:30:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 12 20:28:55 2025 |
|---|
| Root Cause: | A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and this resulted in failures. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 20:28:55 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users couldn't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users were unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admins with access to PowerShell or Graph API could use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Final status: We monitored the service telemetry and confirmed that impact has been successfully remediated by our actions.
Scope of impact: Your organization was affected by this event, and some users couldn't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
End time: Thursday, November 13, 2025, at 12:30 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and this resulted in failures.
Next steps:
- We're continuing to monitor the affected infrastructure closely to assess whether additional changes can be made to more quickly detect and resolve similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 29 20:20:01 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admins with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Current status: Our ongoing monitoring has observed positive trends in the reduction of new affected users. We're continuing to run our fix to restore service for newly affected users. Users and admins with access to PowerShell or Graph API can still use the provided article above to manually setup class notebooks.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and is resulting in failures.
Next update by: Thursday, November 13, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Oct 15 21:00:46 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
Current status: We're continuing our efforts to monitor telemetry to identify any additional affected users and run our fix to restore service.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and is resulting in failures.
Next update by: Thursday, October 30, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Oct 8 20:14:18 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admins with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-micros…
Current status: Our efforts to monitor telemetry to identify any additional affected users and run our fix to restore service for them is ongoing.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and is resulting in failures.
Next update by: Thursday, October 16, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Oct 1 19:56:41 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admins with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-micros…
Current status: We’re continuing to monitor the telemetry to identify any additional affected users so that we can run our fix operation to repair them.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and is resulting in failures.
Next update by: Thursday, October 9, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Sep 24 20:01:11 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admins with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Current status: We're continuing our efforts of monitoring telemetry while we continue to identify additional affected users and run the fix operation to repair them.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, became degraded and is resulting in failures.
Next update by: Thursday, October 2, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Sep 17 20:58:06 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admin with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Current status: Our monitoring of the telemetry is ongoing as we continue to identify affected users and run the fix operation to repair them.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, has became degraded, causing failures.
Next update by: Thursday, September 25, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Sep 10 20:13:10 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admin with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Current status: We’re monitoring telemetry as we continue to identify affected users and run the fix operation to repair them. We recommend users follow the article in the More info section to complete any provisioning through PowerShell and Microsoft Graph as we continue to resolve this issue.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, has became degraded, causing failures.
Next update by: Thursday, September 18, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Sep 3 20:12:51 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users and admin with access to PowerShell or Graph API can use the following article to manually setup class notebooks: https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec
Current status: We're monitoring our telemetry to identify affected users and are running a fix operation to repair them. We continue to recommend users follow the article in the More info section to complete any provisioning through PowerShell and Microsoft Graph.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, has became degraded, causing failures.
Next update by: Thursday, September 11, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 2 20:24:17 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users should follow this article (https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec) for provisioning through PowerShell and Microsoft Graph.
Current status: We're continuing to monitor our telemetry for affected users and are running a fix operation to repair them. In the meantime, we recommend following the article in the More Info section to complete any needed provisioning through PowerShell and Microsoft Graph.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, has became degraded, causing failures.
Next update by: Thursday, September 4, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Aug 25 21:43:48 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
While we're focused on remediation, users should follow this article (https://support.microsoft.com/en-us/topic/provisioning-classes-at-scale-using-powershell-and-microsoft-graph-3428f18f-ff38-4c46-a696-3318e463cbec) for provisioning through PowerShell and Microsoft Graph.
Current status: The partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignment operations has been repaired. Users will no longer encounter issues when performing the operations. We're continuing to monitor our telemetry and are running a fix operation to restore any users who we identify are impacted by the issue. In the meantime, we recommend following the article in the More Info section to complete any needed provisioning through PowerShell and Microsoft Graph.
Scope of impact: Your organization is affected by this event, and some users can't create or publish Assignments or create a class in a notebook in a team.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote and Assignments rely on for creating and publishing assignments, as well as class notebooks creation, has became degraded, causing failures.
Next update by: Wednesday, September 3, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Aug 18 21:32:56 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
More info: In addition, users are unable to create notebooks in Microsoft OneNote Class Notebook.
Current status: Our review of the telemetry indicates that a partner service that Microsoft OneNote relies on for Create and Publish Assignment operations is degraded, causing failures for some users. We anticipate that the repairs to the partner service will take some time to complete. In the meantime, we're manually running a fix operation to restore the Create and Publish Assignment functionality to the impacted infrastructure. Affected users may see the impact remediate as the fix operation propagates over time.
Scope of impact: Your organization is affected by this event, and some users can't perform Create and Publish Assignment operations in Microsoft OneNote.
Start time: Monday, August 11, 2025, at 12:00 AM UTC
Root cause: A partner service that Microsoft OneNote relies on for Create and Publish Assignment operations is degraded, causing failures.
Next update by: Tuesday, August 26, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Aug 15 18:27:15 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
Current status: Our review of telemetry identified an exception we suspect may be related to the impact, and we're gathering service logs to further investigate this possibility before we develop our next steps towards mitigation.
Scope of impact: Your organization is affected by this event, and some users can't perform Create and Publish Assignment operations in Microsoft OneNote.
Next update by: Tuesday, August 19, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Aug 15 17:01:20 2025 |
|---|
| Description: | Title: Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team
User impact: Users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team.
Current status: We're reviewing service telemetry to isolate any errors or exceptions which may help identify the root cause of impact. We’re also assessing if operations outside of Create Assignment are impacted.
Scope of impact: Your organization is affected by this event, and some users can't perform Create and Publish Assignment operations in Microsoft OneNote.
Next update by: Friday, August 15, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Aug 15 16:33:51 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft OneNote
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft OneNote and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1181369 - Users may see issues accessing some Microsoft 365 services and portals
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Oct 29 11:41:00 2025 |
|---|
| End Time: | Wed Oct 29 20:05:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Nov 12 15:06:54 2025 |
|---|
| Root Cause: | An inadvertent configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting Microsoft services dependent on AFD for global content delivery. More information is provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 15:06:54 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 5 19:41:06 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Oct 31 19:29:02 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 22:11:03 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may have seen issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios included, but may not have been limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Final status: After extended monitoring, we confirmed that impact stemming from the Azure configuration change has been resolved.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may have been impacted.
Start time: Wednesday, October 29, 2025, 3:41 PM UTC
End time: Thursday, October 30, 2025, at 12:05 AM UTC
Root cause: An inadvertent configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting Microsoft services dependent on AFD for global content delivery. More information 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 first update will be provided by Friday, November 28.
|
|---|
|
| Time: | Wed Oct 29 20:58:03 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: We've confirmed that service health has largely recovered; however, user reports of impact haven't yet returned to pre-incident thresholds. We're continuing to monitor the service to ensure full recovery.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Thursday October 30, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Oct 29 19:26:42 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: Our configuration deployment and traffic rebalancing is showing steady service health improvement for scenarios listed in the "More info" section of this communication. Some users may experience residual impact until availability fully recovers. We're monitoring for an extended period to ensure service health is restored as expected.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Thursday October 30, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 15:59:57 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: We've edited the Title, User impact, and More info sections of this communication to align with our current understanding of the affected scenarios.
Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: We've completed the deployment of a healthy configuration and we're continuing our active traffic balancing efforts as well as monitoring corresponding service telemetry to ensure widespread recovery.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Wednesday, October 29, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 15:11:53 2025 |
|---|
| Description: | Current status: We've completed the deployment of the previous healthy configuration and are actively rebalancing traffic across healthy infrastructure to actualize recovery across the affected services.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 14:35:04 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: We've edited the Title, User impact, and More info sections of this communication to align with our current understanding of the affected scenarios.
Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Purview, Microsoft Defender, Microsoft Power Apps and Microsoft Intune functions. For example, Microsoft Defender for Cloud Apps policies may not be applying as expected.
- Access to security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls.
Current status: We're deploying a previous healthy configuration to the affected portions of infrastructure to resolve this issue. This is being done in tandem with efforts to rebalance traffic across healthy infrastructure to achieve recovery as quickly as possible.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Wednesday, October 29, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 13:50:57 2025 |
|---|
| Description: | Current status: We've halted the rollout of the impacting configuration change. We're continuing our efforts to route service traffic away from affected infrastructure where the change was already applied, to recover service availability as quickly as possible. In parallel, we're working to revert the impacted infrastructure to a previous healthy state.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 13:17:13 2025 |
|---|
| Description: | Title: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services
User impact: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services.
More info: Additionally, admins are reporting issues when attempting to access some Microsoft Entra, Microsoft Purview, Microsoft Defender, Microsoft Power Apps and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook.
Current status: We've identified a recent configuration change to a portion of Azure infrastructure which we believe is causing the impact. We're pursuing multiple remediation strategies, including moving traffic away from the impacted infrastructure and blocking the offending change. We'll provide an estimated recovery time as soon as possible.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, October 29, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 12:36:49 2025 |
|---|
| Description: | Current status: We're rerouting affected traffic to alternate healthy infrastructure as a near-term resolution while our investigation into the source of the issue is ongoing.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 12:28:13 2025 |
|---|
| Description: | Current status: We're reviewing network and hosting infrastructure health to determine why the service is in an unhealthy state.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 12:21:29 2025 |
|---|
| Description: | Title: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services
User impact: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services.
More info: Additionally, admins are reporting issues when attempting to access some Microsoft Purview and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook.
Current status: We're reviewing reports of an issue impacting Microsoft Azure and Microsoft 365 services, including impact to the Microsoft 365 admin center and other services, including but not limited to those described in the more info section of this communication. We're reviewing corresponding service telemetry to isolate the cause of the issue and determine our next troubleshooting steps.
Scope of impact: Any users attempting to access Microsoft 365 services may be impacted.
Next update by: Wednesday, October 29, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 12:07:49 2025 |
|---|
| Description: | Title: We're receiving reports of a potential problem impacting Microsoft 365 services
User impact: We're looking into a potential problem impacting 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.
|
|---|
|
TM1185128 - Admins may be unable to change the meeting logo or theme image in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 27 20:00:00 2025 |
|---|
| End Time: | Wed Nov 12 07:35:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 12 12:06:51 2025 |
|---|
| Root Cause: | A recent service update to the Microsoft Teams admin center introduced a code regression which resulted in the inability to change the meeting logo or image. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 12:06:51 2025 |
|---|
| Description: | Title: Admins may be unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins may have been unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins may have been unable to change the logo or theme image for meetings via the Microsoft Teams admin center.
Admins may have seen the error message "We can't update your images. Try again."
As an alternative, admins could have connected to the “MicrosoftTeams PowerShell” module and used the "CsTeamsMeetingBrandingPolicy" cmdlet to control the meeting appearance. For more information, please see:
"MicrosoftTeams PowerShell module" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/
"Set-CsTeamsMeetingBrandingPolicy" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy
Final status: We've confirmed that our fix has saturated throughout the affected infrastructure and that impact is remediated after subsequent testing.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may have been impacted.
Start time: Tuesday, October 28, 2025, at 12:00 AM UTC
End time: Wednesday, November 12, 2025, at 12:35 PM UTC
Root cause: A recent service update to the Microsoft Teams admin center introduced a code regression which resulted in the inability to change the meeting logo or image.
Next steps:
- We're reviewing our service update processes to better understand how this regression wasn't detected so we can prevent similar service incidents from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 12 10:59:23 2025 |
|---|
| Description: | Title: Admins may be unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins may be unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins may be unable to change the logo or theme image for meetings via the Microsoft Teams admin center.
Admins may see the error message "We can't update your images. Try again."
As a workaround, admins can connect to the “MicrosoftTeams PowerShell” module and use the "CsTeamsMeetingBrandingPolicy" cmdlet to control the meeting appearance. For more information, please see:
"MicrosoftTeams PowerShell module" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/
"Set-CsTeamsMeetingBrandingPolicy" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy
Current status: We're continuing to monitor our fix deployment throughout the affected infrastructure, which we estimate will finish within the next eight hours.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may be impacted.
Start time: Tuesday, October 28, 2025, at 12:00 AM UTC
Estimated time to resolve: The issue should be resolved within the next eight hours.
Root cause: A recent standard service update to the Microsoft Teams admin center has inadvertently introduced a code regression, which is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 07:21:27 2025 |
|---|
| Description: | Title: Admins may be unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins may be unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins may be unable to change the logo or theme image for meetings via the Microsoft Teams admin center.
Admins may see the error message "We can't update your images. Try again."
As a workaround, admins can connect to the MicrosoftTeams PowerShell module and use the "CsTeamsMeetingBrandingPolicy" cmdlet to control the meeting appearance. For more information, please see:
"MicrosoftTeams PowerShell module" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/
"Set-CsTeamsMeetingBrandingPolicy" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy
Current status: Deployment of the fix is ongoing and expected to complete by Wednesday, November 12, 2025.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may be impacted.
Start time: Tuesday, October 28, 2025, at 12:00 AM UTC
Estimated time to resolve: Wednesday, November 12, 2025
Root cause: A recent standard service update to the Microsoft Teams admin center has inadvertently introduced a code regression, which is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 05:26:49 2025 |
|---|
| Description: | Title: Admins may be unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins may be unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins may be unable to change the logo or theme image for meetings via the Microsoft Teams admin center.
Admins may see the error message "We can't update your images. Try again."
As a workaround, admins can connect to the MicrosoftTeams PowerShell module and use the "CsTeamsMeetingBrandingPolicy" cmdlet to control the meeting appearance. For more information, please see:
"MicrosoftTeams PowerShell module" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/
"Set-CsTeamsMeetingBrandingPolicy" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy
Current status: We’ve successfully validated the fix, and deployment is now in progress. We expect the rollout to complete later today and will confirm when it is finished.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may be impacted.
Start time: Tuesday, October 28, 2025, at 12:00 AM UTC
Estimated time to resolve: Wednesday, November 12, 2025
Root cause: A recent standard service update to the Microsoft Teams admin center has inadvertently introduced a code regression, which is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 04:18:17 2025 |
|---|
| Description: | Title: Admins may be unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins may be unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins may be unable to change the logo or theme image for meetings via the Microsoft Teams admin center.
Admins may see the error message "We can't update your images. Try again."
As a workaround, admins can connect to the MicrosoftTeams PowerShell module and use the "CsTeamsMeetingBrandingPolicy" cmdlet to control the meeting appearance. For more information, please see:
"MicrosoftTeams PowerShell module" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/
"Set-CsTeamsMeetingBrandingPolicy" - https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy
Current status: We’ve determined that a recent standard service update to the Microsoft Teams admin center inadvertently introduced a code regression, resulting in impact. We’re developing and validating a fix before being deployed. We’ll share updates on the deployment as they become available.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may be impacted.
Root cause: A recent standard service update to the Microsoft Teams admin center has inadvertently introduced a code regression, which is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Nov 12 03:41:00 2025 |
|---|
| Description: | Title: Admins are unable to change the meeting logo or theme image in Microsoft Teams
User impact: Admins are unable to change the meeting logo or theme image in Microsoft Teams.
More info: Admins see the error message “We can't update your images. Try again.”
Current status: We’re reviewing HTTP Archive (HAR) files alongside API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: All admins attempting to change the meeting logo or theme image via the Microsoft Teams admin center may be impacted.
Next update by: Wednesday, November 12, 2025, at 10:30 AM UTC
|
|---|
|
DZ1185191 - Some users were experiencing unexpected changes in alert product names in Microsoft Sentinel
| Status: | serviceRestored |
|---|
| Start Time: | Tue Nov 11 22:15:00 2025 |
|---|
| End Time: | Wed Nov 12 07:50:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Sentinel |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Nov 12 09:05:59 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently introduced a code regression that changed the product names of some alerts in Microsoft Sentinel. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 12 09:05:08 2025 |
|---|
| Description: | Title: Some users were experiencing unexpected changes in alert product names in Microsoft Sentinel
User impact: Users were experiencing unexpected changes in alert product names in Microsoft Sentinel.
More info: The product names of some alerts changed unexpectedly.
Final status: We’ve completed the rollback and have confirmed that the issue is fully mitigated. All new alerts are now being ingested with the correct (previous) product names. However, the mitigation does not retroactively change or update alerts that were already ingested with the unexpected product names during the impact period; those remain unchanged.
Scope of impact: Some users of Microsoft Sentinel in West Europe were impacted.
Start time: Wednesday, November 12, 2025, at 3:15 AM UTC
End time: Wednesday, November 12, 2025, at 12:50 PM UTC
Root cause: A recent standard service update inadvertently introduced a code regression that changed the product names of some alerts in Microsoft Sentinel.
Next steps:
- We're reviewing our deployment procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 12 07:55:09 2025 |
|---|
| Description: | Title: Some users are experiencing unexpected changes in alert product names in Microsoft Sentinel
User impact: Users are experiencing unexpected changes in alert product names in Microsoft Sentinel.
More info: The product names of some alerts changed unexpectedly.
Current status: We’ve determined that a recent standard service update inadvertently introduced a code regression, resulting in unplanned changes to the product names for certain alerts in Microsoft Sentinel. A rollback of the affected release is now in progress and is expected to complete within the hour, which is expected to fully resolving the issue.
Scope of impact: Some users of Microsoft Sentinel in West Europe are impacted.
Start time: Wednesday, November 12, 2025, at 3:15 AM UTC
Root cause: A recent standard service update inadvertently introduced a code regression that changed the product names of some alerts in Microsoft Sentinel.
Next update by: Wednesday, November 12, 2025, at 3:00 PM UTC
|
|---|
|
OD1182545 - Some users may be unable to share content to Microsoft OneDrive from iPhone 17
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 1 01:56:00 2025 |
|---|
| End Time: | Mon Nov 10 13:00:00 2025 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 11 14:06:41 2025 |
|---|
| Root Cause: | A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which prevented users with iPhone 17 devices on iOS 26.0.1 from sharing content to Microsoft OneDrive. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 11 14:06:41 2025 |
|---|
| Description: | Title: Some users may be unable to share content to Microsoft OneDrive from iPhone 17
User impact: Users may have been unable to share content to Microsoft OneDrive from iPhone 17.
More info: Impact was specific to iOS 26.0.1. Users were returned the following error message stating, "Your organization will remove its data for this account because a jailbroken or rooted device was detected." Please note that the error was erroneous and there was no risk of data being removed.
Final status: We've confirmed with a subset of previously affected users that updating their OneDrive app from the app store has resolved the issue. Affected users must have the latest version to receive the fix and remediate impact.
Scope of impact: Impact was to some users that were trying to share content to Microsoft OneDrive from iPhone 17 (iOS version 26.0.1).
Start time: Wednesday, October 1, 2025, at 5:56 AM UTC
End time: Monday, November 10, 2025, at 6:00 PM UTC
Root cause: A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which prevented users with iPhone 17 devices on iOS 26.0.1 from sharing content to Microsoft OneDrive.
Next steps:
- We're reviewing our standard update procedures to ensure similar misconfigurations are caught and addressed ahead of deployment to prevent this from happening in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 11 13:17:51 2025 |
|---|
| Description: | Title: Some users may be unable to share content to Microsoft OneDrive from iPhone 17
User impact: Users may be unable to share content to Microsoft OneDrive from iPhone 17.
More info: Impact is specific to iOS 26.0.1. Users are returned the following error message stating, "Your organization will remove its data for this account because a jailbroken or rooted device was detected." Please note that the error is erroneous and there is no risk of data being removed.
Current status: While we've confirmed the updated version has completed its deployment and all affected users can update their OneDrive app from the app store, we're reaching out to affected users to confirm that the fix has remediated this issue.
Scope of impact: Impact is to some users that are trying to share content to Microsoft OneDrive from iPhone 17 (iOS version 26.0.1). This section may be updated as the incident progresses.
Start time: Wednesday, October 1, 2025, at 5:56 AM UTC
Root cause: A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which prevents users with iPhone 17 devices on iOS 26.0.1 from sharing content to Microsoft OneDrive.
Next update by: Wednesday, November 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 10 12:53:04 2025 |
|---|
| Description: | Title: Some users may be unable to share content to Microsoft OneDrive from iPhone 17
User impact: Users may be unable to share content to Microsoft OneDrive from iPhone 17.
More info: Impact is specific to iOS 26.0.1. Users are returned the following error message stating, "Your organization will remove its data for this account because a jailbroken or rooted device was detected." Please note that the error is erroneous and there is no risk of data being removed.
Current status: We've validated that the updated iOS client is set to release today, Monday, November 10, 2025, and we are working with some affected users to validate if impact is resolved after updating to the latest iOS client.
Scope of impact: Impact is to some users that are trying to share content to Microsoft OneDrive from iPhone 17 (iOS version 26.0.1). This section may be updated as the incident progresses.
Start time: Wednesday, October 1, 2025, at 5:56 AM UTC
Root cause: A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which prevents users with iPhone 17 devices on iOS 26.0.1 from sharing content to Microsoft OneDrive.
Next update by: Tuesday, November 11, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 13:54:34 2025 |
|---|
| Description: | Title: Some users may be unable to share content to Microsoft OneDrive from iPhone 17 due to false-positive jailbreak detection
User impact: Users may be unable to share content to Microsoft OneDrive from iPhone 17 due to false-positive jailbreak detection.
More info: Users are returned the following error message stating, "Your organization will remove its data for this account because a jailbroken or rooted device was detected."
Impact is specific to iOS 26.0.1.
Current status: We've completed validation of an updated iOS client and we expect it to be available for affected users by the next scheduled update.
Scope of impact: Impact is to some users who may be unable to share content to Microsoft OneDrive from iPhone 17 (iOS version 26.0.1) due to false-positive jailbreak detection.
Start time: Wednesday, October 1, 2025, at 5:56 AM UTC
Root cause: A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which resulted in users with devices on iOS 26.0.1 to receive false-positive jailbreak detection alerts.
Next update by: Monday, November 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 13:15:33 2025 |
|---|
| Description: | Title: Some users may be unable to share content to Microsoft OneDrive from iPhone 17 due to false-positive jailbreak detection
User impact: Users may be unable to share content to Microsoft OneDrive from iPhone 17 due to false-positive jailbreak detection.
More info: Users are returned the following error message stating, "Your organization will remove its data for this account because a jailbroken or rooted device was detected."
Impact is specific to iOS 26.0.1.
Current status: We've validated that a recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which resulted in users with devices on iOS 26.0.1 to receive false-positive jailbreak detection alerts. We've created a code fix to resolve the issue which we're testing in our internal testing environment. We expect that this validation will complete by our next update at which point we'll submit it for App Store approval.
Scope of impact: Impact is to some users who may be unable to share content to Microsoft OneDrive from iPhone 17 (iOS version 26.0.1) due to false-positive jailbreak detection.
Root cause: A recent update to our Intune Software Development Kit (SDK) introduced a misconfiguration which resulted in users with devices on iOS 26.0.1 to receive false-positive jailbreak detection alerts.
Next update by: Tuesday, November 4, 2025, at 7:30 PM UTC
|
|---|
|
IT1184773 - Some users were unable to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Fri Nov 7 12:00:00 2025 |
|---|
| End Time: | Tue Nov 11 06:42:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 11 08:05:39 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently contained a code regression, which was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 11 07:57:41 2025 |
|---|
| Description: | Title: Some users were unable to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune
User impact: Users were unable to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune.
More info: As a workaround, users could leverage the Intune Graph to create the store app.
Final status: We've determined that a recent standard service update inadvertently contained a code regression, which was resulting in impact. We've reverted the offending change and confirmed after monitoring service telemetry that impact has been remediated.
Scope of impact: Impact was specific to some users attempting to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune.
Start time: Friday, November 7, 2025, at 5:00 PM UTC
End time: Tuesday, November 11, 2025, at 11:42 AM UTC
Root cause: A recent standard service update inadvertently contained a code regression, which was resulting in impact.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 11 04:58:00 2025 |
|---|
| Description: | Title: Some users may be unable to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune
User impact: Users may be unable to search for any Microsoft Store app or create a new Microsoft Store app from Microsoft Intune.
More info: As a workaround, users can leverage the Intune Graph to create the store app.
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 some users attempting to search for any Microsoft Store app or create a new Microsoft Store app from the Microsoft Intune console may be impacted.
Next update by: Tuesday, November 11, 2025, at 4:00 PM UTC
|
|---|
|
MV1177163 - Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
| Status: | serviceRestored |
|---|
| Start Time: | Sat Sep 6 20:00:00 2025 |
|---|
| End Time: | Tue Oct 28 20:00:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 10 14:21:21 2025 |
|---|
| Root Cause: | A service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values were being calculated incorrectly. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 10 14:21:21 2025 |
|---|
| Description: | Title: Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users may have seen inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact was specific to Copilot Assisted Hours and the Copilot Assisted Value metrics which were part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics didn’t necessarily reflect actual declines. The issue was related to a calculation issue in the "Meeting hours summarized or recapped" metric, which was currently in Public Preview.
The following documentation contains information pertaining to an alternative calculation method to validate impact metrics for September and October 2025: https://learn.microsoft.com/en-us/viva/insights/org-team-insights/alternate-calculation-total-meeting-hours-summarized-recapped
Final status: We've completed our monitoring period and validated that users are able to see accurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app for November 2025. We want to reiterate that users will need to utilize the alternative calculation method provided in the "More info" section of this communication to calculate impact metrics for September and October 2025.
Scope of impact: Your organization was affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app were impacted.
Start time: Sunday, September 7, 2025, at 12:00 AM UTC
End time: Wednesday, October 29, 2025, at 12:00 AM UTC
Root cause: A service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values were being calculated incorrectly.
Next steps:
- We're analyzing the offending service change to determine why the potential for impact wasn't caught during our update testing and validation phases. This analysis will help us to improve the quality and resilience of our future updates and to ensure similar impact doesn't occur in future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 30 16:00:06 2025 |
|---|
| Description: | Title: Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours and the Copilot Assisted Value metrics which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics don’t necessarily reflect actual declines. The issue is related to a calculation issue in the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
The following documentation contains information pertaining to an alternative calculation method to validate impact metrics for September and October 2025: https://learn.microsoft.com/en-us/viva/insights/org-team-insights/alternate-calculation-total-meeting-hours-summarized-recapped
Current status: We’ve finalized an alternative calculation method which will allow users to estimate the Total meeting hours summarized or recapped values for September and October 2025, and recalculate their Copilot Assisted Hours and Value figures, and documentation on this process is provided in the "More info" section of this communication. Simultaneously, we've completed deployment of our fix to ensure the values will be calculated accurately starting in November 2025, and we're continuing to monitor impact metrics until November 10, 2025.
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Start time: Sunday, September 7, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate our monitoring period to be completed by the time of our next scheduled update on Monday, November 10, 2025, at 9:00 PM UTC.
Root cause: A service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values are being calculated incorrectly.
Next update by: Monday, November 10, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Oct 23 18:20:07 2025 |
|---|
| Description: | Title: Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours and the Copilot Assisted Value metrics which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to a calculation issue in the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We're continuing to develop an alternative calculation method to allow users to ascertain the accurate values for September and October 2025, which will be provided through the following documentation once complete: https://learn.microsoft.com/en-us/viva/insights/org-team-insights/copilot-dashboard#known-underreporting-issue-with-copilot-assisted-hours-metrics
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Root cause: A service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values are being calculated incorrectly.
Next update by: Thursday, October 30, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 17:22:31 2025 |
|---|
| Description: | Title: Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours and the Copilot Assisted Value metrics which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to a calculation issue in the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We've identified that a service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values are being calculated incorrectly. We're developing a fix to ensure the values will be calculated accurately and expect the deployment will complete by the end of October 2025. While this fix will correct the calculations moving forward, it may not correct the impacted metrics for September 2025 and October 2025. We're developing an alternative calculation method to allow users to ascertain the accurate values for September and October, and it will be provided through the following documentation once complete: https://learn.microsoft.com/en-us/viva/insights/org-team-insights/copilot-dashboard#known-underreporting-issue-with-copilot-assisted-hours-metrics
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Root cause: A service change introduced an issue with the "Meeting hours summarized or recapped" metric, in which the values are being calculated incorrectly.
Next update by: Thursday, October 23, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 21:19:49 2025 |
|---|
| Description: | Title: Some users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours or the Copilot Assisted Values which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to calculations of the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We’re developing a solution to remediate the impact, and once this process has completed, we’ll begin deploying it to affected users. Based on our current estimations, we anticipate deployment will be complete by Saturday, October 25, 2025. In parallel, we’re continuing with our review of the calculation of the "Meeting hours summarized or recapped" metric to determine why the Copilot Assisted Hours for the Copilot Assisted Values are inaccurate.
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Next update by: Wednesday, October 22, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 19:16:36 2025 |
|---|
| Description: | Title: Some users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours or the Copilot Assisted Values which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to calculations of the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We're continuing to review the calculation of the "Meeting hours summarized or recapped" metric so that we can figure out why the Copilot Assisted Hours for the Copilot Assisted Values are inaccurate and develop a remediation strategy.
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Next update by: Wednesday, October 22, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Oct 21 18:23:38 2025 |
|---|
| Description: | Title: Some users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours or the Copilot Assisted Values which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to calculations of the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We're reviewing the calculation of the "Meeting hours summarized or recapped" metric to help us understand why the Copilot Assisted Hours for the Copilot Assisted Values are inaccurate, so that we can determine a strategy to remediate the impact.
Scope of impact: Your organization is affected by this event, and some users attempting to view Copilot Assisted Hours for the Copilot Assisted Values on the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app are impacted.
Next update by: Tuesday, October 21, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 18:01:08 2025 |
|---|
| Description: | Title: Some users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app
User impact: Users see inaccurate metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app.
More info: Impact is specific to Copilot Assisted Hours or the Copilot Assisted Values which are part of the Impact tab in the Copilot Dashboard within the Microsoft Viva Insights web app and started in early September 2025. The unexpected declines in these metrics doesn't necessarily reflect actual declines. The issue is related to calculations of the "Meeting hours summarized or recapped" metric, which is currently in Public Preview.
Current status: We're investigating a potential issue with the Copilot dashboard in the Microsoft Viva Insights web app and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1184299 - Users using the "Create" video function in Microsoft Copilot (Microsoft 365) with a PowerPoint file observed failures
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 5 16:00:00 2025 |
|---|
| End Time: | Mon Nov 10 01:30:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 10 04:25:33 2025 |
|---|
| Root Cause: | A recent update meant to improve service security inadvertently affected image processing capabilities, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 10 04:22:39 2025 |
|---|
| Description: | Title: Users using the "Create" video function in Microsoft Copilot (Microsoft 365) with a PowerPoint file observed failures
User impact: Users utilizing the "Create" video function in Copilot with a PowerPoint file may have seen failures.
More info: When attempting to create a video using a PowerPoint file, the creation attempt failed and users may have seen an error message stating, "Something went wrong".
Final status: We’ve deployed a fix to roll back the offending change and, after monitoring service telemetry, confirmed that the impact has been fully remediated.
Scope of impact: Any user utilizing the "Create" function in Copilot using a PowerPoint file may have been impacted.
Start time: Wednesday, November 5, 2025, at 9:00 PM UTC
End time: Monday, November 10, 2025, at 6:30 AM UTC
Root cause: A recent update meant to improve service security inadvertently affected image processing capabilities, which led to impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 10 00:39:00 2025 |
|---|
| Description: | Title: Users utilizing the "Create" video function in Microsoft Copilot (Microsoft 365) with a PowerPoint file may see failures
User impact: Users utilizing the "Create" video function in Copilot with a PowerPoint file may see failures.
More info: When attempting to create a video using a PowerPoint file, the creation attempt fails and users may see an error message stating, "Something went wrong".
Current status: We received reports of an issue with the Copilot create feature and after some internal testing, we confirmed that a recent update meant to improve service security inadvertently affected image processing capabilities, leading to impact. We've deployed a fix to roll back the change to more expediently remediate impact and provide additional time to develop and deploy a long-term fix.
Scope of impact: Any user utilizing the "Create" function in Copilot using a PowerPoint file may be impacted.
Start time: Wednesday, November 5, 2025, at 9:00 PM UTC
Root cause: A recent update meant to improve service security inadvertently affected image processing capabilities, leading to impact.
Next update by: Monday, November 10, 2025, at 10:00 AM UTC
|
|---|
|
TM1181326 - Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 6 19:04:00 2025 |
|---|
| End Time: | Fri Nov 7 13:23:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Nov 7 17:26:07 2025 |
|---|
| Root Cause: | A recent standard service update contained a code regression, which was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Nov 7 17:26:07 2025 |
|---|
| Description: | Title: Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
User impact: Users may have experienced intermittent crashes when launching the Microsoft Teams desktop app on Windows.
Final status: We've completed our reversion of the impacting change and confirmed impact was successfully remediated.
Scope of impact: Impact was specific to some users attempting to launch the Microsoft Teams desktop app on Windows.
Start time: Monday, October 6, 2025, at 11:04 PM UTC
End time: Friday, November 7, 2025, at 6:23 PM UTC
Root cause: A recent standard service update contained a code regression, which was resulting in impact.
Next steps:
- We're reviewing our standard service update testing and validation procedures to identify opportunities to improve regression detection and better prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 29 17:43:31 2025 |
|---|
| Description: | Title: Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
User impact: Users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows.
Current status: Our reversion of the change is underway, and we anticipate the process will complete by the time of our next update.
Scope of impact: Impact is specific to some users attempting to launch the Microsoft Teams desktop app on Windows.
Start time: Monday, October 6, 2025, at 11:04 PM UTC
Root cause: A recent standard service update contains a code regression, which is resulting in impact.
Next update by: Saturday, November 8, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 13:42:38 2025 |
|---|
| Description: | Title: Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
User impact: Users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows.
Current status: We're progressing with our change reversion process and will provide an updated timeline for the completed process and the remediation of impact once it has become available.
Scope of impact: Impact is specific to some users attempting to launch the Microsoft Teams desktop app on Windows.
Start time: Monday, October 6, 2025, at 11:04 PM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Wednesday, October 29, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 10:03:20 2025 |
|---|
| Description: | Title: Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
User impact: Users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We're reverting the offending change to remediate impact and expect to provide a remediation timeline by our next update.
Scope of impact: Impact is specific to some users attempting to launch the Microsoft Teams desktop app on Windows.
Start time: Monday, October 6, 2025, at 11:04 PM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Wednesday, October 29, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 08:43:47 2025 |
|---|
| Description: | Title: Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows
User impact: Users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows.
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 attempting to launch the Microsoft Teams desktop app on Windows.
Next update by: Wednesday, October 29, 2025, at 3:00 PM UTC
|
|---|
|
PL1154805 - Users may be unable to access the Planner component in Microsoft Loop
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 1 20:00:00 2025 |
|---|
| End Time: | Fri Oct 31 13:00:00 2025 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 6 17:04:54 2025 |
|---|
| Root Cause: | An update to the authentication enforcement that some Planner component in Loop features relied on resulted in authentication failures, causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 6 16:51:57 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may have been unable to access the Planner component in Loop.
More info: The Planner component in Loop was disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features could still be accessed directly through the Microsoft Planner web app.
Final status: We've completed deployment of the fix to the affected environments and after monitoring the service, we've verified that that this action has successfully resolved the issue.
Scope of impact: Any user accessing the Planner component in Loop may have been affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
End time: Friday, October 31, 2025, at 5:00 PM UTC
Root cause: An update to the authentication enforcement that some Planner component in Loop features relied on resulted in authentication failures, causing impact.
Next steps:
- We’re investigating how the update to authentication enforcement, which certain Planner components within Loop features relied on, resulted in authentication failures, to help prevent this problem from occurring again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 30 17:00:04 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We’re continuing to monitor the progression of our fix deployment to the impacted environment. Based on our current estimate, deployment is expected to complete by Friday, November 14, 2025. We’ll continue to provide updates on our timeline to mitigation as deployment progresses.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate this issue will be fully resolved by Friday, November 14, 2025.
Root cause: An update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, November 6, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 16:44:56 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We've initiated deployment of our fix to the impacted environment and we anticipate our fix to reach all affected users by Friday, November 7, 2025. We aim to provide updates on our timeline to mitigation as deployment continues.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Root cause: An update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, October 30, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 17:47:57 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We've completed our internal validations and are preparing to deploy the fix to the impacted environment. We anticipate it may take approximately three weeks for the saturation to fully complete, with our estimate being around Friday, November 7, 2025.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Root cause: An update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, October 23, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 9 16:18:16 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We're expecting our internal validations will have completed, and that an estimated timeline for the deployment of our fix and the remediation of impact will be available by our next scheduled update.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, October 16, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 2 17:12:03 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: The process of validating the efficacy of the fix to ensure it operates as expected by remediating the impact is ongoing and taking more time than initially expected. We’re assessing our options to implement the fix as soon as possible and will provide an updated estimate for it reaching affected users by our next scheduled update.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, October 9, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Sep 25 17:16:44 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We're validating the efficacy of the fix in remediating the impact prior to deployment and we anticipate the validation process will complete by our next scheduled communications update. Our current estimation is that this will be fully deployed by mid-October 2025.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Start time: Tuesday, September 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, October 2, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Sep 17 20:12:22 2025 |
|---|
| Description: | Title: Users may be unable to access the Planner component in Microsoft Loop
User impact: Users may be unable to access the Planner component in Loop.
More info: The Planner component in Loop is disabled due to authentication failures with some features related to a recent authentication change. Planner task lists and other features can still be accessed directly through the Microsoft Planner web app.
Current status: We've identified an issue in which users may be unable to access the Planner component in Loop and determined that a recent update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact. As a precaution, we've disabled the Planner component in Loop until we've deployed a fix for the authentication enforcement failures. We're validating a fix in our internal test environment, and we'll provide an estimated timeline for deployment once this is complete.
Scope of impact: Any user accessing the Planner component in Loop may be affected.
Root cause: A recent update to the authentication enforcement that some Planner component in Loop features rely on resulted in authentication failures, causing impact.
Next update by: Thursday, September 25, 2025, at 10:00 PM UTC
|
|---|
|
TM1180817 - Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 20 20:00:00 2025 |
|---|
| End Time: | Thu Nov 6 01:20:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 6 01:41:30 2025 |
|---|
| Root Cause: | A recent update to the Microsoft Teams app was not properly downloading the necessary native app bundles, resulting in incompatibilities and launch failures. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Nov 6 01:41:30 2025 |
|---|
| Description: | Title: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
User impact: Android users experienced app launch failures or delays for native app bundles in the Microsoft Teams mobile app.
More info: This specifically affected users who recently updated their Microsoft Teams mobile app to the latest version of 1416/1.0.0.2025193702.
Users could have worked around this issue by relaunching the app bundles multiple times, as the specific app should have successfully launched within a few attempts once the associated app bundles were also upgraded to this latest version of Microsoft Teams. Users may have also been able to avoid this launch failure by signing out and in of the Teams mobile app again, which should have cleared the associated cache of these app bundles.
Final status: The deployment of the fix completed to the affected environment and we validated that the updated version of the Microsoft Teams mobile app with the fix is available for all users.
Scope of impact: Your organization was affected by this event, and all Android users who had recently updated their Microsoft Teams mobile app to the latest version may have experienced app launch failures or delays for native app bundles in the Teams mobile app.
Start time: Tuesday, October 21, 2025, at 12:00 AM UTC
End time: Thursday, November 6, 2025, at 6:20 AM UTC
Root cause: A recent update to the Microsoft Teams app was not properly downloading the necessary native app bundles, resulting in incompatibilities and launch failures.
Next steps:
- We're analyzing our service update procedures for the Microsoft Teams mobile app to better identify similar issues prior to their deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 31 01:32:55 2025 |
|---|
| Description: | Title: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
User impact: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app.
More info: This specifically affects users who recently updated their Microsoft Teams mobile app to the latest version of 1416/1.0.0.2025193702.
Users can work around this issue by relaunching the app bundles multiple times, as the specific app should successfully launch within a few attempts once the associated app bundles are also upgraded to this latest version of Microsoft Teams. Users may also be able to avoid this launch failure by signing out and in of the Teams mobile app again, which should clear the associated cache of these app bundles.
Current status: We developed and validated a fix to the update the Microsoft Teams mobile app version which will allow the correct app bundles to download. The deployment of the fix is underway to the affected environment and we're monitoring the progress to ensure that the impact is remediated.
Scope of impact: Your organization is affected by this event, and all Android users who have recently updated their Microsoft Teams mobile app to the latest version may experience app launch failures or delays for native app bundles in the Teams mobile app.
Start time: Tuesday, October 21, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Teams app is not properly downloading the necessary native app bundles, resulting in incompatibilities and launch failures.
Next update by: Thursday, November 6, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Oct 28 02:11:47 2025 |
|---|
| Description: | Title: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
User impact: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app.
More info: This specifically affects users who recently updated their Microsoft Teams mobile app to the latest version of 1416/1.0.0.2025193702.
Users can work around this issue by relaunching the app bundles multiple times, as the specific app should successfully launch within a few attempts once the associated app bundles are also upgraded to this latest version of Microsoft Teams. Users may also be able to avoid this launch failure by signing out and in of the Teams mobile app again, which should clear the associated cache of these app bundles.
Current status: We're developing a fix to update the Microsoft Teams mobile app version and allow the correct app bundles to download. The development and validation of the fix is expected to take some time to complete. We anticipate having an update on the status of the fix by the next scheduled update time.
Scope of impact: Your organization is affected by this event, and all Android users who have recently updated their Microsoft Teams mobile app to the latest version may experience app launch failures or delays for native app bundles in the Teams mobile app.
Start time: Tuesday, October 21, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Teams app is not properly downloading the necessary native app bundles, resulting in incompatibilities and launch failures.
Next update by: Friday, October 31, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Oct 27 14:59:49 2025 |
|---|
| Description: | Title: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
User impact: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app.
More info: This specifically affects users who recently updated their Microsoft Teams mobile app to the latest version of 1416/1.0.0.2025193702.
Users can work around this issue by relaunching the app bundles multiple times, as the specific app should successfully launch within a few attempts once the associated app bundles are also upgraded to this latest version of Microsoft Teams. Users may also be able to avoid this launch failure by signing out and in of the Teams mobile app again, which should clear the associated cache of these app bundles.
Current status: We suspect this issue is due to native app bundles in the Microsoft Teams mobile not getting upgraded alongside the Microsoft Teams app itself, which causes incompatible app versions to attempt launch. We're developing a possible fix that addresses when these app bundles are upgraded as part of the Microsoft Teams mobile app upgrade process, to confirm the root cause and to avoid these outdated app versions from being called prior to fully updating.
Scope of impact: Your organization is affected by this event, and all Android users who have recently updated their Microsoft Teams mobile app to the latest version may experience app launch failures or delays for native app bundles in the Teams mobile app.
Next update by: Tuesday, October 28, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Oct 27 14:18:08 2025 |
|---|
| Description: | Title: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app
User impact: Android users may experience app launch failures or delays for native app bundles in the Microsoft Teams mobile app.
More info: This specifically affects users who recently updated their Microsoft Teams mobile app to the latest version of 1416/1.0.0.2025193702.
Current status: We're investigating a potential issue in which Android users who have recently updated their Microsoft Teams app to the latest version from the Play Store may experience app launch failures or delays for native apps, like Microsoft Viva Connections. We'll provide an update within 30 minutes.
|
|---|
|
MV1183146 - Users may be unable to post messages or view feeds in Viva Engage.
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 5 08:07:00 2025 |
|---|
| End Time: | Wed Nov 5 12:38:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Nov 6 01:35:52 2025 |
|---|
| Root Cause: | A portion of the infrastructure serving users posting messages and viewing feeds was operating below expected performance thresholds, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 5 13:47:14 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may have experienced issues when posting messages or viewing feeds in Viva Engage.
Final status: The configuration changes we applied have successfully decreased error rates and returned the service to a healthy state.
Scope of impact: This issue may have affected a subset of infrastructure hosted in North America; however, this infrastructure serves organizations and users globally.
Start time: Wednesday, November 5, 2025, at 1:07 PM UTC
End time: Wednesday, November 5, 2025, at 5:38 PM UTC
Root cause: A portion of the infrastructure serving users posting messages and viewing feeds was operating below expected performance thresholds, leading to impact.
Next steps:
- We're monitoring the service and conducting a thorough investigation into this underlying root cause to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Nov 5 12:37:49 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may experience issues when posting messages or viewing feeds in Viva Engage.
Current status: We've implemented several configuration changes to decrease error rates. Telemetry shows that these actions have resulted in a drop in error rates. We're continuing to monitoring the service and review recent changes and telemetry to identify the underlying root cause.
Scope of impact: This issue affects a subset of infrastructure hosted in North America, however, this infrastructure serves organizations globally.
Next update by: Wednesday, November 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 11:15:02 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may experience issues when posting messages or viewing feeds in Viva Engage.
Current status: Telemetry shows error rates have increased again. We're currently implementing some configuration changes to optimize memory usage and we're reviewing options to add additional processing throughput. Furthermore, we're continuing to review telemetry and error logs to isolate the source of the issue.
Scope of impact: This issue affects a subset of infrastructure hosted in North America, however, this infrastructure serves organizations globally.
Next update by: Wednesday, November 5, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 11:00:22 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may experience issues when posting messages or viewing feeds in Viva Engage.
Current status: We've observed a significant drop in error rates and monitoring the situation closely. We're also continuing to analyze telemetry to understand the root cause of the issue and plan next steps.
Scope of impact: This issue affects a subset of infrastructure hosted in North America, however, this infrastructure serves organizations globally.
Next update by: Wednesday, November 5, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 09:45:22 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may experience issues when posting messages or viewing feeds in Viva Engage.
Current status: From initial analysis, we've identified higher than normal errors rates. We’re analyzing telemetry further to determine the root cause and define a remediation plan.
Scope of impact: This issue affects a subset of infrastructure hosted in North America, however, this infrastructure serves organizations globally.
Next update by: Wednesday, November 5, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 09:15:00 2025 |
|---|
| Description: | Title: Users may be unable to post messages or view feeds in Viva Engage.
User impact: Some users may experience issues when posting messages or viewing feeds in Viva Engage.
More info: This issue affects message posting and feed updates within Viva Engage for a subset set of users in North America.
Current status: We’re investigating a potential issue causing message posting and feed viewing failures in Viva Engage, and we’re checking for impact to your organisation. We'll provide an update within 30 minutes.
|
|---|
|
CP1181486 - Users may have experienced issues when accessing m365.cloud.microsoft or portal.office.com
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Oct 29 17:30:00 2025 |
|---|
| End Time: | Thu Oct 30 00:21:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Nov 5 22:08:38 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 5 21:26:01 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Oct 31 21:34:43 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 30 00:45:49 2025 |
|---|
| Description: | Title: Users may have experienced issues when accessing m365.cloud.microsoft or portal.office.com
User impact: Users may have experienced issues when accessing m365.cloud.microsoft or portal.office.com.
More info: Users were redirected to an error page http://m365.cloud.microsoft/error. While we were investigating this issue, users could have navigated to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Final status: We identified a code issue within a recent change that led to impact, and we've subsequently corrected it to provide mitigation. We confirmed via internal testing, diagnostic data, and customer reports that the issue is resolved.
Scope of impact: This issue may have potentially impacted any user attempting to access http://m365.cloud.microsoft or portal.office.com. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America were affected.
Start time: Wednesday, October 29, 2025, 9:30 PM UTC
End time: Thursday, October 30, 2025, at 4:21 AM UTC
Preliminary root cause: A recent code change inadvertently caused issues when users attempted to access m365.cloud.microsoft or portal.office.com.
Next steps:
- For a more comprehensive list of next steps, please see the post incident report.
|
|---|
|
| Time: | Wed Oct 29 23:52:17 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Current status: While we previously observed an improvement to the service, error rates continue to show service degradation. Following further testing, we have ruled out the CDN as the source of the problem and we're continuing to rollback any recent service-side changes to restore service as quickly as possible.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 23:11:47 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Current status: We've initiated a rollback of the service to its last known good build. We are seeing improvement to service availability; however, the rollback has not completed, and we do not believe this is related to a recent deployment. We're still reviewing any relevant data to identify the underlying cause of the issue.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 22:41:33 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps as a potential solution in the interim.
Current status: We're continuing to review diagnostic data and tracing 404 errors related to service-to-CDN calls. We're analyzing data to determine if this issue is due to incorrect file paths or version placeholders in the CDN requests. In parallel, we're reviewing any recent change or deployment that occurred to the service as a troubleshooting step.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 22:02:37 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error.
Current status: We’re reviewing recent changes and available logging to help narrow down the cause of impact. We’ve confirmed impact may be affecting any user attempting to access the Office Home Pages.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 21:34:09 2025 |
|---|
| Description: | Title: Users may experience issues with the Microsoft Copilot (Microsoft 365) service
User impact: Users may experience issues with the Copilot service.
Current status: We’re reviewing recent changes and available logging to help narrow down the cause of impact. We’ve confirmed impact may be affecting any user attempting to access Copilot across multiple regions.
Scope of impact: This issue may potentially impact any user attempting to utilize the Copilot service. This information may be updated as our investigation continues.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 21:04:38 2025 |
|---|
| Description: | Title: Users may experience issues with the Microsoft Copilot (Microsoft 365) service in the Asia Pacific region
User impact: Users may experience issues with the Copilot service.
Current status: We're investigating a potential issue with the Copilot service and are checking the impact to our users. We'll provide an update within 30 minutes.
Scope of impact: This issue may potentially impact any user attempting to utilize the Copilot service in the Asia Pacific region based on our telemetry. This information may be updated as our investigation continues.
|
|---|
|
MO1181501 - Users may have experienced issues when accessing m365.cloud.microsoft or portal.office.com
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Oct 29 17:30:00 2025 |
|---|
| End Time: | Thu Oct 30 00:21:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Nov 5 22:08:00 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Nov 5 21:26:46 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Oct 31 21:35:24 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 30 00:45:12 2025 |
|---|
| Description: | Title: Users may experience issues when accessing m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing m365.cloud.microsoft or portal.office.com.
More info: Users were redirected to an error page http://m365.cloud.microsoft/error. While we were investigating this issue, users could have navigated to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Final status: We identified a code issue within a recent change that led to impact, and we've subsequently corrected it to provide mitigation. We confirmed via internal testing, diagnostic data, and customer reports that the issue is resolved.
Scope of impact: This issue may have potentially impacted any user attempting to access http://m365.cloud.microsoft or portal.office.com. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America were affected.
Start time: Wednesday, October 29, 2025, 9:30 PM UTC
End time: Thursday, October 30, 2025, at 4:21 AM UTC
Preliminary root cause: A recent code change inadvertently caused issues when users attempted to access m365.cloud.microsoft or portal.office.com.
Next steps:
- For a more comprehensive list of next steps, please see the post incident report.
|
|---|
|
| Time: | Thu Oct 30 00:05:06 2025 |
|---|
| Description: | Title: Users may experience issues when accessing m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Current status: While we previously observed an improvement to the service, error rates continue to show service degradation. Following further testing, we have ruled out the CDN as the source of the problem and we're continuing to rollback any recent service-side changes to restore service as quickly as possible.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 23:11:45 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps or m365.cloud.microsoft/search as a potential solution in the interim.
Current status: While we previously observed an improvement to the service, error rates continue to show service degradation. Following further testing, we have ruled out the CDN as the source of the problem and we're continuing to rollback any recent service-side changes to restore service as quickly as possible.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 22:41:36 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error. While we're investigating this issue, users may navigate to m365.cloud.microsoft/apps as a potential solution in the interim.
Current status: We're continuing to review diagnostic data and tracing 404 errors related to service-to-CDN calls. We're analyzing data to determine if this issue is due to incorrect file paths or version placeholders in the CDN requests. In parallel, we're reviewing any recent change or deployment that occurred to the service as a troubleshooting step.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 22:04:30 2025 |
|---|
| Description: | Title: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com
User impact: Users may experience issues when accessing the m365.cloud.microsoft or portal.office.com.
More info: Users will be redirected to an error page http://m365.cloud.microsoft/error.
Current status: We’re reviewing recent changes and available logging to help narrow down the cause of impact. We’ve confirmed impact may be affecting any user attempting to access the Office Home Pages.
Scope of impact: This issue may potentially impact any user attempting to access Office Home Pages. Specifically, users located in Australia, India, Japan, United States, Asia-Pacific, and South America may be affected.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
|
|---|
|
TM1182987 - Some users' shifts may be missing from the Shifts app in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 17:00:00 2025 |
|---|
| End Time: | Tue Nov 4 13:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 4 18:07:51 2025 |
|---|
| Root Cause: | A recent service change designed to add new functionality caused impact |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 4 18:07:51 2025 |
|---|
| Description: | Title: Some users' shifts may be missing from the Shifts app in Microsoft Teams
User impact: Users' shifts may have been missing from the Shifts app in Microsoft Teams.
Final status: We've identified a recent service change designed to add new functionality that caused impact. We've reversed the offending change and confirmed through service health monitoring that the impact is remediated. All shifts that were previously missing are available again. If users still not seeing their shift populate, they can refresh the shifts app by clicking the three dots in the far right corner and then selecting the refresh button from the Shifts app. Alternatively, users can sign out and sign back in to refresh their shifts.
Scope of impact: Some users attempting to view their shifts from the Shifts app in Microsoft teams may have been impacted.
Start time: Monday, November 3, 2025, at 10:00 PM UTC
End time: Tuesday, November 4, 2025, at 6:00 PM UTC
Root cause: A recent service change designed to add new functionality caused impact
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar issues with shifts in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 4 17:42:46 2025 |
|---|
| Description: | Title: Some users' shifts may be missing from the Shifts app in Microsoft Teams
User impact: Users' shifts may have been missing from the Shifts app in Microsoft Teams.
Current status: We've investigated a problem with the Shifts app in Microsoft Teams and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
TM1182837 - Users may be unable to view images that are uploaded through the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Sat Nov 1 01:00:00 2025 |
|---|
| End Time: | Tue Nov 4 13:26:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 4 17:36:58 2025 |
|---|
| Root Cause: | A recent configuration change, designed to update a backend protocol responsible for rendering images in the Microsoft Teams Windows client, introduced a code error that caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 4 16:58:12 2025 |
|---|
| Description: | Title: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client
User impact: Users may have been unable to paste or view images uploaded through the Microsoft Teams Windows desktop client.
Final status: We've completed reverting the impacting change and validated this has remediated impact using service telemetry.
Scope of impact: Impact was limited to a small subset of users attempting to view or paste any images that were uploaded through the Microsoft Teams Windows desktop client.
Start time: Saturday, November 1, 2025, at 5:00 AM UTC
End time: Tuesday, November 4, 2025, at 6:26 AM UTC
Root cause: A recent configuration change, designed to update a backend protocol responsible for rendering images in the Microsoft Teams Windows client, introduced a code error that caused impact.
Next steps:
- We're continuing our analysis of the impacting change to better understand the underlying cause of impact and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 4 14:31:22 2025 |
|---|
| Description: | Title: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client
User impact: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client.
Current status: We've completed deployment of our configuration change and have received feedback from a subset of affected users that the impact is remediated after restarting the Microsoft Teams desktop client. We're monitoring our service health telemetry for an extended period to ensure that the issue is fully resolved.
Scope of impact: Any user attempting to view any images that are uploaded through the Microsoft Teams desktop client may be impacted.
Root cause: A recent service change, designed to update a backend protocol responsible for rendering images in the Microsoft Teams client, introduced a code error that's causing impact.
Next update by: Tuesday, November 4, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Nov 4 13:50:22 2025 |
|---|
| Description: | Title: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client
User impact: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client.
Current status: Our gradual deployment process continues as initial validations in our testing have proven it to be effective. We'll provide an updated timeline to remediation as one becomes available.
Scope of impact: Any user attempting to view any images that are uploaded through the Microsoft Teams desktop client may be impacted.
Root cause: A recent service change, designed to update a backend protocol responsible for rendering the Microsoft Teams client, introduced a code change that's causing impact.
Next update by: Tuesday, November 4, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 11:26:07 2025 |
|---|
| Description: | Title: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client
User impact: Users may be unable to view images that are uploaded through the Microsoft Teams desktop client.
Current status: Our initial tests of our configuration change have continued to be successful. We've begun rolling out the fix gradually and we expect to complete the validations and deployment of the fix by the time of our next update.
Scope of impact: Any user attempting to view any images that are uploaded through the Microsoft Teams desktop client may be impacted.
Root cause: A recent service change, designed to update a backend protocol responsible for rendering the Microsoft Teams client, introduced a code change that's causing impact.
Next update by: Tuesday, November 4, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 09:26:18 2025 |
|---|
| Description: | Title: Users may be unable to view any images that are uploaded to the Microsoft Teams client
User impact: Users may be unable to view any images that are uploaded to the Microsoft Teams client.
Current status: We've confirmed with a sample of affected users that the fix mitigates impact after restarting the Microsoft Teams client. We're preparing to deploy the fix to a section of impacted infrastructure to again validate that the fix mitigates impact before deploying to the remaining affected infrastructure.
Scope of impact: Impact is specific to users attempting to view any images that are uploaded to the Microsoft Teams client.
Root cause: A recent code change is causing impact to occur.
Next update by: Tuesday, November 4, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 06:57:22 2025 |
|---|
| Description: | Title: Users may be unable to view any images that are uploaded to the Microsoft Teams client
User impact: Users may be unable to view any images that are uploaded to the Microsoft Teams client.
Current status: We've determined that a recent code change is causing impact to occur. We're testing a fix to confirm that this mitigates impact.
Scope of impact: Impact is specific to users attempting to view any images that are uploaded to the Microsoft Teams client.
Root cause: A recent code change is causing impact to occur.
Next update by: Tuesday, November 4, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 05:23:06 2025 |
|---|
| Description: | Title: Users may be unable to view any images that are uploaded to the Microsoft Teams client
User impact: Users may be unable to view any images that are uploaded to the Microsoft Teams client.
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 users attempting to view any images that are uploaded to the Microsoft Teams client.
Next update by: Tuesday, November 4, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 05:08:58 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.
|
|---|
|
TM1181149 - Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 16 14:14:00 2025 |
|---|
| End Time: | Tue Nov 4 16:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 4 17:05:00 2025 |
|---|
| Root Cause: | A recent service update contained a misconfiguration and was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 4 17:05:00 2025 |
|---|
| Description: | Title: Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
User impact: Users may have not received the toast notification when another user answered a call from a Microsoft Teams call queue.
Final status: Our deployment of the fix to address the misconfiguration introduced in a recent service update has completed. After a brief monitoring period, we've validated that impact is resolved.
Scope of impact: Some users that were members of a call queue may have been impacted.
Start time: Thursday, October 16, 2025, at 6:14 PM UTC
End time: Tuesday, November 4, 2025, at 9:30 PM UTC
Root cause: A recent service update contained a misconfiguration and was causing impact.
Next steps:
- We're analyzing the offending service update to determine why the potential for impact wasn't caught during our update testing and validation phases. This analysis will help us to improve the quality and resilience of our future updates and to ensure similar impact doesn't occur in future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 3 17:14:08 2025 |
|---|
| Description: | Title: Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
User impact: Users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue.
Current status: We've initiated deployment of our fix and we anticipate our deployment to complete prior to our next scheduled update, which will allow us to validate if impact is mitigated at that time.
Scope of impact: Some users that are members of a call queue may be impacted.
Start time: Thursday, October 16, 2025, at 6:14 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by the time of our next scheduled update on Wednesday, November 5, 2025, at 12:00 AM UTC.
Root cause: A recent service update contains a misconfiguration and is causing impact.
Next update by: Wednesday, November 5, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Oct 28 16:28:20 2025 |
|---|
| Description: | Title: Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
User impact: Users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue.
Current status: We're continuing to validate the efficacy of our fix and expect that deployment will begin during the first week of November.
Scope of impact: Some users that are members of a call queue may be impacted.
Start time: Thursday, October 16, 2025, at 6:14 PM UTC
Root cause: A recent service update contains a misconfiguration and is causing impact.
Next update by: Tuesday, November 4, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Oct 28 16:00:41 2025 |
|---|
| Description: | Title: Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
User impact: Users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue.
Current status: We've identified a recent service update that contains a misconfiguration and is causing impact. We've developed a new build which corrects the misconfiguration, and we're verifying its efficacy before deploying.
Scope of impact: Some users that are members of a call queue may be impacted.
Start time: Thursday, October 16, 2025, at 6:14 PM UTC
Root cause: A recent service update contains a misconfiguration and is causing impact.
Next update by: Tuesday, October 28, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Oct 28 15:40:41 2025 |
|---|
| Description: | Title: Some users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue
User impact: Users may not receive the toast notification when another user answers a call from a Microsoft Teams call queue.
Current status: We're investigating a potential issue with Microsoft Teams call queues and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1182769 - Some users may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 10:00:00 2025 |
|---|
| End Time: | Tue Nov 4 16:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 4 16:56:51 2025 |
|---|
| Root Cause: | A recent service update to the affected service contained a code misconfiguration and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 4 16:56:51 2025 |
|---|
| Description: | Title: Some users may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows
User impact: Users may not have seen QR codes generating on Front-of-Room screens in MTR for Windows.
More info: Users could have still utilized the QR code generated on the console to proximity join.
Final status: We've completed deployment of the aforementioned fix and confirmed through internal testing that the impact is remediated. Some users may need to restart their devices manually or allow 24 hours for the device to restart automatically overnight in order to receive the fix.
Scope of impact: Some users that attempted to generate QR codes on Front-of-Room screens in MTR for Windows may have been impacted.
Start time: Monday, November 3, 2025, at 3:00 PM UTC
End time: Tuesday, November 4, 2025, at 9:00 PM UTC
Root cause: A recent service update to the affected service contained a code misconfiguration and caused impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify and prevent similar code misconfigurations in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Tue Nov 4 04:19:12 2025 |
|---|
| Description: | Title: Users may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows
User impact: Users may not see QR codes generating on Front-of-Room screens in MTR for Windows.
More info: Users can still utilize the QR code generated on the console to proximity join.
Current status: We're validating the aforementioned fix in our internal testing environment to ensure its efficacy prior to starting a deployment. We expect to provide a deployment timeline by our next scheduled update.
Scope of impact: Any user may be affected and may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows.
Root cause: A recent service update to the affected service contains a code misconfiguration, leading to impact.
Next update by: Tuesday, November 4, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Nov 4 00:54:24 2025 |
|---|
| Description: | Title: Users may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows
User impact: Users may not see QR codes generating on Front-of-Room screens in MTR for Windows.
More info: Users can still utilize the QR code generated on the console to proximity join.
Current status: We've identified a potential mitigation strategy of making a configuration change fix. Once ready, we'll test and validate the change to ensure it has the desired effect of remediating impact.
Scope of impact: Any user may be affected and may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows.
Root cause: A recent service update to the affected service contains a code misconfiguration, leading to impact.
Next update by: Tuesday, November 4, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Mon Nov 3 23:39:21 2025 |
|---|
| Description: | Title: Users may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows
User impact: Users may not see QR codes generating on Front-of-Room screens in MTR for Windows.
More info: Users can still utilize the QR code generated on the console to proximity join.
Current status: We've identified an issue from our internal testing where QR codes aren't generating on Front-of-Room screens in MTR. We investigated our service logs and have correlated impact with a recent service update containing a code misconfiguration, leading to impact. We're working to identify a remediation strategy and assessing all options to resolve impact.
Scope of impact: Any user may be affected and may not see QR codes generating on Front-of-Room screens in Microsoft Teams Rooms (MTR) for Windows.
Root cause: A recent service update to the affected service contains a code misconfiguration, leading to impact.
Next update by: Tuesday, November 4, 2025, at 6:00 AM UTC
|
|---|
|
DZ1163645 - Some macOS devices with multiple security providers may have no display output
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Sep 29 16:00:00 2025 |
|---|
| End Time: | Fri Oct 3 03:28:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Nov 4 10:06:22 2025 |
|---|
| Root Cause: | A deadlock in the Apple enterprise security framework occurred when multiple security providers were listening to events. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Nov 4 10:04:55 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 28 21:37:34 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 28 20:28:00 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 28 20:27:50 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 28 20:26:22 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 2 13:27:55 2025 |
|---|
| Description: | Title: Some macOS devices with multiple security providers may have no display output
User impact: MacOS devices with multiple security providers may have become unresponsive while sleeping.
Final status: Following our extended service telemetry monitoring, we've validated that impact has been remediated. Any devices that remain unresponsive will need to be restarted to be updated with our solution.
Scope of impact: Some users may have seen black screen crashes for macOS devices if their macOS devices were updated after September 29, 2025.
Start time: Monday, September 29, 2025, at 8:00 PM UTC
End time: Friday, October 3, 2025, at 7:28 AM UTC
Root cause: A deadlock in the Apple enterprise security framework occurred when multiple security providers were listening to events.
Next steps:
- We're further working with Apple to analyze the security framework to help prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 2 00:43:25 2025 |
|---|
| Description: | Title: Some macOS devices with multiple security providers may have no display output
User impact: MacOS devices with multiple security providers may become unresponsive while sleeping.
Current status: We’re continuing to monitor our service telemetry to confirm that our updated EDR configuration resolved the impact. Devices that are unresponsive will need to be restarted to be updated with our solution.
Scope of impact: Some users may see black screen crashes for macOS devices if their macOS devices were updated after September 29, 2025.
Start time: Monday, September 29, 2025, at 8:00 PM UTC
Root cause: A deadlock in Apple enterprise security framework is occurring when multiple security providers are listening to events.
Next update by: Thursday, October 2, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Oct 1 22:29:37 2025 |
|---|
| Description: | Title: Some macOS devices with multiple security providers may have no display output
User impact: MacOS devices with multiple security providers may have no display output.
More info: This issue is not specific to a single macOS device version and could affect users of any version of macOS.
Current status: Based on our monitoring of the telemetry, we’ve observed our solution is having its intended effect and we’re continuing to monitor to ensure the issue is resolved.
Scope of impact: Some users may see black screen crashes for macOS devices if their macOS devices were updated after September 29, 2025.
Start time: Monday, September 29, 2025, at 8:00 PM UTC
Root cause: A deadlock in Apple enterprise security framework occurs when multiple security providers are listening to events.
Next update by: Thursday, October 2, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Wed Oct 1 17:19:16 2025 |
|---|
| Description: | Title: Some macOS devices with multiple security providers may have no display output
User impact: MacOS devices with multiple security providers may have no display output.
More info: This issue is not specific to a single macOS device version and could affect users of any version of macOS.
Current status: Further analysis indicates that the root cause is a deadlock in Apple enterprise security framework is occurring when multiple security providers are listening to events, and we’ve updated the “root cause” section of communications to reflect this. We've mitigated this in Defender by updating our configuration, which is available in Endpoint Detection and Response (EDR) configuration version 2025.10.01.02 and higher. We're monitoring service health telemetry as our solution rolls out to confirm it’s resolving the issue.
Scope of impact: Some users may see black screen crashes for macOS devices if their macOS devices were updated after September 29, 2025.
Start time: Monday, September 29, 2025, at 8:00 PM UTC
Root cause: A deadlock in Apple enterprise security framework occurs when multiple security providers are listening to events.
Next update by: Thursday, October 2, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Oct 1 14:04:00 2025 |
|---|
| Description: | Title: Some users may see black screen crashes for MacOS devices configured using Microsoft Defender for Endpoint.
User impact: Users may see black screen crashes for MacOS devices configured using Microsoft Defender for Endpoint.
Current status: We received reports from some users where they see black screen crashes on MacOS devices. We've determined that a recent Microsoft Defender for Endpoint service update to improve performance contains a code regression which is resulting in crashes for MacOS devices or devices being unable to wake from deep sleep without a reboot. We're rolling back the offending update and we aim to provide a timeline to mitigation as one becomes available. Once we've rolled back the offending update, no additional actions will need to be taken by affected users.
Scope of impact: Some users may see black screen crashes for MacOS devices if their MacOS devices were updated after September 29, 2025.
Start time: Monday, September 29, 2025, at 8:00 PM UTC
Root cause: A recent Microsoft Defender for Endpoint service update to improve performance introduced a code regression which resulted in black screen crashes for MacOS devices.
Next update by: Wednesday, October 1, 2025, at 9:30 PM UTC
|
|---|
|
EX1182661 - Users may be unable to access their mailbox with any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 18:00:00 2025 |
|---|
| End Time: | Mon Nov 3 19:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 3 21:17:27 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 21:17:27 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may have been unable to access their mailbox with any Exchange Online connection method.
Final status: While we were in the process of analyzing the affected service telemetry, our system monitoring indicated that the service had returned to normal health and all affected Exchange Online connection methods recovered. We've confirmed that the issue is no longer occurring and we'll continuing to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: This event may have affected any users in North America who attempted to access their mailboxes with any Exchange Online connection method.
Start time: Monday, November 3, 2025, at 11:00 PM UTC
End time: Tuesday, November 4, 2025, at 12:00 AM UTC
Next steps:
- We're further investigating the drop in service reliability that impacted Exchange Online connection methods to understand the underlying cause of impact and how we can make changes to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 3 19:26:23 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: We've received alerts from our internal monitoring systems, indicating impact for users attempting to access their Exchange Online mailboxes. We're investigating the affected service telemetry to better understand the root cause of impact and to help inform our next steps.
Scope of impact: This event may affect users who attempt to access their mailboxes with any Exchange Online connection method.
Next update by: Tuesday, November 4, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Nov 3 18:36:01 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.
|
|---|
|
MO1180261 - Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun Oct 26 19:44:00 2025 |
|---|
| End Time: | Sun Oct 26 21:30:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 3 19:41:30 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 19:13:57 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 30 08:16:02 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 19:35:53 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sun Oct 26 22:47:11 2025 |
|---|
| Description: | Title: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
User impact: Users in the Asia-Pacific region may have experienced issues with various Microsoft 365 services.
More info: Users may have received 404 errors when attempting to access Microsoft services from portal.office.com.
Reports indicated that users were unable to access resources from portal.office.com but were able to access Teams, Outlook, and other services directly or through the waffle menu.
Additionally, users may have been able to access admin portal features and Microsoft 365 services through admin.microsoft.com/AdminPortal/Home.
Users may have experienced issues accessing the following Microsoft 365 services:
- Microsoft Teams
- Microsoft Outlook
- Microsoft 365 Copilot
- OneDrive
Final status: Our automated recovery features took the appropriate action to restore service. We’ve confirmed by analyzing telemetry and working with some previously affected customers that the impact has been mitigated.
Scope of impact: Any user located in the Asia-Pacific region may have experienced issues accessing Microsoft 365 services through portal.office.com.
Start time: Sunday, October 26, 2025 at approximately 11:30 PM UTC
End time: Monday, October 27, 2025 at approximately 1:30 AM UTC
Preliminary root cause: The underlying root cause of the issue remains under investigation.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Sun Oct 26 22:02:28 2025 |
|---|
| Description: | Title: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
User impact: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services.
More info: Users may receive 404 errors when attempting to access Microsoft services from portal.office.com.
Reports indicate that users are unable to access resources from portal.office.com but are able to access Teams, Outlook, and other services directly or through the waffle menu. Affected users are encouraged to attempt these alternative means of accessing our services while we work to remediate the problem.
Additionally, users may be able to access admin portal features and Microsoft 365 services through admin.microsoft.com/AdminPortal/Home.
Users may experience issues with the following Microsoft 365 services:
- Microsoft Teams
- Microsoft Outlook
- Microsoft 365 Copilot
- OneDrive
Current status: Our automated recovery features have taken action to restore service, and our telemetry indicates that service health has improved; however, some users may still be affected. We’re continuing our efforts to isolate the source of impact and fully remediate the issue.
Scope of impact: Any user located in the Asia-Pacific region may experience issues accessing Microsoft 365 services through portal.office.com.
Next update by: Monday, October 27, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Sun Oct 26 21:55:49 2025 |
|---|
| Description: | Our automated recovery features have taken action to restore service, and our telemetry indicates that service health has improved; however, some users may still be affected. We’re continuing our efforts to isolate the source of impact and fully remediate the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun Oct 26 20:53:42 2025 |
|---|
| Description: | Title: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
User impact: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services.
More info: Users may receive 404 errors when attempting to access Microsoft services from portal.office.com.
Additionally, reports indicate that users may experience issues with the following Microsoft 365 services:
- Microsoft Teams
- Microsoft Outlook
- Microsoft 365 Copilot
- OneDrive
Current status: We're continuing to analyze the available telemetry as we work to assess the scope of the problem and isolate the source of impact.
Scope of impact: Any user located in the Asia-Pacific region may experience issues with various Microsoft 365 services.
Next update by: Monday, October 27, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sun Oct 26 20:27:31 2025 |
|---|
| Description: | Our telemetry indicates that impact is largely to users hosted in Japan and Australia, though users in other regions may also experience impact.
Initial reports indicate that within Copilot specifically, users are receiving an error message stating, "We are sorry, something went wrong. Please try refreshing the page in a few minutes."
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun Oct 26 20:16:44 2025 |
|---|
| Description: | Title: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
User impact: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services.
More info: Users may experience issues with the following Microsoft 365 services:
- Microsoft Teams
- Microsoft Outlook
- Microsoft 365 Copilot
Current status: We're reviewing service telemetry logs to better understand the cause of impact and to help inform our next steps.
Scope of impact: Any user located in the Asia-Pacific region may experience issues with various Microsoft 365 services.
Next update by: Monday, October 27, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Sun Oct 26 20:02:47 2025 |
|---|
| Description: | Title: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services
User impact: Users in the Asia-Pacific region may experience issues with various Microsoft 365 services.
Current status: We're investigating user reports of impact with various Microsoft 365 services, including predominantly Microsoft Teams and Microsoft Copilot (Microsoft 365). We'll provide an update within 30 minutes.
|
|---|
|
TM1182515 - Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
| Status: | serviceRestored |
|---|
| Start Time: | Sun Nov 2 22:00:00 2025 |
|---|
| End Time: | Mon Nov 3 13:41:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 3 19:12:24 2025 |
|---|
| Root Cause: | A recent build rollout intended to provide improvements for PowerPoint in Teams introduced a code regression that caused Microsoft Teams meetings and call recording files to not capture PowerPoint shared content, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 19:12:24 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may have been unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Final status: After monitoring the service health telemetry following the finalization of the aforementioned rollback, we’ve confirmed that impact has been remediated.
Scope of impact: Your organization was impacted by this event, and all users may have been unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Start time: Monday, November 3, 2025, at 7:00 AM UTC
End time: Monday, November 3, 2025, at 6:41 PM UTC
Root cause: A recent build rollout intended to provide improvements for PowerPoint in Teams introduced a code regression that caused Microsoft Teams meetings and call recording files to not capture PowerPoint shared content, which resulted in impact.
Next steps:
- We're analyzing performance data and trends on the affected systems and reviewing our service rollout procedures to identify possible improvements to help prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 3 18:27:16 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
More info: As a temporary workaround, users may utilize screen-sharing or application-sharing for any PowerPoint slides or presentations rather than sharing directly through PowerPoint itself.
Current status: We're working to finalize the rollback in the affected infrastructure while continuing to monitor service health telemetry to verify that impact has been fully remediated.
Scope of impact: Your organization is impacted by this event, and all users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Start time: Monday, November 3, 2025, at 7:00 AM UTC
Root cause: A recent build rollout intended to provide improvements for PowerPoint in Teams introduced a code regression that caused Microsoft Teams meetings and call recording files to not capture PowerPoint shared content, which results in impact.
Next update by: Tuesday, November 4, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Nov 3 16:30:51 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
More info: As a temporary workaround, users may utilize screen-sharing or application-sharing for any PowerPoint slides or presentations rather than sharing directly through PowerPoint itself.
Current status: We're continuing to monitor the final stages of our rollback and are seeing increasingly positive results that indicate impact is almost fully mitigated, and that our root cause analysis is correct.
Scope of impact: Your organization is impacted by this event, and all users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Start time: Monday, November 3, 2025, at 7:00 AM UTC
Root cause: A recent build rollout intended to provide improvements for PowerPoint in Teams introduced a code regression that caused Microsoft Teams meetings and call recording files to not capture PowerPoint shared content, and resulted in impact.
Next update by: Monday, November 3, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 14:29:08 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
More info: As a temporary workaround, users may utilize screen-sharing or application-sharing for any PowerPoint slides or presentations rather than sharing directly through PowerPoint itself.
Current status: We're monitoring a rollback of the suspected offending build and are seeing positive results that indicate impact is being mitigated. We'll continue to analyze this rollback completion in order to fully verify this issue's root cause and its mitigation.
Scope of impact: Your organization is impacted by this event, and all users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Start time: Monday, November 3, 2025, at 7:00 AM UTC
Next update by: Monday, November 3, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 12:32:03 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
More info: As a temporary workaround, users may utilize screen-sharing or application-sharing for any PowerPoint slides or presentations rather than sharing directly through PowerPoint itself.
Current status: We suspect this issue with Microsoft Teams meetings and call recording files not containing PowerPoint shared content is due to a recent build rollout. We're working to revert this build to both confirm the root cause and mitigate impact, and we’ll provide you with a timeline on the rollback and overall mitigation as one becomes available.
Scope of impact: Your organization is impacted by this event, and all users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Start time: Monday, November 3, 2025, at 7:00 AM UTC
Next update by: Monday, November 3, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 11:55:47 2025 |
|---|
| Description: | Title: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls
User impact: Users may be unable to record PowerPoint presentations during Microsoft Teams meetings and calls.
Current status: We're investigating a potential issue in which users may be unable to record PowerPoint presentations in Microsoft Teams calls and meetings, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1180557 - Some users may have been unable to hear text-to-speech during auto-attendant calls in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat Oct 25 00:15:00 2025 |
|---|
| End Time: | Mon Oct 27 08:22:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 3 17:54:41 2025 |
|---|
| Root Cause: | A recent change caused a specific language (English (United Kingdom)) to become unavailable within a backend Speech service. The Speech service is leveraged by Microsoft Teams auto-attendant text-to-speech functionality. More information is provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 17:54:41 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 12:28:16 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Oct 27 09:02:31 2025 |
|---|
| Description: | Title: Some users may have been unable to hear text-to-speech during auto-attendant calls in Microsoft Teams
User impact: Users may have been unable to hear text-to-speech during auto-attendant calls in Microsoft Teams.
Final status: We've confirmed that the issue is resolved after reverting the impacting update.
Scope of impact: This issue affected a subset of organizations that were configured to use English (United Kingdom) as the language.
Start time: Saturday, October 25, 2025, at 4:15 AM UTC
End time: Monday, October 27, 2025, at 12:22 PM UTC
Root cause: A recent change caused a specific language (English (United Kingdom)) to become unavailable within a backend Speech service. The Speech service is leveraged by Microsoft Teams auto-attendant text-to-speech functionality. More information 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'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Oct 27 08:42:24 2025 |
|---|
| Description: | We've started to receive confirmation from previously impacted organizations that the issue is no longer occurring. We're continuing to monitor the service to confirm resolution.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Oct 27 08:39:41 2025 |
|---|
| Description: | Title: Some users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams
User impact: Users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams.
Current status: We've prioritized reverting the change in the regions which use English (United Kingdom) as a language, and monitoring telemetry shows the last error occurred at 12:22 PM UTC. We're still reverting the change in other regions, however, it is expected that impact was not occurring in those regions due to different languages being used.
Scope of impact: This issue affects a subset of organizations that were configured to use English (United Kingdom) as the language.
Start time: Saturday, October 25, 2025, at 4:15 AM UTC
Next update by: Monday, October 27, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 08:18:00 2025 |
|---|
| Description: | We've reverted the change in a section of the European infrastructure, and monitoring telemetry is showing improvement. We're continuing the revert in the remaining infrastructures.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Oct 27 08:11:21 2025 |
|---|
| Description: | Title: Some users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams
User impact: Users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams.
Current status: We’ve identified that a recent change is resulting in impact, and we’re reverting the change to remediate impact.
Scope of impact: Currently the majority of reports have been from users in the Europe regions. We’re still investigating if additional regions are affected.
Next update by: Monday, October 27, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 07:01:37 2025 |
|---|
| Description: | Title: Some users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams
User impact: Users may be unable to hear text-to-speech during auto-attendant calls in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: This issue may impact any user within your organization served via the affected region in Europe.
Next update by: Monday, October 27, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 06:27:06 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.
|
|---|
|
EX1181125 - Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 3 13:34:00 2025 |
|---|
| End Time: | Fri Oct 31 13:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 3 17:24:37 2025 |
|---|
| Root Cause: | A latent code bug resulted in users added to groups receiving "Owner" instead of "Member" permissions by default. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 16:20:12 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurred when users were added as members to the group through Outlook on the web.
Final status: We've confirmed using internal testing that our code fix remediated the impact.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may have been given "Owner" permissions by default instead of "Member" permissions.
Start time: Friday, October 3, 2025, at 5:34 PM UTC
End time: Friday, October 31, 2025, at 5:30 PM UTC
Root cause: A latent code bug resulted in users added to groups receiving "Owner" instead of "Member" permissions by default.
Next steps:
- We're reviewing the code of the affected component to determine methods to detect similar regressions before they cause impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 31 20:43:06 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've verified through internal testing that our code solution has successfully saturated and taken effect throughout the impacted environment. We're reaching out to a final subset of impacted users to validate the issue is fully remediated.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Start time: Friday, October 3, 2025, at 5:34 PM UTC
Root cause: The impacted component contains a long-standing code regression that has remained dormant until now.
Next update by: Monday, November 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Oct 31 15:34:01 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've validated that our actions to implement a corrective code solution have shown success when tested by a subset of impacted users. We're continuing to monitor to ensure this fix has saturated and alleviates impact fully.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Start time: Friday, October 3, 2025, at 5:34 PM UTC
Root cause: The impacted component contains a long-standing code regression that has remained dormant until now.
Next update by: Saturday, November 1, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Oct 30 13:58:29 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've implemented a corrective fix to address an impacted component containing a long-standing code regression that has remained dormant until now. We're monitoring the rollout of this fix to ensure that the environment has returned to a healthy state.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Root cause: The impacted component contains a long-standing code regression that has remained dormant until now.
Next update by: Friday, October 31, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 13:59:00 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've identified that the impacted component contains a long-standing code regression that has remained dormant until now. We've developed a corrective fix and are preparing to deploy it to remediate the observed impact.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Root cause: The impacted component contains a long-standing code regression that has remained dormant until now.
Next update by: Thursday, October 30, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 05:20:14 2025 |
|---|
| Description: | Title: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default
User impact: Users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've identified that the impacted component contains a long-standing code regression that has remained dormant until now. Our engineering team has developed a corrective fix, which is currently undergoing rigorous validation to ensure its effectiveness and confirm that it provides a sustainable solution to mitigate the observed impact.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Root cause: The impacted component contains a long-standing code regression that has remained dormant until now.
Next update by: Wednesday, October 29, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 16:30:07 2025 |
|---|
| Description: | Title: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions
User impact: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We're continuing to investigate the affected component that helps facilitate groups membership management that we suspect is resulting in newly added users being added as members to a Microsoft 365 group to have their default permissions set to "Owner" instead of "Member". We expect that this investigation into the component will help us identify the cause of this issue and inform us in creating resolution steps.
Scope of impact: Some users added as members to a Microsoft 365 group in Outlook on the web may be given "Owner" permissions by default instead of "Member" permissions.
Next update by: Wednesday, October 29, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Oct 28 15:07:17 2025 |
|---|
| Description: | Title: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions
User impact: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We've isolated the component causing default permissions for newly added users to be set to "Owner" instead of "Member" and we're discussing our next troubleshooting steps to isolate the underlying root cause and what actions we can take to remediate impact.
Scope of impact: Your organization is affected by this event, and users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
Next update by: Tuesday, October 28, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 14:02:34 2025 |
|---|
| Description: | Title: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions
User impact: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
Current status: We're reviewing support case information and analyzing provided HTTP Archive format (HAR) logs to isolate potential errors to determine our initial troubleshooting actions.
Scope of impact: Your organization is affected by this event, and users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
Next update by: Tuesday, October 28, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 13:45:11 2025 |
|---|
| Description: | Title: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions
User impact: Users added as members to a Microsoft 365 group in Outlook on the web are given "Owner" permissions.
More info: Specifically, this issue occurs when users are added as members to the group through Outlook on the web.
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.
|
|---|
|
TM1178123 - Some users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 17 13:15:00 2025 |
|---|
| End Time: | Sun Nov 2 01:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 3 14:55:07 2025 |
|---|
| Root Cause: | A code change, designed to adjust the screen capture blocking feature, contained a misconfiguration that caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 14:55:07 2025 |
|---|
| Description: | Title: Some users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings
User impact: Users leveraging the Microsoft Teams iOS app may have seen a picture-in-picture window after leaving meetings.
More info: This issue specifically impacted users who had Intune app protection policies enabled on their iOS devices. Impact was specific to the following Microsoft Teams iOS app builds:
7.17.0
7.17.1
7.18.0
7.18.1
7.18.2
7.19.0
Final status: The build has reached the remaining impacted users who rely on automatic updates, and after confirming the impact is remediated with a subset of affected users, we've verified the issue is resolved.
Scope of impact: Some users that left meetings in the Microsoft Teams iOS app may have been impacted.
Start time: Wednesday, September 17, 2025, at 5:15 PM UTC
End time: Sunday, November 2, 2025, at 6:30 AM UTC
Root cause: A code change, designed to adjust the screen capture blocking feature, contained a misconfiguration that caused impact.
Next steps:
- We're reviewing our code change implementation process to ensure similar misconfigurations are identified and corrected ahead of deployment to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 30 20:08:24 2025 |
|---|
| Description: | Title: Some users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings
User impact: Users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings.
More info: This issue specifically impacts users who have Intune app protection policies enabled on their iOS devices. Impact is specific to the following Microsoft Teams iOS app builds:
7.17.0
7.17.1
7.18.0
7.18.1
7.18.2
7.19.0
Current status: We've confirmed with some users who initially reported the issue that the new build version 7.19.1 successfully remediates impact. The saturation of the build is currently ten percent complete to users with automatic updates enabled, though users can manually update the Microsoft Teams iOS app to version 7.19.1 to experience immediate relief. We anticipate the deployment will reach full saturation for the remaining impacted users who rely on automatic updates and the issue will be resolved by our next scheduled update.
Scope of impact: Some users that leave meetings in the Microsoft Teams iOS app may be impacted.
Start time: Wednesday, September 17, 2025, at 5:15 PM UTC
Root cause: A code change, designed to adjust the screen capture blocking feature, contains a misconfiguration that's causing impact.
Next update by: Monday, November 3, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Oct 30 15:39:40 2025 |
|---|
| Description: | Title: Some users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings
User impact: Users leveraging the Microsoft Teams iOS app may see a picture-in-picture window after leaving meetings.
More info: This issue specifically impacts users who have Intune app protection policies enabled on their iOS devices.
Impact is specific to the following Microsoft Teams iOS app builds:
7.17.0
7.17.1
7.18.0
7.18.1
7.18.2
7.19.0
Current status: We've confirmed the new build version, which is currently available as a manual update for users in the Teams iOS app as version 7.19.1, has reached ten percent of users with automatic updates enabled. We're reaching out to a subset of users who have received the new build to confirm impact remediation, and in parallel, we're continuing to monitor as the new build proceeds to update automatically for the remaining affected users.
Scope of impact: Some users that leave meetings in the Microsoft Teams iOS app may be impacted.
Start time: Wednesday, September 17, 2025, at 5:15 PM UTC
Root cause: A code change, designed to adjust the screen capture blocking feature, contains a misconfiguration that's causing impact.
Next update by: Friday, October 31, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Oct 27 14:57:43 2025 |
|---|
| Description: | Title: Some users may see a meeting window after leaving in the Microsoft Teams iOS app
User impact: Users may see a meeting window after leaving in the Microsoft Teams iOS app.
More info: This issue specifically impacts users who have Intune app protection policies enabled on their iOS devices.
Impact is specific to the following Microsoft Teams iOS app builds:
7.17.0
7.17.1
7.18.0
7.18.1
7.18.2
7.19.0
Current status: We've completed developing the new build version with the fix that is currently available for users to manually update in the Teams iOS app as version 7.19.1. Alternately, we anticipate that users with automatic updates enabled will automatically receive the new app version by our next scheduled communications update.
Scope of impact: Some users attempting to leave a meeting in the Microsoft Teams iOS app may be impacted.
Start time: Wednesday, September 17, 2025, at 5:15 PM UTC
Root cause: A code change, designed to adjust the screen capture blocking feature, contains a misconfiguration that's causing impact.
Next update by: Thursday, October 30, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Oct 24 15:27:06 2025 |
|---|
| Description: | Title: Some users may see a meeting window after leaving in the Microsoft Teams iOS app
User impact: Users may see a meeting window after leaving in the Microsoft Teams iOS app.
More info: This issue specifically impacts users who have Intune app protection policies enabled on their iOS devices.
Impact is specific to the following Microsoft Teams iOS app builds:
7.17.0
7.17.1
7.18.0
7.18.1
7.18.2
7.19.0
Current status: We've identified a code change, designed to adjust the screen capture blocking feature, which contains a misconfiguration that's causing impact. We're developing an updated build version for the Teams iOS app containing a code fix which will then need to be approved for the App Store prior. We'll provide an estimated timeline for availability through the App Store if possible.
Scope of impact: Some users attempting to leave a meeting in the Microsoft Teams iOS app may be impacted.
Start time: Wednesday, September 17, 2025, at 5:15 PM UTC
Root cause: A code change, designed to adjust the screen capture blocking feature, contains a misconfiguration that's causing impact.
Next update by: Monday, October 27, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 16:08:51 2025 |
|---|
| Description: | Title: Some users may see a meeting window after leaving in the Microsoft Teams iOS application
User impact: Users may see a meeting window after leaving in the Microsoft Teams iOS application.
More info: This issue specifically impacts users who have Intune app protection policies enabled on their iOS devices.
Current status: We're reviewing recent service changes in effort to isolate the cause of the underlying issue and to identify an appropriate remediation action.
Scope of impact: Some users attempting to leave a meeting in the Microsoft Teams iOS application may be impacted.
Next update by: Friday, October 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 07:28:10 2025 |
|---|
| Description: | Title: Some users may see a meeting window after leaving in the Microsoft Teams iOS application
User impact: Users may see a meeting window after leaving in the Microsoft Teams iOS application.
Current status: We're continuing to analyse diagnostic data from system telemetry and reaching out to your representatives to gather additional context to support our investigation.
Scope of impact: Some users attempting to leave a meeting in the Microsoft Teams iOS application may be impacted.
Next update by: Thursday, October 23, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 04:18:20 2025 |
|---|
| Description: | Title: Some users may see a meeting window after leaving in the Microsoft Teams iOS application
User impact: Users may see a meeting window after leaving in the Microsoft Teams iOS application.
Current status: We're reviewing diagnostic data from our system telemetry to identify the source of the issue and establish a mitigation plan.
Scope of impact: Some users attempting to leave a meeting in the Microsoft Teams iOS application may be impacted.
Next update by: Thursday, October 23, 2025, at 12:30 PM UTC
|
|---|
|
MV1182528 - Users may encounter intermittent failures when loading the Microsoft Viva Engage feed
| Status: | serviceRestored |
|---|
| Start Time: | Mon Nov 3 06:00:00 2025 |
|---|
| End Time: | Mon Nov 3 12:05:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 3 14:26:55 2025 |
|---|
| Root Cause: | An outdated configuration was incorrectly applied during a normal optimization task, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 14:26:55 2025 |
|---|
| Description: | Title: Users may encounter intermittent failures when loading the Microsoft Viva Engage feed
User impact: Users may have encountered intermittent failures when loading the Viva Engage feed.
More info: Affected users saw the following message:
"The page isn't loading right now, please try again in a few minutes."
While we were working to remediate impact, retries may have been successful.
Final status: We've completed the application of the long-term fix and confirmed this issue is no longer occurring using service telemetry and with affected users.
Scope of impact: Any user accessing their Viva Engage feed in the United States region may have been intermittently affected.
Start time: Monday, November 3, 2025, at 11:00 AM UTC
End time: Monday, November 3, 2025, at 5:05 PM UTC
Root cause: An outdated configuration was incorrectly applied during a normal optimization task, resulting in impact.
Next steps:
- We're reviewing our configuration update procedures to better understand the underlying cause of impact and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Nov 3 13:14:20 2025 |
|---|
| Description: | Title: Users may encounter intermittent failures when loading the Microsoft Viva Engage feed
User impact: Users may encounter intermittent failures when loading the Viva Engage feed.
More info: Affected users are seeing the following message:
"The page isn't loading right now, please try again in a few minutes."
While we're working to remediate impact, retries may be successful.
Current status: We've received user reports of intermittent Viva Engage feed loading failures and our investigation has identified that an outdated configuration was incorrectly applied during a normal optimization task, resulting in impact. We've manually corrected the configuration and telemetry shows this issue has been remediated. We're working on a long-term fix which may incur additional errors during the application and will provide a complete remediation timeline once available.
Scope of impact: Any user accessing their Viva Engage feed in the United States region may be intermittently affected.
Start time: Monday, November 3, 2025, at 11:00 AM UTC
Root cause: An outdated configuration was incorrectly applied during a normal optimization task, resulting in impact.
Next update by: Monday, November 3, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 12:42:03 2025 |
|---|
| Description: | Title: Users may encounter intermittent failures when loading the Microsoft Viva Engage feed
User impact: Users may encounter intermittent failures when loading the Viva Engage feed.
More info: Affected users are seeing the following message:
"The page isn't loading right now, please try again in a few minutes."
Current status: We're investigating a potential issue with Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1180553 - Some admins may be unable to access public folders from the Exchange admin center or PowerShell
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 24 15:00:00 2025 |
|---|
| End Time: | Mon Nov 3 07:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Nov 3 14:18:26 2025 |
|---|
| Root Cause: | A recent service update to improve mailbox folder schema produced an impacting code exception that may have been preventing admins from accessing public folders from the Exchange admin center or PowerShell. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 13:58:33 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins may have been unable to access public folders from the Exchange admin center or PowerShell.
More info: Affected admins may have seen the following error message: “Internal server error” when attempting to access public folders from the Exchange admin center or PowerShell.
Additionally, admins may have been unable to run the PowerShell command Get-PublicFolder.
Final status: We've confirmed that the code fix has completed deployment to the affected environment and the impact is remediated.
Scope of impact: Impact may have occurred for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Start time: Friday, October 24, 2025, at 7:00 PM UTC
End time: Monday, November 3, 2025, at 12:30 PM UTC
Root cause: A recent service update to improve mailbox folder schema produced an impacting code exception that may have been preventing admins from accessing public folders from the Exchange admin center or PowerShell.
Next steps:
- We're reviewing our service update procedures to ensure similar issues are caught and addressed in testing ahead of deployment to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 29 12:33:24 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins are unable to access public folders from the Exchange admin center or PowerShell.
More info: Affected admins may see the following error message: "Internal server error" when attempting to access public folders from the Exchange admin center or PowerShell.
Additionally, admins may be unable to run the PowerShell command Get-PublicFolder.
Current status: We've begun deployment of the code fix, and we're monitoring the deployment as it progresses to ensure it completes in a timely manner. Initial projections indicate the deployment will complete by Wednesday, November 5, 2025, and we'll provide an update on the deployment saturation on our next update.
Scope of impact: Impact may occur for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Start time: Friday, October 24, 2025, at 7:00 PM UTC
Root cause: A recent service update to improve mailbox folder schema has produced an impacting code exception that is preventing admins from accessing public folders from the Exchange admin center or PowerShell.
Next update by: Monday, November 3, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Oct 28 13:07:45 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins are unable to access public folders from the Exchange admin center or PowerShell.
More info: Affected admins may see the following error message: "Internal server error" when attempting to access public folders from the Exchange admin center or PowerShell.
Additionally, admins may be unable to run the PowerShell command Get-PublicFolder.
Current status: We’ve developed and validated the code fix to address the code exception and are in the final stages of deployment preparation. Once available, we’ll provide a resolution timeline.
Scope of impact: Impact may occur for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Start time: Friday, October 24, 2025, at 7:00 PM UTC
Root cause: A recent service update to improve mailbox folder schema has produced an impacting code exception that is preventing admins from accessing public folders from the Exchange admin center or PowerShell.
Next update by: Wednesday, October 29, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 13:05:24 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins are unable to access public folders from the Exchange admin center or PowerShell.
More info: Affected admins see the following error message: "Internal server error" when attempting to access public folders from the Exchange admin center or PowerShell.
Additionally, admins are unable to run the PowerShell command.
Current status: Our analysis of logs and other impact scenario data provided by affected admins has isolated a recent update to mailbox folder schema that has produced an impacting code exception that is preventing admins from accessing public folders from the Exchange admin center or PowerShell. We're developing a code fix to address the code exception and expect an estimated timeline for the deployment of our solution to be available once our internal testing and validations have completed.
Scope of impact: Impact may occur for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Start time: Friday, October 24, 2025, at 7:00 PM UTC
Root cause: A recent service update to improve mailbox folder schema has produced an impacting code exception that is preventing admins from accessing public folders from the Exchange admin center or PowerShell.
Next update by: Tuesday, October 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 08:04:39 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins are unable to access Public Folders from the Exchange admin center or PowerShell.
More info: Affected admins see the following error message: "Internal server error" when attempting to access Public Folders from the Exchange admin center or PowerShell.
Additionally, admins are unable to run the PowerShell command.
Current status: We’re continuing to review logs and affected admin provided impact scenario data alongside detailed system error data, to identify the root cause and develop a mitigation plan.
Scope of impact: Impact may occur for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Next update by: Monday, October 27, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Oct 27 06:19:38 2025 |
|---|
| Description: | Title: Some admins may be unable to access public folders from the Exchange admin center or PowerShell
User impact: Admins are unable to access Public Folders from the Exchange admin center or PowerShell.
More info: Affected admins see the following error message: "Internal server error" when attempting to access Public Folders from the Exchange admin center or PowerShell.
Additionally, admins are unable to run the PowerShell command.
Current status: We're reviewing logs and impact scenario data provided by affected admins to determine our next troubleshooting steps.
Scope of impact: Impact may occur for some admins globally that attempt to access public folders from the Exchange admin center or PowerShell.
Next update by: Monday, October 27, 2025, at 12:30 PM UTC
|
|---|
|
MV1172356 - Users may experience intermittent delays or HTTP 429 errors when accessing Microsoft Viva Engage
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Oct 14 08:45:00 2025 |
|---|
| End Time: | Tue Oct 14 11:00:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Nov 3 09:55:28 2025 |
|---|
| Root Cause: | During routine capacity tuning, the service infrastructure was inadvertently downscaled beyond intended limits, leaving insufficient service instances for peak traffic. Once peak traffic occurred, this triggered resource exhaustion and cascading failures across dependent components. Automated scaling and failover mechanisms did not restore service instances promptly due to gaps in logic, while downstream dependencies exhibited high latency, creating backpressure and amplifying the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Nov 3 09:55:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 30 07:23:35 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 14 12:45:53 2025 |
|---|
| Description: | Title: Users may experience intermittent delays or HTTP 429 errors when accessing Microsoft Viva Engage
User impact: Users may have experienced intermittent delays or HTTP 429 errors when accessing Viva Engage.
Final status: Our monitoring has validated that our rebalancing actions have successfully remediated impact.
Scope of impact: Any user attempting to access Microsoft Viva Engage may have been intermittently impacted.
Start time: Tuesday, October 14, 2025, at 12:45 PM UTC
End time: Tuesday, October 14, 2025, at 3:00 PM UTC
Root cause: During routine capacity tuning, the service infrastructure was inadvertently downscaled beyond intended limits, leaving insufficient service instances for peak traffic. Once peak traffic occurred, this triggered resource exhaustion and cascading failures across dependent components. Automated scaling and failover mechanisms did not restore service instances promptly due to gaps in logic, while downstream dependencies exhibited high latency, creating backpressure and amplifying the impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 14 11:27:14 2025 |
|---|
| Description: | Title: Users may experience intermittent delays or HTTP 429 errors when accessing Microsoft Viva Engage
User impact: Users may experience intermittent delays or HTTP 429 errors when accessing Viva Engage.
Current status: Our monitoring has identified an unexpected increase in traffic, resulting in impact. We've performed rebalancing operations and are monitoring the environment to validate this issue has been remediated.
Scope of impact: Any user attempting to access Microsoft Viva Engage may be intermittently impacted.
Start time: Tuesday, October 14, 2025, at 1:30 PM UTC
Root cause: An unexpected increase in traffic is resulting in suboptimal performance when attempting to process access requests to service.
Next update by: Tuesday, October 14, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Oct 14 10:42:45 2025 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Viva Engage
User impact: User impact: Users may be unable to access Microsoft Viva Engage.
Current status: We’re reviewing service health telemetry to isolate the root cause and determine the next steps to mitigate impact.
Scope of impact: Some users attempting to access Microsoft Viva Engage may be impacted.
Next update by: Tuesday, October 14, 2025, at 4:30 PM UTC
|
|---|
|
DZ1181559 - Some admins may have encountered delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 29 12:30:00 2025 |
|---|
| End Time: | Thu Oct 30 03:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Nov 1 05:47:32 2025 |
|---|
| Root Cause: | A recent service issue impacted the ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Nov 1 05:47:32 2025 |
|---|
| Description: | Title: Some admins may have encountered delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may have encountered delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios included, but weren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Final status: The backlog has completely drained and we've confirmed after a period of monitoring service health, that impact has been resolved.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may have been impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
End time: Saturday, November 1, 2025, at 7:00 AM UTC
Root cause: A recent service issue impacted the ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
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 Oct 31 16:15:34 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: The backlog is taking longer to drain than initially anticipated. The service remains stable and we're continuing to monitor the backlog as it gradually drains. We'll provide an updated timeline for the remediation as one becomes available.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Saturday, November 1, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Oct 31 11:59:08 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: The backlog continues to drain after the completion of our optimization efforts. We're actively monitoring as the drain continues and anticipate it will complete, and impact will be fully resolved, by our next communication update.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Friday, October 31, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Oct 31 07:39:33 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: The backlog is actively draining as a result of our optimization efforts, and we expect it to be fully cleared by the time of our next scheduled update.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Friday, October 31, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Oct 31 00:34:19 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We’re continuing to monitor the rollout of our optimization efforts to ensure they expedite the drain of the backlog, and we’re aiming to provide a new timeline to remediation by our next scheduled update.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Friday, October 31, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Oct 30 16:28:39 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're monitoring the rollout of our optimization efforts to ensure they expedite the drain of the backlog, as well as determining if an estimated timeline to remediation will be available.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Friday, October 31, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Oct 30 14:38:10 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: Optimization efforts and the process to drain the backlog of events is ongoing, with a portion of infrastructure nearly complete and the remaining infrastructure progressing through requests as expected.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Thursday, October 30, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Oct 30 12:07:11 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: Optimization efforts and the process to drain the backlog of events is ongoing, with a portion of infrastructure nearly complete and the remaining infrastructure progressing through requests as expected.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events and resulting in slow processing.
Next update by: Thursday, October 30, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Oct 30 07:37:02 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're continuing to optimize traffic and performance parameters on the affected infrastructure to clear a backlog of events and mitigate impact.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events, which is causing slow processing.
Next update by: Thursday, October 30, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Oct 30 04:44:27 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We're optimizing traffic and performance parameters on the affected infrastructure, to remediate impact.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events, which is causing slow processing.
Next update by: Thursday, October 30, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Oct 30 03:00:20 2025 |
|---|
| Description: | Title: Some admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps
User impact: Admins may encounter delays for Microsoft 365 events in Microsoft Defender for Cloud Apps.
More info: Impacted Microsoft 365 event scenarios include, but aren't limited to:
- Viewing activities
- Activity alerts
- Advanced hunting
- Anomaly detection
- Microsoft Sentinel
- File policy evaluation
Current status: We've determined that a recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events, which is causing slow processing. We're evaluating the best way to safely remediate impact.
Scope of impact: Some admins attempting to use Microsoft 365 events in Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, October 29, 2025, at 4:30 PM UTC
Root cause: A recent service issue is impacting ingestion of Microsoft 365 events in Microsoft Defender for Cloud Apps, causing a backlog of events, which is causing slow processing.
Next update by: Thursday, October 30, 2025, at 9:00 AM UTC
|
|---|
|
OP1181966 - Some users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 31 14:45:00 2025 |
|---|
| End Time: | Fri Oct 31 18:00:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 31 18:17:51 2025 |
|---|
| Root Cause: | A recent service update to change an authentication component was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 31 18:17:51 2025 |
|---|
| Description: | Title: Some users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features
User impact: Users may have encounter issues or been prompted to sign in when using some Microsoft 365 apps features.
More info: The following scenarios may have been impacted; however, impact may have not been limited to:
-Intelligence features such as Copilot.
-Compliance features, such as Auto-Classification and Consumer consent.
-Collaboration features, such as @mentions.
-Identity features such as people cards and the people well.
-Personalization features, such as roaming and most recently used documents.
-Application features such as Present in PowerPoint or PowerQuery in Excel.
Final status: We've completed the reversal of the offending service update and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Some users attempting to use any of the scenarios mentioned in the "More Info" section may have been impacted.
Start time: Friday, October 31, 2025, at 6:45 PM UTC
End time: Friday, October 31, 2025, at 10:00 PM UTC
Root cause: A recent service update to change an authentication component was causing impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify and prevent similar authentication configuration issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 31 17:05:38 2025 |
|---|
| Description: | Title: Some users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features
User impact: Users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features.
More info: The following scenarios may be impacted; however, impact may not be limited to:
-Intelligence features such as Copilot.
-Compliance features, such as Auto-Classification and Consumer consent.
-Collaboration features, such as @mentions.
-Identity features such as people cards and the people well.
-Personalization features, such as roaming and most recently used documents.
-Application features such as Present in PowerPoint or PowerQuery in Excel.
Current status: Our service health monitoring alerted us to authentication failures occurring when some users attempt to use some Microsoft 365 apps features. We've identified a recent service update to change an authentication component, which is causing impact. We're reversing the offending update to remediate the impact.
Scope of impact: Some users attempting to use any of the scenarios mentioned in the "More Info" section may be impacted.
Root cause: A recent service update to change an authentication component is causing impact.
Next update by: Friday, October 31, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Oct 31 16:50:55 2025 |
|---|
| Description: | Title: Users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features
User impact: Users may encounter issues or be prompted to sign in when using some Microsoft 365 apps features.
More info: The following scenarios may be impacted; however, impact may not be limited to:
-Intelligence features such as Copilot.
-Compliance features, such as Auto-Classification and Consumer consent.
-Collaboration features, such as @mentions.
-Identity features such as people cards and the people well.
-Personalization features, such as roaming and most recently used documents.
-Application features such as Present in PowerPoint or PowerQuery in Excel.
Current status: We're investigating a potential issue with Microsoft 365 apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1169016 - Affected users may be unable to access Microsoft 365 services and features
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Oct 9 14:10:00 2025 |
|---|
| End Time: | Thu Oct 9 14:50:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 31 15:56:24 2025 |
|---|
| Root Cause: | The cause of this incident was a misconfiguration of Border Gateway Protocol (BGP) routing policy which applied during the activation of a new peering session between Microsoft and a third-party networking provider in the San Jose area. The correct policy would have balanced egress traffic from Microsoft and the third-party network provider among multiple peering locations within North America, allowing more localized traffic routing and distribution. Due to a latent bug in our policy generation code, the incorrect policy configuration was applied on the networking device during the new peering link turnup. This incorrect policy caused the third-party networking provider to carry less-preferred metrics on the Microsoft network. This resulted in a large volume of egress traffic to our third-party network provider, leading in excessive outbound traffic and congestion at specific locations. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 31 15:56:24 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 16 19:55:48 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Oct 13 19:27:39 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Oct 13 19:20:05 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 9 15:52:06 2025 |
|---|
| Description: | Title: Affected users may be unable to access Microsoft 365 services and features
User impact: Affected users may have been unable to access Microsoft 365 services and features.
More info: Users attempting to access or use features within Microsoft Teams, Exchange Online, Microsoft 365 admin center, and Windows 365 may have been impacted.
Final status: We’ve identified that a portion of network infrastructure in North America was misconfigured, which caused traffic across the region to become unhealthy. We’ve taken mitigating action to rebalance traffic in the affected infrastructure, and we’ve observed service health improve to normal levels across all impacted services.
Scope of impact: Any users in North America attempting to access the services listed in the More info of this communication may have been impacted.
Start time: Thursday, October 9, 2025, at 6:10 PM UTC
End time: Thursday, October 9, 2025, at 6:48 PM UTC
Root cause: The cause of this incident was a misconfiguration of Border Gateway Protocol (BGP) routing policy which applied during the activation of a new peering session between Microsoft and a third-party networking provider in the San Jose area. The correct policy would have balanced egress traffic from Microsoft and the third-party network provider among multiple peering locations within North America, allowing more localized traffic routing and distribution. Due to a latent bug in our policy generation code, the incorrect policy configuration was applied on the networking device during the new peering link turnup. This incorrect policy caused the third-party networking provider to carry less-preferred metrics on the Microsoft network. This resulted in a large volume of egress traffic to our third-party network provider, leading in excessive outbound traffic and congestion at specific locations.
As this change was planned several weeks before the incident, we confirmed that a latent bug in our service did not detect policy generation failures and thus allowed the network link to take traffic when it was not properly configured to do so.
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 or up to all items being completed if sooner, to show the status of the Next Steps. The first update was provided on Friday, October 31, 2025. The next update will be provided by Friday, November 28, 2025.
|
|---|
|
| Time: | Thu Oct 9 15:08:53 2025 |
|---|
| Description: | Quick: While we’re observing service health recovering, we’ve received additional reports of issues accessing the Microsoft 365 admin center related to this issue. We expect these issues to resolve as service health improves.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Oct 9 15:01:38 2025 |
|---|
| Description: | We've taken mitigating action to rebalance traffic to healthy infrastructure and are seeing improvements in service health. We'll continue to closely monitor the service environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Oct 9 14:54:25 2025 |
|---|
| Description: | Title: Affected users may be unable to access Microsoft 365 services and features
User impact: Affected users may be unable to access Microsoft 365 services and features.
More info: Initial reports show issues accessing Microsoft Teams and Exchange Online.
Current status: We're reviewing internal telemetry and traffic patterns to determine a source of impact for reported issues with accessing Microsoft 365, Microsoft teams, and Exchange Online services and features. We're working to rebalance traffic to healthy infrastructure.
Scope of impact: Any users attempting to access the services listed above may be impacted.
Next update by: Thursday, October 9, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Oct 9 14:33:13 2025 |
|---|
| Description: | Title: Affected users may be unable to access Microsoft 365 services and features
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
More info: Initial reports show issues accessing Microsoft Teams and Exchange Online.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
EX1181857 - Some users may have been unable to change photos for Outlook groups
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 25 10:08:00 2025 |
|---|
| End Time: | Fri Oct 31 09:40:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 31 11:44:28 2025 |
|---|
| Root Cause: | A recently enabled change caused a code regression, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 31 10:30:53 2025 |
|---|
| Description: | Title: Some users may have been unable to change photos for Outlook groups
User impact: Users may have been unable to change photos for Outlook groups.
Final status: We've determined that a recently enabled change caused a code regression, which resulted in impact. We've reverted the offending change to mitigate impact and can confirm after a period of monitoring that impact is remediated.
Scope of impact: Users attempting to change photos for Outlook groups may have been impacted.
Start time: Thursday, September 25, 2:08 PM UTC
End time: Friday, October 31, 2025, at 1:40 PM UTC
Root cause: A recently enabled change caused a code regression, which resulted in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 31 08:52:04 2025 |
|---|
| Description: | Title: Some users are unable to change photos for Outlook groups
User impact: Users are unable to change photos for Outlook groups.
Current status: We're continuing our analysis of HTTP Archive format (HAR) logs to isolate the root cause and develop a mitigation plan.
Scope of impact: Users attempting to change photos for Outlook groups may have been impacted.
Next update by: Friday, October 31, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Oct 31 06:41:33 2025 |
|---|
| Description: | Title: Some users are unable to change photos for Outlook groups
User impact: Users are unable to change photos for Outlook groups.
Current status: We're analyzing support provided information to determine our next troubleshooting steps to reach a mitigation plan and root cause analysis.
Scope of impact: Users attempting to change photos for Outlook groups may have been impacted.
Next update by: Friday, October 31, 2025, at 1:00 PM UTC
|
|---|
|
OP1162778 - PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 30 12:42:16 2025 |
|---|
| End Time: | Thu Oct 30 23:46:36 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 30 23:46:56 2025 |
|---|
| Root Cause: | A recently deployed change was preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 30 23:46:56 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users were unable to open DKE files on mobile devices
More info: Additionally, users could not change DKE file sensitivity labels. This occured for users leveraging both iOS and Android devices. There was no impact on other platforms where PowerPoint was supported, such as PPT for Win32.
Final status: We confirmed that the fix has saturated throughout the affected environment. After an extended period of monitoring, we're confident that the issue is resolved.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices was affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
End time: Monday, October 27, 2025, at 12:00 PM UTC
Root cause: A recently deployed change was preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next steps:
- We're assessing our deployment procedures to prevent similar impact stemming from future changes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 28 18:11:48 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users are unable to open DKE files on mobile devices
More info: Additionally, users cannot change DKE file sensitivity labels. This occurs for users leveraging both iOS and Android devices. There is no impact on other platforms where PowerPoint is supported, such as PPT for Win32.
Current status: Our fix is continuing to saturate without issue. We're monitoring for a period to confirm it completes successfully and that impact is resolved for all users.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices is affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
Root cause: A recently deployed change is preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next update by: Thursday, October 30, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Oct 20 14:33:48 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users are unable to open DKE files on mobile devices.
More info: Additionally, users cannot change DKE file sensitivity labels. This occurs for users leveraging both iOS and Android devices. There is no impact on other platforms where PowerPoint is supported, such as PPT for Win32.
Current status: We've completed testing the fix and have begun deployment. We anticipate that it'll fully saturate and resolve impact by our next scheduled update.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices is affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
Root cause: A recently deployed change is preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next update by: Tuesday, October 28, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Oct 13 19:14:36 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users are unable to open DKE files on mobile devices
More info: Additionally, users cannot change DKE file sensitivity labels. This occurs for users leveraging both iOS and Android devices. There is no impact on other platforms where PowerPoint is supported, such as PPT for Win32.
Current status: We're continuing to test the fix within our internal environments and expect it to take an extended period due to the complexity of the proposed solution.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices is affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
Root cause: A recently deployed change is preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next update by: Monday, October 20, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Oct 6 13:10:13 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users are unable to open DKE files on mobile devices
More info: Additionally, users cannot change DKE file sensitivity labels. This occurs for users leveraging both iOS and Android devices. There is no impact on other platforms where PowerPoint is supported, such as PPT for Win32.
Current status: We've developed a code change to address the issue, and it's currently undergoing internal testing to validate its efficacy. While we're unable to provide an estimated time to deployment at this time, we'll aim to provide one as soon as it's available.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices is affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
Root cause: A recently deployed change is preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next update by: Monday, October 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Sep 30 12:46:36 2025 |
|---|
| Description: | Title: PowerPoint users are unable to open double key encryption (DKE) files on mobile devices
User impact: PowerPoint users are unable to open DKE files on mobile devices
More info: Additionally, users cannot change DKE file sensitivity labels. This occurs for users leveraging both iOS and Android devices. There is no impact on other platforms where PowerPoint is supported, such as PPT for Win32.
Current status: We recently deployed a change which prevents users from opening DKE files on PPT for mobile devices or creating DKE labeled files as expected. We're developing a subsequent code change to address the issue. We'll aim to outline an estimated time to deployment at our next scheduled update.
Scope of impact: Any user attempting to open DKE files or change DKE file sensitivity labels in PowerPoint on iOS and Android devices is affected.
Start time: Thursday, September 18, 2025, at 12:00 AM UTC
Root cause: A recently deployed change is preventing users from opening DKE files on mobile devices or changing DKE file sensitivity labels as expected.
Next update by: Monday, October 6, 2025, at 10:00 PM UTC
|
|---|
|
EX1176994 - Some users may be unable to access their Exchange Online email using Outlook for Mac
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Oct 20 12:00:00 2025 |
|---|
| End Time: | Tue Oct 21 16:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Oct 29 23:40:48 2025 |
|---|
| Root Cause: | A recent update to the Exchange ActiveSync (EAS) Allow, Block, Quarantine (ABQ) policy enabled administrators to block Mac devices, expanding upon the previous support for iOS and Android platforms. This enhancement is designed to provide administrators with greater control, allowing them to temporarily or permanently prevent unauthorized devices from synchronizing emails. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 29 23:40:48 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 23:40:22 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 23:40:00 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 28 20:18:30 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Oct 23 06:24:20 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 21 19:11:58 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online email using Outlook for Mac
User impact: Users may have been unable to access their Exchange Online email using Outlook for Mac.
More info: Some users’ Mac devices may have been quarantined, which prohibited impacted users from accessing their email in Outlook for Mac.
Impact is specific to the latest build, 16.102.1018.1.
Final status: We’ve confirmed with reporting users that the issue is now resolved. If you are still experiencing impact, close, then reopen Outlook and wait ten seconds. If you receive an error message that says, “This account has been blocked on this device by your administrator,” please repeat the steps above until you no longer receive the error message.
Scope of impact: This issue impacted users on the latest version (16.102.1018.1) of the Outlook for Mac client.
Start time: Monday, October 20, 2025, at 4:00 PM UTC
End time: Tuesday, October 21, 2025, at 8:30 PM UTC
Root cause: A recent update to the Exchange ActiveSync (EAS) Allow, Block, Quarantine (ABQ) policy enabled administrators to block Mac devices, expanding upon the previous support for iOS and Android platforms. This enhancement is designed to provide administrators with greater control, allowing them to temporarily or permanently prevent unauthorized devices from synchronizing emails.
However, due to a coding error, the update inadvertently caused Mac devices to be treated in the same way as iOS and Android devices. As a result, organizations that had used ABQ policies to block only iOS and Android devices (without intending to block Mac) found that their users were unable to access their Exchange Online email using Outlook for Mac.
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 Oct 21 16:58:20 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online email using Outlook for Mac
User impact: Users may be unable to access their Exchange Online email using Outlook for Mac.
More info: Some users’ Mac devices may be quarantined, which is prohibiting impacted users from accessing their email in Outlook for Mac.
Impact is specific to the latest build, 16.102.1018.1.
Current status: We've reverted the latest build of the Outlook for Mac client to the previous update version, and we’re working with users that reported the problem to test and verify that this rollback mitigates impact as expected.
Scope of impact: This issue impacts users on the latest version (16.102.1018.1) of the Outlook for Mac client.
Start time: Monday, October 20, 2025, at 4:00 PM UTC
Root cause: The latest build release contains a code issue which is causing the Exchange ActiveSync policy to block the Outlook for Mac client, resulting in the impact.
Next update by: Wednesday, October 22, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Oct 21 13:39:21 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online email using Outlook for Mac
User impact: Users may be unable to access their Exchange Online email using Outlook for Mac.
More info: Some users’ Mac devices may be quarantined, which is prohibiting impacted users from accessing their email in Outlook for Mac.
Impact is specific to the latest build, 16.102.1018.1.
Current status: We've confirmed the latest build version contains a code issue which is causing the Exchange ActiveSync policy to block the Outlook for Mac client, resulting in the impact. We're reverting the latest build to resolve the issue.
Scope of impact: This issue impacts users on the latest version (16.102.1018.1) of the Outlook for Mac client.
Start time: Monday, October 20, 2025, at 4:00 PM UTC
Root cause: The latest build release contains a code issue which is causing the Exchange ActiveSync policy to block the Outlook for Mac client, resulting in the impact.
Next update by: Tuesday, October 21, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 12:39:10 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online email using Outlook for Mac
User impact: Users may be unable to access their Exchange Online email using Outlook for Mac.
More info: Some users’ Mac devices may be quarantined, which is prohibiting impacted users from accessing their email in Outlook for Mac.
Impact is specific to the latest build, 16.102.1018.1.
Current status: We're reviewing some affected user profiles and Outlook logs to determine our next troubleshooting steps.
Scope of impact: This issue impacts users on the latest version (16.102.1018.1) of the Outlook for Mac client.
Next update by: Tuesday, October 21, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Oct 21 12:04:11 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online email using Outlook for Mac
User impact: Users may be unable to access their Exchange Online email using Outlook for Mac.
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.
|
|---|
|
TM1178840 - Some users may be unable to open the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 21 12:34:00 2025 |
|---|
| End Time: | Wed Oct 29 21:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Oct 29 21:50:03 2025 |
|---|
| Root Cause: | A recently merged code change introduced a code issue, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 29 21:49:53 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may have been unable to open the Microsoft Teams desktop client.
More info: Users who had characters in their user profile path that couldn’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may have been unable to open Microsoft Teams.
Final status: After an extended period of monitoring the affected portion of the environment following the deployment of our fix, we’ve confirmed that impact has been remediated.
Scope of impact: Some users who attempted to open the Microsoft Teams desktop client who had characters in their user profile path that couldn’t be expressed in the ANSI code page may have been impacted.
Start time: Tuesday, October 21, 2025, at 4:34 PM UTC
End time: Thursday, October 30, 2025, at 1:00 AM UTC
Root cause: A recently merged code change introduced a code issue, which resulted in impact.
Next steps: We'll review our code merging validation process to identify possible refinement in order to prevent similar instances of this issue in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 29 17:26:23 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may be unable to open the Microsoft Teams desktop client.
More info: Users who have characters in their user profile path that can’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may be unable to open Microsoft Teams.
As a workaround, users may be able to open Microsoft Teams using Microsoft Teams on the web.
Current status: A fix to the code issue introduced by a recently merged code change has rolled out to the majority of affected users. We're continuing to monitor its progress in the remaining affected portion of the environment to ensure that the service has definitively returned to a healthy state.
Scope of impact: Some users attempting to open the Microsoft Teams desktop client who have characters in their user profile path that can’t be expressed in the ANSI code page may be impacted.
Start time: Tuesday, October 21, 2025, at 4:34 PM UTC
Root cause: A recently merged code change introduced a code issue, resulting in impact.
Next update by: Thursday, October 30, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Oct 27 17:03:23 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may be unable to open the Microsoft Teams desktop client.
More info: Users who have characters in their user profile path that can’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may be unable to open Microsoft Teams.
As a workaround, users may be able to open Microsoft Teams using Microsoft Teams on the web.
Current status: The fix has rolled out to 50 percent of affected users, and we're continuing to monitor as it progresses. We expect the impact for all users to be resolved by the next scheduled update.
Scope of impact: Some users attempting to open the Microsoft Teams desktop client who have characters in their user profile path that can’t be expressed in the ANSI code page may be impacted.
Start time: Tuesday, October 21, 2025, at 4:34 PM UTC
Root cause: A recently merged code change introduced a code issue, resulting in impact.
Next update by: Wednesday, October 29, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 17:43:57 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may be unable to open the Microsoft Teams desktop client.
More info: Users who have characters in their user profile path that can’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may be unable to open Microsoft Teams.
As a workaround, users may be able to open Microsoft Teams using Microsoft Teams on the web.
Current status: We've completed the development of a fix and expect the deployment to initiate by the next scheduled communications update.
Scope of impact: Some users attempting to open the Microsoft Teams desktop client who have characters in their user profile path that can’t be expressed in the ANSI code page may be impacted.
Start time: Tuesday, October 21, 2025, at 4:34 PM UTC
Root cause: A recently merged code change introduced a code issue, resulting in impact.
Next update by: Monday, October 27, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 09:51:06 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may be unable to open the Microsoft Teams desktop client.
More info: Users who have characters in their user profile path that can’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may be unable to open Microsoft Teams.
As a workaround, users may be able to open Microsoft Teams using Microsoft Teams on the web.
Current status: We've identified that a recently merged code change introduced a code issue, resulting in impact. Our team is actively working to validate a code change to address this, and we’re aiming to have completed this by our next scheduled update.
Scope of impact: Some users attempting to open the Microsoft Teams desktop client who have characters in their user profile path that can’t be expressed in the ANSI code page may be impacted.
Start time: Tuesday, October 21, 2025 at 4:34 PM UTC
Root cause: A recently merged code change introduced a code issue, resulting in impact.
Next update by: Friday, October 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 07:57:07 2025 |
|---|
| Description: | Title: Some users may be unable to open the Microsoft Teams desktop client
User impact: Users may be unable to open the Microsoft Teams desktop client.
More info: Users who have characters in their user profile path that can’t be expressed in the Application and Network Seamlessly Integrated (ANSI) code page may be unable to open Microsoft Teams.
As a workaround, users may be able to open Microsoft Teams using Microsoft Teams on the web.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users attempting to open the Microsoft Teams desktop client who have characters in their user profile path that can’t be expressed in the ANSI code page may be impacted.
Next update by: Friday, October 24, 2025, at 2:00 PM UTC
|
|---|
|
TM1181113 - Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 23 20:18:00 2025 |
|---|
| End Time: | Tue Oct 28 14:29:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 28 15:54:55 2025 |
|---|
| Root Cause: | A recent service update contained a configuration issue for processes facilitating the Planner tab link creation process, resulting in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 28 14:58:44 2025 |
|---|
| Description: | Title: Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels
User impact: Users couldn't add Planner tabs or access newly created tabs in Microsoft Teams channels.
More info: Users received an error stating "There was a problem reaching this app. Retry".
As a workaround, users could directly open the Planner app, create a plan, and then share it with the group in the appropriate Microsoft Teams channel.
Users will need to recreate any Planner app tabs that failed during the impact period.
Final status: We've determined that a recent service update contained a configuration issue for processes facilitating the Planner tab link creation process, resulting in the impact. We've redirected affected requests to portion of infrastructure that hadn't receive this update to expedite resolution for your users. Any Planner tabs creating during the impact period will need to be recreated for them to function as expected.
Scope of impact: Your organization was affected by this event, and any user attempting to create a Planner tab or access a newly created Planner tab in a Microsoft Teams channel was affected.
Start time: Friday, October 24, 2025, at 12:18 AM UTC
End time: Tuesday, October 28, 2025, at 6:29 PM UTC
Root cause: A recent service update contained a configuration issue for processes facilitating the Planner tab link creation process, resulting in the impact.
Next steps:
- We're reviewing our service update testing and validation process to identify configuration prior to deployment and to avoid similar issues that could impact Planner tab creation actions.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 28 13:26:14 2025 |
|---|
| Description: | Title: Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels
User impact: Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels.
More info: Users receive an error stating "There was a problem reaching this app. Retry".
As a workaround, users can directly open the Planner app, create a plan, and then share it with the group in the appropriate Microsoft Teams channel.
Current status: We've reviewing recent updates that may be contributing to this issue. Once we've identified the problem, we'll evaluate our resolution options to allow users to create and access newly created Planner tabs.
Scope of impact: Your organization is affected by this event, and any user attempting to create a Planner tab or access a newly created Planner tab in a Microsoft Teams channel is affected.
Next update by: Tuesday, October 28, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Oct 28 12:25:48 2025 |
|---|
| Description: | Title: Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels
User impact: Users can't add Planner tabs or access newly created tabs in Microsoft Teams channels.
More info: Users receive an error stating "There was a problem reaching this app. Retry".
As a workaround, users can directly open the Planner app, create a plan, and then share it with the group in the appropriate Microsoft Teams channel.
Current status: We're investigating a potential issue with Planner in Microsoft Teams and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
EX1181079 - Users’ searches for email messages may return no results in the Outlook desktop and web clients
| Status: | serviceRestored |
|---|
| Start Time: | Sun Oct 26 05:08:00 2025 |
|---|
| End Time: | Tue Oct 28 14:22:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Oct 28 15:54:49 2025 |
|---|
| Root Cause: | A recent feature update to the search service caused search data to be unreadable by the Outlook desktop and web clients, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 28 15:54:49 2025 |
|---|
| Description: | Title: Users’ searches for email messages may return no results in the Outlook desktop and web clients
User impact: Users’ searches for email messages may have returned no results in the Outlook desktop and web clients.
Final status: We've identified that a recent feature update to the search service is causing search data to be unreadable by the Outlook desktop and web clients, resulting in impact. We've stopped this update from its ongoing deployment and reverted it in the affected environment to remediate impact. We've validated using internal telemetry and affected user confirmation that impact is remediated.
Scope of impact: Any user attempting to search for email messages in the Outlook desktop and web clients may have been impacted.
Start time: Sunday, October 26, 2025, at 9:08 AM UTC
End time: Tuesday, October 28, 2025, at 6:22 PM UTC
Root cause: A recent feature update to the search service caused search data to be unreadable by the Outlook desktop and web clients, resulting in impact.
Next steps:
- We're reviewing the offending feature update to identify the specific changes that caused impact, allowing us to make corrections and redeploy a new version of this update.
- We're updating our feature update validation procedures to better detected and prevent similar issues before they cause impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 28 14:08:18 2025 |
|---|
| Description: | Title: Users’ searches for email messages may return no results in the Outlook desktop and web clients
User impact: Users’ searches for email messages may return no results in the Outlook desktop and web clients.
Current status: We've received the additional network traces and discovered that our search service is providing results that the Outlook desktop and web clients can't parse. We're investigating recent changes to the service search and the network traces to determine the root cause and a strategy that remediates impact.
Scope of impact: Any user attempting to search for email messages in the Outlook desktop and web clients may be impacted.
Next update by: Tuesday, October 28, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 12:31:42 2025 |
|---|
| Description: | Title: Users’ searches for email messages may return no results in the Outlook desktop and web clients
User impact: Users’ searches for email messages may return no results in the Outlook desktop and web clients.
Current status: We've gathered and are investigating HAR logs from affected users, but they haven't provided the details we need to identify the root cause. We're seeking network traces from affected users to help identify the root cause and a strategy that remediates impact.
Scope of impact: Any user attempting to search for email messages in the Outlook desktop and web clients may be impacted.
Next update by: Tuesday, October 28, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 11:26:24 2025 |
|---|
| Description: | Title: Users’ searches for email messages may return no results in the Outlook desktop and web clients
User impact: Users’ searches for email messages may return no results in the Outlook desktop and web clients.
Current status: We're gathering HTTP Archive format (HAR) logs from affected users to identify why users’ searches for email messages may return no results in the Outlook desktop and web clients.
Scope of impact: Any user attempting to search for email messages in the Outlook desktop and web clients may be impacted.
Next update by: Tuesday, October 28, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Oct 28 10:32:04 2025 |
|---|
| Description: | Title: We’re looking into a potential problem with the search feature in Outlook and Outlook on the web
User impact: We’re checking for potential impact to your users.
Current status: We’re investigating a potential issue and checking for impact to your organization. We’ll provide an update within an hour.
|
|---|
|
EX1102371 - Users may be unable to access some Exchange Online archive mailboxes
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 23 09:00:00 2025 |
|---|
| End Time: | Mon Oct 27 18:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 27 18:32:24 2025 |
|---|
| Root Cause: | As part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 27 18:31:15 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may have been unable to access some Exchange Online archive mailboxes.
More info: This issue occurred when routine mailbox database maintenance for archive mailboxes relocated the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may have persisted both during the maintenance move and after the move. The problem impacted archive mailbox access through any Exchange Online connection method.
Final status: We've confirmed the fix has completed its deployment and been activated in all environments, confirming mitigation with affected users and service telemetry.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may have encountered this issue if their primary and archive mailboxes weren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
End time: Monday, October 27, 2025, at 10:00 PM UTC
Root cause: As part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact.
Next steps:
- We're continuing our analysis of the impacting maintenance procedures to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 23 10:58:00 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: We've enabled the fix within a portion of the affected environment and validated its efficacy in remediating the impact. We're enabling the fix for all affected users and anticipate this process will complete by our next scheduled communications update.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Estimated time to resolve: We anticipate the fix will be enabled for all affected users by Tuesday, October 28, 2025, at 12:00 AM UTC.
Root cause: As part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact.
Next update by: Tuesday, October 28, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Oct 16 17:13:34 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: We've completed the deployment of the fix and we're enabling it within a portion of the affected environment to validate that it resolves the impact. We'll aim to provide a timeline for the fix to be enabled for all affected users by our next scheduled communications update.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Root cause: As part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact.
Next update by: Friday, October 24, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Oct 9 17:00:21 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: We've identified that as part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact. Our aforementioned fix, designed to allow the archive mailboxes to remain accessible while in a different location from the primary mailbox, is continuing to saturate the affected environments. Once the fix has completed deployment, we'll enable the fix for the affected users. We'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Root cause: As part of routine mailbox database maintenance, the affected archive mailboxes were migrated to a separate portion of database service infrastructure from the primary, preventing users from accessing the archive mailbox and causing impact.
Next update by: Thursday, October 16, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 2 18:13:44 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: As we progress with our root cause analysis and confirm the source for this event, we completed our fix validations and deployed our solutions. We're projecting that deployments will be complete and impact to be remediated by the third week of October, and we expect a more detailed timeline to be available by our next scheduled communication update.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Thursday, October 9, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Sep 18 17:13:44 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: Our fix validations are progressing and scheduled to be complete by our next scheduled communication update. At said time, we're expecting a timeline for the deployment of our fix and the remediation of impact.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Thursday, October 2, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Sep 11 16:43:16 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: Our validation efforts are taking longer than initially anticipated, and we're continuing to verify the efficacy of our secondary fix within our testing environment for an extended period. We expect to have a more substantial update by Thursday, September 25, 2025, and will provide an updated timeline as one becomes available.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailboxes aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Thursday, September 18, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 18 15:34:14 2025 |
|---|
| Description: | Title: Users may be unable to access some Exchange Online archive mailboxes
User impact: Users may be unable to access some Exchange Online archive mailboxes.
More info: This issue occurs when routine mailbox database maintenance for archive mailboxes relocates the archive to a different portion of Active Directory infrastructure from the primary mailbox. Impact may persist both during the maintenance move and after the move. The problem impacts archive mailbox access through any Exchange Online connection method.
Current status: We've completed the validations of our secondary fix and we're deploying it to our internal test environment to further confirm its' ability to safely resolve this issue. We expect that this validation process may take until Wednesday, September 3, 2025. Once confirmed, we'll begin deploying the fix to all affected users and will provide an estimated timeline for that process once available.
Scope of impact: Any user attempting to access their Exchange Online archive mailbox may encounter this issue if their primary and archive mailbox aren't located on the same portion of Active Directory infrastructure.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Thursday, September 11, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 4 15:05:16 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our server-side fix to update the method that users’ cache is generated upon loading the affected mailboxes has completed and saturated to affected environments, but also revealed additional code discrepancies that will need to be addressed by our supplementary fix. To ensure complete remediation, the internal validations for our secondary fix's deployment has been delayed to allow for additional review and testing so we can ensure it doesn't produce any unexpected problems in the service. We aim to provide a timeline for our secondary fix deployment and the remediation of impact at the time of our next scheduled update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Monday, August 18, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jul 28 15:28:24 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our server-side fix to update the method that users’ cache is generated upon loading the affected mailboxes has completed approximately 93 percent of the necessary deployment, and we're monitoring its completion. While progressing with our root cause analysis, the internal validations for our secondary fix's deployment are also progressing so we can ensure it doesn't produce any unexpected problems in the service. We'll provide a timeline for our secondary fix deployment and the remediation of impact once they have become available.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Monday, August 4, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 16:39:03 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Validation of a server-side fix to change to the way the user cache is generated upon loading the affected mailboxes is complete and has begun deploying. Validation of a second client-side fix, on which mitigation for Outlook on the web is dependent, is progressing. We're continuing to confirm the efficacy of the client-side fix, and we'll provide a timeline for deployment once this process is complete.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Monday, July 28, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 15:00:54 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We’ve completed developing the previously mentioned change to the way the user cache is generated upon loading the affected mailboxes, and we’re validating the change for efficacy before beginning deployment to the impacted environment. We’re aiming to complete the validation process and provide an estimated timeline for deployment and remediation in our next scheduled communication update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, July 23, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jul 15 15:16:04 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: While we continue to investigate the source of the impact, we're developing a possible fix that will change the way user cache is generated upon loading the affected mailboxes. This fix is only being developed for Outlook on the web at this time and its efficacy will be tested before proceeding with further development. We expect to complete testing of this possible mitigation by the time of our next update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 15:34:55 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're continuing to coordinate with affected users to complete the migration for those whose migrations were already initiated and then entered a stuck state, and in parallel we’re proceeding with our efforts to create a long-term fix to prevent the mailboxes from entering the stuck state again.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, July 15, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 15:55:48 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with affected users to complete the migration for those whose migrations were already initiated and then entered a stuck state to assist us in remediating impact for all affected users. Simultaneously, we’re working internally to create a fix that will prevent similar impact scenarios from occurring in future.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 10, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 26 14:55:00 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're preparing to initiate the operation to expedite the impacted migration while we continue to coordinate with affected users to obtain the previously mentioned list of priority users. In parallel, we're preparing a secondary operation to revert the migration for users whose migrations were already initiated and then entered a stuck state to assist us in remediating impact for all affected users.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 3, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 25 15:28:47 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with your representatives to confirm a list of priority users who need their mailbox migration expedited along with discussing potential mitigation paths while we work to investigate and confirm the underlying issue.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, June 26, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 24 19:43:38 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We've completed the pause of the mailbox migration and we're continuing to work with impacted users to confirm a list of priority users who need their mailbox migration expedited, and to discuss our remediation strategy.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, June 25, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 16:35:28 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're pausing the current mailbox migration for some users while we work with them to discuss potential mitigation paths. Simultaneously, we're confirming a list of priority users who need their mailbox migration expedited to bypass high impact scenarios while we work to investigate and confirm the underlying root cause of impact.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, June 25, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 24 14:43:26 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with some affected users to discuss potential mitigation paths and what actions we can take to resolve impact for affected users while we work to investigate and resolve the underlying root cause.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 12:51:58 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our process to move the affected archive and primary mailboxes to the same forest to alleviate impact in the short term is ongoing and we aim to provide a timeline for this migration as one becomes available. Simultaneously, we’re analyzing Fiddler traces for working and non-working mailbox authentication requests to better understand the underlying root cause and what steps we can take to resolve impact.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 10:32:38 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: While we progress with our analysis of diagnostic data to isolate the root cause, we've initiated a process to manually relocate the archive and primary mailboxes to the same forest to alleviate impact in the short term.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 08:49:12 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're analyzing provided server and HTTP Archive format (HAR) logs to isolate the root cause and formulate a mitigation plan.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 3:00 PM UTC
|
|---|
|
CP1180735 - Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Sun Oct 26 19:44:00 2025 |
|---|
| End Time: | Mon Oct 27 13:16:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Oct 27 18:17:12 2025 |
|---|
| Root Cause: | The portion of service infrastructure responsible for facilitating access to the Copilot app and for Copilot features within Outlook was operating in a suboptimal state. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 27 18:17:12 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may have received timeouts when attempting to use or access Copilot.
More info: Impact occurred for the Copilot app and for Copilot features within Outlook.
Final status: We've reviewed the portion of service infrastructure responsible for facilitating access to the Copilot app and for Copilot features within Outlook and determined that it was operating in a suboptimal state. After an extended period of monitoring, we've confirmed that our efforts to rebalance the request traffic and reverse recent service updates remediated the impact.
Scope of impact: Any user attempting to use or access the Copilot app or Copilot features within Outlook may have been impacted.
Start time: Sunday, October 26, 2025, at 11:44 PM UTC
End time: Monday, October 27, 2025, at 5:16 PM UTC
Root cause: The portion of service infrastructure responsible for facilitating access to the Copilot app and for Copilot features within Outlook was operating in a suboptimal state.
Next steps:
- We're reviewing the portion of affected infrastructure to isolate the reason it was operating in a suboptimal state, so that we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 27 17:38:36 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may receive timeouts when attempting to use or access Copilot.
More info: Impact occurs for the Copilot app and for Copilot features within Outlook.
Current status: While we continue to investigate the root cause, we're reviewing our service health monitoring to confirm that reversing the recent service update and rebalancing the request traffic remediated the impact as expected.
Scope of impact: Any user attempting to use or access the Copilot app or Copilot features within Outlook may be impacted.
Start time: Sunday, October 26, 2025, at 11:44 PM UTC
Next update by: Monday, October 27, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 14:50:41 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may receive timeouts when attempting to use or access Copilot.
More info: Impact occurs for the Copilot app and for Copilot features within Outlook.
Current status: Our service health telemetry continues to reflect recovery. Our reversion of the recent service update to remediate the impact for the remaining affected users is still ongoing.
Scope of impact: Any user attempting to use or access the Copilot app or Copilot features within Outlook may be impacted.
Start time: Sunday, October 26, 2025, at 11:44 PM UTC
Next update by: Monday, October 27, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 12:49:01 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may receive timeouts when attempting to use or access Copilot.
More info: Impact occurs for the Copilot app and for Copilot features within Outlook.
Current status: Our service health telemetry indicates that the number of timeouts are decreasing since rebalancing the request traffic. While we continue to monitor the recovery, we're reverting a recent service update to further remediate the impact. In tandem, our investigation to isolate the root cause is ongoing.
Scope of impact: Any user attempting to use or access the Copilot app or Copilot features within Outlook may be impacted.
Start time: Sunday, October 26, 2025, at 11:44 PM UTC
Next update by: Monday, October 27, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 11:57:54 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may receive timeouts when attempting to use or access Copilot.
More info: Impact occurs for the Copilot app and for Copilot features within Outlook.
Current status: Our service health monitoring alerted us to timeouts occurring when users attempt to use or access Copilot. While we continue to investigate the portion of service infrastructure responsible for facilitating access to Copilot, we've rebalanced request traffic to determine whether this remediates the impact.
Scope of impact: Any user attempting to use or access the Copilot app or Copilot features within Outlook may be impacted.
Next update by: Monday, October 27, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 11:50:50 2025 |
|---|
| Description: | Title: Some users may receive timeouts when attempting to use or access Microsoft Copilot (Microsoft 365)
User impact: Users may receive timeouts when attempting to use or access Copilot.
More info: Impact occurs for the Copilot app and for Copilot features within Outlook.
Current status: We're investigating a potential issue with accessing and using the Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1180739 - Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 22 16:34:00 2025 |
|---|
| End Time: | Mon Oct 27 16:30:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 27 17:30:37 2025 |
|---|
| Root Cause: | A recent update contained a misconfiguration to the policy assignments logic and mistakenly deployed the new audit baseline logic before a Graph API update that it was dependent upon, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 27 17:30:37 2025 |
|---|
| Description: | Title: Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security
User impact: Admins couldn't load Security Baseline UX or modify assignments for policies under Endpoint Security.
More info: This specifically impacted editing endpoint security policy assignments and loading any security baselines in the Microsoft Intune admin center.
When making changes to policy assignments, admins received a message that these changes were successful, but the changes weren't applied.
Admins could have created new endpoint security policy assignments with the needed Microsoft Entra groups as a work around for adding these groups to existing policy assignments.
Final status: We've reverted the offending update and confirmed from our internal telemetry data that impact is remediated. Admins will need to log out and back into the Microsoft Intune admin center to revert to previous healthy version and remediate impact.
Scope of impact: Your organization was affected by this event, and any admin attempting to load the Security Baseline UX or modify Endpoint Security policy assignments was impacted.
Start time: Wednesday, October 22, 2025, at 8:34 PM UTC
End time: Monday, October 27, 2025, at 8:30 PM UTC
Root cause: A recent update contained a misconfiguration to the policy assignments logic and mistakenly deployed the new audit baseline logic before a Graph API update that it was dependent upon, resulting in impact.
Next steps:
- We're reviewing our service update validation procedures to improve the detection of similar misconfigurations and early deployments before they cause impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 27 16:19:23 2025 |
|---|
| Description: | Title: Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security
User impact: Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security.
More info: This specifically impacts editing endpoint security policy assignments and loading any security baselines in the Microsoft Intune admin center.
When making changes to policy assignments, admins receive a message that these changes were successful, but the changes aren’t applied.
Admins can create new endpoint security policy assignments with the needed Microsoft Entra groups as a work around for adding these groups to existing policy assignments.
Current status: The process to revert the offending update is ongoing, but we expect it will complete and remediate impact by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any admin attempting to load the Security Baseline UX or modify Endpoint Security policy assignments is impacted.
Start time: Wednesday, October 22, 2025, at 8:34 PM UTC
Root cause: A recent update contains a misconfiguration to the policy assignments logic and was mistakenly deployed the new audit baseline logic before a Graph API update that it’s dependent upon, resulting in impact.
Next update by: Monday, October 27, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Oct 27 14:15:59 2025 |
|---|
| Description: | Title: Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security
User impact: Admins can’t load Security Baseline UX or modify assignments for policies under Endpoint Security.
More info: This specifically impacts editing endpoint security policy assignments and loading any security baselines in the Microsoft Intune admin center.
When making changes to policy assignments, admins will receive a message that these changes were successful, but the changes will not be applied.
Admins can create new endpoint security policy assignments with the needed Microsoft Entra groups as a work around for adding these groups to existing policy assignments.
Current status: We've further analyzed the offending update and confirmed that a misconfiguration within prevented the assignment update logic from running, resulting in impact. Additionally, the same update contained UX changes for audit baselines which deployed before a Graph API update that the audit baseline changes were dependent on, causing the listing page to fail. We're continuing to revert the offending update to remediate impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to add or remove Microsoft Entra groups to or from endpoint security policy assignments in the Microsoft Intune admin center is impacted.
Start time: Wednesday, October 22, 2025, at 8:34 PM UTC
Root cause: A recent update contains a misconfiguration to the policy assignments logic and mistakenly deployed the new audit baseline logic before a Graph API update it is dependent upon, resulting in impact.
Next update by: Monday, October 27, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Oct 27 12:40:27 2025 |
|---|
| Description: | Title: Admins can’t add or remove Microsoft Entra groups to existing policy assignments in the Microsoft Intune admin center
User impact: Admins can’t add or remove Microsoft Entra groups to existing policy assignments in the Microsoft Intune admin center.
More info: This specifically impacts editing endpoint security policy assignments.
Admins can create new endpoint security policy assignments with the needed Microsoft Entra groups as a work around for adding these groups to existing policy assignments.
Current status: We've identified a recent update to the settings catalogue based endpoint security profiles that may contain a code issue and could be the cause of impact. We're reverting this update as a potential method of remediating impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to add or remove Microsoft Entra groups to or from endpoint security policy assignments in the Microsoft Intune admin center is impacted.
Next update by: Monday, October 27, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 12:15:18 2025 |
|---|
| Description: | Title: Admins can’t add or remove Microsoft Entra groups to existing policy assignments in the Microsoft Intune admin center
User impact: Admins can’t add or remove Microsoft Entra groups to existing policy assignments in the Microsoft Intune admin center.
More info: This specifically impacts editing endpoint security policy assignments.
Current status: We're investigating a potential issue in the Microsoft Intune admin center and are checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1173828 - Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 14 05:18:00 2025 |
|---|
| End Time: | Mon Oct 20 22:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 27 15:55:58 2025 |
|---|
| Root Cause: | A bug contained in a recent package intended to update the appearance of the Outlook suite header created this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 27 15:43:14 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may have been unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Final status: We've determined that a recent package intended to update the appearance of the Outlook suite header contained a bug that created this impact. A new version of this update, without the bug, was then implemented to update the suite header without any residual impact.
Scope of impact: This issue could have potentially affected any user when accessing shared mailboxes from Outlook on the web.
Start time: Tuesday, October 14, 2025, at 9:18 AM UTC
End time: Tuesday, October 21, 2025, at 2:00 AM UTC
Root cause: A bug contained in a recent package intended to update the appearance of the Outlook suite header created this impact.
Next steps:
- We're reviewing the bug in a recent package intended to update the appearance of the Outlook suite header to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 21 12:16:26 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: While we were in the process of determining if this issue was related to another ongoing event, a subset of affected users reported the issue is no longer occurring. We suspect the issue was caused by a recent service update that's been reverted, and we're working to gather more details on the suspected update while we monitor the service to ensure remediation.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Monday, October 27, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Oct 20 12:19:21 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: While we've been unable to reproduce this issue internally, we've identified a potential fix that's being developed for a similar issue. We're validating how these two issues might be related and if the fix will remediate impact for both.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Tuesday, October 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Oct 17 14:48:46 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: Due to the complexity of this impact scenario, we’re continuing our ongoing review of the error logs. In addition, we’re attempting to internally reproduce the issue in our test environment to gather vital diagnostic data that will aid in isolating the cause and identifying an appropriate remediation action.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Monday, October 20, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 17:28:31 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: We’re continuing our assessment of the errors observed when users attempt to access shared mailboxes in Outlook on the web, as we work to isolate the cause of this issue and determine an appropriate remediation action.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Friday, October 17, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 13:07:37 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: We're analyzing 404 "Bad request" errors seen when users attempt to access the shared mailboxes to isolate a root cause and to determine our next steps.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Thursday, October 16, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Oct 16 12:30:16 2025 |
|---|
| Description: | Title: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes
User impact: Users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes.
Current status: We're received reports that users may be unexpectedly signed out from Outlook on the web when accessing shared mailboxes. We're working with some reporting users to validate the current impact scenario to determine our next troubleshooting steps.
Scope of impact: This issue can potentially affect any user when accessing shared mailboxes from Outlook on the web.
Next update by: Thursday, October 16, 2025, at 5:30 PM UTC
|
|---|
|
EX1177475 - Some admins using PowerShell to create unified groups may receive an error indicating creation failure
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 29 05:54:00 2025 |
|---|
| End Time: | Wed Oct 22 16:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 27 14:06:51 2025 |
|---|
| Root Cause: | A recent change to optimize the configure API leveraged in this scenario, by moving the calls from EWS to REST, caused a group fetching issue that led to the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 27 14:06:51 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may have received an error indicating creation failure.
More info: Despite the error message, group creation didn't actually fail for admins and the groups were viewable in the admin center.
Final status: Following our change reversion our internal service telemetry has validated that the offending group fetching problem has been addressed and that impact has been remediated.
Scope of impact: Some admins may have been unable to create unified groups through PowerShell.
Start time: Monday, September 29, 2025, at 9:54 AM UTC
End time: Wednesday, October 22, 2025, at 8:30 PM UTC
Root cause: A recent change to optimize the configure API leveraged in this scenario, by moving the calls from EWS to REST, caused a group fetching issue that led to the impact.
Next steps:
- We're further analyzing the introduced group fetching issue to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 24 12:55:30 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may receive an error indicating creation failure.
More info: Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.
Current status: We’re awaiting validation from some reporting users to confirm if the issue is still occurring as we continue to review options to expedite the deployment of the long-term solution.
Scope of impact: Some admins may be unable to create unified groups through PowerShell.
Start time: Monday, September 29, 2025, at 9:54 AM UTC
Root cause: A recent change to optimize the configure API leveraged in this scenario, by moving the calls from EWS to REST, caused a group fetching issue that led to the impact.
Next update by: Monday, October 27, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Oct 22 13:44:52 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may receive an error indicating creation failure.
More info: Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.
Current status: We’ve determined that a recent change to optimize the configure API leveraged in this scenario by moving from EWS to REST caused a group fetching issue that led to the impact. We’ve rolled back the offending change to provide impact relief and are developing a fix to add retries in this scenario that should fully resolve this issue. We’re validating with your representative to confirm whether the issue is still occurring as we review options to expedite the deployment of the long-term solution.
Scope of impact: Some admins may be unable to create unified groups through PowerShell.
Start time: Monday, September 29, 2025, at 9:54 AM UTC
Root cause: A recent change to optimize the configure API leveraged in this scenario, by moving the calls from EWS to REST, caused a group fetching issue that led to the impact.
Next update by: Friday, October 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 04:51:08 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may receive an error indicating creation failure.
More info: Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.
Current status: We’re continuing to review reproduction details, support provided information, and error logs to help identify the root cause and develop a mitigation plan.
Scope of impact: Some admins may be unable to create unified groups through PowerShell.
Next update by: Wednesday, October 22, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 03:19:21 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may receive an error indicating creation failure.
More info: Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.
Current status: We’ve reproduced the issue in our internal environment and are reviewing the provided case details and error logs, to help pinpoint the root cause and develop a mitigation plan.
Scope of impact: Some admins may be unable to create unified groups through PowerShell.
Next update by: Wednesday, October 22, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Oct 22 02:09:36 2025 |
|---|
| Description: | Title: Some admins using PowerShell to create unified groups may receive an error indicating creation failure
User impact: Admins using PowerShell to create unified groups may receive an error indicating creation failure.
More info: Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.
Current status: We received reports of admins receiving errors when creating unified groups using PowerShell. We're reviewing the provided case details and error logs to better understand what's causing the unintentional error message to appear and to help develop our next troubleshooting steps.
Scope of impact: Some admins may be unable to create unified groups through PowerShell.
Next update by: Wednesday, October 22, 2025, at 8:00 AM UTC
|
|---|
|
WP1178466 - Users intermittently can't launch Cloud PC instances from the Windows 365 portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 23 10:38:00 2025 |
|---|
| End Time: | Thu Oct 23 15:40:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 23 17:00:49 2025 |
|---|
| Root Cause: | Two service deployments overlapped in the affected infrastructure, which caused the service versions to become simultaneously changed. Because of this, the Windows 365 portal was attempting to load an outdated service version that no longer existed, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 23 16:29:39 2025 |
|---|
| Description: | Title: Users intermittently may be unable launch Cloud PC instances from the Windows 365 portal
User impact: Users intermittently may have been unable to launch Cloud PC instances from the Windows 365 portal.
More info: As a workaround, users could have tried refreshing the Windows 365 portal as this issue was intermittent. Alternatively, users could have tried this process from the Azure Virtual Desktop (AVD) web client portal instead.
Final status: We determined this issue was due to two service deployments atypically overlapping, as an earlier scheduled deployment on the affected infrastructure took longer than originally expected to complete. This caused two versions of the service to simultaneously get changed, which resulted in the portal attempting to load an outdated service version that no longer existed. We monitored this earlier deployment's completion and confirmed that service was restored once the overlap ended.
Scope of impact: Users were intermittently unable to launch Cloud PC instances in the Windows 365 portal.
Start time: Thursday, October 23, 2025, at 2:38 PM UTC
End time: Thursday, October 23, 2025, at 7:40 PM UTC
Root cause: Two service deployments overlapped in the affected infrastructure, which caused the service versions to become simultaneously changed. Because of this, the Windows 365 portal was attempting to load an outdated service version that no longer existed, which resulted in impact.
Next steps:
-We're reviewing our deployment pipeline scheduling processes for updating our services, in order to avoid deployment overlaps such as this and prevent similar service incidents from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 23 15:44:19 2025 |
|---|
| Description: | Title: Users may be intermittently unable to launch Clouds PC instances from the Windows 365 portal
User impact: Users may be intermittently unable to launch Clouds PC instances from the Windows 365 portal.
More info: As a workaround, users can try refreshing the Windows 365 portal as this issue is intermittent. Alternatively, users can try this process from the Azure Virtual Desktop (AVD) web client portal instead.
Current status: We're reviewing error logs from internal reproductions while analyzing overall service health telemetry to investigate this issue's root cause and explore possible mitigation strategies.
Scope of impact: Users may be intermittently unable to connect to Cloud PCs through the Windows 365 portal.
Next update by: Thursday, October 23, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 15:18:55 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting user's ability to launch resource app services in the Windows 365 porta
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue in which users may experience errors when trying to launch resource app services in the Windows 365 portal, and we’re checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1176553 - Admins may have been unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
| Status: | serviceRestored |
|---|
| Start Time: | Sun Oct 12 20:00:00 2025 |
|---|
| End Time: | Tue Oct 21 00:42:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 23 01:45:25 2025 |
|---|
| Root Cause: | Recent configuration changes for how admin information is retrieved was causing impact to saving changes to groups in the Microsoft 365 and Exchange Online admin centers. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 22 04:38:14 2025 |
|---|
| Description: | Title: Admins may have been unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
User impact: Admins may have been unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Final status: We've received confirmation from the representatives of some affected users that the impact is remediated.
Scope of impact: This issue may have impacted any admin attempting to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Start time: Monday, October 13, 2025, at 12:00 AM UTC
End time: Tuesday, October 21, 2025, at 4:42 AM UTC
Root cause: Recent configuration changes for how admin information is retrieved was causing impact to saving changes to groups in the Microsoft 365 and Exchange Online admin centers.
Next actions:
- We're reviewing our configuration change procedures to help prevent this problem from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Tue Oct 21 03:31:02 2025 |
|---|
| Description: | Title: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
User impact: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Current status: The fix has been fully deployed and validated internally. We're currently awaiting confirmation from your organization's representatives to verify that impact has been fully remediated.
Scope of impact: Your organization is affected by this event, and the issue impacts any admin users attempting to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Start time: Monday, October 13, 2025, at 12:00 AM UTC
Root cause: Recent configuration changes for how admin information is retrieved is causing impact to saving changes to groups in the Microsoft 365 and Exchange Online admin centers.
Next update by: Wednesday, October 22, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 00:58:25 2025 |
|---|
| Description: | Title: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
User impact: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Current status: After further review, we identified that recent configuration changes for how admin information is retrieved is causing the impact to saving changes to groups. We're rolling back the changes to remediate the impact. We anticipate that the changes will finish rolling back by the next scheduled update time.
Scope of impact: Your organization is affected by this event, and the issue impacts any admin users attempting to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Start time: Monday, October 13, 2025, at 12:00 AM UTC
Root cause: Recent configuration changes for how admin information is retrieved is causing impact to saving changes to groups in the Microsoft 365 and Exchange Online admin centers.
Next update by: Tuesday, October 21, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Oct 20 23:30:08 2025 |
|---|
| Description: | Title: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
User impact: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Current status: We're analyzing system logs to help identify the source of the behavior, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue impacts any admin users attempting to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Next update by: Tuesday, October 21, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Mon Oct 20 23:10:17 2025 |
|---|
| Description: | Title: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers
User impact: Admin users are unable to save changes to groups in the Microsoft 365 and Exchange Online admin centers.
Current status: We're investigating a potential issue with Microsoft 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1177363 - Users may have seen intermittent delays with @mentions for recently added users in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 21 19:38:00 2025 |
|---|
| End Time: | Wed Oct 22 03:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 22 07:00:37 2025 |
|---|
| Root Cause: | A portion of infrastructure supporting the @mention functionality in Microsoft Teams was performing below the expected service threshold, resulting in delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 22 06:55:24 2025 |
|---|
| Description: | Title: Users may have seen intermittent delays with @mentions for recently added users in Microsoft Teams
User impact: Users may have seen intermittent delays with @mentions for recently added users in Microsoft Teams.
Final status: We've successfully processed the remaining backlog and confirmed that issue has been mitigated.
Scope of impact: This issue may have intermittently impacted any user utilizing the @mention functionality for recently added users in Microsoft Teams in the North America West region.
Start time: Tuesday, October 21, 2025, at 11:38 PM UTC
End time: Wednesday, October 22, 2025, at 7:30 AM UTC
Root cause: A portion of infrastructure supporting the @mention functionality in Microsoft Teams was performing below the expected service threshold, resulting in 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: | Wed Oct 22 02:13:01 2025 |
|---|
| Description: | Title: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams
User impact: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams.
Current status: After further analysis, we identified that recent efforts to improve the processing of requests on the affected portion of infrastructure is contributing to the delays. We're allocating additional resources to help process the remaining backlog of requests to remediate the impact. We anticipate that the majority of the backlog will have finished processing by the next scheduled update time.
Scope of impact: This issue may intermittently impact any user utilizing the @mention functionality for recently added users in Microsoft Teams in the North America West region.
Start time: Tuesday, October 21, 2025, at 11:38 PM UTC
Root cause: A portion of infrastructure supporting the @mention functionality in Microsoft Teams is performing below the expected service threshold, resulting in delays.
Next update by: Wednesday, October 22, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Oct 22 00:56:41 2025 |
|---|
| Description: | Title: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams
User impact: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams.
Current status: We rerouted traffic to alternate infrastructure and are seeing improvement in the delays for the @mention function. We're monitoring the backlog of requests to ensure that the impact is remediated.
Scope of impact: This issue may intermittently impact any user utilizing the @mention functionality for recently added users in Microsoft Teams in the North America West region.
Start time: Tuesday, October 21, 2025, at 11:38 PM UTC
Root cause: A portion of infrastructure supporting the @mention functionality in Microsoft Teams is performing below the expected service threshold, resulting in delays.
Next update by: Wednesday, October 22, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 23:02:08 2025 |
|---|
| Description: | Title: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams
User impact: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams.
Current status: We identified a portion of infrastructure supporting the @mention functionality that is performing below the expected service threshold, resulting in delays. We're rerouting traffic to alternate infrastructure to remediate the impact.
Scope of impact: This issue may intermittently impact any user utilizing the @mention functionality for recently added users in Microsoft Teams in the North America West region.
Start time: Tuesday, October 21, 2025, at 11:38 PM UTC
Root cause: A portion of infrastructure supporting the @mention functionality in Microsoft Teams is performing below the expected service threshold, resulting in delays.
Next update by: Wednesday, October 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 22:39:33 2025 |
|---|
| Description: | Title: Users may see intermittent delays with @mentions for recently added users in Microsoft Teams
User impact: Users may see intermittent delays with @mentions for recently added users 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.
|
|---|
|
SP1177136 - Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 16 18:29:00 2025 |
|---|
| End Time: | Tue Oct 21 17:35:57 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 21 17:38:26 2025 |
|---|
| Root Cause: | A recent feature deployment to improve internal engineering consistency and data discrepancies between web parts resulted in an impacting News web part configuration issue. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 21 17:36:25 2025 |
|---|
| Description: | Title: Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages
User impact: Users couldn't aggregate news posts when utilizing a News web part on SharePoint Online pages.
Final status: We've isolated a recent feature update that produced an impacting News web part configuration issue that was preventing users from aggregating news posts when utilizing a News web part on SharePoint Online pages. After enabling our feature change reversion process, our testing with impacted users validated that impact had been remediated.
Scope of impact: This issue may have prevented any user from aggregating news posts when utilizing a News web part on SharePoint Online pages.
Start time: Thursday, October 16, 2025, at 10:29 PM UTC
End time: Tuesday, October 21, 2025, at 8:30 PM UTC
Root cause: A recent feature deployment to improve internal engineering consistency and data discrepancies between web parts resulted in an impacting News web part configuration issue.
Next steps:
- We're further analyzing the offending feature deployment to help improve our pre-deployment testing and validation processes, and if our effort to prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 21 16:11:47 2025 |
|---|
| Description: | Title: Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages
User impact: Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages.
Current status: We've received reports of an issue that users are unable to aggregate news posts when utilizing a News web part on SharePoint Online pages. We're analyzing the details within the support ticket and recent updates to the service as we isolate the source for this event.
Scope of impact: Your organization is affected by this event, and all users are unable to aggregate news posts when utilizing a News web part on SharePoint Online pages.
Next update by: Tuesday, October 21, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 21 15:56:56 2025 |
|---|
| Description: | Title: Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages
User impact: Users can't aggregate news posts when utilizing a News web part on SharePoint Online pages.
Current status: We're investigating a potential issue with aggregating news posts when utilizing a News web part, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1176212 - Users' SharePoint Online Events web part may not be displaying events when users select "See all"
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 15 14:24:00 2025 |
|---|
| End Time: | Tue Oct 21 10:46:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 21 14:05:22 2025 |
|---|
| Root Cause: | A recent code change produced an event web-part search configuration issue that was preventing users' SharePoint Online Events web part from displaying events when users selected "See all." |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 21 13:53:26 2025 |
|---|
| Description: | Title: Users' SharePoint Online Events web part may not be displaying events when users select "See all"
User impact: Users' SharePoint Online Events web part may not have displayed events when users selected "See all."
Final status: We've isolated a recent code change that produced an event web-part search configuration issue that was preventing users' SharePoint Online Events web part from displaying events when users selected "See all." As we progress our analysis into the offending service update, our code change deployment was validated by affected users to remediate the impact.
Scope of impact: This issue may have impacted any user attempting to view their SharePoint Online Events list when selecting "See all".
Start time: Wednesday, October 15, 2025, at 6:25 PM UTC
End time: Tuesday, October 21, 2025, at 2:46 PM UTC
Root cause: A recent code change produced an event web-part search configuration issue that was preventing users' SharePoint Online Events web part from displaying events when users selected "See all."
Next steps:
- We're further analyzing the offending code change and the event web-part search configuration issue to help us improve our pre-deployment testing and validation processes and in our effort to prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 20 12:42:34 2025 |
|---|
| Description: | Title: Users' SharePoint Online Events web part may not be displaying events when users select "See all"
User impact: Users' SharePoint Online Events web part may not be displaying events when users selected "See all."
Current status: We’re conducting further analysis into logs provided by affected users to investigate into this issue's root cause and to develop possible mitigation strategies.
Scope of impact: This issue may impact any user attempting to view their SharePoint Online Events list when selecting "See all".
Next update by: Tuesday, October 21, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 20 12:11:19 2025 |
|---|
| Description: | Title: Users' SharePoint Online Events web part may not be displaying events when users select "See all"
User impact: Users' SharePoint Online Events web part may not be displaying events when users selected "See all."
Current status: We’re investigating SharePoint Online logs provided by some affected users to better understand the impact scenario and cause of this issue.
Scope of impact: This issue may impact any user attempting to view their SharePoint Online Events list when selecting "See all".
Next update by: Monday, October 20, 2025, at 5:30 PM UTC
|
|---|
|
MF1176934 - Users can't perform multiple flow operations in Microsoft Power Automate
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 21 07:50:00 2025 |
|---|
| End Time: | Tue Oct 21 11:43:00 2025 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 21 12:50:27 2025 |
|---|
| Root Cause: | A limited power event in a datacenter that processes these requests was causing a network disruption that results in this impact to Microsoft Power Automate. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 21 12:46:58 2025 |
|---|
| Description: | Title: Users can't perform multiple flow operations in Microsoft Power Automate
User impact: Users couldn't perform multiple flow operations in Microsoft Power Automate.
More info: Impacted Microsoft Power Automate flow operations included:
- Turning on and off flows
- Listing flows
- Loading flow properties
- Accessing flow run history
- Admin flow and flow list access
- Admin center and flow management connector operations
- Admin ability to change or get flow permissions
Final status: We successfully restored power to the affected infrastructure to alleviate this impact to Microsoft Power Automate and service has been restored. We've also added additional impacted scenarios to the More info section of this communication.
Scope of impact: Your organization was affected by the event and couldn't perform the flow operations listed in the More info section in Microsoft Power Automate.
Start time: Tuesday, October 21, 2025, at 11:50 AM UTC
End time: Tuesday, October 21, 2025, at 3:43 PM UTC
Root cause: A limited power event in a datacenter that processes these requests was causing a network disruption that results in this impact to Microsoft Power Automate.
Next steps:
- We're reviewing our service resiliency and automated traffic routing contingencies to better understand how we can contend with unexpected issues like this and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 21 11:30:50 2025 |
|---|
| Description: | Title: Users can't perform multiple flow operations in Microsoft Power Automate
User impact: Users can't perform multiple flow operations in Microsoft Power Automate.
More info: Impacted Microsoft Power Automate flow operations include:
- Turning on and off flows
- Listing flows
- Loading flow properties
- Accessing flow run history
- Admin flow and flow list access
- Admin center and flow management connector operations
- Admin ability to change or get flow permissions
Current status: We've determined that a limited power event in a datacenter that processes these requests is resulting in this impact to the Microsoft Power Automate service. We're monitoring the actions we took to restore power to the affected infrastructure to ensure this impact is alleviated while we investigate the inciting event to avoid any future disruptions to service.
Scope of impact: Your organization is affected by the event, and users can't perform the flow operations listed in the More info section in Microsoft Power Automate.
Root cause: A limited power event in a datacenter that processes these requests is causing a network disruption that results in this impact to Microsoft Power Automate.
Next update by: Tuesday, October 21, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 10:54:26 2025 |
|---|
| Description: | Title: Users can't perform multiple flow operations in Microsoft Power Automate
User impact: Users can't perform multiple flow operations in Microsoft Power Automate.
Current status: 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.
|
|---|
|
OP1173892 - Users may intermittently see blank Microsoft Word documents opening unexpectedly
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 8 20:00:00 2025 |
|---|
| End Time: | Sat Oct 18 10:13:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 20 17:25:13 2025 |
|---|
| Root Cause: | The recent Microsoft Word version 2508, build 19127.20302, contained a code issue that intermittently caused new Microsoft Word documents to automatically populate once the app was closed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 20 17:07:20 2025 |
|---|
| Description: | Title: Users may intermittently see blank Microsoft Word documents opening unexpectedly
User impact: Users may have intermittently seen blank Microsoft Word documents opening unexpectedly.
More info: Specifically, after users closed the Microsoft Word app, the app may have opened on its own and populated a new blank Microsoft Word document. This issue only impacted Microsoft Word version 2508, build 19127.20302.
Final status: We've completed deployment of the fix to correct the code issue and confirmed after testing that impact is remediated.
Scope of impact: Any user on the affected Microsoft Word version may have experienced the impact intermittently.
Start time: Tuesday, September 9, 2025, at 12:00 AM UTC
End time: Saturday, October 18, 2025, at 2:13 PM UTC
Root cause: The recent Microsoft Word version 2508, build 19127.20302, contained a code issue that intermittently caused new Microsoft Word documents to automatically populate once the app was closed.
Next steps:
- We're reviewing our build testing and validation procedures to identify and prevent similar code issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 16 17:21:28 2025 |
|---|
| Description: | Title: Some users may intermittently see blank Microsoft Word documents opening unexpectedly
User impact: Users may intermittently see blank Microsoft Word documents opening unexpectedly.
More info: Specifically, after users close the Microsoft Word app, the app may open on its own and populate a new blank Microsoft Word document. This issue only impacts Microsoft Word version 2508, build 19127.20302.
Current status: We've confirmed that the recent Microsoft Word version 2508, build 19127.20302, contains a code issue that's intermittently causing new Microsoft Word documents to automatically populate once the app is closed. We've developed a code fix that will be released in an updated Microsoft Word version. The new updated version will be released incrementally, which we anticipate will be fully deployed by the end of the week of October 24, 2025. We'll aim to provide a precise deployment timeline once available.
Scope of impact: Any user on the affected Microsoft Word version may experience the impact intermittently.
Start time: Tuesday, September 9, 2025, at 12:00 AM UTC
Root cause: The recent Microsoft Word version 2508, build 19127.20302, contains a code issue that's intermittently causing new Microsoft Word documents to automatically populate once the app is closed.
Next update by: Monday, October 20, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 16:13:48 2025 |
|---|
| Description: | Title: Users intermittently see blank Microsoft Word documents opening unexpectedly
User impact: Users intermittently see blank Microsoft Word documents opening unexpectedly.
More info: This issue impacts Microsoft Word version 2508, build 19127.20302.
Current status: We're reviewing a recent Microsoft Word build update which we expect introduced an issue leading to users intermittently seeing blank Microsoft Word documents opening unexpectedly. Alongside confirming that this update is contributing to the impact, we're evaluating options for remediating the issue.
Scope of impact: Any user on the affected Microsoft Word version may experience the impact intermittently.
Next update by: Thursday, October 16, 2025, at 10:00 PM UTC
|
|---|
|
EX1173600 - Some users may have the new Outlook client open in their web browser instead of the Desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 13 23:00:00 2025 |
|---|
| End Time: | Fri Oct 17 12:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 20 16:22:23 2025 |
|---|
| Root Cause: | A code issue contained in a recent service update was causing a race condition and resulting in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 20 16:22:23 2025 |
|---|
| Description: | Title: Some users may have the new Outlook client open in their web browser instead of the Desktop client
User impact: Users had the new Outlook client open in their web browser instead of the Desktop client.
More info: As a workaround, users were able to use the classic Outlook to access their Exchange Online mailbox.
Final status: Our fix deployment is complete, and we’ve confirmed from service telemetry that this issue is resolved. Affected users may need to restart Outlook, potentially more than one time, to pick up the fix.
Scope of impact: Your organization was affected by this event, and some users attempting to open the new Outlook client were impacted.
Start time: Tuesday, October 14, 2025, at 3:00 AM UTC
End time: Friday, October 17, 2025, at 4:00 PM UTC
Root cause: A code issue contained in a recent service update was causing a race condition and resulting in the impact.
Next steps:
- We’re continuing our investigation to determine exactly how the offending code bug was introduced to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 16 15:30:41 2025 |
|---|
| Description: | Title: Some users have the new Outlook client open in their web browser instead of the Desktop client
User impact: Users have the new Outlook client open in their web browser instead of the Desktop client.
More info: As a workaround, users are able to use the classic Outlook to access their Exchange Online mailbox.
Current status: We've identified that a code bug contained in a recent service update is causing a race condition and resulting in the impact. We've developed a fix to address the code issue which we're preparing to deploy to the affected environment. We'll aim to provide a timeline for the fix to deploy by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and some users attempting to open the new Outlook client are impacted.
Root cause: A code issue contained in a recent service update is causing a race condition and resulting in the impact.
Next update by: Monday, October 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Oct 16 10:33:27 2025 |
|---|
| Description: | Title: Some users may have the new Outlook client open in their web browser instead of the Desktop client
User impact: Users may have the new Outlook client open in their web browser instead of the Desktop client.
More info: As a workaround, users are able to use the classic Outlook to access their Exchange Online mailbox.
Current status: We’re currently reviewing HTTP Archive (HAR) files to determine the underlying cause of the issue where the new Outlook client is unexpectedly launching Outlook on the web instead. Our analysis is focused on identifying any misconfigurations or behavioural anomalies contributing to this redirection.
Scope of impact: Some users attempting to open the new Outlook client may be impacted.
Next update by: Thursday, October 16, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Oct 16 08:51:19 2025 |
|---|
| Description: | Title: Some users may have the new Outlook client open in their web browser instead of the Desktop client
User impact: Users may have the new Outlook client open in their web browser instead of the Desktop client.
More info: As a workaround, users are able to use the classic Outlook to access their Exchange Online mailbox.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users attempting to open the new Outlook client may be impacted.
Next update by: Thursday, October 16, 2025, at 3:00 PM UTC
|
|---|
|
TM1176003 - Users may have been unable to receive Amazon push (ADM) notifications in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 20 03:40:00 2025 |
|---|
| End Time: | Mon Oct 20 05:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 20 06:35:37 2025 |
|---|
| Root Cause: | A third-party outage was affecting ADM push notifications in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 20 06:35:37 2025 |
|---|
| Description: | Title: Users may have been unable to receive Amazon push (ADM) notifications in Microsoft Teams
User impact: Users may have been unable to receive ADM notifications in Microsoft Teams.
Final status: We've confirmed through monitoring that the issue has been fully mitigated, and ADM notifications are now functioning as expected.
Scope of impact: Impact was specific to any user expecting to receive ADM notifications in Microsoft Teams.
Start time: Monday, October 20, 2025, at 7:40 AM UTC
End time: Monday, October 20, 2025, at 9:30 AM UTC
Root cause: A third-party outage was affecting ADM push notifications in Microsoft Teams.
Next steps:
- We're continuing to monitor service telemetry closely to ensure stability and ADM push notification performance has been restored.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 20 05:13:05 2025 |
|---|
| Description: | Title: Users may be unable to receive Amazon push (ADM) notifications in Microsoft Teams
User impact: Users may be unable to receive ADM notifications in Microsoft Teams.
Current Status: We've identified that an ongoing third-party outage is affecting ADM push notifications and Amazon is actively working to resolve the issue. We're monitoring the service and we'll provide an update once one becomes available.
Scope of impact: Impact is specific to any user expecting to receive ADM notifications in Microsoft Teams.
Root cause: An ongoing third-party outage is affecting ADM push notifications in Microsoft Teams.
Next update by: Monday, October 20, 2025, at 11:30 AM UTC
|
|---|
|
|
