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

# Inforcer

> Connect Inforcer to Triggr with an Inforcer REST API key.

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

<Steps>
  <Step title="Open the REST API settings">
    In the [Inforcer portal](https://portal.inforcer.com/), go to Configure and open **REST API**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Copy the key">
    Copy the key, and note the region your account is hosted in: ANZ, EU, UK or US.
  </Step>
</Steps>

## Connect it in Triggr

<Steps>
  <Step title="Open the integration">
    Go to **Integrations > Inforcer** and click Configure on the Base Configuration card.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=bb81acb082055015f91beda7b4876f35" alt="The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button." width="2272" height="330" data-path="images/integrations-common/base-configuration.png" />
    </Frame>
  </Step>

  <Step title="Enter the key and region">
    Paste the API Key, select your account's Region and click Save Configuration.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/inforcer/configure.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=c760cb9a072257fb76625d90f6cf7c20" alt="The Inforcer configuration window with an API Key field, a Region dropdown, an Allow insecure TLS switch under Advanced, and a Save Configuration button." width="1344" height="1190" data-path="images/inforcer/configure.png" />
    </Frame>
  </Step>
</Steps>

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

<AccordionGroup>
  <Accordion title="Authentication errors (401)">
    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.
  </Accordion>

  <Accordion title="Permission errors (403)">
    The key doesn't cover that area or tenant. Create a new key with the right tenants and permissions.
  </Accordion>

  <Accordion title="Report outputs not found (404)">
    Use List Report Runs to check the run is `completed` or `completedWithErrors` first. The key must cover every tenant in the run.
  </Accordion>
</AccordionGroup>


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