Sidebar Teams ServiceNow Integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2025 03:52 AM
I have established the connection between Side bar Teams and ServiceNow. Token is generating correctly and the over all setup is done. But Now when I am trying to send a message from sidebar ServiceNow, the message is not getting delievered into Teams.
I am getting error in OOB sub flow " send or edit chat" mentioning that "No record found in Look up action item" in "Send Collab Chat" Action.
I figured out that the records are not automatically getting created in Collab Chat Maps table "sys_cs_external_collab_chat_map". And also when the scheduled job "Subscribe Teams App" is executing it is throwing an error "To access this resource, the app must be associated with an Azure subscription".
Requesting you to help me to resolve this error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2025 03:57 AM
not very sure on this as I haven't worked on it.
From the likes of it, it looks like some data issue as the integration is working fine.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2025 04:48 AM
There are some ACL's on that particular record where write access is only maint role but there are some records which got created already when I am doing testing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2025 04:59 AM
then try to see what's stopping the record insertion.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Were you able to address this issue? If so what was the resolution on this. I am seeing the same issue on our instance.