> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/documentation/integrations/integration-guides/microsoft-cloud-integration-bundle.md).

# Microsoft Cloud Integration Bundle

{% hint style="info" %}
Were you a Rewst Classic customer? Microsoft integration is now easier in Rewst. The in-platform setup wizard will walk you through all the needed steps for integration.
{% endhint %}

{% hint style="success" %}
Users of New Rewst who set up the Microsoft Cloud Integration Bundle before November 5th 2026 will notice changes to how Rewst handles the integrations in the bundle. We've moved away from ready-made permission tiers and adopted robust permission lists with selectable checkboxes. To take full advantage of these upgrades to the bundle, including our new Custom Profiles to differentiate permission sets between customers, you'll need to update your bundle setup.&#x20;
{% endhint %}

## What is the Microsoft Cloud Integration Bundle?

Rewst can't work with Microsoft 365 and its related apps until you've given it permission to. Setting up the Microsoft integration is how you give that permission: first for your own company, then for each customer you manage.

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FcKAPsuXALDGwXlROJlyj%2FScreenshot%202026-09-24%20at%209.50.17%E2%80%AFAM.png?alt=media&amp;token=71df3608-4b21-4793-b769-f0bca3f88aed" alt=""><figcaption><p>Find the <strong>Set up</strong> button to start integration for Microsoft at the top of your Integrations page.</p></figcaption></figure>

When setup is finished, Rewst can do Microsoft 365 admin work for you and your customers automatically. For example:

* Create a new user: make the account, assign licenses, add them to groups
* Remove a user: block sign-in, remove licenses, hand the mailbox to someone else
* Reports: list users, licenses, MFA status, and security settings for every customer
* Mail tasks: shared mailboxes, forwarding, distribution lists - these use Exchange Online, which is part of the same setup

{% hint style="info" %}
Though you’ll be working from one integration menu tile to set up all integrations, each integration will appear as its own section with its own actions in the actions list of the workflow builder.
{% endhint %}

## How does the Microsoft integration work?

Rewst gets its access to your customers through Microsoft's partner program:

* Cloud Solution Provider (CSP): Microsoft's program for IT providers who resell and manage Microsoft 365 for customers. Your Partner Center account is where this is managed.
* Granular Delegated Admin Privileges (GDAP): a permission agreement between you and each customer. It sets exactly which admin rights you hold in that customer's Microsoft 365, and for how long. The customer has to approve it.

The chain looks like this:

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FJklGxizLzSgigLAQkZL8%2FScreenshot%202026-09-24%20at%209.43.34%E2%80%AFAM.png?alt=media&amp;token=5f5d791c-020a-44b3-b3ce-11a91928e6d4" alt=""><figcaption></figcaption></figure>

Rewst never stores a separate password for each customer. It works through your company's partner connection, and it can only do what each customer's GDAP permissions allow.

## **What integrations are in the Microsoft Cloud Integration Bundle?**

The Microsoft Cloud Integration Bundle contains integrations for:

1. **Microsoft Graph:** A unified API that provides a single endpoint for accessing and managing data and intelligence across Microsoft 365, Windows, and Enterprise Mobility and Security.<br>
2. **Microsoft Exchange Online:** The cloud-hosted version of the traditional Microsoft Exchange Server, offering similar functionalities but without the need for on-premises server infrastructure.<br>
3. **Microsoft Cloud Solution Provider (CSP)**: This allows for the resale of Microsoft cloud services like Azure, Microsoft 365, and Dynamics 365 to businesses, often with added value services. It's a subscription-based model where MSPs can bill customers.<br>
4. **Microsoft Azure**: A cloud computing platform, Azure offers a range of cloud infrastructure services, including computing, analytics, storage, networking, and AI. Note that Microsoft formerly called a different tool Azure, and renamed that tool Microsoft Entra.<br>

## Set up the Microsoft Cloud Integration Bundle

{% hint style="info" %}
Follow our in-platform wizard to set up the Microsoft Cloud Integration Bundle. Below is a high-level overview of what will happen during all the steps. While the Rewst Agent can help you with questions and setup, much of the credentialing and information entered as part of the setup process must be done by you.
{% endhint %}

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FTnREhVj7cCXZ29pOGMGz%2FScreenshot%202026-09-24%20at%209.54.01%E2%80%AFAM.png?alt=media&amp;token=bdd1c61c-ff31-46a6-b524-cd13ab5eaa48" alt=""><figcaption></figcaption></figure>

