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 551-575 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-outputs.md ...icles/azure-resource-manager/templates/copy-outputs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI when discussing supported versions for zero-count copy loops, and by featuring a 'Next steps' link that exclusively points to a PowerShell deployment guide. There are no Linux-specific deployment examples or references to Bash, shell scripting, or Linux tools. The page does mention Azure CLI, but PowerShell is consistently listed first and is the only deployment method highlighted in the 'Next steps' section.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning supported tools, or alternate their order to avoid perceived prioritization.
  • Add links to Linux-focused deployment guides, such as 'Deploy resources with ARM templates and Azure CLI' or Bash scripting equivalents, in the 'Next steps' section.
  • Include example commands for both Azure PowerShell and Azure CLI when discussing deployment, ensuring parity for Linux users.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
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 examples and explanations, with output samples shown in PowerShell format. The installation instructions and command syntax for PowerShell are more detailed than for Azure CLI. Output screenshots and text samples use PowerShell conventions, and confirmation prompts are shown in PowerShell style. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as using Bash scripting or Linux terminal conventions).
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is sometimes presented first, or present both side-by-side.
  • Include explicit Bash/Linux shell examples and output, especially for Azure CLI commands.
  • Show output samples in both PowerShell and CLI formats, or use CLI as the default for cross-platform parity.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add notes or sections for Linux/macOS users, such as how to install Azure CLI on those platforms.
  • Avoid using only PowerShell-style confirmation prompts; show CLI equivalents.
  • Where possible, use generic terminology (e.g., 'terminal' instead of 'PowerShell window') and avoid Windows-specific language.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-tutorial-local-template.md ...anager/templates/deployment-tutorial-local-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (Azure PowerShell) are mentioned first and more prominently throughout, and installation instructions for the Azure CLI list Windows before Linux and macOS. PowerShell examples are given equal prominence to CLI, but PowerShell is a Windows-centric tool. The editor recommendation (Visual Studio Code) is cross-platform, but no mention is made of Linux-native editors. The Azure CLI examples are written for Bash, which is good for Linux parity, but there are no explicit Linux-specific tips or troubleshooting notes.
Recommendations
  • Alternate the order of tool presentation (sometimes CLI first, sometimes PowerShell) to avoid Windows-first bias.
  • Add explicit notes or troubleshooting tips for Linux users (e.g., file permissions, path formats, shell differences).
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Clarify that Azure PowerShell is available on Linux and macOS, or provide links to cross-platform installation instructions.
  • Ensure that all examples work as written on Linux, and call out any platform-specific differences.
  • Consider including a section or callout for Linux users, highlighting best practices or common issues.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-script-template.md ...source-manager/templates/deployment-script-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in examples and explanations, with more detailed coverage and sample code than Azure CLI/bash. Many code samples, especially for inline and external scripts, use PowerShell exclusively or primarily, while Linux/bash examples are less frequent and less detailed. Windows-specific tools and APIs (e.g., CommandLineToArgvW, ARMClient in PowerShell mode) are referenced without Linux equivalents. Some sections (e.g., error handling, script output, troubleshooting) focus on PowerShell patterns and commands, with limited or no coverage of Linux/bash alternatives. There is a lack of parity in example depth and troubleshooting guidance for Linux/bash users.
