Microsoft Teams Integration – "Security constraints prevent access to requested page"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi Everyone,
We are facing an issue with a self-configured Microsoft Teams app integrated with ServiceNow.
Previously, the integration was working as expected. However, users are now unable to open the ServiceNow portal from within the Microsoft Teams application. Instead, the following error is displayed:
"Security constraints prevent access to requested page."
Our initial analysis indicates the following:
- The Azure AD application is successfully issuing a valid authentication token.
- The ServiceNow portal works correctly when accessed directly through a web browser.
- The issue only occurs when launching the portal from within the Microsoft Teams app.
- Teams notifications continue to work as expected.
We suspect the issue may be related to the authentication flow or token validation between Microsoft Teams and ServiceNow, but we have not yet identified whether the root cause is on the Microsoft Teams side or the ServiceNow side.
Has anyone encountered a similar issue recently, particularly with a self-configured Teams app? Are there any known platform changes, configuration updates, or logs that we should review to help identify the root cause?
Any guidance or suggestions would be greatly appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @AshutoshB
Validate your implemented steps by these links:
KB0722359 Fix page access restriction error caused by security constraints in Service Portal
KB3076476 MS Teams service portal page issue
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10m ago
We have seen the same issue occur since updating to Zurich Patch 10 HF 3.
I did try following the guidance listed in these 2 KB's, but the issue remains for all users, including our admin accounts.
Any other thoughts?