Skip to main content

Azure Integration

Connect your Azure billing to Viio to bring in your cloud spend. Viio reads a Cost Management export that you publish to your own storage account. Viio needs no billing API access and writes nothing back to your tenant.

D
Written by Dmitry Kosar

Capabilities

✅ Cloud cost

Viio brings in every line item of your Azure bill in the FOCUS format, with the service, region, subscription, resource, commitment discount and all four cost columns.

Prerequisites

  • An Enterprise Agreement or Microsoft Customer Agreement. Azure does not offer FOCUS exports for pay-as-you-go (MOSP) subscriptions.

  • Cost Management Contributor, or a billing role that can create exports, at the scope you export. A billing account or billing profile covers every subscription under it.

  • A storage account you can assign roles on, which needs Owner or User Access Administrator on it.

  • A storage account that accepts connections from outside Azure. Viio cannot reach an account that disables public network access, or that allows only selected networks or private endpoints.

  • A Global Administrator or Privileged Role Administrator to approve the Viio application.

Setup

  1. Create a storage account for the export, or pick an existing one, and add a container, for example cost-exports.

  2. Create the FOCUS export:

    1. Open Cost Management, select your billing scope, open Exports and click Create.

    2. Choose the Cost and usage (FOCUS) template.

    3. Set the frequency to Daily export of month-to-date costs.

    4. Pick your storage account and container as the destination, with a directory such as focus.

    5. Set the format to CSV with Gzip compression. Viio cannot read Parquet exports.

    6. Turn Overwrite data off, which is on by default. With it off, each run writes its own folder instead of replacing files Viio may be reading.

    7. Create the export, then click Run now.

    To bring in earlier months, open the export and use Export selected dates, one month at a time, up to 13 months back. Azure refreshes the current month every day. For the first five days of a month it also refreshes the previous month, so late charges and credits appear in the next run.

  3. Find the export path. After the first run finishes, open the container. The export path runs from the container down to the folder named after the export, which holds folders such as 20261001-20261031. For example, a directory focus and an export named viio-focus-cost give focus/viio-focus-cost.

  4. Connect the integration in Viio:

    1. In Viio, open Integrations, choose Azure Cloud Cost and click Connect.

    2. Sign in as an administrator and accept the Microsoft consent prompt. This adds the Viio - Azure Cloud Cost enterprise application to your tenant. It asks only to sign you in and read your profile, and it has no access to your data until step 5.

    3. Enter the three values below, click Continue, add a name, and click Save.

      • Storage account: the storage account name only, with no URL, for example contosocosts.

      • Container: the container the export writes to, for example cost-exports.

      • Export path: the path from step 3, without the container name, for example focus/viio-focus-cost.

  5. Grant Viio read access. In the Azure portal, open the container and go to Access control (IAM), then Add role assignment. Choose Storage Blob Data Reader, select User, group, or service principal, and assign the role to Viio - Azure Cloud Cost. Assign it on the container itself, because the Reader role on the subscription does not cover blob data.

  6. Wait for the first sync:

    1. Azure applies a new role assignment within about 10 minutes, and occasionally takes up to 30. A sync that runs before then fails with access denied. The next scheduled sync picks the data up, so you don't need to retry anything.

    2. The first sync reads every billing period already in the container, so it brings in every month the export covers.

    3. After that, Viio picks up each new run and replaces that month's figures with the latest ones Azure published.

Troubleshooting & FAQ

Symptom

Quick fix

The integration saves but no cost appears.

Azure has usually not finished the first run yet, which can take up to 24 hours after you create the export. Check the export's run history in Cost Management. Then open the container and look for a <export path>/<YYYYMMDD-YYYYMMDD>/<run id>/manifest.json file.

I get an access denied error.

Check that the Viio - Azure Cloud Cost enterprise application holds Storage Blob Data Reader on the container (step 5). Check that the storage account, container and export path in Viio match where the export writes. On the storage account's Networking page, public network access must be enabled from all networks. If you assigned the role in the last 30 minutes, wait for the next sync.

The consent prompt says I need admin approval.

Only a Global Administrator or Privileged Role Administrator can approve an application for the whole tenant. Ask one of them to click Connect in Viio and accept the prompt.

What does Viio see in my tenant?

Viio sees only the blobs in the one container you grant access to. It holds no other role and never writes to your tenant.

Which month does a charge count towards?

A charge counts towards the billing period folder Azure delivered its row in. A charge recorded late still lands in the month it belongs to, not the month it arrived.

Can I connect more than one subscription?

Export at the billing account or billing profile scope. One export there covers every subscription under it and identifies each one separately. Don't connect two exports that cover the same subscription, because Viio would count both copies.

How do I disconnect Viio?

Remove the integration in Viio. Then remove the role assignment from the container, and delete the Viio - Azure Cloud Cost application under Enterprise applications in Microsoft Entra ID.

Technical details

  • Authentication: Viio signs in as its own multi-tenant Microsoft Entra application with a federated client assertion, so no client secret exists on either side. The admin consent prompt creates the application's service principal in your tenant and returns your tenant ID. Viio then requests a token for Azure Storage, and the Storage Blob Data Reader role on the container is the only thing that authorizes it.

  • Discovery: Every export run writes <export_path>/<YYYYMMDD-YYYYMMDD>/<runId>/manifest.json next to its data files, and every run is a full snapshot of its billing period. Viio lists the export path and keeps the newest manifest in each period folder. It fetches a period only when that manifest's runId differs from the one Viio recorded on the last successful sync.

  • Reading: Viio streams the data files the manifest lists and decompresses them as it reads, so memory does not grow with the size of the export. It sends rows in batches that close on a row count or a byte budget, whichever comes first. Viio passes money and quantity columns through as the exact decimal strings Azure exported, and parses only the period columns. A blank cell arrives as no value rather than an empty string. Viio keeps columns outside the FOCUS specification, such as x_SkuMeterCategory, alongside the row.

Additional resources

Did this answer your question?