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

Microsoft's Incident Report for PennO365

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

TM1173754 - Users may see that composed text is rendered in a different font once sent in Microsoft Teams

Status:serviceDegradation
Start Time:Mon Sep 15 11:30:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Nov 7 13:24:30 2025
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:Monday, November 10, 2025, at 8:00 PM UTC

Details

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.

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 7 09:03:50 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, November 14, 2025, at 3:30 PM UTC

Details

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

EX1182980 - Some users may experience delays in the "Shared with me" page

Status:serviceDegradation
Start Time:Tue Nov 4 16:16:33 2025
End Time:N/A
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Thu Nov 6 19:38:02 2025
Root Cause:A recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact.
Next Update:Tuesday, November 11, 2025, at 2:00 AM UTC

Details

Time:Thu Nov 6 19:38:02 2025
Description:Title: Some users may experience delays in the "Shared with me" page
User impact: Users may experience delays in the "Shared with me" page.
More info: Sharing retries are usually successful. The "Shared with me" page is accessed via the Settings > Accounts tab when accessed using the new Outlook for Windows desktop app and Outlook for the web.
Current status: After additional troubleshooting of our telemetry regarding the deployment of the fix to all impacted environments, we identified that the fix deployment is still in progress. The initial deployment has completed in our internal testing environment and we're seeing positive results. We're preparing for further deployments and we'll continue to monitor this to ensure it completes as expected.
Scope of impact: Some users may experience intermittent delays in the "Shared with me" page. This section may be updated as our investigation continues.
Start time: Tuesday, October 14, 2025, at 12:00 AM UTC
Root cause: A recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact.
Next update by: Tuesday, November 11, 2025, at 2:00 AM UTC
Time:Wed Nov 5 19:27:21 2025
Description:Title: Some users may experience delays in the "Shared with me" page
User impact: Users may experience delays in the "Shared with me" page.
More info: Sharing retries are usually successful. The "Shared with me" page is accessed via the Settings > Accounts tab when accessed using the new Outlook for Windows desktop app and Outlook for the web.
Current status: We're further monitoring the environment and troubleshooting our telemetry logs to ensure impact has been fully remediated as expected.
Scope of impact: Some users may experience intermittent delays in the "Shared with me" page. This section may be updated as our investigation continues.
Start time: Tuesday, October 14, 2025, at 12:00 AM UTC
Root cause: A recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact.
Next update by: Friday, November 7, 2025, at 2:00 AM UTC
Time:Wed Nov 5 13:00:06 2025
Description:Title: Some users may experience intermittent delays in the "Shared with me" page
User impact: Users may experience intermittent delays in the "Shared with me" page.
More info: Sharing retries are usually successful.
The "Shared with me" page is accessed via the Settings > Accounts tab when accessed using the new Outlook for Windows desktop app and Outlook for the web.
Current status: We've confirmed that the fix has completed its deployment and we're monitoring the environment to validate this has remediated impact.
Scope of impact: Some users may experience intermittent delays in the "Shared with me" page. This section may be updated as our investigation continues.
Start time: Tuesday, October 14, 2025, at 12:00 AM UTC
Root cause: A recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact.
Next update by: Thursday, November 6, 2025, at 1:30 AM UTC
Time:Tue Nov 4 16:59:17 2025
Description:Title: Some users may experience intermittent delays in the "Shared with me" page
User impact: Users may experience intermittent delays in the "Shared with me" page.
More info: Sharing retries are usually successful.
Current status: Our investigation determined that a recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact. We're reverting this update to resolve the issue.
Scope of impact: Some users may experience intermittent delays in the "Shared with me" page. This section may be updated as our investigation continues.
Start time: Tuesday, October 14, 2025, at 12:00 AM UTC
Root cause: A recent update to the Software Development Kit (SDK) library introduced a code error which is resulting in the impact.
Next update by: Wednesday, November 5, 2025, at 7:30 PM UTC
Time:Tue Nov 4 16:32:14 2025
Description:Title: Some users may experience intermittent delays in the "Shared with me" page
User impact: Users may experience intermittent delays in the "Shared with me" page.
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.

EX1183581 - Potential issues accessing mailboxes via one or more connection methods

Status:falsePositive
Start Time:Thu Nov 6 18:10:04 2025
End Time:Thu Nov 6 19:15:02 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Thu Nov 6 19:15:34 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Thu Nov 6 19:15:09 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.
Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours.
This is the final update for the event.
Time:Thu Nov 6 18:16:25 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.

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

MO1181369 - Users may see issues accessing some Microsoft 365 services and portals

Status:postIncidentReviewPublished
Start Time:Wed Oct 29 11:45:00 2025
End Time:Wed Oct 29 20:05:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Nov 5 19:45:36 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 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:45 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 will be providing an additional update to this PIR by Thursday, November 13, 2025, to provide the updates from the Azure AFD’s Final Post Incident Report.
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.

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 5 14:21:30 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:Wednesday, November 12, 2025, at 8:00 PM UTC

Details

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 5 14:20:43 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:Wednesday, November 12, 2025, at 8:00 PM UTC

Details

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.

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

OD1182545 - Some users may be unable to share content to Microsoft OneDrive from iPhone 17 due to false-positive jailbreak detection

Status:serviceDegradation
Start Time:Wed Oct 1 01:56:00 2025
End Time:N/A
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:advisory
Last Updated:Tue Nov 4 13:54:34 2025
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:Monday, November 10, 2025, at 7:30 PM UTC

Details

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

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:Tue Nov 4 11:50:29 2025
Root Cause:N/A
Next Update:N/A

Details

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.

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.

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:Mon Nov 3 20:35:43 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, November 10, 2025, at 10:00 AM UTC

Details

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

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.

EX1177461 - Admins may be unable to remove and view the latest status changes of migration batches in Exchange Online.

Status:serviceDegradation
Start Time:Wed Oct 22 00:49:21 2025
End Time:N/A
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Mon Nov 3 19:10:50 2025
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:Monday, November 10, 2025, at 7:30 PM UTC

Details

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.

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

MV1177163 - Some users may see inaccurate impact metrics on the Microsoft Copilot Dashboard in the Microsoft Viva Insights web app

Status:serviceDegradation
Start Time:Sat Sep 6 20:00:00 2025
End Time:N/A
Service:Microsoft Viva
Feature Group:Viva Insights
Classification:advisory
Last Updated:Thu Oct 30 16:00:06 2025
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:Monday, November 10, 2025, at 9:00 PM UTC

Details

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.

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 Oct 29 23:52:50 2025
Root Cause:A recent deployment incorrectly enabled this feature in the affected environment.
Next Update:Thursday, November 20, 2025, at 5:00 AM UTC

Details

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

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

OP1135993 - Some users can't create or publish Assignments in Microsoft OneNote or create a class notebook in a team

Status:serviceDegradation
Start Time:Sun Aug 10 20:00:00 2025
End Time:N/A
Service:Microsoft 365 apps
Feature Group:Office Client issues
Classification:advisory
Last Updated:Wed Oct 29 20:37:51 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 is resulting in failures.
Next Update:Thursday, November 13, 2025, at 2:30 AM UTC

Details

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.

TM1181326 - Some users may experience intermittent crashes when launching the Microsoft Teams desktop app on Windows

Status:serviceDegradation
Start Time:Wed Oct 29 08:42:25 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Wed Oct 29 17:43:31 2025
Root Cause:A recent standard service update contains a code regression, which is resulting in impact.
Next Update:Saturday, November 8, 2025, at 12:00 AM UTC

Details

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

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 Oct 28 21:01:53 2025
Root Cause:A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next Update:Wednesday, November 12, 2025, at 3:00 AM UTC

Details

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

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.

FL1176909 - Users are unable to run cloud and desktop flows or manage flows

Status:serviceRestored
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:Tue Oct 21 12:11:57 2025
Root Cause:N/A
Next Update:N/A

Details

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.

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

IT1168328 - Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app

Status:serviceRestored
Start Time:Fri Sep 26 15:16:00 2025
End Time:Fri Oct 17 14:45:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Fri Oct 17 15:15:54 2025
Root Cause:A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next Update:N/A

Details

Time:Fri Oct 17 15:15:54 2025
Description:Title: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices may have run out of disk space if the user was targeted with any Microsoft Store app.
More info: While we were focused on remediation, admins could’ve deleted the contents of the "%windir%\Temp\WinGet\defaultState" folder and restarted the device to temporarily mitigate the issue.
Final status: We’ve confirmed that our fix is available with the latest version of Microsoft Intune and that it’s operating as expected to resolve this problem. Affected devices should update to the fixed version automatically; however, affected users with full disk space may need to perform the manual mitigation mentioned above in the more info section to experience impact remediation.
Scope of impact: This issue may have affected any user with a Windows device managed through Microsoft Intune that was being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
End time: Friday, October 17, 2025, at 6:45 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
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:Fri Oct 17 01:17:58 2025
Description:Title: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app.
More info: While we're focused on remediation, admins can delete the contents of the "%windir%\Temp\WinGet\defaultState" folder and restart the device to temporarily mitigate the issue.
Current status: We’ve completed the remaining incremental deployments and are validating that no additional actions are necessary to fully resolve the impact.
Scope of impact: This issue may potentially affect any user with a Windows device managed through Microsoft Intune that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Friday, October 17, 2025, 8:30 PM UTC
Time:Thu Oct 16 19:32:29 2025
Description:Title: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app.
More info: While we're focused on remediation, admins can delete the contents of the "%windir%\Temp\WinGet\defaultState" folder and restart the device to temporarily mitigate the issue.
Current status: We've revised our expected timeline for the completion of the long-term fix. We're finishing up the remaining incremental deployments and once completed, we'll evaluate whether any additional actions will be needed to fully resolve impact.
Scope of impact: This issue may potentially affect any user with a Windows device managed through Microsoft Intune that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Friday, October 17, 2025, at 5:30 AM UTC
Time:Tue Oct 14 14:37:52 2025
Description:Title: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices may run out of disk space if the user is targeted with any Microsoft Store app.
More info: While we're focused on remediation, admins can delete the contents of the "%windir%\Temp\WinGet\defaultState" folder and restart the device to temporarily mitigate the issue.
Current status: We’ve initiated the incremental deployment of our long-term fix and anticipate the deployment should reach all affected users early next week. Affected users have reported that the temporary mitigation is operating as expected; however, it is possible that the issue will return until the fix deployment is complete, at which point the mitigation steps will need to be performed again to fully resolve the issue.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Tuesday, October 21, 2025, at 1:00 AM UTC
Time:Mon Oct 13 20:18:56 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: Our process to determine a deployment timeline is taking longer than anticipated but is ongoing. We'll provide the timeline once one is established.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Tuesday, October 14, 2025, at 7:00 PM UTC
Time:Mon Oct 13 14:10:33 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: We've validated the efficacy of the code fix and expect to have a timeline for its deployment by the time of our next update. Please note that we’ve removed the previously provided “More info” suggestion to delete the contents of a specific folder to temporarily mitigate the problem. We've also amended the 'Root cause' of this communication to contain more specificity.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Tuesday, October 14, 2025, at 1:00 AM UTC
Time:Fri Oct 10 14:09:32 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: We've completed our first round of testing, and we're continuing our validation efforts to ensure the efficacy of the fix before we begin deployment to the affected environment. We'll provide a timeline for remediation as one becomes available.
Scope of impact: TThis issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Monday, October 13, 2025, at 7:00 PM UTC
Time:Thu Oct 9 16:35:40 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: We're continuing to validate the fix internally and expect it will begin deployment on Monday, October 13, 2025. We'll provided an updated timeline for the deployment once validation completes.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Friday, October 10, 2025, at 7:00 PM UTC
Time:Wed Oct 8 22:12:54 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: We anticipate that the code fix to prevent excessive error logging is going to take time to validate. We'll provide an update on the code fix status by the next scheduled update time.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Thursday, October 9, 2025, at 9:30 PM UTC
Time:Wed Oct 8 19:56:48 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact. We're exploring options to update the code to prevent the excessive error logging and remediate impact.
Scope of impact: This issue may potentially affect any user with a Windows Intune device that’s being targeted with any Microsoft Store app.
Start time: Friday, September 26, 2025, at 7:16 PM UTC
Root cause: A recent update to a library used by the Intune Management Extension (IME) to manage Microsoft Store apps contains a code issue that's causing error logging to take up too much disk space and causing the impact.
Next update by: Thursday, October 9, 2025, at 8:00 AM UTC
Time:Wed Oct 8 19:05:24 2025
Description:Title: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app
User impact: Users’ Windows Intune devices run out of disk space if the user is targeted with any Microsoft Store app.
Current status: We're investigating a potential issue with Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

PB1172871 - Users may see blank documents after exporting reports to PDF using Power BI Desktop

Status:serviceRestored
Start Time:Thu Oct 9 03:00:00 2025
End Time:Fri Oct 17 01:54:00 2025
Service:Power BI
Feature Group:PowerBI.com
Classification:advisory
Last Updated:Fri Oct 17 14:28:44 2025
Root Cause:A recent service-side configuration was prematurely enabled, resulting in impact.
Next Update:N/A

Details

Time:Fri Oct 17 14:25:48 2025
Description:Title: Users may see blank documents after exporting reports to PDF using Power BI Desktop
User impact: Users may have seen blank documents after exporting reports to PDF using Power BI Desktop.
Final status: We've disabled the offending configuration change and confirmed through testing with a subset of affected users that the impact has been remediated.
Scope of impact: Impact was specific to some users attempting to export reports to PDF in Power BI Desktop.
Start time: Thursday, October 9, 2025, at 7:00 AM UTC
End time: Friday, October 17, 2025, at 5:54 AM UTC
Root cause: A recent service-side configuration was prematurely enabled, resulting in impact.
Next steps: - We're reviewing our update procedures to understand why the configuration was enabled prematurely, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Thu Oct 16 15:34:34 2025
Description:Title: Users may see blank documents after exporting reports to PDF using Power BI Desktop
User impact: Users may see blank documents after exporting reports to PDF using Power BI Desktop.
Current status: We've identified that a recent service-side configuration was prematurely enabled, resulting in impact. We're in the process of disabling this change and expect to have complete mitigation by the next scheduled update.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Root cause: A recent service-side configuration was prematurely enabled, resulting in impact.
Next update by: Friday, October 17, 2025, at 7:30 PM UTC
Time:Thu Oct 16 10:55:35 2025
Description:Title: Some users may see blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may see blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: Our analysis of the network trace data and reproducing the issue is ongoing, to assist with locating the source of impact and form or next steps.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Thursday, October 16, 2025, at 7:30 PM UTC
Time:Thu Oct 16 03:16:16 2025
Description:Title: Some users may see blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may see blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We’re continuing to review network trace data. In parallel, we’re working to consistently reproduce the issue to help identify the root cause and define a remediation plan.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Thursday, October 16, 2025, at 3:00 PM UTC
Time:Wed Oct 15 20:59:52 2025
Description:Title: Some users may see blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may see blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We've internally reproduced the problem and are continuing to review network trace data to help identify the root cause and determine a remediation plan.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Thursday, October 16, 2025, at 9:00 AM UTC
Time:Wed Oct 15 15:58:36 2025
Description:Title: Some users may see blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may see blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: Our initial analysis into service updates hasn't yet isolated any changes that correlate with our understanding of when impact started to occur. As we internally reproduce the problem and review network trace data, we're progressing with our service update analysis so we can confirm our next steps for remediating the impact.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Thursday, October 16, 2025, at 2:30 AM UTC
Time:Wed Oct 15 11:53:53 2025
Description:Title: Some users may see blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may see blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We're progressing with our analysis into recent updates to the service as we isolate the source for this event. In parallel, we're internally reproducing the problem to help us determine our next troubleshooting steps for remediating the impact.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Wednesday, October 15, 2025, at 8:30 PM UTC
Time:Wed Oct 15 09:56:58 2025
Description:Title: Some users may experience blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may experience blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We’re continuing to analyze recent changes made to the service that may be contributing to the impact.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Wednesday, October 15, 2025, at 5:00 PM UTC
Time:Wed Oct 15 08:45:21 2025
Description:Title: Some users may experience blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may experience blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We’re analyzing recent changes made to the service that may be contributing to the impact.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Wednesday, October 15, 2025, at 3:00 PM UTC
Time:Wed Oct 15 07:09:23 2025
Description:Title: Some users may experience blank visuals when exporting reports to PDF in Power BI Desktop
User impact: Users may experience blank visuals when exporting reports to PDF in Power BI Desktop.
Current status: We're reviewing service monitoring telemetry alongside support provided information, to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to export reports to PDF in Power BI Desktop.
Next update by: Wednesday, October 15, 2025, at 1:30 PM UTC

DZ1174522 - Some admins' event data in the Microsoft Defender XDR portal may be delayed up to six hours

Status:serviceRestored
Start Time:Thu Oct 16 15:20:00 2025
End Time:Thu Oct 16 21:16:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Cloud Apps
Classification:advisory
Last Updated:Fri Oct 17 13:46:07 2025
Root Cause:A portion of infrastructure responsible for facilitating the communication of Entra ID sign in or ARM event data to the Microsoft Defender XDR portal wasn't efficiently processing requests.
Next Update:N/A

Details

Time:Fri Oct 17 13:45:57 2025
Description:Title: Some admins' event data in the Microsoft Defender XDR portal may be delayed up to six hours
User impact: Admins' event data in the Microsoft Defender XDR portal may have been delayed up to six hours.
More info: Impact occurred for some Entra ID sign in or Azure Resource Manager (ARM) events. These scenarios may have included but weren't limited to: - Viewing activities - Activity alerts - Advanced hunting (limited to Entra ID sign in and Azure events) - Anomaly detection - Microsoft Sentinel
Final status: We've identified that a portion of infrastructure responsible for facilitating the communication of Entra ID sign in or ARM event data to the Microsoft Defender XDR portal wasn't efficiently processing requests. We've rebalanced the request traffic and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Some admins attempting to view the affected Entra ID sign in or Azure Resource Manager (ARM) events within the Microsoft Defender XDR portal may have been impacted.
Start time: Thursday, October 16, 2025, at 7:20 PM UTC
End time: Friday, October 17, 2025, at 1:16 AM UTC
Root cause: A portion of infrastructure responsible for facilitating the communication of Entra ID sign in or ARM event data to the Microsoft Defender XDR portal wasn't efficiently processing requests.
Next steps: - We're reviewing the affected infrastructure to identify the reason it wasn't efficiently processing requests, so that we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Fri Oct 17 13:32:15 2025
Description:Title: Some admins' event data in the Microsoft Defender XDR portal may be delayed up to six hours
User impact: Admins' event data in the Microsoft Defender XDR portal may have been delayed up to six hours.
More info: Impact occurred for some Entra ID sign in or Azure Resource Manager (ARM) events. These scenarios may have included but weren't limited to:
- Viewing activities - Activity alerts - Advanced hunting (limited to Entra ID sign in and Azure events) - Anomaly detection - Microsoft Sentinel
Current status: We've investigated a problem in which Microsoft Defender for Cloud Apps 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.

