EBMUDM365 Status

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures.

We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 5:00 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.

We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 4:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 3:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 3:00 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 2:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.

The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 2:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

-Microsoft 365 Apps Admin Center: Multiple services including Cloud Update, Cloud Policy, and Inventory are affected.

Current status: We've reviewed known impact scenarios and have revised the list of impact services and features, which can be viewed in the "more info" section of this communication.

We're continuing our work to isolate the issue affecting server availability, as well as other workstreams.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 1:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.

Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 1:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 12:30 AM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 11:30 PM UTC

We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.

Next update by: Thursday, November 12, 2026, at 10:30 PM UTC

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: More info: Potentially impacted services include:

Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 10:30 PM UTC

While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

Next update by: Thursday, November 12, 2026, at 9:30 PM UTC

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 9:30 PM UTC

We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.

This quick update is designed to give the latest information on this issue.

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 9:00 PM UTC

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Thursday, November 12, 2026, at 8:30 PM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures.

We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 5:30 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.

We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 4:30 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 4:00 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 3:30 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 3:00 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.

The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 2:00 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.

Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 1:00 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Friday, November 13, 2026, at 12:00 AM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 11:00 PM UTC

We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC

While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

Next update by: Thursday, November 12, 2026, at 9:00 PM UTC

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Impact to additional Microsoft 365 services is described under MO1550821 in the Service Health Dashboard.

Current status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 9:00 PM UTC

We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.

This quick update is designed to give the latest information on this issue.

Next update by: Thursday, November 12, 2026, at 8:00 PM UTC

We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

This quick update is designed to give the latest information on this issue.

We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Current status: We've completed redistributing Outlook connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 8:00 PM UTC

We've identified a pattern in which affected servers are becoming intermittently unavailable, which places additional strain on the remaining infrastructure and contributes to the connectivity issues users are experiencing. We've begun redistributing Outlook connection traffic across our broader worldwide infrastructure to help balance the load, which may result in some latency while this change is in effect, and we're reviewing recent changes to identify the source of the increased traffic.

This quick update is designed to give the latest information on this issue.

We've redirected a portion of traffic away from the affected infrastructure in the US to reduce load, and we're evaluating doing the same in other regions. While Exchange is the primarily impacted service, we've identified additional Microsoft 365 services that are also experiencing connectivity issues, and we're communicating those issues under MO1550821 on the Service Health Dashboard.

This quick update is designed to give the latest information on this issue.

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Current status: Our investigation indicates that the affected infrastructure is experiencing elevated load across multiple regions, which is contributing to the connectivity errors users are receiving. We're restarting and repairing impacted portions of this infrastructure to mitigate impact and are evaluating options to redirect traffic to alternate infrastructure to expedite relief.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 7:30 PM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Current status: We’ve identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 8:00 PM UTC

Title: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

Current status: We’re reviewing service health telemetry information to identify and isolate any errors contributing to impact for further investigation.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 6:00 PM UTC

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.

Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online

User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.

More info: To remediate impact while our investigation is ongoing, admins can configure free/busy sharing between impacted organizations using Organization Relationship. The Organization Relationship will take precedence over the cross-tenant access policy and sharing will begin working again after caches clear, usually within 2 hours. If EWS has been disabled in your tenant, it will need to be re-enabled to support Organization Relationship. The Organization Relationship should be removed when this incident is resolved.

Current status: We're monitoring the deployment of our fix which has reached 62 percent saturation to the affected environment. We anticipate the fix will complete deployment by Saturday, November 14, 2026.

Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.

Estimated time to resolve: We anticipate that the fix will complete deployment and remediate the impact by Friday, November 14, 2026.

Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.

Next update by: Friday, November 13, 2026, at 11:00 PM UTC

Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online

User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.

More info: To remediate impact while our investigation is ongoing, admins can configure free/busy sharing between impacted organizations using Organization Relationship. The Organization Relationship will take precedence over the cross-tenant access policy and sharing will begin working again after caches clear, usually within 2 hours. If EWS has been disabled in your tenant, it will need to be re-enabled to support Organization Relationship. The Organization Relationship should be removed when this incident is resolved.

More information on this process can be viewed here: https://learn.microsoft.com/en-us/exchange/sharing/organization-relationships/create-an-organization-relationship

Current status: After further analysis, we've isolated that additional organizations utilizing cross-tenant access policies are affected by this free/busy issue, and we've expanded communications to all potentially affected users. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this. We've initiated deployment of a fix to address a regression introduced by a recent service change that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address. We're evaluating ways to expedite our deployment and we aim to provide a timeline to remediation as soon as possible

Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.

Start time: Wednesday, November 4, 2026, at 4:00 PM UTC

Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.

Next update by: Friday, November 13, 2026, at 12:00 AM UTC

Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online

User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.

Current status: We've completed validation of our code fix to revert the service change responsible for this issue and have initiated deployment to the affected environment. As deployment progresses, some users may begin experiencing impact alleviation. We'll provide an estimated resolution timeline once available.

Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.

Next update by: Friday, November 13, 2026, at 8:30 PM UTC

Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online

User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.

Current status: We're validating our code fix that'll revert the offending service change, address the offending regression, and remediate the impact. We'll provide an updated timeline for the deployment of our code fix after our internal validations have verified that its deployment won't produce any unexpected problems for the service.

Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.

Next update by: Wednesday, November 11, 2026, at 8:30 PM UTC

Title: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web

User impact: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web.

Current status: We've identified that a recent change introduced a regression that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address, resulting in impact. We're reverting the change to restore the correct configuration and expect to confirm the deployment timeline by our next scheduled update.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.

Root cause: A recent change introduced a regression that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.

Next update by: Tuesday, November 10, 2026, at 8:30 PM UTC

Title: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web

User impact: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web.

Current status: After further investigation, it was determined that additional information from affected systems and users regarding recent mailbox migrations would be required to facilitate remediation efforts. We're reaching out to your representatives to gather additional diagnostic logs to help with understanding the underlying root cause.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.

Next update by: Tuesday, November 10, 2026, at 9:30 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: Our investigation into data migration configurations is progressing, however due to the complexity of the issue this is taking longer than initially anticipated. We're reviewing telemetry relevant to affected systems and will provide an updated timeline on remediation as one becomes available.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.

Next update by: Tuesday, November 10, 2026, at 5:30 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: Our review of the database mismatch mentioned in previous communications is ongoing. In parallel, we've expanded the investigation and are examining configuration settings and system telemetry to identify and isolate potential errors which may have occurred during recent data migrations to determine whether these could be contributing to impact.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.

Next update by: Tuesday, November 10, 2026, at 3:30 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: We're analyzing a database mismatch from free/busy information requests shared by your representatives to isolate if this is the underlying source of impact and to evaluate our next steps towards remediation.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.

Next update by: Tuesday, November 10, 2026, at 1:30 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: Our review of the recently provided data from your organization has been inconclusive. Subsequently, we’ve begun to reach out to your representatives to gather several reproductions of impact as we anticipate that these items will expedite our investigative efforts and help determine our next troubleshooting actions.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.

Next update by: Monday, November 9, 2026, at 11:30 PM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: We’ve collected the read-only outputs containing information about your organization's relationship and connector settings and are working on correlating its GetSchedule requests to the failures observed in the HAR so that we can identify the underlying root cause and develop a remediation plan.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.

Next update by: Sunday, November 8, 2026, at 3:00 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: We're continuing our investigation of HAR logs and have determined that additional information about your organization's relationship and connector settings is needed to better understand the issue and identify remediation steps. We're coordinating with your representatives to collect these details.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.

Next update by: Saturday, November 7, 2026, at 6:00 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: We’ve received the requested fresh HAR logs and are analyzing them to identify and isolate any errors potentially contributing to impact for further investigation.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.

Next update by: Saturday, November 7, 2026, at 1:00 AM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

Current status: We’re reaching out to your representatives to request fresh HTTP Archive format (HAR) logs to assist our investigation into the source of the issue.

Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.

Next update by: Friday, November 6, 2026, at 11:00 PM UTC

Title: Users can’t see free/busy information in cross-tenant calendar

User impact: Users can’t see free/busy information in cross-tenant calendar.

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.

Title: Users may experience delays installing Volume Purchase Program (VPP) apps in Microsoft Intune for iOS and Mac

User impact: Users may have experienced delays installing VPP apps in Microsoft Intune for iOS and Mac.

More info: Users may have seen delays in installing VPP apps of up to eight hours.

Final status: The third-party provided have deployed their fix, and we've confirmed through monitoring service health telemetry that the impact has been remediated.

Scope of impact: This event may have impacted any user installing VPP apps in Microsoft Intune for iOS and Mac.

Start time: Wednesday, November 11, 2026, at 8:00 AM UTC

End time: Wednesday, November 11, 2026, at 7:30 PM UTC

Root cause: A recent third-party change was resulting in this impact.

Next steps:

This is the final update for the event.

Title: Users may experience delays installing Volume Purchase Program (VPP) apps in Microsoft Intune for iOS and Mac

User impact: Users may experience delays installing VPP apps in Microsoft Intune for iOS and Mac.

More info: Users may see delays in installing VPP apps of up to eight hours.

Current status: We've isolated a recent third-party change, which is resulting in this impact. We're working closely with the third-party to expedite a resolution and will provide an updated remediation timeline as soon as one becomes available.

Scope of impact: This event may impact ay user installing VPP apps in Microsoft Intune for iOS and Mac. This information may be updated as our investigation continues.

Start time: Wednesday, November 11, 2026, at 8:00 AM UTC

Root cause: A recent third-party change is resulting in this impact.

Next update by: Thursday, November 12, 2026, at 8:30 PM UTC

Title: Users may experience delays installing Volume Purchase Program (VPP) apps in Microsoft Intune for iOS and Mac

User impact: Users may experience delays installing VPP apps in Microsoft Intune for iOS and Mac.

Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may be unable to install third-party apps from the organization store in Microsoft Teams

User impact: Users may have been unable to install third-party apps from the organization store in Microsoft Teams.

Final status: We've disabled the offending configuration change affecting how app installations are processed. After monitoring the service and verifying with affected users, we've confirmed that this action successfully resolved the issue.

Scope of impact: Impact may have occurred for users attempting to install third-party apps from the organization store in Microsoft Teams.

Start time: Wednesday, September 23, 2026, at 5:20 PM UTC

End time: Wednesday, November 11, 2026, at 4:41 PM UTC

Root cause: A recent configuration change intended to update how app installations are processed introduced a blocking dependency on the Microsoft Store catalog service, resulting in third-party app installation failures in Microsoft Teams.

Next steps: We're investigating why the configuration change resulted in app installation failures to implement measures for preventing this problem from happening again in the future.

This is the final update for the event.

Title: Users may be unable to install third-party apps from the organization store in Microsoft Teams

User impact: Users may be unable to install third-party apps from the organization store in Microsoft Teams.

Current status: We're continuing to validate whether disabling the suspected configuration change will restore functionality and help us confirm the underlying cause. We'll provide a resolution timeline once available.

Scope of impact: Impact may occur for all users attempting to install third-party apps from the organization store in Microsoft Teams.

Next update by: Thursday, November 12, 2026, at 7:00 PM UTC

Title: Users may be unable to install third-party apps from the organization store in Microsoft Teams

User impact: Users may be unable to install third-party apps from the organization store in Microsoft Teams.

Current status: We've received reports that users are unable to install third-party apps from the organization store in Microsoft Teams. We've identified a potential recent configuration change that may be affecting how app installation requests are processed. We're investigating whether disabling this change will restore functionality and help us validate the underlying cause. We'll provide a resolution timeline once available.

Scope of impact: Impact may occur for all users attempting to install third-party apps from the organization store in Microsoft Teams.

Next update by: Wednesday, November 11, 2026, at 6:30 PM UTC

A post-incident report has been published.

A post-incident report has been published.

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may have been unable to load chat history or previously pinned chats, and couldn't pin chats in Copilot.

More info: Previously pinned chats didn't show up for users to select, and chat histories weren't showing up as expected.

Final status: The fix is fully deployed across all affected environments and we've confirmed with affected users that impact is remediated.

Scope of impact: Some users may have been unable to load chat history, previously pinned chats, and couldn't pin chats in Copilot.

Start time: Tuesday, September 1, 2026, at 3:38 AM UTC

End time: Wednesday, November 4, 2026, at 12:30 PM UTC

Root cause: The pinned chats feature in Microsoft 365 Copilot and Copilot Chat contained a code defect that had been present since the feature was first released. This defect wasn’t caught during testing due to its difficulty to reproduce locally. A recent migration exposed this defect, which, under certain conditions, prevented pinned chats from loading and prevented users from pinning new chats.

Next steps:

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: We're monitoring the rollout of the fix deployment intended to remediate impact, and the current timeline estimates it will be completed by our next scheduled communication update.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot. This information may be updated as our investigation continues.

Start time: Tuesday, September 1, 2026, at 3:38 AM UTC

Root cause: A recent feature update revealed an error resulting in this impacting event.

Next update by: Wednesday, November 4, 2026, at 4:30 PM UTC

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: Our fix deployment is ongoing, and we anticipate some users to start seeing remediation at this time. We aim to provide a finalized timeline to remediation as soon as possible.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot. This information may be updated as our investigation continues.

Root cause: A recent feature update revealed an error resulting in this impacting event.

Next update by: Thursday, October 29, 2026, at 7:30 PM UTC

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: We've identified that a recent feature update revealed the error that is causing this impact. As previously communicated, there is a fix already being deployed. We're working to deploy this at a more expediated pace to remediate impact. We anticipate having a better deployment schedule at our next communication time.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot. This information may be updated as our investigation continues.

Root cause: We've identified that a recent feature update revealed an error resulting in this impacting event.

Next update by: Wednesday, October 28, 2026, at 7:30 PM UTC

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: We've identified that this is a potentially known issue and that there is already a fix in progress. We're reviewing ways to expediate this fix to help remediate as quickly as possible.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot. This information may be updated as our investigation continues.

Next update by: Tuesday, October 27, 2026, at 7:30 PM UTC

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: We're reviewing the information provided in specific support cases to better understand the issue and determine our next steps for troubleshooting.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot. This information may be updated as our investigation continues.

Next update by: Tuesday, October 27, 2026, at 5:30 PM UTC

Title: We're looking into a potential problem impacting Microsoft 365 Copilot

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

A post-incident report has been published.

A post-incident report has been published.

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may have been unable to load chat history or previously pinned chats, and couldn't pin chats in Copilot Chat.

More info: Previously pinned chats didn't show up for users to select, and chat histories weren't showing up as expected.

Final status: The fix is fully deployed across all affected environments and we've confirmed with affected users that impact is remediated.

Scope of impact: Some users may have been unable to load chat history, previously pinned chats, and couldn't pin chats in Copilot Chat.

Start time: Tuesday, September 1, 2026, at 3:38 AM UTC

End time: Wednesday, November 4, 2026, at 12:30 PM UTC

Root cause: The pinned chats feature in Microsoft 365 Copilot and Copilot Chat contained a code defect that had been present since the feature was first released. This defect wasn’t caught during testing due to its difficulty to reproduce locally. A recent migration exposed this defect, which, under certain conditions, prevented pinned chats from loading and prevented users from pinning new chats.

Next steps:

Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot

User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot Chat.

More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected.

Current status: We've identified a recent feature update that introduced an error which is resulting in impact. We've deployed a code fix to address the error and remediate the impact. We're monitoring the rollout of the fix deployment, and the current timeline estimates it will be completed by our next scheduled communication update.

Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot Chat. This information may be updated as our investigation continues.

Start time: Tuesday, September 1, 2026, at 3:38 AM UTC

Root cause: A recent feature update revealed an error resulting in this impacting event.

Next update by: Wednesday, November 4, 2026, at 4:30 PM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit.

More info: Affected admins may encounter delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Specifically, admins may experience various latency ranges before all of the Audit log data is available for search in the Purview portal.

Current status: The processing of the aforementioned backlog is steadily progressing and users should see relief as it continues to progress. We'll continue to monitor it to ensure it successfully completes and issue is resolved.

Scope of impact: Any admin attempting to access audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues.

Next update by: Thursday, November 12, 2026, at 6:30 AM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit.

More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell.

Current status: The processing of the backlog of affected events is progressing as expected and we'll continue to monitor it along with relevant telemetry to ensure the service is recovering.

Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues.

Next update by: Thursday, November 12, 2026, at 6:30 AM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit.

More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell.

Current status: Our efforts to process the backlog of affected events are ongoing. In parallel, we're monitoring relevant telemetry to verify improvement in system health. However, due to the complexity of this issue, more time will be required to confirm a timeline for remediation.

Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues.

Next update by: Thursday, November 5, 2026, at 7:30 AM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit.

More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell.

Current status: We're continuing to monitor the backlog of affected events as they're processed. Due to the complexity of the issue, we're anticipating it may take some additional time before we're able to confirm a timeline for full remediation.

Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues.

Next update by: Thursday, October 29, 2026, at 6:30 AM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview.

More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview portal, Microsoft Graph API, or PowerShell.

Current status: Our monitoring of the queued backlog continues to report reduced delays when accessing audit log data results in Microsoft Purview. We're continuing to monitor the events that require processing and expect clarity into the timeline for it completing by our next scheduled communication update.

Scope of impact: Any admin accessing audit log data from Microsoft Purview may be affected. This information may be updated as our investigation continues.

Next update by: Thursday, October 22, 2026, at 6:30 AM UTC

Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview

User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview.

More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview portal, Microsoft Graph API, or PowerShell.

Current status: Our monitoring identified an increase in processing latency with Microsoft Purview audit log data. We've analyzed service telemetry and determined that a dependent service isn't processing requests as efficiently as expected, resulting in impact. We've taken action to rebalance load and improve throughput. While most users should see relief, we're continuing to monitor as the remaining backlog of events are processed, and we'll provide a complete remediation timeline once available.

Scope of impact: Any admin accessing audit log data from Microsoft Purview may be affected.

Next update by: Wednesday, October 21, 2026, at 6:00 PM UTC

Title: Users may be unable to install applications on Windows devices through Microsoft Intune

User impact: Users may have been unable to install applications on Windows devices through Microsoft Intune.

Final status: We've been alerted by our automated monitoring system to an issue in which users in Central US may have been unable to install applications on Windows devices through Microsoft Intune. We've identified that a gateway configuration change caused this impact. We've reverted this configuration change to remediate impact and confirmed with our service health telemetry that this issue has been resolved.

Scope of impact: Users in Central US who attempted to install applications on Windows devices through Microsoft Intune may have been impacted by this event.

Start time: Wednesday, November 11, 2026, at 8:12 PM UTC

End time: Wednesday, November 11, 2026, at 8:57 PM UTC

Root cause: A gateway configuration change caused this impact.

Next steps:

This is the final update for the event.

Title: Some users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune

User impact: Users may see delays receiving policies, apps, and other changes on Windows devices enrolled in Microsoft Intune.

More info: A recent Windows security update, MSRC144654, can cause a single device check in to fail during installation. Affected devices receive pending changes at their next successful check in. Users can check in manually after the update finishes instead of waiting for the next scheduled check in.

Current status: We’ve confirmed that a recent Windows security update, MSRC144654, can cause a single check in to fail during installation. We’re developing a fix to address this issue and anticipate its release for early December 2026. We’ll provide a better estimate for the delivery of our fix when available.

Scope of impact: Some users with Windows devices enrolled in Microsoft Intune may experience delays receiving policies, apps, and other changes while their devices install Windows security update MSRC144654. This information may be updated as our investigation continues.

Root cause: A recent Windows security update, MSRC144654, can cause a single check in to fail during installation.

Next update by: Wednesday, November 25, 2026, at 2:30 AM UTC

Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours

User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours.

More info: While we're working to remediate impact, affected users can perform a manual check-in.

