MyZapp can talk in Microsoft Teams through two separate bots: Notifications and Assistant. This page explains how to declare them in Azure. No program is installed on Azure: the Azure Bot service simply relays messages to your instance.
Repeat this procedure for each bot you want to enable. This page is for administrators.
Installing the app in Teams and the messages sent by the bots will come with the next versions of the connector.
What you need
- a Microsoft Entra account allowed to create app registrations;
- an Azure subscription and a resource group;
- an instance reachable from the Internet over HTTPS, with a publicly trusted certificate.
Address to declare for each bot, replacing <instance> with the address of your instance:
| Bot | Address |
|---|---|
| Notifications | https://<instance>/api/teams/notifications/messages |
| Assistant | https://<instance>/api/teams/assistant/messages |
1. Register the application in Entra
- In the Azure portal, open Microsoft Entra ID › App registrations › New registration.
- Enter a name. Your users will not see it in Teams.
- Under Supported account types, choose Accounts in this organizational directory only.
- Leave the redirect URI empty, then click Register.
- Note the Application (client) ID and the Directory (tenant) ID.
2. Create the secret
- In the application, open Certificates & secrets › Client secrets › New client secret.
- Choose a duration and note the expiry date: on that date, the bot will stop writing.
- Copy the Value column straight away, not "Secret ID": it is only shown once.
3. Create the Azure Bot resource
- In the Azure portal, click Create a resource, search for Azure Bot, then Create.
- Enter a bot handle, choose the subscription and resource group, and Global data residency.
- The free F0 pricing tier is enough.
- Under Type of App, choose Single Tenant.
- Under Creation type, choose Use existing app registration, then paste the two IDs from step 1.
- Click Review + create, then Create.
4. Declare the address of the instance
In the Azure Bot resource, open Settings › Configuration, enter the bot address in Messaging endpoint, then click Apply.
5. Enable the Teams channel
Open Settings › Channels › Microsoft Teams, accept the terms, choose Microsoft Teams Commercial, then Apply.
6. Configure MyZapp
- In Secrets, create a secret with the value copied in step 2 and a name of your choice, for example
teams-notifications-secret. - In Configuration, add the following settings, replacing
{Bot}withNotificationsorAssistant:
| Setting | Value |
|---|---|
Teams:Bots:{Bot}:AppId |
Application (client) ID |
Teams:Bots:{Bot}:TenantId |
Directory (tenant) ID |
Teams:Bots:{Bot}:ClientSecretName |
Name of the secret in Secrets, never its value |
Teams:Bots:{Bot}:Enabled |
true |
7. Check
Send an unauthenticated POST request to the bot address:
- 401: the bot is enabled and the instance is reachable. This is the expected result.
- 404: the bot is disabled or a setting is missing.
- Any other response, or no response: check the network, the proxy and the certificate.
Renew the secret
- In Entra, create a new secret without removing the old one.
- In Secrets, replace the value of the secret. Its name does not change.
- Wait about one hour, then delete the old secret in Entra.
How accounts are recognized
On the first exchange, the person's Microsoft 365 address is matched with the address of an active MyZapp account. If no account matches, or several do, no link is created. A disabled account loses its link the following night.