Renewall Certificate from Intune

Handian Sudianto 7,676 Reputation points
2026-11-19T00:11:03.1166667+00:00

We have implemented 802.1X authentication using certificates. The certificates are issued from our on-premises Active Directory Certificate Services (AD CS) environment through the Intune Certificate Connector, and Intune deploys the certificates to the endpoints.

When a certificate is about to expire or has expired, what is the renewal process handled by Intune?

Will Intune request and deploy a new certificate while keeping the existing certificate on the endpoint, resulting in two certificates with the same purpose but different expiration dates?

Or will Intune automatically replace the existing certificate with the newly issued certificate and remove the old one?

Windows for business | Windows Server | Directory services | Certificates and public key infrastructure (PKI)
0 comments No comments

2 answers

Sort by: Newest
  1. Hoang Le Huy 2,240 Reputation points Independent Advisor
    2026-11-19T00:54:56.8366667+00:00

    Hello Handian Sudianto,

    For Intune-issued PKCS or SCEP certificates that are sourced from on-premises AD CS through the Intune Certificate Connector, the normal behavior is that Intune initiates renewal before expiration based on the certificate profile's Renewal Threshold (%) configuration and requests a new certificate from the CA. The renewed certificate is issued as a new certificate, and Microsoft documentation does not state that an in-place renewal overwrites the existing certificate object on the device.

    More importantly, Microsoft documents specific scenarios where certificates are removed or revoked, such as device wipe, retire, unenrollment, profile removal, or loss of profile targeting. The documentation does not list successful renewal as an event that automatically deletes the previous certificate from the Windows certificate store.

    Therefore, for 802.1X deployments, you should expect that a newly renewed certificate can coexist with the previous certificate during the transition period, resulting in two certificates with the same purpose but different validity periods until cleanup conditions occur. Microsoft confirms removal behavior separately from renewal behavior and does not document automatic replacement-and-delete semantics during a standard renewal cycle.

    From an operational perspective, Windows and the EAP-TLS supplicant normally select a valid certificate based on certificate selection criteria, EKU, trust chain, and expiration status, so temporary coexistence of old and new certificates is generally expected and does not normally disrupt 802.1X authentication.

    If you need to validate your exact deployment behavior, the supported approach is to review the issued certificates in the local machine or user certificate store (certlm.msc or certmgr.msc) after a renewal event and compare thumbprints and expiration dates, because Microsoft's published documentation describes renewal and removal independently but does not explicitly state that renewal removes the prior certificate.

    If my answer is useful for you, please hit Accept the answer for me please.

    HL.

    Was this answer helpful?


  2. AI answer

    2026-11-19T00:11:56.0666667+00:00

    Configure the certificate profile’s Renewal threshold so Intune requests a new certificate before expiry, but do not assume that a successful SCEP or PKCS renewal automatically removes the previous 802.1X certificate from a Windows endpoint.

    Renewal behavior

    SCEP profiles

    In the Intune admin center, open:

    Devices → Manage devices → Configuration → select the SCEP certificate profile → Properties → Configuration settings.

    The Renewal threshold (%) specifies how much certificate lifetime remains when renewal starts. For example, 20 causes renewal to begin after 80% of the lifetime has elapsed. Intune continues renewal attempts until successful. A successful SCEP renewal issues a new certificate with a new public/private key pair.^1^

    PKCS profiles

    PKCS profiles also expose Renewal threshold (%) for all supported platforms; Microsoft recommends 20%. The configured certificate validity can be from five days through 24 months, although the AD CS template can affect the resulting validity.^2^

    The Certificate Connector service account performs CA interactions for issuance, renewal, and revocation.^3^

    What happens to the existing certificate?

    The Intune documentation confirms creation of a new certificate during renewal, but it does not explicitly state that successful renewal of an Intune-delivered SCEP or PKCS 802.1X certificate on Windows immediately deletes the previous certificate.

    Microsoft documents these Windows cleanup conditions separately:^4^

    • SCEP: The certificate is revoked and removed when the device is unenrolled, wiped, retired, removed from the targeted Microsoft Entra group, or the profile is removed from its assignment.
    • PKCS: The certificate is removed when its PKCS profile no longer targets the device or user. Unenroll, wipe, and retire revoke and remove it.
    • Updating a Windows SCEP profile revokes its certificate; updating a Windows PKCS profile does not automatically remove the existing PKCS certificate.

    Therefore, during a normal renewal window, plan for a possible temporary overlap where both the older and newer certificates are visible. Do not remove the old certificate manually as part of routine renewal: if a targeted certificate is manually deleted, Intune detects that the expected certificate is missing and issues another one.^4^

    The Windows MDM documentation stating that the client gets a new certificate and deletes the old one concerns the MDM enrollment client certificate. It should not be used to infer cleanup behavior for a separate SCEP or PKCS certificate used by 802.1X.^5^

    Validate the behavior in your environment

    Test renewal against a pilot device before the production threshold:

    1. Shorten the validity period on a dedicated test template/profile.
    2. Set a suitable renewal threshold and synchronize the test device.
    3. On Windows, inspect the applicable certificate store:
      • Device certificate: run certlm.msc, then open Personal → Certificates.
      • User certificate: run certmgr.msc, then open Personal → Certificates.
    4. Compare the serial number, thumbprint, validity period, subject/SAN, and private-key status.
    5. Open Event Viewer → Applications and Services Logs → Microsoft → Windows → DeviceManagement-Enterprise-Diagnostics-Provider → Admin. For SCEP delivery, Event 39 indicates that the certificate installed successfully.^6^
    6. Confirm the RADIUS/NPS certificate-selection rules accept the renewed certificate and do not rely on a fixed thumbprint.

    If renewal fails, inspect the same DeviceManagement event log. For PKCS, also check the CA server’s Application log and the Certificate Connector logs; Microsoft’s PKCS troubleshooting guidance covers pending requests, policy denial, RPC failures, and incorrect CA profile settings.^7^


    References

    1. Create and assign SCEP certificate profiles in Intune
    2. Configure and use PKCS certificates with Intune
    3. Certificate Connector for Microsoft Intune
    4. Remove SCEP and PKCS certificates in Microsoft Intune
    5. Certificate Renewal
    6. Troubleshooting the delivery of certificates provisioned by SCEP to devices in Microsoft Intune
    7. Troubleshooting PKCS certificate deployment in Intune
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.