FYI – I couldn’t post on the article’s web page, https://www.thurrott.com/cloud/microsoft-365/199710/microsoft-teams-is-down-and-users-arent-happy#, kept on getting error messages in Edge and Chrome, so I’m posting it here, because I believe this feedback can inform the reporting on the site and help someone that currently isn’t very familiar with Office 365.
Hello Mehedi,
I agree that there is a valid argument for a more transparent publically available status page that shows both possible outages on any tenants and known ones on all of them.
Unfortunately, the Microsoft web page you have in the article, https://status.office365.com/, isn’t supposed to do that by design, per https://docs.microsoft.com/en-us/office365/enterprise/view-service-health.
“You can view the health of Office 365, Yammer, Microsoft Dynamics CRM, and Microsoft Intune cloud services on the Office 365 Service health page in the admin center. If you are experiencing problems with a cloud service, you can check the service health to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting.
If you are unable to sign in to the service portal, you can use the service status page to check for known issues preventing you from logging into your tenant.”
Since the Thurrott.com people know Microsoft people, feel free to recommend they change how they communicate, but know that the product documentation is saying it is technically “Working as designed”.
I recommend to folks that they either (best option 1st):
So for example, first thing this morning Teams did not work for me. I immediately checked the service health status page in the admin portal and found it was a known issue. I then notified the other Office 365 folks that I work with about it, then monitored the status of the portal until it was resolved.
There are no conversations