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 demonstrates a Windows bias by providing PowerShell scripts and instructions first, using Windows-centric tools (PowerShell, Invoke-WebRequest), and focusing on PowerShell-based workflows for setup and deployment. While Azure CLI examples are included, the initial and most detailed setup instructions rely on PowerShell, which is more familiar to Windows users. There is also a lack of Linux-native shell scripting or guidance for Linux users in the setup phase, and the 'Try-it' Cloud Shell guidance assumes PowerShell usage.
Recommendations:
- Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for setup and template upload steps.
- Present Azure CLI or Bash examples before or alongside PowerShell, not after.
- Include explicit instructions for Linux/macOS users, such as using curl/wget instead of Invoke-WebRequest, and clarify Cloud Shell defaults.
- Avoid assuming PowerShell as the default shell; clarify when instructions are Windows-specific.
- Add notes or callouts for cross-platform differences, especially in file paths and command syntax.
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)