- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2025 06:17 PM
Is the BotID in the manifest file and the AppID in ServiceNow for Teams the same?
①Register your AppID in system Property > "sn_now_azure.teams_installed_app_id" > Value
②The manifestFile BotID is different from the App ID.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2025 04:09 AM
Hello @NatsukiO
The value seen in your first image (System property in ServiceNow) is the Client ID (or Application ID) of the Azure AD Application Registration created for the overall ServiceNow integration with Teams. This ID is what Azure AD uses to identify your ServiceNow application instance for OAuth, permissions, and other API calls. It identifies the "wrapper" application that hosts the ServiceNow logic, including the bot.
The value seen highlighted as red in your last image is the ID of the bot service itself. This ID is specifically used by Microsoft Teams to route messages and interactions to the correct Azure Bot Service instance that is running the ServiceNow bot logic. In the context of a Teams application, the bot usually has its own registration (often within the application registration but represented by a separate Bot ID).
If my response has helped you, hit the helpful button, and if your concern is solved, do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2025 04:09 AM
Hello @NatsukiO
The value seen in your first image (System property in ServiceNow) is the Client ID (or Application ID) of the Azure AD Application Registration created for the overall ServiceNow integration with Teams. This ID is what Azure AD uses to identify your ServiceNow application instance for OAuth, permissions, and other API calls. It identifies the "wrapper" application that hosts the ServiceNow logic, including the bot.
The value seen highlighted as red in your last image is the ID of the bot service itself. This ID is specifically used by Microsoft Teams to route messages and interactions to the correct Azure Bot Service instance that is running the ServiceNow bot logic. In the context of a Teams application, the bot usually has its own registration (often within the application registration but represented by a separate Bot ID).
If my response has helped you, hit the helpful button, and if your concern is solved, do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2025 05:01 PM
Hello @Viraj Hudlikar
It was very easy to understand, thank you very much.
That is, the first ID was the overall integration identifier and the last ID was the bot-only identifier and the r started.
In fact, I post issues that occur in other cases.
I thought this was the cause, but I didn't think it would have anything to do with it.
I want to solve the problem in the following case. If you know any clues, please let me know.
Other cases of community ↓
https://www.servicenow.com/community/virtual-agent-forum/integrating-virtual-agent-and-microsoft-tea...
