Forum Discussion
Create a teams-app (app studio) - left menu to just open sharepoint url site - That works on Desktop
- Apr 01, 2022X-Frame-Options is a header included in the response to the request to state if the domain requested will allow itself to be displayed within a frame. It has nothing to do with javascript or HTML, and cannot be changed by the originator of the request. 
 This website has set this header to disallow it to be displayed in an iframe. There is nothing that can be done in a client-side web browser to stop this behaviour.
 Please refer: X-Frame-Options - HTTP | MDN (mozilla.org)
Anyone able to figure out why some links do not work to open in the teams client but do work in the browser. Specially when it is a sharepoint link... i can accept that all pages can not be opened but sharepoint should be supported...
- Prasad_Das-MSFTMar 30, 2022Microsoft You must allow your tab pages to be shown in an iFrame, using X-Frame-Options and Content-Security-Policy HTTP response headers. - Set header: Content-Security-Policy: frame-ancestors teams.microsoft.com *.teams.microsoft.com *.skype.com
- For Internet Explorer 11 compatibility, set X-Content-Security-Policy.
- Alternately, set header X-Frame-Options: ALLOW-FROM https://teams.microsoft.com/. This header is deprecated but still accepted by most browsers
 Ref: Prerequisites - Teams | Microsoft Docs
 - oskarkuusMar 30, 2022Brass ContributorThank you for your reply.
 But i dont know how to do this. Tried to google around but i cant figure out if i even can change "x-frame-options" on a sharepoint site. Or is it something i should have in the teams-app so that the webpage work?- Prasad_Das-MSFTApr 01, 2022Microsoft X-Frame-Options is a header included in the response to the request to state if the domain requested will allow itself to be displayed within a frame. It has nothing to do with javascript or HTML, and cannot be changed by the originator of the request. 
 This website has set this header to disallow it to be displayed in an iframe. There is nothing that can be done in a client-side web browser to stop this behaviour.
 Please refer: X-Frame-Options - HTTP | MDN (mozilla.org)
 
 
- Set header: