Skip to main content
Connect a client

Connect your own tenant (the Internal client)

Your own tenant connects as the Internal client. Data Governance there needs an Entra role; Copilot agents need System Administrator and a Dataverse license.

Written By The Lemhi Product Team

Last updated 10 days ago

This is for the MSP admin who wants Lemhi to work in the MSP's own Microsoft 365 tenant, shown in Lemhi as the Internal client. Inventory and employees work there with no extra setup. Two things need setup on the account that completed Partner Connect: Data Governance needs an Entra role in your own tenant (see Your own tenant needs an Entra role), and creating Copilot agents needs the setup below.

Why your own tenant is different

In a client tenant, Lemhi's Copilot Studio calls run over GDAP, and Dataverse treats your delegated admin as a System Administrator, so your account's own licenses don't matter.

In your own tenant there is no GDAP relationship. The account that completed Partner Connect acts as itself, and Dataverse requires both of these on that account:

  • The System Administrator security role in the Copilot Studio environment. Assign it in the Power Platform admin center, under the environment's Users.

  • A license that includes Dataverse: a Copilot Studio User License ($0 per user, but your tenant needs a Copilot Studio subscription or credit pack first), Microsoft 365 Copilot with the Copilot Studio and Dataverse service plans turned on, or any Power Apps or Dynamics 365 license.

An admin without a license lands in Dataverse's Administrative access mode: admin tasks work, but creating an agent fails with a 403 about an "unlicensed user with filtered privileges". A new license can take a while to reach the environment; re-adding the user to the environment in the Power Platform admin center forces the sync. In Lemhi, the Internal client's Compass > Agents page shows the cause and a Check again button.

The simplest setup is a service account that holds the role and a license, or completing Partner Connect with an admin who already has both.

Checklist

  • The Partner Connect account has System Administrator in your Copilot Studio environment.

  • That account has a license that includes Dataverse.

  • If the license is new, re-add the user to the environment in the Power Platform admin center.

  • On the Internal client, Compass > Agents shows no license warning after Check again.

Was this helpful?

Still need help? Ask the team