> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/system/data-sources/microsoft-azure.md).

# Microsoft Azure

FinOps for Cloud supports both Azure tenants and individual Azure subscriptions. This topic describes how you can add your Azure data sources to the FinOps for Cloud platform. 

### Prerequisites 

Before connecting Microsoft Azure to FinOps for Cloud, ensure:

* Azure subscriptions are active.
* Required permissions are assigned. See [Configure Azure Access](/system/data-sources/microsoft-azure/configure-azure-access.md) for the Azure roles and permissions required to connect Azure to FinOps for Cloud.
* Azure Cost Management is enabled and accessible for the subscriptions being onboarded.

FinOps for Cloud retrieves Azure cost and usage information through Azure Cost Management. 

If Azure Cost Management data is unavailable or access is restricted, cost and consumption data cannot be imported into the platform.

### Add an Azure tenant

Adding an Azure tenant requires creating an app registration and assigning the Reader role to each Azure subscription.

To add an Azure tenant:

{% stepper %}
{% step %}
**Configure Azure Access**

1. [Create the app registration](/system/data-sources/microsoft-azure/configure-azure-access.md#create-the-app-registration)
2. [Create a client secret](/system/data-sources/microsoft-azure/configure-azure-access.md#create-a-client-secret)
3. [Assign the Reader role](/system/data-sources/microsoft-azure/configure-azure-access.md#assign-the-reader-role)
   {% endstep %}

{% step %}
**Add your tenant to FinOps for Cloud**

1. [Add your Azure tenant to FinOps for Cloud](/system/data-sources/microsoft-azure/add-your-azure-subscriptions-to-finops-for-cloud.md)
2. [\[Optional\] Reimport historical billing data](/system/data-sources/microsoft-azure/import-historical-data.md)
   {% endstep %}
   {% endstepper %}

### Add individual Azure subscriptions

Adding individual Azure subscriptions requires creating an app registration and assigning the Reader role to each Azure subscription.

To add individual Azure subscriptions:

{% stepper %}
{% step %}
**Configure Azure access**

1. [Create the app registration](/system/data-sources/microsoft-azure/configure-azure-access.md#create-the-app-registration)
2. [Create a client secret](/system/data-sources/microsoft-azure/configure-azure-access.md#create-a-client-secret)
3. [Find your Azure subscription IDs](/system/data-sources/microsoft-azure/configure-azure-access.md#find-your-subscription-ids)
4. [Assign the Reader role](/system/data-sources/microsoft-azure/configure-azure-access.md#assign-the-reader-role)
   {% endstep %}

{% step %}
**Add your tenant to FinOps for Cloud**

1. [Add your Azure subscriptions to FinOps for Cloud](/system/data-sources/microsoft-azure/add-your-azure-subscriptions-to-finops-for-cloud.md)
2. [\[Optional\] Reimport historical billing data](/system/data-sources/microsoft-azure/import-historical-data.md)
   {% endstep %}
   {% endstepper %}

{% hint style="warning" %}
Adding the same Azure subscription under a tenant and individually can cause problems when importing billing data.
{% endhint %}


---

# 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.finops.softwareone.com/system/data-sources/microsoft-azure.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.