Current status: We've confirmed that a component introduced in a recent Windows update is causing the issue and are developing a fix. We'll provide an estimated release timeline once one is available.

Scope of impact: Any user with a Microsoft Intune enrolled Windows device may be affected. This information may be updated as our investigation continues.

Root cause: A recent Windows update contains a code issue affecting Intune's ability to perform an initial check-in, resulting in impact.

Next update by: Thursday, November 12, 2026, at 2:30 AM UTC

Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours

User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours.

More info: While we're working to remediate impact, affected users can perform a manual check-in.

Current status: This event is a continuation of the issue previously communicated via IT1547988.

Our monitoring has identified an increase in delays affecting check-ins for Microsoft Intune-enrolled Windows devices. Our investigation indicates that an issue in a recent Windows update is causing initial device check-in attempts to fail, while subsequent automated and manual attempts remain unaffected. We're continuing to analyze the changes introduced in the recent Windows update to isolate the specific root cause and determine an appropriate remediation strategy.

Scope of impact: Any user with a Microsoft Intune enrolled Windows device may be affected. This information may be updated as our investigation continues.

Next update by: Wednesday, November 11, 2026, at 8:00 PM UTC

Title: Some users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours

User impact: Users' Microsoft Intune enrolled Windows devices may experience device check-in delays of up to eight hours.

Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

A post-incident report has been published.

A post-incident report has been published.

A post-incident report has been published.

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not have been quarantined and failed to be stored in the quarantine folder.

More info: The following error appeared in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Final status: We completed deployment of our fix to the affected environments and confirmed with affected users that this action successfully resolved the problem.

Scope of impact: This issue impacted users attempting to have email messages quarantined in Exchange Online.

Start time: Wednesday, September 23, 2026, at 12:56 AM UTC

End time: Friday, October 2, 2026, at 8:24 AM UTC

Root cause: Exchange Online can place messages that match an organization's protection or data loss prevention (DLP) policies into quarantine, where administrators can review and release them. Some of these messages are stored in a quarantine location that belongs to the organization, and to route a message there, the service first identifies the organization it belongs to. A recent service update included a change to how our service creates and retrieves organization identity information. After this update, the step that routes messages to the organization's quarantine location was, in some cases, unable to obtain the organization's identifier. When this occurred, the service couldn't determine where to store the message, and the message was returned to the sender with the error "550 5.1.10 Failed to deliver to Quarantine store" instead of being quarantined.

Next steps: We're reviewing the service-side update that introduced the code error to understand why it resulted in this impact and help prevent similar issues from occurring in the future.

Next steps:

We've provided a Post-Incident Report for this incident.

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: We're continuing to monitor the deployment of our fix, which has reached 88 percent saturation to the affected environment. We anticipate the deployment will complete by our next scheduled communications update.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Start time: Wednesday, September 23, 2026, at 12:56 AM UTC

Estimated time to resolve: We anticipate the fix will complete deployment by Friday, October 2, 2026, at 7:00 PM UTC.

Root cause: A recent service-side update introduced a code error that has caused this impacting event.

Next update by: Friday, October 2, 2026, at 7:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: We've initiated the fix release and are monitoring as it progresses. We expect to have a completion timeline by the next scheduled update.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent service-side update introduced a code error that has caused this impacting event.

Next update by: Thursday, October 1, 2026, at 11:30 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: Validation of our fix is in its final stages, and we expect to begin deploying it to the affected environment by our next scheduled update. We’ll provide an estimated completion timeline once available.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.

Next update by: Thursday, October 1, 2026, at 6:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: Validation of our fix is in its final stages, and we expect to begin deploying it to the affected environment by our next scheduled update. We’ll provide an estimated completion timeline once available.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.

Next update by: Thursday, October 1, 2026, at 6:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: We've identified a recent service-side update that introduced an impacting code error that's causing some email messages to not be quarantined and fail to be stored in the quarantine folder. As we develop a code fix to remediate the impact, we're exploring a secondary potential mitigation option involving moving affected service traffic. We're expecting more clarity into our mitigation action plan by our next scheduled communication update.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.

Next update by: Thursday, October 1, 2026, at 1:00 AM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: Affected emails cannot be released through the standard Microsoft Defender quarantine workflow. The following error appears in message trace: '‎550 5.1.10 Failed to deliver to Quarantine store‎'.

Current status: A recent service-side update unintentionally introduced a code error that is causing legitimate email messages to be incorrectly quarantined and not delivered to recipients. We're developing a code fix and actively validating and testing the remediation in our test environment before broader deployment. We expect this validation work to be completed before our next scheduled communication update.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Start time: Wednesday, September 23, 2026, at 12:56 AM UTC

Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.

Next update by: Thursday, October 1, 2026, at 11:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: Affected email can’t be released through the normal Microsoft Defender quarantine workflow.

Current status: We've received the requested network message IDs (NMIDs) for failing email deliveries and are analyzing them in order to assist with our ongoing root cause investigation.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Next update by: Thursday, September 24, 2026, at 11:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: Affected email can’t be released through the normal Microsoft Defender quarantine workflow.

Current status: We're analyzing potential email processing failures from the provided message IDs. We're working with some reporting users to collect and provide network message IDs (NMIDs) from failing email deliveries to assist with our troubleshooting analysis.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Next update by: Thursday, September 24, 2026, at 8:00 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: Some legitimate email messages are not being delivered to the intended recipient and cannot be released through the normal Microsoft Defender quarantine workflow.

Current status: We're reviewing message IDs to help determine the next steps to reach a mitigation plan and root cause analysis.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Next update by: Thursday, September 24, 2026, at 4:30 PM UTC

Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder

User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.

More info: Some legitimate email messages are not being delivered to the intended recipient and cannot be released through the normal Microsoft Defender quarantine workflow.

Current status: We're reviewing support case details to determine our next troubleshooting steps.

Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.

Next update by: Thursday, September 24, 2026, at 1:30 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not have fully displayed Out of office text.

More info: Selecting “See more” may not have displayed the full Out of office message. Users could hover over the message and see the full text in a tool tip.

Final status: Following the deployment of our solution, our internal service telemetry has verified that contact cards are displaying the full expected Out of office text, and that the impact has been remediated.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may have been impacted.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

End time: Friday, November 6, 2026, at 11:30 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contained an invalid value, resulting in impact.

Next steps:

This is the final update for the event.

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We've confirmed that our deployment has completed in the remaining impacted environments. We're performing final verification to confirm that the issue is fully remediated. Users who are still experiencing impact should restart their Teams app and ensure that they're running the latest version.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Tuesday, November 10, 2026, at 10:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We've addressed the deployment blocker and our fix deployment to the remaining affected environments has resumed. We estimate that this deployment will complete and have resolved the remaining impact by our next scheduled communications update.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Monday, November 9, 2026, at 10:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We're continuing to address the deployment blocker to allow our remediation deployment to resume and resolve the remaining impact. The majority of the impact has already been resolved, and we'll provide an updated resolution timeline once available.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Wednesday, November 4, 2026, at 9:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We've isolated a deployment blocker that is delaying our mitigation deployment from completing. While a majority of the impact has already been resolved, we're addressing the blocker so our deployment can resume and so the impact for the subset of remaining users can be resolved.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Friday, October 30, 2026, at 9:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We're continuing to monitor the deployment of our fix, which has completed deployment to a majority of affected users at this time. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:15 AM UTC

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Tuesday, October 27, 2026, at 9:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: The deployment of our fix is continuing to progress as expected and we estimate that it'll reach completion by our next scheduled communications update. We'll continue to monitor as it progresses through the affected environments to ensure no adverse effects occur along the way. Additionally, as it progresses, users will experience relief from impact as the fix reaches them.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted. This section may be updated as our investigation continues.

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Friday, October 23, 2026, at 9:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We've identified that a recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact. We're deploying a fix to correct the value and remediate the impact. We'll provide a timeline for the completion of the deployment as one becomes available.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted.

Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.

Next update by: Monday, October 19, 2026, at 9:00 PM UTC

Title: Users' Microsoft Teams contact cards may not fully display Out of office text

User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.

More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

Current status: We're reviewing the screenshots provided by a subset of affected users to gain clarity on the issue and determine the next steps to isolate the root cause.

Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted.

Next update by: Monday, October 12, 2026, at 11:00 PM UTC

Title: Users' Microsoft Teams contact cards don't fully display Out of office text

User impact: Users' Microsoft Teams contact cards don't fully display Out of office text.

More info: Selecting “See more” doesn’t display the full Out of office message. Users may hover over the message to see the full text in a tool tip.

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.

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may have been unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) made the team visible for that user.

Final status: We've confirmed that the fix has completed across all affected environments and validated this issue has been remediated with service telemetry and affected users.

Scope of impact: This issue may have affected any user attempting to view previously deleted and restored teams.

Start time: Monday, October 26, 2026, at 12:53 PM UTC

End time: Tuesday, November 10, 2026, at 2:00 PM UTC

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next steps: We're continuing our analysis of the impacting change to better identify and prevent similar impact in the future.

This is the final update for the event.

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: The rollout of our fix is ongoing and will be completed in stages. Early deployment has been completed and we're seeing improvements in system health, but more time will be required to complete the full rollout and monitor for confirmation of impact resolution.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Start time: Monday, October 26, 2026, at 12:53 PM UTC

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next update by: Tuesday, November 10, 2026, at 8:30 PM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: We're continuing our fix deployment and expect the process to finish in a few hours.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Start time: Monday, October 26, 2026, at 12:53 PM UTC

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next update by: Tuesday, November 10, 2026, at 7:00 AM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: We're monitoring our fix deployment as it saturates throughout the affected environment, and we expect this process to complete by Tuesday, November 10, 2026, at 12:00 AM UTC. Once fully saturated, we'll validate whether impact is resolved or if any additional mitigative actions may be required to do so.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Start time: Monday, October 26, 2026, at 12:53 PM UTC

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next update by: Tuesday, November 10, 2026, at 2:00 AM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: We’ve completed the development of our fix and have initiated its deployment. We’re working to establish an accurate timeline for deployment completion and impact remediation to provide with our next scheduled communication update.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next update by: Monday, November 9, 2026, at 10:30 PM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: We’ve identified a recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. We’re developing a fix to correct this issue and working to establish a timeline for the fix deployment.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact.

Next update by: Monday, November 9, 2026, at 7:30 PM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

Current status: We’re reviewing screenshots of impact and client logs captured from an affected user to assist our investigation into the source of the issue. In parallel, we’ve successfully reproduced impact in our internal testing environment and are reviewing this reproduction to further assist our root cause efforts.

Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues.

Next update by: Monday, November 9, 2026, at 5:30 PM UTC

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams

User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams.

More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user.

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.

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may have shown outdated data in the Microsoft 365 admin center.

Final status: We've completed processing the backlog of events and validated that Microsoft 365 apps usage reports are now up to date.

Scope of impact: This issue may have impacted any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

End time: Tuesday, November 10, 2026, at 8:00 AM UTC

Root cause: An upstream component of the data processing pipeline had entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next steps:

-We're analyzing the problematic upstream component to validate why it entered an unhealthy state. This further analysis will help us to evaluate what actions we can take to ensure similar impact scenarios don't occur in the future.

This is the final update for the event.

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: While reporting is now available through Tuesday, November 2, 2026, we're continuing to monitor as the backlog of events are processed.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Tuesday, November 10, 2026, at 8:00 PM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We're continuing our aforementioned efforts to ensure that the issue is fully resolved.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Monday, November 9, 2026, at 8:00 PM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We're continuing to monitor the recovery of the data pipeline health as it returns to normal, along with ensuring that all fix deployments have completed successfully.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Saturday, November 7, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: Our data pipeline is recovering as our ongoing fix deployment continues to progress. We'll continue to monitor the data pipeline health and fix deployment to ensure they complete successfully.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Friday, November 6, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We've applied a fix to a number of additional sources that we identified as contributors to the delays. While we monitor the data pipeline health throughout our ongoing fix deployment, we're also continuing our investigation to ensure that we to identify and resolve all sources of these delays.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Thursday, November 5, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: While the upstream fix has restored some historical Apps usage data up to October 28, 2026, we're investigating additional sources that are contributing to ongoing delays so that we can determine our next steps to fully resolve reporting delays.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Wednesday, November 4, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We've applied our fix to correct the impact to the upstream components of the Microsoft 365 apps usage data processing pipeline, and we're ensuring the continue recovery of affected reports. We'll provide a timeline for this process to complete as one becomes available.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Tuesday, November 3, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We continue to work on our fix to correct the unhealthy nature of the upstream components of the Microsoft 365 apps usage data processing pipeline.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Monday, November 2, 2026, at 8:00 PM UTC

Title: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center

User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the Microsoft 365 admin center.

Current status: We've identified through our monitoring of service health telemetry that an upstream component of the Microsoft 365 Apps usage data processing pipeline is in an unhealthy state, which is resulting in data reporting delays. We're working to implement a fix for the impacted component to restore timely data processing.

Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues.

Start time: Friday, October 30, 2026, at 12:00 AM UTC

Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data.

Next update by: Saturday, October 31, 2026, at 2:00 AM UTC

Title: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder

User impact: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder.

More info: The Copilot Agent is shared as expected, but users may see an error message that reads: "We couldn't save your sharing settings. There was an issue saving sharing settings. Try again.” This error is purely a UI issue and is non-blocking.

This issue only occurs when sharing agents with new owners after giving them editing permissions in the Microsoft Copilot Agent Builder.

Current status: Our internal validations are proceeding as expected and we anticipate having a release timeline by the next scheduled communications update.

Scope of impact: This impacts any user attempting to share agents to new owners with editing permissions in Copilot Agent Builder, who may see an erroneous error. This information may be updated as our investigation continues.

Root cause: An underlying code issue in the service is resulting in this incorrect message in the User Interface.

Next update by: Tuesday, November 17, 2026, at 12:00 AM UTC

Title: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder

User impact: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder.

More info: The Copilot Agent is shared as expected, but users may see an error message that reads: "We couldn't save your sharing settings. There was an issue saving sharing settings. Try again.” This error is purely a UI issue and is non-blocking.

This issue only occurs when sharing agents with new owners after giving them editing permissions in the Microsoft Copilot Agent Builder.

Current status: We're in the process of validating a fix internally and expect to initiate the release by the next scheduled update.

Scope of impact: This impacts any user attempting to share agents to new owners with editing permissions in Copilot Agent Builder, who may see an erroneous error. This information may be updated as our investigation continues.

Root cause: An underlying code issue in the service is resulting in this incorrect message in the User Interface.

Next update by: Tuesday, November 10, 2026, at 12:00 AM UTC

Title: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder

User impact: Users may see an erroneous error when sharing agents with new owners in Microsoft Copilot Agent Builder.

More info: The Copilot Agent is shared as expected, but users may see an error message that reads: "We couldn't save your sharing settings. There was an issue saving sharing settings. Try again.” This error is purely a UI issue and is non-blocking.

This issue only occurs when sharing agents with new owners after giving them editing permissions in the Microsoft Copilot Agent Builder.

Current status: After further analysis, we've validated that impact is only occurring when sending agents to new owners with editing permissions and we've updated the "Title", "User impact", "More info", and "Scope of impact" sections of our communications to reflect this. We're continuing to monitor the deployment of our fix, and we aim to provide a timeline to remediation as soon as possible.

Scope of impact: This impacts any user attempting to share agents to new owners with editing permissions in Copilot Agent Builder, who may see an erroneous error. This information may be updated as our investigation continues.

Root cause: An underlying code issue in the service is resulting in this incorrect message in the User Interface.

Next update by: Thursday, November 5, 2026, at 12:00 AM UTC

Title: Users may see an erroneous error when sharing agents in Microsoft Copilot Agent Builder

User impact: Users may see an erroneous error when sharing agents in Microsoft Copilot Agent Builder.

More info: The Copilot Agent is shared as expected, but users may see an error message that reads: "We couldn't save your sharing settings. There was an issue saving sharing settings. Try again.” This error is purely a UI issue and is non-blocking.

Current status: We determined that an underlying code issue in the service is resulting in this incorrect message in the User Interface and have deployed a fix to address this issue. We'll monitor this fix and provide a remediation timeline as soon as one becomes available.

Scope of impact: This impacts any user attempting to share agents in Copilot Agent Builder, who may see an erroneous error. This information may be updated as our investigation continues.

Root cause: An underlying code issue in the service is resulting in this incorrect message in the User Interface.

Next update by: Thursday, November 5, 2026, at 12:00 AM UTC

Title: Admins may be unable to utilize some administrative Microsoft Teams features

User impact: Admins may be unable to utilize some administrative Microsoft Teams features.

More info: The following administrative Microsoft Teams features are impacted:

Current status: We're progressing with the final pre-deployment steps before re-enablement of the affected administrative Microsoft Teams features. We'll validate if these will be re-enabled by our estimate of November 15, 2026, during our next scheduled communication update.

Scope of impact: This issue may prevent any admin from utilizing some administrative Microsoft Teams features. This section may be updated as our investigation continues.

Start time: Thursday, October 15, 2026, at 1:30 AM UTC

Root cause: The Windows Autopilot and One-Time Passcode features were temporarily disabled to allow for a Pro Management Portal service update to properly integrate.

Next update by: Saturday, November 14, 2026, at 12:00 AM UTC

Title: Admins may be unable to utilize some administrative Microsoft Teams features

User impact: Admins may be unable to utilize some administrative Microsoft Teams features.

More info: The following administrative Microsoft Teams features are impacted:

Current status: We're continuing to re-enable the features now that the service update has successfully deployed, and we expect it will complete on Sunday, November 15, 2026.

Scope of impact: This issue may prevent any admin from utilizing some administrative Microsoft Teams features. This section may be updated as our investigation continues.

Start time: Thursday, October 15, 2026, at 1:30 AM UTC

Root cause: The Windows Autopilot and One-Time Passcode features were temporarily disabled to allow for a Pro Management Portal service update to properly integrate.

Next update by: Monday, November 9, 2026, at 11:00 PM UTC

Title: Admins may be unable to utilize some administrative Microsoft Teams features.

User impact: Admins may be unable to utilize some administrative Microsoft Teams features.

More info: The following administrative Microsoft Teams features are impacted:

Current status: We've adjusted the root cause statement of this communication to clarify that the disablement of the Autologin and One-Time Passcode features was intended and necessary for a Pro Management Portal service update to properly integrate. We're working to re-enable the features now that the service update has successfully deployed, and we'll aim to provide a timeline for when both features will be accessible again by our next scheduled communications update.

Scope of impact: This issue may prevent any admin from utilizing some administrative Microsoft Teams features. This section may be updated as our investigation continues.

Start time: Thursday, October 15, 2026, at 1:30 AM UTC

Root cause: The Autologin and One-Time Passcode features were temporarily disabled to allow for a Pro Management Portal service update to properly integrate.

Next update by: Monday, October 26, 2026, at 11:00 PM UTC

Title: Admins may be unable to utilize some administrative Microsoft Teams features.

User impact: Admins may be unable to utilize some administrative Microsoft Teams features.

More info: The following administrative Microsoft Teams features are impacted:

Current status: We've determined that a recent update to security to the Pro Management Portal is causing some administrative features to be unavailable. We're further reviewing the offending update and the affected features to determine how best to re-enable.

Scope of impact: This issue may prevent any admin from utilizing some administrative Microsoft Teams features. This section may be updated as our investigation continues.

Start time: Thursday, October 15, 2026, at 1:30 AM UTC

Root cause: A recent security update to the Pro Management Portal has resulted in impact.

Next update by: Thursday, October 22, 2026, at 11:00 PM UTC

Title: Some users may be unable to access Microsoft Forms

User impact: Users may have been unable to access Microsoft Forms.

More info: Impacted Forms scenarios included, but weren't limited to:

Final status: A clean-up service running after the initial restarts briefly caused an interruption which has since passed. We've confirmed that this issue has been remediated with affected users and service telemetry.

