Azure-docs: Azure Cloud Shell (Powershell) can't find path 'path'

[wilsonriv]

I had no issues following the QuickStart using bash as my CLI but for some reason Powershell can't find my template file or any other file even when clearly the file exists. Even creating a directory and cd to it trigger the issue.

Cannot retrieve the dynamic parameters for the cmdlet. Cannot find path 'Azure:/azuredeploy.json' because it does not exist.

---

Document Details

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

• ID: 30ef211a-c625-61cd-9ae9-ca63e32ff4d2
• Version Independent ID: b60685c0-1d9c-ebcb-4393-e231d7b09c24
• Content: Use Visual Studio Code to create Azure Resource Manager template
• Content Source: articles/azure-resource-manager/resource-manager-quickstart-create-templates-use-visual-studio-code.md
• Service: azure-resource-manager
• GitHub Login: @mumian
• Microsoft Alias: jgao

[SadiqhAhmed-MSFT]

@sabdiel Thanks for the question! Did you upload the file to CLI/PowerShell? If yes, logout from Cloud Shell and re-login. If this doesn't work, logout from the Azure portal and re-login.

[mumian]

@sabdiel - Thank you for reporting the issue. It seems an issue with the Cloud shell. The issue is under investigation. Until the problem is resolved, you can deploy the template from your local computer. For the instructions, see https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy#deploy-a-template-from-your-local-machine.

[wilsonriv]

Thanks @SadiqhAhmed-MSFT @mumian

I did as instructed by @SadiqhAhmed-MSFT but the issue still persists and as I am able to complete the QuickStart using Bash I also believe is a Cloud Shell (Powershell) issue as indicated by @mumian.

Thanks again.

[Georg-M]

In addition to the workaround given in Note for Deploy the template
there is one much simpler workaround:
Use "$HOME/azuredeploy.json" instead of "azuredeploy.json" in a command-line

[WatersJohn]

This unfortunately is still an issue in March; the $HOME workaround is helpful.

[ielcoro]

I don't know why is this issue closed, I´m still it experiencing it, and using $HOME is the only workaround working.

[mumian]

It is by design. Using $HOME is required.