MS Teams Meeting Extension not workingSummaryAfter Setting up Meeting Extensions for Microsoft TeamsApp id: sn_now_teams_ext Documentation for "self-configured": https://www.servicenow.com/docs/bundle/yokohama-employee-service-management/page/product/meeting-extensibility/concept/meeting-extensibility-ms-teams.html When Conference call is started from Major incident workbench and from Teams Meeting opening the Meeting Extension App throws "Error while Authorising the User" or Does not load anything but shows "failed to connect to instance" Console errors with "Blocked a frame with Origin "https://<instance>.service-now.com/" from accessing a cross origin frame" ReleaseWashington, Xanadu, YokohamaInstructionsFor Cross Origin frame error, please check sys_response_header.LIST table: Like Meeting Extension App, many other applications also ship sys_response_header entry for cross origin access requirement. It is important to review this table. See documentation on Http Response Header here. Anything on GLOBAL scope and "all pages" will take precedence. One can always append more domains within the same Content-Security-Policy value. For "Error While authorising user" error: Our documentation today calls out to add oidc metadata url as https://login.microsoftonline.com/<tenant>/v2.0/.well-known/openid-configuration but we have seen couple of times that this metadata url is different. The clue to look for is in system logs, it will log (system logs -> All) a message like below, meaning that it cannot find the right application to validate against. Fix is to change the oidc_provider_configuration record that is mapped in the "oauth_oidc_entity" (entry that was created under application register)Cannot find oauth_oidc_entity for issuer https://sts.windows.net/<tenant>/ with any of the following client_ids: api://<instance>.service-now.com/<client-id>: no thrown errorOidc provider configuration "user claim" and "user field" values. OOB it is upn/preferred_username and email (sys_user). this can vary on the basis of how the customer azure tenant is configured. in this customer case, it was user_name that matches their azure/entra id upn value.