Cost by Tag
Azure spend grouped by a tag (Environment, Team, CostCenter) — what each slice costs.
What this pane shows
Monthly spend split by the values of an Azure tag key. Untagged resources are called out separately so coverage gaps are obvious. Driven by Azure Cost Management's group-by-tag query.
Key use cases
- Show-back: bill departments or teams for their share of the Azure bill.
- Find the cost of running staging or development environments.
- Quantify how much spend is on untagged resources.
- Compare cost per environment month-over-month.
How often it refreshes
Cached data is served within the window your plan guarantees. Faster refresh is one of the things a higher plan buys.
| Explorer | Builder | Team |
|---|---|---|
| 24 hours | 8 hours | 6 hours |
Linking to LightPane
Once you connect one or more cloud accounts in LightPane you can create
access keys, which are what allow panes to read those
accounts. A key is a text string: the prefix lp_ak_ followed
by 43 characters drawn from A–Z a–z 0–9 - _
(URL-safe base64 of 32 random bytes), so 49 characters in all.
Each cloud account you connect is also given an account
handle — a short name such as zesty-ridge, minted
by LightPane when you link the account and never changed afterwards. It
lets a pane reference the same account for good, without putting a cloud
account ID in your page. Use the handle, not the account's editable
alias: renaming an alias makes a pane match nothing, and that failure is
silent — the pane shows an ordinary empty state, not an error.
More on naming accounts.
When adding the code below into your web page, replace
lp_ak_YOUR_ACCESS_KEY and YOUR_ACCOUNT_HANDLE
with your own access key and account handle.
- No key? Paste this exactly as it is. With the placeholder still in, the pane renders clearly-marked mock data, so you can place and style it before you connect anything. (A key that is present but rejected shows an error instead — a live dashboard must never quietly fall back to sample numbers.)
- No handle? The pane falls back to the access key's default account. That works, but the default moves if the key's grants change — naming a handle is what guarantees the same account every time.