Integrations

Microsoft 365 tenants

Connect each client's Microsoft 365 tenant once, with your own app registration and GDAP or the client's own app, so Enlist can register PCs in Windows Autopilot and make new-hire accounts.

Some of what Enlist does happens in your client's own Microsoft 365 tenant: registering new PCs in Windows Autopilot, and making accounts for new hires. Enlist does that through Microsoft Graph, signed in as an app registration that an admin of the tenant has consented to. You connect each client's tenant once, on the client's page.

Two ways to connect #

Your own app, with GDAP (recommended)
You make one multi-tenant app registration in your tenant and add it to Enlist once. For each client, Enlist gives you an admin consent link. With a GDAP relationship that gives your admins the Cloud Application Administrator or Application Administrator role in the client's tenant, your own admin opens the link and accepts. Without GDAP, send the link to the client's admin. Either way, nobody shares a password.
The client's own app
For a client you have no GDAP with, the client (or you, with their admin account) makes an app registration in their tenant, grants admin consent there, and you paste its Application (client) ID and secret into Enlist. Enlist signs in with it before saving, so a wrong secret is caught at once.

Enlist keeps every secret encrypted and never shows it again. It calls only Microsoft's own sign-in and Graph addresses for the tenant's cloud.

Make your app registration #

  1. Sign in to the Microsoft Entra admin center of your own tenant (portal.azure.com, or portal.azure.us for GCC High and DoD tenants).

  2. Open Identity → Applications → App registrations and choose New registration. Name it Enlist, and set Supported account types to Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant).

  3. Under Redirect URI, pick Web and paste the address Enlist shows in Settings → Microsoft 365 (it ends in /api/m365/consent). Choose Register.

  4. Open API permissions → Add a permission → Microsoft Graph → Application permissions, and add the permissions for the features you use (below). You don't need to grant consent in your own tenant.

  5. Open Certificates & secrets → New client secret. Copy its Value (not the Secret ID) right away: the portal shows it only once.

  6. In Enlist, open Settings → Microsoft 365, pick the cloud, paste the Application (client) ID from the app's Overview and the secret value, add the secret's end date so Enlist can warn you before it stops working, and choose Add app. Approve with your passkey.

Tenants in GCC High or DoD need an app made in the US Government cloud: add it under that cloud in the same screen. GCC (moderate) tenants use the commercial cloud.

Permissions each feature needs #

FeatureMicrosoft Graph application permissions
Windows Autopilot registrationDeviceManagementServiceConfig.ReadWrite.All
New-hire accountsUser.ReadWrite.All, GroupMember.ReadWrite.All, Group.Read.All, Organization.Read.All

The client's page shows, for each feature, whether the tenant's consent covers it, and names any permission that's missing. Add a permission to the app later and grant consent again: the next check picks it up.

Connect a client's tenant #

  1. Open Clients, open the client, and find Microsoft 365 among its settings.

  2. Enter the client's Tenant ID (Microsoft Entra admin center → Overview) and pick its cloud. Choose Connect and approve with your passkey.

  3. Choose Get consent link, then Open Microsoft's consent page signed in as an admin of the client's tenant (with GDAP, your own admin account), and accept. Or copy the link and send it to the client's admin. The link works once, for 30 minutes.

  4. Microsoft brings you back to the client's page, and Enlist signs in to the tenant to check. If it says Microsoft is still applying the consent, choose Check a minute later.

To use the client's own app instead, tick Use the client's own app registration, paste its ID and secret, and choose Connect.

Change or remove #

  • Changing your app to another one (a new Application ID) means every client tenant that used it needs consent again. A new secret for the same app doesn't.
  • Changing a client's tenant ID, cloud or app also needs consent again.
  • Disconnect stops Enlist working in the tenant. It changes nothing in the tenant: to take the app's access away there too, an admin removes it under Enterprise applications.
  • Every connection, change, consent and disconnection is in the activity log.

Last updated 2026-11-17. Something wrong or missing? Email [email protected].