> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/azure-faq/csp-no-cost-data.md).

# Why Does Archera Show No Cost Data for My CSP Subscriptions?

Two causes account for nearly all of these, and they can both be true at once.

## Onboard by Subscription, Not Billing Account

Under a Cloud Solution Provider, your Microsoft Partner Agreement billing account lives in your *partner's* Microsoft Entra tenant, not yours. Users in your tenant have Azure RBAC access to subscriptions and resource groups, and those are the only scopes you can export cost data from. A billing account onboarding therefore produces **no data at all**.

Archera detects CSP subscriptions during onboarding and recommends subscription scope automatically — take that recommendation.

## Ask Your Partner to Enable Cost Visibility

Your CSP must enable the Cost Management visibility policy for your tenant from their partner tenant. Microsoft [disables it by default](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/get-started-partners) for all subscription users. Until your partner sets it to **Yes**, Azure Cost Management — and therefore Archera — cannot read your costs.

Your partner finds it in their own tenant under **Cost Management + Billing → Customers → \[your organization] → Settings → Policies**. Only a member of their **admin agent** group can change it.

The Integration Health page in Archera shows whether the cost policy is disabled for a subscription.

## Related Resources

* [Supported Account / Subscription Types](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/supported-account-types.md)
* [Why Don't Archera's Azure Costs Match My CSP Invoice?](https://docs.archera.ai/help-center/azure-faq/costs-dont-match-csp-invoice.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/help-center/azure-faq/csp-no-cost-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
