Okta outage, 3 October 2024
O365 OIN Provisioning Setup Issue
- Started
- Resolved
- 10 Oct 2024, 19:22 UTC (after 6 days)
- Impact
- Minor
- Affected
- Core Platform
Is this still happening?
No. Okta marked this incident resolved on 10 Oct 2024, 19:22 UTC, 6 days after it began.
Right now: Okta reports degraded performance on some systems. (as of 30 Oct, 12:16 UTC) Live Okta status
Last update from Okta
Timing: Incident start: October 3, 2024, at 6:38 PM PDT Incident resolved: October 10, 2024, at 3:22 PM PDT Detection: Customers began reporting that they were unable to save their Office 365 application in Okta when “User Sync” or “Universal Sync” was selected for provisioning. Impact: Customers would receive a 400 error when attempting to save an Office 365 application after completing the Microsoft consent page. Root Cause: Okta Engineering has confirmed that impacted customers had Microsoft Entra conditional access policy enforcing MFA for the service account used by Okta’s provisioning service. Accounts used for provisioning must not have MFA or require any manual intervention. Remediat...
Similar Okta incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 7 h 34 min
-
, resolved after 1 h 20 min
-
, resolved after 42 min
-
, resolved after 36 min
-
, resolved after 5 h 4 min