- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2024 11:39 PM
Hello, I am currently running the Teams integration with the Self Configured Setup, not with the Enterprise Apps, because I would like to connect my DEV and test instance with another bot.
Now I had created a bot in Teams with the following instructions and added it to my application manifest.
The integration also works so far, so that I can import messages and create Teams chats from ServiceNow and open the ESC directly in Teams. Unfortunately, my bot is not responding to me, I am not receiving any messages from the app. Are there any permissions missing in Azure, Teams?
I don't have the Now Virtual Agent in my Teams tenant.
https://docs.servicenow.com/bundle/utah-servicenow-platform/page/administer/virtual-agent/task/creat...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 05:02 AM
Hi @Rohit Ladda yes following article helped us
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1642138.
The bot has to be in multi tenant, that is missing in the ServiceNow Docs
Description
After Creation of Custom Bot on microsoft teams and integrating in ServiceNow, there is no response while initiating conversations
From instance outbound logs 400 error could see below error response
"error":"unauthorized_client","error_description":"AADSTS700016: Application with identifier '1234567890' was not found in the directory 'Bot Framework'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. Trace ID: 1234567890 Correlation ID: 1234567890 Timestamp: 2024-05-02 06:51:24Z","error_codes":[700016],
Cause
The error message above is the response received from Microsoft when the instance tries to communicate with the bot using the Application (Client) ID but Azure cannot find the bot in the bot framework.
This is because in the Azure portal the application is created in single tenant
When the bot is created in the "Teams Developer Portal" the bot is registered in the bot framework. When you view the bot at dev.botframework.com, Select Bot Name -> Settings -> Scroll down to "Configurations", you will see it is registered as multi tenant
Resolution
Ensure the Bot Tenancy in Azure Portal matches the value in dev.botframework.com
- dev.botframework.com
- Select Bot Name -> Settings -> Scroll down to "Configurations"
- Azure Portal Applications
- Select Bot Name -> Authentication -> Supported account Types
Additional Information
ServiceNow has no specific requirement for the bot to be multi tenant or single tenant
Details as to why the azure application needs to have the same tenancy configuration as the bot framework will need to come from Microsoft as this is outside of ServiceNow control.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 06:28 AM
I found one HTTP Log for URL https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token which is showing 401 response whenever I am sending a message to VA bot in MS Teams. But this log does not have any details in Request / Response, REST message, etc.
