> 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/supported-account-types.md).

# Supported Account / Subscription Types

Archera offers the flexibility to onboard using either an individual **Subscription** or overall **Billing Account**.

To onboard Archera into your Azure environment, your cost and usage report will need to be available in FOCUS format. Microsoft is a [founding member](https://azure.microsoft.com/en-us/blog/focus-a-new-specification-for-cloud-cost-transparency/) of The FinOps Cost Usage Specification (FOCUS) project, an industry standard cost data specification.

All modern, paid Azure subscriptions support the FOCUS format. Common scenarios that do not support FOCUS include legacy subscriptions (e.g., MOSP) and unpaid subscriptions (e.g., Azure Credit for MSDN subscribers).

## How to Check Your Azure Billing Account Type

1. Login to your Azure account
2. Click on **"Cost Management and Billing"**
   * If you don't have permissions for this page, scroll down to see how to check your Azure subscription type
3. Next click on **"Billing Scopes"**
4. Take a look at the column titled **"Billing Account Type"**
5. Ensure the value there in billing account type is populated with either **"Enterprise Agreement"**, **"Microsoft Partner Agreement"**, or **"Microsoft Customer Agreement"**

## How to Check Your Subscription Type

1. Login to your Azure account
2. Click on **"Subscriptions"**
3. Click on each of your individual subscriptions listed
4. Check the **Plan Name** value — it should show **"Azure Plan"** or **"Azure in CSP"**

If the Plan Name shows **"Microsoft Online Services Program"** (MOSP), that subscription is not supported. You will need to transfer it to a supported plan before onboarding. For more information on transferring subscriptions, see [Microsoft instructions here](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/subscription-transfer).

## Related Resources

* [Azure Onboarding - Prerequisite Checklist](/help-center/azure-onboarding/technical-onboarding/prerequisite-checklist.md)
* [Azure Onboarding - Required Permissions](/help-center/azure-onboarding/technical-onboarding/required-permissions.md)
* [Does Archera for Azure rely on Microsoft Azure Exchanges or Returns policy?](/help-center/azure-onboarding/other-faq/exchanges-returns-policy.md)
* [Does Archera Support Reservations for Azure Storage Disks?](/help-center/azure-onboarding/services-supported/storage-disks.md)
* [Azure Offboarding](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/supported-account-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.