MO1174110 - Users may be unable to access the Microsoft Whiteboard service through the web and receive an error

Status:serviceRestored
Start Time:Thu Oct 16 18:12:00 2025
End Time:Thu Oct 16 21:40:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Thu Oct 16 23:28:08 2025
Root Cause:An HTML file within the affected infrastructure leveraged by the Microsoft Whiteboard web URL service was inadvertently removed through an automated action, which led to impact.
Next Update:N/A

Details

Time:Thu Oct 16 22:58:11 2025
Description:Title: Users may be unable to access the Microsoft Whiteboard service through the web and receive an error
User impact: Users may have been unable to access the Microsoft Whiteboard service through the web and received an error.
Final status: Our investigation of the service logs and the inaccessible Microsoft Whiteboard URL has identified that an HTML file within the affected infrastructure leveraged by the Microsoft Whiteboard web URL service was inadvertently removed through an automated action, which led to impact. We manually updated and restored this HTML file and confirmed from a subset of affected users that impact is remediated.
Scope of impact: Any user may have been affected by this event and may have been unable to access the Microsoft Whiteboard service through the web.
Start time: Thursday, October 16, 2025, at 10:12 PM UTC
End time: Friday, October 17, 2025, at 1:40 AM UTC
Root cause: An HTML file within the affected infrastructure leveraged by the Microsoft Whiteboard web URL service was inadvertently removed through an automated action, which led to impact.
Next steps: - We're further analyzing why the HTML file was automatically removed to identify what additional changes can be made to detect sooner and prevent similar impact from occurring again in the future.
This is the final update for the event.
Time:Thu Oct 16 21:44:51 2025
Description:Title: Users may be unable to access the Microsoft Whiteboard service through the web and receive an error
User impact: Users may be unable to access the Microsoft Whiteboard service through the web and receive an error.
Current status: We're investigating the service logs and the URL that is not accessible, to better understand the cause of impact and help develop our next steps.
Scope of impact: Any user may be affected by this event and may be unable to access the Microsoft Whiteboard service through the web.
Next update by: Friday, October 17, 2025, at 3:00 AM UTC
Time:Thu Oct 16 21:15:52 2025
Description:Title: Users may be unable to access the Microsoft Whiteboard service through the web and receive an error
User impact: Users may be unable to access the Microsoft Whiteboard service through the web and receive an error.
Current status: We're investigating a potential issue with Microsoft Whiteboard and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1168665 - Users were unable to access the admin center and the Entra portal

Status:postIncidentReviewPublished
Start Time:Thu Oct 9 03:55:00 2025
End Time:Thu Oct 9 07:15:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Thu Oct 16 18:46:06 2025
Root Cause:N/A
Next Update:Thursday, October 9, 2025, at 11:00 AM UTC

Details

Time:Thu Oct 16 18:46:06 2025
Description:A post-incident report has been published.
Time:Mon Oct 13 19:23:08 2025
Description:A post-incident report has been published.
Time:Thu Oct 9 08:06:04 2025
Description:Title: Users were unable to access the admin center and the Entra portal
User impact: Users were unable to access the admin center and the Entra portal.
More info: Some users would have also experienced intermittent issues accessing some Microsoft 365 services. Users were also unable to access their cloud PCs via the Windows app web client.
Final update: The failover of the Microsoft 365 portal service is complete, and we've validated that the service has fully recovered. Some of the affected users have also confirmed resolution.
Preliminary Root cause: We identified that the Azure front Door (AFD) service had a significant loss of capacity within the Europe and Africa regions, which resulted in impact to some of the Microsoft 365 services.
Scope of Impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services would have been impacted.
Start time: Thursday, October 9, 2025, at 7:55 AM UTC
End time: Thursday, October 9, 2025, at 11:15 AM UTC
Next steps: - We're analyzing data from the AFD service telemetry to identify the next actions required to improve resilience within the service to avoid recurrence.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Thu Oct 9 07:30:54 2025
Description:Title: Users may be unable to access the admin center and the Entra portal
User impact: Users may be unable to access the admin center and the Entra portal.
More info: Some users may also experience intermittent issues accessing some Microsoft 365 services. Users may also be unable to access their cloud PCs via the Windows app web client.
Current status: We've restored approximately 98% of the AFD service. We’re actively monitoring telemetry to confirm full recovery. In parallel, we’re initiating failover for the Microsoft 365 Portal service to accelerate the restoration process.
Scope of Impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services may be impacted.
Start time: Thursday, October 9, 2025, at 7:58 AM UTC
Next Update: Thursday, October 9, 2025, at 1:00 PM UTC
Time:Thu Oct 9 06:51:51 2025
Description:We identified a loss of capacity within the Azure Front Door (AFD) service causing impact to the Microsoft 365 service. We're restoring the service by bringing the AFD instances back online. Current telemetry shows signs of recovery, and we’re closely monitoring the service to ensure full restoration.
This quick update is designed to give the latest information on this issue.
Time:Thu Oct 9 06:15:17 2025
Description:Title: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services.
More info: Users may be unable to access their cloud PCs via the Windows app web client.
Current status: We've identified that an issue within the Azure Front Door (AFD) service is causing intermittent access issues to Microsoft 365 admin portals leading to wider impact. We're reviewing recent changes that may be contributing to the issue and are actively working on mitigation strategies.
Scope of Impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services may be impacted.
Start time: Thursday, October 9, 2025, at 7:58 AM UTC
Next Update: Thursday, October 9, 2025, at 12:00 PM UTC
Time:Thu Oct 9 05:39:36 2025
Description:Title: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services.
More info: Users may be unable to access Windows 365 Cloud PC via the Windows app web client. Retrying may help users to access their Windows 365 Cloud PC.
Current status: We're looking at diagnostic data to isolate the cause of the issue. Currently our investigation is focussed on the load balancing infrastructure.
Scope of Impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services may be impacted.
Start time: Thursday, October 9, 2025, at 7:58 AM UTC
Next Update: Thursday, October 9, 2025, at 11:00 AM UTC
Time:Thu Oct 9 04:57:52 2025
Description:Title: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services.
Current status: We're investigating reports of an issue in which users may be unable to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services. We're reviewing dependent service pathways to identify our initial investigating actions.
Scope of impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services may be impacted.
Next update by: Thursday, October 9, 2025, at 11:00 AM UTC

PP1161666 - Microsoft Copilot Studio – Intermittent failures and error message when publishing agents

Status:serviceRestored
Start Time:Wed Sep 10 18:29:00 2025
End Time:Wed Oct 15 19:54:00 2025
Service:Power Platform
Feature Group:Other
Classification:advisory
Last Updated:Thu Oct 16 13:15:53 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Thu Oct 16 13:15:53 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experienced intermittent failures and received an error when publishing agents.
Final Status: The deployment has completed, and we have confirmed after a period of service health diagnostics monitoring that copilot publishing reliability has been restored.
This is the final update on this incident.
Preliminary Root Cause: A code regression contained in a recent service update.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
Time:Wed Oct 15 14:31:36 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experience intermittent failures and receive an error when publishing agents.
More Info: The error message “There was an error publishing your agent. Please Try again later” will display in the red banner on the top of the Microsoft Copilot Studio page. This is a false error and the agent has published successfully.
As a workaround, when you receive this error and your agent did not actually publish successfully, you can retry publishing your agents.
Current Status: We have included the hotfix in our weekly service deployment and are initiating its deployment to the affected infrastructure.
Next Update: Thursday, October 16, 2025, at 9:00 PM UTC
Time:Wed Oct 8 13:14:17 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experience intermittent failures and receive an error when publishing agents.
More Info: The error message “There was an error publishing your agent. Please Try again later” will display in the red banner on the top of the Microsoft Copilot Studio page. This is a false error and the agent has published successfully.
As a workaround, when you receive this error and your agent did not actually publish successfully, you can retry publishing your agents.
Current Status: We are preparing to include the fix in an upcoming weekly service update.
Next Update: Wednesday, October 15, 2025, at 9:00 PM UTC
Time:Mon Sep 29 13:28:51 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experience intermittent failures and receive an error when publishing agents.
More Info: The error message “There was an error publishing your agent. Please Try again later” will display in the red banner on the top of the Microsoft Copilot Studio page. This is a false error and the agent has published successfully.
As a workaround, when you receive this error and your agent did not actually publish successfully, you can retry publishing your agents.
Current Status: We have completed the development of a fix for this issue, which will be included as part of an upcoming standard weekly service deployment.
Next Update: Wednesday, October 8, 2025, at 9:00 PM UTC
Time:Sun Sep 28 22:52:37 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experience intermittent failures and receive an error when publishing agents.
More Info: The error message “There was an error publishing your agent. Please Try again later” will display in the red banner on the top of the Microsoft Copilot Studio page.
As a workaround, please retry publishing your agents.
Current Status: Our investigation identified impact occurred following a recent deployment that applied a code change. This code change makes a request call to an active component prior to the component being initiated. We are working on a fix to correct this code change and will deploy the fix once validated.
Next Update: Monday, September 29, 2025, at 7:30 PM UTC
Time:Sun Sep 28 22:33:14 2025
Description:Title: Microsoft Copilot Studio – Intermittent failures and error message when publishing agents
User impact: Users experience intermittent failures and receive an error when publishing agents.
More Info: The error message “There was an error publishing your agent. Please Try again later” will display in the red banner on the top of the Microsoft Copilot Studio page.
As a workaround, please retry publishing your agents.
Current Status: We are aware of an emerging issue where users intermittently receive a “There was an error publishing your agent. Please Try again later” error message and publishing failures when publishing agents in Microsoft Copilot Studio. 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.

TM1173358 - Some users are intermittently unable to join some Teams Walkie Talkie channels

Status:serviceRestored
Start Time:Wed Oct 15 20:20:00 2025
End Time:Wed Oct 15 21:58:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Oct 15 22:45:57 2025
Root Cause:A recent standard service update contained a code issue which was resulting in impact.
Next Update:N/A

Details

Time:Wed Oct 15 22:45:57 2025
Description:Title: Some users are intermittently unable to join some Teams Walkie Talkie channels
User impact: Users wre intermittently unable to join some Teams Walkie Talkie channels.
More info: Affected users received the following failure message: "The channel you selected is no longer available"
Final status: The reversion has been completed through the affected environment and we’ve confirmed that impact has been remediated following our period of monitoring the service health.
Scope of impact: Users in the North American region attempting to join Teams Walkie Talkie channels were impacted.
Start time: Thursday, October 16, 2025, at 12:20 AM UTC
End time: Thursday, October 16, 2025, at 1:58 AM UTC
Root cause: A recent standard service update contained a code issue which was resulting in impact.
Next steps: - We're reviewing this recent service update to understand why impact wasn’t identified prior to implementing the change so that we can better understand the underlying issue and improve our change management practices.
This is the final update for the event.
Time:Wed Oct 15 21:46:06 2025
Description:Title: Some users are intermittently unable to join some Teams Walkie Talkie channels
User impact: Users are intermittently unable to join some Teams Walkie Talkie channels.
More info: Affected users receive the following failure message: "The channel you selected is no longer available"
Current status: We’ve determined that a recent standard service update contains a code issue which is resulting in impact. We’re in the process of reverting the offending service update to remediate impact. We anticipate that this process will be completed and we’ll have finished our subsequent monitoring of the service health to ensure that impact is remediated prior to our next scheduled update.
Scope of impact: Users in the North American region attempting to join Teams Walkie Talkie channels are impacted.
Root cause: A recent standard service update contains a code issue which is resulting in impact.
Next update by: Thursday, October 16, 2025, at 3:30 AM UTC
Time:Wed Oct 15 21:33:23 2025
Description:Title: Some users are intermittently unable to join some Teams Walkie Talkie channels
User impact: Users are intermittently unable to join some Teams Walkie Talkie channels. More info: Affected users receive the follow
More info: Affected users receive the following failure message:
"The channel you selected is no longer available"
Current status: We're investigating a potential issue with Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1168102 - Some users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services

Status:postIncidentReviewPublished
Start Time:Wed Oct 8 12:06:00 2025
End Time:Wed Oct 8 13:59:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Oct 15 19:42:00 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Oct 15 19:42:00 2025
Description:A post-incident report has been published.
Time:Fri Oct 10 19:42:18 2025
Description:A post-incident report has been published.
Time:Wed Oct 8 14:58:49 2025
Description:Title: Some users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may have been unable to access the Microsoft 365 admin center or Microsoft 365 services using Microsoft Entra.
More info: Some users attempting to access other Microsoft 365 services, including but not limited to Microsoft Teams and Exchange Online, may have been unable to authenticate and access the services. Additionally, users might not have received Multi-Factor Authentication (MFA) messages when attempting to sign in. Affected users may have encountered an error stating, "We are sorry, something went wrong. Please try refreshing the page in a few minutes. If the problem persists, please visit status.cloud.microsoft for updates regarding known issues."
Final status: Our analysis identified a portion of directory operations infrastructure which became imbalanced during a period of high traffic volume and caused authorization failures associated with impact. We've successfully rebalanced traffic across the affected infrastructure and confirmed after a period of monitoring that the impact is no longer occurring.
Scope of impact: A portion of users attempting to access the Microsoft 365 services outlined in the 'User impact' and 'More info' sections of this communication may have been impacted.
Preliminary root cause: A portion of directory operations infrastructure became imbalanced during a period of high traffic volume, which caused failures associated with impact.
Start time: Wednesday, October 8, 2025, at 4:06 PM UTC
End time: Wednesday, October 8, 2025, at 5:59 PM UTC
Next steps: - We're analyzing volume trends and traffic management processes on the affected directory operations infrastructure to identify necessary refinements and increase resilience in the event of future instances of high traffic volume.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Wed Oct 8 14:25:52 2025
Description:Current status: We're observing recovery in response to our efforts to rebalance traffic across the affected directory infrastructure. We'll continue to closely monitor the environment to ensure withstanding remediation.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 8 14:06:13 2025
Description:Title: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services.
More info: Some users attempting to access other Microsoft 365 services, including but not limited to Microsoft Teams and Exchange Online, may be unable to authenticate and access the services. Additionally, users may not receive Multi-Factor Authentication (MFA) messages when attempting to sign in.
Affected users may encounter an error stating "We are sorry, something went wrong. Please try refreshing the page in a few minutes. If the problem persists, please visit status.cloud.microsoft for updates regarding known issues."
Current status: Our analysis of diagnostic data associated with the affected directory operations infrastructure is ongoing as we seek to understand the root cause of this issue. In the meantime, we're rebalancing traffic across the affected infrastructure as a near-term mitigation action to provide relief to affected users.
Scope of impact: A portion of users attempting to access the Microsoft 365 services outlined in the 'User impact' and 'More info' sections of this communication may be impacted.
Start time: Wednesday, October 8, 2025, at 4:06 PM UTC
Next update by: Wednesday, October 8, 2025, at 8:00 PM UTC
Time:Wed Oct 8 13:36:05 2025
Description:Current status: We're rebalancing an affected section of dependent service infrastructure as a potential mitigation action.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 8 13:26:03 2025
Description:Current status: We've identified a potential directory operations issue within a portion of dependent service infrastructure. We're reviewing the diagnostics to determine our next steps.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 8 13:11:28 2025
Description:Title: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services
User impact: Users may be unable to access the admin center or leverage Microsoft Entra to access other Microsoft 365 services.
More info: Additionally, users may be unable to receive Multi-Factor Authentication (MFA) messages when attempting to sign in.
Current status: We're investigating reports of an issue in which users may be unable to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services. We're reviewing dependent service pathways to identify our initial investigating actions.
Scope of impact: Any users attempting to access the Microsoft 365 admin center or leverage Microsoft Entra to access other Microsoft 365 services may be impacted.
Next update by: Wednesday, October 8, 2025, at 6:00 PM UTC
Time:Wed Oct 8 12:51:46 2025
Description:Title: Investigating user reports of issues with Microsoft 365 services
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
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.

IT1171820 - Admins may be unable to view enrollment status charts in the Microsoft Intune admin center

Status:serviceRestored
Start Time:Mon Sep 29 07:36:00 2025
End Time:Tue Oct 14 16:00:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Tue Oct 14 16:26:32 2025
Root Cause:A recent update to the data source for enrollment data was preventing enrollment status charts from loading.
Next Update:N/A

Details

