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.
Provisioning creates the Azure resources that connect your agent to channels and host its production dependencies. It's separate from configuring your agent code.
To run an agent through Azure Bot Service:
- Provision an Azure Bot resource and its identity resources.
- Configure the agent connection to match the Azure Bot identity.
- Test the connection locally or deploy the agent code to Azure.
This article covers the first step. The instructions apply regardless of which language you use for the Agents SDK agent.
Provision Azure resources based on authentication type
The Azure AI Bot Service supports multiple authentication types. The details of how to configure each authentication type in your Azure Bot resource and in your agent code are covered in the following articles. Consider the security implications of each authentication type when making your choice.
- Provision agent resources in Azure Bot Service using client secret: Use a client secret for local testing if your tenant allows secrets.
- Provision agent resources in Azure Bot Service using User-Assigned Managed Identity: For better security, use User-Assigned Managed Identity.
- Provision agent resources in Azure Bot Service using federated credentials: If you're creating a Teams agent that requires single sign-on (SSO), select federated credentials.
- Add user authorization using federated identity credential
Provision storage accounts, databases, and other service dependencies separately based on the capabilities your agent uses. For storage provider options, see Use storage in your agent.