Custom status page domain

Why you need it

Your status page is the page customers screenshot, link in tickets, and forward to their boss. When the hostname in the address bar isn't yours, it whispers "third-party tool" at exactly the moment you most need to look in control.

• Your brand in the address bar. status.acme.com instead of a shared subdomain — the page reads as part of your product, not as a vendor we rented you.
• Zero certificate work, ever. Azure issues and auto-renews a managed TLS certificate scoped to your hostname. No uploads, no calendar entries, no 3 AM expiry emails.
• Three steps, then it runs itself. Enter the hostname, drop in two DNS records (CNAME + TXT), click Verify, flip Activate — you're live in under a minute.
• The old URL keeps working. Bookmarks, Slack links, help-centre footers your team posted last quarter — nothing breaks the day you cut over.
• Multi-product? Multi-domain. Run one custom-domain page per product line, each with its own hostname, probes, and brand.

Where it pays off

The day custom domains become non-negotiable:

• You added the status page to your help-centre footer. Customers click through expecting your product; the hostname has to match.
• Enterprise prospects are reviewing your SLA. A status page on your own domain reads as a first-party surface; a shared subdomain reads as a tool you bought last week.
• You sell multiple products. One custom hostname per product line keeps each story clean and on-brand.
• Partner-only or private surfaces. Bind a hostname behind a VPN resolver and the page is effectively invisible from the public internet.

Not the right tool when: you can't (or don't want to) edit DNS on your primary domain — the default URL works perfectly and saves you the registrar trip.

Related

• Status pages
• Custom branding
• Multi-language pages & reports
• Incidents & alerts