Microsoft consumer products Outage History

Microsoft consumer products is up right now

Pingoru has recorded 12 incidents for Microsoft consumer products: 12 in the last 12 months and 1 in the last 90 days.

Source: status.cloud.microsoft · Aggregated across Microsoft consumer products products

12incidents recorded
12last 12 months
1last 90 days
7 daystypical duration
Incidents per month
036AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Microsoft consumer products in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20266423 of 720 (59%)
May 20262215 of 744 (29%)
June 2026357 of 720 (8%)
July 202617 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 590 (0%)

Incidents, newest first

Minor July 27, 2026 Users may be unable to send messages after a recipient of a new chat accepts the request 7h 20m Microsoft Teams Free

Started Jul 27, 2026, 05:40 PM UTC· resolved Jul 28, 2026, 01:00 AM UTC

  1. monitoring Jul 28, 2026, 05:15 PM UTC

    User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We're reviewing scenario telemetry logs to determine why users may be unable to send messages after a recipient of a new chat request accepts in Microsoft Teams Free. Next update by: Tuesday, July 28, 2026, at 6:30 PM UTC

  2. monitoring Jul 28, 2026, 06:26 PM UTC

    User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We've identified that the process which should occur when a user accepts a new chat isn't trigger as expected. We're continuing to review the scenario telemetry logs to identify why this process isn't completing to determine the root cause and a strategy that remediates impact. Next update by: Tuesday, July 28, 2026, at 8:30 PM UTC

  3. monitoring Jul 28, 2026, 08:29 PM UTC

    User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Our review of the scenario telemetry logs is taking longer than anticipated, but we're continuing to make progress in understanding the root cause and developing a strategy that remediates impact. Next update by: Wednesday, July 29, 2026, at 1:00 AM UTC

  4. monitoring Jul 29, 2026, 12:01 AM UTC

    User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Current status: We’ve made changes to improve background processing and confirmed through internal monitoring that the impacted scenario is recovering. We’re continuing to monitor the recovery progress to confirm the issue is fully resolved. Next update by: Wednesday, July 29, 2026, at 10:00 AM UTC

  5. resolved Jul 29, 2026, 05:14 AM UTC

    User impact: Users may have been unable to send new messages in Microsoft Teams Free. Final status: We’ve confirmed after monitoring that this issue is fully resolved. Start time: Monday, July 27, 2026, at 5:40 PM UTC End time: Tuesday, July 28, 2026, at 1:00 AM UTC This is the final update for the event.

Read the full incident report →

Minor June 26, 2026 Users may be unable to access or sign in to Microsoft Teams Free on iOS devices 1d 2h Microsoft Teams Free

Started Jun 26, 2026, 09:21 PM UTC· resolved Jun 28, 2026, 12:08 AM UTC

  1. monitoring Jun 26, 2026, 09:21 PM UTC

    User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS devices. Current status: We're investigating a potential Microsoft Teams Free issue in which users may be unable to access or sign in to the service on iOS devices and will provide an update in 30 minutes.

Read the full incident report →

Minor June 25, 2026 Users may be unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices 1d 6h Microsoft Teams Free

Started Jun 25, 2026, 07:00 PM UTC· resolved Jun 27, 2026, 01:16 AM UTC

  1. monitoring Jun 26, 2026, 09:49 PM UTC

    User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices. Current status: We've determined that this issue is due to a recent change that included a reference to a deprecated token for mobile devices. We're reverting this offending change to mitigate impact. Start time: Thursday, June 25, 2026, at 7:00 PM UTC Next update by: Saturday, June 27, 2026, at 1:30 AM UTC

  2. resolved Jun 27, 2026, 01:16 AM UTC

    User impact: Users may have been unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices. Final status: We’ve successfully reverted the offending change and confirmed with service telemetry that this issue was resolved by our actions. Start time: Thursday, June 25, 2026, at 7:00 PM UTC End time: Saturday, June 27, 2026, at 1:16 AM UTC This is the final update for the event.

Read the full incident report →

Minor June 1, 2026 Users may be unable to access the Microsoft Copilot desktop or web app 3h 40m Microsoft Copilot