Time:Tue Oct 14 16:26:32 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may have been unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempted to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts didn't load.
While we were focused on remediation, admins may have been able to view enrollment data through the enrollment reports in the Microsoft Intune admin center.
Final status: We've reverted the offending update within the remaining affected infrastructure and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: This issue may have potentially impacted any admin attempting to view enrollment status charts in the Microsoft Intune admin center.
Start time: Monday, September 29, 2025, at 11:36 AM UTC
End time: Tuesday, October 14, 2025, at 8:00 PM UTC
Root cause: A recent update to the data source for enrollment data was preventing enrollment status charts from loading.
Next steps: - We're reviewing our update procedures to understand why impact to chart visibility 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:Tue Oct 14 12:11:50 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts don't load.
While we're focused on remediation, admins may be able to view enrollment data through the enrollment reports in the Microsoft Intune admin center.
Current status: We've reverted the offending service update within a majority of the affected infrastructure, and our review of service health telemetry indicates the number of admins experiencing impact has been significantly reduced. We anticipate the reversion process will complete and fully remediate the impact by our next scheduled communications update.
Scope of impact: This issue may potentially impact any admin attempting to view enrollment status charts in the Microsoft Intune admin center.
Estimated time to resolve: We anticipate the offending update will be reverted by Tuesday, October 14, 2025, at 10:00 PM UTC.
Root cause: A recent update to the data source for enrollment data is preventing enrollment status charts from loading.
Next update by: Tuesday, October 14, 2025, at 10:00 PM UTC
Time:Tue Oct 14 05:27:59 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts don't load.
While we're focused on remediation, users may be able to view enrollment data through the enrollment reports in the Microsoft Intune admin center.
Current status: We're continuing to revert the aforementioned service update to mitigate impact and anticipate this process will be complete by our next scheduled update.
Scope of impact: This issue may potentially impact any admin users attempting to view enrollment status charts in the Microsoft Intune admin center.
Root cause: A recent update to the data source for enrollment data, that is causing loading issues with the enrollment status charts.
Next update by: Tuesday, October 14, 2025, at 6:00 PM UTC
Time:Tue Oct 14 02:00:15 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts don't load.
While we're focused on remediation, users may be able to view enrollment data through the enrollment reports in the Microsoft Intune admin center.
Current status: We've validated that reverting the offending service update is the most efficacious way to resolve the issue and we’re in the beginning stages of initiating the reversion process. We anticipate that we’ll have begun reverting the impacting service update by the time of our next scheduled update, at which point we aim to provide a remediation timeline.
Scope of impact: This issue may potentially impact any admin users attempting to view enrollment status charts in the Microsoft Intune admin center.
Root cause: A recent update to the data source for enrollment data, that is causing loading issues with the enrollment status charts.
Next update by: Tuesday, October 14, 2025, at 10:30 AM UTC
Time:Mon Oct 13 21:40:05 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts don't load.
While we're focused on remediation, users may be able to view enrollment data through the enrollment reports in the Microsoft Intune admin center.
Current status: We've identified a recent update to the data source for enrollment data, that is causing loading issues with the enrollment status charts. We're analyzing whether the update can be reverted to remediate the impact.
Scope of impact: This issue may potentially impact any admin users attempting to view enrollment status charts in the Microsoft Intune admin center.
Root cause: A recent update to the data source for enrollment data, that is causing loading issues with the enrollment status charts.
Next update by: Tuesday, October 14, 2025, at 7:30 AM UTC
Time:Mon Oct 13 19:11:57 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts don't load.
Current status: We suspect a recent update is causing issues with viewing the enrollment status charts. We're reviewing the changes contained in the update to confirm that it's contributing to the impact and help us determine our next troubleshooting steps
Scope of impact: This issue may potentially impact any admin users attempting to view enrollment status charts in the Microsoft Intune admin center.
Next update by: Tuesday, October 14, 2025, at 1:30 AM UTC
Time:Mon Oct 13 18:37:41 2025
Description:Title: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center
User impact: Admins may be unable to view enrollment status charts in the Microsoft Intune admin center.
More info: When admins attempt to view the enrollment status charts from the enrollment failures page in the Microsoft Intune admin center, the charts do not load.
Current status: We're investigating a potential issue with the Microsoft Intune admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1157645 - Users leveraging Surface Copilot + PC devices with Snapdragon Qualcomm processors can’t start video in Microsoft Teams

Status:serviceRestored
Start Time:Tue Jul 22 15:00:00 2025
End Time:Thu Oct 9 21:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Oct 14 15:51:46 2025
Root Cause:A recently released Windows Update was preventing users with Surface Copilot + PC devices with Qualcomm Snapdragon processors from starting video in Microsoft Teams meetings.
Next Update:N/A

Details

Time:Tue Oct 14 15:50:33 2025
Description:Title: Users leveraging Surface Copilot + PC devices with Snapdragon Qualcomm processors can’t start video in Microsoft Teams
User impact: Users of Surface Copilot + PC devices with Qualcomm Snapdragon processors couldn’t start video in Microsoft Teams.
More info: As a workaround, users could have mitigated this issue by turning off Windows Studio effects until a fix was made available:
1. Select Start and then select Settings 2. Select Bluetooth & devices, then Cameras, and then Surface Camera Front 3. Expand the section for Windows Studio Effects and then turn off each effect.
The following articles detail the October 2025 driver update users need to install to resolve impact:
https://support.microsoft.com/en-us/surface/surface-pro-11th-edition-update-history-f26dd8a1-9169-4f4a-ab0d-6a47d2f10e25
https://support.microsoft.com/en-us/surface/surface-laptop-7th-edition-update-history-fdadc3d1-87d4-4a58-bc2e-ec9d7e3af16e
Final status: We've released a driver update for Surface Copilot + PC devices with Qualcomm Snapdragon processors that resolved the issue preventing users from starting their video in Microsoft Teams. We've provided two Microsoft support articles for Surface Pro (11th Edition) and Surface Laptop (7th Edition) which provide details on the October 2025 driver update and version number that users need to upgrade to in order to resolve impact.
Scope of impact: Your organization was impacted by this event, and the problem impacted users leveraging Surface Copilot + PC devices with Qualcomm Snapdragon processors that were trying to start video during Microsoft Teams meetings.
Start time: Tuesday, July 22, 2025, at 7:00 PM UTC
End time: Friday, October 10, 2025, at 1:00 AM UTC
Root cause: A recently released Windows Update was preventing users with Surface Copilot + PC devices with Qualcomm Snapdragon processors from starting video in Microsoft Teams meetings.
Next steps: - We're analyzing the offending Windows update to determine why the potential for impact wasn't caught during our update testing and validation phases. This analysis will help us to ensure similar impact doesn't occur in future by helping us to improve the resilience and quality of our future updates.
This is the final update for the event.
Time:Mon Sep 22 14:41:14 2025
Description:Title: Users leveraging Surface Copilot + PC devices with Qualcomm Snapdragon processors can’t start video in Microsoft Teams
User impact: Users leveraging Surface Copilot + PC devices with Qualcomm Snapdragon processors can’t start video in Microsoft Teams.
More info: As a workaround, users can mitigate this issue by turning off Windows Studio effects until a fix is made available:
1. Select Start and then select Settings 2. Select Bluetooth & devices, then Cameras, and then Surface Camera Front 3. Expand the section for Windows Studio Effects and then turn off each effect.
Current status: We’ve identified and investigated an issue in which users with Surface Copilot + PC devices with Qualcomm Snapdragon processors can’t start video in Microsoft Teams and determined that a recently released Windows Update is causing the problem. A new driver for the impacted processors is being developed to resolve the issue. We’ll provide a timeline to impact remediation when one becomes available.
Scope of impact: Your organization is impacted by this event, and the problem impacts users leveraging Surface Copilot + PC devices with Qualcomm Snapdragon processors that are trying to start video during Microsoft Teams meetings.
Start time: Tuesday, July 22, 2025, at 7:00 PM UTC
Root cause: A recently released Windows Update is preventing users with Surface Copilot + PC devices with Qualcomm Snapdragon processors from starting video in Microsoft Teams meetings.
Next update by: Tuesday, October 14, 2025, at 9:00 PM UTC

OP1171442 - Some users may be unable to access Microsoft 365 applications

Status:investigationSuspended
Start Time:Mon Oct 13 03:30:00 2025
End Time:Mon Oct 13 12:22:03 2025
Service:Microsoft 365 apps
Feature Group:Office Client issues
Classification:incident
Last Updated:Mon Oct 13 12:22:41 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Mon Oct 13 12:22:41 2025
Description:Title: Some users may be unable to access Microsoft 365 applications
User impact: Users may be unable to access Microsoft 365 applications.
More info: When users attempt to access Microsoft 365 apps from the Office homepage, the apps aren't listed.
Final status: While we continue to analyze service-side infrastructure logs and service health telemetry to narrow down the source of the impact, we've concluded that the impact is no longer occurring. In the event impact persists, please contact one of our support representatives so we can continue our investigation into the problem.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access Microsoft 365 applications.
Start time: Monday, October 13, 2025, at 7:30 AM UTC
This is the final update for the event.
Time:Mon Oct 13 09:04:32 2025
Description:Title: Some users may be unable to access Microsoft 365 applications
User impact: Users may be unable to access Microsoft 365 applications.
Current status: We're continuing to analyze service telemetry alongside recent changes made to the service, to help identify the root cause and define a clear path to resolution.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access Microsoft 365 applications.
Next update by: Monday, October 13, 2025, at 6:00 PM UTC
Time:Mon Oct 13 07:52:42 2025
Description:Title: Some users may be unable to access Microsoft 365 applications
User impact: Users may be unable to access Microsoft 365 applications.
Current status: We're proceeding to analyze service telemetry to pinpoint 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 access Microsoft 365 applications.
Next update by: Monday, October 13, 2025, at 2:00 PM UTC
Time:Mon Oct 13 06:18:19 2025
Description:Title: Some users may be unable to access Microsoft 365 applications
User impact: Users may be unable to access Microsoft 365 applications.
Current status: We're continuing to review service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access Microsoft 365 apps.
Next update by: Monday, October 13, 2025, at 12:30 PM UTC
Time:Mon Oct 13 05:06:11 2025
Description:Title: Some users may be unable to access Microsoft 365 applications
User impact: Users may be unable to access Microsoft 365 applications.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access Microsoft 365 apps.
Next update by: Monday, October 13, 2025, at 10:30 AM UTC

DZ1168079 - Users may have received inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management

Status:serviceRestored
Start Time:Mon Sep 29 06:00:00 2025
End Time:Fri Oct 10 09:10:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Sun Oct 12 06:47:57 2025
Root Cause:A recent change related to End-Of-Support software introduced a code issue which resulted in impact.
Next Update:N/A

Details

Time:Sun Oct 12 06:37:10 2025
Description:Title: Users may have received inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management
User impact: Users may have received inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may have seen inaccurate tagging within Threat and Vulnerability Management.
Final status: The fix has been successfully deployed, and we've confirmed that the inaccurate end-of-life tagging issue is now mitigated.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may have been affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
End time: Friday, October 10, 2025, at 1:10 PM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue which resulted in impact.
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:Thu Oct 9 12:36:14 2025
Description:Title: Users may receive inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management
User impact: Users may receive inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
Current status: We've completed deployment the aforementioned fix; however, the inaccurate end-of-life tagging is still occurring. We're investigating to determine what additional actions are necessary to ensure the fix is applied to the affected users.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Sunday, October 12, 2025, at 11:00 AM UTC
Time:Thu Oct 9 11:21:04 2025
Description:Title: Users may receive inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management
User impact: Users may receive inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
Current status: We're continuing to deploy a fix that's designed to reverse the offending change that introduced the code issue and will provide a timeline for its completion as one becomes available.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Thursday, October 9, 2025, at 5:30 PM UTC
Time:Thu Oct 9 06:24:03 2025
Description:Title: Users may experience inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management
User impact: Users may experience inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: We've determined that a further fix is required to mitigate impact. We've deployed the fix and anticipate its completion by our next scheduled update.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Thursday, October 9, 2025, at 3:30 PM UTC
Time:Wed Oct 8 19:02:44 2025
Description:Title: Users may experience inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management.
User impact: Users may experience inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: Our efforts to analyze user logs and service health telemetry to confirm impact was remediated is ongoing.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Thursday, October 9, 2025, at 10:30 AM UTC
Time:Wed Oct 8 17:59:09 2025
Description:Title: Users may experience inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management.
User impact: Users may experience inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: We've completed our fix deployment throughout the entire affected environment, and we’re currently working on validating that this fix has fully mitigated impact by analyzing user logs and overall service health telemetry.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Start time: Monday, September 29, 2025, at 10:00 AM UTC
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Thursday, October 9, 2025, at 12:00 AM UTC
Time:Wed Oct 8 16:04:33 2025
Description:Title: Users may experience inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management.
User impact: Users may experience inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: We've completed our test deployment validation and manual cleanup process of the portion of infrastructure responsible for processing traffic flow. We're monitoring this validated fix as it deploys across the entire affected environment. We’ll provide a timeline as one becomes available to us.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Root cause: A recent change related to End-Of-Support software introduced a code issue, which is resulting in impact.
Next update by: Wednesday, October 8, 2025, at 10:00 PM UTC
Time:Wed Oct 8 14:00:13 2025
Description:Title: Users may experience inaccurate end-of-life tagging for SQL within Microsoft Defender for Endpoint management.
User impact: Users may experience inaccurate end-of-life tagging for SQL Server within Microsoft Defender for Endpoint management.
More info: Users with SQL Server 2019 and 2017 installed may see inaccurate tagging within Threat and Vulnerability Management.
These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: We're currently working on validating a possible code update in our test environment, and will then proceed with manual cleanup of the portion of infrastructure responsible for processing traffic flow after deploying the validated fix to the entire affected environment.
Scope of impact: All users that have SQL Server 2017 and 2019 installed in their environment may be affected by this.
Root cause: A recent change related to End-Of-Support software introduced a code issue, which resulted in impact.
Next update by: Wednesday, October 8, 2025, at 8:00 PM UTC
Time:Wed Oct 8 11:59:32 2025
Description:Title: EOS tags are being incorrectly applied to SQL Server 2017 and 2019 vulnerability reports.
User impact: Vulnerability recommendations for SQL Server 2017 and 2019 may have an incorrect End-Of-Support (EOS) tag applied.
More info: These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
The vulnerability recommendations are legitimate, however, the EOS tag applied is incorrect.
Current status: After further investigation, we've identified that the vulnerability recommendations are legitimate, however, the EOS tags are being incorrectly applied. We've updated the User Impact section to reflect this and provide more clarity on the impact. We're deploying the fix to our test environment where we will perform validation testing. Once complete, we'll deploy it across all environments.
Scope of impact: This could impact users that have SQL Server 2017 and 2019 installed in their environment.
Root cause: A recent change related to End-Of-Support software introduced a bug.
Next update by: Wednesday, October 8, 2025, at 6:00 PM UTC
Time:Wed Oct 8 10:52:13 2025
Description:Title: Users may experience inaccurate vulnerability reports within Microsoft Defender for Endpoint.
User impact: Users with SQL Server 2019 and 2017 installed in their environment may see false positive recommendations.
More info: These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
Current status: We've identified that a recent change related to End-Of-Support (EOS) introduced a code bug resulting in the impact. We're deploying a fix to remediate the issue.
Scope of impact: This could impact users that have SQL Server 2017 and 2019 installed in their environment.
Root cause: A recent change related to End-Of-Support software introduced a bug.
Next update by: Wednesday, October 8, 2025, at 5:00 PM UTC
Time:Wed Oct 8 10:35:20 2025
Description:Title: Users may experience inaccurate vulnerability reports within Microsoft Defender for Endpoint
User impact: Users with SQL Server 2019 and 2017 installed in their environment may see false positive recommendations.
More info: These recommendations would appear within Microsoft Defender for Endpoint - Threat and Vulnerability Management feature.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1169700 - Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect

Status:serviceRestored
Start Time:Fri Oct 10 14:43:30 2025
End Time:Sat Oct 11 04:31:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Sat Oct 11 21:28:09 2025
Root Cause:A recent service configuration change intended to update internal components resulted in an authorization component misconfiguration and caused Microsoft Graph Data Connect dataset extraction failures.
Next Update:N/A

Details

Time:Sat Oct 11 21:28:09 2025
Description:Title: Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect
User impact: Admins may have been unable to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Final status: Our fix has completed deploying and has corrected the authorization component misconfiguration. We’ve observed from our telemetry that failures have stopped occurring, confirming that our solution has resolved the issue.
Scope of impact: Impact may have occurred for some admins who attempted to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Start time: Thursday, October 9, 2025, at 7:00 PM UTC
End time: Saturday, October 11, 2025, at 8:31 AM UTC
Root cause: A recent service configuration change intended to update internal components resulted in an authorization component misconfiguration and caused Microsoft Graph Data Connect dataset extraction failures.
Next steps: - We're reviewing our service configuration change procedures to understand why impact to Microsoft 365 datasets through Microsoft Graph Data Connect wasn't caught during the testing phase so that we can prevent similar impact in the future, and to improve our pre-deployment processes.
This is the final update for the event.
Time:Fri Oct 10 21:28:25 2025
Description:Title: Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect
User impact: Admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Current status: We’re continuing to prepare our code change for deployment and based on our current estimations, this deployment will have begun and completed by our next scheduled communications update.
Scope of impact: Impact may occur for some admins attempting to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Start time: Thursday, October 9, 2025, at 7:00 PM UTC
Root cause: A recent service configuration change intended to update internal components resulted in an authorization component misconfiguration, causing Microsoft Graph Data Connect dataset extraction failures.
Next update by: Sunday, October 12, 2025, at 3:00 AM UTC
Time:Fri Oct 10 19:30:44 2025
Description:Title: Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect
User impact: Admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect.
More info: Some admins may be unable to export datasets in various Microsoft 365 services such as Microsoft Teams, Exchange Online, and SharePoint Online through Microsoft Graph Data Connect pipelines.
Current status: We’ve completed validating our remediation pathway, which involves implementing a code change. We’re preparing to deploy this change to the affected environments and we anticipate being able to provide a timeline for resolution by our next scheduled communications update.
Scope of impact: Impact may occur for some admins attempting to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Start time: Thursday, October 9, 2025, at 7:00 PM UTC
Root cause: A recent service configuration change intended to update internal components resulted in an authorization component misconfiguration, causing Microsoft Graph Data Connect dataset extraction failures.
Next update by: Saturday, October 11, 2025, at 3:00 AM UTC
Time:Fri Oct 10 15:47:40 2025
Description:Title: Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect
User impact: Admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect.
More info: Some admins may be unable to export datasets in various Microsoft 365 services such as Microsoft Teams, Exchange Online, and SharePoint Online through Microsoft Graph Data Connect pipelines.
Current status: We’ve identified that a recent service configuration change intended to update internal components resulted in an authorization component misconfiguration, causing Microsoft Graph Data Connect dataset extraction failures. We’re validating an appropriate remediation pathway and will provide a resolution timeline once available.
Scope of impact: Impact may occur for some admins attempting to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Start time: Thursday, October 9, 2025, at 7:00 PM UTC
Root cause: A recent service configuration change intended to update internal components resulted in an authorization component misconfiguration, causing Microsoft Graph Data Connect dataset extraction failures.
Next update by: Saturday, October 11, 2025, at 1:00 AM UTC
Time:Fri Oct 10 14:59:30 2025
Description:Title: Some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect
User impact: Admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect.
More info: Some admins may be unable to export datasets in various Microsoft 365 services such as Microsoft Teams, Exchange Online, and SharePoint Online through Microsoft Graph Data Connect pipelines.
Current status: We've received reports from affected admins that some admins may be unable to export Microsoft 365 datasets through Microsoft Graph Data Connect. We're reviewing service telemetry to assess this issue and identify an appropriate remediation action.
Scope of impact: Impact may occur for some admins attempting to export Microsoft 365 datasets through Microsoft Graph Data Connect.
Next update by: Friday, October 10, 2025, at 8:00 PM UTC