Scope of impact: Impact was specific to some users attempting to access Microsoft Forms.

Start time: Wednesday, November 4, 2026, at 2:00 AM UTC

End time: Wednesday, November 4, 2026, at 5:40 PM UTC

Root cause: A portion of infrastructure that facilitates Microsoft Forms access wasn't processing requests as efficiently as expected, resulting in impact.

Next steps:

This is the final update for the event.

Title: Some users may be unable to access Microsoft Forms

User impact: Users may be unable to access Microsoft Forms.

More info: Impacted Forms scenarios include, but aren't limited to:

Current status: Our analysis of service telemetry in conjunction with internal testing has identified that a portion of infrastructure that facilitates Microsoft Forms access wasn't processing requests as efficiently as expected, resulting in impact. We've restarted services on the affected infrastructure and while our monitoring indicates that service health has partially recovered, some users are still reporting impact. We're working to gather additional diagnostic data from users still experiencing the issue to further isolate the underlying cause of impact and provide relief to the remaining affected users.

Scope of impact: Impact may be specific to some users attempting to access Microsoft Forms. This information may be updated as our investigation continues.

Start time: Wednesday, November 4, 2026, at 2:00 AM UTC

Next update by: Wednesday, November 4, 2026, at 8:00 PM UTC

Title: Some users may be unable to access Microsoft Forms

User impact: Users may be unable to access Microsoft Forms.

More info: Impacted Forms scenarios include, but aren't limited to:

Current status: We’re continuing to review service telemetry and diagnostic logs to identify the cause of the issue and develop a mitigation plan.

Scope of impact: Impact may be specific to some users attempting to access Microsoft Forms. This information may be updated as our investigation continues.

Next update by: Wednesday, November 4, 2026, at 6:00 PM UTC

Title: Some users may be unable to access Microsoft Forms

User impact: Users may be unable to access Microsoft Forms.

More info: Impacted Forms scenarios include, but aren't limited to:

Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.

Scope of impact: Impact may be specific to some users attempting to access Microsoft Forms. This information may be updated as our investigation continues.

Next update by: Wednesday, November 4, 2026, at 4:00 PM UTC

Title: Users may have been unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may have been unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may have encountered the following error message when attempting to publish their Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates to the Global Address List (GAL) using the "Publish to GAL" option in Microsoft Outlook:

"Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Final status: We've completed deployment of the fix across the affected environment and confirmed with your organization's representatives that impact has now been remediated.

Scope of impact: Impact was specific to any user attempting to upload S/MIME to the GAL through Outlook desktop.

Start time: Tuesday, October 6, 2026, at 12:00 AM UTC

End time: Wednesday, October 28, 2026, at 5:30 AM UTC

Root cause: A recent S/MIME certificate change prevented users from uploading their S/MIME certificates to the GAL through Outlook desktop.

Next steps:

This is the final update for the event.

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: Based on our monitoring of the deployment's saturation process, we now anticipate that impact may be remediated by our next scheduled update. Additionally, we anticipate that affected users will incrementally be remediated as the deployment propagates throughout the affected service environment.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Start time: Tuesday, October 6, 2026, at 12:00 AM UTC

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Wednesday, November 4, 2026, at 10:30 AM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: After verifying with affected users that our fix restored certificate upload capabilities to the GAL through Outlook desktop, we're broadly deploying our solution to remediate the impact. We'll provide an updated timeline for the deployment and the remediation of the impact once it has become available.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Start time: Tuesday, October 6, 2026, at 12:00 AM UTC

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Thursday, October 29, 2026, at 7:30 AM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We've confirmed that the fix has been deployed to a subsection of the affected infrastructure, and some users should begin to see recovery as the changes take effect. We're monitoring the effectiveness of the fix, and once we've confirmed that it resolves the issue and existing deployment restrictions allow, we'll continue deployment across the remaining affected infrastructure.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Wednesday, October 28, 2026, at 9:00 PM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We've begun deploying the aforementioned fix and anticipate completion by our next scheduled update.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Wednesday, October 28, 2026, at 12:30 PM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We've begun deploying the aforementioned fix and anticipate completion by our next scheduled update.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Wednesday, October 28, 2026, at 12:30 PM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: The analysis of our deployment process is progressing, though it's taking an extended period of time as we continue to validate the most effective method at remediating the issue.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Thursday, October 22, 2026, at 12:30 PM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We've received information indicating that the impact persists for some users. We're analyzing our deployment process to determine the appropriate next steps and ensure the issue is fully resolved.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Start time: Tuesday, October 6, 2026, at 12:00 AM UTC

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

Next update by: Wednesday, October 21, 2026, at 5:30 AM UTC

Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center

User impact: Admins' Copilot and Copilot Chat usage reports were delayed by up to 24 hours in the Microsoft 365 admin center.

Final status: We've resolved the upstream pipeline degradation, and the affected reporting jobs have completed successfully. After monitoring the service, we've confirmed that Microsoft 365 Copilot and Copilot Chat usage reports have fully recovered across all affected regions.

Scope of impact: Some admins' Copilot and Copilot Chat usage reports may have been delayed by up to 24 hours in the Microsoft 365 admin center.

Start time: Monday, November 2, 2026, at 12:00 AM UTC

End time: Tuesday, November 3, 2026, at 1:20 AM UTC

Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot Chat usage reports caused impact.

Next steps: We're investigating why the upstream data pipeline didn't function as intended to implement measures for preventing this problem from happening again in the future.

This is the final update for the event.

Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center

User impact: Admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center.

Current status: We're continuing our efforts to resolve the pipeline degradation and restore reports. We anticipate this may complete by our next scheduled update.

Scope of impact: Some admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. This section may be updated as the investigation progresses.

Start time: Monday, November 2, 2026, at 12:00 AM UTC

Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot chat usage reports is causing impact.

Next update by: Tuesday, November 3, 2026, at 7:00 PM UTC

Title: Some admins' Microsoft 365 Copilot and Copilot Chat usage reports may be delayed in the Microsoft 365 admin center

User impact: Admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center.

Current status: Our service telemetry has alerted us to ongoing data population delays of approximately 24 hours for Copilot and Copilot Chat usage reports to populate in the Microsoft 365 admin center. We're isolated that a degradation in the upstream data pipeline used to populate these reports is causing impact, and we're working to remediate the degradation to restore reports as soon as possible.

Scope of impact: Some admins' Copilot and Copilot Chat usage reports may be delayed by 24 hours in the Microsoft 365 admin center. This section may be updated as the investigation progresses.

Start time: Monday, November 2, 2026, at 12:00 AM UTC

Root cause: A degradation in the upstream data pipeline used to populate Copilot and Copilot chat usage reports is causing impact.

Next update by: Tuesday, November 3, 2026, at 3:00 AM UTC

Title: Admins couldn't download the Migration Manager agent from the SharePoint admin center

User impact: Admins couldn't download the Migration Manager agent from the SharePoint admin center.

More info: Admins received an error stating, "The specified container does not exist."

Final status: We've identified that a storage account containing files required for application downloads was inadvertently disabled, which caused the removal of the files needed to execute the download and resulted in impact. We've restored the affected files and confirmed that users can successfully download the applications again. We’re also progressing a long-term solution to prevent similar impact from recurring.

Scope of impact: Your organization was affected by this event, and this issue prevented admins from downloading the Migration Manager agent.

Start time: Monday, November 2, 2026, at 9:07 AM UTC

End time: Tuesday, November 3, 2026, at 4:00 AM UTC

Root cause: A storage account containing files required for application downloads was inadvertently disabled, which caused the removal of the files needed to execute the download and resulted in impact.

Next steps:

This is the final update for the event.

Title: Admins can't download the Migration Manager agent from the SharePoint admin center

User impact: Admins can't download the Migration Manager agent from the SharePoint admin center.

More info: Admins receive an error stating, "The specified container does not exist."

Current status: We've identified a change to the SharePoint Online service that we believe is causing impact. We're in the process of rolling back this change and once complete, we'll validate whether it has had the desired effect of resolving impact.

Scope of impact: Your organization is affected by this event, and this issue prevents admins from downloading the Migration Manager agent. This section may be updated as our investigation continues.

Root cause: A recent change to the SharePoint Online service that supports the Migration Manager agent in the SharePoint Online admin center contains a code regression and is leading to impact.

Next update by: Tuesday, November 3, 2026, at 2:00 PM UTC

Title: Admins can't download the Migration Manager agent from the SharePoint admin center

User impact: Admins can't download the Migration Manager agent from the SharePoint admin center.

More info: Admins receive an error stating, "The specified container does not exist."

Current status: It's taking longer than expected to review the service telemetry and potential changes that may be contributing to this issue, but we're making progress as we strive to understand the root cause and devise a strategy that remediates impact.

Scope of impact: Your organization is affected by this event, and this issue prevents admins from downloading the Migration Manager agent. This section may be updated as our investigation continues.

Next update by: Tuesday, November 3, 2026, at 2:30 AM UTC

Title: Admins can't download the Migration Manager agent from the SharePoint admin center

User impact: Admins can't download the Migration Manager agent from the SharePoint admin center.

More info: Admins receive an error stating, "The specified container does not exist."

Current status: We're continuing to review the service telemetry and looking for potential changes that could be contributing to the issue to identify the root cause and a strategy that remediates impact.

Scope of impact: Your organization is affected by this event, and this issue prevents admins from downloading the Migration Manager agent.

Next update by: Monday, November 2, 2026, at 9:00 PM UTC

Title: Admins can't download the Migration Manager agent from the SharePoint admin center

User impact: Admins can't download the Migration Manager agent from the SharePoint admin center.

More info: Admins receive an error stating, "The specified container does not exist."

Current status: We're reviewing admin reports of impact and service telemetry for this functionality to gain a better understanding of what's leading to this behavior.

Scope of impact: Your organization is affected by this event, and this issue prevents admins from downloading the Migration Manager agent.

Next update by: Monday, November 2, 2026, at 7:00 PM UTC

Title: Possible delays or problems when accessing SharePoint Online

User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online.

Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may have been unable to ask about work-grounded data in Copilot.

More info: This issue may have affected users that attempted to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may have received an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue did not affect Outlook Copilot or mobile Copilot.

When attempting to ask about work-grounded data, users may have received an error stating "I can't access your inbox or email account with the tools available in this chat."

Final status: We disabled some recent code changes that were causing the issue and validated with monitoring internal telemetry that the impact is fully mitigated.

Scope of impact: This issue may have affected any user that attempted to ask about work-grounded data in Copilot

Start time: Thursday, October 29, 2026, at 1:29 AM UTC

End time: Tuesday, November 3, 2026, at 1:09 AM UTC

Root cause: A recent change deployment introduced a conflict by enabling an underlying feature utilized in the search process early prior to the accompanying change deployment.

Next steps:

This is the final update for the event.

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may be unable to ask about work-grounded data in Copilot.

More info: This issue may affect users attempting to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may receive an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue does not affect Outlook Copilot or mobile Copilot.

Current status: We've confirmed after testing with a subset of users that impact persists. We're collecting additional conversation IDs from affected requests to investigate further and determine why our fix worked in our internal testing environment but isn't having the same effect in the affected environment to formulate our next steps.

Scope of impact: This issue may affect any user attempting to ask about work-grounded data in Copilot.

Start time: Thursday, October 29, 2026, at 1:29 AM UTC

Root cause: A recent change deployment introduced a conflict by enabling an underlying feature utilized in the search process early prior to the accompanying change deployment.

Next update by: Tuesday, November 3, 2026, at 1:30 AM UTC

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may be unable to ask about work-grounded data in Copilot.

More info: This issue may affect users attempting to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may receive an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue does not affect Outlook Copilot or mobile Copilot.

Current status: We've confirmed a recent change deployment introduced a conflict by enabling an underlying feature utilized in the search process early prior to the accompanying change deployment. To correct this issue, we've begun rolling back the affecting change. Once complete, we'll reach out to a subset of affected users to confirm impact remediation.

Scope of impact: This issue may affect any user attempting to ask about work-grounded data in Copilot.

Start time: Thursday, October 29, 2026, at 1:29 AM UTC

Root cause: A recent change deployment introduced a conflict by enabling an underlying feature utilized in the search process early prior to the accompanying change deployment.

Next update by: Tuesday, November 3, 2026, at 12:00 AM UTC

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may be unable to ask about work-grounded data in Copilot.

More info: This issue may affect users attempting to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may receive an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue does not affect Outlook Copilot or mobile Copilot.

Current status: After our testing in our internal environment, we've further confirmed that there are two changes concerning the Work IQ tool, which is utilized when performing work-grounded searches in Copilot. One change was to add additional source controls to the client when performing searches in Copilot, while another change was to initialize a component relating to WorkIQ. We've confirmed that the latter change, concerning the component, was deployed, however it requires the former change, concerning source controls, to function as expected. We're reviewing options to complete the source control deployment, or to potentially rollback the component change, to determine the best path forward for remediation before testing further in our internal environment.

Scope of impact: This issue may affect any user attempting to ask about work-grounded data in Copilot.

Next update by: Monday, November 2, 2026, at 10:00 PM UTC

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may be unable to ask about work-grounded data in Copilot.

More info: This issue may affect users attempting to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may receive an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue does not affect Outlook Copilot or mobile Copilot.

Current status: Our investigation of the potentially impacting deployment identified that a recent change to enable a Work IQ tool, which is utilized when performing work-grounded searches in Copilot, wasn’t fully rolled out as expected. After successfully reproducing impact in our internal test environment, we're deploying this change in full to the test environment to confirm whether it remediates impact before completing the deployment in the affected environment.

Scope of impact: This issue may affect any user attempting to ask about work-grounded data in Copilot.

Next update by: Monday, November 2, 2026, at 8:00 PM UTC

Title: Users may be unable to ask about work-grounded data in Microsoft 365 Copilot

User impact: Users may be unable to ask about work-grounded data in Copilot.

More info: This issue may affect users attempting to ask about work-grounded data, such as email messages, calendars and files through Copilot.

When attempting to ask about work-grounded data, users may receive an error stating "I can't access your inbox or email account with the tools available in this chat."

The issue does not affect Outlook Copilot or mobile Copilot.

Current status: We've identified a recent change deployment which we suspect may be responsible for impact. We're reviewing the details of this deployment to confirm this theory and determine our next steps.

Scope of impact: This issue may affect any user attempting to ask about work-grounded data in Copilot.

Next update by: Monday, November 2, 2026, at 6:00 PM UTC

A post-incident report has been published.

A post-incident report has been published.

A post-incident report has been published.

Title: Users may be unable to send or receive messages, upload images, or schedule meetings in Microsoft Teams

User impact: Users may have been unable to send or receive messages, upload images, or schedule meetings in Teams.

More info: Users may have also encountered issues with

Final status: We can confirm after monitoring our telemetry that the automatic scaling efforts to increase processing throughput were successful and the service has returned to healthy levels.

Scope of impact: GCC users who attempted to send or receive messages, upload images, or schedule meetings in Microsoft Teams may have been impacted by this event.

Start time: Monday, October 26, 2026, at 3:01 PM UTC

End time: Monday, October 26, 2026, at 3:42 PM UTC

Preliminary root cause: We've identified that higher-than-normal latency impacted backend services that manage chat threads and messages, along with higher-than-normal Central Processing Unit (CPU) utilization resulted in our service entering an unhealthy state.

Next steps:

We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.

We're seeing positive trends towards recovery in our telemetry following our service's automatic scaling efforts to increase processing throughput.

This quick update is designed to give the latest information on this issue.

Next update by: Monday, October 26, 2026, at 5:00 PM UTC

Title: Users may be unable to send or receive messages, upload images, or schedule meetings in Microsoft Teams

User impact: Users may be unable to send or receive messages, upload images, or schedule meetings in Teams.

More info: Users may also encounter issues with

Current status: We've received reports with Teams issues in GCC and we're analyzing recent changes and service telemetry to isolate the source of the issue.

Scope of impact: GCC users attempting to send or receive messages, upload images, or schedule meetings in Microsoft Teams may be impacted by this event.

Start time: Monday, October 26, 2026, at 3:00 PM UTC

Next update by: Monday, October 26, 2026, at 5:00 PM UTC

Title: We're looking into a potential problem impacting images in Microsoft Teams

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue with images in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may have been unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may have replied or replied all to email messages through user inboxes.

Final status: Our fix deployment has completed, and we've confirmed that this has successfully resolved the event through service health telemetry.

Scope of impact: This issue may have impacted any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

End time: Wednesday, October 28, 2026, at 7:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that required that attribute, which was resulting in this impact.

Next steps: - We're reviewing the responsible change 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.

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We're continuing to monitor the completion of our fix deployment and expect clarity into its remaining timeline to be available by our next scheduled communication update.

Scope of impact: This issue may impact any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Wednesday, October 28, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: The fix has deployed to around 95 percent of the infrastructure. While the deployment progress has slowed, it's within our expectations as the final infrastructure unit deployments usually take more time. A majority of users are likely no longer seeing the issue as they've received the fix. We'll continue to monitor the deployment process to ensure it completes successfully.

Scope of impact: This issue may impact any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Tuesday, October 27, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our fix remains 93 percent saturated, and we're continuing to monitor as the deployment progresses, albeit at a slow pace as it nears completion. We'll aim to provide a timeline for remediation as one becomes available.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Thursday, October 22, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our fix remains at 93 percent, as the remaining saturation is expected to take extra time, per process. We're continuing to monitor progress toward completion and confirm that impact is remediated for all users.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Monday, October 19, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our fix deployment has completed in the initial deployment rings and has started saturating in affected customers' environments. Our monitoring has validated that our fix has completed approximately 93 percent of the deployment, and we'll provide an updated timeline for it completing once it has become available.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Thursday, October 15, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our monitoring of the deployment is ongoing as it propagates through earlier deployment rings prior to beginning saturation to affected customers’ environments. We'll provide a projected timeline for remediation based on the rate of progress as one becomes available.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Wednesday, October 14, 2026, at 8:30 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We're continuing to monitor and track the saturation percentage of the fix deployment to ensure it reaches 100 percent in all affected environments.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We've validated that the previously identified recent change that removed an attribute component from the service process that requires that attribute, has led to impact. We're continuing to monitor our fix deployment; however, this process is taking longer than anticipated. The current fix saturation is at roughly 90 percent, and we'll provide a timeline of completion once it becomes available.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Start time: Tuesday, September 8, 2026, at 11:00 PM UTC

Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.

Next update by: Tuesday, October 13, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We're continuing to monitor the deployment of our fix as it progresses, and we'll aim to provide a timeline of completion by our next scheduled communications.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Thursday, October 8, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our fix deployment is nearing completion, and most affected users should now be experiencing recovery. We’ll continue monitoring the deployment to ensure it completes and restores service for all affected users.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Wednesday, October 7, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: Our fix deployment is nearing completion, and most affected users should now be experiencing recovery. We’ll continue monitoring the deployment to ensure it completes and restores service for all affected users.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Wednesday, October 7, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We've initialized our fix deployment to the affected environment and anticipate the impact should be fully remediated by our next scheduled update.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Tuesday, October 6, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We've completed the validation of our planned fixes and are completing the final stages to prepare them for deployment. We anticipate that users will see progressive relief beginning Monday, September 28, 2026, up to our planned remediation date of Friday, October 2, 2026.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Tuesday, September 29, 2026, at 1:00 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We're conducting verification and validation testing on our proposed remediation to ensure that it will safely and effectively remediate this issue.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.

Next update by: Saturday, September 26, 2026, at 12:30 AM UTC

Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.

Current status: We've identified a recent code change which we believe may be responsible for this issue and are developing a targeted fix to verify.

Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

Next update by: Friday, September 25, 2026, at 11:00 PM UTC

Title: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.

Current status: We're reviewing support case details to better understand the impact scenario and determine our next steps.

Scope of impact: Your organization is impacted by this event and all users attempting to reply to email messages sent to Microsoft 365 groups are affected.

