Microsoft Dynamics endpoints and permissions
Last updated: April 19, 2026
This article explains the key Influ2 integration points with Microsoft Dynamics—which endpoints are used, what data flows through them, and what permissions Influ2 needs to operate.
Authentication and authorization
Endpoint:
https://login.microsoftonline.comWhat happens: Influ2 authenticates to Microsoft Dynamics using OAuth. This endpoint handles token requests and refresh.
Data fields used:
client_id — identifies the Influ2 application
client_secret — secret key for authentication
scope — the requested permissions (e.g., user_impersonation)
code — authorization code from the OAuth flow
grant_type — the type of OAuth grant (authorization_code)
redirect_uri — where Microsoft redirects after authentication
Required permissions: Your Azure AD app must have Dynamics scopes configured (e.g., user_impersonation).
When it's called: During initial OAuth connection setup and when tokens need to be refreshed.
User information retrieval
Fetch user details
Endpoint:
api/data/v9.2/systemusersWhat happens: Influ2 retrieves information about a specific Dynamics user (name, role, active status, etc.).
Data retrieved:
UserID — unique identifier
User name and email
Security role
Disabled status
Required permissions: Read access to the systemusers entity in Dynamics.
Identify current user
Endpoint:
api/data/v9.2/WhoAmIWhat happens: Returns the UserID of whoever is currently authenticated.
Data retrieved:
UserID — the authenticated user's ID
Required permissions: API access to the WhoAmI endpoint (usually granted by default).
Company and account search
Endpoint:
api/data/v9.2/accountsWhat happens: Influ2 searches for companies in your Dynamics instance based on filters you define (e.g., industry, location, company size).
Data retrieved:
Account ID — unique identifier
Company name
Website URL
Account classification
Industry and other custom fields
Required permissions: Read access to the accounts entity in Microsoft Dynamics.