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:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI, and file paths in PowerShell use Windows-style (e.g., c:\Templates\azuredeploy.json) without Linux equivalents. The CLI section mentions Bash but does not provide explicit Linux/Mac file path examples or note cross-platform differences. There is no mention of Linux-specific considerations, and the 'Next steps' section links only to PowerShell-focused resources.
Recommendations:
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows.
- In PowerShell examples, provide both Windows and Linux/Mac file path formats (e.g., c:\Templates\azuredeploy.json and /home/user/Templates/azuredeploy.json).
- Explicitly mention that Azure CLI commands are cross-platform and provide notes or examples for both Windows (CMD/PowerShell) and Linux/Mac (Bash) environments, especially for environment variable syntax and file paths.
- In the 'Next steps' section, include links to both PowerShell and CLI documentation, as well as any Linux-specific deployment guides if available.
- Add a short section or callout highlighting any differences or considerations when running these commands on Linux or MacOS.
Create pull request
Flagged Code Snippets
---
## Upload private template to storage account
Now, you're ready to upload your template to the storage account. Provide the path to the template you want to use.
# [PowerShell](#tab/azure-powershell)
---
## Provide SAS token during deployment
To deploy a private template in a storage account, generate a SAS token and include it in the URI for the template. Set the expiry time to allow enough time to complete the deployment.
> [!IMPORTANT]
> The blob containing the private template is accessible to only the account owner. However, when you create a SAS token for the blob, the blob is accessible to anyone with that URI. If another user intercepts the URI, that user is able to access the template. A SAS token is a good way of limiting access to your templates, but you should not include sensitive data like passwords directly in the template.
>
# [PowerShell](#tab/azure-powershell)