Azure DevOps Wiki跳转时QuickLink格式异常问题求助

Problem #

When adding ServicePulse links to an Azure DevOps Wiki table, colons (:) in query parameters get automatically escaped to %3A, breaking the expected URL structure for ServicePulse endpoints. IIS redirects aren’t feasible due to multi-environment constraints.

Solutions #

1. Use Raw HTML Anchor Tags Instead of Markdown Links #

Azure DevOps Wiki supports raw HTML, which bypasses the Markdown parser’s automatic URL encoding. Replace your Markdown link with an HTML <a> tag in the table cell:

| Endpoint Alpha | <a href="http://servicepulse.<domain>.nl/?scu=http://servicepulse.<domain>.nl/api/alpha/&amp;mu=http://servicepulse.<domain>.nl/monitoring/alpha/#/dashboard">ServicePulse</a> |

This preserves the original URL structure, including unescaped colons in query parameters. Note that ampersands (&) in the href attribute must be escaped to & to comply with HTML standards.

2. Check Wiki Rendering Configuration #

Confirm your Azure DevOps Wiki isn’t set to enforce strict URL encoding. While this is rarely a configurable setting, reviewing Wiki markup rendering options (under Wiki settings) can rule out unexpected behavior.

3. Leverage Environment Variables (If Applicable) #

If your organization uses Azure DevOps variables for environment-specific domains, define the base ServicePulse URL as a variable and inject it into the HTML link. This simplifies multi-environment management without altering URL structure:

| Endpoint Alpha | <a href="$(ServicePulseBaseUrl)/?scu=$(ServicePulseBaseUrl)/api/alpha/&amp;mu=$(ServicePulseBaseUrl)/monitoring/alpha/#/dashboard">ServicePulse</a> |

(Note: Variable support depends on your Azure DevOps configuration and may require additional setup.)

Why This Works #

Azure DevOps Wiki’s Markdown parser automatically encodes special characters like colons to comply with RFC standards, but ServicePulse expects the literal http:// prefix in query parameters. Using HTML anchors directly avoids this automatic encoding, ensuring the URL is passed to ServicePulse exactly as intended.

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