Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The healthcare agent service is a highly configurable and extensible bot building platform. One of the core capabilities is the ability to integrate authenticated third party services into your scenarios flows. To build such integrations, we provide an authentication layer on top of the regular data connection object. Authentication providers let your data connections make authenticated HTTPS calls to third-party APIs or your own endpoints.
Create a new Authentication Provider
Navigate to Integration - Authentication Providers and select on + New to create a new authentication provider.

Select OAuth 2.0: Server-to-server authentication to authenticate calls from your data connections to protected APIs.
OAuth 2.0: Server-to-server authentication
To set up server-to-server authentication, you need to provide six variables:
- Name: Add an internal name for the connection
- Description: Add an internal description for recognizing this connection
- Client ID: Add the client ID issued by the OAuth provider when you registered your application.
- Client Secret: Add the client secret issued by the OAuth provider when you registered your application.
- Access Token URL: The OAuth provider’s token endpoint, used to obtain an access token for server-to-server API calls.
- Scope: The scope is used to restrict the level of access to the application. By default you can use openid
If you're using Azure Entra as your authentication provider, you will need to create a service principal to get your Client ID and Client Secret for the Access Token Url, this should be: login.microsoftonline.com/{tenant id}/oauth2/v2.0/token