Identity
Microsoft Entra ID is the identity backbone for the Engage platform. Every sign-in flow — Management Portal staff access, Customer Portal access from your enterprise customers, and outbound OAuth tokens that the Engage Integration layer needs for Microsoft 365 and Dynamics 365 — flows through Entra.
The Engage platform owns the enterprise app registrations and publishes them as multi-tenant apps in its own external Entra tenant. Your tenant grants admin consent to install them; you do not create app registrations on your side for portal authentication.
Pages in this section
| Page | When to read |
|---|---|
| Microsoft Entra Integration | The integration architecture between your Entra tenant and the Engage platform — multi-tenant app model, admin consent flow, tenant lookup, user-to-role mapping |
| App Registration Installation | Step-by-step installation of the Engage-owned app registrations into your Entra tenant via admin-consent links |
Related
- SCIM Provisioning — once Entra is set up, SCIM keeps the directory data flowing into Engage automatically.
- Integration Onboarding — see section 2 for the full architectural treatment of portal authentication and the three identity paths.