Next update by: Friday, September 25, 2026, at 6:00 PM UTC

Title: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online

User impact: Users can't reply or reply-all to email messages sent to Microsoft 365 groups 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.

Title: Admins were unable to complete Microsoft OneDrive or SharePoint site migrations

User impact: Admins were unable to complete OneDrive or SharePoint site migrations.

More info: Several migration workflows may have experienced impact, which included:

Final status: We've received confirmation from previously impacted users that the issue is no longer occurring.

Scope of impact: This issue would have impacted any admins attempting to perform OneDrive or SharePoint site migrations. This only applied to the M365 Multi-Geo and Cross-Tenant Migration features for SharePoint and OneDrive. Other modes of migration, such as Migration Manager (https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started) or 3rd party tools, were not affected.

Start time: Wednesday, October 28, 2026, at 6:29 PM UTC

End time: Monday, November 2, 2026, at 3:37 PM UTC

Root cause: A configuration issue within a backend migration job resulted in impact.

Next steps: - We're reviewing the migration infrastructure to better understand how to prevent this type of issue happening again.

This is the final update for the event.

Title: Admins are unable to complete Microsoft OneDrive or SharePoint site migrations

User impact: Admins are unable to complete OneDrive or SharePoint site migrations.

More info: Several migration workflows may experience impact, which include:

Current status: The aforementioned fix deployment has completed successfully. We're reaching out to a sample of previously affected admins to validate that this functionality has been restored.

Scope of impact: This issue will impact any admins attempting to perform OneDrive or SharePoint site migrations. This applies only to the M365 Multi-Geo and Cross-Tenant Migration features for SharePoint and OneDrive. Other modes of migration, such as Migration Manager (https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started) or 3rd party tools, are not affected. This information may be updated as our investigation continues.

Start time: Wednesday, October 28, 2026, at 6:29 PM UTC

Next update by: Tuesday, November 3, 2026, at 3:00 AM UTC

Title: Admins are unable to complete Microsoft OneDrive or SharePoint site migrations

User impact: Admins are unable to complete OneDrive or SharePoint site migrations.

More info: Several migration workflows may experience impact, which include:

Current status: The deployment is progressing as expected and we believe this to fully complete within the next eight hours. To expedite recovery, once a section of the service receives the full deployment, we're making the required configuration change to allow the processing of the migration jobs, so some organizations and admins will begin to experience relief sooner.

Scope of impact: This issue will impact any admins attempting to perform OneDrive or SharePoint site migrations. This applies only to the M365 Multi-Geo and Cross-Tenant Migration features for SharePoint and OneDrive. Other modes of migration, such as Migration Manager (https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started) or 3rd party tools, are not affected. This information may be updated as our investigation continues.

Start time: Wednesday, October 28, 2026, at 6:29 PM UTC

Next update by: Saturday, October 31, 2026, at 5:00 AM UTC

Title: Admins are unable to complete Microsoft OneDrive or SharePoint site migrations

User impact: Admins are unable to complete OneDrive or SharePoint site migrations.

More info: Several migration workflows may experience impact, which include:

Current status: We've identified the source of the issue, and have developed a fix which we are currently testing. Once the validations are complete, we'll start deployment.

Scope of impact: This issue will impact any admins attempting to perform OneDrive or SharePoint site migrations. This applies only to the M365 Multi-Geo and Cross-Tenant Migration features for SharePoint and OneDrive. Other modes of migration, such as Migration Manager (https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started) or 3rd party tools, are not affected. This information may be updated as our investigation continues.

Start time: Wednesday, October 28, 2026, at 6:29 PM UTC

Next update by: Friday, October 30, 2026, at 6:00 PM UTC

Title: Admins are unable to complete cross-tenant Microsoft OneDrive migrations

User impact: Admins are unable to complete cross-tenant OneDrive migrations.

More info: Admins may see some migration jobs remain in the Scheduled/Queued state.

Current status: We're continuing to review the move request jobs, and the underlying migration infrastructure to isolate the source of the issue.

Scope of impact: This could potentially impact an admins attempting to perform cross-tenant OneDrive migrations. This information may be updated as our investigation continues.

Next update by: Thursday, October 29, 2026, at 6:00 PM UTC

Title: Admins are unable to complete cross-tenant Microsoft OneDrive migrations

User impact: Admins are unable to complete cross-tenant OneDrive migrations.

More info: Admins may see some migration jobs remain in the Scheduled/Queued state.

Current status: We're reviewing the move request jobs to identify where the migration process is failing to complete. Once this review is complete, we'll have a better understanding of the root cause and the appropriate steps to mitigate impact.

Scope of impact: Your organization is affected by this event, and admins attempting to complete cross-tenant OneDrive migrations are impacted. This information may be updated as our investigation continues.

Next update by: Thursday, October 29, 2026, at 2:30 PM UTC

Title: Admins are unable to complete cross-tenant Microsoft OneDrive migrations

User impact: Admins are unable to complete cross-tenant OneDrive migrations.

More info: Admins may see some migration jobs remain in the Scheduled/Queued state.

Current status: We're analyzing support provided information to determine our next troubleshooting steps.

Scope of impact: Your organization is affected by this event, and admins attempting to complete cross-tenant OneDrive migrations are impacted.

Next update by: Thursday, October 29, 2026, at 12:30 PM UTC

Title: Users may have been prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may have been prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may have been prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Final status: We've received confirmation from affected users that the fix fully resolved the issue.

Scope of impact: Some users attempting to resolve "Potentially leaked credentials" recommendations in Microsoft Defender for Identity within the Microsoft Defender portal may have been impacted.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

End time: Thursday, October 29, 2026, at 8:00 PM UTC

Root cause: A code issue was causing the same identities to be repeatedly retriggered, which resulted in impact.

Next steps:

This is the final update for the event.

Title: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: We’re awaiting feedback from affected users to confirm that the fix has fully resolved the impact.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Root cause: A code issue is retriggering the same identities, resulting in impact.

Next update by: Monday, November 2, 2026, at 3:00 PM UTC

Title: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: We've completed deployment of our fix to cover all impact scenarios. Our service health telemetry suggests that this fix improved the issue, and we're reaching out to a subset of affected users to confirm that the impact is fulling remediated.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Root cause: A code issue is retriggering the same identities, resulting in impact.

Next update by: Sunday, November 1, 2026, at 3:30 PM UTC

Title: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: This event is a continuation of DZ1513805 that was thought to be resolved when we implemented a code fix to correct an issue in which the same identities were retriggering and causing prompts with outdated or repeated recommendations in Microsoft Defender for Identity. We've identified that our fix didn't cover all scenarios and impact continues to occur in some instances. We've fine-tuned our fix to cover all impact scenarios and are deploying it to the affected environment. We expect this fix will complete and remediate impact by our next scheduled update.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Root cause: A code issue is retriggering the same identities, resulting in impact.

Next update by: Thursday, October 29, 2026, at 9:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: Following additional validation, we've determined that the fix hasn't completed deployment across all impacted environments as previously indicated. We're continuing the deployment and monitoring its progress to establish an updated completion timeline.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Friday, November 13, 2026, at 10:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've received reports from a subset of affected users that impact persists. We're continuing our investigation into the newly provided HTTP Archive format (HAR) trace logs to help identify why impact persists.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Friday, October 30, 2026, at 9:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’ve confirmed that the fix is fully deployed across all impacted environments. We’re reaching out to a number of affected users to confirm that the issue is successfully resolved.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Friday, October 30, 2026, at 6:30 AM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: The aforementioned fix is showing positive results and we’re continuing our efforts to develop a remediation timeline and expect that one will be provided by our next scheduled communications update.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, October 28, 2026, at 3:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've verified and developed a second fix to address the issue with opening the Copilot Analyst or Researcher from the Unified store accessed through Outlook, which is now beginning its deployment alongside the previous fix to the opening the Copilot Analyst or Researcher in the Microsoft 365 app store. We're monitoring the deployment of both fixes and we'll share a more accurate timeline for completion once one becomes available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, October 28, 2026, at 2:00 AM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've identified a fix for the opening the Copilot Analyst or Researcher in the Microsoft 365 app store and we expect it will complete deployment sometime in mid November. We'll provide a more accurate timeline for this if it becomes available. In parallel, we're continuing to review the additional diagnostic data to identify a fix for opening the Copilot Analyst or Researcher from the Unified store accessed through Outlook .

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Thursday, October 22, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’ve gathered additional diagnostic data through our internal reproduction of the issue and are reviewing our findings to further isolate the underlying cause and determine appropriate remediation actions. We’ll provide a resolution timeline once available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, October 21, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’re continuing our internal reproduction efforts to collect additional diagnostic data and further isolate why the impact persists in specific environments to formulate the appropriate remediation action.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, October 14, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’re continuing our efforts to reproduce the impact internally to gather additional diagnostic data to aid our ongoing investigation into why the impact is persisting in specific environments and formulate an appropriate remediation action.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, October 7, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: The process of collecting an internal reproduction of impact is taking longer than anticipated, but we're actively pursuing this reproduction in order to assist our ongoing investigation into why this impact is persisting in specific environments.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 30, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: The process of collecting an internal reproduction of impact is taking longer than anticipated, but we're actively pursuing this reproduction in order to assist our ongoing investigation into why this impact is persisting in specific environments.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 30, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're progressing with our internal reproduction of the impact within our internal testing environment. This data is expected to provide further clarity on the impact scenario and identify our next troubleshooting steps for remediating the impact.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 23, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: Based on our internal testing, we've determined that the impact is still occurring. We're continuing to reproduce the impact using our internal testing environment to provide us further clarity on the impact scenario, so that we can develop our next mitigation strategy.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Monday, September 21, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're continuing to reach out to impacted users to confirm if impact is remediated after the deployment of our fix.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Thursday, September 17, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've created and deployed the fix and we're confirming with impacted users if the issue is resolved.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 16, 2026, at 9:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’re continuing our efforts to develop and evaluate a fix for the Unified store accessed through Outlook. We’ll provide a resolution timeline once available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 16, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're continuing to develop and evaluate a fix for the Unified store accessed through Outlook, and we aim to provide a timeline for when fix development will be completed as soon as possible.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.

Next update by: Tuesday, September 15, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've updated the More Info, Scope of impact, and Root cause sections as the impact may also occur within the Unified store accessed through Outlook. We've deployed a permanent fix for the Microsoft 365 app store, and our internal testing has confirmed the impact is no longer occurring in this scenario. We're developing a fix for the Unified store accessed through Outlook, and we'll aim to provide a timeline for these fixes to deploy by our next scheduled communications update.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store, or Unified store accessed through Outlook contains the incorrect URL redirection and is causing impact.

Next update by: Monday, September 14, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're continuing to validate and evaluate the effectiveness of our permanent fix prior to initiating deployment to affected users. We recommend users continue to utilize the Copilot agent store while we troubleshoot our remediation steps, and we’ll provide an updated timeline as soon as one becomes available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Wednesday, September 9, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: After further review, we've determined that our permanent fix for this issue needs to undergo additional validations, meaning it will take longer than originally project to fully resolve this event. We recommend users continue to utilize the Copilot agent store while we troubleshoot our remediation steps, and we will provide an updated timeline as soon as one becomes available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Tuesday, September 8, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: Our projection for deployment completion, based on the rate of progress, indicates that the process will be nearing completion by the end of August, but may require additional time to fully saturate. We're continuously monitoring the deployment and will provide an updated timeline for remediation as one becomes available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Start time: Thursday, July 9, 2026, at 5:33 PM UTC

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Monday, August 31, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’ve developed and validated the fix to correct the URL redirection and have initiated deployment to the affected environments. Based on our current estimates, we suspect that the deployment will take several weeks to complete, with completion expected by Monday, August 31, 2026. We’re continuing to monitor the progress of the deployment and will provide progress updates as they become available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Wednesday, August 19, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We’re continuing to develop a fix to correct the URL redirection, and we’ll provide a resolution timeline once available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We've identified that the "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact. We're developing a fix to correct the URL redirection and will provide an update on its timeline as one becomes available.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.

Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're continuing to review the details provided by a subset of affected users, including screenshots of the impact, so that we can investigate the source of the impact.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.

More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.

Current status: We're reviewing the screenshots provided by a subset of affected users to gain further understanding of the impact and to determine the next steps to isolate the root cause.

Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.

Next update by: Tuesday, August 4, 2026, at 4:30 PM UTC

Title: We're looking into a potential problem impacting Microsoft 365 Copilot

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have seen refresh delays.

More info: Admins may have seen delays for the following usage reports:

The last updated date for these reports may have been October 18th, 2026, or later depending on the report.

Final status: Following the successful deployment of our fix, our internal service telemetry has verified that the offending upstream pipeline issues have been addressed, and that the impact has been remediated.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may have been impacted and saw delayed reporting information.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

End time: Thursday, October 29, 2026, at 5:47 PM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center was causing reporting delays.

Next steps:

This is the final update for the event.

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: Our fix to address the remaining delays for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports has nearly completed and much of the usage reports are now up-to-date. We expect this will complete by our next scheduled update and completely remediate impact.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Thursday, October 29, 2026, at 11:30 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: Our fix to address the remaining delays for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports is taking longer to complete than anticipated. We'll continue to closely monitor this deployment and provide an updated remediation timeline as soon as one is available.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Thursday, October 29, 2026, at 6:30 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: Our fix to address the remaining delays for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports is taking longer to complete than anticipated. We'll continue to closely monitor this deployment and provide an updated remediation timeline as soon as one is available.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Thursday, October 29, 2026, at 6:30 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: Our fix to address the remaining delays for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports is taking longer to complete than anticipated. We'll continue to closely monitor this deployment and provide an updated remediation timeline as soon as one is available.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Thursday, October 29, 2026, at 6:30 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: Our telemetry has validated that usage reports for Email Apps has caught up and are no longer experiencing refresh delays. We're continuing to apply our remediation action to the upstream data pipeline for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports, and our remediation timeline expects them to have completed by our next scheduled communication update.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Thursday, October 29, 2026, at 2:00 AM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: We've completed the remediation action in the upstream data pipeline for the Microsoft 365 Apps Usage and Active Users reports, and the reporting data is catching up. However, the Exchange Email, Mailbox, and Email Apps reports remain impacted. We're continuing to work on applying the same remediation action in the upstream data pipeline to the remaining affected reports. We'll provide a remediation timeline once available.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Wednesday, October 28, 2026, at 6:00 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: We’re continuing to work with our upstream data provider to apply a remediation action and resolve the reporting delay.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Tuesday, October 27, 2026, at 4:00 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: We've identified through our service-side telemetry that the reporting data as identified in the "More info" section of this communication are delayed. We're applying a remediation action through working with our upstream data provider to correct this delay.

Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

Next update by: Monday, October 26, 2026, at 4:00 PM UTC

Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

More info: This includes the following usage reports:

The last updated date for these reports may be October 18th, 2026, or later depending on the report.

Current status: We're investigating a potential issue with Microsoft 365 suite and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not have been able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may have been presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option was no longer available after encountering the error. Users could have selected "Save as" to download the file and then open the attachment to bypass the impact.

Final status: We've completed deployment of our targeted fix to disable the impacting configuration and confirmed with a subset of affected users that the impact is remediated as a result. Any users still impacted will need to close and reopen new Outlook for the change to take effect and resolve the issue.

Scope of impact: This issue may have affected new Outlook desktop users who had upgraded to Edge version 156 and were attempting to open email file attachments or see the "Open" option in the new Outlook desktop app.

Start time: Friday, October 23, 2026, at 12:00 AM UTC

End time: Thursday, October 29, 2026, at 12:00 PM UTC

Root cause: A recent update to Edge Version 156 unintentionally enabled an unnecessary configuration change and caused impact.

Next steps:

This is the final update for the event.

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We’ve determined that a recent update to Edge Version 156 unintentionally enabled an unnecessary configuration, resulting in impact. We’ve developed and deployed a targeted fix to disable this configuration, which may take up to 12 hours to propagate across our service infrastructure. We’ll use service telemetry to confirm the fix has been applied across the infrastructure. Once confirmed, users will need to close and reopen New Outlook for the change to take effect and resolve the issue.

Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156. This section may be updated as our investigation continues.

Root cause: A recent update to Edge Version 156 unintentionally enabled an unnecessary configuration change and is resulting in impact.

Next update by: Thursday, October 29, 2026, at 8:30 PM UTC

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We're continuing to work on validating our root cause hypothesis and once completed, we'll determine our next steps towards remediation.

Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156. This section may be updated as our investigation continues.

Next update by: Wednesday, October 28, 2026, at 1:30 AM UTC

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We're narrowing down a potential root cause that is related to a recent service-side update. We're in the process of validating this hypothesis and once confirmed will help us determine our remediation options.

Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156.

Next update by: Wednesday, October 28, 2026, at 11:30 PM UTC

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We're continuing our investigation into this issue, reviewing the information provided in specific support cases as well as our own service-side reproductions of this issue in order determine the best approach for troubleshooting this issue.

Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156.

Next update by: Wednesday, October 28, 2026, at 9:30 PM UTC

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We're reviewing user reports of impact and data collected from an internal reproduction of the problem to determine what's leading to this behavior, as well as our approach to addressing the impact.

Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156.

Next update by: Wednesday, October 28, 2026, at 7:30 PM UTC

Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app

User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app.

More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact.

Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 60 minutes.

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may have been unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online.

More info: When users attempted to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may have received an error that stated, “We couldn't verify your license.”

Final status: We've confirmed the deployment of the fix to address the missing configuration has completed and validated with a subset of affected users that this has remediated the impact.

Scope of impact: Any user who attempted to create SharePoint knowledge agents using Copilot in SharePoint Online may have been affected.

Start time: Thursday, October 8, 2026, at 4:31 AM UTC

End time: Wednesday, October 28, 2026, at 9:38 PM UTC

Root cause: A recent service change had a missing configuration that prevented the licensing from being fetched and validated, which resulted in the impact.

Next steps:

This is the final update for the event.

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: Our monitoring of the rate of the deployment is ongoing and we're observing continued progress. We'll confirm a timeline for remediation as one becomes available.

Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues.

Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact.

Next update by: Thursday, October 29, 2026, at 7:00 PM UTC

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: We're continuing to monitor the rate of the deployment's progression through the impacted environment in an effort to establish a timeline for remediation. We'll aim to provide an update on this when possible.

Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues.

Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact.

Next update by: Wednesday, October 28, 2026, at 7:00 PM UTC

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: We're deploying our fix to correct the misconfiguration that's preventing the licensing from being fetched and validated and we'll provide a timeline for the completion of the deployment as one becomes available.

Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues.

Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact.

Next update by: Thursday, October 22, 2026, at 7:00 PM UTC

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: We've identified that a recent service change had a missing configuration that's preventing the licensing from being fetched and validated. We're developing a fix to add the missing configuration and remediate the impact.

Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues.

Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact.

Next update by: Friday, October 16, 2026, at 8:00 PM UTC

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agents using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: We're reviewing the HTTP Archive format (HAR) logs provided by a subset of affected users to isolate the source of the error and determine the reason users can't create SharePoint knowledge agents.

Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 5:30 PM UTC

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online

User impact: Users may be unable to create SharePoint knowledge agents using Copilot in SharePoint Online.

More info: When users attempt to create a SharePoint knowledge agents using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.”

Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may have seen multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not have been viewable.

The following usage reports may not have shown data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Final status: Our deployment of the fix to correct the upstream process inefficiency has completed, and we've confirmed after monitoring service telemetry that the remaining reports have been recovered, and the issue has been remediated.

Scope of impact: Some admins may not have seen updated usage reports in the Microsoft 365 admin center with varying delays.

Start time: Sunday, August 30, 2026, at 12:00 AM UTC

End time: Wednesday, October 28, 2026, at 12:00 AM UTC