EX1170184 - Some users may have experienced errors or failures when accessing mailbox via any Exchange Online connection method

Status:serviceRestored
Start Time:Sat Oct 11 08:02:00 2025
End Time:Sat Oct 11 08:49:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Sat Oct 11 10:46:22 2025
Root Cause:A section of mailbox database infrastructure was performing below acceptable performance thresholds.
Next Update:N/A

Details

Time:Sat Oct 11 10:19:54 2025
Description:Title: Some users may have experience errors or failures when accessing mailbox via any Exchange Online connection method
User impact: Users may have experienced errors or failures when accessing their mailbox via any Exchange Online connection method.
Final status: We've determined that a section of mailbox database infrastructure was performing below acceptable performance thresholds, causing impact to occur. Our automated recovery procedures redirected network traffic to alternate infrastructure, which we confirmed after a period of monitoring service telemetry, that impact has been remediated.
Scope of impact: Impact was specific to users located in North America, attempting to access their mailbox via any Exchange Online connection method.
Start time: Saturday, October 11, 2025, at 12:02 PM UTC
End time: Saturday, October 11, 2025, at 12:49 PM UTC
Root cause: A section of mailbox database infrastructure was performing below acceptable performance thresholds.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Sat Oct 11 08:43:37 2025
Description:Title: Some users may experience errors or failures when accessing their mailbox via any Exchange Online connection method
User impact: Users may experience errors or failures when accessing their mailbox via any Exchange Online connection method.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America, attempting to access their mailbox via any Exchange Online connection method.
Next update by: Saturday, October 11, 2025, at 3:00 PM UTC
Time:Sat Oct 11 08:25:45 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.

MO1169051 - Some admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center

Status:serviceRestored
Start Time:Thu Oct 9 15:43:00 2025
End Time:Thu Oct 9 19:59:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Thu Oct 9 21:31:55 2025
Root Cause:A dependent service that Intune and Entra admin center access requests rely on experienced a drop in availability, resulting in failures and errors when admin users attempted to access those admin centers.
Next Update:N/A

Details

Time:Thu Oct 9 21:04:45 2025
Description:Title: Some admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center
User impact: Admin users may have not been able to access the Microsoft Intune or Microsoft Entra ID admin center.
More info: Affected admin users were returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Final status: The dependent service that Intune and Entra admin center access relies upon has restored connections and we monitored our telemetry to validate that impact was remediated.
Scope of impact: Some admin users may have been unable to access the Microsoft Intune or Microsoft Entra admin center and were returned an error message stating "Error displaying your content" when they attempted to connect to the affected admin centers.
Start time: Thursday, October 9, 2025, at 7:43 PM UTC
End time: Thursday, October 9, 2025, at 11:59 PM UTC
Root cause: A dependent service that Intune and Entra admin center access requests rely on experienced a drop in availability, resulting in failures and errors when admin users attempted to access those admin centers.
Next steps: - We're continuing to analyze the issue with the dependent service to better understand what triggered the initial impact, which will help us in preventing similar impact from occurring in the future.
This is the final update for the event.
Time:Thu Oct 9 20:30:25 2025
Description:Title: Some admin users may not be able to access the Microsoft Intune or Microsoft Entra admin center
User impact: Admin users may not be able to access the Microsoft Intune or Microsoft Entra admin center.
More info: Affected admin users are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Current status: Based on monitoring, the vast majority of services have recovered and we've received confirmation from some affected admin users that the impact is remediated. We're performing further validation in our telemetry to confirm that the Microsoft Intune and Microsoft Entra admin centers are accessible in the affected regions.
Scope of impact: Some admin users may be unable to access the Microsoft Intune or Microsoft Entra ID admin center and are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Root cause: A dependent service that Intune and Entra admin center access requests rely on experienced a drop in availability, resulting in failures and errors when admin users attempt to access those admin centers.
Next update by: Friday, October 10, 2025, at 2:30 AM UTC
Time:Thu Oct 9 18:31:48 2025
Description:Title: Some admin users may not be able to access the Microsoft Intune or Microsoft Entra admin center
User impact: Admin users may not be able to access the Microsoft Intune or Microsoft Entra admin center.
More info: Affected admin users are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Current status: We've determined that a dependent service that Intune and Entra IDs portal access requests rely on experienced a drop in availability, resulting in failures and errors when admins attempt to access those portals. Our monitoring indicates that services are recovering and that some admin users may be seeing the impact remediate. We'll provide a timeline to mitigation as one becomes available.
Scope of impact: Some admin users may be unable to access the Microsoft Intune or Microsoft Entra ID admin center and are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Root cause: A dependent service that Intune and Entra IDs portal access requests rely on experienced a drop in availability, resulting in failures and errors when admin users attempt to access those portals.
Next update by: Friday, October 10, 2025, at 12:30 AM UTC
Time:Thu Oct 9 17:30:07 2025
Description:Title: Some admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center
User impact: Admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center.
More info: Affected admin users are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Current status: We received reports from affected admin users stating that they're unable to access the Microsoft Intune or Microsoft Entra ID admin center, and are now receiving reports from a subset of affected admin users that impact is now resolved. We're validating the root cause of impact and what actions were done, if any, to restore service.
Scope of impact: Some admin users may be unable to access the Microsoft Intune or Microsoft Entra ID admin center and are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Next update by: Thursday, October 9, 2025, at 11:30 PM UTC
Time:Thu Oct 9 17:05:38 2025
Description:Title: Some admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center
User impact: Admin users may not be able to access the Microsoft Intune or Microsoft Entra ID admin center.
More info: Affected admin users are returned an error message stating "Error displaying your content" when they attempt to connect to the affected admin center.
Current status: We're investigating a potential issue with the Microsoft 365 Suite and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1166829 - Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client

Status:serviceRestored
Start Time:Fri Oct 3 19:00:00 2025
End Time:Wed Oct 8 01:39:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Wed Oct 8 23:44:33 2025
Root Cause:A recent deployment introduced a code regression, which resulted in impact.
Next Update:N/A

Details

Time:Wed Oct 8 23:44:33 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users couldn't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempted to save an email or calendar event, they received a message that stated, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Final status: We've completed monitoring service health telemetry and confirmed that impact was remediated.
Scope of impact: Any user attempting to use the "Send to OneNote" feature to forward emails or calendar events to their OneNote notebooks may have been impacted.
Start time: Friday, October 3, 2025, at 11:00 PM UTC
End time: Wednesday, October 8, 2025, at 5:39 AM UTC
Root cause: A recent deployment introduced a code regression, which resulted in impact.
Next steps: - To help prevent similar impact in the future, we're further reviewing our deployment release procedures to identify code regressions before being initiated.
This is the final update for the event.
Time:Wed Oct 8 04:48:25 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: We've successfully deployed the fix addressing the code regression and we’re actively monitoring service telemetry to ensure that impact has been mitigated.
Scope of impact: Any user attempting to use the "Send to OneNote" feature to forward emails or calendar events to their OneNote notebooks may be impacted.
Start time: Friday, October 3, 2025, at 11:00 PM UTC
Root cause: A recent deployment introduced a code regression, resulting in impact.
Next update by: Wednesday, October 8, 2025, at 7:00 PM UTC
Time:Wed Oct 8 00:52:30 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: Our investigation determined a recent deployment introduced a code regression, which is leading to impact. We've developed and initiated deployment of a fix to restore service. We're monitoring as it progresses to determine a completion timeline.
Scope of impact: Your organization is affected by this event, and this issue prevents any user of the "Send to OneNote" feature from sending email or calendar events to their OneNote notebooks.
Start time: Friday, October 3, 2025, at 11:00 PM UTC
Root cause: A recent deployment introduced a code regression, which is leading to impact.
Next update by: Wednesday, October 8, 2025, at 9:00 AM UTC
Time:Tue Oct 7 12:21:29 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: We’re continuing our analysis of the change, which enables stricter compliance regulations, to confirm the root cause and identify a strategy that remediates impact.
Scope of impact: Your organization is affected by this event, and this issue prevents any user of the "Send to OneNote" feature from sending email or calendar events to their OneNote notebooks.
Next update by: Wednesday, October 8, 2025, at 6:00 AM UTC
Time:Mon Oct 6 20:18:14 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: Our review of the collected failing request IDs and service logs has determined that this issue may be related to a recent change which enables stricter compliance regulations. We’re further analyzing this change to confirm our suspicions into the underlying cause of impact which will help guide our troubleshooting steps.
Scope of impact: Your organization is affected by this event, and this issue prevents any user of the "Send to OneNote" feature from sending email or calendar events to their OneNote notebooks.
Next update by: Tuesday, October 7, 2025, at 5:30 PM UTC
Time:Mon Oct 6 18:17:15 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: We're able to reproduce the issue and have collected failing request IDs to review within our service logs. This analysis will help to pinpoint the reason for the failures and direct our next steps towards finding a solution.
Scope of impact: Your organization is affected by this event, and this issue prevents any user of the "Send to OneNote" feature from sending email or calendar events to their OneNote notebooks.
Next update by: Tuesday, October 7, 2025, at 12:30 AM UTC
Time:Mon Oct 6 17:54:55 2025
Description:Title: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client
User impact: Users can't send email or calendar events to OneNote through the "Send to OneNote" add-in in any Outlook client.
More info: When users attempt to save an email or calendar event, they receive a message that states, "Error: Cannot save this item to a shared notebook due to sensitivity label restrictions. Please save it to personal notebook."
Current status: We're investigating a potential issue with Exchange Online and OneNote, and we're checking for impact to your organization. We'll provide an update within 60 minutes.

PL1168478 - Users are unable to access the Planner app and receive an error message

Status:serviceRestored
Start Time:Wed Oct 8 19:54:00 2025
End Time:Wed Oct 8 22:36:00 2025
Service:Planner
Feature Group:Planner
Classification:incident
Last Updated:Wed Oct 8 23:36:12 2025
Root Cause:A specific authentication component within a recent deployment was preventing users from accessing the service.
Next Update:N/A

Details

Time:Wed Oct 8 23:22:27 2025
Description:Title: Users are unable to access the Planner app and receive an error message
User impact: Users were unable to access the Planner app and received an error message.
More info: Users received the following error message, "Office 365 Planner services aren't available right now. We're working to restore all services as soon as possible."
Final status: We've completed reconfiguring the offending component within the recent deployment and confirmed with internal validations that the impact is remediated and access to the service is restored.
Scope of impact: Your organization was affected by this event, and any user that attempted to access the Planner app was impacted.
Start time: Wednesday, October 8, 2025, at 11:54 PM UTC
End time: Thursday, October 9, 2025, at 2:36 AM UTC
Root cause: A specific authentication component within a recent deployment was preventing users from accessing the service.
Next steps: - We're further reviewing the recent deployment to understand how the issue with the specific authentication component was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future deployments.
This is the final update for the event.
Time:Wed Oct 8 21:30:01 2025
Description:Title: Users are unable to access the Planner app and receive an error message
User impact: Users are unable to access the Planner app and receive an error message.
More info: Users receive the following error message when attempting to open the Planner app, "Office 365 Planner services aren't available right now. We're working to restore all services as soon as possible."
Current status: We've identified an issue in which users are unable to access the Planner app and receive an error message. We've determined that a recent deployment introduced a misconfigured authentication component that’s preventing users from accessing the application. We're reconfiguring this component within the recent deployment, and anticipate the issue will be resolved and accessibility to the service restored by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to access the Planner app is impacted.
Start time: Wednesday, October 8, 2025, at 11:54 PM UTC
Root cause: A specific authentication component within a recent deployment is preventing users from accessing the application.
Next update by: Thursday, October 9, 2025, at 4:30 AM UTC

TM1168486 - Admins may be unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams

Status:serviceRestored
Start Time:Wed Oct 8 12:50:00 2025
End Time:Wed Oct 8 20:30:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Oct 8 22:29:53 2025
Root Cause:A recent update to the certificate authentication for a portion of Microsoft Teams service infrastructure contained a certificate configuration issue, which led to impact.
Next Update:N/A

Details

Time:Wed Oct 8 22:29:53 2025
Description:Title: Admins may be unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams
User impact: Admins may have been unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams.
Final status: We were alerted to an issue from our telemetry that indicated impact to the "create teams from a template" scenario in Microsoft Teams. We investigated the issue and our service logs, and identified a recent update to the certificate authentication for a portion of Microsoft Teams service infrastructure that contained a certificate configuration issue, which led to impact. We updated the configuration to correct the issue and confirmed through our telemetry that service health has been restored and the impact is remediated.
Scope of impact: Any admin located in North America may have been impacted and unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams.
Start time: Wednesday, October 8, 2025, at 4:50 PM UTC
End time: Thursday, October 9, 2025, at 12:30 AM UTC
Root cause: A recent update to the certificate authentication for a portion of Microsoft Teams service infrastructure contained a certificate configuration issue, which led to impact.
Next steps: - We're reviewing our update procedures to understand why impact wasn't identified earlier and how we can make improvements to identify and prevent similar issues in the future.
This is the final update for the event.
Time:Wed Oct 8 21:52:06 2025
Description:Title: Admins may be unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams
User impact: Admins may be unable to check the status of the 'Create teams from a template' scenario in Microsoft Teams.
Current status: We've investigated a problem that affected the ability to check the status of the "create teams from a template" scenario in Microsoft Teams and confirmed that the service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

MP1162928 - Users’ review set pagination options may be missing from Microsoft Purview eDiscovery (Premium)

Status:serviceRestored
Start Time:Mon Sep 29 09:10:00 2025
End Time:Tue Sep 30 23:05:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Wed Oct 8 13:34:11 2025
Root Cause:A recent service deployment intended to address an unrelated review set page display issue contained a code issue which resulted in impact.
Next Update:N/A

Details

Time:Wed Oct 1 16:45:45 2025
Description:Title: Users’ review set pagination options may be missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options may have been missing from eDiscovery (Premium).
Final status: We've confirmed after monitoring our service telemetry that the fix has resolved the issue.
Scope of impact: Any user who attempted to access the review set pagination options in eDiscovery (Premium) may have been impacted.
Start time: Monday, September 29, 2025, at 1:10 PM UTC
End time: Wednesday, October 1, 2025, at 3:05 AM UTC
Root cause: A recent service deployment intended to address an unrelated review set page display issue contained a code issue which resulted in impact.
Next steps: - We're reviewing our standard service update protocols to ensure similar code issues are identified and corrected ahead of deployment, so this doesn't occur again.
This is the final update for the event.
Time:Wed Oct 1 14:46:27 2025
Description:Title: Users’ review set pagination options may be missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options may be missing from eDiscovery (Premium).
Current status: We've confirmed the deployment has completed and we're monitoring the service to ensure the impact is fully remediated.
Scope of impact: Any user attempting to access the review set pagination options in eDiscovery (Premium) may be impacted.
Root cause: A recent service deployment intended to address an unrelated review set page display issue contained a code issue resulting in impact.
Next update by: Wednesday, October 1, 2025, at 9:00 PM UTC
Time:Tue Sep 30 20:19:15 2025
Description:Title: Users’ review set pagination options may be missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options may be missing from eDiscovery (Premium).
Current status: We've identified that a recent service deployment intended to address an unrelated review set page display issue contained a code issue resulting in impact. We've begun the process of deploying a fix to resolve the issue and anticipate this should complete, remediating impact, by the time of our next scheduled communications update.
Scope of impact: Any user attempting to access the review set pagination options in eDiscovery (Premium) may be impacted.
Root cause: A recent service deployment intended to address an unrelated review set page display issue contained a code issue resulting in impact.
Next update by: Wednesday, October 1, 2025, at 7:00 PM UTC
Time:Tue Sep 30 18:46:13 2025
Description:Title: Users’ review set pagination options are missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options are missing from eDiscovery (Premium).
Current status: While we've identified that a portion of infrastructure that facilitates the return and display of review set pagination options may not be operating in a healthy state, and we're attempting to reproduce this issue internally to determine the root cause and a strategy that remediates impact.
Scope of impact: Your organization is affected by this event, and any user attempting to access the review set pagination options in eDiscovery (Premium) is impacted.
Next update by: Wednesday, October 1, 2025, at 1:30 AM UTC
Time:Tue Sep 30 17:40:28 2025
Description:Title: Users’ review set pagination options are missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options are missing from eDiscovery (Premium).
Current status: We're reviewing support case data to identify why users’ review set pagination options are missing from eDiscovery (Premium).
Scope of impact: Your organization is affected by this event, and any user attempting to access the review set pagination options in eDiscovery (Premium) is impacted.
Next update by: Tuesday, September 30, 2025, at 11:00 PM UTC
Time:Tue Sep 30 17:24:43 2025
Description:Title: Users’ review set pagination options are missing from Microsoft Purview eDiscovery (Premium)
User impact: Users’ review set pagination options are missing from eDiscovery (Premium).
Current status: We're investigating a potential issue with eDiscovery (Premium) and checking for impact to your organization. We'll provide an update within 30 minutes.

FL1167519 - Users are unable to manage or run cloud and desktop flows

