Skip to main content
The digest summarises Core’s GDAP health checks, so it needs a GDAP (Partner Center) connection. Only admins can change it.

​
Turn on the digest

1

Set the contacts and schedule

Go to Settings > Alerts and turn on Email a GDAP health digest. Add Contacts (press Enter after each; they don’t need a Core account) and choose when to send it.
The Alerts page with Email a GDAP health digest turned on, contacts alerts@yourmsp.com and noc@yourmsp.com, How often set to Weekly, Day Mon, Time 08:00, Timezone London, and Send test and Save changes buttons.
2

Save and test

Click Save changes, then Send test to email one now.
Daily sends only when something changed; Weekly always sends, with an all-clear when nothing needs attention. The digest comes from app@triggr-app.com within 15 minutes of the time you set and lists new, fixed and ongoing problems, plus relationships expiring within 30 days. Each contact has their own Unsubscribe link; when the last contact unsubscribes, the digest turns off.

​
Check Microsoft access for every client

On Clients, click Connection Audit, then Run all. Click a cross to see the error.
The Connection Audit page with Clients and Run all buttons, totals of 2 full, 4 partial and 0 none, and a table of six clients with a tick or cross under Users, Directory, Domains, Groups, Roles, Applications, Conditional access, Devices, Risky users, Security alerts and Exchange Online, a Score such as 10/11 and a Re-run button.

​
Troubleshooting

The message names the address or error. Correct the contact and click Save changes; Core retries hourly for up to 24 hours.
The digest only covers GDAP clients. Check Default Microsoft connection in Settings > General.
Triggr’s own sign-in needs renewing: sign in again as the service account.
Connection Audit also tests reads Core’s workflows don’t use, such as Devices and Risky users. See the Microsoft and GDAP FAQ.