Microsoft’s own authority issues OV certificates for Microsoft’s services only. Its value is microsoft.com — but the certificates Azure gets for customers’ domains come from DigiCert, and need digicert.com.
| Run by | Microsoft Corporation (Microsoft PKI Services), United States |
| CAA value | microsoft.com |
| CAA parameters | accounturi and validationmethods — it “may” limit issuance by them |
| Cost | Not sold: Microsoft’s own services only |
| Certificates | OV only |
| Longest certificate | 200 days |
| Issuer names on its certificates | Microsoft Azure RSA TLS Issuing CA 03, Microsoft TLS G1 RSA CA 01 |
May Microsoft issue for your domain?
Enter a domain or hostname: we read its CAA records as Microsoft must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for Microsoft
Published on your domain, this lets Microsoft issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "microsoft.com"
An issue record covers wildcard certificates too. To let Microsoft issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "microsoft.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
It processes issue, issuewild and iodef (mailto: and https: only).
What changed
- 2025 — New Microsoft TLS RSA and ECC Root G2, cross-signed by DigiCert.
- 2025–2026 — Azure’s managed certificates moved to DigiCert’s G2 and G3 roots, with server authentication only.
Worth knowing
- Azure App Service, Front Door, Container Apps and Azure’s other managed certificates are DigiCert’s: Microsoft tells customers to publish 0 issue “digicert.com”, and says the issuer and root can change at any time.
Questions
Does Azure need microsoft.com in my CAA records?
No — Azure’s managed certificates are issued by DigiCert, so it needs digicert.com. microsoft.com is for Microsoft’s own first-party certificates.
Sources
Checked on 27 September 2026 against these official sources:
- Microsoft PKI Services repository — microsoft.com
- Azure Certificate Authority details — learn.microsoft.com
- Install a TLS/SSL Certificate for Your App — learn.microsoft.com
- Domains — Azure Front Door — learn.microsoft.com