Azure Resource Manager
1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
492 issues found
Showing 76-100 of 492 flagged pages
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-variables.md
...les/azure-resource-manager/templates/copy-variables.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the 'Copy limits' section, Azure PowerShell is listed before Azure CLI, and the 'Next steps' section links only to a PowerShell deployment guide, omitting Linux-specific or cross-platform deployment instructions. There are no explicit Linux or Bash examples, and no mention of Linux-specific tools or workflows for ARM template deployment.
Recommendations
- Add explicit Bash or shell examples for deploying ARM templates, alongside PowerShell examples.
- In sections listing supported tools (e.g., 'Copy limits'), mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Include links to documentation for deploying ARM templates using Azure CLI and REST API, not just PowerShell.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users.
- Where possible, provide parity in example scripts and command-line instructions for both Windows and Linux environments.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/create-visual-studio-deployment-project.md
...r/templates/create-visual-studio-deployment-project.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows users by exclusively using Visual Studio (a Windows-centric IDE) and PowerShell scripts for deployment. All examples and workflows assume the use of Visual Studio and PowerShell, with no mention of Linux, macOS, or cross-platform alternatives. There are no CLI, Bash, or VS Code examples, nor any guidance for non-Windows environments. The only deployment scripts referenced are PowerShell-based, and all project creation and management steps are Visual Studio GUI-centric.
Recommendations
- Add equivalent instructions for creating and deploying resource group projects using cross-platform tools such as Visual Studio Code, Azure CLI, and ARM/Bicep templates.
- Provide Bash or Azure CLI script examples for deployment, in addition to or instead of PowerShell scripts.
- Mention and link to cross-platform alternatives for users on Linux or macOS, such as using VS Code with Azure extensions.
- Clearly state the Windows-specific nature of the Visual Studio workflow at the top, and guide non-Windows users to alternative documentation.
- Include a section or callout for Linux/macOS users, outlining supported workflows and tools.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/data-types.md
...rticles/azure-resource-manager/templates/data-types.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references PowerShell specifically when discussing integer parameter limits, without mentioning Linux equivalents such as Azure CLI. No Linux-specific tools or examples are provided, and the only command-line tool mentioned is PowerShell, which is Windows-centric.
Recommendations
- When discussing SDK or command-line tool limitations, mention both PowerShell and Azure CLI, and provide information about their respective behaviors on Windows, Linux, and macOS.
- Include examples or notes for Linux users, such as how to deploy ARM templates using Azure CLI.
- Avoid referencing only Windows tools unless there is a clear technical reason; provide parity in tool references and examples.
- Consider a table or section comparing behaviors across PowerShell, Azure CLI, and other SDKs to ensure cross-platform clarity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-resource-group.md
...resource-manager/templates/deploy-to-resource-group.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but PowerShell examples are consistently shown before CLI examples in multi-step deployment sections. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows-first bias. There is no mention of Linux-specific shells or scripting environments (e.g., Bash), nor are there explicit Linux command-line examples or notes about cross-platform usage. The documentation does not reference Linux tools or patterns, and the use of PowerShell as a primary example can be seen as a bias toward Windows users.
Recommendations
- Present Azure CLI (which is cross-platform) examples before PowerShell examples to avoid suggesting a Windows-first workflow.
- Explicitly mention that Azure CLI commands work in Bash, Cloud Shell, and other Linux environments.
- Add Bash-specific notes or examples where appropriate, especially for scripting or automation scenarios.
- Clarify that PowerShell Core is cross-platform if referencing PowerShell, or provide links to instructions for using PowerShell on Linux/macOS.
- Ensure parity in troubleshooting and tool references for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-subscription.md
...e-resource-manager/templates/deploy-to-subscription.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands, but PowerShell is consistently presented as the second option after Azure CLI. There are no explicit Linux shell (bash) examples, nor are there any references to Linux-specific tools or scripting environments. The use of PowerShell (which is traditionally associated with Windows, though now cross-platform) is prominent, and there is no mention of Linux-native scripting or automation approaches. The documentation does not clarify that Azure CLI commands are cross-platform, nor does it provide bash-specific guidance or troubleshooting.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- Add bash-specific examples or notes, especially for parameter passing and environment variable usage, to address common Linux shell scenarios.
- Include troubleshooting tips or links for common issues encountered on Linux (e.g., line endings, quoting differences).
- Consider providing examples using native Linux tools (e.g., curl for REST API calls) where relevant.
- Reorder sections or alternate the order of CLI and PowerShell examples to avoid implicit prioritization of Windows tools.
- Clarify that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-what-if.md
...les/azure-resource-manager/templates/deploy-what-if.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and terminology are presented first and in greater detail than Azure CLI equivalents. Output samples and explanations use PowerShell syntax and conventions, and the installation instructions for Azure PowerShell are more prominent than those for Azure CLI. The use of PowerShell-specific tools and patterns (e.g., `$results = ...`, `foreach ($change in $results.Changes)`) is emphasized, while Linux-specific considerations (such as shell differences, color handling, or alternative scripting) are not addressed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so that CLI is presented first in some sections.
- Provide equivalent output samples using Azure CLI syntax, especially for text output and programmatic inspection.
- Include notes on running Azure CLI commands in Linux/macOS environments, such as shell differences and color handling.
- Add Bash or shell scripting examples for programmatic evaluation of what-if results (e.g., using jq to parse JSON output).
- Clarify that both PowerShell and CLI are cross-platform, and explicitly mention Linux/macOS compatibility.
- Ensure installation instructions for Azure CLI are as detailed and prominent as those for PowerShell.
- Avoid using only PowerShell conventions (e.g., `$variable`, `foreach`) in output and code samples; provide CLI/Bash alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-modes.md
...s/azure-resource-manager/templates/deployment-modes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting the PowerShell example before the Azure CLI example in the 'Set deployment mode' section. PowerShell is a Windows-centric tool, and its precedence over Azure CLI (which is cross-platform and more commonly used on Linux/macOS) suggests a Windows-first approach. Additionally, there are no explicit Linux shell (e.g., Bash) or platform-agnostic deployment examples, nor is there mention of Linux-specific considerations or tools. The documentation also references file paths in a Windows format (e.g., c:\MyTemplates\storage.json) in the PowerShell example, further reinforcing the Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples or at least clarify that Azure CLI commands work on Linux/macOS terminals.
- Use platform-neutral file paths in examples (e.g., ./MyTemplates/storage.json) or provide both Windows and Linux path formats.
- Explicitly mention that both Azure CLI and PowerShell are supported on all major platforms, and link to guidance for Linux/macOS users.
- Consider adding a short section or note for Linux/macOS users to ensure parity and inclusivity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/resource-extensions.md
...zure-resource-manager/templates/resource-extensions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page references Windows resources and links before Linux equivalents (e.g., 'features for Windows' is mentioned first), and does not provide Linux-specific examples or highlight Linux tools. The tutorials and extension references do not clarify Linux support or provide parity in examples.
Recommendations
- List Linux and Windows resources in parallel or alternate order to avoid Windows-first bias.
- Explicitly mention and link to Linux extension documentation wherever Windows extensions are referenced.
- Provide Linux-specific examples or tutorials alongside Windows ones, especially for common post-deployment scenarios.
- Clarify in each extension or tutorial whether it applies to Windows, Linux, or both.
- Include references to Linux tools and patterns (e.g., shell scripts, cloud-init) where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md
...nager/templates/deployment-tutorial-linked-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell scripts as the primary method for template storage and deployment, with Azure CLI examples presented only after PowerShell. The instructions for storing templates in Azure Storage use only PowerShell, and the 'Try-it' Cloud Shell guidance is tailored to PowerShell users. There is also a reliance on Windows-centric tools and patterns, with minimal Linux-specific guidance except for a brief note about the 'date' command in macOS.
Recommendations
- Provide equivalent Azure CLI and/or Bash scripts for all steps, especially for storing templates in Azure Storage, not just for deployment.
- Present Azure CLI and Bash examples alongside PowerShell, or allow users to select their preferred environment at the start of each section.
- Include Linux/macOS-specific notes and troubleshooting tips where command syntax or behavior differs, not just for the 'date' command.
- Avoid language such as 'right-click to paste' which is Windows-centric; instead, use platform-neutral instructions.
- Ensure that all 'Try-it' and Cloud Shell instructions clarify how to switch between Bash and PowerShell environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/key-vault-parameter.md
...zure-resource-manager/templates/key-vault-parameter.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is given equal prominence and is referenced throughout. The introductory sections and links reference Windows scenarios (e.g., VM certificate install for Windows), and there is no mention of Linux-specific tools or shell patterns (such as Bash, zsh, or Linux-native scripting). References to PowerShell and Windows-centric deployment patterns are present, while Linux or cross-platform alternatives are not highlighted or explained.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Add Bash/zsh script examples for Linux users, especially for parameter file manipulation and deployment.
- Include references or links to Linux-specific documentation or quickstarts (e.g., deploying to Linux VMs, using Linux-native tools).
- Clarify that PowerShell Core is available on Linux/macOS, or recommend Azure CLI as the default for non-Windows environments.
- Add notes or sections that address Linux deployment scenarios, such as using SSH keys or Linux VM configuration with Key Vault secrets.
- Ensure that example links and quickstarts are not Windows-specific unless necessary, or provide Linux equivalents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/overview.md
.../articles/azure-resource-manager/templates/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias. While it mentions both PowerShell and Bash for deployment scripts, the only concrete tooling example for testing (arm-ttk) is a PowerShell script, and the authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are more Windows-centric (though VS Code is cross-platform). In the CI/CD section, Azure DevOps and Visual Studio project pipelines are emphasized, which are often associated with Windows workflows. PowerShell is mentioned before Bash, and there are no explicit Linux-specific examples or tool recommendations. The deployment options list Azure CLI and PowerShell, but PowerShell is mentioned before Bash in the extensibility section.
Recommendations
- Provide explicit Linux/bash examples or references alongside PowerShell, especially for testing and scripting (e.g., mention Bash-based test kits or how to use arm-ttk in Linux environments).
- Highlight cross-platform or Linux-native authoring tools (such as vim, nano, or JetBrains IDEs) or clarify that Visual Studio Code is cross-platform.
- In the CI/CD section, mention other popular CI/CD systems (such as GitHub Actions, Jenkins, or GitLab CI) with Linux runners, and provide links to relevant guides.
- When listing deployment options, alternate the order or explicitly state that both Azure CLI and PowerShell are cross-platform, and provide example commands for both.
- Where PowerShell is mentioned, ensure Bash is given equal prominence and provide sample Bash scripts or references.
- If possible, include screenshots or walkthroughs from Linux environments (e.g., Azure Cloud Shell in Bash mode).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/parameter-files.md
...es/azure-resource-manager/templates/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool. The PowerShell example appears after the CLI example, but there is no explicit Linux shell example (e.g., Bash), nor is there mention of Linux file path conventions. The Visual Studio tip is also Windows-specific. There is no mention of Linux editors or deployment patterns.
Recommendations
- Add explicit Bash/Linux shell examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/storage.parameters.json).
- Clarify that Azure CLI works cross-platform and provide Linux/macOS file path examples alongside Windows ones.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for parameter file management.
- Where PowerShell is referenced, note that PowerShell Core is available on Linux/macOS, and provide examples with Linux file paths.
- Avoid Windows-centric file paths in generic examples, or provide both Windows and Linux/macOS variants.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-deploy-linked-template.md
...ger/templates/template-specs-deploy-linked-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. File paths are given in Windows format (e.g., c:\Templates\deployTS\azuredeploy.json) without mention of Linux alternatives. PowerShell examples and instructions are presented before Azure CLI, and troubleshooting notes specifically reference Windows PowerShell issues. There are no explicit Linux shell examples, nor are Linux file path conventions or considerations discussed.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/deployTS/azuredeploy.json).
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implicit prioritization.
- Include troubleshooting notes relevant to Linux/macOS environments, not just Windows PowerShell.
- Explicitly state that both Windows and Linux are supported, and mention any platform-specific considerations.
- Add Bash shell examples for variable assignment and command usage where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-template-specs.md
...-manager/templates/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits several Windows-centric biases. File paths in all examples use Windows-style (C:\Templates\...), with no mention of Linux or macOS equivalents. PowerShell is presented as a primary tool alongside Azure CLI, and references to Azure PowerShell are frequent, including in prerequisites and role assignment tutorials. There are no Linux shell (bash) or macOS-specific instructions, nor are Linux file paths or environment differences addressed. Known issues are only called out for Windows PowerShell, and the documentation assumes a Windows environment throughout.
Recommendations
- Provide Linux/macOS file path examples (e.g., /home/user/Templates/createStorageV1.json) alongside Windows paths.
- Explicitly mention that Azure CLI commands work on Linux/macOS and show sample commands using bash syntax where appropriate.
- Include notes or tabs for Linux/macOS environments, especially for file operations and environment setup.
- Reference role assignment tutorials using Azure CLI or bash, not only PowerShell.
- Call out any cross-platform differences or issues, not just Windows-specific ones.
- Ensure screenshots and instructions in the portal are not Windows-specific (e.g., avoid showing Windows file dialogs only).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md
...emplates/quickstart-create-templates-use-the-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio Code and Visual Studio (both Windows-centric tools) for ARM template development, and by mentioning Azure PowerShell and Azure CLI for deployment, with PowerShell listed first. There are no explicit Linux examples or mentions of Linux-specific tools or workflows. The guidance assumes a Windows environment and does not address Linux users' needs or alternative editors and shells.
Recommendations
- List Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, and suggest alternative editors (e.g., Vim, Emacs, nano) for Linux users.
- Include a note or section on how to deploy ARM templates using the Azure CLI from a Linux terminal.
- Avoid recommending Visual Studio (which is Windows-only) as the primary editor; instead, focus on cross-platform tools.
- Add Linux-specific instructions or screenshots where relevant, or clarify that the portal experience is identical across platforms.
- Ensure parity in tool recommendations by including Bash and Linux shell examples where command-line deployment is discussed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/secure-template-with-sas-token.md
...ce-manager/templates/secure-template-with-sas-token.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all steps, but the PowerShell examples use Windows-style paths (e.g., c:\Templates\azuredeploy.json) and are presented before the Azure CLI/Bash examples in each section. There are no explicit Linux/macOS-specific notes or examples, and the CLI section only briefly mentions Bash in Cloud Shell, without addressing local Linux environments or common Linux file paths. This structure subtly prioritizes Windows/PowerShell users and may cause confusion for Linux users.
Recommendations
- Alternate the order of PowerShell and CLI examples or present them side-by-side to avoid consistently prioritizing Windows/PowerShell.
- In CLI examples, provide explicit Linux/macOS shell commands and file path examples (e.g., /home/user/Templates/azuredeploy.json) to improve clarity for Linux users.
- Add notes or callouts for Linux/macOS users regarding any differences in command syntax, environment variables, or file paths.
- Consider including a table summarizing command differences or prerequisites for Windows, Linux, and macOS environments.
- Ensure that all references to file paths and shell commands are platform-agnostic or provide platform-specific alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-expressions.md
...ure-resource-manager/templates/template-expressions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) command-line examples for deploying ARM templates. There are no examples using cross-platform tools like Azure CLI or bash scripts, and the resource deployment examples use 'AzurePowerShell' as the script kind. Linux or cross-platform equivalents are not mentioned or shown, and PowerShell is referenced before any other tool.
Recommendations
- Add equivalent Azure CLI (az) command-line examples for deploying templates and passing parameters, alongside or before PowerShell examples.
- Include examples using 'AzureCLI' as the deployment script kind in ARM templates, not just 'AzurePowerShell'.
- Explicitly mention that ARM templates and their deployment can be managed from Linux, macOS, and Windows, and provide bash or shell script examples where appropriate.
- Reorder examples or provide parallel examples so that Linux/cross-platform tools are not always secondary to Windows/PowerShell.
- Clarify when a tool or pattern is Windows-specific, and offer alternatives for other platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-create-linked.md
...urce-manager/templates/template-specs-create-linked.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths (e.g., c:\Templates\...), presenting PowerShell examples and terminology before Azure CLI, and omitting explicit Linux/macOS file path examples. The instructions and examples assume a Windows environment, with no mention of Linux-specific considerations or shell usage.
Recommendations
- Provide Linux/macOS file path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
- Explicitly mention that the instructions apply to all platforms, and clarify any OS-specific differences.
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
- Include notes or tabs for Bash or other common Linux shells where variables or commands differ.
- Avoid using Windows-specific terminology (e.g., 'local computer' with Windows paths) without also referencing Linux/macOS equivalents.
- Add troubleshooting notes for Linux/macOS if there are known issues, not just for Windows PowerShell.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs.md
...les/azure-resource-manager/templates/template-specs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell and Azure CLI examples side-by-side, but PowerShell is always listed first and referenced as a primary tool. There are no explicit Linux-specific instructions, nor are there examples using Bash, native Linux shell scripting, or Linux-specific tooling. The documentation assumes familiarity with PowerShell patterns (e.g., variable assignment, parameter passing) and does not mention platform differences, such as file paths or shell environments. No examples are given for deploying template specs using Bash scripts, nor is there guidance for Linux users regarding prerequisites or environment setup.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) first to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash script examples for common workflows.
- Add a section on environment setup for Linux users, including installation instructions for Azure CLI and notes on file path conventions.
- Where PowerShell syntax is shown, provide equivalent Bash or shell scripting examples for variable assignment and command chaining.
- Clarify that PowerShell examples are primarily for Windows users, and encourage Linux users to use Azure CLI.
- Include troubleshooting tips or notes for Linux-specific issues (e.g., file permissions, shell quoting).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-functions.md
...e-manager/templates/template-tutorial-add-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias. In the prerequisites, 'Azure PowerShell' is mentioned before Azure CLI, and PowerShell is listed as an option alongside Azure CLI, which is more cross-platform. In the deployment section, PowerShell instructions are presented before Azure CLI, and the example uses PowerShell-specific syntax. There are no explicit Linux shell (bash) examples, and the verification and cleanup steps rely on the Azure Portal UI, which is platform-agnostic but does not provide CLI alternatives.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for both.
- Add bash shell examples for running Azure CLI commands, showing both Windows (cmd/PowerShell) and Linux/macOS (bash) syntax for environment variables and command usage.
- Where possible, provide CLI commands for verification and cleanup steps, not just portal instructions.
- Avoid implying that Visual Studio Code is required; mention it as a recommended editor but also suggest alternatives available on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-parameters.md
...-manager/templates/template-tutorial-add-parameters.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI examples, and provides no explicit Linux/macOS shell (e.g., Bash) instructions or screenshots. While Azure CLI is cross-platform, there are no Linux-specific notes, nor are there any examples using native Linux tools or terminal environments. The clean-up section only describes using the Azure Portal (web UI), not command-line options, and the prerequisites mention Visual Studio Code but do not mention Linux editors or shells.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples, or present Azure CLI (the more cross-platform tool) first.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
- Add Linux/macOS-specific notes or screenshots where relevant (e.g., for file paths or shell variables).
- In the prerequisites, mention popular Linux editors (e.g., vim, nano) and shells as alternatives to Visual Studio Code.
- For resource clean-up, provide Azure CLI commands to delete the resource group, in addition to the Azure Portal instructions.
- Where variables are used (e.g., $templateFile), clarify shell syntax differences between PowerShell and Bash.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-resource.md
...ce-manager/templates/template-tutorial-add-resource.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which can be perceived as a Windows-first bias. While Azure CLI is cross-platform and included, there are no explicit Linux/macOS-specific instructions or terminal usage examples. The verification and cleanup steps rely solely on the Azure Portal GUI, which is platform-agnostic but omits command-line alternatives that Linux users may prefer. No Linux-specific tools or shell examples (e.g., Bash scripting, use of environment variables in Bash) are provided.
Recommendations
- Present Azure CLI instructions before PowerShell, or at least in parallel, to avoid a Windows-first impression.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example terminal commands using Bash syntax (e.g., export, $HOME).
- Include instructions for verifying deployment and cleaning up resources using Azure CLI commands, not just the Azure Portal.
- Where variables are referenced (e.g., $templateFile), show both PowerShell and Bash syntax for setting them.
- Consider adding a short section or callout for Linux/macOS users, highlighting any differences or tips.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/test-toolkit.md
...icles/azure-resource-manager/templates/test-toolkit.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily PowerShell-centric, as the ARM template test toolkit is implemented as a set of PowerShell scripts. All usage examples, regardless of platform, require PowerShell (pwsh) to be installed and used. Windows instructions are presented first, and the Linux and macOS sections are nearly identical but still rely on PowerShell rather than native shell scripting. There are no examples or guidance for running the toolkit with native Linux tools (e.g., Bash, Python), and the documentation does not discuss Linux-specific patterns or troubleshooting beyond PowerShell. This creates a Windows/PowerShell bias, even though cross-platform PowerShell is available.
Recommendations
- Clearly state early in the documentation that the toolkit is PowerShell-based and required on all platforms.
- Provide native Linux (Bash) and macOS (zsh/bash) alternatives if possible, or explicitly note that only PowerShell is supported.
- If feasible, offer or link to a wrapper script or Docker container for Linux users who may not want to install PowerShell.
- Add troubleshooting tips for common Linux/macOS PowerShell issues (e.g., permissions, execution policy differences).
- Consider developing and documenting a cross-platform CLI or containerized version of the toolkit that does not require PowerShell.
- Reorder sections or provide a platform-neutral overview before diving into Windows-specific instructions.
- Highlight any Linux/macOS-specific dependencies (e.g., coreutils on macOS) in a dedicated prerequisites section.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deployment-script.md
...nager/templates/template-tutorial-deployment-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong bias towards Windows and PowerShell. All deployment script examples use PowerShell exclusively, with no Bash or cross-platform scripting alternatives. The 'deploymentScripts' resource is shown only with 'AzurePowerShell' kind, and the script content is PowerShell-only. Even in the deployment steps, PowerShell is presented alongside CLI, but the core scripting and troubleshooting are PowerShell-centric. There is no mention or example of using Bash or other Linux-native tools for the deployment script, and PowerShell-specific patterns and escape rules are discussed in detail. This limits accessibility and parity for Linux users.
Recommendations
- Provide equivalent examples using 'AzureCLI' as the 'kind' for the 'deploymentScripts' resource, with Bash script content.
- Include Bash script examples for creating and adding certificates to Key Vault, demonstrating cross-platform compatibility.
- Discuss Bash/Linux-specific troubleshooting steps and file locations in the debugging section.
- Present CLI/Bash examples before or alongside PowerShell, not after or as an alternative.
- Clarify in the prerequisites and throughout the tutorial that both PowerShell and Bash/CLI are supported, and link to relevant documentation for both.
- Add notes about any limitations or differences between PowerShell and Bash deployment scripts in ARM templates.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
...r/templates/template-tutorial-create-first-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (e.g., PowerShell, Visual Studio Code, Windows file dialogs) are mentioned or shown first in most sections. PowerShell examples are consistently presented before Azure CLI (Bash) examples, and the instructions for file creation and navigation assume a Windows GUI workflow. While Azure CLI (with Bash) is supported and Linux installation is mentioned, there are no explicit Linux-native editor or terminal workflow examples, and the CLI instructions are written for Bash but lack parity in terms of Linux file management or editor usage.
Recommendations
- Present Azure CLI (Bash) examples before PowerShell, or at least alternate their order to avoid implicit prioritization.
- Include Linux-native editor options (e.g., Vim, nano, gedit) and show how to create and save files using terminal-based editors.
- Provide explicit instructions for Linux and macOS users for file creation and navigation, not just Windows GUI steps.
- Add screenshots or descriptions of the workflow on Linux (e.g., using a terminal, different file paths).
- Clarify that Visual Studio Code is cross-platform, and mention how to install and launch it on Linux.
- When referencing installation instructions, link to Linux and macOS options first or equally with Windows.
- Ensure that all PowerShell-specific notes (e.g., line continuation with backticks) are matched with Bash/Linux equivalents.