Microsoft Cloud PKI for Intune is a PKI-as-a-service solution that issues and manages user and device authentication certificates for Intune-managed endpoints. It provides a two-tier certification authority (CA) hierarchy hosted by Microsoft, along with a cloud-hosted Simple Certificate Enrollment Protocol (SCEP) service, all managed from the Intune admin center. With Cloud PKI for Intune, organizations can deploy certificates for Wi-Fi, VPN, email, and other authentication scenarios without deploying Active Directory Certificate Services (AD CS), the Network Device Enrollment Service (NDES), or the Intune Certificate Connector on-premises.
Last updated: November 9, 2026
How Cloud PKI for Intune Works
Cloud PKI for Intune combines a CA service with a certificate registration authority. The enrollment process works as follows.
- An administrator creates a root and issuing CA in the Intune admin center, then assigns trusted certificate and SCEP certificate profiles to users or devices.
- The device checks in with Intune, receives the profiles, and generates a key pair and certificate signing request (CSR). The private key is created on the device and never leaves it.
- The device sends the CSR and an encrypted, signed SCEP challenge to the Cloud PKI for Intune SCEP service, which validates that the request comes from an enrolled, managed device and matches the SCEP profile.
- The issuing CA signs the certificate and returns it to the device.
Cloud PKI for Intune supports Windows, macOS, iOS/iPadOS, and Android. Devices must be enrolled in Intune, and the platform must support the Intune SCEP certificate profile. The join type doesn’t matter: Entra joined, hybrid Entra joined, and personally owned enrolled devices are all supported.
Advantages
Cloud PKI for Intune offers several significant advantages over a traditional on-premises AD CS deployment, including the following.
No Infrastructure
The most obvious advantage is that there’s no CA infrastructure to deploy or manage. Although installing AD CS isn’t difficult, operating a CA securely over time is challenging. Cloud PKI for Intune CAs use signing keys protected by Azure Managed HSM at no additional cost and with no Azure subscription required, removing the expense and complexity of on-premises hardware security modules (HSMs).
Cloud-Hosted SCEP
Removing the need to deploy NDES and the Intune Certificate Connector is a welcome change. NDES is notoriously difficult to configure, secure, and troubleshoot. Cloud PKI for Intune includes a highly available, cloud-hosted SCEP service for each issuing CA.
Certificate Lifecycle and Revocation
Cloud PKI for Intune automates certificate issuance and renewal for Intune-managed users and devices. Intune revokes certificates when a device is retired or wiped, or when the certificate profile no longer applies, and administrators can revoke certificates manually from the Intune admin center. Intune hosts the certificate revocation list (CRL) and Authority Information Access (AIA) endpoints for each CA.
Reporting
Administrators can view active, expired, and revoked certificates for each issuing CA in the Intune admin center.

Selecting View all certificates displays a detailed list of every certificate the CA has issued.

Bring Your Own CA (BYOCA)
With BYOCA, administrators can create a Cloud PKI for Intune issuing CA that chains to an existing private root CA, such as an on-premises AD CS root. This is ideal when AD CS already issues certificates to domain-joined clients and servers. BYOCA extends the existing hierarchy to the cloud, so Cloud PKI for Intune handles Intune-managed endpoints while AD CS continues to serve everything else.
Limitations
Although Cloud PKI for Intune has many advantages, there are some important limitations to consider.
RSA Only
Cloud PKI for Intune supports RSA keys only, with key sizes of 2048, 3072, or 4096 bits. Elliptic curve (ECC) keys aren’t supported, and neither are post-quantum algorithms such as ML-DSA, which AD CS on Windows Server 2025 now supports. See Post-Quantum Cryptography (PQC) in the Enterprise for more information.
Intune-Managed Devices Only
Cloud PKI for Intune issues certificates only to Intune-enrolled devices using SCEP. It can’t issue certificates to servers, network devices, or unmanaged endpoints, and it doesn’t support ACME or other enrollment protocols. Most organizations still need another CA, such as AD CS, for server and infrastructure certificates.
Fixed Configuration
Root and issuing CAs can’t be reconfigured after deployment. Because Cloud PKI for Intune CAs don’t support the Any Purpose EKU (2.5.29.37.0), all required EKUs must be defined when the CA is created. If a new EKU is needed later, a new hierarchy (root and issuing CA) must be deployed. In addition, any variable used in a certificate subject name must exist on the corresponding Entra user or device object, or the certificate isn’t issued.
CRL Only
Cloud PKI for Intune publishes CRLs but doesn’t provide an Online Certificate Status Protocol (OCSP) responder. CRLs are valid for seven days and are refreshed every 3.5 days, so make sure relying parties can reach the Intune-hosted CRL endpoints.
Trial Keys
CAs created during a Cloud PKI for Intune trial use software-backed keys, and they can’t be converted to HSM-backed keys after you purchase a license. Plan to create new CAs for production.
Licensing
Licensing for Cloud PKI for Intune changed significantly in 2026. It’s available in the following ways.
- Microsoft 365 E5. Since July 1, 2026, Cloud PKI for Intune is included in Microsoft 365 E5 at no additional cost. It isn’t included in Microsoft 365 E3.
- Standalone add-on. The Cloud PKI for Intune add-on is available for organizations with Intune Plan 1, at a list price of $2.00 per user per month with an annual commitment.
- Intune Suite. Cloud PKI for Intune is also included in the Microsoft Intune Suite.
For organizations licensed for Microsoft 365 E5, cost is no longer a barrier to adoption.
Is Cloud PKI for Intune Right for You?
Cloud PKI for Intune is an excellent choice for issuing user and device authentication certificates to Intune-managed endpoints, especially for cloud-first organizations that want to avoid NDES and on-premises CA infrastructure. Certificates are strong, phishing-resistant credentials, and Cloud PKI for Intune makes them easier to deploy. They can also be used to sign in to Microsoft Entra ID with Microsoft Entra certificate-based authentication (CBA). However, it doesn’t replace AD CS for server certificates, non-Intune devices, ECC or post-quantum algorithms, or scenarios that require OCSP or flexible CA configuration. Many organizations will benefit from a hybrid approach, using BYOCA to chain Cloud PKI for Intune to their existing AD CS hierarchy. Learn more about digital certificates for strong, phishing-resistant authentication and my enterprise PKI consulting services.
Related Articles
I’ve written extensively about Cloud PKI for Intune. The following articles provide additional detail.
- Microsoft Intune Cloud PKI
- Microsoft Intune Cloud PKI and Active Directory
- Microsoft Intune Cloud PKI and Certificate Templates
- Microsoft Cloud PKI for Intune SCEP URL
- Delete a Cloud PKI for Intune Certificate Authority
- Always On VPN and Cloud PKI for Intune Error 853
- Strong Certificate Mapping for Intune PKCS and SCEP Certificates
- Cloud PKI for Microsoft Intune on RunAs Radio
Want to go deeper? Cloud PKI for Intune is covered in my Intune Certificates Training: PKCS, SCEP, NDES, and Cloud PKI course.
Additional Information
Overview of Microsoft Cloud PKI for Microsoft Intune (Microsoft Learn)
Advanced Microsoft Intune Capabilities Now Available in Microsoft 365 (Microsoft Tech Community)
Simple Certificate Enrolment Protocol (RFC 8894)
Enterprise PKI with Microsoft Active Directory Certificate Services
Enterprise PKI Consulting: Microsoft AD CS and Cloud PKI
Start a Conversation
Considering Cloud PKI for Intune, planning a hybrid deployment with AD CS, or migrating from NDES? Tell me about your environment, and I’ll follow up, typically within one business day.








