Step-by-step walkthroughs for connecting your environment (or each customer's, if you are an MSP) and getting Dex resolving real user issues. Follow them in order. Progress saves as you go.
Get from a fresh Dex login to a connected Microsoft 365 client tenant — convert to multi-tenant, add the tenant, and register Dex in Entra.
Replace Dex’s name, logo, and chat terminology with your own brand — across the admin center, the chat experience, and Microsoft Teams.
Install the tenant-agnostic MSI across your Windows fleet — manually, or at scale with Intune, Group Policy, or your RMM — and enroll each device with the tenant's token.
Install the signed, notarized pkg across your Macs — manually, via MDM (Jamf, Intune, Kandji, Mosyle), or your RMM — deliver the enrollment token, and pre-grant privacy permissions.
Deploy the Dex Device Agent as a domain-joined AD connector — run it under a least-privilege gMSA, delegate only the rights it needs, then enable the Local Active Directory app so Dex can manage users, groups, and OUs in on-prem AD.
