> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-user-manual/login/login_with_active_directory_account.md).
# Login with MS Entra (AD) account
Access with an MS Entra account.
Use this method if your Boomerang user is configured for Microsoft Entra ID (AD) login.
{% stepper %}
{% step %}
### Start Microsoft login
Click **Login with Microsoft**.
{% endstep %}
{% step %}
### Pick an account
Microsoft displays the **Pick an account** form.
{% endstep %}
{% step %}
### Approve sign-in
Select the Microsoft account you registered in Boomerang.
Approve the sign-in request in Microsoft Authenticator.
{% endstep %}
{% step %}
### Stay signed in prompt
The **Stay signed in** choice does not affect Boomerang login.
Click **Yes** or **No**.
{% endstep %}
{% step %}
### Confirm you are logged in
The Dashboard opens.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Entra (AD) users must have a PIN enabled to sign operations and events in the system.
See [Sign](/boomerang-3-user-manual/common_elements/sign.md).
{% endhint %}
{% hint style="info" %}
Subsequent logins may skip the Microsoft prompts. This depends on whether you are still signed in to your Microsoft account.
{% endhint %}
### Logout
For Entra users, logout is called **Logout AD**.
---
# 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://help.boomerang3.com/boomerang-3-user-manual/login/login_with_active_directory_account.md?ask=&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.
