What the CIPP integration does
Each client's users, licenses and managed devices sit next to the rest of their documentation, refreshed automatically.
Setting it up
If you manage clients' Microsoft 365 with CIPP, connect it once instead of approving an app in every client tenant.
- In CIPP, open Integrations › CIPP-API & MCP and create an API client. Give it a role that can read tenants, users and devices; a read-only role is enough. (Self-hosted CIPP older than version 7.1 needs CIPP's extra API setup first.)
- Copy the Application ID, the secret and the tenant ID CIPP shows.
- In DokLocker, open Admin › Integrations › CIPP, enter your CIPP address (for example
https://cipp.yourcompany.com) and those three values, then click Test connection. It tells you how many tenants it found. - Open Sync and matching. Each tenant is matched to the client with the same name; pick the right client for any that didn't match, or ignore tenants you don't want.
- Click Sync now. After that it runs every hour.
For every matched tenant, licensed users become User records with their job title, email, phone and licenses; a Microsoft 365 licenses note shows what's assigned and owned; and Intune-managed devices become Workstation or Asset records with make, model, serial number, operating system, compliance state and last check-in. Guests and old disabled accounts are skipped, and nothing you've written yourself is overwritten.
You don't need the Microsoft 365 (client tenants) integration as well, but both can run side by side.
Included in every plan
Every integration is included at no extra cost, on the hosted service and self-hosted. Connect it under Admin › Integrations, click Test, and the first sync starts straight away.