Unit economics

Overview

Unit economics connects your Azure spend to the business volume it delivers. Instead of asking "how much are we spending?", it answers "how much does the cloud cost us per unit of business?" You can track cost per customer, per transaction, per 1,000 API calls, or any unit your team defines, and see whether that cost is moving in the right direction over time.

Business value

Total cloud spend is a poor signal on its own. A team whose spend grows from $10k to $15k per month may be scaling efficiently if the number of customers grew from 100 to 200. It may also be burning money if nothing changed. Unit economics makes that distinction visible, so engineering and finance teams can hold a shared, honest conversation about cloud efficiency rather than arguing over raw cost numbers.

Prerequisites

Required permissions

Access to Unit economics is controlled by the Unit economics feature permission in Cost Analyzer. Permissions are assigned per role under User management.

A cost management group with imported cost data must exist before unit economics data is meaningful.

How it works

Unit economics is configured per cost management group. Each group can have multiple units defined. For example, one tracking cost per customer and another tracking cost per transaction at the same time.

Each unit has three components:

• Unit name: a free-text label that also defines what the unit represents. Name it "Cost per customer" and the unit is automatically inferred as "customer". The name appears as the axis label and status badge throughout the panel.
• Description: an optional note describing what business output the unit tracks.
• Measured in: the counting noun for the unit, such as customers, transactions, GB, sessions, or API calls. Accepts any free-text value.

Once a unit is created, you enter the volume for each month manually or upload volumes in bulk using the Excel template. Turbo360 divides the group's monthly Azure spend by the volume you entered to produce the cost per unit for that month.

Each unit is evaluated against its own 12-month rolling average, within a tolerance band of plus or minus 5%. The status badge reflects this comparison:

• At average: unit cost is within the normal range. Steady.
• Below average: unit cost is below the 12-month average. The unit is becoming more efficient.
• Above average: unit cost is rising above the 12-month average and needs attention (shown in red).

The status badge always matches the displayed percentage, so the label and the number are always in agreement.

The Unit economics panel offers two views. Chart view plots monthly spend as bars alongside a trend line for unit volume. Where the two lines diverge, the cost per unit is moving; this chart is the fastest way to spot whether spend and volume are growing together or drifting apart. Table view shows a month-by-month breakdown with spend, volume, cost per unit, change vs. the previous month, change vs. the 12-month average, status badge, and an optional note. Select Export to download the table as an Excel file.

The panel also includes a What moved it breakdown, which compares the two most recent months and separates how much of the cost-per-unit change came from spend versus volume. This makes it immediately clear whether a rising unit cost is a spending problem or a volume problem.

Use the time range control to analyze over the last 3, 6, or 12 months, this or last quarter, or this or last year. The 12-month average, status, and trend all recompute for the selected window.

Steps

Open the Unit economics panel from the cost management group's context menu or from the Unit economics card on the group's Overview tab. The steps below cover creating a unit, entering volumes, and managing existing units.

Create a unit

Creating a unit defines the business metric you want to track against your Azure spend.

1. Open the Unit economics panel for the cost management group.
2. Click + Add unit.
3. Enter a Unit name. Name it "Cost per [unit]", for example "Cost per customer", so the unit label is inferred automatically.
4. Enter an optional Description to describe what business output this unit tracks.
5. Enter the Measured in value: the counting noun for the unit, for example customers, transactions, or sessions.
6. Click Create unit.

After creating the unit, add monthly volumes to start seeing cost-per-unit calculations.

Enter monthly volumes

Entering volumes gives Turbo360 the business data it needs to calculate cost per unit for each month.

1. Select the unit from the Unit dropdown.
2. Click Actions > Unit volumes, or click Edit unit and then Edit monthly volumes.
3. Select the year from the Months dropdown to navigate to the relevant period.
4. Enter the volume for each month in the Volume field. Add an optional note in the Note field to record what changed that month.
5. Click Save volumes.

To enter volumes in bulk, click Template to download the Excel template, fill in the monthly volumes, and click Upload Excel to import the data.

Import from a parent group

Importing unit definitions from a parent group lets you reuse existing unit setup across child groups without recreating each unit manually.

1. Open the Unit economics panel for the child cost management group.
2. Click Actions > Import from parent.
3. Select up to five unit definitions to import.
4. Click Import.

Importing copies the unit name, description, and measured-in label. Volume data is not copied. You must enter volumes separately for the child group.

Edit a unit

Editing a unit lets you update its name, description, or measured-in label.

1. Select the unit from the Unit dropdown.
2. Click Actions > Edit unit.
3. Update the fields as needed.
4. Click Save changes.

Delete a unit

Deleting a unit permanently removes it and all its volume data from the cost management group.

1. Select the unit from the Unit dropdown.
2. Click Actions > Delete unit.
3. Confirm the deletion.

Example scenario

A SaaS team wants to prove their infrastructure is scaling efficiently as the product grows. They create a unit called "Cost per customer" in their production cost management group. Each month, they enter the number of active customers served. After three months of data, the Unit economics panel shows that total Azure spend has increased by 18% while the cost per customer has dropped by 12%, confirming that the infrastructure is scaling sub-linearly. When cost per customer spikes in August and the status badge changes to Above average, the What moved it breakdown shows the volume dropped by 33% while spend stayed flat, pinpointing the issue as a demand drop rather than a cost increase.

Limitations

• Volume data must be entered or uploaded manually. There is no automatic integration with CRM or billing systems.
• Importing unit definitions from a parent group copies definitions only, not volume data. Volumes must be entered separately per group.
• Up to five unit definitions can be imported from a parent group at once.
• Cost per unit calculations require at least one month of volume data. Months without a volume entry show spend only, with no cost-per-unit figure.
• The 12-month average and status badge require sufficient volume history to be meaningful. With fewer than three months of data, the average and status may not reflect the unit's true trend.

Troubleshooting

1. Cost per unit is not displayed for some months
   Cause: No volume was entered for those months. Cost per unit requires a volume entry to calculate.
   Fix: Open Actions > Unit volumes and enter the missing monthly volumes, then click Save volumes.

2. The status badge shows Above average but the cost looks expected
   Cause: The 12-month average may be skewed by an unusual period, such as a month with exceptionally low spend or very high volume.
   Fix: Review the monthly breakdown in Table view to identify any outliers, and add a note to those months for context.

3. Upload Excel returns an error
   Cause: The file format does not match the expected template, or the volume values contain non-numeric characters.
   Fix: Download the template again using the Template button, re-enter the volumes using the correct format, and re-upload.

4. Import from parent group is not available
   Cause: The current group has no parent group, or the parent group has no units defined.
   Fix: Verify that a parent cost management group exists and that at least one unit has been created there before attempting to import.

5. Unit economics panel shows no data after adding volumes
   Cause: Cost data may not have been imported for the months where volumes were entered, or the cost group has no spend in those months.
   Fix: Check the cost import status for the group and confirm that spend data exists for the relevant months. Cost per unit cannot be calculated if spend is zero or missing.

FAQs

1. Can I track multiple business metrics at the same time?
   Yes. You can create multiple units within the same cost management group, for example one for cost per customer and another for cost per transaction. Switch between units using the Unit dropdown in the panel.

2. What happens to unit economics data if the cost management group is deleted?
   All unit definitions and volume data are permanently deleted with the group. There is no way to recover them after deletion.

3. Can I share unit definitions across cost management groups?
   You can import unit definitions from a parent group into a child group, which copies the definition but not the volume data. There is no direct sharing mechanism between sibling groups.

Related articles

• Cost management groups
• Managing cost groups
• Cost analysis
• Savings tracker