> 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/why-consent-acts-on-my-behalf.md).

# Why Does the Azure Consent Screen Ask to Let Archera Act on My Behalf?

Most of our access runs as the Archera enterprise application, using the roles you grant it. A small number of Microsoft APIs have no application-permission path and accept only a token tied to a signed-in user, so we request delegated permission for those.

## Which Operations Need a Delegated Token

* **Enumerating a billing account and its billing profiles**, when you onboard by billing account rather than by subscription.
* **The Azure Price Sheet API**, which Microsoft exposes to delegated user tokens only.

If you onboard by selecting subscriptions — which is what we recommend for Cloud Solution Provider customers — your cost exports are created and read by the Archera enterprise application using the roles you granted it, not by delegated permission.

Consent does not give us standing access to your user account or to that account's other permissions.

## If Your Policy Prohibits Interactive Admin Consent

We publish a command-line onboarding script you can read before running. It provisions the enterprise application, creates the custom role and storage account, and assigns the roles, all from your own `az` session. It supports direct subscription onboarding — Pay-As-You-Go, Enterprise Agreement, CSP, and MSDN/DevTest — and does not support Microsoft Customer Agreement billing account onboarding.

## Related Resources

* [How Does Archera Access My Azure Environment?](https://docs.archera.ai/help-center/sign-in-and-security/azure-access.md)
* [Onboarding using Azure CLI](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/onboarding-using-azure-cli.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/why-consent-acts-on-my-behalf.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.
