![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 67%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETY%3C/text%3E%3C/svg%3E)
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
1,242 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 61%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELR%3C/text%3E%3C/svg%3E)
Hi @Tony Yip
Thanks for the question and using MS Q&A platform.
Yes, the special characters in the URL must be anyway encoded for their correct interpretation by browsers and servers. This is more relevant when URLs carrying query parameters buffer characters that are not encoded, which can result in misinterpretation of the URL layout.
1.The URL being created dynamically by different teams should be better off if they were all implementing a consistent mechanism for encoding so that all special characters are being encoded correctly before the URLs are used. This will avoid any problems with tracking users and ensure that all parameters are properly recognized.
2.Unfortunately, ACS doesn't have a global switch to automatically encode URLs - this needs to be handled either in your code or templates.
references:
https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-url-filters#special-characters-in-url-filters
https://learn.microsoft.com/en-us/xandr/invest/click-tracking#track-clicks-on-third-party-tags
Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.