能否在Microsoft Teams内部机器人中添加可点击的FTP、Windows网络或路径链接？

Hey there! Great question—this is a super common gotcha when working with Teams bots and non-standard link types, so let’s break down why your links aren’t clickable and how to fix it.

Teams enforces strict security restrictions on certain link protocols to protect users from malicious access to local or network resources. By default, it blocks links using ftp://, file:// (which covers Windows network paths like \\server\share and local paths), since these can expose sensitive system resources. That’s why your links show up as link-style text but can’t be clicked.

Let’s go through each link format you’re using and the practical workarounds to make them functional in Teams:

1. FTP Links #

Teams does support ftp:// links, but you need to ensure the link is fully formatted with the protocol prefix. For example:

• Use standard Markdown syntax: [Latest Installer (FTP)](ftp://your-ftp-server/path/to/latest-installer.exe)
• Heads up: Some Teams clients might prompt users to confirm opening the link due to security defaults, but it should become clickable once they approve. If it’s still not working, check with your org’s Teams admins—they might have blocked FTP links via the Teams Admin Center.

2. Windows Network Paths (\\server\share) #

These rely on the file:// protocol, which Teams blocks by default. Here are two reliable workarounds:

• Convert to a web-accessible link: Host the installer on an internal web server (like IIS) or set up a reverse proxy that maps the network share to an http:// or https:// endpoint. For example: [Latest Installer (Network Share)](http://internal-web-server/installers/latest.exe)
• Custom protocol (org-dependent): If your IT team allows it, you can create a small helper app that registers a custom protocol (e.g., mycompany-installer://). When users click this link, the helper app opens the network path. This requires admin setup and deploying the helper to users, so it’s more involved but works for internal use cases.

3. Local Windows Paths #

Local paths (like C:\installers\latest.exe) are never going to be clickable in Teams—this is a hard security restriction to prevent unauthorized access to a user’s local machine. Instead:

• Format the path as code to make copying easy: C:\installers\latest.exe
• Or, if possible, host the installer on an internal web server so users can download it directly via an HTTP/HTTPS link instead.

• Test links in both desktop and web Teams—behavior can vary slightly between clients.
• Check with your Teams admins about link-blocking policies—they might be able to whitelist specific protocols or internal domains for your bot’s use case.

内容的提问来源于stack exchange，提问作者PortMan