Root cause: An upstream process responsible for managing user data was unable to process data as effectively as expected, which led to delays populating user reports.

Next steps:

This is the final update for the event.

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: We're proceeding with monitoring the progress of our fix deployment. In parallel, we're continuing to implement optimizations to speed up the processing and expedite the remediation.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Wednesday, October 28, 2026, at 8:30 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: While we continue to monitor the progress of our fix deployment, we're implementing optimizations to speed up the processing and expedite the remediation.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Tuesday, October 27, 2026, at 4:00 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: Our fix deployment is ongoing but is taking longer than expected due to the complexity of the issue and system limitations on data request volume. We're continuing to monitor the deployment's progress and expect to provide a completion timeline by our next scheduled update.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Friday, October 23, 2026, at 11:00 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: We've confirmed that the aforementioned fix deployment is ongoing and progressing as expected. We’re completing the remaining data operations necessary to restore service for affected users and expect to provide a completion timeline by our next scheduled update.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Friday, October 23, 2026, at 2:30 AM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: We're determined that an infrastructure migration is producing corrupt file formatting and delaying our upstream data processing for the remaining affected reports. We've validated that the corrupt file formatting doesn't affect the data output from these reports, and we're deploying our pre-discussed fix to remove the infrastructure mitigation and return expected data to the remaining affected reports.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Thursday, October 22, 2026, at 4:00 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: Our telemetry shows that some reporting data is now flowing as expected; however, admins may continue to encounter issues until the fix is released. We're continuing our development and validation of a fix and will provide a release timeline once available.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Wednesday, October 21, 2026, at 8:30 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

-Microsoft 365 Apps Active Users reports

-Overview reports

-Forms reports

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: Our enablement of the optimizations to resolve the delayed Microsoft 365 Apps Active Users reports, Overview, and Forms reports is still ongoing, and we'll provide a timeline for the completion of our resolution as one becomes available.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Monday, October 19, 2026, at 8:30 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

-Microsoft 365 Apps Active Users reports

-Overview reports

-Forms reports

The following usage reports have recovered as of October 12, 2026:

The following usage reports have recovered as of October 15, 2026:

Current status: After our optimizations addressed the delays for Mailbox usage, Microsoft Teams User activity, and Microsoft 365 Group activity reports, we've determined that our pipeline is also producing delays for Microsoft 365 Apps Active Users reports, Overview, and Forms reports. We're enabling the same optimizations to affected users which we're expecting to remediate the impact.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Friday, October 16, 2026, at 8:30 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

Current status: We've identified that additional server-side optimizations are needed to fully remediate the impact. We're applying these optimizations to the remaining affected users and continuing to monitor the affected report types to validate full recovery.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Thursday, October 15, 2026, at 8:30 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

Current status: We've completed our additional service-side optimizations and received some reports from impacted users that this issue has been remediated. We're continuing to monitor the final impacted report types to validate recovery.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Wednesday, October 14, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage reports may not show data since October 6, 2026:

The following usage reports have recovered as of October 12, 2026:

Current status: We've updated the "More info" section to reflect the current processing delays for the impacted report types. While we've remediated the issues which led to the majority of delays across the listed report types, we're completing additional optimization to ensure that the data reporting delays for the remaining three report types recover as quickly and efficiently as possible.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Tuesday, October 13, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

More info: The following usage reports may not show data since October 5, 2026:

The following usage reports may not show data since October 4, 2026:

Current status: We've updated the More info section of this communication to indicate that a portion of some of the reports with stale data since October 3, 2026 now include data through October 5, 2026. We'll continue to update that portion of our messaging while the remediation actions progress through the backlog of data ingestion. need to monitor in order to provide a better timeline for remediation is taking longer than expected. We continue to monitor as the backlog of data processes. We anticipate that a better timeline will be available with our next communication.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Monday, October 12, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: The following usage report types may show data from prior to October 3, 2026:

The following usage reports have recovered as of October 8, 2026, and show data up to October 4, 2026:

Current status: We've enabled our long-term fix, but we're continuing our monitoring of service health as the backlog processes to ensure that this fully remediates the issue. We anticipate that our monitoring will also help us provide more information on our timeline by our next scheduled communications update,

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.

Next update by: Friday, October 9, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types may show delays after October 3, 2026:

Current status: While our efforts to enable our long-term fix are ongoing, we're continuing to rebalance service traffic to provide an interim improvement to data freshness for impacted users.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Thursday, October 8, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types may have been delayed since September 29, 2026:

Current status: Following our traffic optimizations to the affected subset of service infrastructure, we're monitoring their recovery and the reduction of data reporting delays. We're expecting clarity into our mitigation timeline by our next scheduled communication update.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Wednesday, October 7, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types may have been delayed since September 29, 2026:

Current status: We've continued to observe significant recovery in data reporting delays for the impacted report types. However, our monitoring of service health telemetry has allowed us to identify a portion of service infrastructure that is underperforming and which is resulting in continued impact. We're analyzing our next steps so that we can develop a timeline for full remediation.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Tuesday, October 6, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

As of Friday, October 2, 2026, the following usage report types are no longer delayed:

-Teams Activity reports

As of Wednesday, September 23, 2026, the following usage report types are no longer delayed:

As of Sunday, September 20, 2026, the following usage report types are no longer delayed:

-Adoption Score reports

More info: As of Friday, October 2, 2026, the following usage report types are no longer delayed:

As of Wednesday, September 23, 2026, the following usage report types are no longer delayed:

As of Sunday, September 20, 2026, the following usage report types are no longer delayed:

Current status: We've verified that a significant portion of the scenarios listed in the "More info" section have recovered. We're continuing to monitor the remaining impacted report types, which we anticipate will recover by the time of our next scheduled communications update on Monday, October 5, 2026.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Monday, October 5, 2026, at 9:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types are delayed since September 19, 2026:

- Microsoft Teams usage reports

- Microsoft 365 Group Activity reports

- Mailbox usage reports

The following report types are delayed since September 23, 2026:

- Email Activity reports

- Email Apps usage reports

- Active User reports

- Copilot Readiness reports

- Microsoft 365 Apps usage reports

Current status: While our investigation into the combination of issues that are resulting in impact is ongoing, we're continuing to monitor as additional reporting is generated and made available to admins. Most scenarios are showing improvement, and we'll provide a complete remediation timeline once available.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Friday, October 2, 2026, at 7:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types are delayed since September 19, 2026:

- Microsoft Teams usage reports

- Microsoft 265 Group Activity reports

- Mailbox usage reports

The following report types are delayed since September 23, 2026:

- Email Activity reports

- Email Apps usage reports

- Active User reports

- Copilot Readiness reports

- Microsoft 365 Apps usage reports

Current status: We've identified that there are multiple issues impacting different groups of usage report types in the Microsoft 365 admin center. We're working to isolate all underlying causes of impact, and at this time, we're aware of a code issue occurring within an upstream dependency service that's causing impact to a portion of the affected reports. While we work to confirm which reports are affected by the upstream code issue, we've successfully implemented mitigation and restored Email Activity reports, Email Apps usage reports, and Active User reports to expected functionality. Our investigation is still ongoing to identify what caused these three reports to be impacted, and which other reports are facing a similar issue where this mitigation strategy can be implemented.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Thursday, October 1, 2026, at 8:00 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types are delayed since September 19, 2026:

- Microsoft Teams usage reports

- Microsoft 365 Group Activity reports

- Mailbox usage reports

The following report types are delayed since September 23, 2026:

- Email Activity reports

- Email Apps usage reports

- Active User reports

- Copilot Readiness reports

- Microsoft 365 Apps usage reports

Current status: Our investigation into the underlying cause is ongoing, while in parallel looking into methods to improve reporting throughput.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Wednesday, September 30, 2026, at 5:30 PM UTC

Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center

User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.

More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

The following usage report types are delayed since September 19, 2026:

- Microsoft Teams usage reports

- Microsoft 365 Group Activity reports

- Mailbox usage reports

The following report types are delayed since September 23, 2026:

- Email Activity reports

- Email Apps usage reports

- Active User reports

- Copilot Readiness reports

- Microsoft 365 Apps usage reports

Current status: After further review, we've validated that more tenants are impacted than initially diagnosed, and we've expanded communications to all potentially affected tenants. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change and we've outlined the delayed usage report types in the "More info" section of this communication. We're analyzing delayed report types to isolated potential discrepancies and to determine our next troubleshooting steps.

Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

Next update by: Tuesday, September 29, 2026, at 11:00 PM UTC

Title: Admins see Microsoft Teams usage reports not being updated since September 1, 2026, in the Microsoft 365 admin center

User impact: Admins see Microsoft Teams usage reports not being updated since September 1, 2026, in the Microsoft 365 admin center.

Current status: We've received reports from your representatives that the impact scenario documented in MO1476333 is still ongoing. We're reviewing the latest reports of impact to further our understanding of the current impact scenario and to determine our next troubleshooting steps.

Scope of impact: Your organization is affected by this event, and your admins don’t see updated Microsoft Teams usage reports in the Microsoft 365 admin center since September 1, 2026. This section may be updated as the investigation progresses.

Next update by: Tuesday, September 29, 2026, at 5:00 PM UTC

Title: Some users may be unable to see or select Claude models in the Microsoft 365 Copilot Chat model picker

User impact: Users may have been unable to see or select Claude models in the Copilot Chat model picker.

Final status: We've received reports from some affected users that the issue is no longer occurring. No service side remediation actions were taken and we've not identified a service issue that would have led to this impact. If the problem should reoccur, please reach out to a support resource with relevant logs and we'll resume our investigation.

Scope of impact: Some users were unable to leverage Claude models in Copilot Chat.

This is the final update for the event.

Title: Some users may be unable to see or select Claude models in the Microsoft 365 Copilot Chat model picker

User impact: Users may be unable to see or select Claude models in the Copilot Chat model picker.

Current status: We're investigating a potential issue with licensed users being unable to see or select Claude models in the Copilot Chat model picker and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Some admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal

User impact: Admins may have seen Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal.

Final status: Following the deployment of our fix, our internal service telemetry verified that the connectivity problems had been addressed, and that the impact had been remediated.

Scope of impact: Some admins saw their Microsoft Teams Rooms devices marked as offline or unmonitored in the Pro Management portal.

Start time: Tuesday, October 13, 2026, at 4:08 PM UTC

End time: Tuesday, October 27, 2026, at 7:00 PM UTC

Root cause: A recent service migration introduced connectivity issues between affected Microsoft Teams Rooms devices and the internet, resulting in devices showing as unmonitored or offline in the Pro Management portal.

Next steps:

This is the final update for the event.

Title: Some admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal

User impact: Admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal.

Current status: The deployment of the fix has now fully completed. We're reaching out to some affected admins confirm the effectiveness of the fix.

Scope of impact: Some admins may see their Microsoft Teams Rooms devices marked as offline or unmonitored in the Pro Management portal. This section may be updated as the investigation progresses.

Root cause: A recent service migration introduced connectivity issues between affected Microsoft Teams Rooms devices and the internet, resulting in devices showing as unmonitored or offline in the Pro Management portal.

Next update by: Tuesday, October 27, 2026, at 11:00 PM UTC

Title: Some admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal

User impact: Admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal.

Current status: After analyzing device logs from an affected Microsoft Teams Rooms device, we have isolated that impact is caused by a recent service migration which introduced connectivity issues between affected Microsoft Teams Rooms devices and the internet, resulting in devices showing as unmonitored or offline in the Pro Management portal. We're developing a code fix to resolve the connectivity issues, and we aim to provide a timeline for its deployment in our next scheduled communication update.

Scope of impact: Some admins may see their Microsoft Teams Rooms devices marked as offline or unmonitored in the Pro Management portal. This section may be updated as the investigation progresses.

Root cause: A recent service migration introduced connectivity issues between affected Microsoft Teams Rooms devices and the internet, resulting in devices showing as unmonitored or offline in the Pro Management portal.

Next update by: Monday, October 26, 2026, at 11:00 PM UTC

Title: Some admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal

User impact: Admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal.

Current status: After further analysis, we've isolated that impact isn’t limited to Microsoft Teams Rooms on Windows devices and any Microsoft Teams Rooms device could be affected for users operating in a specific service environment. We’ve updated the "Title" and "User impact" field of communications to reflect this updated impact scenario. We're analyzing device logs from affected Microsoft Teams Rooms devices to isolate potential discrepancies leading to impact.

Scope of impact: Some admins may see their Microsoft Teams Rooms devices marked as offline or unmonitored in the Pro Management portal. This section may be updated as the investigation progresses.

Next update by: Monday, October 26, 2026, at 5:00 PM UTC

Title: Some admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal

User impact: Admins may see Microsoft Teams rooms devices marked as offline or unmonitored in the Pro Management portal.

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.

Title: Admins' audit logs for AI interactions in the Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not have included Copilot web chats.

Final status: We've completed deployment of our fix to reverse the impacting service change and confirmed through internal testing that the impact is remediated as a result.

Scope of impact: This issue may have impacted admins attempting to audit AI interactions in the Purview portal.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

End time: Tuesday, October 27, 2026, at 7:55 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, which resulted in these logs incorrectly showing as non-web search in Microsoft Purview.

Next steps:

This is the final update for the event.

Title: Admins' audit logs for AI interactions in the Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've bypassed the blockages and have resumed deployment to the remaining impacted users. We'll provide a timeline for the completion of the deployment as one becomes available.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Wednesday, October 28, 2026, at 1:30 AM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The majority of users have received the fix; however, we've encountered a blockage that's preventing the fix from completing deployment for the last remaining affected users. While we explore options to bypass this blockage and resume the deployment, we're checking with a subset of users that have received the fix to confirm that it remediates the impact as expected.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Tuesday, October 27, 2026, at 8:00 PM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The fix has deployed to the majority of the affected environment and we're monitoring the process to confirm it completes by our next scheduled communications update on Tuesday, October 27.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Tuesday, October 27, 2026, at 6:00 PM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We're continuing to validate the efficacy of our configuration changes, and we'll provide a timeline for the completion of our validations as one becomes available.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Friday, October 23, 2026, at 8:00 PM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The validation process for the configuration changes we believe will remediate the issue continues as we closely follow proper implementation procedures.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Monday, October 19, 2026, at 7:00 PM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've developed our two code changes required to reinstate the affected component. We're completing our validation process to ensure their efficacy,

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Saturday, October 17, 2026, at 2:30 AM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We're continuing our work to revert this change. We've developed one portion of the required change and are finalizing the details of its counterpart which will allow us to ensure a thorough resolution.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Saturday, October 17, 2026, at 12:30 AM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've identified a recent code change which was intended to streamline client-side code that caused Copilot web chat logging to not work as expected when enabled in Copilot chat mode but disabled in Copilot work mode. We're reverting this change and are monitoring progress.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Friday, October 16, 2026, at 10:30 PM UTC

Title: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've identified a recent change made to audit log searches which may be contributing to this impact. We're continuing to investigate to verify our observations.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 8:30 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats.

Current status: We're investigating the information we've received from some affected admins to determine our next steps.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 6:30 PM UTC

Title: We're looking into a potential problem impacting Microsoft 365 Copilot

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not have included Copilot web chats.

Final status: We've completed deployment of our fix to reverse the impacting service change and confirmed through internal testing that the impact is remediated as a result.

Scope of impact: This issue may have impacted admins attempting to audit AI interactions in the Purview portal.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

End time: Tuesday, October 27, 2026, at 7:55 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, which resulted in these logs incorrectly showing as non-web search in Microsoft Purview.

Next steps:

This is the final update for the event.

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've bypassed the blockages and have resumed deployment to the remaining impacted users. We'll provide a timeline for the completion of the deployment as one becomes available.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Wednesday, October 28, 2026, at 1:30 AM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The majority of users have received the fix; however, we've encountered a blockage that's preventing the fix from completing deployment for the last remaining affected users. While we explore options to bypass this blockage and resume the deployment, we're checking with a subset of users that have received the fix to confirm that it remediates the impact as expected.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Tuesday, October 27, 2026, at 8:00 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The fix has deployed to the majority of the affected environment and we're monitoring the process to confirm it completes by our next scheduled communications update on Tuesday, October 27.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Tuesday, October 27, 2026, at 6:00 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We're continuing to validate the efficacy of our configuration changes, and we'll provide a timeline for the completion of our validations as one becomes available.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Friday, October 23, 2026, at 8:00 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: The validation process for the configuration changes we believe will remediate the issue continues as we closely follow proper implementation procedures.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Monday, October 19, 2026, at 7:00 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've developed our two code changes required to reinstate the affected component. We're completing our validation process to ensure their efficacy,

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Saturday, October 17, 2026, at 2:30 AM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We're continuing our work to revert this change. We've developed one portion of the required change and are finalizing the details of its counterpart which will allow us to ensure a thorough resolution.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Start time: Monday, August 10, 2026, at 5:35 PM UTC

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Saturday, October 17, 2026, at 12:30 AM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've identified a recent code change which was intended to streamline client-side code that caused Copilot web chat logging to not work as expected when enabled in Copilot chat mode but disabled in Copilot work mode. We're reverting this change and are monitoring progress.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Root cause: A recent change intended to streamline client-side code removed a component used to facilitate Copilot web chat logging, resulting in these logs incorrectly showing as non-web search in Microsoft Purview.

Next update by: Friday, October 16, 2026, at 10:30 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Purview portal may not include Copilot web chats.

Current status: We've identified a recent change made to audit log searches which may be contributing to this impact. We're continuing to investigate to verify our observations.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 8:30 PM UTC

Title: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Microsoft 365 Copilot web chats

User impact: Admins' audit logs for AI interactions in the Microsoft Purview portal may not include Copilot web chats.

Current status: We're investigating the information we've received from some affected admins to determine our next steps.

Scope of impact: This issue may impact admins attempting to audit AI interactions in the Purview portal. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 6:30 PM UTC

Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal

User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.

Final status: We've confirmed through monitoring service health telemetry that reverting the upgrade we identified as the source of this issue effectively resolved the impact, and that all delayed data is now available to admins in the Defender and Sentinel portals.

Scope of impact: This issue impacted admins, who may have seen delays in Endpoint alerts and telemetry reported through the Microsoft 365 Defender portal and the Microsoft Azure Sentinel portal.

Start time: Monday, October 26, 2026, at 9:00 PM UTC

End time: Tuesday, October 27, 2026, at 12:47 AM UTC

Root cause: A recent upgrade intended to reinforce service functionality introduced a code conflict which resulted in data processing delays for Endpoint alerts and telemetry.

Next steps:

This is the final update for the event.

Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal

User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.

Current status: We're continuing our reversion of the impacting change while we confirm its effectiveness through monitoring service health telemetry.

Scope of impact: This issue impacts admins, who may see delays in Endpoint alerts and telemetry reported through the Microsoft 365 Defender portal and the Microsoft Azure Sentinel portal. This information may be updated as our investigation continues.

Start time: Monday, October 26, 2026, at 9:00 PM UTC

Root cause: A recent upgrade intended to reinforce service functionality introduced a code conflict which is resulting in data processing delays for Endpoint alerts and telemetry.

Next update by: Tuesday, October 27, 2026, at 2:30 AM UTC

Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal

User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.

Current status: We've identified a recent upgrade intended to reinforce service functionality introduced a code conflict, which is leading to data processing delays. We're reverting to the last known good build while continuing our analysis to ensure that our intended remediation can be effectively applied for all impacted admins.

Scope of impact: This issue impacts admins, who may see delays in Endpoint alerts and telemetry reported through the Microsoft 365 Defender portal and the Microsoft Azure Sentinel portal. This information may be updated as our investigation continues.

Start time: Monday, October 26, 2026, at 9:00 PM UTC

Root cause: A recent upgrade intended to reinforce service functionality introduced a code conflict which is resulting in data processing delays for Endpoint alerts and telemetry.

Next update by: Tuesday, October 27, 2026, at 12:30 AM UTC

Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal

