> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.2/built-in-connectors/azure.md).
# Azure
The Azure connector for Elimity Insights fetches principals, roles and subscriptions from Azure so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.
## 1. Creating a dedicated app registration in Entra ID
As usual we recommend creating a dedicated account for this connector. Follow the steps below to set up a new app registration in Entra ID:
1. In Azure, open the overview of your tenant's app registrations by typing 'app registrations' in the global search bar and clicking the 'App registrations' service.
2. Click the 'New registration' button.
3. Choose a name for this registration (e.g. `elimity-insights`).
4. Leave the default for 'Supported account types' and 'Redirect URI' and click 'Register'.
Note down both the client identifier and the tenant identifier for this new app registration.
## 2. Generating credentials for the new app registration
The Azure connector authenticates as the app registration using a client secret. Click "Certificates & secrets" in the menu on the left and add a new client secret. Immediately note down the value of your new secret.
## 3. Granting read access to management groups
Having created a new app registration in Entra ID, we now need to grant it read access to the relevant management groups:
1. If you want to target your tenant's root management group, then first make sure to temporarily elevate your Global Administrator access (refer to [the official documentation](https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin?tabs=azure-portal%2Centra-audit-logs#step-1-elevate-access-for-a-global-administrator) for detailed instructions); otherwise you can safely skip this step.
2. Open the overview of your tenant's management groups by typing 'management groups' in the global search bar and clicking the 'Management groups' service.
3. Click the management group for which you want to import and then click the 'Access control (IAM)' item in the side navigation menu.
4. Click 'Add' in the top-left corner of the main content panel, and select 'Add role assignment'.
5. Select the 'Reader' role and click 'Next'.
6. Click 'Select members', search for your newly created app registration, select it and click 'Next' again.
7. Click 'Review + assign'.
8. If you elevated your Global Administrator access in step 1: remove it again.
## 4. Creating a source in Elimity Insights
In Elimity Insights you can now create a new Azure source providing the following configuration options:
Configuration option
Description
Tenant identifier
Tenant identifier you noted down in step 1.
Client identifier
Client identifier you noted down in step 1.
Client secret
Client secret you noted down in step 2.
---
# 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.elimity.com/reference-manual/v3.44.2/built-in-connectors/azure.md?ask=&goal=
```
`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.