Connect Inforcer
Inforcer is a Microsoft 365 policy management platform. An MSP uses it to hold a baseline of Intune, Defender and Entra policy, align every customer tenant to that baseline, document what is deployed,…
Written By Christopher Scaminaci
Last updated 8 days ago
Inforcer is a Microsoft 365 policy management platform. An MSP uses it to hold a baseline of Intune, Defender and Entra policy, align every customer tenant to that baseline, document what is deployed, and run assessments and reports. StackJack connects an AI assistant to Inforcer's public API.
Connecting Inforcer to StackJack gives your AI assistant a family of inforcer_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through
StackJack. With them, your AI can:
- Find the tenants you manage - every Microsoft 365 tenant the API client can see, with its alignment summary and licenses
- Read what is deployed - a tenant's policies in Inforcer's format, its Microsoft Secure Score and history, and its Entra directory roles
- Measure drift - the baselines you hold, the alignment score of each tenant against each baseline, and the per-policy comparison of one tenant with one baseline
- Look inside a tenant - Entra users (with their groups, roles and devices), groups and group members
- Run assessments and reports (on Pro plans) - run an assessment against a tenant, trigger a report for one or more tenants, and download the finished file
- Review activity - search the Inforcer activity log by user, event type and date
How StackJack authenticates to Inforcer
Inforcer uses an API client: a client ID and a client secret. StackJack exchanges the pair for a short-lived token on its own and never shows the token. You enter the pair and the region your Inforcer account is in.
Creating the API client
- Sign in to the Inforcer portal and open Configure, then REST API.
- Create an API client. On its Permissions tab, grant the areas you want StackJack to use: Tenants, Policies, User and Group Management, Entra Dashboard, Baselines, Align, Tenant Assessment, Reports and Activity. Inforcer has not published which permission each route needs, so grant the read permission of every area you need. Add the run permissions for assessments and reports if you want those tools.
- If the client should reach only some customers, limit it on the Filters tab. A tenant outside the filter is answered as not found.
- Copy the client ID and the client secret when you create the client. Store the secret before you leave the page.
Choosing the region
Choose the region you sign in to Inforcer in: United States, Europe, United Kingdom, or Australia and New Zealand. A client only works in the region it was created in. The wrong region is refused in exactly the same way as a wrong secret, so StackJack has no default and asks you to choose.
Connect it in StackJack
- Open Connectors, then Inforcer.
- Choose the Region, enter the Client ID and the Client secret.
- Click Test connection. StackJack asks Inforcer for a new token and reads the baselines list. Both steps change nothing.
Enter the region, the client ID and the secret again whenever you save the connection, including when you only rename it.
What is worth knowing before you start
Permissions decide what works
The client's permissions are set in Inforcer, and StackJack cannot widen them. A call for an area the client does not hold fails with a clear message that names the permission area, and that failure does not count against the connection. The connection test reads the baselines, so a client without the Baselines permission shows a refused test even though the client works for the areas it does hold.
Tenants and their ids
Inforcer addresses a tenant by its Microsoft Entra tenant id, a GUID. Start with inforcer_list_tenants: every tenant tool takes the msTenantId it returns. A tenant that is outside the client's filter,
or that does not exist, answers not found.
Paging
Lists that page return a continuationToken. Read the first page, then pass the token back unchanged until an answer carries none. Users come 200 to a page, groups 20 and group members 100. The activity
log search takes the token in its request, with a pageSize of 1 to 100 (default 25). Narrow a list with search (users and groups) instead of reading every page.
Policies can be large
inforcer_list_tenant_policies returns every policy of a tenant. A non-empty failedPolicyTypes object in the answer means the list is partial: each entry names a policy type Inforcer could not read and
why, for example a tenant with no Windows 365 license.
Assessments and reports
Running an assessment or triggering a report is a Pro tool. Both read the customer tenant and store a run inside Inforcer. They change nothing in the tenant, delete nothing and contact no one. The
assessment runs while StackJack waits and can take a while. A report is queued: trigger it, then read inforcer_list_report_runs until it finishes, then inforcer_list_report_run_outputs, then
inforcer_get_report_run_output for the file. A report run is listed for 7 days.
Triggering a report again queues a second run, and running an assessment again runs it again, so read the run list before you repeat a call that failed.
Report files
A report is rendered as a PDF, CSV, HTML or JSON file. inforcer_get_report_run_output stores the file and answers a temporary download link that works for 30 minutes, with the file name, type and size.
Open the link before it expires: StackJack keeps no other copy. Files over 50 MB are refused.
Rate limit
Inforcer allows 400 calls a minute for each partner, shared by every API client of the partner. A call that fans out over many tenants costs one call per tenant. StackJack paces one connection below the limit and backs off when Inforcer asks it to slow down.
When Inforcer refuses a call
- The client is refused: the client ID or secret is wrong, the client was removed, or the region is not the one the client was created in. Create a client under Configure, then REST API, and paste the region, the client ID and the secret again.
- The client lacks a permission (403): grant the area on the client's Permissions tab. A report type also needs every target tenant to hold the license that report needs.
- A tenant, user, group, run or output is not found (404): check the id against the list tools. A tenant outside the client's filter answers the same way.
- A value is rejected (400): the answer names the field. A
continuationTokenmust be passed back exactly as Inforcer returned it. - Rate limited (429) or an outage (5xx): wait and try again. An assessment run can answer 500 or 502.
Plans and limits
Reads are available on the Free tier, including the activity log search. Running an assessment, triggering a report and downloading a report file are Pro. Business reaches the same tools as Pro and differs by monthly call quota.
See the generated Inforcer tool reference for the current inventory, plan assignment, input schemas and destructive-action labels.
Inforcer tools
inforcer_ · 22 tools · Free 19 · Pro 3
Tenants
Users and groups
Baselines and alignment
Assessments
Reports
Audit events
Was this helpful?
More in Connector guides
Connect 3CXConnect AbleSignConnect Acronis Cyber Protect CloudConnect Action1Still need help? Ask the team