Follow these 6 steps to download and connect CloudMonitor to your Azure cost data and generate your own cost insights and recommendations. You only have to do these setup steps once.
Step 1: Install the CloudMonitor Analytics Engine in Azure
The CloudMonitor Analytics Engine is the “smarts” and AI behind your cost insights. It extracts and analyzes your cost data and prepares it for reporting in Power BI. It is free to install from the Microsoft Azure Marketplace and installs into one of your Azure Subscriptions.
Click here to install the CloudMonitor Engine.
Step 2: Configure Azure Synapse
For CloudMonitor to receive cost data and perform maintenance activities, specific role assignments are required. These roles are necessary for ensuring access to the required resources, deploying Synapse artefacts, and conducting maintenance within the appropriate resource groups and storage accounts.
Click here to configure CloudMonitor Synapse
Now, we need to configure specific permissions to monitor your chosen Azure subscription, access and view billing information, and receive cost data.
Click here to configure permissions.
Step 4: Raise a Support Ticket
Create a Support Ticket on our Helpdesk and we’ll configure your deployment and process the cost metadata. Once we have run our health checks on historic costs, we'll supply you with the credentials to connect Power BI to the Engine that you have just installed.
Step 5: Download and Connect Power BI to the CloudMonitor Analytics Engine
The CloudMonitor PowerBI Reporting suite gives you visibility of your costs by Cost Group and cost-saving insights and recommendations. It is free to install from the Microsoft AppSource marketplace.
Click here to download the Power BI App into Power BI and connect your data
Step 6: Configure the Admin App, Cost Groups and Budgets
The next step is to create Cost Groups and choose which users can access which Cost Groups. First, we need to configure the Admin App Service Principal.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article