Status:serviceRestored
Start Time:Tue Oct 7 09:00:00 2025
End Time:Tue Oct 7 13:20:00 2025
Service:Microsoft Power Automate
Feature Group:Other
Classification:incident
Last Updated:Tue Oct 7 14:24:44 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Oct 7 14:24:44 2025
Description:Title: Users are unable to manage or run cloud and desktop flows
User impact: Users were unable to manage or run cloud and desktop flows.
Final Status: After a period of monitoring service health diagnostics, we have confirmed that flow management and runtime functionality have been restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the downstream storage infrastructure became unreachable due to a subset of network components entering an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
Time:Tue Oct 7 13:43:32 2025
Description:Title: Users are unable to manage or run cloud and desktop flows
User impact: Users are unable to manage or run cloud and desktop flows.
Current Status: Our investigation determined that a portion of the downstream storage infrastructure became unreachable due to a subset of network components entering an unhealthy state. We performed mitigation actions to restore the health of the affected components, and are now monitoring service health diagnostics for signs of recovery.
Next Update: Tuesday, October 7, 2025, at 8:00 PM UTC
Time:Tue Oct 7 13:25:27 2025
Description:Title: Users are unable to manage or run cloud and desktop flows
User impact: Users are unable to manage or run cloud and desktop flows.
Current Status: We are aware of an emerging issue where users are unable to perform flow management operations (create, edit, delete) or run flows in your environment. 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.

EX1166774 - Some users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method

Status:serviceRestored
Start Time:Mon Oct 6 11:58:00 2025
End Time:Mon Oct 6 18:18:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Mon Oct 6 19:43:04 2025
Root Cause:A portion of infrastructure responsible for request flow traffic wasn't updated and thus couldn't process traffic at the expected thresholds, which resulted in impact.
Next Update:N/A

Details

Time:Mon Oct 6 19:43:04 2025
Description:Title: Some users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method
User impact: Users may have intermittently encountered delays or timeouts accessing Exchange Online using any connection method.
More info: Affected connection methods included -
Exchange ActiveSync (EAS) Internet Message Access Protocol (IMAP) Messaging API (MAPI) Outlook on the web Representational State Transfer (REST)
Final status: Our investigation identified that a portion of infrastructure responsible for request flow traffic wasn't updated and thus couldn't process traffic at the expected thresholds. We've since manually updated the infrastructure and after a period of monitoring, have confirmed that impact has been alleviated by our actions.
Scope of impact: Any user in the United States region may have been intermittently impacted.
Start time: Monday, October 6, 2025, at 3:58 PM UTC
End time: Monday, October 6, 2025, at 10:18 PM UTC
Root cause: A portion of infrastructure responsible for request flow traffic wasn't updated and thus couldn't process traffic at the expected thresholds, which resulted in impact.
Next steps: - We're analyzing why the update didn't get applied to this portion of infrastructure in an effort to prevent this issue from happening again.
This is the final update for the event.
Time:Mon Oct 6 18:00:15 2025
Description:Title: Some users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method
User impact: Users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method.
More info: Affected connection methods include -
Exchange ActiveSync (EAS) Internet Message Access Protocol (IMAP) Messaging API (MAPI) Outlook on the web Representational State Transfer (REST)
Current status: Our investigation into authentication logs is ongoing as we work to identify the source of the authentication component issue, which we suspect is related to the impact.
Scope of impact: Any user in the United States region may be intermittently impacted.
Start time: Monday, October 6, 2025, at 3:58 PM UTC
Next update by: Tuesday, October 7, 2025, at 1:00 AM UTC
Time:Mon Oct 6 15:25:21 2025
Description:Title: Some users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method
User impact: Users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method.
More info: Affected connection methods include -
Exchange ActiveSync (EAS) Internet Message Access Protocol (IMAP) Messaging API (MAPI) Outlook on the web Representational State Transfer (REST)
Current status: Our initial analysis of service telemetry indicates that an authentication component isn't responding as expected. We're expanding our investigation to include authentication logs and develop remediation options.
Scope of impact: Any user in the United States region may be intermittently impacted.
Start time: Monday, October 6, 2025, at 3:58 PM UTC
Next update by: Monday, October 6, 2025, at 11:30 PM UTC
Time:Mon Oct 6 14:28:15 2025
Description:Title: Some users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method
User impact: Users may intermittently encounter delays or timeout errors accessing Exchange Online using any connection method.
More info: Affected connection methods include -
Exchange ActiveSync (EAS) Internet Message Access Protocol (IMAP) Messaging API (MAPI) Outlook on the web Representational State Transfer (REST)
Current status: We're reviewing service telemetry of the affected infrastructure to better understand the nature of impact and determine our next diagnostics steps.
Scope of impact: Any user in the United States region may be intermittently impacted.
Next update by: Monday, October 6, 2025, at 7:30 PM UTC
Time:Mon Oct 6 13:44:00 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.

TM1166675 - Admins may be unable to change user calling settings in the Microsoft Teams admin center or PowerShell

Status:serviceRestored
Start Time:Mon Oct 6 05:42:00 2025
End Time:Mon Oct 6 10:46:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Oct 6 11:22:54 2025
Root Cause:A recent service update contained a code change that caused impact.
Next Update:N/A

Details

Time:Mon Oct 6 11:22:54 2025
Description:Title: Admins may be unable to change user calling settings in the Microsoft Teams admin center or PowerShell
User impact: Admins may have been unable to change user calling settings in the Microsoft Teams admin center or PowerShell.
Final status: We've identified that a recent service update contained a code change that caused impact. We've reversed the offending service update and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Any admin attempting to change user calling settings in the Microsoft Teams admin center or PowerShell may have been impacted.
Start time: Monday, October 6, 2025, at 9:42 AM UTC
End time: Monday, October 6, 2025, at 2:46 PM UTC
Root cause: A recent service update contained a code change that caused impact.
Next steps: - We're reviewing our service update testing and validation procedures to identify and prevent similar issues with code changes in deployments moving forward.
This is the final update for the event.
Time:Mon Oct 6 11:00:28 2025
Description:Title: Admins may be unable to change user calling settings in the Microsoft Teams admin center or PowerShell
User impact: Admins may have been unable to change user calling settings in the Microsoft Teams admin center or PowerShell.
Current status: We've investigated a problem in which admins may have been unable to change user calling settings in the Microsoft Teams admin center or PowerShell 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.

SP1164059 - Admins are unable to conduct cross-tenant migrations for SharePoint Online

Status:serviceRestored
Start Time:Tue Sep 23 03:29:00 2025
End Time:Fri Oct 3 02:00:00 2025
Service:SharePoint Online
Feature Group:Tenant Admin
Classification:advisory
Last Updated:Mon Oct 6 08:36:49 2025
Root Cause:A recent feature update, designed to improve the overall experience of the environment, has unintentionally caused a service regression, resulting in impact.
Next Update:N/A

Details

Time:Mon Oct 6 08:36:49 2025
Description:Title: Admins are unable to conduct cross-tenant migrations for SharePoint Online
User impact: Admins are unable to conduct cross-tenant migrations for SharePoint Online.
More Info: When performing a cross-tenant migration, please note that pre-provisioning Microsoft 365 Groups in the target tenant using the 'New-UnifiedGroup' PowerShell cmdlet will immediately create the associated SharePoint Online (SPO) site. This automatic site creation causes the 'Start-SPOCrossTenantSiteContentMove' migration to fail, as the site is already provisioned in the target tenant.
Final status: We’ve proposed actions to correct the misconfiguration preventing cross-tenant migrations. While we have not received confirmation from your representatives due to challenges with your organisation’s PowerShell environment, we’ve validated the solution internally and confirmed it resolves the problem under expected conditions. If impact persists following implementation of the steps provided, please contact support to continue the investigation.
This is the final update for the event.
Time:Fri Oct 3 06:16:24 2025
Description:Title: Admins are unable to conduct cross-tenant migrations for SharePoint Online
User impact: Admins are unable to conduct cross-tenant migrations for SharePoint Online.
More Info: When performing a cross-tenant migration, please note that pre-provisioning Microsoft 365 Groups in the target tenant using the 'New-UnifiedGroup' PowerShell cmdlet will immediately create the associated SharePoint Online (SPO) site. This automatic site creation causes the 'Start-SPOCrossTenantSiteContentMove' migration to fail, as the site is already provisioned in the target tenant.
Current Status: We've verified some mitigation steps to fix the issue. We're working with your organization's representatives to action these and expect impact to be mitigated by the next scheduled update.
Scope of Impact: Impact is specific to some admins who are attempting to conduct cross-tenant migrations for SharePoint Online.
Root Cause: A recent feature update, designed to improve the overall experience of the environment, has unintentionally caused a service regression, resulting in impact.
Next update by: Monday, October 6, 2025, at 2:00 PM UTC
Time:Thu Oct 2 05:39:32 2025
Description:Title: Admins are unable to conduct cross-tenant migrations for SharePoint Online
User Impact: Admins are unable to conduct cross-tenant migrations for SharePoint Online.
More Info: When performing a cross-tenant migration, please note that pre-provisioning Microsoft 365 Groups in the target tenant using the 'New-UnifiedGroup' PowerShell cmdlet will immediately create the associated SharePoint Online (SPO) site. This automatic site creation causes the 'Start-SPOCrossTenantSiteContentMove' migration to fail, as the site is already provisioned in the target tenant.
Current Status: We’ve identified that a recent feature update, designed to improve the overall experience of the environment, has unintentionally caused a service regression, resulting in impact. We're actively evaluating the most effective mitigation strategy to resolve the issue.
Scope of Impact: Impact is specific to some admins who are attempting to conduct cross-tenant migrations for SharePoint Online.
Root Cause: A recent feature update, designed to improve the overall experience of the environment, has unintentionally caused a service regression, resulting in impact.
Next Update by: Friday, October 3, 2025, at 10:30 AM UTC
Time:Thu Oct 2 04:00:31 2025
Description:Title: Admins are unable to conduct cross-tenant migrations for SharePoint Online
User Impact: Admins are unable to conduct cross-tenant migrations for SharePoint Online.
Current Status: We're reviewing support provided information and reproducing the issue internally, to determine our next troubleshooting steps.
Scope of Impact: Impact is specific to some admins who are attempting to conduct cross-tenant migrations for SharePoint Online.
Next Update Time: Thursday, October 02, 2025, at 10:00 AM UTC

TM1156052 - Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams

Status:serviceRestored
Start Time:Tue Sep 16 08:49:00 2025
End Time:Wed Oct 1 14:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Oct 3 15:12:08 2025
Root Cause:A recent update intended to bolster Copilot performance introduced a regression that resulted in impact.
Next Update:N/A

Details

Time:Fri Oct 3 15:12:08 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button was missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may have also been impacted. The problem occured in all Microsoft Teams connection methods.
Final status: After a review of telemetry showing Copilot dictate usage returning to pre-impact levels, we've confirmed the impact is remediated. Users who aren't able to see the dictate button will need to restart Teams to resolve the issue.
Scope of impact: Users who attempted to use the dictation feature in platform apps and Copilot within Microsoft Teams were impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
End time: Wednesday, October 1, 2025, at 6:00 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that resulted in impact.
Next steps: - We're reviewing our update release standards to ensure similar issues are caught and addressed ahead of deployment to prevent this from occurring again.
This is the final update for the event.
Time:Thu Oct 2 15:40:27 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Our fix deployment is complete, and we’ve confirmed that the issue is resolved for the majority of affected users. We’ve received reports that some users still don’t see the dictate button, and we’re working with those users to collect fresh reproduction information to determine whether any additional remediation steps will be necessary.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Friday, October 3, 2025, at 8:30 PM UTC
Time:Fri Sep 26 15:08:28 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: The fix deployment has saturated across ten percent of the environment, and we're monitoring to ensure it continues to progress at an acceptable pace. We'll update the expected timeline for relief when possible.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Thursday, October 2, 2025, at 8:30 PM UTC
Time:Wed Sep 24 14:23:38 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Validations have completed and we've begun deploying the fix to the affected environment and we'll provide a timeline for remediation as one becomes available.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Friday, September 26, 2025, at 8:30 PM UTC
Time:Tue Sep 23 18:26:40 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Validations are nearing completion, and we anticipate the deployment will have been initiated by the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Wednesday, September 24, 2025, at 8:00 PM UTC
Time:Tue Sep 23 15:30:46 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We've discovered that one additional round of validations are required before we deploy the code fix to address performance degradations and restore the Copilot dictate button to Microsoft Teams. We aim to provide a timeline for the deployment of our code fix at the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Wednesday, September 24, 2025, at 12:00 AM UTC
Time:Mon Sep 22 15:16:51 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We're completing the final round of validations for our code fix to address performance degradations and to restore the Copilot dictate button to Microsoft Teams. We aim to provide a timeline for the deployment of our code fix at the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Tuesday, September 23, 2025, at 8:30 PM UTC
Time:Fri Sep 19 16:22:19 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We've identified that a recent update intended to bolster Copilot performance introduced a regression that's resulting in impact. We've developed, tested and are releasing a code fix that we anticipate will alleviate impact. We’ll provide an update on the status of the fix by our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Monday, September 22, 2025, at 8:30 PM UTC
Time:Fri Sep 19 15:35:18 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
Current status: We're investigating a potential issue in which users Copilot dictate button is missing within Microsoft Teams. We'll provide an update within 30 minutes.

CP1156051 - Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams

Status:serviceRestored
Start Time:Tue Sep 16 08:49:00 2025
End Time:Wed Oct 1 14:00:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Fri Oct 3 15:11:43 2025
Root Cause:A recent update intended to bolster Copilot performance introduced a regression that resulted in impact.
Next Update:N/A

Details

Time:Fri Oct 3 15:11:43 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button was missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may have also been impacted. The problem occured in all Microsoft Teams connection methods.
Final status: After a review of telemetry showing Copilot dictate usage returning to pre-impact levels, we've confirmed the impact is remediated. Users who aren't able to see the dictate button will need to restart Teams to resolve the issue.
Scope of impact: Users who attempted to use the dictation feature in platform apps and Copilot within Microsoft Teams were impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
End time: Wednesday, October 1, 2025, at 6:00 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that resulted in impact.
Next steps: - We're reviewing our update release standards to ensure similar issues are caught and addressed ahead of deployment to prevent this from occurring again.
This is the final update for the event.
Time:Thu Oct 2 15:40:23 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Our fix deployment is complete, and we’ve confirmed that the issue is resolved for the majority of affected users. We’ve received reports that some users still don’t see the dictate button, and we’re working with those users to collect fresh reproduction information to determine whether any additional remediation steps will be necessary.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Friday, October 3, 2025, at 8:30 PM UTC
Time:Fri Sep 26 15:08:09 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: The fix deployment has saturated across ten percent of the environment, and we're monitoring to ensure it continues to progress at an acceptable pace. We'll update the expected timeline for relief when possible.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Thursday, October 2, 2025, at 8:30 PM UTC
Time:Wed Sep 24 14:23:47 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Validations have completed and we've begun deploying the fix to the affected environment and we'll provide a timeline for remediation as one becomes available.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Friday, September 26, 2025, at 8:30 PM UTC
Time:Tue Sep 23 18:26:49 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: Validations are nearing completion, and we anticipate the deployment will have been initiated by the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Wednesday, September 24, 2025, at 8:00 PM UTC
Time:Tue Sep 23 15:28:55 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We've discovered that one additional round of validations are required before we deploy the code fix to address performance degradations and restore the Copilot dictate button to Microsoft Teams. We aim to provide a timeline for the deployment of our code fix at the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Wednesday, September 24, 2025, at 12:00 AM UTC
Time:Mon Sep 22 15:16:49 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We're completing the final round of validations for our code fix to address performance degradations and to restore the Copilot dictate button to Microsoft Teams. We aim to provide a timeline for the deployment of our code fix at the time of our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Tuesday, September 23, 2025, at 8:30 PM UTC
Time:Fri Sep 19 16:23:31 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
More info: Platform apps within Microsoft Teams that use the dictation feature may also be impacted. The problem occurs in all Microsoft Teams connection methods.
Current status: We've identified that a recent update intended to bolster Copilot performance introduced a regression that's resulting in impact. We've developed, tested and are releasing a code fix that we anticipate will alleviate impact. We’ll provide an update on the status of the fix by our next scheduled update.
Scope of impact: Users who attempt to use the dictation feature in platform apps and Copilot within Microsoft Teams are impacted.
Start time: Tuesday, September 16, 2025, at 12:49 PM UTC
Root cause: A recent update intended to bolster Copilot performance introduced a regression that's resulting in impact.
Next update by: Monday, September 22, 2025, at 8:30 PM UTC
Time:Fri Sep 19 15:34:15 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) dictate button is missing within Microsoft Teams
User impact: Users' Copilot dictate button is missing within Microsoft Teams.
Current status: We're investigating a potential issue in which users Copilot dictate button is missing within Microsoft Teams. We'll provide an update within 30 minutes.

MV1164906 - Some users may encounter delays or timeout errors when accessing group feeds in Microsoft Viva Engage

Status:serviceRestored
Start Time:Fri Oct 3 11:12:00 2025
End Time:Fri Oct 3 12:30:00 2025
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Fri Oct 3 13:47:28 2025
Root Cause:A recent service update contained a code error, that resulted in impact.
Next Update:N/A

Details

Time:Fri Oct 3 13:47:28 2025
Description:Title: Some users may encounter delays or timeout errors when accessing group feeds in Microsoft Viva Engage
User impact: Users may have encountered delays or timeout errors when accessing group feeds in Microsoft Viva Engage.
Final status: We've completed the reversion of the change that resulted in impact, and our monitoring has confirmed this issue is no longer occurring.
Scope of impact: Some users in the United States region may have been affected.
Start time: Friday, October 3, 2025, at 3:12 PM UTC
End time: Friday, October 3, 2025, at 4:30 PM UTC
Root cause: A recent service update contained a code error, that resulted in 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:Fri Oct 3 13:08:26 2025
Description:Title: Some users may encounter delays or timeout errors when accessing group feeds in Microsoft Viva Engage
User impact: Users may encounter delays or timeout errors when accessing group feeds in Microsoft Viva Engage.
Current status: Our monitoring has identified an increase in errors accessing group feeds in Viva Engage. We've reviewed service telemetry and determined that a recent service update contains a code error, resulting in impact. We're in the process of initiating a revert for this change and will provide a remediation timeline once available.
Scope of impact: Some users in the United States region may be affected.
Start time: Friday, October 3, 2025, at 3:12 PM UTC
Root cause: A recent service update contains a code error, resulting in impact.
Next update by: Friday, October 3, 2025, at 6:30 PM UTC
Time:Fri Oct 3 12:46:32 2025
Description:Title: Some users may encounter delays or timeout errors when accessing group feeds in Microsoft Viva Engage
User impact: Users may encounter delays or timeout errors when accessing group feeds 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.

