Vendor record
Azure Identity
Checked
Front door check counts and Azure Identity’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Azure Identity endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- login.microsoftonline.com
- Scope
- entra-idNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Azure Identity product, region or your app worked.
How we count front door checksAzure Identity says
Incident posts from Azure Identity’s status page, with its titles, impact levels and times. They say what Azure Identity chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
Azure publishes its status as an RSS feed with no per-service breakdown, so incidents shown here are Azure-wide rather than specific to this product. We do not guess which product an Azure incident touched.
12
incidents Azure Identity posted, last 180 days
Median recorded duration: 1h 27m. From 12 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Active -Azure Data Factory – Pipeline/Activity Failures and Timeouts – UK South
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(1h 27m)
Active -Azure Data Factory – Pipeline/Activity Failures, Delays & Timeouts – UK South
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(11m)
Active - Multiple services experiencing connectivity issues in multiple regions
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(6h 5m)
Active - ExpressRoute Gateway - Multiple services experiencing connectivity issues in multiple regions
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(2h 50m)
Active - Azure ExpressRoute Gateway service impacting event in multiple Azure Regions
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(2h 30m)
7 older records
Observing improvements - Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(9h)
Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(7h 10m)
Azure OpenAI and Foundry agent Service intermittent request failures and increased latency
MinorAzure Identity’s postStarted, per Azure Identity
Closed in our record(5h)
Active - Network Infrastructure impacting event in East US
MinorStarted, per Azure Identity
Closed in our record(16m)
Active -Multiple Service impacted affecting West US Regions
MajorStarted, per Azure Identity
Closed in our record(15m)
Investigating- Issues in Southeast Asia
MajorStarted, per Azure Identity
Closed in our record(17m)
Active -Azure Portal access issues affecting Australia Regions
MajorStarted, per Azure Identity
Closed in our record(22m)
Your code, your dependencies
See which of your code paths call Azure Identity
Connect GitHub or GitLab to find where your public or private repository uses Azure Identity. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Azure Identity status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Azure Identity currently down?
Azure Identity's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Azure Identity last have an outage?
The most recent closed incident record began 8 days ago and spans 1h 27m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Azure Identity?
No. CheckUpstream checks Azure Identity’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Azure Identity in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Azure Identity?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.