Microsoft Intune
Device enrollment

Use SCEP Certificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn

In brief

The page updates wording and expands explanations of KDC strong mapping, the OnpremisesSecurityIdentifier SAN variable, Android trusted-root limitations, and public CA requirements for S/MIME certificates.

What Intune admins need to know

Review the revised strong-mapping and certificate attribute guidance when maintaining SCEP profiles.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Use SCEP certificate profilesCertificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn

After you configure your infrastructure to support Simple Certificate Enrollment Protocol (SCEP) certificates, you can create and then assign SCEP certificate profiles to users and devices in Intune.

For devices to use a SCEP certificate profile, they must trust your Trusted Root Certification Authority (CA). Trust of the root CA is best established by deploying a trusted certificate profile to the same group that receives the SCEP certificate profile. Trusted certificate profiles provision the Trusted Root CA certificate.

Note

Beginning with Android 11, trusted certificate profiles can no longer install the trusted root certificate on devices that are enrolled as Android device administrator. This limitation does notdoesn't apply to Samsung Knox.

For more information about this limitation,information, see Trusted certificate profiles for Android device administrator.

Important

  • iOS
  • macOS

The Key Distribution Center (KDC) requires user or device objects to be strongly mapped to Active Directory for certificate-based authentication. This requirement means that the certificate's subject alternative name (SAN) must contain a security identifier (SID) extension that maps to the user or device SID in Active Directory.

When a user or device authenticates with a certificate in Active Directory, the KDC checks for the SID to verify that the certificate is mapped and issued to the correct user or device. The mapping requirement protects against certificate spoofing and ensures that certificate-based authentication against the KDC continues working.

Strong mapping is required for all certificates deployed by Microsoft Intune and used for certificate-based authentication against KDC. The strong mapping solution is applicableapplies to user certificates across all platforms. For device certificates, it only applies to Microsoft Entra hybrid-joined Windows devices. If certificates in these scenarios don't meet the strong mapping requirements by the full enforcement mode date, authentication will beis denied.

To implement the strong mapping solution for SCEP certificates delivered viaby using Intune, you must add the OnpremisesSecurityIdentifier variable to the SAN in the SCEP profile.

SCEP certificate profile Configuration settings section

  • Given name attribute
  • Surname attribute

In terms of Microsoft Intune, you need these attributes are required forwhen you when usinguse Intune SCEP certificate profiles with third party public CA partners to issue S/MIME certificates for secure email. For a list of those CA partners, see Third party certification authority partners.

Public CAs will reject certificate requests from Intune-enrolled devices that omit the given name and surname attributes from the subject name. This requirement applies to new certificates and renewals.

When you edit an existing certificate profile to include these attributes, it triggers a reissuance of all certificates, which might incur additionalextra costs depending on your CA agreement.

To avoid service disruption, complete the following steps in the Microsoft Intune admin center:

- G={{GivenName}}
- SN={{SurName}}

You can enterEnter variables in the SCEP profile under **Configuration settings** > **Subject name format**.

![SCEP certificate profile configuration settings with subject name format highlighted](media/scep-profiles/subject-name-2506.png)
  1. Test changes. Before broad deployment, create a new profile and assign a small user group.