EX1162980 - Some users experienced errors or failures when accessing their mailbox in one or more Exchange Online connection methods

Status:serviceRestored
Start Time:Tue Sep 30 19:27:00 2025
End Time:Wed Oct 1 07:15:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Fri Oct 3 13:33:04 2025
Root Cause:A recent configuration change unexpectedly caused a portion of infrastructure responsible for processing request flow traffic to operate below expected thresholds, resulting in impact.
Next Update:N/A

Details

Time:Wed Oct 1 07:39:54 2025
Description:Title: Some users experienced errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Some users experienced errors or failures when accessing their mailbox in one or more Exchange Online connection methods
More info: Impact more heavily affected Outlook.com users.
Final status: After subsequent investigations and telemetry analysis, we’ve confirmed that this incident only affected the Consumer account environment. The issue did not affect the Enterprise environment. As such, your organization was not impacted by this event.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may have been impacted.
Start time: Tuesday, September 30, 2025 at 11:27 PM
End Time: Wednesday, October 1, 2025 at 11:15 AM
Root cause: A recent configuration change unexpectedly caused a portion of infrastructure responsible for processing request flow traffic to operate below expected thresholds, resulting in impact.
Next Steps: - Previously, within this communication, we stated that we would provide a Post-Incident Report within 5 business days. As there was no Enterprise environment impact, we will no longer be providing a Post-Incident Report. This is the final update for this event.
This is the final update for this event.
Time:Wed Oct 1 06:29:00 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
More info: Impact more heavily affects Outlook.com users.
Current status: We’ve confirmed that service availability has almost returned to normal levels, and most users should be experiencing relief. For the remaining limited impact, we’re continuing to perform systematic restarts to ensure full recovery.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic is operating below expected thresholds, resulting in impact.
Next update by: Wednesday, October 1, 2025, at 12:30 PM UTC
Time:Wed Oct 1 05:03:20 2025
Description:We’re continuing to observe steady improvements in service availability while the backlog of messages is progressing as expected.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 1 04:14:10 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
More info: Impact more heavily affects Outlook.com users.
Current status: Service availability is steadily improving, and the backlog of messages is being processed. We’re actively monitoring service telemetry to ensure a complete recovery.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic is operating below expected thresholds, resulting in impact.
Next update by: Wednesday, October 1, 2025, at 10:30 AM UTC
Time:Wed Oct 1 03:37:01 2025
Description:We’re observing improvements in service availability following our targeted restarts. We’re closely monitoring to ensure full recovery.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 1 02:54:02 2025
Description:We’re continuing to closely monitor service availability and we're performing additional targeted restarts where required.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 1 02:11:28 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
More info: Impact more heavily affects Outlook.com users.
Current status: We’ve confirmed the revert and subsequent manual restarts of affected infrastructure has been successful. We’ll continue to apply these targeted restarts as we monitor the service for recovery.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic that isn't operating at expected thresholds and this is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 8:30 AM UTC
Time:Wed Oct 1 01:06:23 2025
Description:As we monitor the service revert, we’re also applying smaller targeted reboots of affected infrastructure to further alleviate impact. We’re slowly seeing a gradual decrease in traffic errors.
This quick update is designed to give the latest information on this issue.
Time:Wed Oct 1 00:57:30 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
More info: Impact more heavily affects Outlook.com users.
Current status: We’ve isolated and have reverted a recent configuration change that we suspect to be contributing to user impact. We'll continue monitoring this revert and in tandem we'll explore additional solutions to further expedite mitigation efforts.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic that isn't operating at expected thresholds, and this is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 7:00 AM UTC
Time:Tue Sep 30 23:22:58 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
More info: Impact more heavily affects Outlook.com users.
Current status: We're continuing to monitor our traffic redistribution out of the affected infrastructure, however this is not resolving the impact as we anticipated. We’re reviewing additional logging to develop alternate mitigation options to address the continual service errors.
In addition, we've confirmed impact is more heavily affecting Outlook.com users rather than our Microsoft 365 Exchange users.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic that isn't operating at expected thresholds and this is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 6:00 AM UTC
Time:Tue Sep 30 21:56:41 2025
Description:Title: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox in one or more Exchange Online connection methods.
Current status: We've identified a portion of infrastructure responsible for processing request flow traffic that isn't operating at expected thresholds. We've since redistributed traffic to alternate infrastructure and are monitoring to confirm if our actions alleviate impact as expected.
Scope of impact: Users attempting to access their mailbox in one or more Exchange Online connection methods may be impacted.
Root cause: A portion of infrastructure responsible for processing request flow traffic that isn't operating at expected thresholds and this is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 4:00 AM UTC
Time:Tue Sep 30 20:15:50 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.

EX1162604 - Some users may not see auto-complete suggestions when searching in Outlook on the web

Status:serviceRestored
Start Time:Wed Aug 27 02:35:00 2025
End Time:Wed Oct 1 11:11:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Fri Oct 3 12:10:46 2025
Root Cause:A recent service update contained a code regression that caused impact.
Next Update:N/A

Details

Time:Fri Oct 3 12:10:46 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may have not seen auto-complete suggestions when searching in Outlook on the web.
More info: Users may have also not seen expected results when searching with keywords. As a workaround, suggestions were working on the Outlook mobile application.
Final status: We've confirmed after testing and monitoring with a subset of affected users that the impact is remediated.
Scope of impact: Impact was specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
End time: Wednesday, October 1, 2025, at 3:11 PM UTC
Root cause: A recent service update contained a code regression that caused impact.
Next steps: - We're reviewing our update protocols to ensure similar code issues are identified and corrected ahead of deployment so this doesn't happen again.
This is the final update for the event.
Time:Fri Oct 3 08:44:00 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We're reaching out to your representatives to confirm that impact has fully remediated.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Saturday, October 4, 2025, at 6:00 AM UTC
Time:Thu Oct 2 12:38:37 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: Our verification efforts are ongoing as we work closely with a subset of affected users to validate our rollback has fully remediated impact.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Friday, October 3, 2025, at 1:00 PM UTC
Time:Thu Oct 2 04:55:03 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We continue our in depth testing with a subset of affected users to validate during peak traffic hours to confirm if the rollback of the update was successful in resolving impact.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Thursday, October 2, 2025, at 5:30 PM UTC
Time:Wed Oct 1 21:25:56 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We're continuing to work with a subset of affected users to test and monitor during peak traffic hours to determine if the rollback of the update was successful in remediating impact.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Thursday, October 2, 2025, at 9:00 AM UTC
Time:Wed Oct 1 11:59:11 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’ve reverted the update containing the code regression to mitigate impact, and we’re reaching out to a subset of affected users to test if this rollback successfully resolved the issue.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Thursday, October 2, 2025, at 3:00 AM UTC
Time:Wed Oct 1 09:21:37 2025
Description:Title: Some users may not see auto-complete suggestions when searching in Outlook on the web
User impact: Users may not see auto-complete suggestions when searching in Outlook on the web.
More info: Users may also not see expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’ve identified that a recent standard service update inadvertently contains a code regression that's causing impact. We're reverting the update to mitigate impact and anticipate this process will be complete by our next scheduled update.
Scope of impact: Impact is specific to some users expecting to see auto-complete suggestions when searching in Outlook on the web.
Start time: Wednesday, August 27, 2025, at 6:35 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression that's causing impact.
Next update by: Wednesday, October 1, 2025, at 4:00 PM UTC
Time:Wed Oct 1 08:05:38 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’re continuing to analyze backend logs and error data from impacted environments to determine the cause and formulate a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Wednesday, October 1, 2025, at 2:00 PM UTC
Time:Wed Oct 1 05:51:42 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’re analyzing backend logs and error data from impacted environments to determine the cause and formulate a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Wednesday, October 1, 2025, at 12:00 PM UTC
Time:Tue Sep 30 17:57:50 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’ve isolated some 500 errors in our logs and we’re investigating these errors to determine the cause and formulate a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Wednesday, October 1, 2025, at 10:00 AM UTC
Time:Tue Sep 30 14:07:38 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: Our analysis of the HAR file and API call patterns has pointed the investigation towards a portion of infrastructure that handles message flow. We're investigating this correlation to determine if it's the origin of impact or a symptom of the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Tuesday, September 30, 2025, at 11:00 PM UTC
Time:Tue Sep 30 11:12:26 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’re analyzing the provided HAR file and API call patterns to isolate a potential root cause and to determine our next troubleshooting steps. We anticipate this process to be completed by the time of our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Tuesday, September 30, 2025, at 7:30 PM UTC
Time:Tue Sep 30 09:30:41 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’re proceeding with our analysis of the aforementioned HAR and API call patterns to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Tuesday, September 30, 2025, at 3:30 PM UTC
Time:Tue Sep 30 07:29:23 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
Current status: We’re continuing to review HTTP Archive (HAR) files and API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Tuesday, September 30, 2025, at 1:30 PM UTC
Time:Tue Sep 30 05:52:17 2025
Description:Title: Some users aren't getting auto-complete suggestions when searching in Outlook on the web
User impact: Users aren't getting auto-complete suggestions when searching in Outlook on the web.
More info: Users aren't also seeing expected results when searching with keywords. As a workaround, suggestions are working on the Outlook mobile application.
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: Your organization is affected by this event, and some users attempting to search in Outlook on the web are impacted.
Next update by: Tuesday, September 30, 2025, at 11:30 AM UTC

MO1164360 - Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center

Status:serviceRestored
Start Time:Thu Oct 2 15:00:00 2025
End Time:Thu Oct 2 20:35:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Thu Oct 2 20:53:01 2025
Root Cause:A recent User Experience (UX) change for the Microsoft 365 admin center licenses list page to introduce new service properties contained a misconfiguration which was resulting in impact.
Next Update:N/A

Details

Time:Thu Oct 2 20:53:01 2025
Description:Title: Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center
User impact: Admins may not have seen any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
More info: Users could have directly managed their licenses via either PowerShell or a Microsoft Graph API query.
Admins could have also used the Users tab in the Microsoft 365 admin center to manage licenses for individuals within their organization.
Final status: We’ve validated that the hotfix added the missing UX elements to the Microsoft 365 admin center Licenses page and deployed it to the affected infrastructure. We’ve subsequently monitored our telemetry to ensure that the user impact is remediated.
Scope of impact: Some admins may not have seen any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 7:00 PM UTC
End time: Friday, October 3, 2025, at 12:35 AM UTC
Root cause: A recent User Experience (UX) change for the Microsoft 365 admin center licenses list page to introduce new service properties contained a misconfiguration which was resulting in impact.
Next steps: - We're reviewing our code analysis procedures to develop better methods of detecting similar misconfigurations prior to their implementation in the future.
This is the final update for the event.
Time:Thu Oct 2 18:36:22 2025
Description:Title: Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center
User impact: Admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
More info: Users can directly manage their licenses via either PowerShell or a Microsoft Graph API query.
Admins can also use the Users tab in the Microsoft 365 admin center to manage licenses for individuals within their organization.
Current status: We're validating our hotfix to add the missing UX elements back to the Microsoft 365 admin center Licenses page internally, after which we’ll deploy the hotfix to a subset of regions to validate that the fix is successful before proceeding with a general rollout. We aim to provide a timeline to mitigation once we commence our general rollout.
Scope of impact: Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 7:00 PM UTC
Root cause: A recent User Experience (UX) change for the Microsoft 365 admin center licenses list page to introduce new service properties contains a misconfiguration which is resulting in the Licenses page to not show data.
Next update by: Friday, October 3, 2025, at 1:00 AM UTC
Time:Thu Oct 2 17:43:39 2025
Description:Title: Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center
User impact: Admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
More info: Users can directly manage their licenses via either PowerShell or a Microsoft Graph API query.
Admins can also use the Users tab in the Microsoft 365 admin center to manage licenses for individuals within their organization.
Current status: We've isolated that a recent User Experience (UX) change for the Microsoft 365 admin center licenses list page to introduce new service properties contains a misconfiguration which is resulting in the Licenses page to not show data. We're creating a fix to retrieve the missing UX properties and we aim to provide a timeline to resolution once we've validated a deployment timeline.
Scope of impact: Some admins may not see any products or subscriptions in the Licenses page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 7:00 PM UTC
Root cause: A recent User Experience (UX) change for the Microsoft 365 admin center licenses list page to introduce new service properties contains a misconfiguration which is resulting in the Licenses page to not show data.
Next update by: Thursday, October 2, 2025, at 11:00 PM UTC

TM1164063 - Some users may have been unable to download the correct Microsoft Teams Windows client installer

Status:serviceRestored
Start Time:Wed Oct 1 21:14:00 2025
End Time:Thu Oct 2 10:15:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Oct 2 10:58:06 2025
Root Cause:A recent configuration change to the format of how the Microsoft Teams Windows client installer is downloaded caused impact to occur.
Next Update:N/A

Details

Time:Thu Oct 2 10:53:26 2025
Description:Title: Some users may have been unable to download the correct Microsoft Teams Windows client installer
User impact: Users may have been unable to download the correct Microsoft Teams Windows client installer.
More info: Affected users were getting an installer with a .gz extesion when attempting to download the installer from the download site.
As a workaround, affected users were recommended to download the installer using the Microsoft Store App using the following steps: - Go to Microsoft Store - https://apps.microsoft.com/ - Search "Microsoft Teams" - Result will show the Teams app - Select and "Download" the app - Install the app once the .exe file has been downloaded
Final status: We've determined that a recent configuration change to the format of how the Microsoft Teams Windows client installer is downloaded caused impact to occur. We've implemented a fix to the affected infrastructure and confirmed that impact has been remediated.
Scope of impact: Impact was specific to users attempting to download the Microsoft Teams installer.
Start time: Thursday, October 2, 2025, at 1:14 AM UTC
End time: Thursday, October 2, 2025, at 2:15 PM UTC
Root cause: A recent configuration change to the format of how the Microsoft Teams Windows client installer is downloaded caused impact to occur.
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 Oct 2 07:00:35 2025
Description:Title: Some users may be unable to download the correct Microsoft Teams Windows client installer
User impact: Users may be unable to download the correct Microsoft Teams Windows client installer.
More info: Affected users when attempting to download the installer from the download site, the installer will be downloaded with a .gz extension.
As a workaround, affected users are recommended to download installer using Microsoft Store App to download Microsoft Teams Windows client using the following steps:
Go to Microsoft Store - https://apps.microsoft.com/ Search "Microsoft Teams" Result will show the Teams app Select and "Download" the app Install the app - Once exe file is downloaded
Current status: We're reviewing any recent changes that we suspect may be causing the impact to occur, and this will help us identify the origin of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to users attempting to download the Microsoft Teams installer.
Next update by: Thursday, October 2, 2025, at 3:00 PM UTC
Time:Thu Oct 2 04:58:17 2025
Description:Title: Some users may be unable to download the correct Microsoft Teams Windows client installer
User impact: Users may be unable to download the correct Microsoft Teams Windows client installer.
More info: Affected users when attempting to download the installer from the download site, the installer will be downloaded with a .gz extension.
As a workaround, affected users are recommended to download installer using Microsoft Store App to download Microsoft Teams Windows client using the following steps:
Go to Microsoft Store - https://apps.microsoft.com/ Search "Microsoft Teams" Result will show the Teams app Select and "Download" the app Install the app - Once exe file is downloaded
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to users attempting to download the Microsoft Teams installer.
Next update by: Thursday, October 2, 2025, at 11:00 AM UTC

EX1159552 - Some admins are intermittently unable to download extended message traces from the Exchange Online admin center

Status:serviceRestored
Start Time:Sun Sep 21 20:00:00 2025
End Time:Wed Oct 1 15:00:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Wed Oct 1 15:33:27 2025
Root Cause:A misconfiguration within a portion of service infrastructure responsible for facilitating the download of extended message traces was intermittently preventing the download process from completing and was causing impact.
Next Update:N/A

Details

Time:Wed Oct 1 15:31:45 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins were intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurred for both on-demand and scheduled extended message traces.
When affected admins attempted to download extended message traces, the download didn't complete and they received an error that stated there was a network issue.
Affected admins were able to download the extended message traces as expected upon subsequent retries.
Final status: We've completed the deployment of the fix and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Your organization was affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center were intermittently impacted.
Start time: Monday, September 22, 2025, at 12:00 AM UTC
End time: Wednesday, October 1, 2025, at 7:00 PM UTC
Root cause: A misconfiguration within a portion of service infrastructure responsible for facilitating the download of extended message traces was intermittently preventing the download process from completing and was causing impact.
Next steps: - We're reviewing the impacting portion of service infrastructure to determine how the misconfiguration was introduced into the service, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Mon Sep 29 15:45:24 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: After deploying our solution, our service telemetry has validated that it is remediating impact and reducing the failures admins see when downloading extended message traces. Our fix has completed approximately 30 percent of the necessary deployment, and our timeline estimates that it will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Start time: Monday, September 22, 2025, at 12:00 AM UTC
Root cause: A misconfiguration within a portion of service infrastructure responsible for facilitating the download of extended message traces is intermittently preventing the download process from completing and is causing impact.
Next update by: Wednesday, October 1, 2025, at 9:00 PM UTC
Time:Fri Sep 26 16:54:59 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We've verified that the aforementioned configuration change remediates the impact within our testing environment and are preparing to deploy a service update containing this change to the affected users. We anticipate that this should start saturating by the time of our next update.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Start time: Monday, September 22, 2025, at 12:00 AM UTC
Root cause: A misconfiguration within the portions of service infrastructure responsible for facilitating the download of extended message traces is intermittently preventing the download process from completing and is causing impact.
Next update by: Monday, September 29, 2025, at 9:00 PM UTC
Time:Fri Sep 26 15:24:53 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We're applying configuration changes to the portions of service infrastructure responsible for facilitating the download of extended message traces within our testing environment, so that we can determine whether they remediate the impact.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Friday, September 26, 2025, at 9:30 PM UTC
Time:Fri Sep 26 05:40:32 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We're continuing with further efforts to reproduce the issue internally to aid us in diagnosing the underlying root cause and determining our options for remediation.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Friday, September 26, 2025, at 8:00 PM UTC
Time:Fri Sep 26 00:50:18 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: Our preliminary analysis of the most-recently collected telemetry data has been inconclusive. We're proceeding with further efforts to reproduce the issue internally to aid us in diagnosing the underlying root cause and determining our options for remediation.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Friday, September 26, 2025, at 10:30 AM UTC
Time:Thu Sep 25 20:41:02 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We're analyzing the latest collected telemetry data to gain further insight into the impacted request flow. In parallel, we're working to reproduce the issue within our internal testing environment to assist us in determining our next troubleshooting steps.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Friday, September 26, 2025, at 5:30 AM UTC
Time:Thu Sep 25 15:31:05 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We're continuing to collect additional service health telemetry to isolate the source of the failures to narrow down the root cause and determine the most effective remediation strategy.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Friday, September 26, 2025, at 1:00 AM UTC
Time:Thu Sep 25 14:06:37 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: Our service health monitors alerted us to failures occurring when admins attempt to download extended message traces. We're reviewing our service health telemetry to identify any patterns in the failures, so that we can determine the next steps to isolate the root cause.
Scope of impact: Your organization is affected by this event and some admins attempting to download on-demand or scheduled extended message traces from the Exchange Online admin center are intermittently impacted.
Next update by: Thursday, September 25, 2025, at 7:30 PM UTC
Time:Thu Sep 25 14:00:44 2025
Description:Title: Some admins are intermittently unable to download extended message traces from the Exchange Online admin center
User impact: Admins are intermittently unable to download extended message traces from the Exchange Online admin center.
More info: Impact occurs for both on-demand and scheduled extended message traces.
When affected admins attempt to download extended message traces, the download doesn't complete and they receive an error that states there is a network issue.
Current status: We're investigating a potential issue with the Exchange Online admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