Recommendations
  • Provide Linux/bash examples alongside PowerShell for all sample templates, including inline and external scripts.
  • Present Azure CLI/bash and PowerShell examples in parallel, rather than listing PowerShell first or exclusively.
  • Include troubleshooting and error handling guidance for bash scripts, similar to the PowerShell sections.
  • Reference Linux-native tools and APIs where appropriate (e.g., mention how argument parsing works in bash, alternatives to CommandLineToArgvW).
  • Expand the 'Develop deployment scripts' section to cover bash scripting best practices and error management.
  • Ensure that all management instructions (portal, CLI, REST) include both PowerShell and Azure CLI commands with equal detail.
  • Add links to Linux-specific resources and documentation for users developing on non-Windows platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and file paths in examples use Windows-style (e.g., c:\Templates\azuredeploy.json). There is no explicit mention of Linux or cross-platform considerations, and the CLI examples assume Bash but do not provide parity for other shells or platforms. The documentation also references PowerShell-focused next steps and does not provide guidance for Linux-specific workflows or tools.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows.
  • Use platform-neutral file paths in examples (e.g., ./Templates/azuredeploy.json) or provide both Windows and Linux path formats.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide notes for shell differences (e.g., Bash vs. PowerShell).
  • Add guidance or links for deploying ARM templates from Linux environments, including common patterns and troubleshooting tips.
  • Balance 'Next steps' links to include both PowerShell and CLI documentation, or provide a cross-platform introduction.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-cloud-consistency.md ...source-manager/templates/template-cloud-consistency.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is consistently presented as the primary scripting example, often before or in addition to Azure CLI. Examples of VM images and scripts use Windows-centric publishers, offers, and file types (e.g., .ps1 PowerShell scripts, MicrosoftWindowsServer images). There are no Linux-specific examples, such as Bash scripts, Linux VM images, or Linux VM extensions. Windows tools and patterns (PowerShell DSC, CustomScriptExtension for Windows, .ps1 scripts) are referenced exclusively or before their Linux equivalents.
Recommendations
  • Provide Linux/Bash equivalents for all PowerShell script examples, especially for verifying template functions and resource providers.
  • Include examples using Linux VM images (e.g., Ubuntu, CentOS) alongside WindowsServer in ARM template snippets.
  • Show how to use CustomScriptExtension for Linux, referencing .sh scripts, and demonstrate parameterization for Linux artifacts.
  • List and demonstrate Linux VM extensions and their availability in Azure Stack, not just Windows extensions.
  • Balance the order of CLI and PowerShell examples, or present CLI first for cross-platform parity.
  • Reference Linux-friendly tools and workflows (e.g., VS Code on Linux, Bash automation) in testing and automation sections.
  • Avoid defaulting artifact locations and examples to Windows-centric repositories; provide parallel Linux-focused samples.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by consistently using Windows-style paths (e.g., c:\Templates\...), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., known issue with Windows PowerShell). There are no Linux/macOS-specific instructions, examples, or notes, and all file paths and tooling references assume a Windows environment.
Recommendations
  • Provide Linux/macOS equivalent file paths in examples (e.g., /home/user/Templates/deployTS/azuredeploy.json).
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit prioritization.
  • Explicitly mention cross-platform compatibility for Azure CLI and PowerShell, and note any OS-specific issues for both Windows and Linux/macOS.
  • Add troubleshooting notes for Linux/macOS environments where relevant.
  • Use environment-agnostic variables for file paths in code samples (e.g., <template-path>) and clarify usage for different operating systems.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
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 referenced is for a Windows VM, and there are no equivalent examples or guidance for Linux VMs, such as using Bash scripts, Linux extensions, or Linux-specific configuration steps. Windows tools and patterns are mentioned first and exclusively throughout the tutorial.
Recommendations
  • Add parallel examples for deploying VM extensions to Linux VMs, including using Bash scripts and Linux-specific extensions (e.g., CustomScript for Linux).
  • Reference and link to Azure Quickstart Templates for Linux VMs alongside Windows examples.
  • Provide sample ARM template snippets for Linux VM extensions, showing how to execute Bash scripts.
  • Include instructions for retrieving the public IP address and accessing the web server on Linux VMs using Azure CLI or Bash.
  • Mention Linux tools (e.g., apt, yum, systemctl) where appropriate, and provide parity in the explanation of extension usage.
  • Ensure that both Windows and Linux scenarios are covered in prerequisites, deployment, and clean-up steps.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-functions-scope.md ...resource-manager/templates/template-functions-scope.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides examples and references for ARM template scope functions, but in the 'Next steps' section, it only links to instructions for deploying templates using Azure PowerShell, which is primarily a Windows tool. There are no references to Linux-native tools (such as Azure CLI or Bash), nor are there examples showing deployment from Linux environments. This suggests a bias toward Windows and PowerShell, both in tool recommendation and in omission of Linux alternatives.
