Skip to content

Commit ca49d4b

Browse files
authored
Merge pull request #6917 from Brenduns/13677533-cert-connector-deprecation
13677533 - Edits for certificate connectors and deprecated versions
2 parents 092e05f + 7540cf1 commit ca49d4b

5 files changed

Lines changed: 18 additions & 24 deletions

memdocs/intune/protect/certificate-connector-overview.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 02/18/2022
10+
ms.date: 02/28/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -36,7 +36,7 @@ For Microsoft Intune to support use of certificates for authentication and the s
3636
This article introduces the Certificate Connector for Microsoft Intune, its lifecycle, and how to keep it up to date.
3737

3838
> [!TIP]
39-
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft** Intune replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. With the release of version 6.2109.51.0 of the Certificate Connector for Microsoft, the previous connectors are no longer supported.
39+
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft Intune** replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. With the release of version 6.2109.51.0 of the Certificate Connector for Microsoft, the previous connectors are no longer supported.
4040
4141
## Connector overview
4242

@@ -87,7 +87,7 @@ The Certificate Connector for Microsoft Intune supports:
8787

8888
Periodically, updates to the certificate connector are released. Announcements for new updates appear in the [What's new for the Certificate Connector](#whats-new-for-the-certificate-connector) section in this article.
8989

90-
Intune supports each connector release for six months after its released. After the six months have passed, the connector is no longer be supported and might not function as expected.
90+
Intune supports each connector release for six months after its released. After the six months have passed, the connector is no longer supported and might not function as expected.
9191

9292
If you don’t allow the connector to automatically update, plan to manually update it to the latest version at the first opportunity.
9393

@@ -217,12 +217,14 @@ All events are tagged with a Task Category to aid in filtering. Task categories
217217

218218
## What's new for the Certificate Connector
219219

220-
Updates for the Certificate Connector for Microsoft Intune are released periodically. When we update the connector, you can read about the changes here.
220+
Updates for the Certificate Connector for Microsoft Intune are released periodically and then [supported for six months](#lifecycle). When we update the connector, you can read about the changes here.
221221

222222
New updates for the connector can take a week or more to become available for each tenant.
223223

224+
<!-- Note for future use if/when relevant>
224225
> [!IMPORTANT]
225-
> On February 1, 2022, Intune certificate connectors earlier than version **6.1806.5.0** will no longer allow you to issue certificates to users and devices.
226+
> On [DATE], certificate connectors earlier than version [version] will no longer allow you to issue certificates to users and devices.
227+
-->
226228

227229
### February 18, 2022
228230

memdocs/intune/protect/certificate-connectors.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 12/02/2021
10+
ms.date: 02/28/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -32,17 +32,15 @@ ms.collection: M365-identity-device-management
3232

3333
# Certificate connectors for Microsoft Intune
3434

35+
<!-- The details in this article are for deprecated functionality. These two connectors are no longer supported and this article will be retired at a future date. -->
36+
3537
> [!IMPORTANT]
36-
> As of July 29, 2021, the **Certificate Connector for Microsoft** Intune replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. Support for the previous connectors ends on 9/22/2021 with the release of version 6.2109.51.0 of the Certificate Connector for Microsoft.
37-
>
38-
> On February 1, 2022, Intune certificate connectors earlier than version 6.1806.5.0 will no longer allow you to issue certificates to users and devices.
38+
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft Intune** replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. Support for the previous connectors that are described in this article, ended on 9/22/2021 with the release of version 6.2109.51.0 of the Certificate Connector for Microsoft.
3939
>
4040
> If you need to install a new certificate connector, or reinstall a connector, install the newer Certificate Connector for Microsoft Intune. For more information, see [Certificate Connector for Microsoft Intune](../protect/certificate-connector-overview.md).
4141
4242
To support the use of certificates for authentication and the signing and encryption of email using S/MIME, Intune requires the use of a certificate connector. A certificate connector is software you install on an on-premises server. The connector enables cloud-managed devices to provision certificates from on-premises infrastructure, like an issuing Certificate Authority.
4343

44-
This article describes the available connectors, their lifecycle, prerequisites for use, and how to keep them up to date.
45-
4644
## Available connectors
4745

4846
There are two certificate connectors for Intune. Each has its own uses and requirements.
@@ -146,6 +144,9 @@ For guidance on installation of this connector, see [Configure infrastructure to
146144

147145
## Connector Lifecycle
148146

147+
> [!IMPORTANT]
148+
> Beginning on July 29, 2021, the [**Certificate Connector for Microsoft Intune**](../protect/certificate-connector-overview.md) replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors.
149+
149150
Periodically, updated versions of certificate connectors are released. Announcements for new connector releases appear in the [What’s New](../fundamentals/whats-new.md) article for Intune and in the [What's new for Connectors](#whats-new-for-connectors) section near the end of this article.
150151

151152
When a new version releases, support for the previous version is deprecated with a limited grace period for its continued use. After the grace period expires, support for that deprecated version ends, and it can stop functioning at any time. The grace period is six months.
@@ -270,7 +271,7 @@ All events are tagged with a Task Category to aid in filtering. Task categories
270271
Updates for the two certificate connectors are released periodically. When we update a connector, you can read about the changes here.
271272

272273
> [!IMPORTANT]
273-
> On February 1, 2022, Intune certificate connectors earlier than version 6.1806.5.0 will no longer allow you to issue certificates to users and devices. See the note at the to start of this article for detail on moving to the new **Certificate Connector for Microsoft**.
274+
> On June 1, 2022, Intune certificate connectors earlier than version 6.2101.13.0 will no longer allow you to issue certificates to users and devices. See the note at the to start of this article for detail on moving to the new **Certificate Connector for Microsoft**.
274275
275276
### PFX Certificate Connector release history
276277

memdocs/intune/protect/certificates-imported-pfx-configure.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords:
55
author: brenduns
66
ms.author: brenduns
77
manager: dougeby
8-
ms.date: 09/22/2021
8+
ms.date: 02/28/2022
99
ms.topic: how-to
1010
ms.service: microsoft-intune
1111
ms.subservice: protect
@@ -66,9 +66,6 @@ To use imported PKCS certificates with Intune, you'll need the following infrast
6666
- [Prerequisites](certificate-connector-prerequisites.md).
6767
- [Installation and configuration](certificate-connector-install.md).
6868

69-
> [!TIP]
70-
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft** Intune replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. With the release of version 6.2109.51.0 of the Certificate Connector for Microsoft, the previous connectors are no longer supported.
71-
7269
- **Windows Server**:
7370

7471
The certificate connector installs on a Windows Server that meets the connectors [prerequisites](certificate-connector-prerequisites.md).

memdocs/intune/protect/certificates-pfx-configure.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords:
55
author: brenduns
66
ms.author: brenduns
77
manager: dougeby
8-
ms.date: 01/18/2022
8+
ms.date: 02/28/2022
99
ms.topic: how-to
1010
ms.service: microsoft-intune
1111
ms.subservice: protect
@@ -68,9 +68,6 @@ To use PKCS certificates with Intune, you'll need the following infrastructure:
6868
- [Prerequisites](certificate-connector-prerequisites.md).
6969
- [Installation and configuration](certificate-connector-install.md).
7070

71-
> [!TIP]
72-
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft Intune** replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. With the release of version 6.2109.51.0 of the Certificate Connector for Microsoft, the previous connectors are no longer supported.
73-
7471
## Export the root certificate from the Enterprise CA
7572

7673
To authenticate a device with VPN, WiFi, or other resources, a device needs a root or intermediate CA certificate. The following steps explain how to get the required certificate from your Enterprise CA.

memdocs/intune/protect/certificates-scep-configure.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords:
55
author: brenduns
66
ms.author: brenduns
77
manager: dougeby
8-
ms.date: 01/04/2022
8+
ms.date: 02/28/2022
99
ms.topic: how-to
1010
ms.service: microsoft-intune
1111
ms.subservice: protect
@@ -59,9 +59,6 @@ To support SCEP, the following on-premises infrastructure must run on servers th
5959
- [Prerequisites](certificate-connector-prerequisites.md).
6060
- [Installation and configuration](certificate-connector-install.md).
6161

62-
> [!TIP]
63-
> Beginning on July 29, 2021, the **Certificate Connector for Microsoft** Intune replaces the use of *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*. The new connector includes the functionality of both previous connectors. With the release of version 6.2109.51.0 of the Certificate Connector for Microsoft, the previous connectors are no longer supported.
64-
6562
- **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](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj125375(v=ws.11)).
6663

6764
If your CA runs Windows Server 2008 R2 SP1, you must [install the hotfix from KB2483564](https://support.microsoft.com/kb/2483564/).

0 commit comments

Comments
 (0)