#### High-level overview of setup

1\. Connect Rewst to your own company's Microsoft account

* Someone with Global Admin rights in your company's Microsoft 365, who also has access to Partner Center, signs in through Rewst's setup screen. A service account should be used, not a personal account.
* They approve and consent to the Rewst app. This adds Rewst as a trusted app in your company's Microsoft account.

2\. Make sure each customer has an active GDAP relationship

* Each customer needs a GDAP relationship with you, and the customer must accept it.
* Many IT providers already have these in place. If a customer doesn't, you request one in Partner Center (or through Rewst's tools) and the customer approves it.

3\. Choose permissions&#x20;

* When you set up the integration bundle, Rewst automatically selects the minimum suggested level of permissions for both GDAP and your Microsoft Apps and displays them to you via checkboxes and expanders in the setup wizard. Our specific permissions are recommended to allow for the use of all Rewst-compatible endpoints available through Microsoft.
* You may deselect permissions, but realize that this could prevent your ability to access certain Microsoft endpoints. It may also impact your ability to use Microsoft-related Crates in our Marketplace.
* If you deselect permissions and wish to update them at a later time to allow for use of specific endpoints or Crates, there may be an access loop in Microsoft where you do not have permission to adjust permissions. Work on the Microsoft-side of adjustment would be up to you the customer, and not manageable by the Rewst support team.
* Use the Custom Profiles section of the integration configuration wizard to set up different permission sets, which can be assigned to individual organizations. <br>

  <figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FBcxxb7169JyCk8f09NF7%2FScreenshot%202026-11-04%20at%2012.10.17%E2%80%AFPM.png?alt=media&amp;token=bc62792b-ab5e-48ae-a90c-59a12d742657" alt=""><figcaption></figcaption></figure>

4\. Apply those permissions to each customer

* Rewst pushes your chosen permissions to each customer's account.

5\. Match Microsoft customers to Rewst customers

* Rewst pulls your customer list from Microsoft. Each Microsoft customer gets linked to the matching customer in Rewst.
* When an automation runs "for Customer A," Rewst knows which Microsoft account to act on.

6\. Test with something harmless

* Run a read-only task against one customer first, like listing their users.
* Result: you've confirmed the whole chain works before running anything that makes changes.

{% hint style="info" %}
If you aren't a Microsoft partner (CSP)**,** or you only want to manage one Microsoft account— for example, your own company's— , setup is simpler. You connect that one account directly and skip the GDAP steps.
{% endhint %}

#### What you'll need before you start

| Item                                         | Why                                                                 |
| -------------------------------------------- | ------------------------------------------------------------------- |
| A Microsoft Global Admin in your own company | To approve the Rewst app in step 1                                  |
| Access to Partner Center (CSP)               | Customer relationships and GDAP are managed there                   |
| Customers willing to approve GDAP requests   | Only needed for customers who don't already have one                |
| Admin rights in Rewst                        | To run the Microsoft setup inside Rewst                             |
| A decision on permission level               | "Read-only reports" and "full user management" need different tiers |

#### What is GDAP and why is it important to the setup process?

In 2024, Microsoft moved away from regular user-based access, where users logged into Microsoft Entra with an individually permissioned account. Instead, they now operate via delegated admin permissions, where permissions are assigned from the top level down, for more secure access management. This is known as *Granulated Delegated Admin Permissions*, or *GDAP*.

#### GDAP templates in Rewst

Rewst has no single, optimal role set for GDAP within the integration configuration. It defines tiers, with each tier mapping to a list of GDAP roles. You choose the tier based on what your automations need to do, via the in-wizard prompts while setting up the integration.

{% hint style="info" %}
If you were a Rewst Classic customer, the Full Management tier is closest to what was recommended and used in Rewst Classic's Microsoft Cloud Integration Bundle.
{% endhint %}

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Tier</th><th>Purpose</th><th>GDAP roles</th></tr></thead><tbody><tr><td>Monitor</td><td>Read-only</td><td>Directory Readers, Global Reader</td></tr><tr><td>Helpdesk </td><td>User support actions</td><td>Monitor's roles, plus user Administrator and Privileged Authentication Administrator</td></tr><tr><td>Services Admin </td><td>Managing workloads</td><td>Helpdesk's roles, plus Exchange Administrator, Intune Administrator, Teams Administrator, SharePoint Administrator, and Cloud Device Administrator</td></tr><tr><td>Full Management </td><td>Complete automation</td><td>Application Administrator, Authentication Policy Administrator, Cloud App Security Administrator, Cloud Device Administrator, Exchange Administrator, Intune Administrator, User Administrator, Privileged Authentication Administrator, Privileged Role Administrator, Security Administrator, SharePoint Administrator, and Teams Administrator</td></tr><tr><td>Full Control</td><td>Unrestricted</td><td>Global Administrator</td></tr><tr><td>Custom</td><td>You pick the roles</td><td>None preset</td></tr></tbody></table>

## Troubleshoot the Microsoft Cloud integration bundle setup

Frequent errors stem from a customer's GDAP relationship that has expired or was never approved, or if the permission tier is set too low for the task. The automation then fails with a "permission denied" error for that one customer. Fixing that customer's GDAP or tier repairs it.

Your first step for any troubleshooting should be to ask the Rewst Agent to assess your situation and provide advice. For additional assistance, we have a separate guide with all bundle troubleshooting information. View that page [here](https://docs.rewst.help/rewst-documentation/documentation/integrations/integration-guides/microsoft-cloud-integration-bundle/microsoft-cloud-integration-bundle-troubleshooting-guide.md).&#x20;

## Microsoft Graph triggers

<details>

<summary>User Updated</summary>

This trigger starts the workflow when a user's profile changes.

</details>

<details>

<summary>User Deleted</summary>

This trigger starts the workflow when a user is removed.

</details>

<details>

<summary>Group Updated</summary>

This trigger starts the workflow when a group's membership or settings change.

</details>

<details>

<summary>Group Deleted</summary>

This trigger starts the workflow when a group is removed.

</details>

<details>

<summary>Security Alert Created</summary>

This trigger starts the workflow when new security alert is raised.

</details>

<details>

<summary>Security Alert Updated</summary>

This trigger starts the workflow when an amert that's still marked as new is updated.

</details>

<details>

<summary>Team Created</summary>

This trigger starts the workflow when a new team is created.

</details>

<details>

<summary>Team Updated</summary>

This trigger starts the workflow when a team's settings change.

</details>

<details>

<summary>Team Deleted</summary>

This trigger starts the workflow when a team is deleted.

</details>

<details>

<summary>Any Channel Message Changed</summary>

This trigger starts the workflow when a message or reply is created, edited, or deleted in any channel in the tenant.

</details>

<details>

<summary>Any Chat Message Changed</summary>

This trigger starts the workflow when a message is created, edited, or deleted in any chat in the tenant.

</details>

<details>

<summary>Call Record Created</summary>

This trigger starts the workflow when a teams call ends.

</details>

<details>

<summary>Mail Message Created</summary>

This trigger starts the workflow when an email arrives in a user's mailbox.

**Configuration fields**

User ID - the mailbox owner's Entra object ID or their sign-in name (UPN)

</details>

<details>

<summary>Mail Message Updated</summary>

This trigger starts the workflow when an email changes, such as being read or flagged.

**Configuration fields**

User ID - the mailbox owner's Entra object ID or their sign-in name (UPN)

</details>

<details>

<summary>Mail Message Deleted</summary>

This trigger starts the workflow when an email is deleted from the mailbox.

**Configuration fields**

User ID - the mailbox owner's Entra object ID or their sign-in name (UPN)

</details>

<details>

<summary>Channel Message Changed</summary>

This trigger starts the workflow when a message is created, edited, or deleted in one channel.

**Configuration fields**

Team ID - the team's Microsoft 365 group ID

Channel ID - for example, `19: ...@thread.tacv2`

</details>

<details>

<summary>Chat Message Changed</summary>

This trigger starts the workflow when a message is created, edited, or deleted in one chat.

**Configuration fields**

Chat ID - for example,  `19: ... @thread.v2` or `19: ...@unq.gbl.spaces`

</details>


---

# 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.rewst.help/rewst-documentation/documentation/integrations/integration-guides/microsoft-cloud-integration-bundle.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.
