This enables customers to track and address expiring secrets in advance.

| Field | Description |
|---|---|
| Client Secret ID | Unique identifier of the client secret. |
| Application Name | Name of the application the client secret belongs to. |
| Expires On | Date the client secret will expire. |
| Days to Expire | Number of days remaining until the client secret expires. |
| Status | Expired – Secret expired (up to 30 days ago). Expiring Today – Secret expires today. Expiring Soon – Secret expires within the next 90 days. |
Note: Client secrets expiring today or already expired will show "0" under Days to Expire. The Status field will indicate whether the secret is expiring today or has already expired.By default, Client secret expiry monitoring is disabled for both Microsoft 365 and Microsoft Azure monitors. When enabled, it covers:
To enable Client secret expiry monitoring, customers must:
Important:
Performance Polling should be enabled only after granting the required permission.
Enabling polling before providing the correct permission may cause data collection failures. If this happens, customers may need to wait until the next polling cycle (up to 12 hours or the configured interval) to see the data.
Customers can customize polling frequency and monitoring range under:
Settings → Performance Polling → Optimize Data Collection → Choose Monitor Type (Microsoft Azure/Microsoft 365)
Metric Name: Client Secret Expiry Details.
Options:
Note: Polling intervals below 12 hours may cause performance issues. If a lower interval is set, a warning alert will be displayed on the monitor page.
Customers can also adjust the date ranges for which secrets are monitored:
| Option | Allowed Range | Default |
|---|---|---|
| Number of days to monitor expired secrets | 1 to 30 days | 10 days |
| Number of days to monitor expiring secrets | 0 to 90 days | 30 days |