Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.3.3. Microsoft Cloud PKI

💡 First Principle: Certificate-based Wi-Fi and VPN are more secure than passwords, but traditionally they needed a certificate authority, an NDES server and a connector on premises — infrastructure many cloud-first organizations no longer want to run. Cloud PKI moves the whole chain into Intune, so the design questions become how many CAs you need, which one anchors trust, and which profiles each device must receive to trust and request a certificate.

What it replaces. Cloud PKI issues, renews and revokes certificates with no on-premises CA, no NDES and no Intune Certificate Connector. It supports Intune-enrolled Android, iOS/iPadOS, macOS and Windows devices, issuing leaf certificates only through the SCEP certificate profile.

The hierarchy. Cloud PKI creates a two-tier hierarchy: a root CA and an issuing CA, both in the cloud, and each issuing CA gets its own cloud SCEP service. If your organization already has a private PKI, bring your own CA (BYOCA) anchors a Cloud PKI issuing CA to your existing root, such as Active Directory Certificate Services.

The three-CA limit. A tenant can have at most three CAs, licensed or trial, and the root, any Cloud PKI issuing CAs and any BYOCA issuing CAs all count. Microsoft's examples: one root plus two issuing CAs; one root, one issuing and one BYOCA; or three BYOCAs. So a tenant with one root and two issuing CAs is full — adding a BYOCA would make four. Older material sometimes quotes a different number; use three.

Creating CAs. At Tenant administration > Cloud PKI > Create, you create the root first. Root validity is 5–25 years; issuing CA validity is 2–10 years and can't exceed the root's. Keys are RSA 2048, 3072 or 4096. An issuing CA can only use extended key usages defined on its root, and the overly broad Any Purpose EKU isn't allowed. CA properties can't be edited after creation, so adding an EKU later means creating a new CA — and spending one of your three slots. Licensed CAs use Azure Managed HSM keys; CAs created during a trial use software keys and stay that way after you buy a license.

What devices need. For each platform, deploy three profiles: a trusted certificate profile for the root CA, a trusted certificate profile for the issuing CA, and a SCEP certificate profile that points to the issuing CA. In the SCEP profile, Root Certificate links to the root's trusted certificate profile, and the SCEP server URL is the issuing CA's SCEP URI with the {{CloudPKIFQDN}} placeholder left exactly as it is. Don't mix NDES URLs with Cloud PKI URLs in one profile. The SCEP profile's EKU must exist on the issuing CA, or nothing is issued. During issuance the device creates the key pair itself; the private key never leaves the device. Every relying party that checks the certificate — a RADIUS server or VPN gateway — also needs the root and issuing CA certificates installed.

Revocation and lifecycle. Intune hosts each CA's CRL, valid for 7 days and republished every 3.5 days and on every revocation. CA actions are Pause (reversible; the CA stops issuing but still answers CRL requests), Revoke and Delete (both permanent), and a root can't be deleted until every issuing CA under it is deleted.

In-place renewal is new in 2026. An issuing CA becomes eligible at half its validity lifetime — a 4-year issuing CA after 2 years — or once expired. Renewal generates a new key pair in a staged CA you can test for up to 90 days; Activate promotes it and restores the original production SCEP URI, so existing SCEP profiles keep working unchanged.

⚠️ Exam Trap: Revoking a device's certificate in Cloud PKI doesn't stop it getting a new one. As long as the SCEP profile is still assigned to the device, Intune reissues the certificate at the next check-in; to block the device, remove the assignment as well.

Reflection Question: A tenant runs a Cloud PKI root and one issuing CA, and now needs certificates with a new extended key usage while also anchoring a second issuing CA to its existing ADCS root. Can it do both, and what constrains the plan?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned