Skip to main content
Triggr runs Exchange Online PowerShell in your clients’ tenants as its own Microsoft app, for shared mailboxes, out-of-office replies, mailbox permissions, distribution groups and your own cmdlets. Microsoft 365 steps use it through GDAP or SAM; steps that run through CIPP use CIPP instead. In each tenant, Triggr’s app (e0ce32ae-7ba3-4f66-b686-d22dd0eb7841) needs Exchange.ManageAsApp on Office 365 Exchange Online and the Exchange Administrator role. See Microsoft’s app-only authentication.

​
Set up Exchange for GDAP clients

For clients linked through Microsoft Graph (GDAP), Triggr does this itself, as long as Triggr’s security group has Privileged Role Administrator in their GDAP relationships.
1

Link the client

Linking a client through Microsoft Graph (GDAP) creates its Exchange configuration from its default verified domain, saved as its microsoftTenantDomain variable. If that didn’t happen, Triggr tries again the first time an Exchange step runs for the client.
2

Run Repair

Open the client from Clients and click Repair on its GDAP Health card, if shown. It grants Exchange.ManageAsApp, assigns Exchange Administrator and adds any missing configuration.
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.

A client's GDAP Health card in Triggr Core.

​
Connect it in Triggr

To add or fix a client’s configuration yourself:
1

Open the client's row

Go to Integrations > Microsoft Exchange and click Configure (or Edit) on the client’s row in the Per-Client Configuration card.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.
2

Enter the client's domain

Leave ClientID as e0ce32ae-7ba3-4f66-b686-d22dd0eb7841, enter a domain of the client’s tenant in MicrosoftTenantDomain without https:// (ideally its .onmicrosoft.com domain), and click Save Configuration.
The Microsoft Exchange configuration window with ClientID already filled in (blurred), an empty MicrosoftTenantDomain field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
Triggr saves the domain as the client’s microsoftTenantDomain variable. For many clients, click Automap, then Approve All; clients without that variable are skipped. Per-client integrations never fall back to the Base Configuration when a workflow runs for a client. To use Exchange in your own tenant, for workflows without a client, enter your own domain on the Base Configuration card and grant Exchange access yourself.

​
Grant Exchange access yourself

Use this in your own tenant, or when Repair can’t. Triggr’s app must already be in the tenant: GDAP consent adds it to a client’s, and Admin Consent on the Microsoft Graph (GDAP) Base Configuration adds it to yours (check under Entra ID > Enterprise apps > All applications, with Application Type set to All applications, by searching for e0ce32ae). Sign in to Microsoft Graph PowerShell as a Privileged Role Administrator or Global Administrator and run this, replacing <tenant-id>:
Or assign the role in the admin centre: Entra ID > Roles & admins > Exchange Administrator > Add assignments, select Triggr’s app and click Add.

​
Run your own cmdlets

Run Cmdlet runs the PowerShell in script in the client’s tenant (or yours, without a client) and returns its output as JSON in body.output. Add -ErrorAction Stop to fail the step on an error, and return only the properties you need:
Microsoft doesn’t allow New-UnifiedGroup, Remove-UnifiedGroup, Add-UnifiedGroupLinks or Remove-UnifiedGroupLinks with this sign-in; use Triggr’s Microsoft 365 group steps.

​
Troubleshooting

The client has no configuration, or no MicrosoftTenantDomain. Configure it, run Automap, or click Repair on its GDAP Health card.
Check MicrosoftTenantDomain is the client’s domain (try its .onmicrosoft.com one) and ClientID is Triggr’s app. Then click Repair, or grant Exchange.ManageAsApp yourself.
Triggr’s app lacks Exchange Administrator in that tenant. Click Repair, or assign it yourself.
Add Privileged Role Administrator to the client’s GDAP relationship for Triggr’s security group and run Repair again, or grant access yourself.
The configuration holds a GUID. Click Edit on the client’s row and enter a domain of its tenant, such as contoso.onmicrosoft.com, or click Repair to correct it.
Triggr couldn’t find Exchange Online there. Check the client has a Microsoft 365 subscription that includes Exchange Online.