O365 Down (06-04-2018) UK, Europe & Asia

Well what a great Friday this is turning in to:

First of all I was chucked out of One Drive, then all my other O365 reliant services.

Users take to Twitter:

Slightly compounded by the inability to login to the Admin Centre.

Again after an update more tweets:

https://twitter.com/Office365Status/status/982191898902212615

Hits: 160

2 thoughts on “O365 Down (06-04-2018) UK, Europe & Asia”

  1. According to Microsoft, everything is now resolved.

    https://twitter.com/Office365Status/status/982233277304979456

    There are still some grumblings on Twitter about the lack of informative information, especially for those peeps that have to report to their Line Managers or bosses about what happened, and how it can be prevented.

    In some cases, this is a good argument for “on-premises first”.

    It may seem like an insignificant amount of time to be without the service, but when you rely solely on cloud services, and certainly if they are critical to the operation of your business, these can be troubling times.

  2. MO133518 – Can’t sign in
    Status:Service restored
    User impact:Users may have been unable to access the Office 365 service.
    Latest message:Title: Can’t sign in

    User Impact: Users may have been unable to access the Office 365 service.

    More info: Users may have been unable to sign in to Exchange Online, SharePoint Online, Skype for Business, Intune, Power BI, Microsoft Teams, Yammer and the Office 365 portal.

    Admins affected by this issue may not have had access to the Admin center. However, updates were provided on https://status.office.com and via the twitter handle @Office365Status.

    Final status: A subset of infrastructure that handles authentication requests became degraded, causing user sign in failures. We recovered the affected infrastructure to mitigate impact and monitored the service to confirm resolution.

    Scope of impact: This issue could have potentially affected any of your users if they were routed through the affected infrastructure.

    Start time: Friday, April 6, 2018, at 8:30 AM UTC

    End time: Friday, April 6, 2018, at 11:30 AM UTC

    Preliminary root cause: A subset of infrastructure that handles authentication requests became degraded.

    Next steps:
    – We’re analyzing performance data and trends on the affected systems to help prevent this problem from happening again.

    We’ll publish a preliminary post-incident report within 48 hours.

Leave a Reply