Manage Azure bots in Developer Portal for Teams

Use Developer Portal for Teams to find existing Azure Bot resources and open their supported configuration settings. You don’t need to recreate or import an Azure bot to use this experience.

Azure-managed bots and Teams-managed bots have separate lists. An Azure-managed bot remains an Azure resource: Azure permissions govern its resource settings, and the Azure portal remains the place to manage its lifecycle and other properties.

What you can do

Task Where to do it
Find Azure bots by subscription, resource group, or search Developer Portal: Tools > Bot management > Azure-managed bots
View supported delivery settings Open the bot and select Configure. The availability of HTTPS endpoint and Socket Mode settings depends on the preview and your access.
Create or delete an Azure bot; manage channels, credentials, or its icon Azure portal, or the linked identity management experience where applicable
Package, test, or publish a Teams app that uses the bot The app’s workflow under Apps in Developer Portal

Prerequisites

  • Access to Developer Portal. The Azure-managed bots preview is available to all organizations in the commercial cloud. It doesn't include GCC Moderate or other sovereign clouds.
  • An existing Azure Bot resource and Azure read permission at the resource, resource group, or subscription scope. Developer Portal lists only enabled subscriptions.
  • To use the bot in Teams, enable the Microsoft Teams channel in Azure.

Delivery settings at a glance

The Configure page provides HTTPS endpoint settings and socket mode settings for bots. HTTPS delivery uses a messaging endpoint; socket mode uses an outbound connection for development. For setup steps, endpoint access requirements, and delivery-specific troubleshooting, see Configure the delivery method for an agent.

Find an Azure bot

  1. Sign in to Developer Portal and select Tools from the left pane.
  2. Select Bot management, and then select Azure-managed bots. The Teams-managed bots tab is the default.
  3. In Subscription, select a subscription or All subscriptions. Search the subscription picker by subscription name or ID. Bot results load after you choose a scope.
  4. If you selected one subscription, optionally choose a Resource group to narrow the results. You can filter by resource group only after selecting a single subscription.
  5. Use Search app to search by bot name, display name, application ID, or resource group within your selected scope. Scroll to view more results or select Load more when available.
  6. Select the bot’s name to open the Configure page. Verify the subscription and resource group, especially when you have multiple bots with the same name.

The app ID identifies the bot’s backing Microsoft Entra application. It isn’t the Teams app package’s app ID. Keep these identifiers separate when configuring your Teams app.

Note

The list reflects Azure resources your signed-in account can read, not a list of applications you own. Seeing a bot doesn’t automatically grant permission to change its settings.

Developer Portal can remember a subscription you previously selected if you still have access to it. Developer Portal doesn't automatically restore the All subscriptions selection.

If you don’t have an Azure bot

Select Create an Azure bot to open the Azure portal and create the resource there. Return to Developer Portal, select its subscription, and search again. New Azure resources and recent changes might take a short time to appear in the list.

Enable the Microsoft Teams channel

Configure channels for Azure-managed bots in the Azure portal, not on the Teams-managed bot Channels page in Developer Portal.

  1. In the Azure portal, open your Azure Bot resource.
  2. Select Channels, and then select Microsoft Teams.
  3. Accept the terms of service, if prompted. Select the appropriate cloud environment on the Messaging tab, and select Apply.
  4. Return to your bot in Developer Portal and reload its details before continuing.

Note

The Microsoft Teams bot channel connects an Azure bot to Teams. It isn’t a team or a conversation channel inside Teams. Enabling it doesn’t install or publish a Teams app.

For the complete Azure procedure, see Connect a bot to Microsoft Teams.

Troubleshoot Azure bot discovery

Use the message in Developer Portal to choose the next step. This section covers finding and opening Azure bots. For delivery-method setup, endpoint access, and troubleshooting save failures, see Configure the delivery method for an agent.

# What you see What to check or do
1. Azure-managed bots isn’t available. Confirm that you're signed in to an organization in the commercial cloud. The preview is available to all commercial-cloud organizations, but not to organizations in GCC Moderate or other sovereign clouds.
2. No enabled subscriptions. Check the signed-in account and tenant. Ask the Azure resource owner to confirm your access and the subscription’s status. Developer Portal excludes disabled, warned, past-due, and deleted subscriptions.
3. No Azure bots or no matching results. Check the subscription, resource group, and search text. Try All subscriptions. Confirm that the resource is an Azure Bot and that your account can read it. Allow time for recent Azure changes to appear.
4. We couldn’t load your subscriptions or bots. Select Retry. If the failure continues, check Azure access and service availability. A loading error doesn't mean that you have no subscriptions or bots.
5. We couldn’t reach Azure. Check your network connection and select Retry.
6. No access to a subscription or bot. Ask the Azure resource owner to confirm that your account has read access. Retrying alone doesn’t grant missing permission.
7. Azure access isn’t available yet. Contact your administrator to confirm that Azure access is enabled for your tenant.
8. Policy blocked or Sign in again. Follow the sign-in action shown, or ask your administrator to review the blocking policy. Retry after the requirement is resolved.
9. Azure is busy. Wait for the retry interval shown, then retry. Avoid repeated rapid requests.
10. This Azure bot no longer exists. Return to Bot management. Check whether the resource was deleted or moved and locate its current subscription and resource group in Azure.

Manage other bot properties

On the Configure page, select the Azure portal link under Update other bot properties in Azure portal. Use Azure to manage the bot’s channels, icon, credentials, and other resource settings. Developer Portal doesn’t create, delete, or migrate the Azure resource.

Test the bot as part of a Teams app

Listing an Azure bot doesn’t create, install, or publish its Teams app. Use Apps to configure the app that references the bot’s application ID, prepare its package, and test it in Teams. Your tenant's policies must allow you to upload or install the app.