Recommendations
  • Include links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • In the 'Next steps' section, add parallel instructions for Bash and/or Azure CLI alongside PowerShell.
  • Explicitly mention that ARM templates can be deployed from any OS, and provide guidance for Linux users.
  • Review other documentation pages linked from this one to ensure Linux parity in deployment instructions and examples.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by using Windows-style file paths (e.g., c:\Templates\...), presenting PowerShell examples and terminology before Azure CLI, and referencing Windows-specific issues. There are no explicit Linux/macOS file path examples, nor guidance for Linux users on directory creation or template file management. The documentation assumes a Windows environment for local file operations and scripting.
Recommendations
  • Include Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/linkedTS/azuredeploy.json).
  • Provide instructions for creating directories and saving files using Linux/macOS commands (e.g., mkdir, touch, nano/vim).
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid Windows-first bias.
  • Add notes or troubleshooting tips relevant to Linux/macOS users, especially where command syntax or environment behavior may differ.
  • Explicitly state that the instructions apply to both Windows and Linux/macOS, and clarify any platform-specific differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-export-template.md ...manager/templates/template-tutorial-export-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is mentioned before Azure CLI in prerequisites and deployment instructions, and PowerShell examples are presented before CLI equivalents. There is no mention of Linux-specific shell usage (e.g., bash), nor are there examples tailored for Linux environments (such as using bash variables or command-line patterns). The instructions for installing tools and running commands do not address Linux-specific nuances, and the cleanup steps rely solely on the Azure portal UI, which is platform-agnostic but omits CLI-based alternatives that would benefit Linux users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention Linux shell usage (e.g., bash) and provide example commands using bash syntax and environment variables.
  • Include instructions for installing Azure CLI on Linux, and reference Linux-specific documentation where appropriate.
  • Add cleanup instructions using Azure CLI commands (e.g., 'az group delete') to provide parity for users who prefer command-line operations.
  • Review and update prerequisite sections to clarify cross-platform compatibility and highlight Linux support.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-create-portal-forms.md ...anager/templates/template-specs-create-portal-forms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets for obtaining required values (such as tenantId and objectId) and providing PowerShell examples before Azure CLI equivalents. It also mentions Visual Studio Code as the editor, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell (bash) examples or instructions for obtaining values using Linux-native tools, and the guidance for prerequisites and commands leans toward Windows-centric tooling.
Recommendations
  • Provide Linux/bash equivalents for obtaining tenantId and objectId, such as using Azure CLI commands (e.g., az account show, az ad user show) alongside PowerShell.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, not after.
  • Mention cross-platform editors (such as nano, vim) in addition to Visual Studio Code, or clarify that VS Code is available on Linux and macOS.
  • Add explicit notes or examples for Linux/macOS users, including file path conventions and shell usage.
  • Where PowerShell cmdlets are referenced for prerequisite information, include equivalent Azure CLI commands and links.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-not-found.md ...re-resource-manager/troubleshooting/error-not-found.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Azure CLI together, but mentioning PowerShell first and providing a direct link to the Set-AzContext PowerShell cmdlet. There are no examples or instructions for Linux-specific shell usage (e.g., Bash), nor are there references to Linux-native tools or patterns. The guidance for changing subscriptions and context is Windows/PowerShell-centric, and no Linux terminal screenshots or commands are provided. All portal instructions are platform-neutral, but command-line guidance is Windows-first.
Recommendations
  • Provide Bash-specific examples for Azure CLI commands, including context switching and resource management.
  • Mention Linux and macOS platforms explicitly when discussing Azure CLI usage, and clarify any differences in command syntax or environment setup.
  • Add screenshots or terminal output examples from Linux shells to balance the visual representation.
  • Ensure that references to PowerShell and Azure CLI are presented in a platform-neutral order, or alternate which is listed first.
  • Include troubleshooting steps or notes relevant to Linux users, such as environment variables, shell profiles, or authentication differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/enable-debug-logging.md ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell for enabling debug logging, with explicit statements that debug logging cannot be enabled via Azure CLI (the cross-platform tool). All enabling examples use PowerShell cmdlets, which are traditionally Windows-centric, and there are no Linux-specific instructions or alternative methods for enabling debug logging. The documentation does not mention or provide parity for Linux-native tools or workflows, and PowerShell is presented first and in more detail throughout the page.
