Skip to main content
Triggr works with the Microsoft 365 tenants you manage in Inforcer: their baselines, alignment scores, policies, users, groups, roles, Secure Score, assessments, activity log and reports.

​
Set up Inforcer

1

Open the REST API settings

In the Inforcer portal, go to Configure and open REST API.
2

Create a key

Create a key covering every tenant your workflows use, with read access to the areas they use, plus permission to run assessments and reports if they start them. Triggr can only reach what the key covers.
3

Copy the key

Copy the key, and note the region your account is hosted in: ANZ, EU, UK or US.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > Inforcer and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the key and region

Paste the API Key, select your account’s Region and click Save Configuration.
The Inforcer configuration window with an API Key field, a Region dropdown, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
One configuration covers all your clients. Actions on one tenant take its Inforcer ID as tenantId, a number that List Tenants returns as clientTenantId (not the Microsoft tenant ID). For paged results, pass each response’s continuationToken back in the next call.

​
Troubleshooting

Check the key was pasted in full and Region matches your account: a key only works in its own region. If the key was deleted, create a new one and paste it in with Edit on the Base Configuration card.
The key doesn’t cover that area or tenant. Create a new key with the right tenants and permissions.
Use List Report Runs to check the run is completed or completedWithErrors first. The key must cover every tenant in the run.