Configure Infrastructure to Support SCEP Certificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn
In brief
The article received capitalization, grammar, wording, metadata, and authoring-reference updates. Its guidance continues to cover configuring the on-premises AD domain, certification authority, NDES server, and Certificate Connector for SCEP.
What Intune admins need to know
Use the refreshed article as the current reference when configuring SCEP infrastructure.
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.
Configure infrastructureInfrastructure to supportSupport SCEP certificate profilesCertificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn
Important
To support Windows requirements for strong mapping of SCEP certificates that were introduced and announced in KB5014754 from May 10, 2022 we’ve, Microsoft made changes to Intune SCEP certificate issuance for new and renewed SCEP certificates. With these changes, new or renewed Intune SCEP certificates for iOS/iPadOS, macOS, and Windows now include the following tag in the Subject Alternative Name (SAN) field of the certificate: URL=tag:microsoft.com,2022-09-14:sid:<value>
ThisStrong mapping uses this tag is used by strong mapping to tie a certificate to a specific device or user SID from Entra ID. With this change and requirement to map a SID from Entra ID:
- Device certificates are supported for Windows hybrid-joined devices when that device has a SID in Entra ID that
has beenis synchronized from an on-premises Active Directory. - User certificates use the User's SID from Entra ID, synced from on-premises Active Directory.
Certification Authorities (CAs) that do notdon't support the URL tag in the SAN might fail to issue certificates. Microsoft Active Directory Certificate Services servers that installed the update from KB5014754 support the use of this tag. If you use a third-party CA, check with your CA provider to ensure they support this format, or how and when this support will be added.they plan to add support.
For more information, see Support tip: Implementing strong mapping in Microsoft Intune certificates - Microsoft Community Hub.
Intune supports use of the Simple Certificate Enrollment Protocol (SCEP) to authenticate connections to your apps and corporate resources. SCEP uses the Certification Authority (CA) certificate to secure the message exchange for the Certificate Signing Request (CSR). When your infrastructure supports SCEP, you can use Intune SCEP certificate profiles (a type of device profile in Intune) to deploy the certificates to your devices.
TheYou need the Certificate Connector for Microsoft Intune is required to use SCEP certificate profiles with Intune when you also use an Active Directory Certificate Services Certification Authority, also called a Microsoft CA. The connector isnYou can't supporteduse the connector on the same server as your issuing Certification Authority (CA). TheAuthority. You don't need the connector isn't required when usingyou use Third-party Certification Authorities.
The information in thisThis article can help you configure your infrastructure to support SCEP when usingyou use Active Directory Certificate Services. After you configure your infrastructure is configured,infrastructure, you can create and deploy SCEP certificate profiles with Intune.
Tip
Prerequisites for using SCEP for certificates
Before you continue, ensure you've create and deploy a trusted certificate profile to devices that use SCEP certificate profiles. SCEP certificate profiles directly reference the trusted certificate profile that you use to provision devices with a Trusted Root CA certificate.
- Servers and server roles
- Accounts
To support SCEP, the following on-premises infrastructure must run on servers that are domain-joined to your Active Directory, with the exception of the Web Application Proxy Server.
Certificate Connector for Microsoft Intune
– The Certificate Connector for Microsoft Intune is required to. To use SCEP certificate profiles with Intune when you use a MicrosoftCA. It installsCA, you need the Certificate Connector for Microsoft Intune. Install it on the server that also runs the NDES server role.However, theThe connector isn't supported on the same server as your issuing Certification Authority (CA).For information about the certificate connector, see:
Certification Authority
–. Use a Microsoft Active Directory Certificate Services Enterprise Certification Authority (CA) that runs on an Enterprise edition of Windows Server 2008 R2 with service pack 1, or later. The version of Windows Server you use must remain in support by Microsoft. A Standalone CA isn't supported. For more information, see Install the Certification Authority.If your CA runs Windows Server 2008 R2 SP1, you must install the hotfix from KB2483564.
NDES server role
–. To support using the Certificate Connector for Microsoft Intune with SCEP,you mustconfigure the Windows Server that hosts the certificate connector with the Network Device Enrollment Service (NDES) server role. The connector supports installation on Windows Server 2012 R2 or later. In a later section of this article,we guideyouthrough installinginstall NDES.- The server that hosts NDES and the connector must be domain-joined and in the same forest as your Enterprise CA.
- The server that hosts NDES must not be a domain controller.
Support for NDES on the internet
To allow devices on the internet to get certificates, you must publish your NDES URL external to your corporate network. To do this, youYou can use a reverse proxy like Microsoft Entra application proxy, Microsoft's Web Application Proxy Server, or a third-party reverse proxy service or device.
Microsoft Entra application proxy
–. You can use the Microsoft Entra application proxy instead of a dedicated Web Application Proxy (WAP) Server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates. For more information, see Integrate with Microsoft Entra application proxy on a Network Device Enrollment Service (NDES) server.Web Application Proxy Server
-. Use a server that runs Windows Server 2012 R2 or later as a Web Application Proxy (WAP) server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates.The server that hosts WAP must install an update that enables support for the long URLs that are used by the Network Device Enrollment Service. This update is included with the December 2014 update rollup, or individually from KB3011135.
The WAP server must have an SSL certificate that matches the name that's published to external clients and trust the SSL certificate that's used on the computer that hosts the NDES service. These certificates enable the WAP server to terminate the SSL connection from clients and create a new SSL connection to the NDES service.
For more information, see Plan certificates for WAP and general information about WAP servers.
Third-party reverse proxy
–. When you use a third-party reverse proxy, ensure that the proxy supports a long URI get request. As part of the certificate request flow, the client makes a request with the certificate request in the query string. As a result, the URI length can be large, up to 40 kb in size.
SCEP protocol limitations prevent use of preauthentication. When you publish the NDES URL viaby using a reverse proxy server, you must have Pre Authentication set to Passthrough.
Intune secures the NDES URL when you install the Intune Certificate connector,connector by installing an Intune-SCEP policy module on the NDES server. The module helps to secure the NDES URL by preventing certificates from being issued to invalid or digitally tampered certificate requests. This approach limits access to only Intune enrolled devices that you manage with Intune and that have well-formed certificate requests.
When an Intune SCEP certificate profile is delivered to a device, Intune generates a custom challenge blob that it encrypts and signs. The blob isn't readable by the device. Only the policy module and the Intune service can read and verify the challenge blob. The blob includes details that Intune expects to be provided by the device in its certificate signing request (CSR). For example, the expected Subject and Subject Alternative Name (SAN).
Accounts
To configure the connector to support SCEP, use an account that has permissions to configure NDES on the Windows Server and to manage your Certification Authority. For details,more information, see Accounts in the Prerequisites for the Certificate Connector for Microsoft Intune article..
Network requirements
In addition to the network requirements for the certificate connector, we recommend publishing the NDES service through a reverse proxy, such as the Microsoft Entra application proxy, Web Access Proxy, or a third-party proxy. If you don't use a reverse proxy, then allow TCP traffic on port 443 from all hosts and IP addresses on the internet to the NDES service.
Allow all ports and protocols necessary for communication between the NDES service and any supporting infrastructure in your environment. For example, the computer that hosts the NDES service needs to communicate with the CA, DNS servers, domain controllers, and possibly other services or servers withinin your environment, like Configuration Manager.
Certificates and templates
| Object | Details |
|---|---|
| SCEP Certificate Template | Template that you configure on your issuing CA that's used to |
| Server authentication certificate | Web Server certificate requested from your issuing CA or public CA. You install and bind this SSL certificate in IIS on the computer that hosts NDES. |
| Trusted Root CA certificate | To use a SCEP certificate profile, devices must trust your Trusted Root Certification Authority (CA). Use a trusted certificate profile in Intune to provision the Trusted Root CA certificate to users and devices. - Use a single Trusted Root CA certificate per operating system platform and associate that certificate with each trusted certificate profile you create. - You can use additional Trusted Root CA certificates when needed. For example, you might use additional certificates to provide a trust to a CA that signs the server authentication certificates for your Wi-Fi access points. Create additional Trusted Root CA certificates for issuing CAs. In the SCEP certificate profile you create in Intune, be sure to specify the Trusted Root CA profile for the issuing CA. For information about the trusted certificate profile, see Export the trusted root CA certificate and Create trusted certificate profiles in Use certificates for authentication in Intune. |
Note
The following certificate is notisn't used with the Certificate Connector for Microsoft Intune. This information is provided for those who have not yet replaceddidn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
| Object | Details |
|---|---|
| For Android Enterprise, the version of encryption on a device determines whether the device must be configured with a PIN before SCEP can provision that device with a certificate. The available encryption types are: |
- Full-disk encryption, which requires the device have a PIN configured.
- File-based encryption, which is required on devices that
are installed bytheOEMmanufacturer installs with Android 10 or later. These deviceswondon't require a PIN. Devices that upgrade to Android 10 might still require a PIN.
Note
The version of Android on a device can affect the available encryption type:
- Android 10 and later: Devices
installedthat the hardware manufacturer installs with Android 10 or laterby the OEMuse file-based encryption andwondon't require a PIN for SCEP to provision a certificate. Devices that upgrade to version 10 or later and begin to use file-based encryption might still require a PIN. - Android 8 to 9: These versions of Android support the use of file-based encryption, but
itdon's not required.t require it. EachOEMmanufacturer chooses which encryption type to implement for a device. It's also possible thatOEMmanufacturer modificationswillresult in a PIN not being required even when full-disk encryption is in use.
For more information, see the following articles in the Android documentation:
For devices that run 9.0 and later and receive a kiosk-mode policy, you can use a device compliance or device configuration policy to enforce the password requirement. View Support Tip: New Google-based Compliance Screens for Kiosk Mode from the Intune Support Team, to understand the device experience.
For devices that run 8.x and earlier, you can also use a device compliance or device configuration policy to enforce the password requirement. However, toTo set up a PIN, you need to manually enter the settings application on the device and configure the PIN.
Configure the certification authority
In the following sections, you'll:you:
- Configure and publish the required template for
NDESNDES. - Set the required permissions for certificate revocation.
The following sections require knowledge of Windows Server 2012 R2 or later, and of Active Directory Certificate Services (AD CS).
Access your Issuingissuing CA
- Sign in to your issuing CA with a domain account
withthat has rightssufficientto manage the CA. - Open the Certification Authority Microsoft Management Console (MMC). Either Run
'certsrv.mscor, in Server Manager, select Tools, and then Certification Authority.' or - Select the Certificate Templates node, select Action > Manage.
Create the SCEP certificate template
Create a v2 Certificate Template
(withwith Windows 2003compatibility)compatibility for use as the SCEP certificate template. You can:- Use the Certificate Templates snap-in to create a new custom template.
- Copy an existing
template (liketemplate, like the Web Servertemplate)template, and then update the copy to use as the NDES template.
Configure the following settings on the specified tabs of the template:
General:
Select Supply in the request. The Intune policy module for NDES enforces security.