Started Jun 01, 2026, 01:55 PM UTC· resolved Jun 01, 2026, 05:35 PM UTC

  1. monitoring Jun 01, 2026, 03:53 PM UTC

    User impact: Users may be unable to access the Microsoft Copilot desktop or web app. Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause. Next update by: Monday, June 01, 2026, at 5:00 PM UTC

  2. monitoring Jun 01, 2026, 04:33 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We're working on getting logs from impacted users to focus our investigative efforts to isolate the source of impact. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 5:00 PM UTC

  3. monitoring Jun 01, 2026, 04:46 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We've received logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC

  4. monitoring Jun 01, 2026, 05:30 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC

  5. resolved Jun 01, 2026, 05:55 PM UTC

    User impact: Users may have been unable to access the Copilot desktop or web app. Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered. Start time: Monday, June 01, 2026, at 1:55 PM UTC End time: Monday, June 01, 2026, at 5:52 PM UTC

Read the full incident report →

Minor May 29, 2026 Users may be unable to use Microsoft Copilot 3h 5m Microsoft Copilot

Started May 29, 2026, 02:30 PM UTC· resolved May 29, 2026, 05:35 PM UTC

  1. monitoring May 29, 2026, 03:50 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We're reviewing service telemetry to isolate the source of the issue. Next update by: Friday, May 29, 2026, at 5:30 PM UTC

  2. monitoring May 29, 2026, 05:01 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover. Next update by: Friday, May 29, 2026, at 6:30 PM UTC

  3. resolved May 29, 2026, 07:01 PM UTC

    User impact: Users were unable to use Microsoft Copilot. Final status: The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We monitored the environment for an extended period of time and have validated that service has been restored. Start time: Friday, May 29, 2026, at 2:30 PM UTC End time: Friday, May 29, 2026, at 5:35 PM UTC This is the final update for this event.

Read the full incident report →

Minor May 14, 2026 Some users may see failures when accessing Microsoft Copilot 3h 44m Microsoft Copilot

Started May 14, 2026, 01:16 PM UTC· resolved May 14, 2026, 05:00 PM UTC

  1. monitoring May 14, 2026, 05:09 PM UTC

    User impact: Users may see failures when accessing Microsoft Copilot More info: Users may be presented with a 401-error response code. Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to users. We'll provide an update within 30 minutes.

  2. resolved May 14, 2026, 05:43 PM UTC

    User impact: Users may have seen failures when accessing Microsoft Copilot. More info: Users may be presented with a 401-error response code. Final status: We've completed a deployment to roll back to the most recent stable version of the service. Through our service side telemetry, we've confirmed that the service has been restored to a healthy level. Start time: Thursday, May 14, 2026, at 1:16 PM UTC End time: Thursday, May 14, 2026, at 5:00 PM UTC This is the final update for this event.

Read the full incident report →

Minor April 29, 2026 iOS and iPadOS users may experience issues accessing Outlook and Hotmail from the iOS default Mail app 9d 19h Outlook.com

Started Apr 29, 2026, 09:02 PM UTC· resolved May 09, 2026, 04:16 PM UTC

  1. monitoring Apr 29, 2026, 09:02 PM UTC

    User impact: iOS and iPadOS users may experience issues accessing Outlook and Hotmail from the iOS default Mail app. More Info: Outlook.com, Hotmail.com, and the Outlook app are still working as expected. However, if your account is locked out, you'll need to take multiple actions. First, you'll need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after you've completed the steps in the above article, you will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: Our service environment remains healthy, and users should follow the instructions listed in the More info section above for EACH impacted device. We’ve included a link to a support article with guidance should you encounter additional issues. Next update by: Thursday, April 30, 2026, at 10:00 PM UTC

Read the full incident report →

Minor April 29, 2026 Users may experience issues accessing or using Microsoft Copilot 1h 37m Microsoft Copilot

Started Apr 29, 2026, 01:51 PM UTC· resolved Apr 29, 2026, 03:28 PM UTC

  1. resolved Apr 29, 2026, 04:11 PM UTC

    User impact: Affected users may have been unable to use Copilot services and features. More info: Prompts to Copilot may have returned an error message stating "Oops, Something happened. Can you try again?" Final status: We observed and mitigated an infrastructure issue that caused issues accessing Microsoft Copilot. We redirected traffic to healthy infrastructure and have confirmed that the issue is resolved. Start time: Wednesday, April 29, 2026, at 1:51 PM UTC End time: Wednesday, April 29, 2026, at 3:28 PM UTC This is the final update for the event.

