> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/clients/mobile-clients/mobile-device-management/microsoft-endpoint-manager.md).

# Microsoft Endpoint Manager

(Formerly known as Microsoft Intune)

An example of a Microsoft Endpoint Manager setup from the real world.  It should not be considered as our recommendation, nor any sort of promise that there is nothing that is different in your environment outside of our control that makes a similar setup work in a different way in your environment. 

Microsoft might change the user interface of the Endpoint Manager admin center, we do not commit to keep this documentation updated in regards to changes from their side. 

There are some differences between iOS and Android and there are also some different strategies below the operating systems. E.g for Android you can have different Enrollment Profiles  

![Different Enrollment Profiles for Android client](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FSfjK86rZLB8HxP1b6fmv%2Fimage.png?alt=media\&token=d3f5ed05-1af9-433f-936d-fa666c531fc7)

**For this example we assume that you already have enrolled the device(s) and that the Novacura Flow app is added in Microsoft Endpoint Manager - Apps**. 

The set-up that the screenshots are copied from is from an Android enrollment with "Personally-owned devices with work profile" 

## Create app configuration policy

Assuming you already have enrolled the device(s) and that the Novacura Flow app is added in Microsoft Endpoint Manager as described above,  create a new app configuration policy for managed devices by chose to add an *App configuration policy* for your managed devices 

![App configuration policy for your managed devices](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2Fn7tra4Bag1CRKQwn4jYf%2Fimage.png?alt=media\&token=c76d07f8-162c-4538-b76e-c2487f3c1f07)

Create a name etc. for your configuration policy

![](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2F4RhyXkDfPHSp3RKEOBDb%2Fimage.png?alt=media\&token=c73f565a-5dad-4ad8-8b32-b3a92dbb432c)

Add and set the applicable configuration keys

![](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FDp2CIoumUrbo7Il04JRv%2Fimage.png?alt=media\&token=162a8769-927b-4c8f-8bf4-4f00d97e3734)

Assign the policy to the groups and/or devices you want the policy applied to. 


---

# 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.novacuraflow.com/clients/mobile-clients/mobile-device-management/microsoft-endpoint-manager.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.