This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(236.8, 4%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESE%3C/text%3E%3C/svg%3E)
We have a Service Account password that contains an ampersand in our web.config. We are using pipeline variables and transforming it during our build.
Escaping the ampersand, & doesn't work, the transform actually put & in the password vs. the &.
We check the build artifacts before they are deployed to see the values that the pipeline puts into the file before they are "encrypted".
How can I set the pipeline variable to correctly transform this password where the value is put in correctly? Should we modify anything to be able to handle this in our pipeline variables that get transformed?
![](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(192, 28.999999999999996%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Hi @Shipman, Edward (WP),
Would you like me to post a detailed answer? I think it could be helpful for others in the community as well.
After testing, we have found that including the escaped ampersands in the pipeline variable will ultimately be put into the sensitive data section with the escaped ampersands but when reading them, it will be returned correctly with just the ampersand.