Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
Hi @CH,
Thank you for posting your question in the Microsoft Q&A forum.
According to your concern, this can be an issue with Windows-protocol handler registration. Windows handles protocol links like tel: / sip: / callto: through the default app associated with that link type. You can try double checking the protocol settings by going to Settings > Apps > Default apps > scroll down and select choose Default by link type > ensure the protocol links are using Teams as its default app
I have researched through Microsoft product help and other official information sources, and the result turns out that this behavior is not likely a service incident but an unexpected behavior. There are also some customers who also reported their problems with protocols in Office products. You can refer to these threads and see whether you are experiencing the same circumstances as they did:
- CANNOT OPEN THE SPECIFIED FILE with tel:-hyperlink | Microsoft Community Hub
- Problem using 'tel' hyperlink in Excel and other Office desktop products - Software & Applications … (I'm providing this information as a convenience to you. The sites are not controlled by Microsoft, and I can't make any representations regarding quality, safety or suitability of any software or information found there. Please make sure you completely understand the risk before retrieving any suggestions from the above link)
Hope this information may help. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.
Thank you for your understanding and cooperation. I'm looking forward to your reply.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread