Virtual Agent integration with Microsoft Teams, Access Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2026 08:11 AM
Hi All,
I'm working on an integration for MS Teams.
Use Case:
Users can request task, incident, problem, change request assigned to them.
Agent and tools are all working inside the instance, but when I test in our Teams environment I'm getting
"You don't have the required access to complete this request. Try another request."
I feel like I missing part of the integration that would allow a role check to say this user has ITIL so they can see ACL protected tables.
Has anyone faced a similar issue.
Thanks in advance!
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I'd start by looking at the user authentication and account linking, especially since the Virtual Agent works fine in ServiceNow but fails when accessed through Microsoft Teams.
When accessing Virtual Agent through Teams, the user's ServiceNow identity is used to determine access to topics, tools and records.
I'd suggest checking the following:
Open the affected user record in sys_user and confirm the account is active.
Verify that the Microsoft Teams email matches the user's ServiceNow email.
Ask the user to select Link to ServiceNow in the Teams Virtual Agent and complete authentication.
Check whether the user has the roles required to access the topics and tools.
Review the relevant table and record-level ACLs to confirm the user can access the requested data.
Test the same request again using the affected user's Teams account.
You can refer to the ServiceNow Microsoft Teams integration guide for the integration and authentication setup.
I'd start with account linking before changing any ACLs or modifying the Virtual Agent configuration. If it still fails, check the Teams integration logs and the specific error returned by the agent.