Skip to main content
Clients you imported while connecting Microsoft 365 are already on Clients. The line above the table lists anything that stops a client being ready.

Add your clients: adding one, fixing what isn't ready, the desktop agent and checking Microsoft access (1:27).

The Clients page with Connection Audit, Import and Add client buttons, a readiness summary line, and a table of clients with Environment, Agent, Microsoft and PSA columns.

Clients. Needs attention filters to clients with a gap.

​
Add clients

With a GDAP connection, click Import > Microsoft Partner Center, tick the customers and click Import. Then click Link all on Clients to link them to GDAP.
Choose Cloud Only for Microsoft 365-only clients. The On-Prem options are for clients with on-premises Active Directory and need the desktop agent; choose synced when AD syncs to Microsoft 365, so Core makes user changes in AD.

​
Fix what’s not ready

Click a client. Readiness shows a button for each gap: Link to GDAP, Add tenant ID, Approve access (per-client app, as the client’s admin) or Map to your PSA. Under Details, fields save as you leave them, and Look up from domain fills in the tenant ID.
The Initech client panel with Readiness showing Microsoft Not linked with a Link to GDAP button and PSA Not mapped with a Map to Halo button, above the Primary domain, Microsoft tenant ID with Look up from domain, and Environment type fields.

​
Keep an eye on Microsoft access

Core checks every GDAP client overnight. Click a client’s Microsoft status to open GDAP health; Check now rechecks it, and Check all and Repair all above the table cover every client.
  • Missing permissions or App not consented: click Repair (admins).
  • Missing roles: add the role in Partner Center. See Recommended roles.
  • Expires in N days: extend the GDAP relationship in Partner Center. Expiring lists these clients.
GDAP health showing App not consented with Repair and Check now buttons, and checks for Microsoft sign-in, Graph permissions, Admin roles, GDAP relationship and Recent failures.
To test a client’s access live, click Check permissions under Microsoft connection, or run Connection Audit for every client.

​
Deploy the desktop agent

Clients with on-premises Active Directory have an Agent section in their panel.
1

Generate credentials

Click Generate agent credentials and copy the Client ID and secret, then click Done — hide secret. The secret shows once; Regenerate replaces it and revokes the old one.
2

Install the agent

Run the install script as administrator on a domain-joined Windows server.
3

Check it's online

Click Refresh. The status should read Online; Never connected means the service hasn’t reached Triggr yet, so check the script’s output.
The Agent section of a client panel showing an Online status, Last seen and Last authenticated times of 1 min ago, a Refresh button, and the Client ID with a Copy button.
For a Cloud + On-Prem (synced) client, then set its OUs on the On-premises AD card.

​
Troubleshooting

Check the domain, or paste the tenant ID from the client’s Microsoft Entra admin center.
On the Microsoft setup’s Sign in step, click Sign in on Connect Partner Center, then click Try again on the import page.
Click Renew, then Redo on Connect Microsoft Graph and Connect Partner Center, signing in as the service account.
The client’s Microsoft tenant ID in Core doesn’t match their account’s tenant.
Next: Share your forms.