> 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.endpoint/windows-installer/endpoint-authentication.md).

# Endpoint Authentication

When the dope.endpoint has been successfully installed, and endpoint authentication has been enabled (See [Users](/dope.console/settings/users.md)), the following Windows notification will appear.

<figure><img src="/files/K5fVM7jVbHveWkreuizn" alt=""><figcaption><p>Windows System Notification</p></figcaption></figure>

Once you select Sign-In you will be prompted to login via your Microsoft 365 / Google corporate email.

{% hint style="info" %}
Windows supports silent auto-login for Intune-managed devices when that feature is configured. For other deployments, users will complete a one-time interactive OIDC sign-in flow.
{% endhint %}

<figure><img src="/files/AtwdT03KgKbWuiJZm2AP" alt=""><figcaption><p>Microsoft 365 Login Example</p></figcaption></figure>

{% hint style="info" %}
If enabled, Multi-Factor Authentication (MFA) will be required.
{% endhint %}

Once the user has successfully authenticated the following page will be displayed.

<figure><img src="/files/PSbD1TOGdnHKSMRWwMaQ" alt=""><figcaption><p>Successful Authentication Page</p></figcaption></figure>

This page can then be closed and the user can continue browsing. The dope.endpoint will be configured with the dope policy you have assigned them in the dope.console. If you have not assigned them a specific policy, they will automatically be assigned the Base Policy.

To check that the authentication was successful simply click on the <img src="/files/N5J8LERdzZ6fbASU8kAx" alt="" data-size="line"> icon in the menu bar. This will show the following information including the logged-in user.

<figure><img src="/files/sXqxhdYfHoPYaUFTXoRl" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Where endpoint authentication has **not** been enabled (see: [Users](/dope.console/settings/users.md)) the user will not be prompted to authenticate and will get the Base Policy.
{% endhint %}

### Unauthenticated Users

Where a user has not successfully authenticated and they attempt to access the internet they will get the following screen, selecting continue here will bring them to the M365 or Google Login Screen.

<figure><img src="/files/ryVad2jyDl7E0RfpXglH" alt=""><figcaption><p>OIDC Block Page</p></figcaption></figure>


---

# 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.endpoint/windows-installer/endpoint-authentication.md?ask=<question>&goal=<endgoal>
```

`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.