Skip to main content
Connecting Microsoft 365 (GDAP)

Which GDAP situation are you in?

Match what you see in Partner Center to the steps you need, from no relationship at all to a relationship that just lacks a security group.

Written By The Lemhi Product Team

Last updated 10 days ago

Use this to find out which steps you need before connecting a client to Lemhi. Open Partner Center > Customers > select the client > Admin relationships, and match what you see.

What you see

What to do

No GDAP relationship with the client

Do steps 1 through 4, starting at Step 1.

A relationship that only carries billing roles (for example Billing Administrator), or other roles without Cloud Application Administrator

Do steps 1 through 4, starting at Step 1. You need a new relationship. Microsoft locks a relationship's roles when it's created, so roles can't be added to the one you have. Keep the billing relationship as it is; the two sit side by side and neither affects the other.

A relationship named MLT_..., or one that shows Expired

Do steps 1 through 4, starting at Step 1. MLT_ relationships came from Microsoft's 2023 automatic transition and carry a consent role Microsoft has since retired.

An active relationship that already has all six roles, but Lemhi can't connect

Skip to Step 3. The roles are there but no security group has been assigned to them. If a security group is already assigned, check the account is an Admin agent (Before you connect a client) and match the message Lemhi shows in Client won't connect.

The six roles are listed in GDAP roles Lemhi needs and why.

Next

Before you connect a client: Admin agent, security group, client contact