--- title: Microsoft Certificate Authority \(CA\) certificates discovery description: The ServiceNow Discovery application can discover Microsoft Certificate Authority \(CA\) certificates using the Microsoft CA - Certificate Management pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery-and-service-mapping-patterns/microsoft-ca-discovery.html release: australia product: Discovery and Service Mapping Patterns classification: discovery-and-service-mapping-patterns topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 4 keywords: [Microsoft Certificate Authority \(CA\) certificates discovery, Microsoft CA certificates discovery, Microsoft CA - Certificate Management, Microsoft CA - Certificate Management pattern, Microsoft CA certificates, Microsoft Certificate Authority \(CA\) certificates, Microsoft Certificate Authority \(CA\) certificates pattern, Microsoft CA certificates pattern] breadcrumb: [Available on-premise discovery patterns, Discovery patterns used by ITOM Visibility, ITOM Visibility, IT Operations Management] --- # Microsoft Certificate Authority \(CA\) certificates discovery The ServiceNow Discovery application can discover Microsoft Certificate Authority \(CA\) certificates using the Microsoft CA - Certificate Management pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Request apps on the Store Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html). Starting with version 1.27.0, Discovery and Service Mapping Patterns supports discovering the subject alternative name \(SAN\) for both the all request IDs and the template ID discovery methods. ## Prerequisites - **Verify the following applications are up to date** - Discovery and Service Mapping Patterns - CMDB CI Class Models - **Verify the certificate Authority process** Ensure that the CA process is up and running on the host machine. - **Verify previous Windows discovery** Verify a Windows host was discovered during a previous horizontal discovery. For more information, see [Windows discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/itom-visibility/r_DataCollDiscoWindowsComputers.md). - **Create a serverless discovery schedule** Create a discovery schedule to perform targeted discovery of Microsoft CA certificates using the host on which the CA process is running. For more information, see [Create a serverless schedule for Microsoft CA discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/create-serverless-schedule-ms-ca.md). ## Data collected by Discovery during horizontal discovery Discovery populates the data in the CMDB when running the Microsoft CA - Certificate Management pattern.
Field Description
Fingerprint \[fingerprint\] Hash value of the certificate.
Fingerprint algorithm \[fingerprint\_algorithm\] Algorithm used to hash the certificate​.
Subject common name \[subject\_common\_name\] Identifies the host name/domain associated with the certificate, listed in the certificate's **Subject​** field.
Subject distinguished name \[subject\_distinguished\_name\] Identifying information of the subject listed in the certificate's **Subject​** field.​
Issuer distinguished name \[issuer\_distinguished\_name\] Distinguished name of the issuer​.
Comments \[comments\] Includes a readable description for users.
Renewal tracking \[renewal\_tracking\] Indicates whether to create any priority 1 or priority 3 tasks for the expiring certificates.​
Certificate Template \[cert\_template\] Certificate template that defines the policies and rules that a CA uses when a request for a certificate is received.
Certificate ThumbPrint \[thumb\_print\]​ Unique identifier for certificates in applications when making trust decisions, in configuration files, and when displayed in interfaces.
Issuer common name \[issuer\_common\_name\] Common name of the issuer​.
Valid from \[valid\_from\] Validity start period of the certificate.
Serial Number \[serial\_number\] Serial number of the certificate.
Subject country \[subject\_country\] Two-letter country code in the certificate's **Subject​** field.
Subject organization \[subject\_organization\] Organization listed in the certificate's **Subject​** field.
Issuer \[issuer\] Entity that signed and issued the certificate.​
Subject organizational unit \[subject\_organizational\_unit\] Organizational unit listed in the certificate's **Subject​** field..​
Subject alternative name \[subject\_alternative\_name\] List of fully qualified domain names secured by the certificate​, listed in the certificate's **Subject​** field.
Valid to \[valid\_to\] Validity end period of the certificate.
Name \[name\] Name of the CI.
State \[state\] Life-cycle state of the certificate​.For example: Installed, Issued, or Revoked.
Root issuer \[root\_issuer\] Root entity that signed and issued the immediate certificate.
Subject locality \[subject\_locality\] Locality listed in the certificate's **Subject​** field.
Subject state \[subject\_state\] State listed in the certificate's **Subject​** field.
Operational status \[operational\_status\] Indicates whether the certificate is valid or was revoked. Possible values are: - **Operational**: Valid certificate - **Non-Operational**: Revoked certificate
Signature algorithm \[signature\_algorithm\] Signature algorithm of the certificate. For example: SHA-256, sha256RSA, or SHA1withRSA.
Request Type \[request\_type\] Format used for requesting the certificate.
Request Submission Date \[request\_submission\_date\] Date that the certificate request was submitted.
Request Resolution Date \[request\_resolution\_date\] Date that the certificate request was resolved by the CA.
Request Revocation Date \[request\_revocation\_date\] Date that the certificate was revoked. This field is populated only for revoked certificates.
Effective Revocation Date \[effective\_revocation\_date\] Date that the certificate was effectively revoked by being added to the Certificate Revocation List \(CRL\). This field is populated only for revoked certificates.
Revocation Reason \[revocation\_reason\] Reason for the certificate’s revocation. This field is populated only for revoked certificates.
Requester Name \[requester\_name\] Name of the person who requested the certificate.
Template Enrollment Flags \[template\_enrollment\_flags\] Information about the certificate that needs to be acted on by the CA or the certificate’s owner. For more information, search for the error code in [the official Microsoft documentation site](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-crtd/ec71fd43-61c2-407b-83c9-b52272dec8a1).
## CI relationships The Microsoft CA - Certificate Management pattern doesn’t create any CI relationships. **Parent Topic:**[Available on-premise discovery patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/available-patterns.md)