Forum Discussion
custom protocol links not supported
Many applications use custom protocols. For example iManage uses the protocol iwl: to allow users launch documents from iManage Why is this not supported in Teams? It's ok to add links to "standa...
In fact there even is a "precedent" for this in Microsoft Office. If, for example, you use a Custom Protocol "foo" in your organisation you can get your Office applications to trust this protocol by entering this into your registry:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\<version>\Common\Security\Trusted Protocols\All Applications\foo:
so you should be able to quite easily do something similar for Teams, e.g. by letting teams check a key like
HKEY_CURRENT_USER\Software\Policies\Microsoft\Teams\Common\Security\Trusted Protocols\All Applications\foo:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\<version>\Common\Security\Trusted Protocols\All Applications\foo:
so you should be able to quite easily do something similar for Teams, e.g. by letting teams check a key like
HKEY_CURRENT_USER\Software\Policies\Microsoft\Teams\Common\Security\Trusted Protocols\All Applications\foo:
rozeboosje370 There is a Uservoice item on this - you might want to vote for it: why don't custom protocols work when inserting links – Welcome to UserVoice!