← Back to Okta History
unknown✓ Resolved
Resolved Service Disruption
Status
resolved
Duration
Duration unavailable
Updates
1
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
Resolved: An issue impacting authentication and system responsiveness for a subset of end-users and administrators accessing Microsoft Office 365 has subsided. Further investigation of the issue found the errors were correlated with a service degradation reported by Microsoft (Incident MO147606). Further information is available from Microsoft via https://status.office365.com.
-------------------------------
Root Cause Analysis: On Sept 4th, 2018, at approximately 6:00am PDT, Okta began receiving reports that end-users were experiencing delays and errors while attempting to authenticate to Office 365 and related services hosted by Microsoft. Upon further investigation the service disruption began at approximately 2:29am PDT and appeared to be localized to customers with Office 365 and related resources hosted within Microsoft’s South-Central US datacenter. The service disruption was reported as fully resolved by Microsoft on Sept 7th at 1:40am PDT. Throughout the duration of the incident, Okta-provided services continued to function normally.
Microsoft reports a severe weather event, including lightning strikes, occurred near one of the South-Central US datacenters. This resulted in a power voltage increase which impacted cooling systems. Automated datacenter procedures designed to ensure data and hardware integrity went into effect and critical hardware entered a structured power down process.
Please refer to your [Office 365 Service Health](https://portal.office.com/adminportal/home#/servicehealth) dashboard for further details regarding this incident and mitigating steps.
📊 TECHNICAL DETAILS
Internal ID
0470a743-0018-40c8-875a-73833edd8718
External ID
https://www.salesforce.com/a9C0Z0000008PTrUAM
🕐 First reported
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
Duration unavailable
Total Duration
1
Recorded Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed