Posts about:
On April 28, 2022, at ~10:04 AM EST, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to make or receive calls using Microsoft Teams.
For IT pros or system admins with Microsoft admin center access, the incident number to reference the issue was TM365276. This service incident comes 1 day after a minor service incident involving Microsoft Sway.
On April 27, 2022, at ~8:59 AM EST, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue involving Microsoft Sway.
For IT pros or system admins with Microsoft admin center access, the incident numbers to reference the issue were MO364969 and SW364924. The apparent issue involved users not being able to either access or create within Sway.
On April 18th, 2022, at ~7:07 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to open files in SharePoint Online, OneDrive, and Teams.
For IT professionals and system admins with Microsoft admin center access, the service incident numbers to reference were SP360511, OD360523, and TM360526.
On April 7, 2022, at ~6:30 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to view data in the News article webpart within SharePoint Online.
For IT professionals and system admins with Microsoft admin center access, the issue # was SP354364. It should be noted that the last service incident reported @MSFT365status was on March 3rd, and that's 4+ weeks without any service incidents. (That is, no service incidents as reported by @MSFT365status.)
On March 3, 2022, at ~09:02 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident involving Microsoft 365 Admin Center access issues.
Initially, Microsoft provided no incident # for system admins and IT pros to reference within the Microsoft Admin Center, because access to the Admin Center was the issue at hand. Instead, Microsoft directed impacted users to refence the Microsoft 365 health status site, status.office.com.
On March 2, 2022, at ~05:32 pm UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident involving SharePoint Online and OneDrive for Business (and possibly other services). Microsoft also clarified that the service incident was contained to customers in New Zealand.
For system admins and IT pros with Microsoft Admin Center access, Microsoft provided the following incident #: MO337921.
On February 25, 2022, at ~09:37 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident in which users were experiencing issues within the Health section of the Admin Center.
Initially, Microsoft provided no incident number, since system admins and IT professionals who may have been unable to access the Microsoft Admin Center would be unable to reference any incident number for further details. Instead, Microsoft advised any users impacted to check status.office.com.
On February 24, 2022, at ~01:31 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident impacting Microsoft Forms.
For system admins and IT professionals with Microsoft Admin Center access, the incident reference number was FM335798. Where @MSFT365status was deficient with details, the Admin Center likely had more detailed information.
On February 21, 2022, at ~03:58 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident impacting Microsoft Planner, Tasks, and Teams.
On February 3, 2022, at ~04:36 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users (in Europe) were unable to access the Microsoft 365 admin portal.
Initially, Microsoft provided no incident # for users to reference, as any user experiencing issues may not have been able to access the admin portal to gather additional information. In its place, Microsoft was directing impacted users to access status.office.com for updated information as to the service incident.