Documentation Index
Fetch the complete documentation index at: https://docs.costoptix.com/llms.txt
Use this file to discover all available pages before exploring further.
Cost Optix reads cost data from the Azure Cost Management API. You will need an Azure Service Principal with Cost Management Reader and Reader roles on the target subscription.
Prerequisites
- Azure CLI installed, or access to the Azure Portal
- Permission to create Service Principals in your Entra ID (Azure Active Directory) tenant
- The Subscription ID you want to monitor
Required Permissions
| Role | Scope | Purpose |
|---|---|---|
| Cost Management Reader | Subscription | Read cost and billing data via the Cost Management API |
| Reader | Subscription | Enumerate resources, resource groups, and resource tags |
Setup: Service Principal (Recommended)
Step 1 — Log in and select your subscription
Step 2 — Create the Service Principal
This command creates the app registration, generates a secret, and assigns the Reader role in one step. The secret (password) is only shown once — save it immediately.| Field | Maps to |
|---|---|
appId | Client ID |
password | Client Secret |
tenant | Tenant ID |
Step 3 — Add Cost Management Reader
Step 4 — Enter credentials in Cost Optix
Navigate to Organization Admin → Accounts → Add Account, select Microsoft Azure, and enter:- Tenant ID — from the
tenantfield above - Client ID — from the
appIdfield above - Client Secret — from the
passwordfield above - Subscription ID — your Azure subscription ID
Setup: Managed Identity
If Cost Optix is running on an Azure resource (VM, Container App, or AKS pod) with a Managed Identity assigned, you can use identity-based authentication without storing any secrets.- Assign the Cost Management Reader and Reader roles to the Managed Identity on the target subscription (same commands as Step 2–3 above, replacing the Service Principal
--assigneewith the Managed Identity’s principal ID). - In Cost Optix, select Managed Identity as the authentication method. No additional credentials are required.
Billing Lag
Azure cost data has a lag of up to 5 days. Today’s spend will not appear immediately. This is an Azure platform constraint, not a Cost Optix limitation.| Data type | Typical availability |
|---|---|
| Daily cost totals | T+1 to T+5 days |
| Resource-level tags | Updated on each sync |
| Usage Details (Tag Explorer) | T+1 to T+5 days |
Tag Explorer
The Azure Tag Explorer uses the Usage Details API to fetch per-resource tag data. This requires the Reader role in addition to Cost Management Reader. Tag keys are loaded on page entry; tag value cost breakdowns are fetched on demand.The Tag Explorer fetches from the Usage Details API in real time. Large subscriptions with many resources may take a few seconds to load a tag key’s cost breakdown.