> 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-information.md).

# What Information Does Archera Require to Connect to My Azure Account?

Archera needs two values to start Azure onboarding.

## Required information

### Tenant ID

The tenant ID identifies your Microsoft Entra tenant.

### Subscription ID

The subscription ID identifies the subscription Archera uses during onboarding.

Archera uses this subscription to create the resource group, storage account, and cost exports needed for setup.

{% hint style="info" %}
Azure cost exports must live in a storage account inside your tenant.
{% endhint %}

## How to find these IDs

If you do not already have these values, get them from the Azure portal.

1. Open Microsoft’s guide for finding Azure tenant and subscription IDs.
2. Copy the `Tenant ID`.
3. Copy the `Subscription ID` for the subscription you plan to use during onboarding.

See [Get subscription and tenant IDs in the Azure portal](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).

## Related resources

* [Prerequisite Checklist](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/prerequisite-checklist.md)
* [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-onboarding/technical-onboarding/required-information.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.
