Before you connect a client: Admin agent, security group, client contact
Five things to have in place before you request a GDAP relationship, starting with the Admin agent setting, the most common blocker.
Written By The Lemhi Product Team
Last updated 10 days ago
This is for the MSP admin who is about to connect a client to Lemhi. When you finish, you have the account, group, customer record, and client contact that the four steps depend on.
The account you use for Lemhi is an Admin agent
Check this first, because it's the most common blocker. Without it, Microsoft rejects every call Lemhi makes, no matter what roles the relationship has.
In Partner Center, select the gear icon, then Account settings.
Select User management and open the user.
Under Assists your customers as, make sure it's checked and Admin agent is selected.
A security group that holds that account
You need a security group in your own Entra ID that holds that account as a direct member (not only through a nested group). If you don't have one, create it now in the Entra admin center: Groups > New group > Security. A name such as "Lemhi GDAP" works. You assign it in Step 3.
The account can approve Lemhi in your own tenant
The account that completes Partner Connect needs Cloud Application Administrator or Application Administrator in your own Microsoft Entra, and must complete MFA when Microsoft asks. If it doesn't hold the role, someone who does can approve through Copy connect link on Settings > Microsoft Partner Account.
The client as a customer in Partner Center
The client exists as a customer in Partner Center. A reseller (CSP) billing relationship isn't required. GDAP alone is enough.
A Global Administrator contact at the client
You have a contact at the client who is a Global Administrator in their Microsoft 365 tenant. They approve the request in Step 2.
Next
Step 1: Request the GDAP relationship in Partner Center
Related
Was this helpful?
Still need help? Ask the team