User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.

Current status: We're investigating a potential issue with telemetry and alerting delays for Microsoft Defender for Endpoint and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may not receive notifications when added to or removed from tags in Microsoft Teams

User impact: Users may have not received notifications when added to or removed from tags in Microsoft Teams.

More info: This event may have also impacted notifications surrounding tag creation, deletion, or restoration.

This only impacted notifications and tag operations still succeed as expected.

Final status: Our fix has completed its deployment, and we've confirmed through service health telemetry that this has successfully resolved the event.

Scope of impact: This event may have impacted any user, and any user may have not received notifications when added to or removed from tags in Microsoft Teams.

Start time: Thursday, September 24, 2026, at 9:19 AM UTC

End time: Friday, October 23, 2026, at 1:00 AM UTC

Root cause: A recent update to the authentication flow contained an issue that resulted in impact to tag notifications.

Next steps: - We're reviewing the responsible update 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.

Title: Users may not receive notifications when added to or removed from tags in Microsoft Teams

User impact: Users may not receive notifications when added to or removed from tags in Microsoft Teams.

More info: This event may also impact notifications surrounding tag creation, deletion, or restoration.

This only impact notifications and tag operations still succeed as expected.

Current status: We've developed a forward fix and validated it in our internal testing environments. We're now deploying this fix to all affected regions and monitoring the progress to ensure impact is fully resolved as expected.

Scope of impact: This event may impact any user, and any user may not receive notifications when added to or removed from tags in Microsoft Teams. This information may be updated as our investigation continues.

Start time: Thursday, September 24, 2026, at 9:19 AM UTC

Root cause: A recent update to the authentication flow that contained the issue resulting in impact.

Next update by: Monday, October 26, 2026, at 8:30 PM UTC

Title: Users may not receive notifications when added to or removed from tags in Microsoft Teams

User impact: Users may not receive notifications when added to or removed from tags in Microsoft Teams.

More info: This event may also impact notifications surrounding tag creation, deletion, or restoration.

This only impact notifications and tag operations still succeed as expected.

Current status: We're continuing our validation of a fix and will provide a remediation timeline once available.

Scope of impact: This event may impact any user, and any user may not receive notifications when added to or removed from tags in Microsoft Teams. This information may be updated as our investigation continues.

Start time: Thursday, September 24, 2026, at 9:19 AM UTC

Root cause: A recent update to the authentication flow that contained the issue resulting in impact.

Next update by: Thursday, October 22, 2026, at 8:30 PM UTC

Title: Users may not receive notifications when added to or removed from tags in Microsoft Teams

User impact: Users may not receive notifications when added to or removed from tags in Microsoft Teams.

More info: This event may also impact notifications surrounding tag creation, deletion, or restoration.

This only impact notifications and tag operations still succeed as expected.

Current status: We identified a recent update to the authentication flow that contained the issue resulting in impact. We're validating a fix to resolve this issue and will provide a remediation timeline as soon as one becomes available.

Scope of impact: This event may impact any user, and any user may not receive notifications when added to or removed from tags in Microsoft Teams. This information may be updated as our investigation continues.

Start time: Thursday, September 24, 2026, at 9:19 AM UTC

Root cause: A recent update to the authentication flow that contained the issue resulting in impact.

Next update by: Wednesday, October 21, 2026, at 8:30 PM UTC

Title: Some users may be unable to access the group feed with Microsoft Viva Engage

User impact: Users may have been unable to access the group feed with Viva Engage.

Final status: We've completed our deployment of the fix and confirmed through service-side telemetry that the service has been restored to a healthy state.

Scope of impact: This issue was preventing any user from accessing the group feed with Microsoft Engage.

Start time: Monday, October 26, 2026, at 1:39 PM UTC

End time: Monday, October 26, 2026, at 4:23 PM UTC

Root cause: A subset of service infrastructure that helps facilitate access to the Viva Engage group feed had fallen below our manageable service performance thresholds, resulting in impact.

Next steps: We'll continue to monitor our service-side telemetry to ensure the service stays healthy and to help prevent similar events int he future.

This is the final update for this event.

Title: Some users may be unable to access the group feed with Microsoft Viva Engage

User impact: Users may be unable to access the group feed with Viva Engage.

Current status: We're working on deploying a fix to help improve the health of the service infrastructure. We'll confirm its effectiveness, once fully deployed, through monitoring the service-side telemetry.

Scope of impact: This issue is preventing any user from accessing the group feed with Microsoft Engage.

Start time: Monday, October 26, 2026, at 1:39 PM UTC

Root cause: A subset of service infrastructure that helps facilitate access to the Viva Engage group feed has fallen below our manageable service performance thresholds, resulting in impact.

Next update by: Monday, October 26, 2026, at 6:30 PM UTC

Title: Some users may be unable to access the group feed with Microsoft Viva Engage

User impact: Users may be unable to access the group feed with Viva Engage.

Current status: Our review of service-side telemetry pinpoints that a subset of service infrastructure facilitating access to the Viva Engage group feed has fallen below our manageable service performance thresholds. To better understand this issue, we’re continuing to review our service telemetry to better understand this issue and determine our next troubleshooting steps.

Scope of impact: This issue is preventing any user from accessing the group feed with Microsoft Engage.

Start time: Monday, October 26, 2026, at 1:39 PM UTC

Root cause: A subset of service infrastructure that helps facilitate access to the Viva Engage group feed has fallen below our manageable service performance thresholds, resulting in impact.

Next update by: Monday, October 26, 2026, at 4:30 PM UTC

Title: Some users may be unable to access the group feed with Microsoft Viva Engage

User impact: Users may be unable to access the group feed with Viva Engage.

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.

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not have been able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation was unaffected.

Final status: Following the deployment of our fix, our internal service telemetry has verified that the policy documents have been corrected, and that the impact has been remediated.

Scope of impact: Any admin may have been impacted by this event and unable to correctly identify non-compliant device settings as expected in Microsoft Intune.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

End time: Sunday, October 25, 2026, at 9:00 AM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next steps:

This is the final update for the event.

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: The deployment of our fix is progressing as expected and we estimate that it'll have completed and resolved this issue by our next scheduled communications update.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Sunday, October 25, 2026, at 7:00 PM UTC

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: We've observed positive trends in telemetry following the deployment of our fix, but this deployment process is methodical to ensure safe and thorough resolution. We'll provide an updated remediation timeline after a period of additional monitoring.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Saturday, October 24, 2026, at 2:00 AM UTC

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: We’ve initiated deployment of the fix and are monitoring its progress to confirm an estimated completion time once available.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Thursday, October 22, 2026, at 9:30 PM UTC

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: We've developed and validated a fix that will deploy shortly and is expected to remediate impact. We'll provide a timeline for the fix deployment if one becomes available.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Thursday, October 22, 2026, at 1:00 AM UTC

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: We're continuing our efforts to develop and validate a fix. We'll provide a release timeline once available.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Wednesday, October 21, 2026, at 9:30 PM UTC

Title: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune

User impact: Admins may not be able to identify non-compliant device settings as expected in Microsoft Intune.

More info: The device compliance calculation is unaffected.

Current status: We were alerted to an issue in Microsoft Intune from a customer report, which indicated that admins may not be able to identify the settings causing non-compliant devices. We investigated the issue and identified that a previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant. We're working on developing a fix to address the issue and once ready, we'll begin deploying to all affected environments.

Scope of impact: Any admins may be impacted by this event and may be unable to correctly identify non-compliant device settings as expected in Microsoft Intune. This section may be updated as our investigation continues.

Start time: Friday, August 7, 2026, at 7:53 PM UTC

Root cause: A previous change to the generation of unique Policy and Settings metadata identifiers caused some policy documents to be malformed, which caused some non-compliant settings to incorrectly show as compliant.

Next update by: Tuesday, October 20, 2026, at 9:30 PM UTC

Title: Users may be unable to import .XLSX files in Microsoft Viva Glint

User impact: Users were unable to import .XLSX files in Microsoft Viva Glint.

More info: Users received an error message indicating that the file was uploaded as an invalid format.

As a temporary alternative, users could have imported the impacted files in .CSV format.

Final status: We've confirmed that our reversion of the impacting change for all impacted users has ensured that Viva Glint correctly identifies .XLSX files, allowing these files to be imported as expected.

Scope of impact: Your organization was affected by this event, and users who were attempting to upload a .XLSX file to Viva Glint were impacted.

Start time: Thursday, October 22, 2026, at 12:00 PM UTC

End time: Friday, October 23, 2026, at 8:17 PM UTC

Root cause: A recent change intended to improve record count accuracy introduced a code conflict that caused .XLSX file types to be misidentified, resulting in these files not recognized and failing to upload in Viva Glint.

Next steps:

This is the final update for the event.

Title: Users are unable to import .XLSX files in Microsoft Viva Glint

User impact: Users are unable to import .XLSX files in Microsoft Viva Glint.

More info: Users receive an error message indicating that the file was uploaded as an invalid format.

As a temporary alternative, users may import the impacted files in .CSV format.

Current status: We've identified that a recent change intended to improve record count accuracy introduced a code conflict that results in files in .XLSX format not being recognized as the intended file type. We're reverting this change.

Scope of impact: Your organization is affected by this event, and users who are attempting to upload a .XLSX file to Viva Glint are impacted.

Start time: Thursday, October 22, 2026, at 12:00 PM UTC

End time: Friday, October 23, 2026, at 8:17 PM UTC

Root cause: A recent change intended to improve record count accuracy introduced a code conflict that causes .XLSX file types to be misidentified, resulting in these files not recognized and failing to upload in Viva Glint.

Next update by: Friday, October 23, 2026, at 11:30 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may have been unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API were impacted. This includes migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) were not impacted.

Final status: We’ve finished the deployment of our fix to all impacted environments and have confirmed that impact is fully resolved.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API were impacted.

Start time: Wednesday, October 21, 2026, at 9:49 AM UTC

End time: Thursday, October 22, 2026, at 5:50 PM UTC

Root cause: A configuration issue made components that facilitate migrations leveraging the MMP API unavailable, which prevented users from performing certain migrations.

Next steps:

This is the final update for the event.

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API are impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted.

Current status: We’ve completed the fix deployment to approximately 75% of our internal environment, where we are performing additional testing to ensure that no additional impact occurs. Once the internal validations are complete, we will start the deployment to the production infrastructures.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API are impacted.

Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations.

Next update by: Thursday, October 22, 2026, at 8:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted.

Current status: The fix has progressed through code validations and is being deployed to our internal environments for further testing. If the internal validations are successful, we’ll begin a broader rollout by our next scheduled update.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations.

Next update by: Thursday, October 22, 2026, at 4:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted.

Current status: We’re continuing to closely monitor service health as the deployment progresses through the validation and early deployment stages. We'll provide a resolution timeline as deployment progresses.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations.

Next update by: Thursday, October 22, 2026, at 12:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted.

Current status: We've resolved the integration issues identified during our previous validation and have started the release process for our updated build. We're progressing the fix through our deployment and validation stages, and we'll continue monitoring its health before deploying it more broadly to the affected infrastructure. We'll provide a resolution timeline as deployment progresses.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations.

Next update by: Thursday, October 22, 2026, at 8:00 AM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted.

Current status: Our internal validation checks found integration issues with the fix. We're taking steps to address those issues and ensure a comprehensive solution is included in the updated build version as intended. Once we confirm that, we'll start deploying the fix to the impacted infrastructure. We'll share an incident resolution timeline once it's available.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations.

Next update: Thursday, October 22, 2026, at 2:00 AM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) will not be impacted.

Current status: The required internal deployment steps are taking longer than anticipated as we perform final validations to ensure the efficacy of our fix. Once internal validation is complete, we’ll begin deploying the fix to the impacted infrastructure.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Next update: Wednesday, October 21, 2026, at 11:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API.

More info: Migrations that use the Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) will not be impacted.

Current status: We're continuing to perform extensive testing on the fix to ensure that it addresses the underlying issue without causing additional impact. Once the fix is validated, we'll start the deployment to the impacted infrastructure.

Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API will be impacted.

Next update: Wednesday, October 21, 2026 at 7:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations

More info: Migrations that use Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) will not be impacted.

Current status: We’ve identified a fix to address the underlying issue and are completing validation cycles to confirm that it resolves the impact without introducing additional risk. Once these checks are complete, we’ll begin deploying the fix to the affected environment. We’ll closely monitor service telemetry throughout the deployment to verify recovery and confirm that the fix is having the intended effect. We’ll provide a further update as deployment progresses.

Scope of impact: Admins attempting to migrate using Migration Manager Platform (MMP) API will be impacted.

Next update: Wednesday, October 21, 2026 at 4:00 PM UTC

Title: Users may be unable to perform migrations

User impact: Users may be unable to perform migrations

More info: Migrations that use Migration Manager Platform (MMP) API will be impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (Sharepoint Migration Tool) will not be impacted.

Current status: After reviewing telemetry data, we’ve identified the source of the issue and have narrowed our investigation to the specific conditions contributing to the impact. We’re now assessing the most effective mitigation options and determining the actions required to restore normal service as quickly and safely as possible.

Next update: Wednesday, October 21, 2026 at 1:00 PM UTC

A post-incident report has been published.

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may have experienced delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may have pasted video share links into a Teams chat or channel. This embedded the video as a playable card that could be played within the Teams client.

Final status: Our monitoring has completed and we've confirmed this issue is no longer occurring with affected users and service telemetry.

Scope of impact: Any user in the North America region may have been affected.

Start time: Thursday, September 17, 2026, at 6:29 PM UTC

End time: Thursday, September 24, 2026, at 8:30 PM UTC

Root cause: We were rolling out two updates to SharePoint Online that changed how video content is delivered when a video is opened. With these updates, the server and the video player each prepare the information that tells the player where to find the video and how to retrieve it. In the Government Community Cloud (GCC) environment, the two did this in slightly different ways, so the player received video content in a format it wasn't expecting. When this happened, the player switched to a slower loading method that still allowed videos to play, which is why some videos took up to 30 minutes to begin playing.

Next steps:

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may paste video share links into a Teams chat or channel. This will embed the video as a playable card that can be played within the Teams client.

Current status: We're continuing to monitor the environment while reaching out to affected users and validate this issue has been remediated.

Scope of impact: Any user in the North America region may be affected. This information may be updated as our investigation continues.

Root cause: A recent configuration change related to video indexing on SharePoint Online contains an error, resulting in impact.

Next update by: Friday, September 25, 2026, at 7:00 PM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may paste video share links into a Teams chat or channel. This will embed the video as a playable card that can be played within the Teams client.

Current status: We've completed disabling the two components we believe are responsible for impact and initial reports indicate that this issue has been remediated. Our telemetry is still showing some impact and we're continuing to investigate while monitoring.

Scope of impact: Any user in the North America region may be affected. This information may be updated as our investigation continues.

Root cause: A recent configuration change related to video indexing on SharePoint Online contains an error, resulting in impact.

Next update by: Thursday, September 24, 2026, at 10:00 PM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may paste video share links into a Teams chat or channel. This will embed the video as a playable card that can be played within the Teams client.

Current status: Our initial mitigation actions have proven ineffective. We've gathered additional logs from affected users and determined that a second feature flag that is related to video indexing on SharePoint Online was enabled. We've since disabled the flag and are working to confirm mitigation internally before testing with affected users.

Scope of impact: Any user in the North America region may be affected. This information may be updated as our investigation continues.

Root cause: A recent configuration change related to video indexing on SharePoint Online contains an error, resulting in impact.

Next update by: Thursday, September 24, 2026, at 8:00 PM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may paste video share links into a Teams chat or channel. This will embed the video as a playable card that can be played within the Teams client.

Current status: We're continuing to reach out for collaborative testing to verify if our intended change resolves the issue.

Scope of impact: Any user in the North America region may be affected.

Next update by: Thursday, September 24, 2026, at 6:00 PM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

More info: As a temporary alternative, impacted users may paste video share links into a Teams chat or channel. This will embed the video as a playable card that can be played within the Teams client.

Current status: We've identified and deployed a potential remediation for a portion of impacted users and are reaching out for collaborative testing to verify if our intended change resolves the issue.

Scope of impact: Any user in the North America region may be affected.

Next update by: Thursday, September 24, 2026, at 4:00 PM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

Current status: We're analyzing the behavior of the calls made between the processes responsible for managing video playback and conversion to identify the source of the issue.

Scope of impact: Any user in the North America region may be affected.

Next update by: Thursday, September 24, 2026, at 2:00 AM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

Current status: We're reviewing the console logs and HTTP Archive (HAR) trace provided by a subset of affected users to help determine our next troubleshooting steps.

Scope of impact: Any user in the North America region may be affected.

Next update by: Thursday, September 24, 2026, at 12:00 AM UTC

Title: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online

User impact: Users may experience delays of up to 30 minutes when loading videos in SharePoint Online.

Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Admins may see delayed Microsoft 365 Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center

User impact: Admins may have seen delayed Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center.

More info: The affected reports displayed complete usage data through October 18th, 2026. Usage data from October 19th, 2026, onward was delayed and became available automatically as reporting updates completed.

Final status: We’ve confirmed that the remaining data has completed processing after our fix deployment, resolving this issue.

Scope of impact: Impact may have occurred for any admin attempting to view Copilot usage and Copilot Chat usage reports in the Microsoft 365 admin center.

Start time: Wednesday, October 21, 2026, at 12:00 AM UTC

End time: Thursday, October 22, 2026, at 3:06 PM UTC

Root cause: A compatibility issue in the upstream data processing pipeline supporting Microsoft 365 Copilot usage reporting resulted in impact.

Next steps: - We're reviewing the responsible compatibility issue 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.

Title: Admins may see delayed Microsoft 365 Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center

User impact: Admins may see delayed Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center.

More info: The affected reports currently display complete usage data through October 18th, 2026. Usage data from October 19th, 2026, onward is delayed and will become available automatically as reporting updates complete.

Current status: We’ve confirmed that our fix is fully deployed and working as expected. Usage data for October 19, 2026, has been fully recovered and published. We’re monitoring the remaining data as it’s processed and expect reporting to be fully up to date by our next scheduled update.

Scope of impact: Impact may occur for any admin attempting to view Copilot usage and Copilot Chat usage reports in the Microsoft 365 admin center.

Start time: Wednesday, October 21, 2026, at 12:00 AM UTC

Root cause: A compatibility issue in the upstream data processing pipeline supporting Microsoft 365 Copilot usage reporting resulted in impact.

Next update by: Thursday, October 22, 2026, at 7:30 PM UTC

Title: Admins may see delayed Microsoft 365 Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center

User impact: Admins may see delayed Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center.

More info: The affected reports currently display complete usage data through October 18th, 2026. Usage data from October 19th, 2026, onward is delayed and will become available automatically as reporting updates complete.

Current status: Our monitoring systems have identified an issue in which admins may see delayed Microsoft 365 Copilot usage and Copilot Chat usage data in the Microsoft 365 admin center. We've identified that a compatibility issue in the upstream data processing pipeline supporting Microsoft 365 Copilot usage reporting resulted in impact. To remediate this, we've developed and deployed a code fix to all the affected environments and are monitoring the service to confirm successful remediation.

Scope of impact: Impact may occur for any admin attempting to view Copilot usage and Copilot Chat usage reports in the Microsoft 365 admin center.

Start time: Wednesday, October 21, 2026, at 12:00 AM UTC

Root cause: A compatibility issue in the upstream data processing pipeline supporting Microsoft 365 Copilot usage reporting resulted in impact.

Next update by: Thursday, October 22, 2026, at 2:00 AM UTC

Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

User impact: Admins experienced intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

More info: Admins may have intermittently received an error stating, "Failed to update Members - Response Content was Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins could use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact was specific to admins utilizing on-premises Exchange who were attempting to add or remove members from Exchange Online distribution groups.

Final status: We've completed the deployment of our fix and confirmed through monitoring service health telemetry that the impact has been remediated.

