> 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-onboarding/technical-onboarding/required-permissions.md).

# Required Permissions

The roles below are granted to the **Archera Enterprise Application** — a service principal in your tenant. They are not granted to any individual person, so they are unaffected if an employee changes their password or leaves your company.

Archera holds **no write access to your workloads**. Nothing on this page permits creating, modifying, or deleting a virtual machine, database, network, or any other compute resource. Write access is confined to two things: the single storage account Archera creates to hold your cost exports, and your reservations and savings plans.

Except where noted, every role named below is an Azure built-in role. You can look up the exact actions each one carries in [Microsoft's Azure built-in roles reference](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles).

{% hint style="info" %}
These are the permissions granted to **Archera**. They are separate from what the person running the onboarding needs in your own tenant — see the [Prerequisite Checklist](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/prerequisite-checklist.md) for that.
{% endhint %}

## Always granted

| Role                                                               | Scope                                                      | Why it is needed                                                                                                                                                                                                                                                  |
| ------------------------------------------------------------------ | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Archera Custom Role** (a custom role, defined during onboarding) | Tenant root group                                          | The main read grant. See [What the custom role contains](#what-the-custom-role-contains) below. It carries read actions only.                                                                                                                                     |
| **Reader and Data Access**                                         | The storage account Archera creates                        | Read the cost export files Azure writes to blob storage.                                                                                                                                                                                                          |
| **Storage Blob Data Reader**                                       | The storage account Archera creates                        | A fallback read path, used when Azure Policy in your tenant blocks shared access signatures (SAS).                                                                                                                                                                |
| **User Access Administrator**                                      | The storage account Archera creates — **and nothing else** | Azure Cost Management runs your export under a system-assigned managed identity, and that identity must be granted write access to the blob container before it can deliver files. Azure requires `roleAssignments/write` to make that grant. See the note below. |

{% hint style="warning" %}
**About User Access Administrator**

This role can assign other roles, so it deserves a direct explanation.

It is scoped to the **single storage account Archera creates for your cost exports** — not to your subscription, not to your tenant, and not to any resource that existed before onboarding. Within that boundary it cannot reach your workloads or grant anyone access to them.

It is required because Azure's own cost export feature authenticates with a managed identity, and Azure will not deliver export files until that identity has been granted access to the destination container. Scoping the assignment to one storage account is the narrowest way Azure permits this to be done.
{% endhint %}

## Granted when you onboard a billing account

If you connect at the billing-account level rather than selecting individual subscriptions, Archera also requests one billing role so it can read cost data for the whole account at once. The role depends on your agreement type.

| Your agreement                                                          | Role                                                                                                                           | Scope                |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------- |
| Enterprise Agreement (EA)                                               | **EA Enrollment Reader**                                                                                                       | Your billing account |
| Microsoft Customer Agreement (MCA) or Microsoft Partner Agreement (MPA) | [**Billing account contributor**](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/understand-mca-roles) | Your billing account |

This grant is **best-effort**. Many people who run onboarding do not have authority over billing-account access, so if it isn't available, onboarding still completes and Archera works with you on the right scope for your environment.

## Commitment permissions

What Archera receives here depends on whether you install for visibility only or for full rate optimization.

### Visibility only — read access

| Role                    | Scope                                  | Why it is needed                                         |
| ----------------------- | -------------------------------------- | -------------------------------------------------------- |
| **Reservations Reader** | `/providers/Microsoft.Capacity`        | Read your existing reservations and their transactions.  |
| **Savings plan Reader** | `/providers/Microsoft.BillingBenefits` | Read your existing savings plans and their transactions. |

### Full access — purchase and management

A full install replaces the two reader roles above with the following. Each one supersedes its reader equivalent, so the readers are not granted separately.

| Role                                                              | Scope                                  | Why it is needed                                                                                                                                                   |
| ----------------------------------------------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Reservation Purchaser**                                         | Tenant root group                      | Purchase reservations on your behalf. Granted at tenant root so a reservation can be purchased for any subscription you have connected.                            |
| **Savings plan Purchaser**                                        | Tenant root group                      | Purchase savings plans on your behalf, for the same reason.                                                                                                        |
| **Reservations Contributor**                                      | `/providers/Microsoft.Capacity`        | Manage reservations after purchase — scope changes, exchanges, and returns. Purchasing alone does not cover these. This role cannot delegate roles to anyone else. |
| **Savings plan Contributor**                                      | `/providers/Microsoft.BillingBenefits` | Manage savings plans after purchase, for the same reason. This role cannot delegate roles to anyone else.                                                          |
| **Advisor Recommendations Contributor (Assessments and Reviews)** | `/providers/Microsoft.Advisor`         | Read Azure Advisor's cost recommendations so Archera can incorporate them.                                                                                         |

{% hint style="info" %}
**Holding a purchase role is not the same as purchasing.** These roles make a purchase technically possible. Archera buys nothing until you approve a commitment plan in the product.
{% endhint %}

{% hint style="info" %}
Azure authorizes a commitment purchase on the **built-in role assignment itself**, not on the underlying actions. A custom role granting the same actions is refused by Azure. This is why the purchase roles must be assigned as built-in roles and cannot be folded into Archera's custom role. See [Microsoft's documentation on buying reservations](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/prepare-buy-reservation).
{% endhint %}

## What the custom role contains

Archera defines one custom role in your tenant during onboarding. It grants these actions and no others:

| Action                                                  | Purpose                                                                                     |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| `*/read`                                                | Read resource metadata across the tenant — what exists, where, and of what size. Read only. |
| `Microsoft.CostManagement/*`                            | Configure and read the cost exports Archera depends on.                                     |
| `Microsoft.Consumption/*`                               | Read usage and consumption detail.                                                          |
| `Microsoft.Billing/billingAccounts/read`                | Identify your billing account and agreement type.                                           |
| `Microsoft.Billing/billingPeriods/read`                 | Align cost data to your billing periods.                                                    |
| `Microsoft.Billing/billingProperty/read`                | Read billing properties such as agreement type and currency.                                |
| `Microsoft.Resources/subscriptions/read`                | Enumerate connected subscriptions.                                                          |
| `Microsoft.Resources/subscriptions/resourceGroups/read` | Enumerate resource groups for cost attribution.                                             |
| `Microsoft.Advisor/configurations/read`                 | Read Advisor configuration.                                                                 |
| `Microsoft.Advisor/recommendations/read`                | Read Advisor cost recommendations.                                                          |
| `Microsoft.Management/managementGroups/read`            | Read your management group hierarchy.                                                       |

Every entry is a read action. The custom role contains no write, delete, or role-assignment permissions.

## Resource providers

Onboarding registers two Azure resource providers on the subscription you nominate for management. Azure requires both before cost exports and storage can be used at all:

* `Microsoft.Storage`
* `Microsoft.CostManagementExports`

{% hint style="info" %}
Archera does **not** automatically register `Microsoft.Advisor`, because that registration is an expensive operation. It is already registered on most subscriptions. If a role assignment fails with an error naming `Microsoft.Advisor`, register that provider manually on the affected subscriptions and retry.
{% endhint %}

## What Archera creates in your tenant

All of it lives inside the management subscription you nominate, and you own all of it:

* One **resource group**
* One **storage account**, which holds the cost export files
* One **blob container** inside it, created by Azure when the first export is written
* One **custom role definition**

Cost export files are written to your storage account, in your subscription, in the region you choose. Archera reads them from there.

Archera uses Azure's compressed cost export feature, which follows the [FinOps Cost and Usage Specification (FOCUS)](https://azure.microsoft.com/en-us/blog/announcing-the-new-finops-cost-usage-specification-report-now-in-public-preview-in-azure-cost-management/) standard. For details on how these exports work, see [Microsoft Learn — Tutorial: Create and manage Cost Management exports](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-improved-exports).

## Removing access

Every role above can be revoked and every resource deleted at any time. See [Azure Offboarding](https://docs.archera.ai/help-center/azure-onboarding/offboarding/offboarding.md).

## Related Resources

* [Prerequisite Checklist](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/prerequisite-checklist.md)
* [What Information Does Archera Require to Connect to My Azure Account?](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/required-information.md)
* [How Does Archera Access My Azure Environment?](https://docs.archera.ai/help-center/sign-in-and-security/azure-access.md)
* [Azure Offboarding](https://docs.archera.ai/help-center/azure-onboarding/offboarding/offboarding.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-onboarding/technical-onboarding/required-permissions.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.