Recommendations
  • Investigate and document any method to enable debug logging using Azure CLI or other cross-platform tools, or clarify if this is a platform limitation.
  • If enabling debug logging is only possible via PowerShell, explicitly state this is a limitation and suggest workarounds for Linux users (e.g., using PowerShell Core on Linux, or providing containerized PowerShell instructions).
  • Provide guidance or examples for running Azure PowerShell on Linux (e.g., installation steps for PowerShell Core, usage in Bash or zsh shells).
  • Consider reordering sections to present Azure CLI and PowerShell equally, or clarify platform dependencies up front.
  • Add notes or links to cross-platform PowerShell installation and usage guides for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md ...ate-tutorial-create-templates-with-dependent-resources.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively using a Windows VM template for the example, referencing RDP (a Windows-specific protocol) for verification, and omitting any Linux VM template or SSH instructions. The deployment example is based on a Windows VM, and there is no mention of Linux equivalents or parity in the walkthrough. While both PowerShell and Bash/CLI deployment options are shown, the resource being deployed is Windows-only, and post-deployment verification is Windows-centric.
Recommendations
  • Include a parallel example using a Linux VM template, such as 'Deploy a simple Linux VM', and provide the relevant template URL.
  • Add instructions for verifying Linux VM deployment, such as using SSH to connect to the VM, alongside the RDP instructions for Windows.
  • Mention both Windows and Linux VM options in the 'Open a Quickstart template' section, allowing users to choose based on their needs.
  • Ensure post-deployment steps cover both RDP (Windows) and SSH (Linux) scenarios.
  • Consider referencing cross-platform tools and patterns equally, and avoid defaulting to Windows-centric resources.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/deployment-quota-exceeded.md ...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, despite PowerShell being primarily a Windows tool (though it is available cross-platform). The Bash scripting example in the Azure CLI section is helpful for Linux users, but there is no explicit mention of Linux environments or alternatives to PowerShell for non-Windows users. The documentation does not clarify that PowerShell commands may require additional setup on Linux/macOS, nor does it provide guidance for native Linux shell users beyond the Bash example.
Recommendations
  • Explicitly mention that PowerShell examples are primarily for Windows users, and note cross-platform availability if relevant.
  • Provide clear guidance for Linux/macOS users, including prerequisites for running PowerShell on those platforms.
  • Offer equivalent examples using native Linux tools (e.g., Bash, zsh) wherever possible.
  • Add a note or section clarifying environment requirements for each example (e.g., 'This Bash example works on Linux/macOS; PowerShell is available on Windows by default, and on Linux/macOS with installation').
  • Consider listing Linux/Bash examples before PowerShell to avoid implicit Windows-first bias.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-template-reference.md .../templates/template-tutorial-use-template-reference.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates some Windows bias. Visual Studio Code is listed as the only prerequisite editor, with no mention of Linux-native alternatives. File operations are described using GUI steps (File > Open File), which are more familiar to Windows users. In deployment instructions, both PowerShell and Azure CLI examples are provided, but PowerShell is mentioned first and in more detail. There is no mention of Linux-specific tools, editors, or workflows, and the tutorial does not provide command-line file handling examples (e.g., using vim, nano, or curl/wget to fetch the template).
Recommendations
  • Add Linux-native editor options (e.g., vim, nano, gedit) in the prerequisites section.
  • Include command-line instructions for downloading and opening the template file (e.g., using curl or wget).
  • Provide file operation steps for Linux (e.g., using cp, mv, or command-line editors) alongside GUI instructions.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid Windows-first perception.
  • Explicitly mention that the tutorial is cross-platform and highlight any differences in workflow between Windows and Linux.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell on all platforms (Windows, Linux, macOS) to use the ARM template test toolkit. Windows installation instructions are presented first, and all usage examples (including CI/CD pipeline integration) rely exclusively on PowerShell commands and modules. There is no mention of native Linux shell alternatives, nor are there Bash or other Linux-native scripting examples. The toolkit itself is described as a set of PowerShell scripts, which inherently favors Windows environments and workflows.
