Connect your Azure account to Cloudmon using a registered Azure AD application. Once connected, Cloudmon auto-discovers your resources and begins collecting metrics in real time.
This guide walks you through connecting your Azure account to Cloudmon for the first time. The setup involves two parts — registering an application in the Azure Portal to generate credentials, then entering those credentials into Cloudmon. Once complete, Cloudmon will have read-only access to your Azure environment and will automatically discover your resources.
Before you begin, ensure the following are in place:
| Requirement | Description |
| Azure account access | You must have permissions to register applications in Azure Active Directory and assign roles to service principals |
| Cloudmon account | An active Cloudmon account with Cloud Monitoring enabled |
| Cloudmon Probe | At least one active Cloudmon Probe is configured in your environment |
| Services to monitor | Decide which Azure services you want to monitor — Virtual Machines, Storage Account, Blob Storage, Table Storage, File Share, Queue Storage, and Cost Management |
Cloudmon connects to your Azure account through a registered Azure Active Directory (AAD) application — also called a service principal. This application is granted read-only access to your Azure subscriptions. Cloudmon's probe uses the application's credentials (Tenant ID, Client ID, and Client Secret Key) to call Azure APIs at regular intervals, pulling metrics, resource lists, and configuration data. Nothing is installed inside your Azure environment.
Cloudmon connects to Azure using an Azure AD App Registration (service principal). Follow the Microsoft documentation to register an application and obtain the required credentials: Register an application with the Microsoft identity platform — Microsoft documentation
Once registered, note down the following — you will need these in Step 3:
⚠️ Important: The Client Secret Key is shown only once. Copy and store it securely before leaving the page.
Once your app is registered, grant it read-only access to your Azure subscription. Follow the Microsoft documentation to assign the built-in Reader role to your registered application at the subscription level: Assign Azure roles using the Azure portal — Microsoft documentation
| Field | Description |
| Probe * | Select the Cloudmon Probe from which the Azure account discovery will be initiated |
| Name * | A friendly name for this Azure account — e.g. "Production Azure" |
| Tenant ID * | Unique identifier for your organisation's Azure Active Directory instance — from Step 1 |
| Client ID * | Unique identifier for the registered application in Azure AD — from Step 1 |
| Client Secret Key * | The secret generated for your registered application — from Step 1. Click Resource Discovery after entering this to validate the credentials |
| Services * | Select the Azure services to monitor — Azure Virtual Machine, Cost Management, Azure Storage Account, Azure Blob Storage, Azure Table Storage, Azure File Share, and Azure Queue Storage |
| Notify Discovery | Enable to receive a notification once the initial resource discovery is complete |
| Discovery Interval * | How frequently Cloudmon scans for new or removed resources — default is 6 hours |
| Tags | Optional tags to associate with this Azure account |
After saving, navigate to Cloud → Azure → [Your Account]. If the connection is successful, your Resource Groups, Subscriptions, and selected services will begin populating within a few minutes. If resources do not appear, use the rediscover option from the account settings to trigger a manual scan.
| Issue | Likely Cause | Resolution |
| No resources discovered after saving | Incorrect Tenant ID, Client ID, or Client Secret | Re-enter credentials and click Resource Discovery to validate before saving |
| Authentication error on save | Client Secret Key has expired or was not copied correctly | Generate a new Client Secret in Azure AD and update the account in Cloudmon |
| Some services are not appearing | Service not selected during setup, or Reader role not assigned | Edit the Azure account, enable the missing service, and re-run discovery |
| Resources not updating | The discovery interval has not elapsed yet | Trigger a manual rediscovery from Settings → Monitoring → Probes → Azure |