Create a SCEP certificate profile

  1. Sign in to the Microsoft Intune admin center.

  2. Select and goGo to Devices > Manage devices > Configuration > Create.

  3. Enter the following properties:

    • Platform: Choose the platform of your devices.

      SCEP certificate profiles for the Fully Managed, Dedicated, and Corporate-Owned Work Profile profile have the following limitations:

        • Under Monitoring,Monitoring, certificate reporting isn't available for Device Owner SCEP certificate profiles.
        • You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for Device Owner. You can manage revocation through an external process or directly with the certification authority.
        • For Android Enterprise dedicated devices, SCEP certificate profiles are supported for Wi-Fi network configuration, VPN, and authentication. SCEP certificate profiles on Android Enterprise dedicated devices aren't supported for app authentication.

    For Android (AOSP), the following limitations apply:

      • Under Monitoring,Monitoring, certificate reporting isn't available for Device Owner SCEP certificate profiles.

      • You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for Device Owners. You can manage revocation through an external process or directly with the certification authority.

      • SCEP certificate profiles are supported for Wi-Fi network configuration. VPN configuration profile support isn't available. A future update might include support for VPN configuration profiles.

      • The following variables aren't available for use on Android (AOSP) SCEP certificate profiles. Support for these variables will comecomes in a future update.

        • onPremisesSamAccountName
        • OnPrem_Distinguished_Name
        • Department

    Device Owner is equivalent to Corporate Owned devices. The following are considered as Device Owner:

    • Android Enterprise -Enterprise: Fully Managed, Dedicated, and Corporate-Owned Work Profile

    • Android AOSP

      • User-affinity
      • User-less
  4. Select Create.

  5. In Basics, enter the following properties:

    • Name: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is SCEP profile for entire company.
    • Description: Enter a description for the profile. This setting is optional, but recommended.We recommend this optional setting.
  6. Select Next.

  7. In Configuration settings, complete the following configurations:

     Always select the user deployment channel in profiles with user certificates. The user channel stores certificates in the user keychain. Always select the device deployment channel in profiles with device certificates. The device channel stores certificates in the system keychain.
    
     ItYou can's not possible tot edit the deployment channel after you deploy the profile. You must create a new profile to select a different channel.
    
    • Certificate type:

      (Applies to: Android, Android Enterprise, Android (AOSP), iOS/iPadOS, macOS, and Windows)Windows

      Select a type, depending on how you plan to use the certificate profile:

        Use **Device** for scenarios such as user-less devices, like kiosks, or for Windows devices. On Windows devices, the certificate is placed in the Local Computer certificate store.
      
        For macOS, if you configure this profile is configured to use the device deployment channel, you can select **User** or **Device**. If you configure the profile is configured to use the user deployment channel, you can select only **User**.
      

      Note

      Storage of certificates provisioned by SCEP:

      • macOS -: Certificates you provision with SCEP are always placed in the system keychain (alsokeychain, also called system store or device keychain), of the device, unless you select the user deployment channel.

      • Android -: Devices have both a VPN and apps certificate store, and a WIFI certificate store. Intune always stores SCEP certificates in the VPN and apps store on a device. Use of the VPN and apps store makes the certificate available for use by any other app.

        However, whenWhen a SCEP certificate is also associated with a Wi-Fi profile, Intune also installs the certificate in the Wi-Fi store.

        When configured for VPN apps, user will beyou're prompted to select the correct certificate. Silent certificate approval for Fully Managed (or BYOD scenarios) is notisn't supported. If everything is setupset up correctly, the correct certificate should already be preselected in the dialog box.

    • Subject name format:

      Enter text to tell Intune how to automatically create the subject name in the certificate request. Options for the subject name format depend on the Certificate type you select, either User or Device.

      Tip

      If your subject name length exceeds 64 characters, you might need to disable name length enforcement on your internal Certification Authority. For more information, see Disable DN Length Enforcement.

      Note

      There is's a known issue with escaped special characters in CSRs for using SCEP to get certificates when the subject name in the resulting Certificate Signing Request (CSR) includes one of the following characters as an escaped character (proceeded by a backslash ):

      • ;
      • IMEI
      • MEID

      Intune certificate profiles for personally owned work profile devices that rely on these variables in the subject name or SAN will fail to provision a certificate on devices that run Android 12 or later at the time the device enrolled with Intune. Devices that enrolled prior to upgrade to Android 12 can still receive certificates so long as Intune previously obtained the devices hardware identifiers.

      For more information about this and other changes introduced with Android 12, see the Android Day Zero Support for Microsoft Endpoint Manager blog post.

        Use the text box to enter a custom subject name format, including static text and variables. Two variable options are supported: **Common Name (CN)** and **Email (E)**.
      
        **Email (E)** wouldis usually be set with the {{EmailAddress}} variable. For example: **E={{EmailAddress}}**
      
        **Common Name (CN)** can be set to any of the following variables:
      
      
        Format options for the Subject name format include the following variables:
      
        - **{{AAD\_Device\_ID}}** or **{{AzureADDeviceId}}** -. Either variable can be used to identify a device by its Microsoft Entra ID.
        - **{{DeviceId}}** -. The Intune device IDID.
        - **{{Device\_Serial}}**
        - **{{Device\_IMEI}}**
        - **{{SerialNumber}}**
        - When you specify a variable, enclose the variable name in double curly brackets {{ }} as seen in the example, to avoid an error.
        - Device properties used in the *subject* or *SAN* of a device certificate, like **IMEI**, **SerialNumber**, and **FullyQualifiedDomainName**, are properties that could be spoofed by a person with access to the device.
        - A device must support all variables specified in a certificate profile for that profile to install on that device. For example, if **{{IMEI}}** is used in the subject name of a SCEP profile and is assigned to a device that doesn't have an IMEI number, the profile fails to install.
      
    • Subject alternative name:

      Configure the subject alternative name (SAN) in the certificate request. You can enter more than one subject alternative name. The text value can contain variables and static text for the attribute.

      Note

      • IMEI
      • MEID

      Intune certificate profiles for personally owned work profile devices that rely on these variables in the subject name or SAN will failfails to provision a certificate on devices that run Android 12 or later at the time the device enrolled with Intune. Devices that enrolled prior to upgrade to Android 12 can still receive certificates so long as Intune previously obtained the devices hardware identifiers.

      For more information about this and other changes introduced with Android 12, see the Android Day Zero Support for Microsoft Endpoint Manager blog post.

        Important
      
        - When usingyou use a device certificate variable, enclose the variable name in double curly brackets {{ }}.
        - Don't use curly brackets **{ }**, pipe symbols **|**, and semicolons **;**, in the text that follows the variable.
        - Device properties used in the *subject* or *SAN* of a device certificate, like **IMEI**, **SerialNumber**, and **FullyQualifiedDomainName**, are properties that could be spoofed by a person with access to the device.
        - A device must support all variables specified in a certificate profile for that profile to install on that device. For example, if you use **{{IMEI}}** is used in the SAN of a SCEP profile and is assigned to a device that doesn't have an IMEI number, the profile fails to install.
      
    • Certificate validity period:

      You can enter a value that is's lower than the validity period in the certificate template, but not higher. If you configured the certificate template to configure custom certificate validity periods, use this setting to specify the amount of remaining time before the certificate expires.

      Intune supports a validity period of up to 24 months.

      For example, if the certificate validity period in the certificate template is two years, you can enter a value of one year, but not a value of five years. The value must also be lower than the remaining validity period of the issuing CA's certificate.

      Plan to use a validity period of five days or greater. When the validity period is less than five days, there's a high likelihood of the certificate entering a near-expiry or expired state, which can cause the MDM agent on devices to reject the certificate before it's installed.

    • Key storage provider (KSP):

      (Applies to: Windows)

      • Enroll to Trusted Platform Module (TPM) KSP, otherwise fail
      • Enroll to Windows Hello for Business, otherwise fail
      • Enroll to Software KSP
    • Key usage:

      Select key usage options for the certificate:

      • Digital signature: Allow key exchange only when a digital signature helps protect the key.
      • Key encipherment: Allow key exchange only when the key is encrypted.
    • Key size (bits):

      Select the number of bits contained in the key:

      • Not configured

      • 1024

      • 2048

      • 4096 - A Keykey size of 4096 is supported for the following platforms:

        • Android (all)
        • iOS/iPadOS 14 and later

        Note

        For Windows devices, 4096-bit key storage is supported only in the Software Key Storage Provider (KSP). The following do notproviders don't support storing keys of this size:

        • The hardware TPM (Trusted Platform Module). As a workaround you can use the Software KSP for key storage.
        • Windows Hello for Business. There is's no workaround for Windows Hello for Business at this time.
    • Hash algorithm:

      (Applies to Android, Android (AOSP), Android enterprise, and Windows)

      Select one of the available hash algorithm types to use with this certificate. Select the strongest level of security that the connecting devices support.

      NOTE:Note

      Android AOSP and Android Enterprise devices will select the strongest algorithm supported -supported. They ignore SHA-1 will be ignored, and use SHA-2 will be used instead.

    • Root Certificate:

      Select the trusted certificate profile you previously configured and assigned to applicable users and devices for this SCEP certificate profile. The trusted certificate profile is used to provisionprovisions users and devices with the Trusted Root CA certificate. For information about the trusted certificate profile,more information, see Export your trusted root CA certificate and Create trusted certificate profiles in Use certificates for authentication in Intune.

      Note

      If you have a multiple level PKI Infastructure,Infrastructure, such as a Root Certification Authority and an Issuing Certification Authority, select the top level Trusted Root certificate profile that validates the Issuing Certification Authority.

    • Extended key usage:

      Add values for the certificate's intended purpose. In most cases, the certificate requires client authentication so that the user or device can authenticate to a server. You can add additionalmore key usages as required.

    • Renewal threshold (%):

      Enter the percentage of the certificate lifetime that remains before the device requests renewal of the certificate. For example, if you enter 20, the renewal of the certificate will beis attempted when the certificate is 80% expired. Renewal attempts continue until renewal is successful. Renewal generates a new certificate, which results in a new public/private key pair.

      Note

      Renewal behavior on iOS/iPadOS and macOS: Certificates can only be renewed during the renewal threshold phase. In addition, the device has to be unlocked while synchingsyncing with Intune. If the renewal was notwasn't successful, the expired certificate will remainremains on the device and Intune does notdoesn't trigger a renewal anymore. Also, Intune does notdoesn't offer an option to redeploy expired certificates. Affected devices need to be excluded from the SCEP profile temporarily to remove the expired certificate and request a new one.

    • SCEP Server URLs:

      Enter one or more URLs for the NDES Servers that issue certificates viaby using SCEP. For example, enter something like https://ndes.contoso.com/certsrv/mscep/mscep.dll.

      To allow devices on the internet to get certificates, you must specify the NDES URL external to your corporate network. The URL can be HTTP or HTTPS. However, toTo support the following devices, the SCEP Server URL must use HTTPS:

      • Android device administrator
      • Android Enterprise device owner
      • Android Enterprise corporate-owned work profile
      • Android Enterprise personally owned work profile

      You can add additionalmore SCEP URLs for load balancing as needed. Devices make three separate calls to the NDES server. The first is to get the serversserver's capabilities, the next to get a public key, and then to submit a signing request. When you use multiple URLs, it's possible that load balancing might result in a different URL being used for subsequent calls to an NDES Server. If a different server is contacted for a subsequent call during the same request, the request will fail.fails.

      The behavior for managing the NDES server URL is specific to each device platform:

      • Android: The device randomizes the list of URLs received in the SCEP policy, and then works through the list until it finds an accessible NDES server is found.server. The device then continues to use that same URL and server through the entire process. If the device can't access any of the NDES servers, the process fails.
      • iOS/iPadOS: Intune randomizes the URLs and provides a single URL to a device. If the device can't access the NDES server, the SCEP request fails.
      • Windows: The list of NDES URLs is randomized and then passed to the Windows device, which then tries them in the order received, until it finds one that's available is found.available. If the device can't access any of the NDES servers, the process fails.

      If a device fails to reach the same NDES server successfully during any of the three calls to the NDES server, the SCEP request fails. For example, this condition might happen when a load-balancing solution provides a different URL for the second or third call to the NDES server, or provides a different actual NDES server based on a virtualized URL for NDES. After a failed request, a device tries the process again on its next policy cycle, starting with the randomized list of NDES URLs (or a single URL for iOS/iPadOS).

  8. This step applies only to Android Enterprise devicesdevice profiles for Fully Managed, Dedicated, and Corporate-Owned work Profile.

    In Apps, configure Certificate access to manage how certificate access is granted to applications. Choose from:

    • Require user approval for apps(default) – Users must approve use of a certificate by all applications.
    • Grant silently for specific apps (require user approval for other apps) – With this option, select Add apps, and then select one or more apps that will silently use the certificate without user interaction.
  9. Select Next.

  10. In Assignments, select the user or groups that willto receive your profile. For more information on assigning profiles, see Assign user and device profiles.

    Select Next.

  11. (Applies to Windows only) In Applicability Rules, specify applicability rules to refine the assignment of this profile. You can choose to assign or not assign the profile based on the OS edition or version of a device.

    For more information, see Applicability rules in Create a device profile in Microsoft Intune.

  12. In Review + create, review your settings. When you select Create,Create, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.

