> 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/ea-custom-price-sheet.md).

# Enabling Custom Price Sheet Downloads

## Background

For Azure Enterprise Agreement (EA) customers whose cost export uses the legacy FOCUS format, the `SkuID` field contains Microsoft **part numbers** rather than standard Azure SKU identifiers. This is a known issue with Microsoft's legacy EA cost export pipeline that affects a subset of EA customers.

To address this, Archera has built a custom pricing solution that uses the customer's EA price sheet to translate those part numbers into actual contracted rates. This enables Archera to produce accurate savings recommendations based on what the customer actually pays rather than public list prices.

To download the price sheet, Azure requires the OAuth user who originally authorized the Archera app to have **Billing Account Reader** at the billing account scope. This is a Microsoft platform constraint — the price sheet API only accepts delegated user credentials and cannot be accessed via a service principal or application token.

**Onboarding cannot be completed until this permission is granted.**

***

## Prerequisites

* Access to an **EA Administrator** account on your Azure tenant
* The email address of the user who completed the **Authorize Archera App** step during onboarding — if you are unsure who this was, contact your Archera representative and they can identify the correct account

***

## Steps

**1. Sign in to Azure as an EA Administrator**

The person making the role assignment must be an EA Administrator, not just a subscription owner.

**2. Navigate to the Billing Account**

* Go to **Cost Management + Billing**
* Select the **Billing Account** (not a subscription or management group)

**3. Open Access Control**

* Click **Access control (IAM)** in the left nav
* Click **Add** → **Add role assignment**

**4. Assign the role**

* Role: **Billing Account Reader**
* Assign access to: **User**
* Select the user who completed the Authorize Archera App step during onboarding

**5. Save and notify Archera**

Once saved, notify your Archera representative. No further action is required — Archera will complete the remaining onboarding steps automatically.

***

## Troubleshooting

* **Wrong scope** — the role must be assigned at the billing account level, not a subscription or management group; subscription-level permissions are insufficient for this API
* **Wrong account** — the role must be assigned to the user who completed onboarding, not an application or service principal; this is a Microsoft platform constraint Archera cannot work around
* **Insufficient permissions** — only EA Administrators can manage billing account-level IAM; subscription owners and Billing Contributors cannot make this change
* **Unsure who completed onboarding** — contact your Archera representative and they can identify the correct account


---

# 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/ea-custom-price-sheet.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.
