This guide walks through creating an Azure Bot, connecting it to Microsoft Teams, publishing the app to your organization, and approving it for users.
Step 1 — Create the Azure bot
Go to portal.azure.com and open Microsoft Foundry → Bot Services , then click Create an Azure Bot .
Fill in:
Bot handle : A unique name for your bot (for example Hymalaia_test).
Subscription : Your Azure subscription.
Resource group : Choose or create one (for example Dev).
Data residency : Global.
Pricing tier : Standard.
Under Microsoft App ID , set up the application identity.
Click Review + create , then Create .
Step 1b — Get the client secret
After the bot is created:
Open App Registrations → your app → Certificates & secrets .
Click + New client secret , set a description and expiration, then Add .
Copy the Value of the secret immediately — it is shown only once.
Keep the Client Secret and Microsoft App ID safe; your Hymalaia backend needs them for configuration.
In your Azure bot: Settings → Configuration , set:
Messaging endpoint : The URL where your server receives Teams messages (for example https://your-deployment.example.com/api/msteams/messages).
Bot Type : Single Tenant.
Microsoft App ID : Your registered application ID.
App Tenant ID : Your Azure AD tenant ID.
Schema Transformation Version : V1.3.
Click Apply to save.
Enable the Microsoft Teams channel
Under Settings → Channels , confirm Microsoft Teams is connected and shows Healthy . Direct Line and Web Chat are usually enabled by default.
If Microsoft Teams is not listed, open Available Channels and add the Teams channel.
Step 3 — Create the app in Teams Developer Portal
Go to dev.teams.microsoft.com and create a new app. You will land on the app dashboard (for example for an app named Hymalaia ). Use the left menu for Basic information , Branding , App features , and other sections.
Under Configure → Basic information , set for example:
Short name : Hymalaia (max 30 characters).
Short description : Short tagline (max 80 characters).
Long description : Full description of what the bot does.
Version : 1.0.0.
Developer name : Your organization name.
Website : https://www.hymalaia.com (or your site).
Branding
Under Configure → Branding , upload:
Color icon : 192×192 px PNG with the symbol centered on a 96×96 px area.
Outline icon : 32×32 px PNG, white or transparent.
Accent color : Primary UI color.
App features — Bot
Under Configure → App features , choose Bot . Then:
Select Enter a bot ID and paste your Microsoft App ID from Azure.
Enable the capabilities you need (for example Upload and download files ).
Enable scopes: Personal , Team , Group chat .
The Bot ID must match the Microsoft App ID from Azure exactly (for example a GUID like f746895b-e836-4c8e-9b16-ab99b74c5afa).
App package editor — supportsChannelFeatures
Under Configure → App package editor , review the generated manifest.json. Ensure supportsChannelFeatures is present and set to tier1 so advanced channel features work.
supportsChannelFeatures: "tier1" is required for the bot to be eligible for publication in organization channels.
Publish to your organization
Use Publish → App validation and run Microsoft’s validation. Acknowledge the prompts and start validation.
Under Publish → Publish to org , submit the app. Status becomes Submitted (awaiting admin’s approval) .
Step 4 — Approve the app in Teams Admin Center
Open admin.teams.microsoft.com → Teams apps → Manage apps .
Filter by Publishing status = Submitted to see pending apps.
Open your app (for example Hymalaia ). If it shows as Blocked , open the details and set the status to Allowed .
You need Teams administrator rights. After approval, the app appears in your organization’s app catalog.
Step 5 — Verify in Microsoft Teams
In Teams: Apps → Built for your organisation . Your bot should appear and users can install it with Add .
Summary
Create the bot in Azure (portal.azure.com → Bot Services).
Set the messaging endpoint and store the Client Secret and Microsoft App ID .
Create the Teams app on dev.teams.microsoft.com (basic info, branding, bot ID, channel features).
Publish to your org (validation + Publish to org ).
Approve the app in admin.teams.microsoft.com → Manage apps .
Users install from Apps → Built for your organisation .