Our services aren't available right now Azure Origin: Platform & cloud Last updated 13 Oct 2026

Azure Front Door: Our services aren't available right now (503/502 from Front Door)

Front Door couldn’t get a valid response from your origin — origin down, health probes failing, TLS/host header mismatch, or a timeout.

Exact message you may see Our services aren't available right nowWe're working to restore all services as soon as possibleFront Door 503
Seen on: Azure

Meaning

The page shows an x-azure-ref you can look up. Common: origin certificate name doesn’t match the origin host header, private link/origin firewall blocking Front Door, or responses exceeding the timeout.

Common causes

  • Origin unhealthy or probe path failing
  • Origin host header/certificate mismatch
  • Origin firewall not allowing AzureFrontDoor.Backend service tag
  • Response slower than origin timeout

⚡ Quick fix

  1. Check origin health and probe settings
  2. Set origin host header to a name the origin’s certificate covers
  3. Allow the AzureFrontDoor.Backend service tag / X-Azure-FDID check

Detailed fix by platform

Azure CLI

  1. az afd origin show -g rg --profile-name fd --origin-group-name og --origin-name app --query "{host:hostName,hostHeader:originHostHeader,enabled:enabledState}"

How to diagnose

  1. Reference — x-azure-ref in diagnostics logs
  2. Health — Origin health %
  3. TLS — Certificate CN/SAN vs host header

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

502 — HTTP 502 Bad Gateway (HTTP)502503 — HTTP 503 Service Unavailable (HTTP)503520 — Cloudflare Error 520: Web Server Returned an Unknown Error (Cloudflare)520522 — Cloudflare Error 522: Connection Timed Out (Cloudflare)522AADSTS500113 — AADSTS500113: No reply address is registered for the application (Azure)AADSTS500113AADSTS50020 — AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application (Azure)AADSTS50020The request could not be satisfied — CloudFront: 403 ERROR — The request could not be satisfied (AWS)The request could not…Our servi…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.