Azure-docs: Issue while passing Environment variable as secret as discussed in https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template?tabs=CLI

[pratiksharma-dev]

Hi Team,

I am currently trying to pass a secret value using environment variable property for Microsoft.Resources/deploymentscripts as mentioned in the docs at https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template?tabs=CLI

But this leads to the value being blank and cannot access it in the container instance create by runtimePowerShell resource. PFB the screenshots.

Everything works fine if I pass it as "value" instead of "securevalue".

PFB my arm template:

azuredeploy.txt

Kindly let me know if this is a platform issue or is there a specific way of accessing secure environment variables?

Thanks & Regards,
Pratik

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b5c4c8c5-7757-a969-5800-17f2f2312649
• Version Independent ID: 9ced8dd5-43ca-6d1f-c054-842299db8327
• Content: Use deployment scripts in templates - Azure Resource Manager
• Content Source: articles/azure-resource-manager/templates/deployment-script-template.md
• Service: azure-resource-manager
• Sub-service: templates
• GitHub Login: @mumian
• Microsoft Alias: jgao

[VikasPullagura-MSFT]

@pratiksharma-dev
Thanks for your Question! We are currently investigating and will get back on this.

[pratiksharma-dev]

@VikasPullagura-MSFT
Have created a support ticket for this as well (SR #120050223000279 | Issue with secret value for Environment variables). If you need any info you can reach me out at [e-mail]

[alex-frankel]

We are investigating the issue. Will report back when we have more information on what is happening. Thanks for reporting.

[lwang2016]

A fix has been checked in and being deployed. Will update once the deployment is done.

[pratiksharma-dev]

@lwang2016 Great news!! Thanks, let me know once it is patched...

[mumian]

please-close

[lwang2016]

Fix has been deployed to all prod regions.