> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/updates/release-notes/announcing-azure-and-azure-active-directory-direct-integration.md).

# Announcing Azure and Azure Active Directory direct integration

BalkanID customers in Administrator roles can now directly integrate BalkanID with Azure and Azure Active Directory. Customers can now continuously sync application access and group membership without having to maintain and operate a custom integration. As a result, Azure and Azure Active Directory data in BalkanID will now be automatically up to date.

Direct integrations are the most convenient way to integrate applications with BalkanID. Once configured, direct integrations automatically sync data between an application and BalkanID. Administrators can manage, configure, and view the status of direct integrations from the [Application Integrations page](https://app.balkan.id/settings/apps).

You can integrate Azure and Azure Active Directory now, by contacting Customer Support to enable the Azure integration for your tenant. Once enabled, consult the [Azure and Active Directory (AD) Integration Setup](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/microsoft-azure-and-entra-id-integration-setup.md) guide for configuration instructions.

<br>


---

# 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.balkan.id/updates/release-notes/announcing-azure-and-azure-active-directory-direct-integration.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.
