Native Azure Cost Analysis can roll costs up to a management-group scope, but it can’t unify billing across multiple tenants or automatically allocate shared costs by business unit. At scale, teams export to Power BI or adopt an Azure-specialist platform like Turbo360 that ingests every subscription into a single, allocation-ready view.
As Azure adoption grows, most organizations don’t stay on one subscription for long. Billing boundaries, access control, per-subscription resource limits, and team autonomy all push you toward more subscriptions, and often more tenants. The moment that happens, the native cost view that served you perfectly well starts asking you to switch scopes just to see the whole picture.
This guide is about that specific problem: analyzing Azure spend when it’s spread across many subscriptions. If you need the fundamentals first, meaning what Cost Analysis is and how to build and save a view, start with the complete Azure Cost Analysis guide and come back here for the multi-subscription layer.
Can you analyze costs across subscriptions natively?
Partly. Native Azure Cost Analysis can aggregate costs across multiple subscriptions within the same tenant by setting the scope to a management group. What it cannot do natively is unify billing across separate tenants, or automatically allocate shared and untagged costs to business units. Those two gaps are where native cross-subscription analysis stops.
Azure gives you three resource-management scopes, and understanding them explains exactly how far native rollups reach:
- Management groups are hierarchical containers that organize subscriptions. A management-group tree can go up to six levels deep (the root and subscription levels don’t count toward that limit). Set your Cost Analysis scope to a management group and you’ll see aggregated cost for every subscription beneath it, as long as they’re in the same tenant and you have access.
- Subscriptions are the primary billing and access boundaries for Azure resources.
- Resource groups are logical collections of related resources with a shared lifecycle.
Azure’s three resource-management scopes. Management-group scope is as far as native cross-subscription rollups reach.
So the native ceiling is clear: management-group scope is the tool for same-tenant, same-directory rollups. Microsoft’s own reference on working with scopes documents this. Here’s where it stops, plainly:
| Native Cost Analysis can | Native Cost Analysis can’t |
| Aggregate cost across subscriptions in one management group | Unify billing across multiple tenants or directories in one view |
| Group and filter by subscription within scope | Automatically allocate shared or untagged costs to a business unit |
| Apply a budget per subscription | Apply one budget rule spanning subscriptions in different scopes |
| Show a cost picture delayed by 8 to 24 hours | Give near-real-time cross-subscription monitoring |
That last row matters more than it looks. Cost data in the native view typically lags 8 to 24 hours, and there’s no real-time cross-subscription monitoring, which makes time-sensitive decisions across a large estate genuinely hard.
How to export Azure cost data to Excel or Power BI
To analyze cost outside the portal: from the Cost Analysis view, use Export to download a CSV or Excel file on demand or on a schedule, or connect the Cost Management connector in Power BI to pull cost data into a model you refresh and shape yourself. Export is right for a one-off cross-subscription reconciliation; Power BI is right when you need recurring, custom, cross-subscription dashboards.
The manual export path is the most common first response to the multi-subscription problem, and it’s worth knowing when it’s the right tool versus when it’s a treadmill.
- On-demand export. In the Cost Analysis view, select Export, choose CSV or Excel, and you have the raw data to pivot across subscriptions yourself.
- Scheduled export. Instead of Export, choose Schedule to have cost data dropped to a storage account on a recurring basis, which is the feed most teams point a BI tool at.
- Power BI connector. For always-fresh, presentation-ready dashboards, connect Power BI via the Cost Management connector and model the data once. Microsoft’s Cost Management FAQ covers the connection options.
The honest trade-off: exporting to Excel each month works, but it’s manual, error-prone, and stale the moment you build it. Power BI fixes freshness and presentation, but you own the modeling, the refresh, and the maintenance forever. Neither one gives you automated allocation of shared costs, so you’re still stitching the estate together by hand. That’s the point where teams start weighing a purpose-built platform.
Analyzing costs at scale: a FinOps lead’s view
At real scale, meaning dozens of subscriptions, multiple tenants, and cost that must map to teams, the native “switch scope and export” workflow breaks down. A FinOps lead managing 40 subscriptions needs one dashboard that unifies every subscription, allocates shared cost to the right business unit despite inconsistent tags, and flags anomalies the same day.
Picture the realistic scenario: a FinOps lead responsible for 40 subscriptions across a couple of tenants, expected to answer “what did each business unit spend last month?” by the 3rd. With native tooling that’s a week of exporting, VLOOKUPs, and chasing down untagged resources. The structural needs at this scale are consistent:
- One unified view across every subscription and tenant, not scope-switching.
- Allocation that survives messy tags, mapping shared and mistagged spend to owners automatically.
- Cross-subscription budgets and monitors in a single rule, not per-subscription.
- Same-day anomaly detection, not an 8 to 24 hour lag surfaced at month-end.
This is where Turbo360’s Cost Analyzer legitimately earns its place. It’s an Azure-native FinOps platform built specifically for the multi-subscription estate: one view across all subscriptions, allocation that doesn’t depend on perfect tagging, and monitoring that spans subscriptions in a single rule. Here’s how the native view maps against it.
Azure Cost Analysis vs. Turbo360 Cost Analyzer
| Feature | Azure Cost Analysis | Turbo360 Cost Analyzer |
| Multi-subscription visibility | Limited; must switch between subscriptions | Unified view across all subscriptions |
| Data refresh rate | 8 to 24 hour delay | Near real-time (4-hour refresh) |
| Cost allocation | Basic allocation options | Advanced allocation with custom business dimensions |
| Budget monitoring | Single-subscription budgets | Cross-subscription budget monitoring |
| Historical data retention | Limited by Azure retention policies | Extended historical retention |
| Customizable dashboards | Basic customization | Advanced dashboard customization |
| Resource scheduling | Not available natively | Built-in scheduling for cost optimization |
| Anomaly detection | Basic | Advanced, AI-driven |
| Alert capabilities | Basic threshold alerts | Custom alerts, multiple notification channels |
| External integrations | Limited API | Comprehensive API and integrations |
| Custom tagging support | Basic tag support | Advanced tag management and inheritance |
| Reserved instance optimization | Basic RI reporting | Advanced RI utilization and recommendations |
| User access controls | Standard RBAC | Fine-grained controls with custom roles |
| Pricing | Included with Azure | Request pricing |
A few capabilities are worth calling out because they’re exactly what the native view can’t do across subscriptions.
Resource-level utilization insights. Click any resource and see utilization metrics and cost trends from the past 90 days: daily spend patterns to catch anomalies, a meter-level breakdown (compute, storage, data transfer), and the specific operations driving cost. It moves you past surface-level totals to the actual optimization target, across the whole estate in one view.
Cross-subscription monitors. Set a monthly or daily budget and get notified when actual cost exceeds it, and a single monitor rule can span resources across multiple subscriptions, which native per-subscription budgets can’t. You can preview cost trends before setting the monitor.
Cost optimization scheduling. Create optimization schedules that set resource tiers, throughput values, and up or down state by hour of day, which is real cost reduction, not just reporting on it.
If you’re comparing several tools for this rather than one, the Azure cost management tools roundup lays out the landscape, and the broader Azure cost management guide covers the discipline. You can start a free 14-day trial of Cost Analyzer here.
