Monitoring Certificates in Azure
Take full control and proactively monitor your Azure Certificates with Nodinite. Detect ageing certificates, automate discovery, and let your team act before an expired certificate impacts your business, all without direct Azure Portal access.
- ✅ Detect ageing and expired certificates with Warning and Error thresholds
- ✅ Discover and monitor all Azure Certificates automatically
- ✅ Share secure, role-based access through Monitor Views
- ✅ Act with Remote Actions and push alerts through Alarm Plugins
Nodinite keeps you informed and in control of your Certificates, so you act before problems arise.
This page explains how the Nodinite Azure Agent monitors Certificates and presents them in one or more role-based Monitor Views. Nodinite tracks the age of each Certificate against your monitoring thresholds. Use remote commands as Actions to resolve issues swiftly; the Managing Certificate page details the Remote Actions.

Example: Monitored Certificates in a Nodinite Monitor View.
How Certificate Monitoring Works
The Azure Agent reads each Certificate through the Azure REST API, compares the days left before certificate expiry with your thresholds, and reports the state to the Nodinite Monitoring Service. State changes reach your team through Alarm Plugins, and users with access to the Monitor View act on them from the Web Client.
Within thresholds"] AG --> WA["fa:fa-triangle-exclamation Warning
Expires within Warning days"] AG --> ER["fa:fa-xmark Error
Expires within Error days"] AG --> UN["fa:fa-ban Unavailable
Cannot evaluate"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP ER --> RA["fa:fa-bolt Edit thresholds"] style OK fill:#93d16d style WA fill:#FFD525 style ER fill:#c33d34,color:#fff style UN fill:#c33d34,color:#fff style AG fill:#2678BD,color:#fff
Diagram: The Azure Agent evaluates each Certificate into OK (green), Warning (yellow), or Error and Unavailable (red); Warning and Error raise alerts, and you adjust thresholds with a Remote Action.
Monitoring Features
- State Evaluation – Assess certificate health against your expiry thresholds.
If Nodinite cannot check your Certificate state, no one else can use them either.
- Automatic Discovery – The Nodinite Azure Agent uses the Azure REST API to present Certificates automatically.
- Category-based Monitoring – Nodinite groups monitored Resources by Categories.
- Role-based Access – Share access to individual items with Users through Monitor Views.
State Evaluation for Certificates
Nodinite presents each Certificate as a Resource. For example, if you have three Certificates, you see three Resources in Nodinite.
- The Nodinite Resources name matches the deployed Certificate name.
- Monitored Certificates belong to the 'Certificate' Category.
- The Application name uses the pattern:
Configuration name/Resource Group Name.
Many other Azure-related Categories exist. Review the Azure Logging and Monitoring Overview.
Each item (shown as a Resource) receives a state (OK, Warning, Error, Unavailable) based on evaluation. Override the evaluation for any Nodinite Resource with the Expected State option.
Certificates live in many Azure services. Certificates in Azure API Management have their own page, and Key Vault monitoring covers Keys, Secrets, and Certificates stored in Key Vaults.
Certificate
For Certificate Resources, Nodinite evaluates state as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available |
|
Review prerequisites |
| ❌ Error | Error threshold breached | Certificate is about to expire or has expired | Edit |
| ⚠️ Warning | Warning threshold breached | Certificate is about to expire or has expired | Edit |
| ✅ OK | Within user-defined thresholds | Details |
When the state is Unavailable, check the Azure rights of the App Registration and the firewall settings in the Prerequisites.
Alert History for Certificate
Analyze the alert history for your Certificates in Nodinite. During root cause analysis, search for historical state changes for any time span, either for all Certificates or individually, if your Monitor View allows it. Learn more in the Add or manage Monitor View guide and the Resource State History user guide.
| Search | Resource history |
|---|---|
![]() Search for alert history for all resources in the Monitor View |
![]() Alert history for the selected Certificate item |
Frequently Asked Questions
Use the Troubleshooting guide to find answers to common questions and known issues.

