Azure Resource Manager
504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1281 issues found
Showing 201-225 of 1281 flagged pages
Azure Resource Manager
CI/CD with Azure Pipelines and templates
...e-manager/templates/add-template-to-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. PowerShell scripts are the primary method shown for ARM template deployment, with no mention of Bash, Azure CLI, or Linux-native alternatives. Windows-based tools and patterns (such as Azure PowerShell and AzureFileCopy) are used exclusively or before any Linux equivalents. YAML examples use 'windows-latest' VM images for key tasks, and there are no Linux-specific or cross-platform examples provided.
Recommendations
- Add equivalent examples using Bash scripts and Azure CLI for ARM template deployment.
- Provide YAML samples that use 'ubuntu-latest' or other Linux VM images for all tasks, not just the PowerShell example.
- Mention and demonstrate cross-platform tools like AzCopy CLI and Azure CLI, showing usage on both Windows and Linux agents.
- Include guidance for users working in Linux environments, such as handling file paths, permissions, and shell script integration.
- Balance the order of presentation so that Linux and cross-platform methods are shown alongside or before Windows-specific approaches.
Create Pull Request
Azure Resource Manager
Data types in ARM templates
...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 page exhibits Windows bias by referencing PowerShell as the example command-line tool for ARM template deployment and integer range limitations, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific examples or parity guidance are provided.
Recommendations
- Include examples and notes for Linux environments, such as Azure CLI and Bash, alongside PowerShell.
- When discussing limitations or behaviors (e.g., integer ranges), specify how these apply to both Windows (PowerShell) and Linux (Azure CLI/Bash) tools.
- Present cross-platform guidance in a neutral order, or provide both Windows and Linux examples side-by-side.
- Add explicit references to Linux tools and usage patterns where relevant.
Azure Resource Manager
Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs
...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the main focus is on Azure CLI (which is cross-platform), several examples and instructions explicitly mention Windows-specific shells (CMD, PowerShell) and provide syntax for those before or instead of equivalent Linux/Bash examples. There are references to escaping quotes and array syntax for Windows shells, but Linux/Bash alternatives are either less detailed or mentioned secondarily. No explicit Linux tools or patterns are highlighted, and there is little guidance for Linux users beyond generic Bash usage.
Recommendations
- Ensure all shell-specific examples (e.g., passing arrays, setting variables) are provided for both Windows (CMD/PowerShell) and Linux (Bash) side-by-side, with equal detail.
- Where shell differences are discussed, present Linux/Bash syntax first or equally, not as an afterthought.
- Add explicit notes or sections for Linux users, such as common pitfalls, file path conventions, and troubleshooting tips.
- Include references to Linux-native tools or patterns (e.g., using curl, jq, or bash scripting techniques) where relevant.
- Review examples for any implicit Windows assumptions (e.g., file paths, environment variables) and clarify cross-platform compatibility.
Azure Resource Manager
Best practices for templates
...les/azure-resource-manager/templates/best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows and PowerShell-specific patterns are mentioned before Linux equivalents, particularly in the section about parameter naming conflicts with PowerShell cmdlets. The links for connecting to VMs list Windows methods first and in greater detail, with Linux mentioned last. Windows tools (PowerShell, WinRM) are referenced directly, while Linux equivalents (SSH, cloud-init) are not discussed or linked in comparable depth. There is no explicit Linux example for deployment commands or scripting, and no mention of Linux-specific tooling or shell usage.
Recommendations
- Provide Linux/CLI examples alongside or before Windows/PowerShell examples, especially for deployment commands and parameter conflicts.
- Include references and links to Linux tools and patterns (e.g., SSH, cloud-init) when discussing VM connectivity and scripting.
- Ensure parity in documentation depth for both Windows and Linux, such as describing how parameter naming conflicts are handled in Azure CLI or Bicep.
- Add Linux-specific best practices for template deployment and management, including shell scripting and automation.
- Balance the order of presentation so that Linux and Windows are treated equally, avoiding Windows-first ordering.
Azure Resource Manager
Define multiple instances of an output value
...icles/azure-resource-manager/templates/copy-outputs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page displays a Windows bias by listing Azure PowerShell before Azure CLI when discussing supported versions, referencing PowerShell in the deployment section, and linking only to PowerShell deployment instructions. There are no explicit Linux or Bash examples, nor links to Linux-specific deployment guides.
Recommendations
- List Azure CLI before Azure PowerShell when mentioning supported versions to avoid Windows-first ordering.
- Include links to both Azure CLI and PowerShell deployment guides in the 'Next steps' section.
- Provide explicit examples of deploying ARM templates using Azure CLI (with Bash or shell syntax) alongside PowerShell examples.
- Mention cross-platform compatibility and clarify that both CLI and PowerShell are available on Windows, Linux, and macOS.
- Ensure that all instructions and examples are platform-neutral or provide parity between Windows and Linux tools.
Azure Resource Manager
Create & deploy Visual Studio resource group projects
...r/templates/create-visual-studio-deployment-project.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all examples and workflows assuming the use of Visual Studio on Windows. Deployment scripts and instructions are exclusively provided for PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. There are no Linux or macOS instructions or screenshots, and no guidance for users who might be developing or deploying from non-Windows environments.
Recommendations
- Add equivalent instructions for using Azure Resource Manager templates with cross-platform tools such as Azure CLI and Bash scripts.
- Provide examples and deployment workflows that use Visual Studio Code, which is cross-platform, or other IDEs/editors available on Linux/macOS.
- Include notes or sections for Linux/macOS users, clarifying which steps are Windows-specific and how to achieve similar results on other platforms.
- Offer alternative deployment scripts in Bash or reference the use of Azure CLI for template deployment.
- Clarify that the Visual Studio Resource Group project is only available on Windows, and suggest cross-platform alternatives for ARM template authoring and deployment.
Azure Resource Manager
Tutorial - Deploy a linked template
...nager/templates/deployment-tutorial-linked-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed Azure PowerShell scripts for key tasks (such as uploading templates to storage), presenting PowerShell examples before Azure CLI, and omitting equivalent Linux/macOS shell commands for template upload and resource creation. The Azure CLI is only used for deployment, not for the earlier steps, and there is no mention of Linux tools or workflows for managing templates in storage.
Recommendations
- Provide equivalent Azure CLI examples for all steps, including uploading templates to storage and resource creation, not just deployment.
- Include Bash shell scripts for Linux/macOS users, especially for tasks currently shown only in PowerShell.
- Explicitly mention cross-platform compatibility and note any OS-specific differences (e.g., file paths, command syntax).
- Present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first, to avoid Windows-first ordering.
- Reference Linux tools (such as curl, azcopy, or Bash scripting) for downloading/uploading files to Azure Storage.
Azure Resource Manager
Template deployment what-if
...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 (a Windows-centric tool) is consistently presented first in command sections and examples, with detailed PowerShell output shown. The installation instructions for Azure PowerShell are more prominent and detailed than those for Azure CLI. Example outputs and explanations use PowerShell syntax and conventions, even when Azure CLI equivalents exist. There is a lack of explicit Linux shell (bash/zsh) context, and no mention of Linux-specific considerations or alternative shells/tools.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections to balance visibility.
- Provide example outputs in both PowerShell and Azure CLI formats, especially in sections where output is shown.
- Include notes or sections on running Azure CLI in Linux/macOS environments, such as shell differences, color support, and configuration.
- Add explicit bash/zsh shell script examples where programmatic evaluation is discussed, not just PowerShell variables and loops.
- Ensure installation instructions for Azure CLI are as detailed and prominent as those for Azure PowerShell.
- Avoid using Windows-centric terminology (e.g., PowerShell prompt conventions) as the default; clarify when examples are Windows-specific.
- Mention cross-platform compatibility and any platform-specific caveats for both PowerShell and CLI usage.
Azure Resource Manager
Use deployment scripts in Azure Resource Manager templates
...source-manager/templates/deployment-script-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell examples and references are presented first and most frequently, with detailed inline and external script samples using PowerShell. Windows-specific tools and APIs (such as CommandLineToArgvW and ARMClient in PowerShell mode) are mentioned before or instead of Linux equivalents. There is a lack of parity in example depth and troubleshooting guidance for Bash/Azure CLI scripts, and Linux-specific scripting patterns are underrepresented.
Recommendations
- Provide equal numbers of Azure CLI/Bash examples alongside PowerShell samples, especially for inline and external scripts.
- Present Azure CLI/Bash examples before or alongside PowerShell examples in each section, not after.
- Include troubleshooting and development workflow guidance for Bash scripts, similar to the PowerShell sections.
- Reference Linux-native tools and APIs (e.g., getopt, bash argument parsing) where Windows tools like CommandLineToArgvW are mentioned.
- Add explicit instructions for running and debugging deployment scripts using Azure CLI/Bash in Linux environments, including Cloud Shell.
- Ensure that supporting script examples and sample templates include Bash scripts, not just PowerShell (.ps1) files.
- Highlight the use of Linux containers and scripting environments in parity with Windows/PowerShell references.
Azure Resource Manager
Tutorial - Deploy a local Azure Resource Manager template
...anager/templates/deployment-tutorial-local-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows evidence of Windows bias. Azure PowerShell (primarily a Windows tool) is presented as a first-class option alongside Azure CLI, and installation instructions for the Azure CLI list Windows before Linux and macOS. The editor recommendation is Visual Studio Code, which, while cross-platform, is traditionally associated with Windows. There is no mention of Linux-specific editors or shell environments beyond Bash, and no explicit parity checks for Linux users. The PowerShell examples are given equal prominence to CLI examples, but PowerShell is more commonly used on Windows.
Recommendations
- List Azure CLI installation instructions for Linux before Windows to avoid implicit prioritization.
- Include examples or recommendations for Linux-native editors (e.g., Vim, Nano, Emacs) alongside Visual Studio Code.
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows, and suggest CLI as the default for Linux/macOS users.
- Add explicit notes or tips for Linux users regarding shell compatibility and file path conventions.
- Ensure that all examples are tested and presented in a way that is equally accessible to Linux users, possibly including screenshots or terminal output from Linux environments.
Azure Resource Manager
Key Vault secret with template
...zure-resource-manager/templates/key-vault-parameter.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI throughout, and Windows-specific terminology and tools (such as PowerShell cmdlets) are used extensively. References to Windows scenarios (e.g., VM certificate installation) are given priority, and there is no mention of Linux-specific patterns, shell environments, or cross-platform scripting considerations. All command-line examples are either Azure CLI (cross-platform) or PowerShell (Windows-centric), with no Bash or Linux shell examples. The documentation assumes familiarity with Windows tools and does not address Linux user workflows.
Recommendations
- Add Bash/Linux shell examples for all Azure CLI commands to demonstrate usage in native Linux environments.
- Include explicit notes about cross-platform compatibility for Azure CLI and clarify that PowerShell examples are primarily for Windows users.
- Reference Linux-specific scenarios or use cases (e.g., installing certificates on Linux VMs from Key Vault).
- Mention alternative tools or scripting environments (e.g., bash, zsh) where appropriate.
- Ensure that links and quickstart templates cover both Windows and Linux deployment scenarios equally.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows moderate Windows bias. PowerShell is mentioned multiple times (deployment scripts, ARM TTK testing), and the ARM TTK tool is only described as a PowerShell script. Visual Studio and Visual Studio Code are listed as authoring tools, both of which are Windows-centric (though VS Code is cross-platform). In the CI/CD section, Azure DevOps and Visual Studio project pipelines are referenced before any mention of Linux-native alternatives. While Azure CLI and Bash are mentioned, examples and tooling references tend to favor Windows/PowerShell first or exclusively.
Recommendations
- Provide explicit Bash and Azure CLI examples alongside PowerShell for deployment scripts and template testing.
- Mention Linux-native authoring tools (e.g., Vim, Emacs, or VS Code on Linux) and clarify cross-platform support.
- Describe ARM TTK alternatives or usage on Linux (e.g., via PowerShell Core on Linux, or suggest equivalent validation workflows).
- In CI/CD integration, include examples for GitHub Actions, Jenkins, or other Linux-friendly CI/CD systems.
- Ensure that references to tools and workflows do not assume a Windows environment, and order mentions of CLI/Bash and PowerShell equally.
Azure Resource Manager
Create and deploy template spec
...-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 demonstrates a Windows bias in several ways: file paths are exclusively given in Windows format (e.g., C:\Templates\...), with no mention of Linux/macOS equivalents; PowerShell is featured prominently and often listed before Azure CLI; references to tools and tutorials (such as role assignment) are PowerShell-centric; and there are no examples or notes for Linux shell usage, such as Bash or alternative file paths. This may make the documentation less accessible or intuitive for users on Linux or macOS platforms.
Recommendations
- Provide Linux/macOS file path examples (e.g., ~/Templates/createStorageV1.json) alongside Windows paths.
- Include Bash shell examples for variable assignment and command usage, especially in CLI sections.
- Avoid listing PowerShell before CLI or alternate between them to avoid implicit prioritization.
- Reference cross-platform tutorials (e.g., role assignment via CLI) in addition to PowerShell-based guides.
- Add notes or tips for Linux/macOS users regarding file system differences and shell syntax.
- Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific steps.
Azure Resource Manager
Roll back on error to successful deployment
.../azure-resource-manager/templates/rollback-on-error.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents PowerShell examples before Azure CLI, and uses Windows-style file paths (e.g., c:\MyTemplates\azuredeploy.json) in PowerShell examples. The PowerShell section is detailed and uses Windows-centric tooling, which may suggest a bias towards Windows users. There are no Linux-specific CLI examples (e.g., Bash), nor are Linux file path conventions shown.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid Windows-first bias.
- Include Linux-style file paths (e.g., /home/user/templates/azuredeploy.json) in CLI and PowerShell examples where appropriate.
- Add explicit Bash shell examples for Azure CLI usage, demonstrating Linux terminal conventions.
- Clarify that both Windows and Linux are supported platforms for Azure CLI and PowerShell, and provide notes or links for installation and usage on Linux.
- Avoid exclusive use of Windows tools and patterns; mention cross-platform alternatives where possible.
Azure Resource Manager
Deploy ARM template with SAS token - Azure Resource Manager | Microsoft Docs
...ce-manager/templates/secure-template-with-sas-token.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents PowerShell (Windows-centric) examples before Azure CLI, and uses Windows file paths (e.g., c:\Templates\azuredeploy.json) in examples. There is an implicit assumption of a Windows environment, with no explicit mention of Linux/Mac equivalents or considerations. Bash is mentioned only briefly, and Linux-specific details (such as file paths or shell differences) are missing.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid Windows-first bias.
- Include Linux/Mac file path examples (e.g., /home/user/Templates/azuredeploy.json) alongside Windows paths.
- Explicitly mention that Azure CLI commands work on Linux, Mac, and Windows, and provide notes on any syntax differences.
- Add guidance for uploading templates from Linux/Mac environments, including handling of environment variables and file paths.
- Clarify that PowerShell examples are for Windows and provide Bash or shell script equivalents for Linux/Mac users where appropriate.
Azure Resource Manager
Template functions - scope
...resource-manager/templates/template-functions-scope.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where deployment guidance is linked specifically to Azure PowerShell, a Windows-centric tool, without mention of Linux-friendly alternatives like Azure CLI. No Linux-specific examples or deployment instructions are provided, and the only deployment walkthrough referenced is PowerShell-based. The template examples themselves are platform-neutral, but the supporting guidance favors Windows tools and patterns.
Recommendations
- Include links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux.
- In the 'Next steps' section, provide parity by referencing both Azure PowerShell and Azure CLI deployment guides.
- Explicitly state that ARM templates can be deployed from any platform, and provide sample commands for Linux/macOS environments.
- Where PowerShell is mentioned, add equivalent Bash/CLI instructions or links to ensure Linux users are equally supported.
Azure Resource Manager
Deploy a template spec as a linked template
...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 demonstrates a Windows bias by using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., variable assignment in Windows PowerShell). There are no explicit Linux or macOS shell examples, nor guidance for non-Windows environments, and the use of Windows tools and conventions is prevalent.
Recommendations
- Provide Linux/macOS shell examples using bash syntax and POSIX-style file 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.
- Add notes or sections addressing platform-specific differences, such as file path formats and environment setup.
- Reference cross-platform tools and clarify any Windows-specific issues or workarounds for Linux/macOS users.
- Ensure that all instructions and examples are equally accessible and clear for users on Linux, macOS, and Windows.
Azure Resource Manager
Azure Resource Manager template specs
...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 page demonstrates a Windows bias by consistently presenting PowerShell examples before Azure CLI examples, and by exclusively using PowerShell for scripting examples. There are no explicit Linux shell (bash/sh) examples, nor are there instructions for Linux-specific environments or considerations. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not mention Linux-native tools or workflows, nor does it address cross-platform nuances (e.g., file paths, shell differences).
Recommendations
- Add explicit bash/sh examples alongside PowerShell and Azure CLI, especially for scripting and automation tasks.
- Where PowerShell is mentioned, clarify that Azure PowerShell is available cross-platform, but also provide Linux-native alternatives or notes.
- Present Azure CLI examples first or equally, as it is more commonly used in Linux environments.
- Include notes or sections on running commands in Linux/macOS terminals, addressing differences such as file path formats and environment setup.
- Reference Linux-native editors and tools (e.g., vim, nano, code) when discussing template editing or file management.
- Ensure that all instructions and examples are validated to work on both Windows and Linux platforms.
Azure Resource Manager
Develop ARM templates for cloud consistency
...source-manager/templates/template-cloud-consistency.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is frequently used for verification and management examples, often appearing before or instead of Linux/Unix alternatives. Many code samples and artifact references use Windows-centric paths, filenames, and tools (e.g., .ps1 scripts, Windows VM images). There is a lack of explicit Linux-focused examples, such as Bash scripts, Linux VM images, or references to Linux-specific tooling, and Windows terminology (e.g., 'PowerShell DSC', 'WindowsServer') is prevalent throughout.
Recommendations
- Provide Linux/Bash equivalents for all PowerShell commands and scripts, ensuring parity in example coverage.
- Include examples of deploying Linux VM images (e.g., Ubuntu, CentOS) alongside WindowsServer examples.
- Reference and demonstrate Linux VM extensions and configuration scripts (e.g., using shell scripts, cloud-init) in addition to PowerShell DSC.
- Use neutral or dual-platform artifact paths and filenames (e.g., .sh and .ps1 scripts) in template examples.
- Mention cross-platform tools (e.g., Azure CLI, Terraform) before or alongside Windows-specific tools.
- Ensure documentation sections do not default to Windows terminology or examples; present Linux options equally or first where appropriate.
Azure Resource Manager
Convert portal template to template spec
...re-resource-manager/templates/template-spec-convert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based migration instructions and scripts, referencing Windows-centric tooling, and omitting any Linux or cross-platform alternatives. No Bash, Azure CLI, or Linux-native instructions are provided, and PowerShell is presented as the primary (and only) automation method.
Recommendations
- Add equivalent migration instructions using Azure CLI and Bash scripts for Linux and macOS users.
- Explicitly mention cross-platform compatibility for the PowerShell script (e.g., PowerShell Core on Linux/macOS) if applicable, or provide alternatives.
- Provide examples and guidance for performing the migration from Linux environments, including installation and usage notes for required tools.
- Reorder or balance the documentation so that Windows and Linux methods are presented with equal prominence.
- Reference platform-agnostic tools and patterns where possible, such as REST API calls or Azure CLI, rather than Windows-specific utilities.
Azure Resource Manager
Create portal forms for template spec
...anager/templates/template-specs-create-portal-forms.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned first in prerequisites and example commands, and Windows-centric tools (PowerShell cmdlets like Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) are referenced for obtaining required values. While Azure CLI examples are provided, PowerShell is consistently presented before CLI, and instructions for obtaining tenantId and objectId rely solely on PowerShell commands, with no Linux-native or cross-platform alternatives. There is no explicit mention of Linux-specific tools or shell environments, nor are there examples using Bash or other Linux-native utilities.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections to balance platform representation.
- Provide explicit Bash/Linux shell examples for obtaining values such as tenantId and objectId, e.g., using Azure CLI commands like 'az account show' or 'az ad user show'.
- Reference cross-platform editors (e.g., VS Code) and avoid suggesting Windows-only tools for editing files.
- Add notes clarifying that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide installation links for all platforms.
- Where PowerShell cmdlets are mentioned for retrieving information, include equivalent Azure CLI commands and examples.
Azure Resource Manager
Deploy VM extensions with template
...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all examples and instructions focus exclusively on deploying VM extensions to Windows VMs using PowerShell scripts and Windows-specific tools (e.g., Install-WindowsFeature, powershell.exe). The template and script examples are for Windows VMs only, with no mention or examples for Linux VMs, Bash scripts, or Linux extensions. Windows terminology and tools are presented first and exclusively throughout the tutorial.
Recommendations
- Add parallel examples for deploying extensions to Linux VMs, including ARM template snippets for Linux Custom Script Extension.
- Provide Bash script examples and show how to execute them via the Linux extension.
- Reference and link to Linux VM extension documentation (e.g., /azure/virtual-machines/extensions/features-linux).
- Include instructions for opening relevant ports and retrieving IP addresses using Linux tools and Azure CLI.
- Clarify in the introduction that the tutorial is Windows-specific, or broaden the scope to cover both platforms.
- Ensure that both Windows and Linux scenarios are covered equally in future tutorials.
Azure Resource Manager
Tutorial - Create and deploy template
...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 page exhibits a moderate Windows bias. Windows tools and patterns (PowerShell, Windows CLI installation) are mentioned first or exclusively in several sections. PowerShell is given equal or slightly more prominence than Azure CLI, and CLI examples are written for Bash but with notes about adapting for Windows. Installation instructions for Azure CLI list Windows before Linux and macOS. There are no explicit Linux shell screenshots, and the workflow assumes familiarity with Windows conventions (e.g., Visual Studio Code, file paths).
Recommendations
- Present installation instructions for Azure CLI in a neutral order (e.g., Linux, macOS, Windows) or group them together.
- Include explicit Linux shell screenshots and examples, not just Bash CLI commands.
- Add notes or examples for Linux-specific file path conventions and shell environments.
- Ensure parity between PowerShell and CLI examples, and clarify that CLI works on all platforms (not just Bash/Windows).
- Mention alternative editors (e.g., Vim, nano) for Linux users alongside Visual Studio Code.
- Avoid language that assumes Windows as the default environment (e.g., 'workstation', 'File menu').
Azure Resource Manager
Template with dependent resources
...ate-tutorial-create-templates-with-dependent-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using a Windows VM template for the example, referencing RDP (a Windows-specific remote access protocol), and not providing a Linux VM equivalent or mentioning SSH. The deployment section presents both Azure CLI (cross-platform) and PowerShell examples, but the overall tutorial is centered around Windows resources and workflows, with no Linux alternatives or parity in examples.
Recommendations
- Include a parallel example using a Linux VM template, such as 'Deploy a simple Linux VM', and provide the corresponding template URL.
- Mention SSH as the recommended remote access method for Linux VMs, and provide instructions for verifying Linux VM deployment using SSH.
- Balance the documentation by alternating or combining Windows and Linux resource examples, ensuring both are equally represented.
- Explicitly state that the tutorial applies to both Windows and Linux VMs, and provide links to both types of Quickstart templates.
- In the clean-up and verification steps, include instructions relevant to Linux VMs (e.g., SSH login, Linux-specific resource checks).
Azure Resource Manager
Use condition in templates
...-manager/templates/template-tutorial-use-conditions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using a Windows VM template for the example, providing only PowerShell deployment scripts, and referencing Windows-centric tools and patterns. There are no equivalent Linux VM examples or Azure CLI/Bash deployment instructions, and the template used is specifically for Windows VMs, with no mention of Linux alternatives.
Recommendations
- Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and show how the condition parameter works in that context.
- Provide Azure CLI/Bash deployment instructions alongside PowerShell scripts, ensuring both Windows and Linux users can follow the tutorial.
- Reference both Windows and Linux Quickstart templates in the 'Open a Quickstart template' section.
- Clarify tool usage in the prerequisites, explicitly stating that both PowerShell and Bash are supported, and provide example commands for each.
- Ensure screenshots and instructions are not Windows-specific (e.g., show VS Code usage on both platforms, or use generic instructions).