Read the full incident report →

Minor April 29, 2026 Users may experience issues accessing Outlook.com 10d 8h Outlook.com

Started Apr 29, 2026, 07:37 AM UTC· resolved May 09, 2026, 04:16 PM UTC

  1. monitoring Apr 29, 2026, 07:37 AM UTC

    User impact: Users may experience intermittent issues signing in to Outlook.com. More Info: If you are still impacted, we recommend the following steps outlined below to sign-in again on iOS devices: 1. Open the Settings app on your iPhone. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to reenter the password. 5. Tap on Account Settings or directly on the Password field. This will depend on your iOS version. 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: We’re closely monitoring our internal and external service telemetry to ensure the impact does not reoccur. We still advise that users attempt to sign-in again and if they encounter the error message stating “You’ve tried to sign-in too many times with an incorrect account or password”, they should follow the inline user experience to reset their password and sign-in again. Next update by: Wednesday, April 29, 2026, at 2:00 PM UTC

  2. monitoring Apr 29, 2026, 12:46 PM UTC

    User impact: Users may experience intermittent issues signing in to Outlook.com. Current status: We’re continuing to closely monitor service telemetry which continues to show the mitigation actions have been successful. However, if users are still impacted, we recommend that users attempt to sign-in again and if they encounter the error message stating “You’ve tried to sign-in too many times with an incorrect account or password”, they should follow the inline user experience to reset their password and sign-in again. Next update by: Wednesday, April 29, 2026, at 10:00 PM UTC

Read the full incident report →

Minor April 28, 2026 Users may experience issues accessing Outlook.com in the iOS mail app 11d 1h Outlook.com

Started Apr 28, 2026, 02:21 PM UTC· resolved May 09, 2026, 04:16 PM UTC

  1. monitoring Apr 28, 2026, 02:21 PM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. Current status: We’ve received reports that impact associated with OL1292958 persists. We've resumed our investigation of the issue and are currently analyzing service telemetry and investigating reported behavior to determine scope and next steps. Next update by: Tuesday, April 28, 2026, at 5:00 PM UTC

  2. monitoring Apr 28, 2026, 05:10 PM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. Current status: We're performing some changes to optimize the outlook.com iOS sign-in experience and, once complete, we'll provide instructions to help users sign back into their accounts. In the interim as we develop this change, we recommend trying the following steps to sign in to your account: 1. Open the Settings app on your iPhone. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to reenter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Next update by: Tuesday, April 28, 2026, at 11:00 PM UTC

  3. monitoring Apr 28, 2026, 10:33 PM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. Current status: We're continuing to optimize the outlook.com iOS sign-in experience to address reports of persisting impact. We've also investigated the scenario in which users are encountering repeated sign-in prompts and are then informed, "You've tried to sign in too many times with an incorrect account or password"; users experiencing this scenario should sign in with other methods or reset their password to sign in to their accounts. We'll provide more guidance as it becomes available. Next update by: Wednesday, April 29, 2026, at 1:30 AM UTC

  4. monitoring Apr 28, 2026, 11:35 PM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. Current status: We're continuing to optimize the outlook.com iOS sign-in experience to address reports of persisting impact. We've also investigated the scenario in which users are encountering repeated sign-in prompts and are then informed, "You've tried to sign in too many times with an incorrect account or password"; users experiencing this scenario should sign in with other methods or reset their password to sign in to their accounts. We'll provide more guidance as it becomes available. Next update by: Wednesday, April 29, 2026, at 1:30 AM UTC

  5. monitoring Apr 29, 2026, 01:25 AM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. Current status: We’re continuing to implement further optimizations for the outlook.com iOS sign-in experience to help address reports of persisting impact. While we monitor these optimization changes to assess their effectiveness, we’re also looking into what additional changes may be needed to address the scenario in which users are encountering repeated sign-in prompts. We still recommend that for users experiencing this scenario, they should sign in with other methods or reset their password to sign in to their accounts. We’ll continue to provide more guidance as it becomes available. Next update by: Wednesday, April 29, 2026, at 3:30 AM UTC

  6. monitoring Apr 29, 2026, 03:29 AM UTC

    User impact: Users may experience intermittent issues signing-in to Outlook.com in the iOS mail app. More Info: If you are still impacted, we recommend the following steps outlined below to sign-in again on iOS devices: 1. Open the Settings app on your iPhone. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to reenter the password. 5. Tap on Account Settings or directly on the Password field. This will depend on your iOS version. 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: We’ve completed all our optimization changes to fully address the impact for the outlook.com iOS sign-in experience and we’ve confirmed service health has returned to normal. We anticipate that users should no longer experience repeated sign-in prompts hindering the sign-in process. We recommend that users attempt to sign-in again and if they encounter the error message stating “You’ve tried to sign-in too many times with an incorrect account or password”, they should follow the inline user experience to reset their password and sign-in again. Next update by: Wednesday, April 29, 2026, at 9:00 AM UTC

