Custom URI handlers
Hyperlinks with non-http or non-https prefixes do not currently work such as M-Files URLs that begin with m-files://
Please allow at least admins enable these custom URI handlers in Teams. They work perfectly in Slack :)
Jordan Ocokoljic commented
This is almost fundamental at my workplace. Not having it hampers communication greatly.
Dave East commented
Yes please! I would probably use this 5-10 times per day.
Daniel Keogh commented
Lack of support here is pretty painful for me.
Brett Shearer commented
Having already gone through the trouble of getting URI scheme support re-enabled in Skype for Business it is ludicrous to have the same fight on our hands again with MS.
Surely no-spam policy doesn't make sense to block custom handlers. Most problems would be with HTTP/HTTPS links anyway.
Tyson Zeilstra commented
Support, this would make workflow much easier.
Chau Nguyen commented
+1. MSFT emphasizes security and no-spam policy in Teams, but allowing admins to opt into custom URI schemes would be really helpful for custom integrations.
Mika Javanainen commented
Would it be possible to get an update on this? Is supporting Custom URI handles on the roadmap?
Seconded. We have a URI scheme for internal applications and it doesn't show up as a hyperlink at all in Teams.
Craig Hawker commented
This could also work in mobile, too, where organisations have added support for custom URI prefixes (e.g. https://www.microsoft.com/en-us/store/p/m-files/9wzdncrdsgx0).
Nicola Rampazzo commented
Also links created with onenote: URI scheme don't work unless created inside Teams.
mailto: uri work as expected, opening outlook.
callto: URI are changed to http://callto: - breaking skype action