Support for http and not only https
Only possible to use HTTPS urls as tabs. Would be nice if HTTP would work as well.
As you may be aware, HTTP is inherently less secure compared to HTTPS, and modern browsers are making it increasingly difficult to access http:// links; many of them require users to bypass an intermediate page with a scary security warning.
We take users privacy and security very seriously, and we also take popular UserVoice feature requests very seriously. We investigated many approaches to address this feature request in a way that would also pass security review. One way would have required tenant administrators to manually add domains/intranet sites to an “allow list”, – we received feedback that be unwieldy and add work for IT departments.
Even if that were acceptable however, we’d have a situation that http:// URLs would only ever work on the desktop client. Users who clicked on the tab using the browser client would see the same scary warning that users accessing the same URL in a browser tab would see.
Given these limitations, we are no longer planning to deliver this feature request.
211 commentsComments are closed
Mirte Hoedemaker commented
Warren, I would like to know the actual status of this issue. Since the last update was in September 2018 things might have changed. Hope so!
I'd like to see http sites with a different border, icon, tab text color or otherwise to indicate that the site is not secure. Maybe something like the certificate icons in browsers for URLs.
Please keep up the good work. I would be of great help.
Thanks for the effort. This feature would be extremely useful to us. Please keep us updated on the progress.
Chris Hamm commented
As a workaround, you can use a URL shortener like bitly to generate an HTTPS link. When added to Teams, this will redirect to the HTTP site.
Would be more than nice. Many government websites are http so only allowing https is very limiting.
Hello, any update regarding this?
Andrew Morley commented
This is a massive inconvenience as it breaks compatibility with our document management system. Workaround is to copy and paste the links but we shouldn't have to in the 21St century. Mattermost gets this right.
James Petesen commented
Any expected timeline on this, nearly all of our intranet sites are http?
This would be very useful to me as well. Hoping to hear an update soon.
Any updates this week? Looking forward to adding my internal http links in the teams tabs
This is kind of a dealbreaker for us when it comes to using Teams. Looks like it's been 3 months since the last update. When can we expect news?
This is becoming a significant feature as users expecting to add none secure site links to their teams channels.
also need this to make Teams a hub for my team
Asking for HTTP is nowadays (2018) ridiculous : if you have internal HTTP websites, that are not yet upgraded to HTTPS, then it is your own company fault, and MS does not need to adapt to your, sorry to say, inability to follow common industry best practices.
Even for developement-like purposes, there is no technical reason you can raise to switch back to HTTP.
If I would be your customer, and would know that vast majority of your IT infra is still using HTTP, I would not forget to quickly go to your competitor.
Not to mention that I don't get how you can pass audits and ISO certifications...
It's not good choice to add encryption(TLS) to internal site ( not published ) for only to use in Teams.
Make Teams can access to not encrypted site will be better choice.
We are looking for the same.
Would love to use teams for out new project, but without http we will not be able to.
E. van Kaam commented
Still waiting for a solution to place http in Teams. Lots of weeks since 9 september 2018
[Deleted User] commented
our internal company sites is not secure, and thats why we need normal http