Use certificates for authentication in Microsoft Intune
Use certificates with Intune to authenticate your users to applications and corporate resources through VPN, Wi-Fi, or email profiles. When you use certificates to authenticate these connections, your end users won't need to enter usernames and passwords, which can make their access seamless. Certificates are also used for signing and encryption of email using S/MIME.
Intune supported certificates and usage
|Type||Authentication||S/MIME Signing||S/MIME encryption|
|Public Key Cryptography Standards (PKCS) imported certificate|
|PKCS#12 (or PFX)|
|Simple Certificate Enrollment Protocol (SCEP)|
To deploy these certificates, you’ll create and assign certificate profiles to devices.
Each individual certificate profile you create supports a single platform. For example, if you use PKCS certificates, you’ll create PKCS certificate profile for Android and a separate PKCS certificate profile for iOS. If you also use SCEP certificates for those two platforms, you’ll create a SCEP certificate profile for Android, and another for iOS.
General considerations when you use a Microsoft Certification Authority
When you use a Microsoft Certification Authority (CA):
To use SCEP certificate profiles, you must set up a Network Device Enrollment Service (NDES) server for use with Intune.
To use the following certificate profile types, you must install the Microsoft Intune Certificate Connector:
- SCEP certification profile
- PKCS certificate profile
To use PKCS imported certificates:
- Install the PFX Certificate Connector for Microsoft Intune.
- Export certificates from the certification authority and then import them to Microsoft Intune. See the PFXImport PowerShell project.
Deploy certificates by using the following mechanisms:
- Trusted certificate profiles to deploy the Trusted Root CA certificate from your root or intermediate (issuing) CA to devices
- SCEP certificate profiles
- PKCS certificate profiles
- PKCS imported certificate profiles
General considerations when you use a third-party Certification Authority
When you use a third-party (non-Microsoft) Certification Authority (CA):
To use SCEP certificate profiles:
- Set up integration with a third-party CA from one of our supported partners. Set up includes following the instructions from the third-party CA to complete integration of their CA with Intune.
- Create an application in Azure AD that delegates rights to Intune to do SCEP certificate challenge validation.
PKCS imported certificates require you to install the PFX Certificate Connector for Microsoft Intune.
Deploy certificates by using the following mechanisms:
Supported platforms and certificate profiles
|Platform||Trusted certificate profile||PKCS certificate profile||SCEP certificate profile||PKCS imported certificate profile|
|Android device administrator|
- Fully Managed (Device Owner)
- Dedicated (Device Owner)
- Work Profile
|Windows Phone 8.1|
|Windows 8.1 and later|
|Windows 10 and later|
Export the trusted root CA certificate
To use PKCS, SCEP, and PKCS imported certificates, devices must trust your root Certification Authority. To establish trust, export the Trusted Root CA certificate, and any intermediate or issuing Certification Authority certificates, as a public certificate (.cer). You can get these certificates from the issuing CA, or from any device that trusts your issuing CA.
To export the certificate, refer to the documentation for your Certification Authority. You’ll need to export the public certificate as a .cer file. Don't export the private key, a .pfx file.
You’ll use this .cer file when you create trusted certificate profiles to deploy that certificate to your devices.
Create trusted certificate profiles
Create a trusted certificate profile before you can create a SCEP, PKCS, or PKCS imported certificate profile. Deploying a trusted certificate profile ensures each device recognizes the legitimacy of your CA. SCEP certificate profiles directly reference a trusted certificate profile. PKCS certificate profiles don’t directly reference the trusted certificate profile but do directly reference the server that hosts your CA. PKCS imported certificate profiles don't directly reference the trusted certificate profile but can use it on the device. Deploying a trusted certificate profile to devices ensures this trust is established. When a device doesn’t trust the root CA, the SCEP or PKCS certificate profile policy will fail.
Create a separate trusted certificate profile for each device platform you want to support, just as you'll do for SCEP, PKCS, and PKCS imported certificate profiles.
To create a trusted certificate profile
Sign in to the Microsoft Endpoint Manager Admin Center.
Select Devices > Configuration profiles > Create profile.
Enter the following properties:
- Name for the profile
- Optionally set a Description
- Platform to deploy the profile to
- Set Profile type to Trusted certificate
Select Settings, and then browse to the trusted root CA certificate .cer file you exported for use with this certificate profile, and then select OK.
For Windows 8.1 and Windows 10 devices only, select the Destination Store for the trusted certificate from:
- Computer certificate store - Root
- Computer certificate store - Intermediate
- User certificate store - Intermediate
When you're done, choose OK, go back to the Create profile pane, and select Create.
The profile appears in the list of profiles on the Devices - Configuration profiles window, with a profile type of Trusted certificate. Be sure to assign this profile to devices that will use SCEP or PKCS certificates. To assign the profile to groups, see assign device profiles.
Android devices might display a message that a third party has installed a trusted certificate.
- Assign device profiles
- Use S/MIME to sign and encrypt emails
- Use third-party certification authority
Create SCEP, PKCS, or PKCS imported certificate profiles for each platform you want to use. To continue, see the following articles: