Manage your connected Azure accounts: add a new account, edit configuration, re-run discovery, enable or disable monitoring, or remove an account entirely.
All account-level actions for Azure monitoring are performed directly from the account's own overview page. Navigate to Cloud → Azure → [Your Azure Account]. The top right of the page shows three buttons: Rediscover, Edit, and Delete. The page itself shows a breakdown of all discovered resources by type, a Cost Management spend tile, a geographical and regional breakdown of resources, and an Advisor Recommendations table aggregating Azure Advisor insights across every resource in the account.
To connect a new Azure account to Cloudmon, refer to How to Set Up Azure Monitoring in Cloudmon for the full setup steps, including registering an Azure AD application, assigning the Reader role, and completing the initial resource discovery.
To update the configuration of a connected Azure account, such as updating credentials, changing which services are discovered, or adjusting resource lifecycle behaviour:
Individual monitoring settings for a specific Azure resource, such as its assigned Alarm Rule, Groups, Depends On relationship, or Tags, can also be changed by selecting the resource from the account's service list and clicking its own edit icon.
If new resources have been added to your Azure account and are not yet appearing in Cloudmon, you can manually trigger a re-discovery scan without waiting for the next scheduled interval:
You can temporarily pause monitoring for an Azure account without deleting it. This is useful during maintenance or testing when you want to stop collecting metrics without losing your configuration.
Note: Disabling monitoring pauses metric collection but retains all existing configuration and historical data. You can re-enable monitoring at any time.
To permanently remove an Azure account from Cloudmon monitoring:
Important: Deleting an Azure account removes all associated monitoring data and alert rules from Cloudmon. This action cannot be undone. Your actual Azure resources are not affected.