Avoid certificate signing requests with escaped special characters

  • Encapsulate the CN value that contains the special character with quotes.
  • Remove the special character from the CN value.

For example,example, you have a Subject Name that appears as Test user (TestCompany, LLC). A CSR that includes a CN that has the comma between TestCompany and LLC presents a problem. The problem can be avoided by placing quotes around the entire CN, or by removing of the comma from between TestCompany and LLC:

  • Add quotes: CN="Test User (TestCompany, LLC)",OU=UserAccounts,DC=corp,DC=contoso,DC=com
  • Remove the comma: CN=Test User (TestCompany LLC),OU=UserAccounts,DC=corp,DC=contoso,DC=com

However, attemptsAttempts to escape the comma by using a backslash character will fail with an error in the CRP logs:

  • Escaped comma: CN=Test User (TestCompany, LLC),OU=UserAccounts,DC=corp,DC=contoso,DC=com

The error is similar to the following error:

Subject Name in CSR CN="Test User (TESTCOMPANY\, LLC),OU=UserAccounts,DC=corp,DC=contoso,DC=com" and challenge CN=Test User (TESTCOMPANY\, LLC),OU=UserAccounts,DC=corp,DC=contoso,DC=com do not match

  Exception: System.ArgumentException: Subject Name in CSR and challenge do not match

   at Microsoft.ConfigurationManager.CertRegPoint.ChallengeValidation.ValidationPhase3(PKCSDecodedObject pkcsObj, CertEnrollChallenge challenge, String templateName, Int32 skipSANCheck)