PB1163355 - Some users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric

Status:serviceRestored
Start Time:Wed Oct 1 07:35:00 2025
End Time:Wed Oct 1 07:50:00 2025
Service:Power BI
Feature Group:PowerBI.com
Classification:advisory
Last Updated:Wed Oct 1 09:06:48 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Oct 1 08:49:25 2025
Description:Title: Some users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric
User impact: Users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric.
Final status: While we were in the process of analyzing service monitoring telemetry to isolate the root cause of impact and establish a fix, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Your organization was affected by this event, and some users located in East US attempting to utilize the Power BI and Microsoft Fabric services may have been impacted.
Start time: Wednesday, October 1, 2025, at 11:35 AM UTC
End time: Wednesday, October 1, 2025, at 11:50 AM UTC
This is the final update for the event.
Time:Wed Oct 1 08:33:28 2025
Description:Title: Some users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric
User impact: Users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric.
Current status: We've investigated a problem in which users may have experienced intermittent failures or delays in Power BI and Microsoft Fabric 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.

DZ1162930 - Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365

Status:serviceRestored
Start Time:Sun Sep 28 20:00:00 2025
End Time:Wed Oct 1 00:45:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Office 365
Classification:advisory
Last Updated:Wed Oct 1 01:15:58 2025
Root Cause:A recently-deployed service update contained a code issue resulting in impact.
Next Update:N/A

Details

Time:Wed Oct 1 01:15:58 2025
Description:Title: Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365
User impact: Users may have been unable to create new custom anti-spam policies in Microsoft Defender for Office 365.
More info: Affected users may have received an error that stated “An error occurred when creating the policy. Please review your settings and try again.”
Final status: We've completed the deployment of our fix and validated through service telemetry that the issue is resolved.
Scope of impact: Users attempting to create new custom anti-spam policies in Microsoft Defender for Office 365 may have been impacted.
Start time: Monday, September 29, 2025, at 12:00 AM UTC
End time: Wednesday, October 1, 2025, at 4:45 AM UTC
Root cause: A recently-deployed service update contained a code issue resulting in impact.
Next steps: - We're reviewing our update testing and validation methods to better identify code issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
Time:Tue Sep 30 22:07:23 2025
Description:Title: Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365
User impact: Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365.
More info: Affected users may receive an error that states “An error occurred when creating the policy. Please review your settings and try again.”
Current status: We've initiated the deployment of our fix and anticipate this may complete by our next scheduled update, at which point we'll monitor to confirm full remediation.
Scope of impact: Users attempting to create new custom anti-spam policies in Microsoft Defender for Office 365 may be impacted.
Root cause: A recently-deployed service update contained a code issue resulting in impact.
Next update by: Wednesday, October 1, 2025, at 6:00 AM UTC
Time:Tue Sep 30 20:25:38 2025
Description:Title: Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365
User impact: Users may be unable to create new custom anti-spam policies in Microsoft Defender for Office 365.
More info: Affected users may receive an error that states “An error occurred when creating the policy. Please review your settings and try again.”
Current status: We've identified that a recently-deployed service update contained a code issue resulting in impact. We're preparing a fix to resolve the issue and aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Users attempting to create new custom anti-spam policies in Microsoft Defender for Office 365 may be impacted.
Root cause: A recently-deployed service update contained a code issue resulting in impact.
Next update by: Wednesday, October 1, 2025, at 2:30 AM UTC
Time:Tue Sep 30 17:58:48 2025
Description:Title: Users can't create new custom anti-spam policies in Microsoft Defender for Office 365
User impact: Users can't create new custom anti-spam policies in Microsoft Defender for Office 365.
More info: Affected users receive an error that states “An error occurred when creating the policy. Please review your settings and try again.”
Current status: We're reviewing HTTP Archive format (HAR) logs captured from affected users' devices to identify and isolate any potential errors which may be contributing to impact for further investigation.
Scope of impact: Your organization is affected by this event, and all users receive an error that states “An error occurred when creating the policy. Please review your settings and try again.”
Next update by: Wednesday, October 1, 2025, at 12:30 AM UTC
Time:Tue Sep 30 17:33:06 2025
Description:Title: Users can't create new custom anti-spam policies in Microsoft Defender for Office 365
User impact: Users can't create new custom anti-spam policies in Microsoft Defender for Office 365.
More info: Affected users receive an error that states “An error occurred when creating the policy. Please review your settings and try again.”
Current status: We're investigating a potential issue with Microsoft Defender for Office and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1160098 - Users may have had missing device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal

Status:serviceRestored
Start Time:Wed Sep 3 01:09:00 2025
End Time:Sat Sep 27 09:00:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Tue Sep 30 08:32:50 2025
Root Cause:A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events was resulting in impact.
Next Update:N/A

Details

Time:Tue Sep 30 06:37:55 2025
Description:Title: Users may have had missing device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may have had missing device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacted some workstation endpoints and not servers.
Final status: We've confirmed after a period of monitoring that impact is no longer occurring.
Scope of impact: This issue may have impacted some users' workstation, and some device timeline and advanced hunting events may have been missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
End time: Saturday, September 27, 2025, at 1:00 PM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events was resulting in impact.
Next steps: - We're reviewing our recent change procedures to help prevent similar impact from happening again.
This is the final update for the event.
Time:Sat Sep 27 14:56:54 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: We’ve addressed the issue that was blocking system restarts and have completed the rollback. We’re monitoring through business hours to confirm that all events are processed as expected.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Tuesday, September 30, 2025, at 12:00 PM UTC
Time:Sat Sep 27 11:38:36 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: We're continuing our efforts to address the issue blocking the system restarts from completing. We'll aim to provide a timeline for the issue to be addressed and the rollback resumed by our next scheduled communications update.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Saturday, September 27, 2025, at 9:30 PM UTC
Time:Sat Sep 27 09:12:20 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: We've experienced an unexpected delay with the system restarts so the rollback changes are applied across the affected infrastructure to fully remediate impact, and estimate that this will complete by our next scheduled update.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Saturday, September 27, 2025, at 5:30 PM UTC
Time:Sat Sep 27 04:23:59 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: We're progressing with the system restarts so the rollback changes are applied across the affected infrastructure to fully remediate impact, and estimate that this will complete by our next scheduled update.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Estimated time to resolve: Saturday, September 27, 2025
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Saturday, September 27, 2025, at 2:30 PM UTC
Time:Fri Sep 26 18:00:16 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: The rollback process has completed, and we’re continuing to run system restarts so the rollback changes are applied across the affected infrastructure to fully remediate impact, and we’ll provide a resolution timeline once available.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Saturday, September 27, 2025, at 9:30 AM UTC
Time:Fri Sep 26 15:08:27 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: The process to rollback the offending change has completed, and we’ve triggered system restarts to ensure the rollback changes are picked up by the affected infrastructure to fully remediate impact.
Scope of impact: This issue may impact some users' workstation, and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection for timeline and advanced hunting events is resulting in impact.
Next update by: Friday, September 26, 2025, at 11:30 PM UTC
Time:Fri Sep 26 12:30:12 2025
Description:Title: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal
User impact: Users may be missing some device timeline and advanced hunting events in the Microsoft Defender for Endpoint portal.
More info: This issue only impacts some workstation endpoints and not servers.
Current status: We've identified that a recent change, intended to provide updates to the mechanism of data collection, introduced an issue that's resulting in impact. We're rolling back this change to remediate the issue for all users, which we expect will complete by our next scheduled communication update. While the rollback is ongoing, users can mitigate impact by restarting their machines.
Scope of impact: This issue may impact some users' workstation and some device timeline and advanced hunting events may be missing in the Microsoft Defender for Endpoint portal.
Start time: Wednesday, September 3, 2025, at 5:09 AM UTC
Root cause: A recent change to provide updates to the mechanism of data collection introduced an issue that's resulting in impact.
Next update by: Friday, September 26, 2025, at 9:00 PM UTC

DZ1153333 - Devices in the Microsoft Defender for Endpoint portal may have shown as misconfigured with the SENSE service not running

Status:serviceRestored
Start Time:Tue Jul 22 03:00:00 2025
End Time:Mon Sep 15 19:15:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Tue Sep 30 06:45:35 2025
Root Cause:A server-side validation issue occurring during the Windows update process was causing the Microsoft Defender for Endpoint SENSE service to not operate as expected, leading to impact.
Next Update:N/A

Details

Time:Tue Sep 16 04:59:08 2025
Description:Title: Devices in the Microsoft Defender for Endpoint portal may have shown as misconfigured with the SENSE service not running
User impact: Devices in the MDE portal may have shown as misconfigured with the SENSE service not running.
More info: Additionally, if Windows11InstallationAssistant.exe was used for OS upgrade to Win11, users may not have seen the SENSE service running and new events not shown in the portal. Some devices in rare scenarios, when using Windows Feature Update (FU) may also have been impacted and impact may have been avoided by running the following steps:
1. Re-onboarding the device to restore SENSE functionality. 2. Install OS updates on the machine to the latest version.
As a note: A duplicated device entry in the device inventory will appear in the portal for the affected machine due to the generation of a new device ID following the faulty upgrade process.
Also, to avoid impact for customers performing offline upgrades, or in cases where Dynamic Updates has been disabled, it is required to use Windows installation media that includes at least the September 2025 monthly security update or later. https://learn.microsoft.com/en-us/windows/deployment/update/media-dynamic-update
Devices may have been affected only if all of the following conditions were met:
- The device was running Windows 10 or Windows 11 and had either the July 2025 preview - update or the August 2025 security update installed. - The installation media used during the upgrade to Windows 11 version 24H2 didn't include the July 2025 security update (KB5062660) or any later cumulative updates. - Dynamic Update was disabled during the upgrade process.
Final status: We've deployed the aforementioned fix after conducting internal testing and validation, which will prevent any further devices to be impacted. However, users can remediate impact for already affected devices by following the steps provided in the more info section of this communication.
Scope of impact: Any user may have been affected and devices that used the Windows11InstallationAssistant.exe for OS upgrading to Windows 11 may have seen the SENSE service not running and the MDE portal may have shown devices as misconfigured, and they may have not seen new events.
Start time: Tuesday, July 22, 2025, at 7:00 AM UTC
End time: Monday, September 15, 2025, at 11:15 PM UTC
Root cause: A server-side validation issue occurring during the Windows update process was causing the Microsoft Defender for Endpoint SENSE service to not operate as expected, leading to impact.
Next steps: - We're reviewing our server-side validation procedures to help prevent this problem from happening again.
This is the final update for the event.
Time:Mon Sep 15 02:17:42 2025
Description:Title: Devices in the Microsoft Defender for Endpoint portal may show as misconfigured with the SENSE service not running
User impact: Devices in the MDE portal may show as misconfigured with the SENSE service not running.
More info: Additionally, if Windows11InstallationAssistant.exe was used for OS upgrade to WIn11, users may not see the SENSE service running and new events are not shown in the portal. Impact can be avoided by running the following steps:
1. Re-onboarding the device to restore SENSE functionality. 2. Install OS updates on the machine to the latest version.
As a note: A new Device ID will be created for those machines.
Current status: We were alerted by several customers of an issue where devices in the Microsoft Defender for Endpoint (MDE) portal may appear as misconfigured and new events for the devices in the portal may not show. We've identified a way for affected devices to avoid impact by following the steps provided. Our investigation has identified the cause of impact as a server side validation issue occurring during the Windows update process that causes the Microsoft Defender for Endpoint SENSE service to not operate as expected, leading to impact. We're now testing internally to develop and validate a fix to resolve impact.
Scope of impact: Any user may be affected and devices that used the Windows11InstallationAssistant.exe for OS upgrading to Windows 11 may see the SENSE service not running and the MDE portal may show devices as misconfigured, and they may not see new events.
Start time: Tuesday, July 22, 2025, at 7:00 AM UTC
Root cause: A server side validation issue occurring during the Windows update process is causing the Microsoft Defender for Endpoint SENSE service to not operate as expected, leading to impact.
Next update by: Tuesday, September 16, 2025, at 9:00 AM UTC

TM1162214 - Users of the free version of Microsoft Copilot may not see the app pinned in Microsoft Teams

Status:serviceRestored
Start Time:Mon Sep 29 08:55:00 2025
End Time:Mon Sep 29 14:45:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Sep 29 16:59:20 2025
Root Cause:A failure in retrieving admin policies caused web grounding to become disabled for all Copilot chat experiences, which resulted in impact.
Next Update:N/A

Details

Time:Mon Sep 29 16:59:20 2025
Description:Title: Users of the free version of Microsoft Copilot may not see the app pinned in Microsoft Teams
User impact: Users of the free version of Copilot may not have seen the app pinned in Teams, even if admins had pin setting enabled.
Final status: We've investigated a problem in which the Copilot app may not have been getting pinned in Microsoft Teams for users of the free version of Copilot, even if admins had the pin setting enabled in Microsoft 365 admin center. We determined this issue was due to a failure in retrieving admin policies, which resulted in web grounding becoming disabled for all Copilot chat experiences. We reduced specific component calls associated with this issue and monitored telemetry to confirm that service is now restored and impact is mitigated.
Scope of impact: Users in the western United States using the free version of Microsoft Copilot may have been affected by this issue.
Start time: Monday, September 29, 2025, at 12:55 PM UTC
End time: Monday, September 29, 2025, at 6:45 PM UTC
Root cause: A failure in retrieving admin policies caused web grounding to become disabled for all Copilot chat experiences, which resulted in impact.
Next steps: - We'll continue to monitor telemetry for the affected infrastructure to further analyze the failures in retrieving admin policies to prevent similar service impacts from occurring in the future.
This is the final update for the event.
Time:Mon Sep 29 16:11:58 2025
Description:Title: Users of the free version of Microsoft Copilot may not see the app pinned in Microsoft Teams
User impact: Users of the free version of Copilot may not have seen the app pinned in Teams, even if admins had pin setting enabled.
Current status: We've investigated a problem in which the Copilot app may not have been getting pinned in Microsoft Teams for users of the free version of Copilot, even if admins had pin setting enabled in Microsoft 365 admin center, and we 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.

CP1162087 - Users' Microsoft Copilot (Microsoft 365) web searches fail and generate an error or give inaccurate responses

Status:serviceRestored
Start Time:Mon Sep 29 09:00:00 2025
End Time:Mon Sep 29 14:30:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Mon Sep 29 15:45:45 2025
Root Cause:Higher than expected traffic in the portion of service infrastructure caused timeouts when requesting policies necessary to perform Copilot web searches, resulting in impact.
Next Update:N/A

Details

Time:Mon Sep 29 15:45:45 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) web searches fail and generate an error or give inaccurate responses
User impact: Users' Copilot web searches may have failed and generated an error or gave inaccurate responses.
Final status: We've identified that higher than expected traffic in the portion of service infrastructure caused timeouts when requesting policies necessary to perform Copilot web searches, resulting in impact. We've rebalanced service traffic to resolve this issue and confirmed with affected users that impact is remediated.
Scope of impact: Any user attempting to perform web searches in Copilot may have been impacted.
Start time: Monday, September 29, 2025, at 1:00 PM UTC
End time: Monday, September 29, 2025, at 6:30 PM UTC
Root cause: Higher than expected traffic in the portion of service infrastructure caused timeouts when requesting policies necessary to perform Copilot web searches, resulting in impact.
Next steps: - We're reviewing the affected portion of infrastructure to identify the cause of the unexpected traffic while improving our automated detection and prevention services to prevent similar traffic issues in the future.
This is the final update for the event.
Time:Mon Sep 29 14:01:29 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) web searches may fail and generate an error or give inaccurate responses
User impact: Users' Copilot web searches may fail and generate an error or give inaccurate responses.
Current status: We've identified that requests to fetch the web search policies are timing out. When the service can't access these policies, it disables web search by default, resulting in impact. We're continuing to investigate potential service changes that may be responsible for these policy request timeouts to determine the root cause and a strategy that remediates impact.
Scope of impact: Any user attempting to perform web searches in Copilot may be impacted.
Next update by: Monday, September 29, 2025, at 9:00 PM UTC
Time:Mon Sep 29 12:59:02 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) web searches may fail and generate an error or give inaccurate responses
User impact: Users' Copilot web searches may fail and generate an error or give inaccurate responses.
Current status: We're reviewing recent service changes that may be contributing to impact to identify why users' Copilot web searches fail and generate an error or give inaccurate responses.
Scope of impact: Any user attempting to perform web searches in Copilot may be impacted.
Next update by: Monday, September 29, 2025, at 6:00 PM UTC
Time:Mon Sep 29 12:31:36 2025
Description:Title: Users' Microsoft Copilot (Microsoft 365) web searches may fail and generate an error or give inaccurate responses
User impact: Users' Copilot web searches may fail and generate an error or give inaccurate responses.
Current status: We're investigating a potential issue with Copilot. We'll provide an update within 30 minutes.

