xdansmith, the five improvements mentioned in the post were all complete when Nadim posted in December. Since publishing the post, we’ve continued work on architectural, operational, and infrastructure reliability initiatives aligned with the principals described here: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fadvancing-azure-active-directory-availability%2F&data=04%7C01%7CBen.Siler%40microsoft.com%7Cd8cf93ed6931497b17cc08d8eafc21cd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637517715913228296%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yuud4rzwvLTw7RnSqfxJfqI3WuZaZmOfwbJnPxiD4Es%3D&reserved=0. We know our customers rely on Azure AD for vital apps, so resilience and security are our top priorities. We’ll follow up later this year with another post to let you know what improvements we’ve completed and what we’re working on.
For a detailed description of the incident this week, you can see the RCA on the https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstatus.azure.com%2Fen-us%2Fstatus%2Fhistory%2F&data=04%7C01%7CBen.Siler%40microsoft.com%7Cd8cf93ed6931497b17cc08d8eafc21cd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637517715913228296%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QRw8G%2BUHo4PnMzO%2BiNUhGXHKwo5lLEWOg1TSuXnSRk4%3D&reserved=0 (posted on 3/15 with tracking ID LN01-P8Z).