Recommendations
  • Provide Bash or shell script examples for Linux users, where possible, or clarify if PowerShell is the only supported method.
  • Explicitly state that the toolkit is PowerShell-only and discuss any limitations or alternatives for users who prefer native Linux tools.
  • Consider developing or recommending cross-platform wrappers or CLI tools that do not require PowerShell, to improve accessibility for Linux users.
  • Reorder installation instructions to present Linux and macOS before Windows, or present all platforms in parallel to avoid Windows-first bias.
  • Add troubleshooting and environment setup guidance specific to Linux (e.g., common issues with PowerShell on Linux, permissions, dependencies).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-sku-not-available.md ...rce-manager/troubleshooting/error-sku-not-available.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal or greater prominence compared to Azure CLI, and Windows-centric tools and patterns (PowerShell scripting, Windows path notation) are used in examples. The REST example uses a Windows-style path ('.\sku-list.json') for output, and PowerShell is featured with detailed scripts, while Linux shell scripting or Bash alternatives are not provided. There is no explicit Linux example or mention of Linux-specific tooling, and Windows/PowerShell commands are often presented before or alongside CLI commands, rather than after or as alternatives.
Recommendations
  • Add Bash/Linux shell script examples for filtering and processing Azure CLI output, especially where PowerShell scripts are provided.
  • Use platform-neutral path notation (e.g., './sku-list.json') in CLI examples to avoid Windows bias.
  • Explicitly mention that Azure CLI commands work cross-platform and provide sample usage in Bash or other Linux shells.
  • Where PowerShell scripts are shown, offer equivalent Bash/awk/jq pipelines for Linux users.
  • Ensure that CLI examples are presented before or alongside PowerShell examples, and clarify platform compatibility for each command.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-conditions.md ...-manager/templates/template-tutorial-use-conditions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively referencing a Windows VM template, providing only PowerShell deployment scripts, and omitting equivalent Linux VM or Azure CLI examples. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
  • Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and reference it alongside the Windows VM template.
  • Provide Azure CLI deployment instructions and scripts in addition to PowerShell, ensuring both are equally detailed.
  • Explicitly mention Linux-compatible tools and workflows, such as Bash scripting, and demonstrate their use in the deployment and cleanup steps.
  • Ensure that screenshots and walkthroughs do not assume a Windows environment (e.g., file paths, shell commands, UI terminology).
  • Add notes or sections highlighting differences or considerations for Linux users where relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/common-deployment-errors.md ...ce-manager/troubleshooting/common-deployment-errors.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In several instances, Windows-specific tools (PowerShell) and links are mentioned before or alongside their Linux equivalents, and sometimes Windows examples or references appear first. For example, in the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are referenced, but PowerShell is listed second. In 'AllocationFailed', troubleshooting links for Linux and Windows are provided, with Linux listed first, which is positive. However, in 'SubnetsNotInSameVnet', the Windows VM link is listed before the Linux VM link. There is also a general tendency to mention PowerShell as a management tool, which is more common on Windows, and no explicit Bash or Linux shell examples are given.
Recommendations
  • Ensure that Linux and Windows troubleshooting links are presented in parallel, and alternate which is listed first to avoid implicit prioritization.
  • Where management tools are referenced (e.g., PowerShell), also provide equivalent Linux/Bash/CLI commands or links, and clarify cross-platform usage.
  • Add explicit Linux/Bash examples where only PowerShell or Windows tools are mentioned.
  • Review all error mitigation steps to ensure Linux parity in tooling and examples, and avoid assuming PowerShell as the default management tool.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md ...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting steps for Bicep deployments using both Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool. Examples for both are given, but there is no mention of Linux-specific shell environments (e.g., Bash), nor are there any Linux-specific troubleshooting steps, file paths, or considerations. The documentation assumes Visual Studio Code as the editor, which is cross-platform, but does not discuss any Linux-specific setup or alternatives. The order of examples sometimes lists Azure CLI first, which is cross-platform, but the heavy inclusion of PowerShell and lack of Linux shell examples indicate a Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for command-line operations.
  • Include notes or troubleshooting steps relevant to Linux environments (e.g., file permissions, path formats).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any platform-specific caveats.
  • Mention Linux package managers (apt, yum, etc.) for installing Azure CLI.
  • Consider including screenshots or instructions for Linux desktop environments where relevant.