OO1162158 - Some users in the Eastern United States may be intermittently unable to access Microsoft PowerPoint for the web

Status:serviceRestored
Start Time:Mon Sep 29 11:55:00 2025
End Time:Mon Sep 29 13:00:00 2025
Service:Microsoft 365 for the web
Feature Group:PowerPoint Online
Classification:advisory
Last Updated:Mon Sep 29 14:42:44 2025
Root Cause:A portion of PowerPoint for the web service infrastructure utilized to process access requests was operating in an unhealthy state, resulting in user requests failing to register and process in a timely manner.
Next Update:N/A

Details

Time:Mon Sep 29 14:32:24 2025
Description:Title: Some users in the Eastern United States may be intermittently unable to access Microsoft PowerPoint for the web
User impact: Users may have been intermittently unable to access Microsoft PowerPoint for the web.
Final status: We've moved affected user traffic to healthy portions of Microsoft PowerPoint for the web service infrastructure. After a period of monitoring service health telemetry, we've validated that users in the Eastern United States are able to access Microsoft PowerPoint for the web as intended.
Scope of impact: A subset of users in the Eastern United States may have been intermittently unable to access Microsoft PowerPoint for the web.
Start time: Monday, September 29, 2025, at 3:55 PM UTC
End time: Monday, September 29, 2025, at 5:00 PM UTC
Root cause: A portion of PowerPoint for the web service infrastructure utilized to process access requests was operating in an unhealthy state, resulting in user requests failing to register and process in a timely manner.
Next steps: - We're analyzing the affected portion of PowerPoint for the web service infrastructure to validate how it came to operate in an unhealthy state and what actions we can take to improve the resilience of our service and prevent similar impact from occurring in future.
This is the final update for the event.
Time:Mon Sep 29 13:15:44 2025
Description:Title: Some users in the Eastern United States may be intermittently unable to access Microsoft PowerPoint for the web
User impact: Users may be intermittently unable to access Microsoft PowerPoint for the web.
Current status: Our service monitoring telemetry has alerted us to an issue in which a subset of users in the Eastern United States may be intermittently unable to access Microsoft PowerPoint for the web. We've isolated that a portion of PowerPoint for the web service infrastructure utilized to process access requests is operating in an unhealthy state, resulting in user requests failing to be registered and processed in a timely manner. We're rerouting traffic to healthy infrastructure to alleviate impact while our investigation continues into the source of impact.
Scope of impact: A subset of users in the Eastern United States may be intermittently unable to access Microsoft PowerPoint for the web.
Start time: Monday, September 29, 2025, at 3:55 PM UTC
Root cause: A portion of PowerPoint for the web service infrastructure utilized to process access requests is operating in an unhealthy state, resulting in user requests failing to be registered and processed in a timely manner.
Next update by: Monday, September 29, 2025, at 6:30 PM UTC

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

Status:serviceRestored
Start Time:Fri Sep 26 21:03:00 2025
End Time:Sat Sep 27 07:05:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Sat Sep 27 09:23:22 2025
Root Cause:A section of infrastructure that supports connectivity for multiple Microsoft 365 services was performing below the expected service threshold.
Next Update:N/A

Details

Time:Sat Sep 27 09:06:40 2025
Description:Title: Users may have experienced issues with multiple Microsoft 365 services
User impact: Users may have experienced issues with multiple Microsoft 365 services.
More info: The impact to services and functionality included, but may not have been limited to:
Microsoft Power BI and Microsoft Fabric - Degraded performance and service unavailability
Windows 365 - Some users may have been unable to connect to their Windows 365 Cloud PCs
Microsoft Teams - Notifications pertaining to existing change notification subscriptions, specifically for new messages, message updates and changes in membership, weren't delivering as expected.
Microsoft Defender for Identity - Users may have seen their update data take time to process, which could have resulted in incomplete information appearing on the identity inventory page.
Final status: We've completed our period of monitoring service health and can confirm that the issue is resolved.
Scope of impact: This issue may have impacted any user in the Switzerland region attempting to utilize the impacted services and functionality in the More Info section of this communication.
Start time: Saturday, September 27, 2025, at 1:03 AM UTC
End time: Saturday, September 27, 2025, at 11:05 AM UTC
Root cause: A section of infrastructure that supports connectivity for multiple Microsoft 365 services was performing below the expected service threshold.
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:Sat Sep 27 05:21:57 2025
Description:Title: Users may be experiencing issues with multiple Microsoft 365 services
User impact: Users may experience issues with multiple Microsoft 365 services.
More info: The impact to services and functionality includes, but may not be limited to: Microsoft Power BI and Microsoft Fabric - Degraded performance and service unavailability Windows 365 - Some users are unable to connect to their Windows 365 Cloud PCs
Additionally, the following impact scenarios have been resolved:
Microsoft Teams - Notifications pertaining to existing change notification subscriptions, specifically for new messages, message updates and changes in membership, weren't delivering as expected. Microsoft Defender for Identity - Users may have seen their update data take time to process, which could have resulted in incomplete information appearing on the identity inventory page.
Current status: We're monitoring the progress of services continuing to recover since our repair of the connectivity for the affected section of infrastructure.
Scope of impact: This issue may impact any user in the Switzerland region attempting to utilize the impacted services and functionality in the More Info section of this communication.
Start time: Saturday, September 27, 2025, at 1:03 AM UTC
Root cause: A section of infrastructure that supports connectivity for multiple Microsoft 365 services is performing below the expected service threshold.
Next update by: Saturday, September 27, 2025, at 3:00 PM UTC
Time:Sat Sep 27 02:30:38 2025
Description:Title: Users may be experiencing issues with multiple Microsoft 365 services
User impact: Users may experience issues with multiple Microsoft 365 services.
More info: The impact to services and functionality includes, but may not be limited to: Microsoft Power BI and Microsoft Fabric - Degraded performance and service unavailability Windows 365 - Some users are unable to connect to their Windows 365 Cloud PCs
Additionally, the following impact scenarios have been resolved:
Microsoft Teams - Notifications pertaining to existing change notification subscriptions, specifically for new messages, message updates and changes in membership, weren't delivering as expected. Microsoft Defender for Identity - Users may have seen their update data take time to process, which could have resulted in incomplete information appearing on the identity inventory page.
Current status: We were able to repair the connectivity for the affected portion of infrastructure and are seeing that the majority of services have recovered. We're reviewing the remaining impacted services to identify whether any additional mitigation actions are necessary. We'll provide an update on the recovery status by our next scheduled update time.
Scope of impact: This issue may impact any user in the Switzerland region attempting to utilize the impacted services and functionality in the More Info section.
Start time: Saturday, September 27, 2025, at 1:03 AM UTC
Root cause: A portion of infrastructure that supports connectivity for multiple Microsoft 365 services is performing below the expected service threshold.
Next update by: Saturday, September 27, 2025, at 9:30 AM UTC
Time:Fri Sep 26 23:43:03 2025
Description:Title: Users may be experiencing issues with multiple Microsoft 365 services
User impact: Users may experience issues with multiple Microsoft 365 services.
More info: The impact to services and functionality includes, but may not be limited to:
Microsoft Power BI and Microsoft Fabric - Degraded performance and service unavailability Windows 365 - Some users are unable to connect to their Windows 365 Cloud PCs Microsoft Teams - Notifications pertaining to existing change notification subscriptions, specifically for new messages, message updates and changes in membership, aren't delivering as expected Microsoft Defender for Identity - users may see their update data take time to process, which could result in incomplete information appearing on the identity inventory page.
Current status: A portion of infrastructure that supports connectivity for multiple Microsoft 365 services is performing below the expected service threshold. We're attempting to reroute connections to alternate infrastructure to remediate the impact. We anticipate having an update on our mitigation efforts by the next scheduled update time.
Scope of impact: This issue may impact any user in the Switzerland region attempting to utilize the impacted services and functionality in the More Info section.
Start time: Saturday, September 27, 2025, at 1:03 AM UTC
Root cause: A portion of infrastructure that supports connectivity for multiple Microsoft 365 services is performing below the expected service threshold.
Next update by: Saturday, September 27, 2025, at 7:00 AM UTC

IT1158880 - Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies

Status:serviceRestored
Start Time:Wed Sep 17 14:23:00 2025
End Time:Fri Sep 26 22:30:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Fri Sep 26 23:28:40 2025
Root Cause:A specific section of code in a general service update intended to improve service performance wasn't updating scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next Update:N/A

Details

Time:Fri Sep 26 23:28:40 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may have been unable to edit or view some Endpoint Security policies.
More info: Impact was to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, impact was isolated to non-global admins and policies that were previously edited.
Final status: We've completed the deployment of our fix to restore the impacted flow and determined the issue is remediated.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may have been impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
End time: Saturday, September 27, 2025, at 2:30 AM UTC
Root cause: A specific section of code in a general service update intended to improve service performance wasn't updating scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next steps: - We're reviewing our update testing and validation methods to better identify code issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
Time:Fri Sep 26 21:55:45 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: We've successfully deployed our fix to the bulk of the impacted environment and are monitoring the final stages of our remediation effort, which we anticipate should complete by our next scheduled communications update.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Saturday, September 27, 2025, at 4:00 AM UTC
Time:Fri Sep 26 18:45:23 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: Our deployment of our fix to restore the previous policy updates and to ensure the underlying issue is fully resolved continues to progress, and the estimated timeline of Saturday, September 27, 2025, at 1:00 AM UTC remains accurate.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Saturday, September 27, 2025, at 2:00 AM UTC
Time:Fri Sep 26 14:37:01 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: Validation of the secondary fix is progressing as expected and we continue to anticipate the deployment to reach all affected users to resolve this issue by Saturday, September 27, 2025, at 1:00 AM UTC.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Saturday, September 27, 2025, at 12:00 AM UTC
Time:Thu Sep 25 22:10:35 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: We’ve completed the aforementioned validation and testing for our secondary fix. While we’re seeing positive effects from this fix, we’ve identified additional testing and validations are necessary to understand how our fix could potentially affect policies. We’re estimating this process will have completed by our next scheduled communications update, at which time we will begin deploying our fix. We anticipate deployment will complete and fully resolve the issue by Saturday, September 27, 2025, at 1:00 AM UTC.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Friday, September 26, 2025, at 7:00 PM UTC
Time:Thu Sep 25 13:53:05 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: The validation and testing for our secondary fix continue to progress and is requiring more time than originally expected. Our updated timeline estimates that our validations will have completed by our next communication update, when we're expecting a timeline for our deployment and the remediation of impact to be available.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Friday, September 26, 2025, at 3:00 AM UTC
Time:Thu Sep 25 10:26:49 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current status: Our process of validation and testing of the aforementioned secondary fix is ongoing and we expect to provide deployment timeline by our next scheduled update.
Scope of impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root cause: A specific section of code in the general service update intended to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next update by: Thursday, September 25, 2025, at 6:00 PM UTC
Time:Thu Sep 25 01:18:35 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More Info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current Status: We've completed deploying the code fix and validated that admins managed by scope tags can now successfully edit and view new Endpoint Security policy changes as expected. Additionally, impact is now isolated to previous edits that were made to Endpoint Security policies within the duration of this event. We're actively developing a secondary fix to restore the previous policy updates and to ensure the underlying issue is fully resolved. Once we complete the validation and testing of the secondary fix, we'll aim to provide a resolution timeline.
Scope of Impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root Cause: A specific portion of code in the general service update meant to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next Update Time: Thursday, September 25, 2025, at 4:00 PM UTC
Time:Wed Sep 24 21:39:34 2025
Description:Title: Some admins managed by scope tags may be unable to edit or view some Endpoint Security policies
User impact: Admins managed by scope tags may be unable to edit or view some Endpoint Security policies.
More Info: Impact is to some Endpoint Security policies in the Microsoft Intune admin center. Additionally, this only impacts non-global admins and policies that were previously edited.
Current Status: We've completed validating the code fix and confirmed that it resolves the underlying issue and allows for admins to view or edit newly created Endpoint Security policies as expected. We anticipate the deployment of this fix will complete by our next scheduled update. Additionally, while we're monitoring the progression of the code fix, we're developing a secondary fix that's intended to restore all previous edits made to Endpoint Security policies that have been impacted by this event.
Scope of Impact: Some non-global admins managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center may be impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root Cause: A specific portion of code in the general service update meant to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next Update Time: Thursday, September 25, 2025, at 6:30 AM UTC
Time:Wed Sep 24 19:31:24 2025
Description:Title: Admins managed by scope tags can’t edit some Endpoint Security policies in the Microsoft Intune admin center
User impact: Admins managed by scope tags can’t edit some Endpoint Security policies in the Microsoft Intune admin center.
More Info: This only impacts non-global admins and policies that were previously edited.
Current Status: We've identified a specific portion of code in the general service update meant to improve service performance that isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center. We've created and are validating a code fix in our internal environment that we expect will remediate impact. Once validated, we'll provide a timeline for its deployment, as one becomes available
Scope of Impact: Your organization is affected by this event, and any non-global admin managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center are impacted.
Start time: Wednesday, September 17, 2025, at 6:23 PM UTC
Root Cause: A specific portion of code in the general service update meant to improve service performance isn't updating the scope tags as expected, preventing non-global admins from editing some Endpoint Security policies in the Microsoft Intune admin center.
Next Update Time: Thursday, September 25, 2025, at 2:30 AM UTC
Time:Wed Sep 24 17:42:33 2025
Description:Title: Admins managed by scope tags are unable to edit some Endpoint Security policies in the Microsoft Intune admin center
User Impact: Admins managed by scope tags are unable to edit some Endpoint Security policies in the Microsoft Intune admin center.
More Info: This only impacts non-global admins and policies that were previously edited
Current Status: We've identified that a recent general service update contained a code regression that prevents non-global admins from editing the affected policies if they have been edited previously. We're considering our options to correct this regression and remediate impact.
Scope of Impact: Your organization is affected by this event, and any non-global admin managed by scope tags attempting to edit Endpoint Security policies that were previously edited in the Microsoft Intune admin center are impacted.
Root Cause: A recent general service update contained a code regression that prevents non-global admins from editing the affected policies if they have been edited previously.
Next Update Time: Wednesday, September 24, 2025, at 11:30 PM UTC

MO1154713 - Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar

Status:serviceRestored
Start Time:Thu Aug 28 01:41:00 2025
End Time:Fri Sep 26 12:36:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Fri Sep 26 12:45:52 2025
Root Cause:A fix deployed for an alternate issue introduced a code error that caused meetings to duplicate.
Next Update:N/A

Details

Time:Fri Sep 26 12:45:52 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users saw duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users could remove and re-add the offending calendar to remove duplicate items while we worked to resolve this issue.
Final status: We've confirmed the deployment of the change has completed and we've verified with a subset of affected users that the issue is resolved.
Scope of impact: Your organization was affected by this event, and users saw duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
End time: Friday, September 26, 2025, at 4:36 PM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that caused meetings to duplicate.
Next steps: - We're reviewing our protocols surrounding fix development and deployment to ensure similar issues are identified and corrected during testing so this doesn't happen again.
This is the final update for the event.
Time:Thu Sep 25 14:34:05 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We're continuing to closely monitor the deployment of the change to enable the cleanup process as it nears completion, and we now anticipate the change will be fully enabled for all affected users by the time of our next update.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Friday, September 26, 2025, at 6:30 PM UTC
Time:Wed Sep 24 14:42:05 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We expect that the change may take until Thursday, September 25, 2025, at 8:00 PM UTC to be fully enabled for all of your users. While this process completes, your users will gradually see remediation.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Thursday, September 25, 2025, at 8:00 PM UTC
Time:Wed Sep 24 00:35:05 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: Deployment of the change to enable the cleanup process has completed. While we anticipate that users are experiencing mitigation, we’re monitoring the cleanup process for an extended period to ensure that the impact is fully remediated. We'll provide an update on the mitigation status for affected users at the next scheduled update time.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Thursday, September 25, 2025, at 6:00 AM UTC
Time:Mon Sep 22 13:20:11 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: Deployment of the changes necessary to enable the cleanup process to remediate the impact is nearing completion. Once the deployment is complete, we expect it’ll take about 24 hours for the cleanup process to take effect to resolve this issue. Additionally, we’re reviewing options to expedite this process for some heavily impacted users. We expect that this issue should be fully resolve for all affected users by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Wednesday, September 24, 2025, at 6:00 AM UTC
Time:Fri Sep 19 00:02:16 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We've completed our internal validations, and the subsequent deployment process has saturated throughout 33 percent of the affected environment. We anticipate that this process will be completed by the time of our next scheduled update.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Monday, September 22, 2025, at 5:30 PM UTC
Time:Thu Sep 18 12:20:09 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We’re deploying the fix to our internal testing environments for additional validation to confirm it fully resolves the impact. Once validation is complete, we’ll share a timeline for deployment.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Friday, September 19, 2025, at 5:30 AM UTC
Time:Wed Sep 17 21:00:16 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We're preparing to deploy the fix to our internal testing environment for additional validations to ensure it remediates impact as expected. Once the validations are complete, we'll aim to provide a deployment timeline.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Thursday, September 18, 2025, at 5:30 PM UTC
Time:Wed Sep 17 12:40:05 2025
Description:Title: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar
User impact: Users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar.
More info: Affected users can also remove and re-add the offending calendar to remove duplicate items while we work to resolve this issue.
Current status: We’ve investigated an issue in which users see duplicate meetings on their shared Exchange Online or Microsoft Teams calendar and determined that a fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate. We've created a fix to resolve the code error and remove the duplicate items that we're currently testing in our internal testing environment. Once we've validated the effectiveness of our fix, we'll deploy the solution and aim to provide a timeline to impact remediation.
Scope of impact: Your organization is affected by this event, and users see duplicate meetings on their shared Exchange Online and Microsoft Teams calendar.
Start time: Thursday, August 28, 2025, at 5:41 AM UTC
Root cause: A fix deployed for an alternate issue introduced a code error that’s causing meetings to duplicate.
Next update by: Thursday, September 18, 2025, at 2:00 AM UTC