About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
windows_tools
Summary:
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for key steps (such as uploading templates to storage) and referencing Windows/PowerShell tooling first and most prominently. The Azure CLI (cross-platform) example is only provided for the deployment step, not for the earlier template upload step. There is no mention of Linux-specific considerations or examples for uploading templates, and the workflow assumes familiarity with PowerShell and Windows-centric patterns.
Recommendations:
- Provide Azure CLI examples for all steps, including uploading templates to storage, not just deployment.
- Explicitly mention that both PowerShell and Azure CLI are cross-platform, and clarify when a script is Windows-specific.
- Add Linux/macOS shell (bash) examples for downloading files (e.g., using curl or wget) and uploading to Azure Storage (using az CLI).
- Reorder examples so that Azure CLI (cross-platform) appears before PowerShell, or present both in parallel tabs.
- Include notes about any OS-specific differences (such as file paths, command syntax, or required tools) for Linux/macOS users.
Create pull request
Flagged Code Snippets
## Deploy template
To deploy templates in a storage account, generate a SAS token and supply it to the _-QueryString_ parameter. Set the expiry time to allow enough time to complete the deployment. The blobs containing the templates are accessible to only the account owner. However, when you create a SAS token for a blob, the blob is accessible to anyone with that SAS token. If another user intercepts the URI and the SAS token, that user is able to access the template. A SAS token is a good way of limiting access to your templates, but you shouldn't include sensitive data like passwords directly in the template.
If you haven't created the resource group, see [Create resource group](./deployment-tutorial-local-template.md#create-resource-group).
> [!NOTE]
> In the below Azure CLI code, `date` parameter `-d` is an invalid argument in macOS. So macOS users, to add 2 hours to current time in terminal on macOS you should use `-v+2H`.
# [PowerShell](#tab/azure-powershell)