Forum Discussion
Forms embedded in SharePoint doesn't display in custom Teams app
Dinesh-MSFT Thank you for your explanation and research, but requiring server side components for embedding SharePoint in Teams is not a good solution. This stopped working some time this winter, and I assume it's caused by security hardening in Teams.
SharePoint is the man in the middle here and should be allowed to request obo tokens when embedded in Teams.
All parties involved here are Microsoft first party apps; Teams, SharePoint and Forms. There's no third party code involved in this custom Viva Connections setup, just the teams app manifest/json.
Is it correct that it's SharePoint that enforces the CORS restrictions on the OBO API endpoint?
Hi Petter Skodvin-Hvammen,
As discussed internally, embedding Microsoft Forms in a custom Teams app is not a standard practice and may lead to authentication issues due to the different handling of third-party apps in Teams. To confirm this, we suggest testing the same SharePoint page within the SharePoint tab app in Teams, which is a standard feature, to see if the form is displayed correctly.
- I think you guys are missing the OPs point.
if he uses Viva Connections then it's working fine.
if he makes his own Teams app then certain webparts [MS Forms .. Viva Engage] will break b/c of the token.
I am also having similar issue with Viva Engage web part on my intranet homepage. If using Viva connections app then it all loads fine. If I build a separate Teams app then the token for yammer is blocked.
