How Many Intune Profiles Are Needed for Cloud PKI User Certificates?
You have a Microsoft 365 E5 subscription and use Microsoft Intune. You plan to implement a Microsoft Cloud PKI solution that will deploy personal user certificates to all Windows devices. What is the minimum number of configuration profiles required to support the solution?
Community Votes
52% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests whether you separate the Cloud PKI service provisioned in the Intune admin center from the device configuration profiles that actually deliver certificates — the trap is counting the root and issuing CA as extra profiles.
Microsoft Cloud PKI in Intune deploys personal user certificates to Windows devices with a trusted certificate profile plus a SCEP certificate profile. This page establishes that the minimum number of configuration profiles is two (B), not three.
Choosing 3 (C) by counting one profile for the root CA, one for the issuing CA and one for the SCEP request; the Cloud PKI service itself and its issuing CA chain are not separate configuration profiles.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The Microsoft Cloud PKI (root CA plus issuing CA) is created under Tenant administration in the Intune admin center, so it is a service resource and never counts as a configuration profile. To get a personal user certificate onto every Windows device you then need exactly two profiles: a trusted certificate profile that deploys the Cloud PKI root certificate so devices trust the chain, and a SCEP certificate profile that requests and installs the personal user certificate and references the trusted profile for its root. The issuing CA is returned in the SCEP response chain, so no third profile is required for the minimum deployment. That gives a minimum of two configuration profiles, matching option B.Why the Other Options Are Wrong
Option A (1) fails because a SCEP profile alone leaves devices without a trusted root, so the issued certificate cannot chain to a trusted authority and enrollment breaks. Options C (3) and D (4) over-count: they treat the Cloud PKI service, the root CA and the issuing CA as separate profiles even though the Cloud PKI is configured in the admin center and the issuing CA is part of the delivered chain. The related rule about one trusted certificate profile "for each platform" (raised by GeorgeMar) only adds profiles when you issue Cloud PKI SCEP certificates to Android, iOS/iPadOS or macOS as well — the scenario here is Windows only, so it does not raise the count.Community Comment Notes
Friscini points directly at the Microsoft Learn step "create certificate profiles" under the Cloud PKI configure-CA article, which is the authoritative source for this count. neothwin and Alboo007_rs007 both land on two by splitting the work into a trusted certificate profile for the Cloud PKI root and a SCEP certificate profile that requests the personal certificate, the same reasoning used here. SR96 argues the other way with "You need Root, Issusing and SCEP hence why it is 3", and AleFCI1908 also votes C, which is exactly the service-versus-profile confusion the question is designed to catch. The vote split (52 for B versus 48 for C) shows how close this trap is, which is why the answer must be derived from the Intune object model rather than from the majority.Official Reference
Exam Strategy
Anchor on the Intune object model: anything you create under Tenant administration (the Cloud PKI itself) is a service, and only objects created under Devices > Configuration profiles count toward the question. Then ask what a Windows device minimally needs — trust in the chain plus one personal certificate request — which is two profiles.
Frequently Asked Questions
Why isn't the Microsoft Cloud PKI itself counted as a configuration profile?
Cloud PKI is provisioned under Tenant administration and creates the root and issuing CAs as a service, not as a device configuration profile, so it adds nothing to the profile count.
Why is a third profile for the issuing CA not required?
The SCEP certificate profile references the trusted certificate profile and returns the issuing CA in the issued chain, so a separate trusted profile for the issuing CA is not part of the minimum deployment.
Related Analysis
Practice All MD-102 Questions
Access 92 questions with complete answers and detailed explanations.
View Full MD-102 Practice Test →