> 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/global-administrator-access.md).

# Does Archera Need Global Administrator Access to My Azure Tenant?

No. The Archera enterprise application never holds Global Administrator, and it is never granted a role at tenant or subscription scope beyond the ones listed in [Required Permissions](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/required-permissions.md).

## What Archera's Application Is Granted

Read roles, the two purchaser roles, and contributor roles on reservations and savings plans. It is also granted User Access Administrator on **one storage account** — the one we create to receive your cost exports — and nowhere else.

## What the Person Running Onboarding Needs

Onboarding creates a custom role and assigns roles at the tenant root management group, so the person running it needs elevated rights for the duration:

* **Contributor** on the single subscription that will host the cost exports. The resource group and storage account are created with that person's own credentials, not ours, so this is the permission that most often blocks onboarding.
* **User Access Administrator at the root management group.** Most tenants get this by turning on **Access management for Azure resources** in Microsoft Entra ID, which does require Global Administrator. If your tenant assigns User Access Administrator at the root management group directly, Global Administrator is never needed.
* **Custom role definitions** enabled under **Entra ID → Roles and administrators → Settings**.

Turn the Access management toggle off once onboarding completes. Only the person running onboarding needs these rights — not everyone who will log in to Archera. Rights granted for an earlier integration don't carry over; the prerequisites must be met at the time onboarding runs.

## Related Resources

* [Required Permissions](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/required-permissions.md)
* [How Does Archera Access My Azure Environment?](https://docs.archera.ai/help-center/sign-in-and-security/azure-access.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/global-administrator-access.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.
