Microsoft Entra ID identity integration with GenticFlow
Entra ID user, group, application, and OIDC identity context
GenticFlow integrates with Microsoft Entra ID through Microsoft Graph to sync users and groups, with optional application and service principal sync. Entra ID can also be configured as an OIDC authentication provider for client portal and agent chat sign-in flows.
What You Get
Graph Directory Sync
- Users sync with names, user principal names, job titles, departments, and account context
- Groups and memberships sync when group sync is enabled
- Applications can sync when Application.Read.All is granted and enabled
- Service principals can sync as optional identity context
OIDC Sign-In Provider
- Entra ID is supported as an authentication provider type
- Issuer URL uses the Microsoft login tenant endpoint
- Authorization code with PKCE is used for OIDC sessions
- Client portal and agent chat sign-in flows can use the configured provider
Identity Context for Tickets
- User and group records help map tickets to identity context
- Directory data can support password, access, and account-state investigations
- Missing Graph permissions are handled by disabling the related sync area
- Token renewal and Microsoft Graph pagination are handled automatically
How It Works
Create an Entra app registration
Grant the Microsoft Graph permissions required for the identity objects you want to sync.
Connect tenant credentials
Enter tenant ID, client ID, and client secret in GenticFlow.
Select sync options
Enable users, groups, applications, and service principals based on the available permissions.
Use identity data in service desk work
The AI engineer can reference identity context during ticket investigation and escalation.
Identity context for support workflows.
Microsoft Entra ID remains the identity provider or directory source. GenticFlow uses supported identity sync and OIDC sign-in flows to connect users, organizations, and sessions to the service desk workflow.
See It In Action