Good morning Terrance Drakes,
The issue is not that your home PC lacks a "secure connection" to Azure. The issue is how the Azure Resource Manager (ARM) service interacts with Azure Files.
When you run az deployment group create --template-uri ..., your local PC does not download that file. Instead, your PC sends that URL to the Azure control plane, and the Azure control plane tries to fetch the file. Azure Files shares (unlike Blob Containers) are not designed to serve files via simple HTTP/HTTPS GET requests unless explicitly authenticated. The error "Unable to retrieve url" is happening because the ARM service tries to hit that link, gets rejected (because there is no authentication token attached to the URL), and fails.
Here are the two actual ways to fix this instantly without building network infrastructure:
Option 1: The "Local File" Switch (Fastest)
Since you are on your PC, you do not need to force Azure to fetch the template from a URL. Download the acrtemp.json file to your local desktop (or if you have it locally already). Change your command parameter from --template-uri to --template-file.
Command: az deployment group create --resource-group myresource --template-file "C:\Path\To\acrtemp.json"
This bypasses the storage account and URL issues entirely by uploading the script directly from your machine during execution.
Option 2: The SAS Token (If you must use a URL)
If you are required to keep the file in the cloud, you cannot just use the plain URL. You must append a SAS (Shared Access Signature) token. The ARM service is external to your storage account; it needs a "key" to get in.
- Go to your Storage Account > File Shares > share1.
- Right-click
acrtemp.jsonand select "Generate SAS". - Copy the Blob SAS URL (it will look like
https://...json?sv=2020...). - Paste that long URL into your
--template-uricommand.