> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/settings/users/importing-from-microsoft.md).
# Importing from Microsoft
Importing users from Microsoft can typically be performed directly via the link without extra steps. However, if there are restrictive permissions in Microsoft, you will need to manually enable the permissions.
{% hint style="warning" %}
These steps are not required unless you are blocked from signing in using your corporate Microsoft domain
{% endhint %}
{% hint style="warning" %}
Azure / Microsoft Entra Security Groups are not currently supported for policy assignment and exceptions in dope.console
{% endhint %}
### Add Enterprise Applications
We use a single OIDC application for both endpoint authentication and importing the users.
```
Application ID: 0556f6fa-1833-4b20-ac87-c3721972ead0
```
{% hint style="info" %}
Add this enterprise application in Microsoft Entra ID and grant admin consent for the permissions below.
{% endhint %}
### Add Permissions
All required permissions are listed below, and should be granted admin consent:
---
# 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://inflight.dope.security/dope.console/settings/users/importing-from-microsoft.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.