Extensions:
Ensure that Description of Application Policies includes Client Authentication.
Important
Only addAdd only the application policies that you require. Confirm your choices with your security admins.For iOS/iPadOS and macOS certificate templates, also edit Key Usage and make sure Signature is proof of origin isn't selected.

Security:
- Add the NDES service account. This account requires Read and Enroll permissions to this template.
- Add
additional Accountsaccounts for Intune administrators whowillcan create SCEP profiles. These accounts require Read permissions to the template to enable these admins to browse to this template while creating SCEP profiles.

Request Handling:
The following image is an example. Your configuration might vary.

Issuance Requirements:
The following image is an example. Your configuration might vary.

Save the certificate template.
Create the client certificate template
Note
The following certificate is notisn't used with the Certificate Connector for Microsoft Intune. This information is provided for those who have not yet replaceddidn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
The Microsoft Intune Connector requires a certificate with the Client Authentication Enhanced Key Usage and Subject name equal to the FQDN of the machine where the connector is installed. AYou need a template with the following properties is required:properties:
- Extensions > Application Policies must contain Client Authentication.
- Subject name > Supply in the request.
If you already have a template that includes these properties, you can reuse it, otherwiseit. Otherwise, create a new template by either duplicating an existing one or creating a custom template.
Create the server certificate template
Communications between managed devices and IIS on the NDES server use HTTPS, which requires use of a certificate. You can use the Web Server certificate template to issue this certificate. Or, ifIf you prefer to have a dedicated template, use the following properties are required:properties:
- Extensions > Application Policies must contain Server Authentication.
- Subject name > Supply in the request.
Grant permissions for certificate revocation
ForTo enable Intune to be able to revoke certificates that are no longer required, you must grant permissions in the Certificate Authority.
On the server that hosts the certificate connector, use either the NDES server system account or a specific account such as the NDES service account.
On your Certificate Authority console,
Right-right-click the CA name and select Properties.In the Security tab, select Add.
Grant the Issue and Manage Certificates permission:
- If you
optchoose to use the NDES server system account,providegrant thepermissionspermission to the NDES server. - If you
optchoose to use the NDES service account,provide permissions forgrant the permission to thataccount instead.account.
- If you
Modify the validity period of the certificate template
It's optional toYou can modify the validity period of the certificate template.
After you create the SCEP certificate template, you can edit the template to review the Validity period on the General tab.
By default, Intune uses the value configured in the template, but you can configure the CA to allow the requester to enter a different value, so you can set that value can be set from within the Microsoft Intune admin center.
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.
Publish certificate templates
On the issuing CA, use the Certification Authority snap-in to publish the certificate template.
- Select the Certificate Templates node, select Action > New > Certificate Template to Issue, and then select the certificate template you created in the previous section.
- Validate that the template
hasis published by viewing it in the Certificate Templates folder.
Set up NDES
The following procedures can help you configure the Network Device Enrollment Service (NDES) for use with Intune. These procedures are provided as
examplesexamples, as the actual configuration might vary depending on your version of Windows Server. Ensure required configurations youaddadd, like those for .NETFrameworkFramework, meet the prerequisites for the Certificate Connector for Microsoft Intune.For more information about NDES, see Network Device Enrollment Service Guidance.
Install the NDES service
On the server that
willyou want to host your NDES service, sign in as an Enterprise Administrator, and then use the Add Roles and Features Wizard to install NDES:In the
Wizard,wizard, select Active Directory Certificate Services togainaccesstothe AD CS Role Services. Select Network Device Enrollment Service, uncheck Certification Authority, and then complete the wizard.Tip
- In Role Services, select the Network Device Enrollment Service.
- In Service Account for NDES, specify the NDES Service Account.
- In CA for NDES,
clickSelect, and thenselect the issuing CA where you configured the certificate template. - In Cryptography for NDES, set the key length to meet your company requirements.
- In Confirmation, select Configure to complete the wizard.
After the wizard completes, update the following registry key on the computer that hosts the NDES service:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MSCEP\To update this key, identify the certificate templates' Purpose
(foundonitsthe Request Handlingtab).tab. Then, update the corresponding registry entry by replacing the existing data with the name of the certificatetemplate (nottemplate, not the display name of thetemplate)template, that you specified when you created the certificate template.The following table maps the certificate template purpose to the values in the registry:
| Encryption | EncryptionTemplate | Key Encipherment | | Signature and encryption | GeneralPurposeTemplate | Key Encipherment Digital Signature |
For example, if the Purpose of your certificate template is Encryption,
thenedit the EncryptionTemplate value to be the name of your certificate template.Restart the server that hosts the NDES service. Don't use iisreset
; iiresetbecause it doesn't complete the required changes.Browse to
http://Server\_FQDN/certsrv/mscep/mscep.dllhttp://<Server_FQDN>/certsrv/mscep/mscep.dll. You should see an NDES page similar to the following image:
If the web address returns a 503 Service unavailable
,error, check thecomputerscomputer's event viewer. This error commonly occurs when the application poolis stoppedstops due to a missing permission for the NDES service account.
Install and bind certificates on the server that hosts NDES
1. Request a **server authentication** certificate from your internal CA or public CA, and then install the certificate on the server. Depending on how you expose your NDES to the internet, there are different requirements. A good configuration is: Note If youare're using Microsoft Entra application proxy, the Microsoft Entra application proxy connectorwill translatetranslates the requests from the external URL to the internal URL. As such, NDESwillonlyrespondresponds to requests directed to the internal URL, usually the FQDN of the NDES Server. In this situation, the external URLis notisn't required. 2. Bind the server authentication certificate in IIS: 1. Afterinstallingyou install the server authentication certificate, open **IIS Manager**, and select the **Default Web Site**. In the **Actions** pane, select **Bindings**. 2. Select **Add**, set **Type** to **https**, and then confirm the port is **443**. 3. For **SSL certificate**, specify the server authentication certificate.Note
When configuring NDES for the Certificate Connector for Microsoft
Intune ,Intune, only the Server authentication certificate is used. If you're configuring NDES to support the older certificate connector (NDESConnectorSetup.exe), you must also configure a Client authentication certificate. You can use a single certificate for both server authentication and client authentication when that certificate is configured to meet the criteria of both uses.Regarding the Subject Name, it must meet the client authentication certificate requirements.
The following information is provided for those who
have not yet replaceddidn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.- Client authentication certificate
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Configure infrastructure to support SCEP certificate profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn+title: Configure Infrastructure to Support SCEP Certificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/fundamentals/certificates/scep-infrastructure author: sdeines-msft ms.author: sdeines@@ -13,8 +13,8 @@ ms.collection: - certificates - sub-certificates ms.subservice: fundamentals-description: To use Simple Certificate Enrollment Protocol (SCEP) with Microsoft Intune, configure your on-premises AD domain, create a certification authority, and set up the NDES server to support use of the Certificate Connector.-ms.date: 2023-06-26T00:00:00.0000000Z+description: Configure your on-premises AD domain, create a certification authority, and set up the NDES server to support use of the Certificate Connector.+ms.date: 2026-11-12T00:00:00.0000000Z ms.topic: how-to locale: en-us document_id: 5c2fa900-7577-502d-d3ff-ca887bf8716d@@ -36,32 +36,34 @@ source_path: intune/fundamentals/certificates/scep-infrastructure.md cmProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/a72e95ff-4b4f-4cc1-90c6-7dcba67ff05f - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/37da4cc9-0cfc-42a9-ba5e-805706b01ef8+- https://authoring-docs-microsoft.poolparty.biz/devrel/b1cfdec6-b0c3-4209-818c-736879856e0e spProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/24dc3ccd-591a-4415-a1fe-8759afafcb12 - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/3661fb96-d414-4a4e-b7ad-9370637790dd+- https://authoring-docs-microsoft.poolparty.biz/devrel/2d0723c1-cf38-4c30-ab3d-5df787b33270 platformId: 519f27f5-b90f-46d7-75dc-d3b003f82a38 --- -# Configure infrastructure to support SCEP certificate profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn+# Configure Infrastructure to Support SCEP Certificate Profiles with Microsoft Intune - Microsoft Intune | Microsoft Learn Important
-To support Windows requirements for strong mapping of SCEP certificates that were introduced and announced in [KB5014754 from May 10, 2022](https://support.microsoft.com/topic/kb5014754-certificate-based-authentication-changes-on-windows-domain-controllers-ad2c23b0-15d8-4340-a468-4d4f3b188f16) we’ve made changes to Intune SCEP certificate issuance for new and renewed SCEP certificates. With these changes, new or renewed Intune SCEP certificates for iOS/iPadOS, macOS, and Windows now include the following tag in the Subject Alternative Name (SAN) field of the certificate: `URL=tag:microsoft.com,2022-09-14:sid:<value>`
+To support Windows requirements for strong mapping of SCEP certificates that were introduced and announced in [KB5014754 from May 10, 2022](https://support.microsoft.com/topic/kb5014754-certificate-based-authentication-changes-on-windows-domain-controllers-ad2c23b0-15d8-4340-a468-4d4f3b188f16), Microsoft made changes to Intune SCEP certificate issuance for new and renewed SCEP certificates. With these changes, new or renewed Intune SCEP certificates for iOS/iPadOS, macOS, and Windows now include the following tag in the Subject Alternative Name (SAN) field of the certificate: `URL=tag:microsoft.com,2022-09-14:sid:<value>`
-This tag is used by strong mapping to tie a certificate to a specific device or user SID from Entra ID. With this change and requirement to map a SID from Entra ID:
+Strong mapping uses this tag to tie a certificate to a specific device or user SID from Entra ID. With this change and requirement to map a SID from Entra ID:
-- Device certificates are supported for Windows hybrid-joined devices when that device has a SID in Entra ID that has been synchronized from an on-premises Active Directory.
+- Device certificates are supported for Windows hybrid-joined devices when that device has a SID in Entra ID that is synchronized from an on-premises Active Directory.
- User certificates use the User's SID from Entra ID, synced from on-premises Active Directory.
-Certification Authorities (CAs) that do not support the URL tag in the SAN might fail to issue certificates. Microsoft Active Directory Certificate Services servers that installed the update from [KB5014754](https://support.microsoft.com/topic/kb5014754-certificate-based-authentication-changes-on-windows-domain-controllers-ad2c23b0-15d8-4340-a468-4d4f3b188f16) support the use of this tag. If you use a third-party CA, check with your CA provider to ensure they support this format, or how and when this support will be added.
+Certification Authorities (CAs) that don't support the URL tag in the SAN might fail to issue certificates. Microsoft Active Directory Certificate Services servers that installed the update from [KB5014754](https://support.microsoft.com/topic/kb5014754-certificate-based-authentication-changes-on-windows-domain-controllers-ad2c23b0-15d8-4340-a468-4d4f3b188f16) support the use of this tag. If you use a third-party CA, check with your CA provider to ensure they support this format, or how and when they plan to add support.
For more information, see [Support tip: Implementing strong mapping in Microsoft Intune certificates - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-implementing-strong-mapping-in-microsoft-intune/ba-p/4053376).
-Intune supports use of the Simple Certificate Enrollment Protocol (SCEP) to [authenticate connections to your apps and corporate resources](overview). SCEP uses the Certification Authority (CA) certificate to secure the message exchange for the Certificate Signing Request (CSR). When your infrastructure supports SCEP, you can use Intune *SCEP certificate* profiles (a type of device profile in Intune) to deploy the certificates to your devices.
+Intune supports use of the Simple Certificate Enrollment Protocol (SCEP) to [authenticate connections to your apps and corporate resources](overview). SCEP uses the Certification Authority (CA) certificate to secure the message exchange for the Certificate Signing Request (CSR). When your infrastructure supports SCEP, you can use Intune *SCEP certificate* profiles to deploy the certificates to your devices.
-The [Certificate Connector for Microsoft Intune](connector/overview) is required to use SCEP certificate profiles with Intune when you also use an Active Directory Certificate Services Certification Authority, also called a *Microsoft CA*. The connector isn't supported on the same server as your issuing Certification Authority (CA). The connector isn't required when using [Third-party Certification Authorities](third-party-ca-scep#set-up-third-party-ca-integration).
+You need the [Certificate Connector for Microsoft Intune](connector/overview) to use SCEP certificate profiles with Intune when you also use an Active Directory Certificate Services Certification Authority, also called a *Microsoft CA*. You can't use the connector on the same server as your issuing Certification Authority. You don't need the connector when you use [Third-party Certification Authorities](third-party-ca-scep#set-up-third-party-ca-integration).
-The information in this article can help you configure your infrastructure to support SCEP when using Active Directory Certificate Services. After your infrastructure is configured, you can [create and deploy SCEP certificate profiles](../../device-configuration/certificates/scep-profiles) with Intune.
+This article can help you configure your infrastructure to support SCEP when you use Active Directory Certificate Services. After you configure your infrastructure, you can [create and deploy SCEP certificate profiles](../../device-configuration/certificates/scep-profiles) with Intune.
Tip
@@ -69,7 +71,7 @@ Intune also supports use of [Public Key Cryptography Standards #12 certificates]
## Prerequisites for using SCEP for certificates
-Before you continue, ensure you've [created and deployed a *trusted certificate* profile](../../device-configuration/certificates/trusted-root-profiles#export-the-trusted-root-ca-certificate) to devices that use SCEP certificate profiles. SCEP certificate profiles directly reference the trusted certificate profile that you use to provision devices with a Trusted Root CA certificate.
+Before you continue, [create and deploy a *trusted certificate* profile](../../device-configuration/certificates/trusted-root-profiles#export-the-trusted-root-ca-certificate) to devices that use SCEP certificate profiles. SCEP certificate profiles directly reference the trusted certificate profile that you use to provision devices with a Trusted Root CA certificate.
- Servers and server roles
- Accounts
@@ -81,17 +83,17 @@ Before you continue, ensure you've [created and deployed a *trusted certificate*
To support SCEP, the following on-premises infrastructure must run on servers that are domain-joined to your Active Directory, with the exception of the Web Application Proxy Server.
-- **Certificate Connector for Microsoft Intune** – The Certificate Connector for Microsoft Intune is required to use SCEP certificate profiles with Intune when you use a Microsoft CA. It installs on the server that also runs the NDES server role. However, the connector isn't supported on the same server as your issuing Certification Authority (CA).
+- **Certificate Connector for Microsoft Intune**. To use SCEP certificate profiles with Intune when you use a Microsoft CA, you need the Certificate Connector for Microsoft Intune. Install it on the server that also runs the NDES server role. The connector isn't supported on the same server as your issuing Certification Authority (CA).
For information about the certificate connector, see:
- - Overview of the [Certificate Connector for Microsoft Intune](connector/overview).
- - [Prerequisites](connector/prerequisites).
- - [Installation and configuration](connector/setup-connector).
-- **Certification Authority** – Use a Microsoft Active Directory Certificate Services Enterprise Certification Authority (CA) that runs on an Enterprise edition of Windows Server 2008 R2 with service pack 1, or later. The version of Windows Server you use must remain in support by Microsoft. A Standalone CA isn't supported. For more information, see [Install the Certification Authority](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj125375%28v=ws.11%29).
+ - [Certificate Connector for Microsoft Intune](connector/overview)
+ - [Prerequisites](connector/prerequisites)
+ - [Installation and configuration](connector/setup-connector)
+- **Certification Authority**. Use a Microsoft Active Directory Certificate Services Enterprise Certification Authority (CA) that runs on an Enterprise edition of Windows Server 2008 R2 with service pack 1, or later. The version of Windows Server you use must remain in support by Microsoft. A Standalone CA isn't supported. For more information, see [Install the Certification Authority](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj125375%28v=ws.11%29).
If your CA runs Windows Server 2008 R2 SP1, you must [install the hotfix from KB2483564](https://support.microsoft.com/kb/2483564/).
-- **NDES server role** – To support using the Certificate Connector for Microsoft Intune with SCEP, you must configure the Windows Server that hosts the certificate connector with the Network Device Enrollment Service (NDES) server role. The connector supports installation on Windows Server 2012 R2 or later. In a later section of this article, we guide you through installing NDES.
+- **NDES server role**. To support using the Certificate Connector for Microsoft Intune with SCEP, configure the Windows Server that hosts the certificate connector with the Network Device Enrollment Service (NDES) server role. The connector supports installation on Windows Server 2012 R2 or later. In a later section of this article, you install NDES.
- The server that hosts NDES and the connector must be domain-joined and in the same forest as your Enterprise CA.
- The server that hosts NDES must not be a domain controller.
@@ -102,19 +104,21 @@ To support SCEP, the following on-premises infrastructure must run on servers th
#### Support for NDES on the internet
-To allow devices on the internet to get certificates, you must publish your NDES URL external to your corporate network. To do this, you can use a reverse proxy like *Microsoft Entra application proxy*, *Microsoft's Web Application Proxy Server*, or a third-party reverse proxy service or device.
+To allow devices on the internet to get certificates, publish your NDES URL external to your corporate network. You can use a reverse proxy like *Microsoft Entra application proxy*, *Microsoft's Web Application Proxy Server*, or a third-party reverse proxy service or device.
-- **Microsoft Entra application proxy** – You can use the Microsoft Entra application proxy instead of a dedicated Web Application Proxy (WAP) Server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates. For more information, see [Integrate with Microsoft Entra application proxy on a Network Device Enrollment Service (NDES) server](/en-us/azure/active-directory/manage-apps/active-directory-app-proxy-protect-ndes).
-- **Web Application Proxy Server** - Use a server that runs Windows Server 2012 R2 or later as a Web Application Proxy (WAP) server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates.
+- **Microsoft Entra application proxy**. You can use the Microsoft Entra application proxy instead of a dedicated Web Application Proxy (WAP) Server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates. For more information, see [Integrate with Microsoft Entra application proxy on a Network Device Enrollment Service (NDES) server](/en-us/azure/active-directory/manage-apps/active-directory-app-proxy-protect-ndes).
+- **Web Application Proxy Server**. Use a server that runs Windows Server 2012 R2 or later as a Web Application Proxy (WAP) server to publish your NDES URL to the internet. This solution allows both intranet and internet facing devices to get certificates.
The server that hosts WAP [must install an update](/en-us/archive/blogs/ems/hotfix-large-uri-request-in-web-application-proxy-on-windows-server-2012-r2) that enables support for the long URLs that are used by the Network Device Enrollment Service. This update is included with the [December 2014 update rollup](https://support.microsoft.com/kb/3013769), or individually from [KB3011135](https://support.microsoft.com/kb/3011135).
The WAP server must have an SSL certificate that matches the name that's published to external clients and trust the SSL certificate that's used on the computer that hosts the NDES service. These certificates enable the WAP server to terminate the SSL connection from clients and create a new SSL connection to the NDES service.
For more information, see [Plan certificates for WAP](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn383650%28v=ws.11%29#plan-certificates) and [general information about WAP servers](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn584113%28v=ws.11%29).
-- **Third-party reverse proxy** – When you use a third-party reverse proxy, ensure that the proxy supports a long URI get request. As part of the certificate request flow, the client makes a request with the certificate request in the query string. As a result, the URI length can be large, up to 40 kb in size.
+- **Third-party reverse proxy**. When you use a third-party reverse proxy, ensure that the proxy supports a long URI get request. As part of the certificate request flow, the client makes a request with the certificate request in the query string. As a result, the URI length can be large, up to 40 kb in size.
-SCEP protocol limitations prevent use of preauthentication. When you publish the NDES URL via a reverse proxy server, you must have *Pre Authentication* set to *Passthrough*. Intune secures the NDES URL when you install the Intune Certificate connector, by installing an Intune-SCEP policy module on the NDES server. The module helps to secure the NDES URL by preventing certificates from being issued to invalid or digitally tampered certificate requests. This limits access to only Intune enrolled devices that you manage with Intune and that have well-formed certificate requests.
+ SCEP protocol limitations prevent use of preauthentication. When you publish the NDES URL by using a reverse proxy server, you must have *Pre Authentication* set to *Passthrough*.
+
+ Intune secures the NDES URL when you install the Intune Certificate connector by installing an Intune-SCEP policy module on the NDES server. The module helps to secure the NDES URL by preventing certificates from being issued to invalid or digitally tampered certificate requests. This approach limits access to only Intune enrolled devices that you manage with Intune and that have well-formed certificate requests.
When an Intune SCEP certificate profile is delivered to a device, Intune generates a custom challenge blob that it encrypts and signs. The blob isn't readable by the device. Only the policy module and the Intune service can read and verify the challenge blob. The blob includes details that Intune expects to be provided by the device in its certificate signing request (CSR). For example, the expected *Subject* and *Subject Alternative Name* (SAN).
@@ -128,13 +132,13 @@ The Intune policy module works to secure NDES in the following ways:
### Accounts
-To configure the connector to support SCEP, use an account that has permissions to configure NDES on the Windows Server and to manage your Certification Authority. For details, see [Accounts](connector/prerequisites#accounts) in the *Prerequisites for the Certificate Connector for Microsoft Intune* article.
+To configure the connector to support SCEP, use an account that has permissions to configure NDES on the Windows Server and to manage your Certification Authority. For more information, see [Accounts](connector/prerequisites#accounts).
### Network requirements
-In addition to the [network requirements](connector/prerequisites) for the certificate connector, we recommend publishing the NDES service through a reverse proxy, such as the [Microsoft Entra application proxy, Web Access Proxy](/en-us/azure/active-directory/app-proxy/application-proxy-add-on-premises-application), or a third-party proxy. If you don't use a reverse proxy, then allow TCP traffic on port 443 from all hosts and IP addresses on the internet to the NDES service.
+In addition to the [network requirements](connector/prerequisites) for the certificate connector, we recommend publishing the NDES service through a reverse proxy, such as the [Microsoft Entra application proxy, Web Access Proxy](/en-us/azure/active-directory/app-proxy/application-proxy-add-on-premises-application), or a third-party proxy. If you don't use a reverse proxy, allow TCP traffic on port 443 from all hosts and IP addresses on the internet to the NDES service.
-Allow all ports and protocols necessary for communication between the NDES service and any supporting infrastructure in your environment. For example, the computer that hosts the NDES service needs to communicate with the CA, DNS servers, domain controllers, and possibly other services or servers within your environment, like Configuration Manager.
+Allow all ports and protocols necessary for communication between the NDES service and any supporting infrastructure in your environment. For example, the computer that hosts the NDES service needs to communicate with the CA, DNS servers, domain controllers, and possibly other services or servers in your environment, like Configuration Manager.
### Certificates and templates
@@ -142,13 +146,13 @@ The following certificates and templates are used when you use SCEP.
| Object | Details |
| --- | --- |
-| **SCEP Certificate Template** | Template that you configure on your issuing CA that's used to fullfil the devices SCEP requests. |
+| **SCEP Certificate Template** | Template that you configure on your issuing CA that's used to fulfill the devices SCEP requests. |
| **Server authentication certificate** | Web Server certificate requested from your issuing CA or public CA. You install and bind this SSL certificate in IIS on the computer that hosts NDES. |
| **Trusted Root CA certificate** | To use a SCEP certificate profile, devices must trust your Trusted Root Certification Authority (CA). Use a *trusted certificate profile* in Intune to provision the Trusted Root CA certificate to users and devices. **-** Use a single Trusted Root CA certificate per operating system platform and associate that certificate with each trusted certificate profile you create. **-** You can use additional Trusted Root CA certificates when needed. For example, you might use additional certificates to provide a trust to a CA that signs the server authentication certificates for your Wi-Fi access points. Create additional Trusted Root CA certificates for issuing CAs. In the SCEP certificate profile you create in Intune, be sure to specify the Trusted Root CA profile for the issuing CA. For information about the trusted certificate profile, see [Export the trusted root CA certificate](../../device-configuration/certificates/trusted-root-profiles#export-the-trusted-root-ca-certificate) and [Create trusted certificate profiles](../../device-configuration/certificates/trusted-root-profiles#create-trusted-certificate-profiles) in *Use certificates for authentication in Intune*. |
Note
-The following certificate is not used with the Certificate Connector for Microsoft Intune. This information is provided for those who have not yet replaced the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
+The following certificate isn't used with the Certificate Connector for Microsoft Intune. This information is provided for those who didn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
| Object | Details |
| --- | --- |
@@ -159,7 +163,7 @@ The following certificate is not used with the Certificate Connector for Microso For Android Enterprise, the version of encryption on a device determines whether the device must be configured with a PIN before SCEP can provision that device with a certificate. The available encryption types are:
- **Full-disk encryption**, which requires the device have a PIN configured.
-- **File-based encryption**, which is required on devices that are installed by the OEM with Android 10 or later. These devices won't require a PIN. Devices that upgrade to Android 10 might still require a PIN.
+- **File-based encryption**, which is required on devices that the manufacturer installs with Android 10 or later. These devices don't require a PIN. Devices that upgrade to Android 10 might still require a PIN.
Note
@@ -167,8 +171,8 @@ Microsoft Intune can't identify the type of encryption on an Android device.
The version of Android on a device can affect the available encryption type:
-- **Android 10 and later:** Devices installed with Android 10 or later by the OEM use file-based encryption and won't require a PIN for SCEP to provision a certificate. Devices that upgrade to version 10 or later and begin to use file-based encryption might still require a PIN.
-- **Android 8 to 9**: These versions of Android support the use of file-based encryption, but it's not required. Each OEM chooses which encryption type to implement for a device. It's also possible that OEM modifications will result in a PIN not being required even when full-disk encryption is in use.
+- **Android 10 and later:** Devices that the hardware manufacturer installs with Android 10 or later use file-based encryption and don't require a PIN for SCEP to provision a certificate. Devices that upgrade to version 10 or later and begin to use file-based encryption might still require a PIN.
+- **Android 8 to 9**: These versions of Android support the use of file-based encryption, but don't require it. Each manufacturer chooses which encryption type to implement for a device. It's also possible that manufacturer modifications result in a PIN not being required even when full-disk encryption is in use.
For more information, see the following articles in the Android documentation:
@@ -181,29 +185,29 @@ For devices enrolled as Android Enterprise dedicated, password enforcement can p
For devices that run 9.0 and later and receive a kiosk-mode policy, you can use a device compliance or device configuration policy to enforce the password requirement. View [Support Tip: New Google-based Compliance Screens for Kiosk Mode](https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-new-google-based-compliance-screens-for-kiosk-mode/ba-p/2129719) from the Intune Support Team, to understand the device experience.
-For devices that run 8.x and earlier, you can also use a device compliance or device configuration policy to enforce the password requirement. However, to set up a PIN, you need to manually enter the settings application on the device and configure the PIN.
+For devices that run 8.x and earlier, you can also use a device compliance or device configuration policy to enforce the password requirement. To set up a PIN, you need to manually enter the settings application on the device and configure the PIN.
## Configure the certification authority
-In the following sections, you'll:
+In the following sections, you:
-- Configure and publish the required template for NDES
+- Configure and publish the required template for NDES.
- Set the required permissions for certificate revocation.
The following sections require knowledge of Windows Server 2012 R2 or later, and of Active Directory Certificate Services (AD CS).
-### Access your Issuing CA
+### Access your issuing CA
-1. Sign in to your issuing CA with a domain account with rights sufficient to manage the CA.
-2. Open the Certification Authority Microsoft Management Console (MMC). Either **Run** 'certsrv.msc' or in **Server Manager**, select **Tools**, and then **Certification Authority**.
+1. Sign in to your issuing CA with a domain account that has rights to manage the CA.
+2. Open the Certification Authority Microsoft Management Console (MMC). Either **Run**`certsrv.msc` or, in **Server Manager**, select **Tools**, and then **Certification Authority**.
3. Select the **Certificate Templates** node, select **Action** > **Manage**.
### Create the SCEP certificate template
-1. Create a v2 Certificate Template (with Windows 2003 compatibility) for use as the SCEP certificate template. You can:
+1. Create a v2 Certificate Template with Windows 2003 compatibility for use as the SCEP certificate template. You can:
- Use the *Certificate Templates* snap-in to create a new custom template.
- - Copy an existing template (like the Web Server template) and then update the copy to use as the NDES template.
+ - Copy an existing template, like the Web Server template, and then update the copy to use as the NDES template.
2. Configure the following settings on the specified tabs of the template:
- **General**:
@@ -214,51 +218,51 @@ The following sections require knowledge of Windows Server 2012 R2 or later, and
- Select **Supply in the request**. The Intune policy module for NDES enforces security.
- 
+ 
- **Extensions**:
- Ensure that **Description of Application Policies** includes **Client Authentication**.
Important
- Only add the application policies that you require. Confirm your choices with your security admins.
+ Add only the application policies that you require. Confirm your choices with your security admins.
- For iOS/iPadOS and macOS certificate templates, also edit **Key Usage** and make sure **Signature is proof of origin** isn't selected.
- 
+ 
- **Security**:
- Add the **NDES service account**. This account requires **Read** and **Enroll** permissions to this template.
- - Add additional Accounts for Intune administrators who will create SCEP profiles. These accounts require **Read** permissions to the template to enable these admins to browse to this template while creating SCEP profiles.
+ - Add accounts for Intune administrators who can create SCEP profiles. These accounts require **Read** permissions to the template to enable these admins to browse to this template while creating SCEP profiles.
- 
+ 
- **Request Handling**:
The following image is an example. Your configuration might vary.
- 
+ 
- **Issuance Requirements**:
The following image is an example. Your configuration might vary.
- 
+ 
3. Save the certificate template.
### Create the client certificate template
Note
-The following certificate is not used with the Certificate Connector for Microsoft Intune. This information is provided for those who have not yet replaced the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
+The following certificate isn't used with the Certificate Connector for Microsoft Intune. This information is for those who didn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
-The Microsoft Intune Connector requires a certificate with the *Client Authentication* Enhanced Key Usage and Subject name equal to the FQDN of the machine where the connector is installed. A template with the following properties is required:
+The Microsoft Intune Connector requires a certificate with the *Client Authentication* Enhanced Key Usage and Subject name equal to the FQDN of the machine where the connector is installed. You need a template with the following properties:
-- **Extensions** > **Application Policies** must contain **Client Authentication**
+- **Extensions** > **Application Policies** must contain **Client Authentication**.
- **Subject name** > **Supply in the request**.
-If you already have a template that includes these properties, you can reuse it, otherwise create a new template by either duplicating an existing one or creating a custom template.
+If you already have a template that includes these properties, you can reuse it. Otherwise, create a new template by either duplicating an existing one or creating a custom template.
### Create the server certificate template
-Communications between managed devices and IIS on the NDES server use HTTPS, which requires use of a certificate. You can use the **Web Server** certificate template to issue this certificate. Or, if you prefer to have a dedicated template, the following properties are required:
+Communications between managed devices and IIS on the NDES server use HTTPS, which requires a certificate. You can use the **Web Server** certificate template to issue this certificate. If you prefer to have a dedicated template, use the following properties:
- **Extensions** > **Application Policies** must contain **Server Authentication**.
- **Subject name** > **Supply in the request**.
@@ -270,24 +274,24 @@ If you have a certificate that satisfies both requirements from the client and s
### Grant permissions for certificate revocation
-For Intune to be able to revoke certificates that are no longer required, you must grant permissions in the Certificate Authority.
+To enable Intune to revoke certificates that are no longer required, grant permissions in the Certificate Authority.
On the server that hosts the certificate connector, use either the NDES server **system account** or a specific account such as the **NDES service account**.
-1. On your Certificate Authority console, Right-click the CA name and select **Properties**.
-2. In **Security** tab, select **Add**.
-3. Grant **Issue and Manage Certificates** permission:
+1. On your Certificate Authority console, right-click the CA name and select **Properties**.
+2. In the **Security** tab, select **Add**.
+3. Grant the **Issue and Manage Certificates** permission:
- - If you opt to use the NDES server **system account**, provide the permissions to the NDES server.
- - If you opt to use the **NDES service account**, provide permissions for that account instead.
+ - If you choose to use the NDES server **system account**, grant the permission to the NDES server.
+ - If you choose to use the **NDES service account**, grant the permission to that account.
### Modify the validity period of the certificate template
-It's optional to modify the validity period of the certificate template.
+You can modify the validity period of the certificate template.
After you create the SCEP certificate template, you can edit the template to review the **Validity period** on the **General** tab.
-By default, Intune uses the value configured in the template, but you can configure the CA to allow the requester to enter a different value, so that value can be set from within the Microsoft Intune admin center.
+By default, Intune uses the value configured in the template, but you can configure the CA to allow the requester to enter a different value, so you can set that value from within the Microsoft Intune admin center.
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.
@@ -303,20 +307,22 @@ On the CA, run the following commands:
## Publish certificate templates
-1. On the issuing CA, use the Certification Authority snap-in to publish the certificate template. Select the **Certificate Templates** node, select **Action** > **New** > **Certificate Template to Issue**, and then select the certificate template you created in the previous section.
-2. Validate that the template has published by viewing it in the **Certificate Templates** folder.
+On the issuing CA, use the Certification Authority snap-in to publish the certificate template.
+
+1. Select the **Certificate Templates** node, select **Action** > **New** > **Certificate Template to Issue**, and then select the certificate template you created in the previous section.
+2. Validate that the template is published by viewing it in the **Certificate Templates** folder.
## Set up NDES
-The following procedures can help you configure the Network Device Enrollment Service (NDES) for use with Intune. These are provided as examples as the actual configuration might vary depending on your version of Windows Server. Ensure required configurations you add like those for .NET Framework meet the [prerequisites for the Certificate Connector for Microsoft Intune](connector/prerequisites).
+The following procedures can help you configure the Network Device Enrollment Service (NDES) for use with Intune. These procedures are provided as examples, as the actual configuration might vary depending on your version of Windows Server. Ensure required configurations you add, like those for .NET Framework, meet the [prerequisites for the Certificate Connector for Microsoft Intune](connector/prerequisites).
For more information about NDES, see [Network Device Enrollment Service Guidance](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831498%28v=ws.11%29).
### Install the NDES service
-1. On the server that will host your NDES service, sign in as an **Enterprise Administrator**, and then use the [Add Roles and Features Wizard](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831809%28v=ws.11%29) to install NDES:
+1. On the server that you want to host your NDES service, sign in as an **Enterprise Administrator**, and then use the [Add Roles and Features Wizard](/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831809%28v=ws.11%29) to install NDES:
- 1. In the Wizard, select **Active Directory Certificate Services** to gain access to the AD CS Role Services. Select **Network Device Enrollment Service**, uncheck **Certification Authority**, and then complete the wizard.
+ 1. In the wizard, select **Active Directory Certificate Services** to access the AD CS Role Services. Select **Network Device Enrollment Service**, uncheck **Certification Authority**, and then complete the wizard.
Tip
@@ -347,14 +353,14 @@ To configure the NDES service, use an account that is an *Enterprise Administrat
- In **Role Services**, select the **Network Device Enrollment Service**.
- In **Service Account for NDES**, specify the NDES Service Account.
- - In **CA for NDES**, click **Select**, and then select the issuing CA where you configured the certificate template.
+ - In **CA for NDES**, select the issuing CA where you configured the certificate template.
- In **Cryptography for NDES**, set the key length to meet your company requirements.
- In **Confirmation**, select **Configure** to complete the wizard.
2. After the wizard completes, update the following registry key on the computer that hosts the NDES service:
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MSCEP\`
- To update this key, identify the certificate templates' **Purpose** (found on its **Request Handling** tab). Then, update the corresponding registry entry by replacing the existing data with the name of the certificate template (not the display name of the template) that you specified when you created the certificate template.
+ To update this key, identify the certificate templates' **Purpose** on the **Request Handling** tab. Then, update the corresponding registry entry by replacing the existing data with the name of the certificate template, not the display name of the template, that you specified when you created the certificate template.
The following table maps the certificate template purpose to the values in the registry:
@@ -364,13 +370,13 @@ To configure the NDES service, use an account that is an *Enterprise Administrat | Encryption | EncryptionTemplate | Key Encipherment |
| Signature and encryption | GeneralPurposeTemplate | Key Encipherment Digital Signature |
- For example, if the Purpose of your certificate template is **Encryption**, then edit the **EncryptionTemplate** value to be the name of your certificate template.
-3. Restart the server that hosts the NDES service. Don't use **iisreset**; iireset doesn't complete the required changes.
-4. Browse to *http://Server\_FQDN/certsrv/mscep/mscep.dll*. You should see an NDES page similar to the following image:
+ For example, if the Purpose of your certificate template is **Encryption**, edit the **EncryptionTemplate** value to be the name of your certificate template.
+3. Restart the server that hosts the NDES service. Don't use **iisreset** because it doesn't complete the required changes.
+4. Browse to `http://<Server_FQDN>/certsrv/mscep/mscep.dll`. You should see an NDES page similar to the following image:
- 
+ 
- If the web address returns a **503 Service unavailable**, check the computers event viewer. This error commonly occurs when the application pool is stopped due to a missing permission for the NDES service account.
+ If the web address returns a **503 Service unavailable** error, check the computer's event viewer. This error commonly occurs when the application pool stops due to a missing permission for the NDES service account.
### Install and bind certificates on the server that hosts NDES
@@ -382,7 +388,7 @@ On the NDES server, add a **Server authentication certificate**.
1. Request a **server authentication** certificate from your internal CA or public CA, and then install the certificate on the server.
- Depending how you expose your NDES to the internet, there are different requirements.
+ Depending on how you expose your NDES to the internet, there are different requirements.
A good configuration is:
@@ -391,20 +397,22 @@ On the NDES server, add a **Server authentication certificate**.
Note
- If you are using Microsoft Entra application proxy, the Microsoft Entra application proxy connector will translate the requests from the external URL to the internal URL. As such, NDES will only respond to requests directed to the internal URL, usually the FQDN of the NDES Server.
+ If you're using Microsoft Entra application proxy, the Microsoft Entra application proxy connector translates the requests from the external URL to the internal URL. As such, NDES only responds to requests directed to the internal URL, usually the FQDN of the NDES Server.
- In this situation, the external URL is not required.
+ In this situation, the external URL isn't required.
2. Bind the server authentication certificate in IIS:
- 1. After installing the server authentication certificate, open **IIS Manager**, and select the **Default Web Site**. In the **Actions** pane, select **Bindings**.
+ 1. After you install the server authentication certificate, open **IIS Manager**, and select the **Default Web Site**. In the **Actions** pane, select **Bindings**.
2. Select **Add**, set **Type** to **https**, and then confirm the port is **443**.
3. For **SSL certificate**, specify the server authentication certificate.
Note
-When configuring NDES for the Certificate Connector for Microsoft Intune , only the Server authentication certificate is used. If you're configuring NDES to support the older certificate connector (NDESConnectorSetup.exe), you must also configure a *Client authentication certificate*. You can use a single certificate for both *server authentication* and *client authentication* when that certificate is configured to meet the criteria of both uses. Regarding the Subject Name, it must meet the *client authentication* certificate requirements.
+When configuring NDES for the Certificate Connector for Microsoft Intune, only the Server authentication certificate is used. If you're configuring NDES to support the older certificate connector (NDESConnectorSetup.exe), you must also configure a *Client authentication certificate*. You can use a single certificate for both *server authentication* and *client authentication* when that certificate is configured to meet the criteria of both uses.
+
+Regarding the Subject Name, it must meet the *client authentication* certificate requirements.
-The following information is provided for those who have not yet replaced the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
+The following information is provided for those who didn't replace the older connector for SCEP (installed by NDESConnectorSetup.exe) with the new connector software.
- **Client authentication certificate**