> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GDAP alerts

> Email your team a daily or weekly digest of new, fixed and expiring GDAP problems across your clients.

The digest summarises Core's [GDAP health checks](https://kb.mspprocess.com/core/get-started/add-your-clients.md#keep-an-eye-on-microsoft-access), so it needs a GDAP (Partner Center) connection. Only admins can change it.

<video controls preload="none" playsInline poster="/images/videos/gdap-alerts.jpg" src="https://mintcdn.com/triggr/arzEeC0dwWyO5_rA/images/videos/gdap-alerts.mp4?fit=max&auto=format&n=arzEeC0dwWyO5_rA&q=85&s=17dbe859f00235092f7672faabad3e23" />

GDAP alerts: turn on the digest, read it, and check every client's Microsoft access (1:21).

## 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.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/gdap-alerts/digest-settings.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=3657477774fb367256ade836c53b1d57)

**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 that end within 30 days and don't auto-extend. 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 what's wrong and how to fix it. Admins can click Fix now there, or Repair all fixable for every client Triggr can fix itself; see [Fix Microsoft connection problems](https://kb.mspprocess.com/core/reference/fix-microsoft-connection-problems.md).

![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.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/gdap-alerts/connection-audit.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=df9389c170b70f695a035b429bdecd12)

## Troubleshooting

> [accordion] Last send failed
>
> The message names the address or error. Correct the contact and click Save changes; Core retries hourly for up to 24 hours.

> [accordion] “Not sent: the default Microsoft connection isn't GDAP”
>
> The digest only covers GDAP clients. Check Default Microsoft connection in Settings > General.

> [accordion] The digest has a Microsoft sign-in section
>
> Triggr's own sign-in needs renewing: [sign in again](https://kb.mspprocess.com/core/get-started/connect-microsoft-365.md#connect-with-gdap) as the service account.

> [accordion] A cross on Connection Audit, but GDAP health says Healthy
>
> Connection Audit also tests reads Core's workflows don't use, such as Devices and Risky users. See the [Microsoft and GDAP FAQ](https://kb.mspprocess.com/core/reference/microsoft-faq.md#health-checks-and-repairs).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.