You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Microsoft Copilot|[iOS](https://apps.apple.com/us/app/microsoft-copilot/id6472538445)|✔|No settings|✔ Supported for v28.1.420324001 or later|N/A|✖|✖|N/A|✖|
69
-
|Microsoft Edge|[Android](https://play.google.com/store/apps/details?id=com.microsoft.emmx)|✔|✔ see [Edge app config](manage-microsoft-edge.md)|✔|N/A|N/A|N/A|✔|✔|
70
-
|Microsoft Edge|[iOS](https://apps.apple.com/us/app/microsoft-edge/id1288723196)|✔|✔ see [Edge app config](manage-microsoft-edge.md)|✔|N/A|N/A|N/A|✔|✔|
69
+
|Microsoft Edge|[Android](https://play.google.com/store/apps/details?id=com.microsoft.emmx)|✔|✔ see [Edge app config](manage-microsoft-edge.md)|✔|N/A|N/A|N/A|✔|✔ Supported for v125.0.2535.96 or later|
70
+
|Microsoft Edge|[iOS](https://apps.apple.com/us/app/microsoft-edge/id1288723196)|✔|✔ see [Edge app config](manage-microsoft-edge.md)|✔|N/A|N/A|N/A|✔|✔ Supported for v126.2592.56 or later|
|Microsoft Teams|[iOS](https://apps.apple.com/us/app/microsoft-teams/id1113153706)|✔|No settings|✔|N/A|✔ Supported for v2.0.22 or later|✔|✔|✔|
96
+
|Microsoft Teams|[Android](https://play.google.com/store/apps/details?id=com.microsoft.teams)|✔|No settings|✔|N/A|✔|✔|✔|✔ Supported for v1416/1.0.0.2023226005 (2023226050) or later|
97
+
|Microsoft Teams|[iOS](https://apps.apple.com/us/app/microsoft-teams/id1113153706)|✔|No settings|✔|N/A|✔ Supported for v2.0.22 or later|✔|✔|✔ Supported for v6.9.2 or later|
Copy file name to clipboardExpand all lines: memdocs/intune/fundamentals/in-development.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ Applies to:
165
165
166
166
### New strong mapping requirements for Intune-issued SCEP certificates<!-- 29005591 -->
167
167
168
-
To align with the Windows Kerberos Distribution Center's (KDC) strong mapping attribute requirements described in [KB5014754](https://support.microsoft.com/help/5014754), SCEP certificates issued by Microsoft Intune will be required to have the following tag in the Subject Alternative Name (SAN) field:
168
+
To align with the Windows Kerberos Key Distribution Center's (KDC) strong mapping attribute requirements described in [KB5014754](https://support.microsoft.com/help/5014754), SCEP certificates issued by Microsoft Intune will be required to have the following tag in the Subject Alternative Name (SAN) field:
Copy file name to clipboardExpand all lines: memdocs/intune/protect/certificate-connector-install.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
# required metadata
3
3
4
-
title: Install the Certificate Connector for Microsoft Intune - Azure | Microsoft Docs
4
+
title: Install the Certificate Connector for Microsoft Intune
5
5
description: Learn how to install and configure the unified Certificate Connector for Microsoft Intune, which supports SCEP, PKCS, imported PKCS, and certificate revocation.
6
6
keywords:
7
7
author: lenewsad
8
8
ms.author: lanewsad
9
9
manager: dougeby
10
-
ms.date: 09/11/2023
10
+
ms.date: 10/09/2024
11
11
ms.topic: how-to
12
12
ms.service: microsoft-intune
13
13
ms.subservice: protect
@@ -33,7 +33,7 @@ ms.collection:
33
33
34
34
# Install the Certificate Connector for Microsoft Intune
35
35
36
-
To support your use of certificates with Intune, you can install the Certificate Connector for Microsoft Intune on any Windows Server that meets the [connector prerequisites](../protect/certificate-connector-prerequisites.md). The following sections will help you install and then configure the connector. This article also explains how to modify a previously installed connector, and how to remove the connector from a server.
36
+
To support your use of certificates with Intune, you can install the Certificate Connector for Microsoft Intune on any Windows Server that meets the [connector prerequisites](../protect/certificate-connector-prerequisites.md). The following sections help you install and then configure the connector. This article also explains how to modify a previously installed connector, and how to remove the connector from a server.
37
37
38
38
## Download and install the connector software
39
39
@@ -47,11 +47,11 @@ To support your use of certificates with Intune, you can install the Certificate
47
47
48
48
4. Sign in to the Windows Server that will host the certificate connector and confirm that the [prerequisites for the certificate connector](../protect/certificate-connector-prerequisites.md) are installed.
49
49
50
-
If you’ll use SCEP with a Microsoft Certification Authority (CA), confirm that the Network Device Enrollment Service (NDES) role is installed.
50
+
To use the Simple Certificate Enrollment Protocol (SCEP) with a Microsoft Certification Authority (CA), confirm that the Network Device Enrollment Service (NDES) role is installed.
51
51
52
52
5. Use an account with admin permissions to the server to run the installer (**IntuneCertificateConnector.exe**). The installer also installs the policy module for NDES. The policy module runs as an application in IIS.
53
53
54
-
> [!NOTE]
54
+
> [!NOTE]
55
55
> When **IntuneCertificateConnector.exe** runs to install a new connector or an existing connector auto upgrades while the Windows Event Viewer is open, the installation process logs a message similar to the following with an Event ID 1000 from the source *Microsoft-Intune-CertificateConnectors cannot be found*:
56
56
>
57
57
> - Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
@@ -73,13 +73,13 @@ After a connector installs, you can run the installation program again to uninst
73
73
74
74
## Configure the certificate connector
75
75
76
-
To configure the certificate connector, you use the **Certificate Connector for Microsoft Intune** wizard. The configuration can start automatically when you choose *Configure Now* at the end of a certificate connector install, or manually by opening an elevated command prompt and running **C:\Program Files\Microsoft Intune\PFXCertificateConnector\ConnectorUI\PFXCertificateConnectorUI.exe**. An example is provided below. The command must be run as an administrator.
76
+
To configure the certificate connector, you use the **Certificate Connector for Microsoft Intune** wizard. The configuration can start automatically when you choose *Configure Now* at the end of a certificate connector install, or manually by opening an elevated command prompt and running **C:\Program Files\Microsoft Intune\PFXCertificateConnector\ConnectorUI\PFXCertificateConnectorUI.exe**. An example follows. The command must be run as an administrator.
Each time **Certificate Connector for Microsoft Intune** starts on a server you’ll see the following *Welcome* page:
82
+
Each time **Certificate Connector for Microsoft Intune** starts on a server you should see the following *Welcome* page:
83
83
84
84
:::image type="content" source="./media/certificate-connector-install/begin-connector-configuration.png" alt-text="Welcome page of the Certificate Connector for Microsoft Intune wizard.":::
85
85
@@ -92,11 +92,11 @@ Use the following procedure to both configure a new connector and modify a previ
92
92
93
93
2. On *Features*, select the checkbox for each connector feature you want to install on this server, and then select **Next**. Options include:
94
94
95
-
-**SCEP**: Select this option to enable certificate delivery to devices from a Microsoft Active Directory Certification Authority using the SCEP protocol. Devices that submit a certificate request will generate a private/public key pair and submit only the public key as part of that request.
95
+
-**SCEP**: Select this option to enable certificate delivery to devices from a Microsoft Active Directory Certification Authority using the SCEP protocol. Devices that submit a certificate request generate a private/public key pair and submit only the public key as part of that request.
96
96
97
-
-**PKCS**: Select this option to enable certificate delivery to devices from a Microsoft Active Directory Certification Authority in PKCS #12 format. Ensure you’ve set up all the necessary prerequisites.
97
+
-**PKCS**: Select this option to enable certificate delivery to devices from a Microsoft Active Directory Certification Authority in PKCS #12 format. Ensure you set up all the necessary prerequisites.
98
98
99
-
-**PKCS imported certificates**: Select this option to enable certificate delivery to devices for pfx certificates that you've imported to Intune. Ensure you’ve set up all the necessary prerequisites.
99
+
-**PKCS imported certificates**: Select this option to enable certificate delivery to devices for pfx certificates that you import to Intune. Ensure you set up all the necessary prerequisites.
100
100
101
101
-**Certificate revocation**: Select this option to enable automatic certificate revocation for certificates issued from a Microsoft Active Directory Certification Authority.
102
102
@@ -108,12 +108,13 @@ Use the following procedure to both configure a new connector and modify a previ
108
108
-**Domain user account** – Use any domain user account that is an administrator on the Windows Server.
109
109
110
110
4. On the *Proxy* page, add details for your proxy server if you require a proxy for internet access. For example, `http://proxy.contoso.com`.
111
-
> [!IMPORTANT]
111
+
112
+
> [!IMPORTANT]
112
113
> Be sure to include the HTTP or HTTPS prefix. This is a change from the proxy configuration for previous versions of the connector.
113
114
114
115
5. On the *Prerequisites* page, the wizard runs several checks on the server before the configuration can begin. Review and resolve any errors or warnings before you continue.
115
116
116
-
6. On the *Microsoft Entra sign-in* page, select the environment that hosts your Microsoft Entra ID, and then select **Sign In**. You’ll then be asked to authenticate your access. An Intune license is required for the account that you sign in with which can be either a Global Administrator or an Intune Administrator.
117
+
6. On the *Microsoft Entra sign-in* page (which appears as *Azure AD Sign-In*), select the environment that hosts your Microsoft Entra ID, and then select **Sign In**. Then when prompted, authenticate your access. An Intune license is required for the account that you sign in with which can be either a Global Administrator or an Intune Administrator.
117
118
118
119
Unless you use a government cloud, use the default of **Public Commercial Cloud** for *Environment*.
119
120
@@ -132,8 +133,8 @@ Use the following procedure to both configure a new connector and modify a previ
132
133
After the configuration completes successfully and the wizard closes, the Certificate Connector for Microsoft Intune is now ready for use.
133
134
134
135
> [!TIP]
135
-
> It might be helpful to rename the connector to reference the server the connector is installed on.
136
-
>
136
+
> It might be helpful to rename the connector to reference the server the connector is installed on.
137
+
>
137
138
> To rename the connector, in the Microsoft Intune admin center, select **Tenant administration** > **Connectors and tokens** > **Certificate connectors**. Select the connector you want to rename. In **Name**, enter the name you want to use, and then select **save**.
138
139
139
140
## Modify the connector configuration
@@ -143,9 +144,9 @@ After you configure a Certificate Connector for Microsoft Intune on a server, yo
143
144
## Remove the connector
144
145
145
146
To uninstall the Certificate Connector for Microsoft Intune from a Windows Server, on the server run **IntuneCertificateConnector.exe**, which is the same [software you use to install the connector](#download-and-install-the-connector-software). When run on a server that has the connector installed, the only available option is to remove the current connector installation.
0 commit comments