Scope of impact: This issue impacted some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

End time: Thursday, October 22, 2026, at 3:00 PM UTC

Root cause: A conflict between a configuration and a recent update was preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next steps:

This is the final update for the event.

Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Current status: We've initiated the deployment of our fix, which is ongoing and has saturated through over 50 percent of the affected environment. We're continuing to monitor its progress as it continues and anticipate it will complete, remediating impact for all users, by our next scheduled communication update.

Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next update by: Thursday, October 22, 2026, at 5:30 PM UTC

Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Current status: We've completed the validations for our fix, which we're preparing to deploy to the affected environment. We still anticipate deployment will begin by Thursday, October 15, 2026.

Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next update by: Thursday, October 15, 2026, at 5:30 PM UTC

Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Current status: Our validations are taking longer than initially anticipated as we test the effectiveness of our code fix to ensure it fully remediates impact once deployed. We anticipate beginning deployment by Friday, October 15, 2026, and we aim to provide updates on our timeline to release as we complete our validation process.

Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next update by: Thursday, October 8, 2026, at 5:30 PM UTC

Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Current status: We're deploying a code fix to our internal test environment to validate its efficacy in remediating the impact. We anticipate our validations will be completed by our next scheduled communications update, at which time we'll aim to provide a timeline for the broad deployment.

Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next update by: Thursday, October 1, 2026, at 5:30 PM UTC

Title: Some admins may experience intermittent failures adding or removing members from Exchange Online distribution groups

User impact: Admins may experience intermittent failures adding or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Current status: After reviewing reports of impact and provided diagnostic data, we've isolated that when admins are attempting to add or remove members from Exchange Online distribution groups, there's a conflict between a configuration and a recent update which is preventing admins from being able to add or remove users from distribution groups for on-premises configurations. We’re removing the problematic behavior from our code flow with a new code fix. We aim to provide a timeline for code fix deployment to be initiated by our next scheduled update.

Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Start time: Tuesday, June 9, 2026, at 9:43 PM UTC

Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Next update by: Thursday, September 24, 2026, at 5:30 PM UTC

Title: Some admins may experience intermittent failures adding or removing members from Exchange Online distribution groups

User impact: Admins may experience intermittent failures adding or removing members from Exchange Online distribution groups.

More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Current status: We've received reports from a subset of affected admins that the impact scenario documented in EX1466035 is still ongoing and additional analysis is required. We're reviewing the latest reports of impact to further our understanding and to determine our next troubleshooting steps.

Scope of impact: This issue impacts some admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Next update by: Wednesday, September 23, 2026, at 6:00 PM UTC

Title: SIP devices can't make or receive calls

User impact: Users may have been unable to make or receive calls using SIP devices.

More info: Users may have been unable to sign in to their SIP devices or encountered "Service Unavailable" errors.

Once a SIP device attempted to perform its next synchronization, the device would have disconnected. Users would have been unable to log back into those devices and therefore could not make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices was not impacted.

Final status: We received additional confirmations from previously impacted organizations that the issue is resolved, and SIP devices are performing as expected.

Scope of impact: Any user attempting to make or receive calls using SIP devices were impacted by this event.

Start time: Wednesday, October 21, 2026, at 6:00 PM UTC

End time: Thursday, October 22, 2026, at 3:30 PM UTC

Root cause: A configuration issue had impacted components that manage SIP devices, resulting in impact.

Next steps:

This is the final update for the event.

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive calls using SIP devices.

More info: Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors.

Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: We continue to monitor service recovery after the fix completed deployment. We've received confirmation from some organizations that SIP devices are now performing as expected. We're contacting other organizations for further validations.

Scope of impact: Any user attempting to make or receive calls using SIP devices are impacted by this event.

Root cause: A configuration issue has impacted components that manage SIP devices, resulting in impact.

Next update by: Thursday, October 22, 2026, at 8:00 PM UTC

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive calls using SIP devices.

More info: Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors.

Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: We've deployed a fix to the affected infrastructure and we've observed a restoration of some of the affected functionality. We're closely monitoring SIP device reconnections and calling stability while conducting additional mitigation actions to push towards a full recovery.

Scope of impact: Any user attempting to make or receive calls using SIP devices is impacted by this event.

Next update by: Thursday, October 22, 2026, at 4:00 PM UTC

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive calls using SIP devices.

More info: Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors.

Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: Our fix is progressing through validation, alongside additional measures to support a safe and stable recovery. Once validation is complete, we'll deploy the fix to the affected infrastructure to begin restoring the affected functionality.

Scope of impact: Any user attempting to make or receive calls using SIP devices is impacted by this event.

Next update by: Thursday, October 22, 2026, at 12:00 PM UTC

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive calls using SIP devices.

More info: Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors.

Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: We're continuing to validate our fix and the recovery of SIP devices within our internal environment. We're also validating additional protective measures before restoring the affected functionality. Once we've confirmed these changes are operating as expected, we'll begin our restoration actions and monitor affected SIP devices as they recover.

Scope of impact: Any user attempting to make or receive calls using SIP devices is impacted by this event.

Next update by: Thursday, October 22, 2026, at 8:00 AM UTC

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive calls using SIP devices.

More info: Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: We’re validating a fix within our internal environments and monitoring how SIP devices recover after the fix is applied. This validation is also helping us determine how long affected devices may take to return to normal functionality once the fix is applied. Once validation is complete, we’ll use the results to guide our remediation and restoration actions.

Scope of impact: Any user attempting to make or receive calls using SIP devices is impacted by this event.

Next update: Thursday, October 22, 2026, at 2:00 AM UTC

Title: SIP devices can't make or receive calls

User impact: Users may be unable to make or receive call using SIP devices.

More info: Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices.

Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted.

Current status: We’ve identified the underlying root cause and we are working on developing a fix.

Scope of impact: This issue could impact any SIP device.

Next update: Wednesday, October 21, 2026 at 11:00 PM UTC

Title: Some users may have been prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may have been prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may have been prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Final status: We've deployed the aforementioned fix and confirmed that impact is no longer occurring after a period of monitoring.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

End time: Wednesday, October 21, 2026, at 6:00 PM UTC

Root cause: A retriggering of the same identities was causing impact to occur.

Next steps:

This is the final update for the event.

Title: Some users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: We’ve determined that a retriggereing of the same identities is causing impact to occur. We've developed and are deploying a fix to resolve the issue and estimate that this should be completed by our next scheduled update.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Estimated time to resolve: Thursday, October 22, 2026

Root cause: A retriggereing of the same identities is causing impact to occur.

Next update by: Thursday, October 22, 2026, at 2:30 PM UTC

Title: Some users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: We’re assessing the results of disabling the feature and continuing to gather information to determine the root cause and whether additional mitigation steps are required. We expect to provide a resolution timeline in our next update.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Next update by: Tuesday, October 20, 2026, at 2:30 PM UTC

Title: Some users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity

User impact: Users may be prompted with outdated or repeated recommendations in Microsoft Defender for Identity.

More info: Users may be prompted repeatedly to reset their password for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity, even after completing the recommended action.

Current status: We've received reports from a subset of users who state they are receiving repeated or outdated recommendations for "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. We've disabled the feature temporarily while we evaluate the underlying root cause and to determine a timeline for when the feature can be reenabled.

Scope of impact: Some users may be prompted to reset their password with outdated or repeated "Potentially leaked credentials" recommendations in Microsoft Defender for Identity. This section may be updated as the investigation progresses.

Start time: Tuesday, September 22, 2026, at 7:20 AM UTC

Next update by: Monday, October 19, 2026, at 2:30 PM UTC

Title: We're looking into a potential problem impacting Microsoft Defender for Identity

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue with Microsoft Defender for Identity and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: The Microsoft Defender portal was not displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins were unable to see certain CVE affected products for PHP2SHELL CVEs.

Final status: We’ve addressed the unrelated issue and have successfully deployed the fix to the remaining affected environments. We’ve confirmed by monitoring service telemetry that the issue is now resolved.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API were impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

End time: Thursday, October 22, 2026, at 12:45 PM UTC

Root cause: A configuration issue resulted in some components that manage the user interface for the Microsoft Defender portal become unavailable, which caused products for some Common Vulnerabilities and Exposures (CVEs) to not be displayed.

Next steps: - We’re reviewing the affected API flow to identify improvements that could prevent similar issues from recurring.

This is the final update for the event.

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

Current status: We’ve confirmed that the environments that received the fix remains recovered. An unrelated issue has been identified that is preventing the deployment of the fix to the remaining affected environments. We’re working to resolve this so that the rollout can complete.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Thursday, October 22, 2026, at 5:00 PM UTC

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

Current status: The fix has successfully completed in almost all the impacted environments, and those that have received the fix have now recovered. We’re investigating what is preventing the fix to be applied in the remaining environments and determining the steps needed to complete mitigation.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Thursday, October 22, 2026, at 1:00 PM UTC

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

More info: The API listed below is not working when directly called and not displaying affected products as expected in the UI.

/api/vulnerabilities/{vulnerabilityId}/affectedProducts/

Some admins may see affected products for CVEs return to their portal as the fix deployment is rolled out.

Current status: We've deployed our fix to almost all of the impacted environment and can confirm impact is resolved for the vast majority of users. We expect the deployment will be completed by our next scheduled update, and we'll continue to monitor through full impact remediation.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Thursday, October 22, 2026, at 9:00 AM UTC

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

More info: The API listed below is not working when directly called and not displaying affected products as expected in the UI.

/api/vulnerabilities/{vulnerabilityId}/affectedProducts/

Some admins may see affected products for CVEs return to their portal as the fix deployment is rolled out.

Current status: We've started deploying our fix to the impacted environment and determined our deployment will require more time than originally estimated. Some admins will see impact mitigated prior to full remediation. We're monitoring the deployment and expect impact for all users to be mitigated by our next scheduled update.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Wednesday, October 21, 2026, at 5:00 AM UTC

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

More info: The API listed below is not working when directly called and not displaying affected products as expected in the UI.

/api/vulnerabilities/{vulnerabilityId}/affectedProducts/

Current status: We're completing our final validations within our internal environment, and we remain on track to remediate the issue by Thursday, October 22, 2026, at 1:00 AM UTC.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Wednesday, October 21, 2026, at 2:00 AM UTC

Title: The Microsoft Defender portal isn't displaying affected products for some Common Vulnerabilities and Exposures (CVEs)

User impact: Microsoft Defender Vulnerability Management Admins cannot see certain CVE affected products for PHP2SHELL CVEs.

More info: The API listed below is not working when directly called and not displaying affected products as expected in the UI.

/api/vulnerabilities/{vulnerabilityId}/affectedProducts/

Current status: We've determined that limitations on the values returned by the affected API resulted in this impact. We've developed a solution which we are rolling out to our internal environment, after which we will test to validate it fully remediates the issue before rolling out throughout the impacted environment. We expect we will be able to complete the validation and further rollout to resolve impact by Thursday, October 22, 2026, at 1:00 AM UTC.

Scope of impact: Admins attempting to view affected products within the UI or using the affected API are impacted.

Start time: Wednesday, October 21, 2026, at 9:00 PM UTC

Root cause: A limitation on the values returned by the API leads to the affected API not returning any results.

Next update by: Thursday, October 22, 2026, at 12:00 AM UTC

Title: Admins may be unable to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal

User impact: Admins may have been unable to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal.

More info: Additionally, users who were assigned the specific permissions role of "reviewer" were impacted.

Final status: We've reviewed our service telemetry metrics and identified that a portion of Microsoft Purview service infrastructure responsible for processing access requests to Communication Compliance policy hits encountered transient errors, which caused it to enter an unhealthy state. Our system monitoring has indicated that the service has returned to normal health with no actions taken and we've confirmed that the issue is no longer occurring.

Scope of impact: Admins and users who attempted to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal may have been affected by this event.

Start time: Wednesday, October 21, 2026, at 11:36 PM UTC

End time: Thursday, October 22, 2026, at 4:53 AM UTC

Root cause: A portion of Microsoft Purview service infrastructure responsible for processing access requests to Communication Compliance policy hits encountered transient errors, which caused it to enter an unhealthy state.

Next steps: - We’re analyzing performance data associated with the impacted Microsoft Purview service infrastructure to better understand why it was encountering transient errors and was unable to process traffic efficiently so that we can prevent impact to accessing Microsoft Purview Communication Compliance policy hits in the future.

Title: Admins may be unable to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal

User impact: Admins may be unable to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal.

More info: Additionally, users who are assigned the specific permissions role of "reviewer" are impacted.

Current status: We're reviewing our service telemetry metrics to better understand why impact may be occurring and identify our next steps towards resolving the issue.

Scope of impact: Admins and users attempting to access Microsoft Purview Communication Compliance policy hits in the Microsoft Purview portal may be affected by this event. This section may be updated as our investigation continues.

Next update by: Thursday, October 22, 2026, at 6:00 AM UTC

Title: Users may be unable to access their policy hits in the Microsoft Purview portal

User impact: Users may be unable to access their policy hits in the Microsoft Purview portal.

Current status: We're investigating a potential issue with Microsoft Purview and checking for impact to your organization. We'll provide an update within 30 minutes.

A post-incident report has been published.

A post-incident report has been published.

Title: Users may be unable to view or modify custom forms in SharePoint Online

User impact: Users may have been unable to view or modify custom forms in SharePoint Online.

More info: Affected users may have encountered multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:

Final status: We've completed deployment of the fix to all affected environments, and we've confirmed with impacted organizations that the issue is no longer occurring.

Scope of impact: This issue may have impacted any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.

Start time: Monday, October 12, 2026, at 1:00 AM UTC

End time: Thursday, October 15, 2026, at 12:30 AM UTC

Root cause: SharePoint Online had been running a new version of the component that supplies page data alongside the existing one, and as part of a planned change that new version was promoted to become the primary one. It did not correctly handle two of the request patterns that custom forms rely on when a page loads, so requests for page data stopped partway through. Because the first part of the page had already been sent to the browser, the service was not able to replace it with an error message, which is why affected users saw a blank form rather than an explanation.

Next steps:

We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.

Title: Users may be unable to view or modify custom forms in SharePoint Online

User impact: Users may be unable to view or modify custom forms in SharePoint Online.

More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:

Current status: We're continuing to deploy our fix to the affected environments and anticipate that deployment will be completed within 48 hours. We'll provide the latest deployment progress and updated completion timeline in our next update.

Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.

Start time: Monday, October 12, 2026, at 1:00 AM UTC

Root cause: A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.

Next update by: Wednesday, October 14, 2026, at 6:00 PM UTC

Title: Users may be unable to view or modify forms in SharePoint Online

User impact: Users may be unable to view or modify forms in SharePoint Online.

More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:

Current status: We've confirmed a recent API change as the source of the impact and have prevented it from reaching any further environments. We're continuing to deploy our fix to the affected environments to remediate the impact.

Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.

Start time: Monday, October 12, 2026, at 1:00 AM UTC

Root cause: A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.

Next update by: Tuesday, October 13, 2026, at 6:00 PM UTC

Title: Users may be unable to view or modify forms in SharePoint Online

User impact: Users may be unable to view or modify forms in SharePoint Online.

More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:

Current status: We’ve isolated a recent API change as the suspected source of the impact. We’ve initiated the process of deploying a fix to confirm our findings and potentially remediate the impact.

Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.

Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC

Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error

User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.

More info: Affected users are encountering multiple potential scenarios, including:

Current status: We're continuing our analysis of the HAR captures to determine the cause of impact.

Scope of impact: Your organization is impacted by this event, and impact is limited to users viewing or modifying Nintex forms in SharePoint Online.

Next update by: Tuesday, October 13, 2026, at 1:30 AM UTC

Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error

User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.

More info: Affected users are encountering multiple potential scenarios, including:

Current status: We're expanding our investigation to include HTTP Archive format (HAR) browser captures of the issue in progress to assist in isolating the underlying cause of impact and develop a remediation strategy.

Scope of impact: Your organization is impacted by this event, and impact is limited to users viewing or modifying Nintex forms in SharePoint Online.

Next update by: Monday, October 12, 2026, at 9:00 PM UTC

Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error

User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.

More info: Affected users are encountering multiple potential scenarios, including:

Current status: We're reviewing support case details to better understand the impact scenario and determine our next steps.

Scope of impact: Your organization is impacted by this event, and impact is limited to users viewing or modifying Nintex forms in SharePoint Online.

Next update by: Monday, October 12, 2026, at 8:00 PM UTC

Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error

User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.

Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may be unable to access the group feed in Microsoft Viva Engage

User impact: Users may have been unable to access the group feed with Microsoft Viva Engage.

Final status: Following our infrastructure optimizations, our internal telemetry verified that the impact had been remediated.

Scope of impact: This issue prevented any user from accessing the group feed with Microsoft Viva Engage.

Start time: Wednesday, October 21, 2026, at 2:01 PM UTC

End time: Wednesday, October 21, 2026, at 4:02 PM UTC

Root cause: A subset of service infrastructure that helps facilitate access to the Microsoft Viva Engage group feed dropped below our manageable service performance thresholds, resulting in impact.

Next steps:

This is the final update for the event.

Title: Users may be unable to access the group feed in Microsoft Viva Engage

User impact: Users may be unable to access the group feed with Microsoft Viva Engage.

Current status: We've identified a subset of service infrastructure that has dropped below our manageable service performance thresholds, preventing users from accessing the Microsoft Viva group feed with Microsoft Viva Engage. We're conducting service optimizations to the affected subset of service infrastructure to remediate the impact.

Scope of impact: This issue is preventing any user from accessing the group feed with Microsoft Viva Engage.

Start time: Wednesday, October 21, 2026, at 2:01 PM UTC

Root cause: A subset of service infrastructure that helps facilitate access to the Microsoft Viva Engage group feed has fallen below our manageable service performance thresholds, resulting in impact.

Next update by: Wednesday, October 21, 2026, at 5:30 PM UTC

Title: Users may have been unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may have been unable to upload S/MIME certificates to the GAL through Outlook desktop.

More info: Affected users may have received the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option, "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Final status: We’ve determined that a recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop. We've decided not to apply the targeted fix to temporarily restore the affected functionality and have instead developed and deployed a longer term solution. We've tested and have confirmed that this has fully resolved the issue.

Scope of impact: This event may have impacted any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Start time: Tuesday, October 6, 2026, at 12:00 AM UTC

End time: Monday, October 19, 2026, at 5:00 PM UTC

Root cause: A recent S/MIME certificate change prevented users from uploading S/MIME certificates to the GAL through Outlook desktop.

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.

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the GAL through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We’re progressing with applying the targeted fix to temporarily restore the affected functionality. In parallel, we’re developing a permanent solution to fully resolve the impact and expect to provide a more conclusive update by our next scheduled update.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Next update by: Tuesday, October 20, 2026, at 11:30 AM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the GAL through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We’re continuing to apply the targeted mitigation to temporarily restore the affected functionality for impacted organizations. We’re monitoring the mitigation’s progress and will provide a timeline for completion once available. We continue to recommend that affected organizations transition their workflows to the supported on-premises approach as soon as possible.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Next update by: Monday, October 19, 2026, at 11:30 AM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the GAL through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We’ve determined that rolling back the recent change isn’t a viable mitigation, as the change corrected an existing issue. We’ve identified a targeted mitigation to temporarily restore the affected functionality, and we’re applying this to impacted organizations. We recommend that affected organizations move their workflows to the supported on-premises approach as soon as possible.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 4:30 PM UTC

Title: Users may be unable to upload S/MIME certificates to the Global Address List (GAL) through Outlook desktop

User impact: Users may be unable to upload S/MIME certificates to the GAL through Outlook desktop.

More info: Affected users may get the following error when attempting to add the Secure/Multipurpose Internet Mail Extensions (S/MIME) certificates using the "publish to GAL" option. Users see "Microsoft Outlook cannot publish your certificates. The server may be offline, or your certificates may be invalid. Contact your administrator if the problem persists."

