For CSPs, MSPs and Azure consultancies
Add CloudMonitor to the Azure services you sell. You lead the client work. We supply and maintain the read-only FinOps platform in Microsoft Fabric.
Microsoft Solutions Partner
Certified software · Azure
FinOps Certified
Specialty Solution
ISO 27001 + 9001
Certified · ISO 42001 verified
Partner evidence
These figures come from published partner stories. We show internal and customer savings as separate results.
What partners deliver
Open the live demo from any image. It uses sample data, so your teams can explore it without putting client data at risk.
Executive reporting
Show billed cost, effective cost, trends, savings, and commitments in each client review. The demo uses the same partner-logo option as the live product.
Cost allocation
Group charges by customer, service, or business unit. Access follows the workspace permissions and Azure scope approved for that customer.
Savings workflow
The platform ranks ways to save. Your team and the customer check each finding. The customer then approves and makes any Azure change.
Routes to market
Use it in a managed service, resell the software, or use it in consulting. Give each option its own contract, invoice, support plan, and renewal path.
You already run an Azure service and want to add FinOps to each client review.
Your team runs the service, leads each review, and follows up.
Add reports, advice, and governance to your managed offer.
The customer mainly needs the platform, while you lead the sale and renewal.
Your team owns the client and sales relationship for the agreed deal.
Your client price and our quoted partner price determine the resale margin.
You sell reviews, cost-saving projects, or an ongoing FinOps service.
Your team uses CloudMonitor data to guide the analysis and client decisions.
Charge for advice and delivery. Handle the software purchase separately.
Commercial model
CloudMonitor's public price follows annual Azure Consumption Revenue (ACR). It does not use seat count or a share of savings. We quote partner pricing for your offer and customer base.
Marketplace treatment
An Azure Marketplace purchase can count toward MACC only if the offer has the Azure benefit eligible badge. The customer must also use an eligible Azure subscription.
The CSP sets the price and bills the customer. Microsoft says CSP private offers do not earn Azure commitment credit. Do not promise MACC drawdown for this route.
These routes may earn Azure commitment credit when the offer and customer meet Microsoft's rules. Check each deal before you quote it.
Read Microsoft's channel sales comparison and MACC rules.
Set the service, price, schedule, and client owner.
Show the product and confirm the sales route it supports.
Confirm the scope, key people, and buying rules.
Help the customer approve access and understand the data boundary.
Set up the workspace and read the approved cost exports and APIs.
Approve the Azure billing scope, subscriptions, and export storage.
Lead reviews, explain findings, and track the next steps.
Maintain the platform and show cost, allocation, anomalies, and savings.
Review each finding and approve any Azure change.
Run the service and keep the customer informed.
Ship updates and handle the agreed path for technical issues.
Raise issues through the agreed route and keep control of Azure changes.
Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA)
At a supported billing scope, CloudMonitor can show cost and usage, the prices agreed for that scope, and supported reservation data.
CSP or subscription access
If the CSP owns the billing access, a customer may use subscription data. That view may omit Marketplace purchases, reservation details, and company-wide costs.
Partner results
“Using CloudMonitor gives us actionable data that translates to better organization of cloud resources along with incremental cost savings.”
Chief Operations OfficerArraya Solutions Figures come from published partner case studies. Results vary by scope, starting point, rollout, and working model.
From fit to first customer
Timing depends on the contract, customer access, and support plan. We start with those facts instead of promising a fixed launch date.
Choose who contracts and bills the customer before you set the margin or promise commitment credit.
Check the billing access, subscriptions, and data needed for the service.
Add your logo, rehearse the demo, and record what keeps the CloudMonitor name.
Agree on reviews, support handoffs, decision owners, and renewal before the first client starts.
Program fit
CloudMonitor suits CSPs, MSPs, Azure consultants, and resellers that want a repeatable FinOps offer. Your team must lead the customer work.
Bring to the fit call
Partner FAQ
The channel is for MSPs, Cloud Solution Provider (CSP) partners, Azure consultancies, and resellers that already advise or manage Azure customers. Microsoft partner status is not required. We confirm regional availability, customer fit, and the appropriate commercial route during the partner-fit discussion.
Reseller mode replaces the CloudMonitor workspace logo with the partner's logo. A small Powered by CloudMonitor mark remains. Screen names, menus, documentation, and support links also keep the CloudMonitor name, so this is a branded workspace rather than a completely unbranded product. See what branding changes before presenting it to a customer.
Partner pricing is quote-based and tied to the Azure consumption covered by each customer license, not to seat count. We agree the wholesale price and billing route before the first deal. You set the price of your packaged service, subject to the Marketplace or reseller terms for that transaction.
MACC treatment depends on the sales route and the specific CloudMonitor offer. Microsoft excludes CSP private offers from Azure commitment credit. A resale-enabled private offer or multiparty private offer can count when the purchased offer is Azure benefit eligible and enrolled in MACC. We confirm the transaction route and who bills the customer before quoting. See Microsoft's channel sales overview and MACC enrollment rules.
The partner leads the customer relationship and service cadence. CloudMonitor maintains the platform and handles the technical escalation path agreed in the partner plan. The agreement defines support ownership, response targets, and handoffs before launch. Onboarding time depends on the transaction route, customer access approvals, and the environments in scope.
CloudMonitor limits access with the workspace, Azure scope, and roles approved for that customer. Azure writes each customer's cost exports to the storage account set up during onboarding. CloudMonitor then processes the approved cost data in its service tenancy. Confirm the workspace and partner access for each deployment. See the Information Trust Center for the current data flow and controls.
Tell us about your Azure service, clients, sales plan, and launch goals. We will confirm the right sales and technical route.
