Frustrated with confusing mess of confusingly named IDs

Question

Frustrated with confusing mess of confusingly named IDs

Victor Konshin 0

Hi, I am an engineer at a small company trying to build a Teams AI Agent to help my company resolve quality hold issues. I have written a simple bot that will summarize the quality hold issue and generate reminders to keep things moving to resolve the issue. I have written all the code but I just can't get the thing to respond. This issue is the insanely complicated and confusing mess of weirdly named IDs: AppIDs, ClientIDs, BotIDs, just plain 'ID'. Neither I, nor our IT department can untangle this and get the damn bot to just say, "hi" let alone do what we want. Does any one know of a document that explains all of these various IDs, what they do and how this chain flows so I can figure this out? Help!

-Victor

Sina Salam 22,576 Reputation points Volunteer Moderator

2025-07-30T14:48:24.9266667+00:00
Hello Victor Konshin,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you having issues with your AI Bot related to named IDs: AppIDs, ClientIDs, BotIDs, just plain 'ID'.

There is an answer similar to how you can find your App ID from this platform: https://learn.microsoft.com/en-us/answers/questions/2151780/question-regarding-application-%28client%29-id-in-team

The ID could be found in App registrations via Azure Portal.

Navigate your bot’s app.

Copy the Application (client) ID, this is your Bot ID.

This ID must be used in:

The Teams app manifest under botId

The Azure Bot resource under “Microsoft App ID”

Other things you can do is to ensure:

Your Bot Resource is Registered in Azure

Test Locally with Bot Framework Emulator, use your bot’s endpoint (e.g., http://localhost:3978/api/messages) and App ID/Secret. And if it doesn’t respond here, the issue is in your bot code or endpoint.

Validate Teams App Manifest

Check Authentication and Permissions

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
Pavankumar Purilla 10,350 Reputation points Microsoft External Staff Moderator

2025-07-31T03:16:56.5033333+00:00

Hi Victor Konshin,
Did you get any chance to check the response. Thank you!
Pavankumar Purilla 10,350 Reputation points Microsoft External Staff Moderator

2025-08-01T04:50:46.4033333+00:00

Hi Victor Konshin,
Just following up to see if you had a chance to review the above response. Thank you!

1 answer

Your answer

Sina Salam 22,576 Reputation points Volunteer Moderator

2025-07-30T14:48:24.9266667+00:00

Hello Victor Konshin,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you having issues with your AI Bot related to named IDs: AppIDs, ClientIDs, BotIDs, just plain 'ID'.

There is an answer similar to how you can find your App ID from this platform: https://learn.microsoft.com/en-us/answers/questions/2151780/question-regarding-application-%28client%29-id-in-team

The ID could be found in App registrations via Azure Portal.

Navigate your bot’s app.

Copy the Application (client) ID, this is your Bot ID.

This ID must be used in:

The Teams app manifest under botId

The Azure Bot resource under “Microsoft App ID”

Other things you can do is to ensure:

Your Bot Resource is Registered in Azure

Test Locally with Bot Framework Emulator, use your bot’s endpoint (e.g., http://localhost:3978/api/messages) and App ID/Secret. And if it doesn’t respond here, the issue is in your bot code or endpoint.

Validate Teams App Manifest

Check Authentication and Permissions

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
Pavankumar Purilla 10,350 Reputation points Microsoft External Staff Moderator

2025-07-31T03:16:56.5033333+00:00

Hi Victor Konshin,
Did you get any chance to check the response. Thank you!
Pavankumar Purilla 10,350 Reputation points Microsoft External Staff Moderator

2025-08-01T04:50:46.4033333+00:00

Hi Victor Konshin,
Just following up to see if you had a chance to review the above response. Thank you!

Answer 1

Hi Victor Konshin,
Understanding and correctly configuring the various IDs in a Microsoft Teams bot deployment is a common source of confusion especially because of similar terms like App ID, Client ID, Bot ID, and Teams App ID. At the core of this process is the Application (Client) ID, a unique GUID created when your app is registered in Microsoft Entra ID (formerly Azure Active Directory). This ID acts as your bot’s primary identity for Azure Bot Service, Teams, and authentication flows. In fact, for bots registered in Azure Bot Service, the Bot ID is the same as the Application (Client) ID, as confirmed by the Azure Bot Service documentation.

In addition to this, there is the Teams App ID. This is a separate identifier defined in the id field of your Teams app manifest. If you do not explicitly specify it, Teams will automatically generate one when the app is uploaded. The Teams App ID uniquely identifies your Teams app in the Teams catalog but should not be confused with your Application (Client) ID.

When implementing Single Sign-On (SSO) or integrating with Microsoft Graph APIs, you also need to configure the Application ID URI (or Resource URI) in Microsoft Entra ID. For bots, this is typically in the format api://botid-{AppID} or api://{AppID} and must be configured as described in Microsoft’s official authentication for bots documentation.

The typical deployment flow is as follows:

Register your bot application in Microsoft Entra ID to obtain the Application (Client) ID.

Use this same ID when creating your bot resource in Azure Bot Service.

Update your Teams app manifest by referencing this Application (Client) ID in the botId field and, for SSO, in the webApplicationInfo section.

Package and upload the Teams app. This step finalizes the Teams App ID (if not already defined in the manifest).

The key to resolving most bot deployment issues is to keep the Application (Client) ID consistent across Entra ID registration, Azure Bot Service, Teams manifest, and authentication settings. This alignment ensures that all services recognize your bot as a single identity, enabling smooth bot responses and advanced features such as SSO.

For more information:
Microsoft Docs: Bot resource and identifiers explained

Configuring Bot Single Sign-On in Microsoft Teams

Microsoft Teams App Manifest Reference

Share via

Frustrated with confusing mess of confusingly named IDs

1 answer

Your answer