M365 Service Status (3 degradations at 2025-01-25 11:17)
↑Return_to_index
Some users’ Microsoft Teams desktop client intermittently crashes
Start Time: 2024-12-17 11:24(JST)
Last Update: 2025-01-25 05:03(JST)
Next Update By: 2025-01-28 01:00(JST)
Status: Service Degradation
Affected Service: Microsoft Teams
Users may see a “We’ve run into an issue” error message. Affected
users who have access to the Microsoft Teams web app can leverage this as a
workaround.
↑Return_to_index
Users can’t access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
Start Time: 2025-01-15 02:18(JST)
Last Update: 2025-01-16 07:46(JST)
Next Update By: 2025-01-22 04:30(JST)
Status: Service Degradation
Affected Service: Microsoft Copilot (Microsoft 365)
When users select the Copilot app from the sidebar in the Microsoft
Teams classic, they receive an error which states the following:
“Sorry, we ran into a problem. Please reload or try again later.”
↑Return_to_index
Users may be unable to share their Outlook calendars externally across any Exchange Online connection method
Start Time: 2024-11-28 09:00(JST)
Last Update: 2025-01-16 06:58(JST)
Next Update By: 2025-01-16 08:00(JST)
Status: Service Degradation
Affected Service: Exchange Online
↑Return_to_index
Some users’ searches may fail and provide no results in the Outlook desktop client and Outlook on the web
Start Time: 2024-10-30 03:11(JST)
Last Update: 2025-01-25 11:14(JST)
Status: Service Restored
Affected Service: Exchange Online
↑Return_to_index
Users on the new Outlook desktop experience can’t open any attachments and receive an error
Start Time: 2025-01-18 05:00(JST)
Last Update: 2025-01-25 02:49(JST)
Status: Service Restored
Affected Service: Exchange Online
The error message stated, “An error occurred while opening the file.
Please try again”. Users could still preview the attachments and can also
download the attachments to open the file through their program of choice to
circumvent this issue. Users could also leverage the old Outlook desktop
experience or Outlook on the web as another alternative to open attachments.
↑Return_to_index
We’re looking into a potential problem impacting Microsoft 365 services in the Germany and Poland regions
Last Update: 2025-01-24 08:26(JST)
Status: False Positive
Affected Service: Microsoft 365 suite
↑Return_to_index
Users within Microsoft 365 groups without an owner may have been unable to take ownership
Start Time: 2024-11-26 09:00(JST)
Last Update: 2025-01-24 04:57(JST)
Status: Service Restored
Affected Service: Exchange Online
Users within a group without an owner were sent an email message
asking if they’d like to take ownership.
A 500 HTTP error response was presented if a user selects “yes” or “no” within
the message.
As a workaround users could reach out to admins to manually set the owner of the
groups.
↑Return_to_index
Some users may have been unable to update desktop flows in Microsoft Power Automate
Start Time: 2025-01-23 11:09(JST)
Last Update: 2025-01-24 12:04(JST)
Status: Service Restored
Affected Service: Microsoft Power Automate in Microsoft 365
↑Return_to_index
We’re looking into a potential problem impacting Microsoft Teams and Microsoft 365 services in the Japan region
Last Update: 2025-01-23 09:17(JST)
Status: False Positive
Affected Service: Microsoft 365 suite
↑Return_to_index
We’re looking into a potential problem impacting Microsoft Teams and Microsoft 365 services in the Japan region
Last Update: 2025-01-23 03:07(JST)
Status: Investigating
Affected Service: Microsoft 365 suite
↑Return_to_index
Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
Start Time: 2024-11-07 04:18(JST)
Last Update: 2025-01-23 09:34(JST)
Next Update By: 2025-01-30 08:30(JST)
Status: Extended Recovery
Affected Service: Microsoft Teams
If you’re using RichTextBlock in your adaptive cards with TextRuns
that have their selectAction property set, unwanted line breaks show up. Your
card, however, remains fully functional.
↑Return_to_index
Some users may be unable to authenticate to Microsoft 365 apps
Start Time: 2025-01-23 04:16(JST)
Last Update: 2025-01-23 09:29(JST)
Status: Service Restored
Affected Service: Microsoft 365 suite
Affected users may have seen issues while using Single Sign On (SSO)
applications. When authenticating with SSO, impacted users may have received a
message stating, “Something went wrong… Authentication error”.
↑Return_to_index
Users’ inbound calls to Microsoft Teams call queues, auto-attendants, or voicemail may fail
Start Time: 2025-01-23 04:34(JST)
Last Update: 2025-01-23 06:14(JST)
Status: Service Restored
Affected Service: Microsoft Teams
Users may have experienced successes after one or more retries.
↑Return_to_index
Some users may be unable to launch Microsoft Teams on Mac devices post auto-update
Start Time: 2024-12-11 09:00(JST)
Last Update: 2025-01-17 10:34(JST)
Status: Service Restored
Affected Service: Microsoft Teams
Some users may have received a popup stating, “The application bundle
was corrupted”. Users could run the application directly from the applications
folder and ignore this popup to avoid this issue. Users could also delete the
application bundle from the applications folder and install Microsoft Teams
again to resolve impact.
Impact was specific to Microsoft Teams for Mac users leveraging macOS versions
13.7.2, 14.7.2, and 15.2.
↑Return_to_index
Some users’ Microsoft 365 applications may be unexpectedly crashing on Windows Server 2016 devices
Start Time: 2025-01-09 08:09(JST)
Last Update: 2025-01-17 04:10(JST)
Status: Service Restored
Affected Service: Microsoft 365 suite
While we’re focused on mitigation, we recommended that affected
customers force an update to roll back to Version 2411 (Build 18227.20162),
which could also have been obtained by following these steps:
1. Open Command Prompt as Administrator
2. Run the following command: cd “C:\Program Files\Common Files\microsoft
shared\ClickToRun”
3. Run the following command: officec2rclient.exe /update user
