{"id":9333,"date":"2022-02-03T12:51:28","date_gmt":"2022-02-03T12:51:28","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/03\/update-takes-down-microsoft-365-admin-portal-the-register\/"},"modified":"2022-02-03T12:51:28","modified_gmt":"2022-02-03T12:51:28","slug":"update-takes-down-microsoft-365-admin-portal-the-register","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/03\/update-takes-down-microsoft-365-admin-portal-the-register\/","title":{"rendered":"Update takes down Microsoft 365 Admin Portal \u2022 The Register"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Microsoft’s legendary approach to quality was demonstrated this morning<\/a> as the Microsoft 365 Admin Portal fell over.<\/p>\n

Without a hint of irony, the company posted<\/a>: “We’ve identified a recent service update designed to improve user experience is causing impact.”<\/p>\n

The impact in question was an inability to access the admin portal, something unlikely to affect an end user pootling around in Excel, but a huge headache for an administrator trying to manage their tenant.<\/p>\n

\"Microsoft<\/a><\/p>\n

Microsoft 365 Portal problems<\/p>\n<\/div>\n

The problem appears to be specific to users in Europe, the Middle East and Africa, according to Microsoft (although some users in North America<\/a> and Asia<\/a> reported issues).<\/p>\n

Other services, such as the Teams Admin Center also dropped over in sympathy, although Teams itself continued functioning. And there was the additional irony that to view Microsoft 365 Service Health from the somewhat sluggish status.office.com, one was directed to portal.office.com, which was… a little poorly when we checked it.<\/p>\n

Microsoft confirmed the fault by 0936 UTC this morning. An excruciating 45 minutes later, the company was hurriedly backing out of whatever it had done to its systems.<\/p>\n

In the latest update to its admin portal, Microsoft said: \u201cThe revert of the update is taking longer than expected to complete. We\u2019re continuing our efforts to resolve the issue by also manually restarting the affected infrastructure to expedite the recovery.\u201d<\/p>\n

\n