Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents

Timeline

Every update Microsoft posted for this issue, newest first.

1. Oct 14, 2026, 20:43 CEST

   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.

2. Oct 7, 2026, 20:37 CEST

   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.

3. Sep 30, 2026, 20:33 CEST

   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.

4. Sep 23, 2026, 20:01 CEST

   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.

5. Sep 23, 2026, 20:01 CEST

   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.

6. Sep 21, 2026, 20:34 CEST

   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.

7. Sep 17, 2026, 19:57 CEST

   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.

8. Sep 16, 2026, 23:33 CEST

   We're continuing to reach out to impacted users to confirm if impact is remediated after the deployment of our fix.

9. Sep 16, 2026, 21:36 CEST

   We've created and deployed the fix and we're confirming with impacted users if the issue is resolved.

10. Sep 15, 2026, 20:02 CEST

    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.

11. Sep 14, 2026, 20:44 CEST

    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.

12. Sep 9, 2026, 20:15 CEST

    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.

13. Sep 8, 2026, 20:40 CEST

    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.

14. Aug 31, 2026, 21:16 CEST

    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.

15. Aug 19, 2026, 20:00 CEST

    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.

16. Aug 12, 2026, 20:18 CEST

    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.

17. Aug 11, 2026, 20:11 CEST

    We’re continuing to develop a fix to correct the URL redirection, and we’ll provide a resolution timeline once available.

18. Aug 4, 2026, 19:46 CEST

    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.

19. Aug 4, 2026, 18:25 CEST

    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.

20. Aug 4, 2026, 17:04 CEST

    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.

21. Aug 4, 2026, 16:51 CEST

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