> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/integrations/advertising/microsoft-advertising/permissions-for-a-microsoft-work-account.md).

# Permissions for a Microsoft work account

When using a Microsoft work account, you need to have the right permissions to set up the Microsoft Advertising integration with Flip.to.

## Configuring the permissions

If you're a Global Administrator, sign into your company's [Microsoft Entra admin center](https://entra.microsoft.com/). Otherwise send these instructions over to your Global Administrator.

{% stepper %}
{% step %}
**Set up your user consent settings**

Go to **Entra ID** → **Enterprise applications** → **Consent and permissions**

Under the **User consent settings**, select the option: **Let Microsoft manage your consent settings.**
{% endstep %}

{% step %}
**Set up your admin consent settings**

Under the **Admin consent settings**, switch **Users can request admin consent to apps they are unable to consent** **to** to **Yes**.

Define the users, groups, and roles that will be allowed to approve these requests.
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}

Once this is configured, head back to [the instructions for integrating Microsoft Advertising with Flip.to.](/docs/integrations/advertising/microsoft-advertising.md)


---

# 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.flip.to/docs/integrations/advertising/microsoft-advertising/permissions-for-a-microsoft-work-account.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.