GitHub Create Pull Request
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 →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples throughout, but the PowerShell examples are prominent and sometimes more detailed (e.g., handling secure strings). The PowerShell examples use Windows-specific cmdlets and patterns, and the documentation references Windows scenarios (such as installing a certificate on a Windows VM) before mentioning general or cross-platform scenarios. There is no mention of Linux-specific tools, shell scripting, or guidance for Linux users, and the PowerShell examples assume a Windows environment.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Add Bash shell scripting examples alongside PowerShell, especially for parameter file creation and deployment steps.
  • When referencing VM scenarios, provide both Windows and Linux quickstart links or examples.
  • Clarify that PowerShell Core is available cross-platform, but provide Bash alternatives for Linux users.
  • Ensure that any advanced scripting (such as secure string handling) has a Linux/Bash equivalent.
  • Review and balance the order of examples so that Azure CLI (cross-platform) is presented first, or alternate the order to avoid implicit Windows-first bias.
GitHub Create Pull Request
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 →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation is heavily PowerShell-centric, reflecting the fact that the ARM template test toolkit is implemented as a set of PowerShell scripts. All usage examples, including those for Linux and macOS, require PowerShell (pwsh) and do not provide alternatives using native Linux/Unix shell tools or scripting languages. The Windows installation instructions are presented before Linux and macOS, and the overall workflow assumes familiarity with PowerShell commands and concepts (e.g., execution policy, Import-Module). There is no mention of using the toolkit outside PowerShell, nor are there any Bash, Python, or other cross-platform scripting examples.
Recommendations
  • Clearly state at the beginning that the toolkit is PowerShell-based and required on all platforms.
  • Consider providing or linking to wrapper scripts or Docker containers that allow running the toolkit without requiring users to install PowerShell, especially for Linux users.
  • If possible, develop and document alternative usage patterns or tools for Linux users who may not be familiar with PowerShell (e.g., Bash scripts that invoke PowerShell, or a CLI wrapper).
  • Present Linux and macOS instructions before or alongside Windows instructions to avoid the impression of Windows primacy.
  • Explicitly acknowledge the PowerShell dependency as a limitation for some Linux environments and suggest workarounds or community solutions.
  • Where possible, provide example commands in both Windows and Linux/macOS path formats and shell conventions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-what-if.md ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell (a Windows-centric tool) examples alongside Azure CLI, often listing PowerShell before CLI in explanations and code samples. There is a strong focus on PowerShell-specific switches, parameters, and output handling, with detailed PowerShell scripting shown. No explicit Linux shell (bash) or cross-platform scripting examples are provided beyond Azure CLI, and PowerShell is treated as a primary interface. The documentation assumes familiarity with PowerShell cmdlets and patterns, which may disadvantage Linux/macOS users who do not use PowerShell.
Recommendations
  • Ensure Azure CLI examples are always presented first, as it is natively cross-platform and more familiar to Linux/macOS users.
  • Where PowerShell scripting is shown, provide equivalent bash scripting examples for common tasks (e.g., looping over results, variable assignment).
  • Clarify that PowerShell Core is available cross-platform, but also provide bash/zsh examples for Linux/macOS users.
  • Avoid using Windows-specific terminology (e.g., 'module', 'cmdlet') without explanation or Linux equivalents.
  • Explicitly mention that all Azure CLI commands work identically on Linux, macOS, and Windows, and highlight any OS-specific considerations.
  • Add a section or callout for Linux/macOS users, linking to relevant shell scripting resources or Azure CLI documentation.
GitHub Create Pull Request
← Previous Page 23 of 52 Next →