Skip to content

Commit fcfc40b

Browse files
authored
Merge pull request #6536 from daniel-microsoft/patch-7
Clarify remove-certificates.md
2 parents 6039ca3 + 806f166 commit fcfc40b

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

memdocs/intune/protect/remove-certificates.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
author: brenduns
99
ms.author: brenduns
1010
manager: dougeby
11-
ms.date: 11/30/2021
11+
ms.date: 01/13/2022
1212
ms.topic: how-to
1313
ms.service: microsoft-intune
1414
ms.subservice: protect
@@ -40,6 +40,9 @@ These certificates can be removed when you [wipe](../remote-actions/devices-wipe
4040
> 1. Wipe or retire the user's device.
4141
> 2. Remove the user from on-premises Active Directory or Azure AD.
4242
43+
The majority of this article applies to SCEP and PKCS certificate profiles, but not to imported PKCS certificates. Imported PKCS certificates are removed by Intune when company data is removed from the device, when a device is unenrolled from management, or a user is no longer targeted by the deployment of the certificate.
44+
45+
4346
## Manually deleted certificates
4447

4548
Manual deletion of a certificate is a scenario that applies across platforms and certificates provisioned by SCEP or PKCS certificate profiles. For example, a user might delete a certificate from a device, when the device remains targeted by a certificate policy.
@@ -254,4 +257,4 @@ PKCS certificates stay on the device (certificates aren't revoked or removed) wh
254257

255258
## Next steps
256259

257-
[Use certificates for authentication](certificates-configure.md)
260+
[Use certificates for authentication](certificates-configure.md)

0 commit comments

Comments
 (0)