Apparently, Microsoft Teams is the fastest growing product in Microsoft’s history and in comparison to some of the other collaboration suites and enterprise social networks I kinda see why. However, when it comes to discussions, it is still miles away from discourse and chances are it will never catch up. Also, teams in Teams are currently limited to 2500 members and although that limit will be increases to 5000, it still means that it is not suitable for organization-wide discussions in larger organizations (discussions in Teams are only possible within teams, not across teams. So for everyone in the organization to be able to see a discussion, everyone has to be a member of a single team).
Discourse could fill these gaps but in order to properly integrate with Teams it would have to run in a Teams tab, which, I suppose, is an iframe.
I understand that discourse currently refuses to run in an iframe for security reasons but I wonder if certain iframes (like those in Teams) could be an exception?
We would absolutely love it. A whole swath of employers in my field have just signed up to Teams, and it looks to be big.
Having an integration between Discourse and Teams would mean that we can get our new Discourse forum working brilliantly. At the moment it is Discourse vs Teams as we are just setting things up. We have compelling international collaboration reasons for using Discourse, but I fear without an integration it will fail to fly.
What does “please do it” mean? What integration could there be other than SSO which already works, assuming you log in to existing internal systems using oauth 2 or ldap?
Just to clarify what is happening here, we ship a header with Discourse called:
X-Frame-Options: SAMEORIGIN
This stops sites adding yours site as an IFRAME which is a filthy SEO trick some people do to steal page rank and causes overall levels of confusion and do nasty things like clickjacking:
What I strongly support adding to Discourse is some ability to customize this header:
This particular request does not come up too often, but I do support amending it. It is a bit of a tricky change cause we do need some defense in depth here, some of our assets are delivered not via the app and we can not swap in the magic value there.
Sure we could have a site setting that simply removes X-Frame-Options to start with. Default off of course, but once you turn it on, you opt in to giving up all framing protection.
I suspect my company is going to end up in Teams too once the pressure to migrate away from Skype for Business beats the security concerns of moving users to a cloud service.
I have a goal of augmenting our traditional Outlook/Exchange e-mail with Discourse and finding a better chat tool than SfB for the daily high speed bot-assisted operations chat, voice and screen sharing (stuff that is outside the scope of Discourse).
If it becomes easy to link Discourse and Teams together that could make it a really nice combination. We already have excellent SSO plugins for Azure and traditional AD to make the user experience pretty seamless
Hi @codinghorror@sam,
Just wondering if anyone’s taken this any further in the past year?
Has the option to modify/remove X-Frame-Options been implemented?
Has anyone managed to do this cleanly with SSO?