Exception: at Microsoft.ConfigurationManager.CertRegPoint.ChallengeValidation.ValidationPhase3(PKCSDecodedObject pkcsObj, CertEnrollChallenge challenge, String templateName, Int32 skipSANCheck)

   at Microsoft.ConfigurationManager.CertRegPoint.Controllers.CertificateController.VerifyRequest(VerifyChallengeParams value

Important

To use a SCEP certificate profile, a device must have also receivedreceive the trusted certificate profile that provisions it with your Trusted Root CA certificate. We recommend you deployDeploy both the trusted root certificate profile and SCEP certificate profile to the same groups.

Consider the following information before you continue:

  • When you assign SCEP certificate profiles to groups, the device installs the Trusted Root CA certificate file (as specifiedthat you specify in the trusted certificate profile) is installed on the device.. The device uses the SCEP certificate profile to create a certificate request for that Trusted Root CA certificate.
  • The SCEP certificate profile installs only on devices that run the platform you specified when you created the certificate profile.
  • You can assign certificate profiles to user collections or to device collections.
  • To publish a certificate to a device quickly after the device enrolls, assign the certificate profile to a user group rather than to a device group. If you assign the certificate profile to a device group, the device requires a full device registration is required before the deviceit receives policies.
  • If you use co-management for Intune and Configuration Manager, in Configuration Manager set the workload slider for Resource Access Policies to Intune or Pilot Intune. This setting allows Windows clients to start the process of requesting the certificate.

Note

  • On iOS/iPadOS and macOS devices, when a SCEP certificate profile or a PKCS certificate profile is associated with an additional profile, like a Wi-Fi or VPN profile, the device receives a certificate for each of those additional profiles. This configuration results in the device having multiple certificates delivered by the SCEP or PKCS certificate request.
  • Certificates delivered by SCEP are each unique. Certificates delivered by PKCS are the same certificate, but appear different as each profile instance is represented by a separate line in the management profile.
  • On iOS 13 and macOS 10.15, there are additional security requirements that are documented by Apple to take into consideration. \ No newline at end of file
Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…