Current status: We’ve isolated a recent change which we suspect is resulting in this impact. We’re validating whether we’re able to safely roll back that change in order to remediate this event a confirm our root cause theory.

Scope of impact: This event may impact any user attempting to upload S/MIME to the GAL through Outlook desktop. This section may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 11:30 AM UTC

Title: Some users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users may have been unable to join town hall meetings in Microsoft Teams and were redirected to a registration page.

More info: This may have occurred when organizers created and published town halls with registration disabled. Additionally, users may have found the Join option unavailable or unresponsive.

While we worked to remediate the impact, affected users could have utilized their Microsoft Teams or Outlook calendars to join town hall meetings.

Final status: We've confirmed that the deployment of the fix has been fully rolled out, and we've validated with our internal monitoring to confirm that the impact has been remediated.

Scope of impact: Impact was specific to some users that attempted to join town hall meetings in Microsoft Teams when registration was disabled.

Start time: Thursday, October 1, 2026, at 4:16 PM UTC

End time: Tuesday, October 20, 2026, at 12:06 AM UTC

Root cause: A recent service change introduced a code regression that incorrectly required attendee registration information when registration was disabled. As a result, the attendee Join URL was removed from the session response, and prevented users from joining affected town hall meetings.

Next steps:

-We're reviewing the code change that resulted in impact to better understand why it incorrectly required users to register, and prevent similar issues from taking place in the future.

This is the final update for the event.

Title: Some users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This may occur when organizers create and publish town halls with registration disabled. Additionally, users may find the Join option unavailable or unresponsive.

While we work to remediate the impact, affected users can utilize their Microsoft Teams or Outlook calendars to join town hall meetings.

Current status: While most affected users have received the fix, the complete deployment is taking longer than initially anticipated. We're continuing to monitor the deployment to ensure that the impact is remediated for all affected users.

Scope of impact: Impact is specific to some users attempting to join town hall meetings in Microsoft Teams when registration is disabled.

Root cause: A recent service change introduced a code regression that incorrectly requires attendee registration information when registration is disabled. As a result, the attendee Join URL is removed from the session response, preventing users from joining affected town hall meetings.

Next update by: Tuesday, October 20, 2026, at 3:00 AM UTC

Title: Some users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This may occur when organizers create and publish town halls with registration disabled. Additionally, users may find the Join option unavailable or unresponsive.

While we work to remediate the impact, affected users can utilize their Microsoft Teams or Outlook calendars to join town hall meetings.

Current status: As we verify the timeline for the offending service change and when users started to become redirected to the registration page when joining Microsoft Teams town hall meetings, we're deploying our solution. Our fix deployment timeline projects our deployment will have completed and that the impact will be remediated by our next scheduled communication update.

Scope of impact: Impact is specific to some users attempting to join town hall meetings in Microsoft Teams when registration is disabled.

Root cause: A recent service change introduced a code regression that incorrectly requires attendee registration information when registration is disabled. As a result, the attendee Join URL is removed from the session response, preventing users from joining affected town hall meetings.

Next update by: Tuesday, October 20, 2026, at 12:00 AM UTC

Title: Some users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This occurs when organizers create and publish town halls with registration disabled. Additionally, users find the Join option unavailable or unresponsive.

Current status: We’ve completed development of the fix and successfully tested the updated build in an internal environment with the offending change removed. We’re progressing the remaining preparations required to deploy the fix to the affected environment. Once deployed, we’ll validate that the fix has remediated impact.

Scope of impact: Impact is specific to some users attempting to join town hall meetings in Microsoft Teams when registration is disabled.

Root cause: A recent service change has introduced a code regression that incorrectly requires attendee registration information when registration is disabled. As a result, the attendee Join URL is removed from the session response, preventing users from joining affected town hall meetings.

Next update by: Monday, October 19, 2026, at 5:30 PM UTC

Title: Some users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This occurs when organizers create and publish town halls with registration disabled. Additionally, some users may find the Join option unavailable or unresponsive.

Current status: We’ve confirmed the source of the regression and are developing a code fix to remediate impact. Once the updated build is complete, we’ll test the fix within an internal environment to confirm its effectiveness before progressing with a gradual rollout to the affected environment.

Scope of impact: Your organization is affected by this event, and some users attempting to join town hall meetings in Microsoft Teams with registration disabled are impacted.

Root cause: A recent service change introduced a code regression that caused the attendee Join URL to be removed when registration was disabled, resulting in impact.

Next update by: Monday, October 19, 2026, at 2:00 PM UTC

Title: Some users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This occurs when organizers create and publish town halls with registration disabled. Additionally, some users may find the Join option unavailable or unresponsive.

Current status: We’ve identified that a recent service change introduced a regression which removes the attendee Join URL when registration is disabled, resulting in the Join option being unavailable or unresponsive. We’re validating this finding and assessing whether reverting the change or implementing a code fix is the most appropriate mitigation to remediate impact.

Scope of impact: Your organization is affected by this event, and some users attempting to join town hall meetings in Microsoft Teams with registration disabled are impacted.

Root cause: A recent service change introduced a code regression that caused the attendee Join URL to be removed when registration was disabled, resulting in impact.

Next update by: Monday, October 19, 2026, at 12:00 PM UTC

Title: Some users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page

User impact: Users are unable to join town hall meetings in Microsoft Teams and are redirected to a registration page.

More info: This occurs when organizers create and publish town halls with registration disabled. Additionally, some users may find the Join option unavailable or unresponsive.

Current status: We’ve confirmed that affected town halls are successfully created and published with registration disabled as intended. However, the attendee experience isn’t honoring this setting and users continue to be directed to a registration page. We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.

Scope of impact: Your organization is affected by this event, and some users attempting to join town hall meetings in Microsoft Teams with registration disabled are impacted.

Next update by: Monday, October 19, 2026, at 10:00 AM UTC

Title: Users and admins couldn't view or manage device group configurations through the Microsoft Defender portal

User impact: Users and admins couldn't view or manage device group configurations through the Microsoft Defender portal.

More info: The device groups page in the Microsoft Defender portal wasn't loading for affected users and admins. Core security operations such as detection, alerting, and incident response weren't affected.

Final status: Our investigation has further determined it was specifically a code issue that was occurring within the device groups page and caused a component in the page rendering process to fail to handle the response correctly and resulted in the page to crash. We've developed and deployed a fix to remediate the impact and confirmed with some affected users that the issue is resolved.

Scope of impact: Users and admins who attempted to view or manage device group configurations through the Microsoft Defender portal may have been affected.

Start time: Monday, October 19, 2026, at 9:00 AM UTC

End time: Monday, October 19, 2026, at 7:51 PM UTC

Root cause: A code issue in the device groups page was causing a component in the page rendering process to fail to handle the response correctly and was resulting in the page to crash.

Next steps:

This is the final update for the event.

Title: Users and admins can't view or manage device group configurations through the Microsoft Defender portal

User impact: Users and admins can't view or manage device group configurations through the Microsoft Defender portal.

More info: The device groups page in the Microsoft Defender portal isn't loading for affected users and admins. Core security operations such as detection, alerting, and incident response aren't affected.

Current status: We've identified that an issue in the device groups page is causing a component in the page rendering process to fail to handle the response correctly and is resulting in the page to crash. We're working on developing a solution that remediates the impact.

Scope of impact: Users and admins attempting to view or manage device group configurations through the Microsoft Defender portal may be affected. This section may be updated as our investigation continues.

Root cause: An issue in the device groups page is causing a component in the page rendering process to fail to handle the response correctly and is resulting in the page to crash.

Next update by: Monday, October 19, 2026, at 9:00 PM UTC

Title: Users are unable to view or manage device group configurations through the Microsoft Defender portal.

User impact: Users are unable to view or manage device group configurations through the Microsoft Defender portal.

Current status: We're investigating a potential issue with Microsoft Defender portal and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users may be unable to complete prompts using Microsoft 365 Copilot and the GPT 5.1 model

User impact: Users may have been unable to complete prompts using Copilot and the GPT 5.1 model.

More info: When attempting to execute prompts, users received a message stating "The model is unavailable."

Final status: While we were in the process of analyzing failing requests, 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 doesn't happen again.

Scope of impact: This issue may have affected any user attempting to complete prompts in Copilot using the GPT 5.1 model.

Start time: Monday, October 19, 2026, at 2:19 PM UTC

End time: Monday, October 19, 2026, at 3:20 PM UTC

This is the final update for the event.

Title: Users may be unable to complete prompts using Microsoft 365 Copilot and the GPT 5.1 model

User impact: Users may be unable to complete prompts using Copilot and the GPT 5.1 model.

More info: When attempting to execute prompts, users receive a message stating "The model is unavailable."

Current status: We’re reviewing failing requests to better understand why the error is occurring and determine next steps for remediation.

Scope of impact: This issue may affect any user attempting to complete prompts in Copilot using the GPT 5.1 model.

Next update by: Monday, October 19, 2026, at 4:30 PM UTC

Title: We're looking into a potential problem impacting Microsoft 365 Copilot

User impact: We're checking for potential impact to your users.

Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users were intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users were intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Impacted users may have received the following error message:

“Can’t retrieve calendar events right now. Refresh the browser and try again.”

As a workaround, some impacted users were able to access their calendar in the classic Outlook desktop client.

Final status: We’ve completed deployment of the fix to the affected environment and monitoring has confirmed that the impact is resolved. Additionally, a subset of affected users has confirmed that the issue is resolved.

Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may have been intermittently impacted.

Start time: Wednesday, July 1, 2026, at 2:49 PM UTC

End time: Saturday, October 17, 2026, at 12:33 AM UTC

Root cause: A caching issue caused outdated calendar data to be referenced after the calendar folder information was refreshed, resulting in intermittent calendar access failures.

Next steps:

This is the final update for the event.

This is the final update for the event.

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Impacted users may receive the following error message:

“Can’t retrieve calendar events right now. Refresh the browser and try again.”

As a workaround, impacted users can access their calendar in the classic Outlook desktop client.

Current status: We’ve completed deployment of the fix to the initially affected service environment and expect this has remediated impact for users in that environment. The fix is continuing to propagate across the remaining affected environment, with this process expected to take approximately one additional week to complete. We’ll continue monitoring the deployment as it progresses to confirm that impact is fully remediated.

Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted.

Start time: Tuesday, July 7, 2026, at 5:33 PM UTC

Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.

Next update by: Monday, October 19, 2026, at 10:00 AM UTC

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Impacted users may receive the following error message:

“Can’t retrieve calendar events right now. Refresh the browser and try again.”

As a workaround, impacted users can access their calendar in the classic Outlook desktop client or through Microsoft Teams.

Current status: Our fix deployment is completing for the initially identified service environment; however, we’ve confirmed that additional environments remain impacted. While some users should experience impact resolution as the fix reaches them, we’re extending the fix deployment to the remaining affected environments, and we’ll provide an estimation for its completion once available.

Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted.

Estimated time to resolve: Friday October 9, 2026

Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.

Next update by: Monday, October 12, 2026, at 9:30 AM UTC

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Impacted users may receive the following error message:

“Can’t retrieve calendar events right now. Refresh the browser and try again.”

As a workaround, impacted users can access their calendar in the classic Outlook desktop client or through Microsoft Teams.

Current status: Our fix deployment is completing and we're reaching out to some users to confirm the issue is no longer occurring.

Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted.

Estimated time to resolve: Friday October 9, 2026

Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.

Next update by: Monday, October 12, 2026, at 7:00 AM UTC

Title: Users may be intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may be intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Impacted users may receive the following error message:

“Can’t retrieve calendar events right now. Refresh the browser and try again.”

As a workaround, impacted users can access their calendar in the classic Outlook desktop client or through Microsoft Teams.

Current status: We’ve identified that the issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated. We’ve implemented and merged a fix to ensure the refreshed calendar data is correctly used when loading subsequent events. The fix is expected to reach affected users by October 9, 2026.

Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted.

Estimated time to resolve: Friday October 9, 2026

Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.

Next update by: Friday, October 9, 2026, at 5:30 PM UTC

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.

Current status: We’re continuing to review service health telemetry and HAR logs to investigate what we suspect is a caching issue that’s leading to the impact. We’re also testing potential solutions to confirm our findings and determine our next steps.

Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.

Current status: Our review of service health telemetry and the HAR logs persists as we continue to isolate the source of this issue.

Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.

Next update by: Thursday, October 1, 2026, at 7:30 AM UTC

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.

Current status: We're currently reviewing telemetry and HTTP Archive format (HAR) log information as we investigate the cause of impact.

Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.

Next update by: Wednesday, September 30, 2026, at 6:30 PM UTC

Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client

User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.

More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.”

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.

Title: Users are experiencing failures when using Power Apps and Power Automate functionality

User impact: Users were experiencing failures when using Power Apps and Power Automate functionality.

Final Status: We have completed the restart for the remaining affected service instances and after a period of monitoring, we confirmed via service monitors that functionality for Power Apps and Power Automate services has been restored.

This is the final update on the incident.

Preliminary Root Cause: A recent deployment to a portion of the infrastructure supporting Power Apps and Power Automate functionality caused a misconfiguration.

Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.

Title: Users are experiencing failures when using Power Apps and Power Automate functionality

User impact: Users are experiencing failures when using Power Apps and Power Automate functionality.

More Info: Affected users may see HTTP 502 errors

Current Status: We have completed the rollback of the deployment and we identified that some existing service instances remained in an unhealthy state. We are restarting the remaining affected service instances to fully mitigate the issue.

Next Update Time: Sunday, October 18, 2026, at 1:00 PM UTC

Title: Users are experiencing failures when using Power Apps and Power Automate functionality

User impact: Users are experiencing failures when using Power Apps and Power Automate functionality.

More Info: Affected users receive HTTP 502 errors.

Current Status: After our investigation, we identified that a recent deployment to a portion of the infrastructure supporting Power Apps and Power Automate functionality caused a misconfiguration, leading to impact. We are preparing to roll back the deployment to mitigate the issue.

Next Update Time: Sunday, October 18, 2026, at 11:00 AM UTC

Title: Users are experiencing failures when using Power Apps and Power Automate functionality

User impact: Users are experiencing failures when using Power Apps and Power Automate functionality.

Current Status: We are aware of an emerging issue where users are experiencing failures when using Power Apps and Power Automate functionality. 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.

Title: Some users' calls may fail in Microsoft Teams

User impact: Users' calls may have failed in Microsoft Teams.

More info: Specifically, reports from affected users indicated that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams weren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not have received inbound calls.

Final status: We've confirmed that the recent configuration change that managed how phone numbers were processed was responsible for impact, and affected users confirm that impact is remediated after we reverted this change and replaying any changes to phone number that occurred during the window of impact.

Scope of impact: Impact was specific to users attempting to make calls to phone numbers that had recently undergone assignment changes in Microsoft Teams.

Start time: Friday, October 16, 2026, at 2:12 AM UTC

End time: Friday, October 16, 2026, at 4:00 PM UTC

Root cause: A recent configuration change that managed how phone numbers were processed was responsible for impact.

Next steps: We're reviewing and improving our configuration change procedures to detect and prevent similar issues from occurring again in the future.

This is the final update for this event.

Title: Some users' calls may fail in Microsoft Teams

User impact: Users' calls may fail in Microsoft Teams.

More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.

Current status: We've reverted the recent configuration change that relates to how phone numbers are processed and are monitoring to confirm if this change caused the reported impact and if the issue is resolved.

Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams. This information may be updated as our investigation continues.

Next update by: Friday, October 16, 2026, at 10:30 PM UTC

Title: Some users' calls may fail in Microsoft Teams

User impact: Users' calls may fail in Microsoft Teams.

More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.

Current status: We’ve reprovisioned the affected resource account-to-phone number association as an initial mitigation. During our investigation, we identified a recent configuration change that may be contributing to the impact. We’re investigating this change to determine whether it’s responsible for the issue.

Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams.

Next update by: Friday, October 16, 2026, at 3:30 PM UTC

Title: Some users' calls may fail in Microsoft Teams

User impact: Users' calls may fail in Microsoft Teams.

More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.

Current status: We’ve identified a potential issue with cached information not updating as expected following phone-number assignment changes. We’re reprovisioning the affected resource account-to-phone number association as an initial mitigation and monitoring the results to validate our root cause hypothesis and determine whether additional steps are required.

Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams.

Next update by: Friday, October 16, 2026, at 1:30 PM UTC

Title: Some users' calls are failing in Microsoft Teams

User impact: Users' calls are failing in Microsoft Teams.

More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.

Current status: We're continuing to review user-provided service logs and call logs to gain insight into the underlying source of impact and determine our next steps.

Scope of impact: Your organization is impacted by this event, and some users making calls in Microsoft Teams are affected.

Next update by: Friday, October 16, 2026, at 9:30 AM UTC

Title: Some users' calls are failing in Microsoft Teams

User impact: Users' calls are failing in Microsoft Teams.

More info: Specifically, reports from affected users indicate that PSTN direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected.

Current status: We're reviewing and analyzing user-provided service logs and contextual details to assist with our investigation and determine our next troubleshooting steps.

Scope of impact: Your organization is impacted by this event, and some users making calls in Microsoft Teams are affected.

Next update by: Friday, October 16, 2026, at 5:00 AM UTC

Title: Some users' calls are failing in Microsoft Teams

User impact: Users' calls are failing 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.

Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may have been unable to join Microsoft Teams meetings and saw sign-in errors.

More info: Affected users saw a sign-in prompt when they attempted to join a meeting but clicking "sign-in" on the prompt had no effect.

Users can sign-out and sign back in as a temporary mitigation.

Final status: We've completed the deployment of our code fix to all affected environments and confirmed through telemetry, along with a subset of impacted users, that the issue is resolved.

Scope of impact: Some users who attempted to join Microsoft Teams meetings may have been affected by this issue.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

End time: Friday, October 16, 2026, at 3:30 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, which resulted in impact.

Next steps:

This is the final update for the event.

Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: Our code fix has nearly completed propagation throughout most of the affected environments and we're continuing to monitor it as it progresses. We anticipate it'll have fully propagated by our next scheduled communications update.

Scope of impact: Some users attempting to join Microsoft Teams meetings may be affected by this issue. This information may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.

Next update by: Friday, October 16, 2026, at 5:30 AM UTC

Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We've halted the code change causing this problem to ensure that no additional users encounter Microsoft Teams meeting join and sign-in errors. We're deploying a code fix to remediate the issue for users who received the code change prior to us halting it. Users will experience progressive relief from the issue as this deployment reaches them and we expect the code fix to propagate fully around the time of our next update.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.

Next update by: Thursday, October 15, 2026, at 11:30 PM UTC

Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We’re monitoring the rollback of the offending change and expect that a remediation timeline will be provided by our next scheduled communications update.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.

Next update by: Wednesday, October 14, 2026, at 10:00 PM UTC

Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We've initiated our rollback of the responsible change and will monitor this rollback to provide a mitigation timeline as it becomes available.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.

Next update by: Wednesday, October 14, 2026, at 3:30 AM UTC

Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We've confirmed a recent change to the authentication flow utilized in the event contained a regression, resulting in this impact. We're preparing to rollback this change in the affected environments and will provide a remediation timeline as soon as one becomes available.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Start time: Wednesday, October 7, 2026, at 1:00 AM UTC

Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.

Next update by: Wednesday, October 14, 2026, at 12:00 AM UTC

Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We're continuing to review the logs provided by a subset of affected users alongside service side data in order to develop the most effective remediation steps.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC

Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors

User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.

More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.

Users can sign-out and sign back in as a temporary mitigation.

Current status: We're reviewing the logs provided by a subset of affected users and have requested an additional set of fresh logs from those users to assist in pinpointing the underlying root cause of this event, so we may develop the most effective remediation steps.

Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.

Next update by: Tuesday, October 13, 2026, at 7:00 PM UTC