Edit

Share via

Manual Configuration

If you prefer manually configuring the resources on Azure, and do not want to follow the automated process, you can follow the following guide. As described in the Core Concepts article, the main things required are an App Registration and an Azure Bot.

Requirements

  1. An Azure subscription
  2. Permissions to create Entra ID App registrations. (If you don't have permissions in your tenant, ask your admin to create the App Registration and share the Application Id)
  3. Permissions to create Azure Bot Service resources
  4. (Optional) The Azure CLI installed and authenticated to your Azure subscription

Create the Entra App Registration

After a successful App Registration you should have the TenantId, ClientId and ClientSecret values, that you will need later.

Tip

We are using Client Secrets authentication here, but it is possible to use other types of authentication. See the App Authentication setup guide for other methods.

  1. Navigate to the Entra Id App Registrations
  2. Select New App Registration and provide a name. Take note of the assigned Application Id (also known as ClientId) and TenantId
  3. Navigate to Certificates & secrets and create New client secret

Create the Azure Bot Service resource

Tip

You can create the Azure Bot Service resource and the Entra App Registration from this screen, and then you will have to create a new client secret.

  1. Create or select the resource group where you want to create the Azure Bot Resource
  2. In the selected resource group, click Create and search for bot.
  3. Select the option Azure Bot, and click Create
  4. Provide the Bot handle, eg. MyBot, select Data Residency and Pricing tier
    1. Under Microsoft App ID, select Single Tenant
    2. In creation type select Use existing app registration and provide the Application Id obtained in the previous step

Configure the Azure Bot Service resource

Once the Azure Bot Service resource has been created you can configure it. You will need to have set up a public facing endpoint so that messages from your. You can use DevTunnels if you wish to expose your local servers to public.

  1. Under Settings/Configuration provide the Message endpoint URL, typically it will look like: https://myapp.mydomain.com/api/messages
    1. When using DevTunnels for local development, use the devtunnels hosting URL with the relative path /api/messages
    2. When deploying to a compute instance, such as App Services, Container Apps, or in other Cloud, use the public hostname with the relative path /api/messages
  2. In Settings/Channels enable the Microsoft Teams channel.

Save the credentials to use as configuration

echo "TENANT_ID=$tenantId" > "$botName.env"
echo "CLIENT_ID=$appId" >> "$botName.env"
echo "CLIENT_SECRET=$clientSecret" >> "$botName.env"

Resources

  • Last updated on