Read the full incident report →

Minor April 27, 2026 iOS, iPadOS, and iPad users may experience issues accessing Outlook and Hotmail from the iOS default Mail app 11d 7h Outlook.com

Started Apr 27, 2026, 08:45 AM UTC· resolved May 08, 2026, 04:00 PM UTC

  1. monitoring Apr 30, 2026, 05:33 PM UTC

    User impact: iOS, iPadOS, and iPad users may experience issues accessing Outlook and Hotmail from the iOS default Mail app. More Info: Outlook.com, Hotmail.com, and the Outlook app are still working as expected. However, if your account is locked out, you'll need to take multiple actions as outlined below. First, you'll need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after you've completed all steps in the above article, you will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: We're continuing to monitor service telemetry and can confirm our environment remains healthy as more users follow the instructions provided in the More info section of this communication for EACH individual impacted device. We’ve included a link to a support article with guidance on remediating impact should affected users encounter issues with this recommended process. Next update by: Friday, May 1, 2026, at 6:00 PM UTC

  2. monitoring May 01, 2026, 04:29 PM UTC

    User impact: iOS, iPadOS, and iPad users may experience issues accessing Outlook and Hotmail from the iOS default Mail app. More info: Outlook.com, Hotmail.com, and the Outlook app are still working as expected. However, if your account is locked out, you'll need to take multiple actions as outlined below. First, you'll need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after you've completed all steps in the above article, you will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: Our service health telemetry indicates that user access continues to be restored as the steps provided in the linked support article in the "More info" section are followed by each impacted device. We're continuing to monitor the telemetry to further validate that the environment remains in a healthy state. Next update by: Monday, May 4, 2026, at 6:00 PM UTC

  3. monitoring May 04, 2026, 05:04 PM UTC

    User impact: iOS, iPadOS, and iPad users may experience issues accessing Outlook and Hotmail from the iOS default Mail app. More info: Outlook.com, Hotmail.com, and the Outlook app are still working as expected. However, if your account is locked out, you'll need to take multiple actions as outlined below. First, you'll need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after you've completed all steps in the above article, you will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: We're continuing to observe the number of impacted devices decrease as users follow the steps provided in the "More info" section and recover access. We'll continue to monitor the telemetry to ensure the service remains in a healthy state. Next update by: Wednesday, May 6, 2026, at 6:30 PM UTC

  4. monitoring May 06, 2026, 05:00 PM UTC

    User impact: iOS, iPadOS, and iPad users may experience issues accessing Outlook and Hotmail from the iOS default Mail app. More info: Outlook.com, Hotmail.com, and the Outlook app are still working as expected. However, if your account is locked out, you'll need to take multiple actions as outlined below. First, you'll need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after you've completed all steps in the above article, you will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account is syncing properly and emails are being sent/received. Current status: We're continuing to observe the number of impacted devices decrease as users follow the recovery guidance provided in the “More info” section and regain access. Our continued close monitoring of system telemetry indicates that the service remains healthy. Next update by: Friday, May 8, 2026, at 6:30 PM UTC

  5. resolved May 08, 2026, 05:21 PM UTC

    User impact: iOS, iPadOS, and iPad users may have experienced issues accessing Outlook and Hotmail from the iOS default Mail app. More info: Outlook.com, Hotmail.com, and the Outlook app worked as expected. However, if the user’s account was locked out, they’ll need to take multiple actions as outlined below. First, users will need to follow guidance in the article: https://support.microsoft.com/en-us/office/ios-ipados-users-may have-experience-issues-accessing-their-outlook-and-hotmail-accounts-from-the-ios-ipados-default-mail-app-3584197b-8ffb-46ce-b5c6-f4cc71ff29a7 Next, after users have completed all steps in the above article, they will need to complete the numbered steps below for each impacted device. iOS and iPadOS users must take the following steps to access their accounts on EACH impacted device: 1. Open the Settings app on your iOS/iPadOS device. 2. Scroll down and tap on Mail. 3. Select Accounts under the Mail settings. 4. Tap on the email account for which you need to re-enter the password. 5. Tap on Account Settings or directly on the Password field (depending on your iOS/iPadOS version). 6. Enter the updated or correct password in the Password field. 7. Tap Done to save the changes. 8. Open the Mail app to confirm that the account was synced properly and that email messages were being sent/received. Final status: We've confirmed through our system telemetry that the service continues to remain healthy. Users who continue to experience issues should follow the steps outlined in "More Info" section. Start time: Monday, April 27, 2026, at 8:45 AM UTC End time: Friday, May 8, 2026, at 4:00 PM UTC This is the final update for the event.

Read the full incident report →

Minor April 8, 2026 Some users may be unable to search, chat, or call users in Microsoft Teams Free 43d 5h Microsoft Teams Free

Started Apr 08, 2026, 06:45 AM UTC· resolved May 21, 2026, 12:09 PM UTC

  1. monitoring Apr 28, 2026, 02:12 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. More info: Some new users who signed up during the impact window were incorrectly treated as already onboarded, causing onboarding and privacy consent screens to be skipped, their profiles to appear as “Unknown users” to others, and preventing them from being searchable or reliably reachable in chat. Current status: We've identified a recently deployed backend change is causing new Teams Free users to bypass required onboarding steps, leaving user profiles in an incomplete state. As a result, affected users can not be discovered, connect with others, or successfully complete chat request flows. We're analyzing all our available resources to identify a mitigation plan. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, April 29, 2026, at 3:30 PM UTC

  2. monitoring Apr 29, 2026, 01:44 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. More info: Some new users who signed up during the impact window were incorrectly treated as already onboarded, causing onboarding and privacy consent screens to be skipped, their profiles to appear as “Unknown users” to others, and preventing them from being searchable or reliably reachable in chat. Current status: We're continuing to review various available mitigation strategies to determine the most effective method to relieve impact. As a workaround, affected users can sign into the mobile application and complete onboarding steps to make the desktop application function as expected. Start time: Wednesday, April 8, 2026, at 6:45 AM UTC Next update by: Wednesday, May 6, 2026, at 3:30 PM UTC

  3. monitoring May 06, 2026, 02:37 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. Current status: We're validating a fix to address the underlying issue. Due to the complexity of the deployment, the validation is taking longer than initially anticipated. Once the fix is finalized, we’ll confirm the update in our internal test environment to ensure it doesn’t introduce any regression, before progressing with a gradual rollout to the affected environment. We'll share an estimated completion timeline when one becomes available. Start time: Wednesday, April 8, 2026, at 6:45 AM UTC Next update by: Wednesday, May 13, 2026, at 3:30 PM UTC

  4. monitoring May 13, 2026, 03:15 PM UTC

    User impact: Users are unable to search, chat, or call users in Microsoft Teams Free. Current status: We've completed validations of our fix within our internal testing environment and have initiated a gradual rollout of our fix to affected users. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC

  5. monitoring May 20, 2026, 03:20 PM UTC

    User impact: Users are unable to search, chat, or call users in Microsoft Teams Free. Current status: We're monitoring our fix deployment to ensure it has saturated throughout the entire affected environment before validating this issue is resolved. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, May 20, 2026, at 5:30 PM UTC

  6. resolved May 20, 2026, 04:12 PM UTC

    User impact: Users may have been unable to search, chat, or call users in Microsoft Teams Free. Final status: We've determined that a recent service update introduced the problem for the Microsoft Teams Free new user onboarding flow and caused new accounts to skip this flow entirely and appear as "unknown user." These affected "unknown" users were marked as non-searchable accounts, which resulted in impact. We've validated that our configuration change fix to correct this error has fully deployed throughout the affected environment and has successfully remediated all impact. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC End time: Wednesday, May 20, 2026, at 12:02 PM UTC This is the final update for the event.

Read the full incident report →