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 276-300 of 1281 flagged pages
Azure Resource Manager Create and deploy a deployment stack with Bicep ...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, which supports cross-platform usage. However, there is a noticeable Windows bias: PowerShell is featured as a primary automation tool (which is native to Windows), and references to Visual Studio Code (a cross-platform editor but historically Windows-centric) are prominent. The prerequisites list Azure PowerShell before Azure CLI, and PowerShell examples are given equal prominence to CLI, despite CLI being more universally available on Linux/macOS. No Linux shell-specific guidance (e.g., bash, zsh) or notes about platform differences are provided. There are no explicit Linux-only examples or troubleshooting tips for non-Windows environments.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is most common on Windows but also available cross-platform.
  • Add notes or links for installing and using Azure CLI on Linux/macOS, including shell integration (bash, zsh, etc.).
  • Consider providing bash script examples or highlighting differences in command syntax/usage between Windows (PowerShell) and Linux/macOS (bash).
  • Explicitly mention that Visual Studio Code and the Bicep extension are available on Linux/macOS, and provide installation instructions for those platforms.
  • Where possible, use Azure CLI as the default/first example, as it is more universally available across platforms.
  • Add troubleshooting or FAQ sections for common issues encountered on Linux/macOS (e.g., file permissions, path formats).
GitHub Create Pull Request
Azure Resource Manager Bicep spread operator ...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where Azure PowerShell and Visual Studio Code are mentioned as the main tools for deploying and authoring Bicep files. Azure CLI is mentioned, but Azure PowerShell is listed first, and there is no mention of Linux-native editors or deployment workflows (e.g., Bash, Vim, or VS Code on Linux). The examples themselves are platform-neutral, but the guidance for running and authoring Bicep files is Windows-centric.
Recommendations
  • Explicitly mention Linux and macOS compatibility for Azure CLI and VS Code.
  • Provide example deployment commands using Bash or shell scripts, not just PowerShell.
  • Include references to Linux-native editors (e.g., Vim, nano) and workflows for authoring Bicep files.
  • Clarify that Azure CLI works cross-platform and provide links to Linux installation guides.
  • Avoid listing Windows tools (PowerShell, VS Code) before their cross-platform or Linux equivalents.
GitHub Create Pull Request
Azure Resource Manager Publish modules to private module registry ...ce-manager/bicep/quickstart-private-module-registry.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples and instructions exclusively for Azure CLI and Azure PowerShell, with no mention of Bash, shell scripting, or Linux-native tools. The development environment setup references Visual Studio Code and Visual Studio, both of which are Windows-centric, and does not mention Linux editors or workflows. There are no explicit Linux shell examples or guidance for Linux users, which may make the documentation less accessible for those on non-Windows platforms.
Recommendations
  • Add Bash/shell examples alongside Azure CLI and PowerShell, especially for file operations and scripting.
  • Include instructions for setting up the Bicep CLI and development environment on Linux, referencing popular editors such as Vim, Emacs, or VS Code on Linux.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., environment variables, file paths).
  • Mention Linux package managers (apt, yum, etc.) for installing prerequisites where appropriate.
  • Balance references to Visual Studio/VS Code with alternatives available on Linux, or explicitly state cross-platform compatibility.
GitHub Create Pull Request
Azure Resource Manager Bicep comparison operators ...s/azure-resource-manager/bicep/operators-comparison.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 mentioning Azure PowerShell before Azure CLI when describing how to run examples. There are no explicit Linux-specific instructions or examples, and the guidance for deploying Bicep files references Visual Studio Code, which is cross-platform but often associated with Windows workflows. No Linux shell (bash) examples or instructions are provided, and the page does not clarify parity between Windows and Linux environments for Bicep deployment.
Recommendations
  • Mention Azure CLI before Azure PowerShell, as CLI is cross-platform and preferred on Linux.
  • Explicitly state that all examples can be run on Linux, macOS, and Windows.
  • Provide example commands for deploying Bicep files using bash or zsh shells on Linux.
  • Add a section or note about Linux prerequisites and common tools for Bicep deployment.
  • Ensure that instructions do not assume use of Windows-specific tooling or patterns.
GitHub Create Pull Request
Azure Resource Manager Move guidance for Cloud Services (extended support) deployment model resources ...nt/move-limitations/cloud-services-extended-support.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 describing move operations, and by not providing explicit Linux-oriented examples or guidance. The mention of 'Azure PowerShell' as a primary tool, without balancing it with Linux-native tools or shell examples, may disadvantage Linux users. No Bash or Linux-specific command-line examples are given.
Recommendations
  • Provide explicit Bash/Azure CLI examples for moving resources, including command syntax and usage.
  • List Azure CLI before or alongside Azure PowerShell when describing supported tools, to avoid Windows-first ordering.
  • Mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Include REST API examples with curl for Linux users.
  • Add a note highlighting parity between PowerShell and CLI, and link to relevant Linux documentation.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Backup to another region ...rce-manager/management/relocation/relocation-backup.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates several Windows biases: Windows-specific instructions and tools (e.g., Azure PowerShell, MARS agent) are referenced or exemplified, while Linux equivalents are either omitted or mentioned only briefly. Windows update instructions are explicit, whereas Linux guidance is generic ('refer to distributor guidance'). Screenshots and agent instructions focus on Windows environments. Linux-specific backup agents, commands, or examples are missing, and scripting examples use Azure PowerShell without CLI or Bash alternatives.
Recommendations
  • Provide explicit Linux examples alongside Windows ones, such as using Azure CLI or Bash scripts for backup and relocation tasks.
  • Include Linux-specific instructions for certificate and CRL updates, with references to common distributions (Ubuntu, RHEL, etc.).
  • Add screenshots and walkthroughs for Linux environments where applicable, especially for agent installation and configuration.
  • Mention and link to Linux backup agents (e.g., Azure Backup Server for Linux, or third-party options) where relevant.
  • Ensure scripting examples are cross-platform, offering both PowerShell and CLI/Bash alternatives.
  • Clarify any differences in backup/restore procedures for Linux VMs, including file system and permission considerations.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Automation to another region ...manager/management/relocation/relocation-automation.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and instructions for exporting and importing Azure Automation runbooks. There is no mention of Linux-native tools, CLI commands, or cross-platform alternatives, and PowerShell is referenced as the primary method for automation tasks. The absence of Azure CLI or REST API examples further reinforces the Windows-centric approach.
Recommendations
  • Include Azure CLI examples for exporting and importing runbooks, which are cross-platform and widely used on Linux.
  • Mention REST API options for automation tasks to provide platform-neutral guidance.
  • Add notes or sections describing how Linux users can perform equivalent tasks, such as using Bash scripts or Python SDKs.
  • Ensure that references to PowerShell are balanced with references to CLI or other tools, and avoid presenting Windows tools as the default or only option.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Key Vault to another region ...-manager/management/relocation/relocation-key-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for key operations (exporting and deploying templates), while omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. PowerShell is presented as the primary scripting interface, and references to obtaining region codes are made via PowerShell commands, with no mention of Azure CLI alternatives. The structure of the examples and instructions prioritizes Windows-centric tools and workflows, leaving Linux users without direct guidance.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, including exporting and deploying templates.
  • Include Bash shell command examples where appropriate, especially for template manipulation and file operations.
  • When referencing region codes, provide Azure CLI commands (e.g., 'az account list-locations') alongside PowerShell commands.
  • Ensure that instructions for scripting and automation are platform-neutral, or explicitly provide both Windows (PowerShell) and Linux (CLI/Bash) options in parallel.
  • Review all sections for references to Windows-specific tools and add Linux equivalents, ensuring parity in guidance and examples.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure NSG to another region ...anagement/relocation/relocation-virtual-network-nsg.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for using the Azure Portal and Azure PowerShell to relocate an NSG, but omits equivalent examples for Linux users (e.g., Azure CLI, Bash). All command-line automation is shown using PowerShell, which is primarily a Windows tool, and references to editors (e.g., Notepad) further reinforce a Windows-centric approach. There are no Linux shell or cross-platform CLI instructions, and PowerShell is presented as the only automation option.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, suitable for Bash or other Linux shells.
  • Reference cross-platform text editors (e.g., vim, nano, code) instead of or in addition to Notepad.
  • Include a tab or section for Linux/macOS users, showing how to perform each step using CLI tools available on those platforms.
  • Avoid assuming PowerShell is the default automation tool; mention alternatives and their parity.
  • Ensure all prerequisites and instructions are platform-neutral or provide platform-specific guidance for both Windows and Linux.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a property ...es/azure-resource-manager/templates/copy-properties.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing Windows-specific examples and tools before Linux equivalents. The only linked example template is for deploying a Windows VM with data disks, and deployment instructions focus on Azure PowerShell, with no mention of Linux-specific deployment methods or CLI usage. There are no Linux VM or cross-platform examples, and PowerShell is listed before Azure CLI in the supported tools section.
Recommendations
  • Include example templates for Linux VMs alongside Windows VM examples.
  • Provide deployment instructions using Azure CLI and highlight its cross-platform nature.
  • Ensure that references to tools (PowerShell, CLI, REST API) are ordered neutrally or with CLI first to reflect cross-platform parity.
  • Add links to Linux-specific quickstart templates or documentation.
  • Explicitly mention that ARM templates and Bicep are platform-agnostic and can be used from any OS.
GitHub Create Pull Request
Azure Resource Manager Data types in ARM templates ...rticles/azure-resource-manager/templates/data-types.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references 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. This presents a Windows-first perspective and omits Linux-specific guidance or parity in tooling examples.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell when discussing deployment and parameter limitations.
  • Explicitly mention that SDK or command-line tool limitations may differ across platforms, and provide details for both Windows (PowerShell) and Linux (Azure CLI/Bash).
  • Add a table or section comparing deployment tools and their integer range limitations for both Windows and Linux environments.
  • Ensure future documentation references cross-platform tools equally, avoiding exclusive or primary mention of Windows tools.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a local Azure Resource Manager template ...anager/templates/deployment-tutorial-local-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Azure PowerShell is presented as a primary tool alongside Azure CLI, and installation instructions for Azure CLI list Windows before Linux and macOS. The editor recommendation is Visual Studio Code, a Microsoft product popular on Windows. The tutorial does provide Bash-based CLI examples and mentions Linux installation, but Windows-centric tools and patterns (PowerShell, VS Code) are emphasized or listed first.
Recommendations
  • List installation instructions for Azure CLI in a neutral or alphabetical order (e.g., Linux, macOS, Windows) rather than Windows first.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and clarify which is recommended for Linux users.
  • Include alternative editor suggestions (e.g., Vim, Nano, Sublime Text) for Linux users alongside Visual Studio Code.
  • Add a note or section highlighting Linux-specific considerations, such as file permissions or shell differences, if relevant.
  • Ensure that examples and instructions are equally accessible and tested on Linux, and avoid implying that Windows tools are the default.
GitHub Create Pull Request
Azure Resource Manager Deploy to Azure button ...e-resource-manager/templates/deploy-to-azure-button.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a PowerShell-only example for URL encoding, omitting equivalent Linux/macOS command-line options (such as curl, python, or bash). This prioritizes Windows tooling and patterns, and does not offer parity for users on Linux or macOS platforms. No Linux-specific tools or examples are mentioned anywhere in the page.
Recommendations
  • Add Linux/macOS command-line examples for URL encoding, such as using Python, curl, or bash.
  • Explicitly mention cross-platform alternatives alongside PowerShell, e.g., show both PowerShell and Linux shell commands.
  • Review other sections for implicit Windows-first assumptions and ensure parity in instructions and tooling.
  • Consider a table or callout that lists equivalent commands for Windows, Linux, and macOS where relevant.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a linked template ...nager/templates/deployment-tutorial-linked-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing PowerShell examples first, using Windows-centric tools and patterns, and offering more detailed guidance for PowerShell users. The storage/upload workflow is described only with PowerShell, and the Azure CLI example is presented after the PowerShell example. There is no mention of Linux-specific shell scripting or alternative Linux tools for template management and upload.
Recommendations
  • Provide Bash or shell script examples for uploading templates to Azure Storage, alongside PowerShell.
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention that all steps can be performed on Linux/macOS, and provide notes for platform-specific differences (e.g., file paths, command syntax).
  • Include troubleshooting or tips for Linux users, such as handling file permissions or using curl/wget for downloads.
  • Avoid assuming use of Windows tools (e.g., PowerShell, Write-Host) and offer cross-platform alternatives.
GitHub Create Pull Request
Azure Resource Manager Key Vault secret with template ...zure-resource-manager/templates/key-vault-parameter.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 quickstart link specifically points to a Windows scenario ('vm-winrm-keyvault-windows'), and PowerShell is tracked as a custom property. There is no mention of Linux-specific shell patterns, nor are Bash or Linux-native examples provided. The documentation assumes familiarity with PowerShell and Windows tools, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash examples alongside Azure CLI, especially for secret creation and deployment commands.
  • Include notes or sections highlighting Linux shell usage, such as environment variable handling and file paths.
  • Balance introductory references: link to both Windows and Linux quickstart scenarios.
  • Clarify that Azure CLI works cross-platform and provide guidance for Linux/Mac users on prerequisites and shell syntax.
  • Avoid tracking or referencing only PowerShell in metadata (e.g., ms.custom), and include Bash or Linux shell equivalents.
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault in templates ...e-manager/templates/template-tutorial-use-key-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 strong Windows bias by exclusively using Windows VM templates, providing only PowerShell scripts for resource creation and deployment, and referencing Windows-specific tools and patterns (such as RDP for VM access and Windows password requirements). Linux equivalents (e.g., Linux VM templates, Azure CLI/bash scripts, SSH access) are not mentioned or demonstrated, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add parallel examples for deploying a Linux VM, including references to Linux VM templates and password/SSH key requirements.
  • Provide Azure CLI/bash script equivalents for all PowerShell commands, especially for key vault creation, secret retrieval, and template deployment.
  • Include instructions for connecting to a Linux VM (e.g., using SSH) after deployment, alongside the RDP/Windows instructions.
  • Reference both Windows and Linux password/credential requirements, and link to relevant documentation for each.
  • Ensure that examples and screenshots are balanced between Windows and Linux scenarios, or clearly indicate when instructions are Windows-specific.
GitHub Create Pull Request
Azure Resource Manager Resource quota errors ...source-manager/troubleshooting/error-resource-quota.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Azure resource quota errors and includes command-line examples for both Azure CLI and PowerShell. However, the PowerShell example is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific patterns or tools. The documentation does not clarify that Azure CLI is cross-platform and does not offer Linux-first or Linux-specific guidance.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add explicit Bash shell examples for Linux users, demonstrating how to run Azure CLI commands in a Linux environment.
  • Consider mentioning Linux-native tools or patterns (e.g., using jq for JSON parsing with Azure CLI output).
  • If PowerShell is included, note its availability on Linux and macOS, or provide guidance for installing PowerShell Core on those platforms.
  • Ensure that examples and instructions do not assume a Windows environment by default.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager deployment modes ...s/azure-resource-manager/templates/deployment-modes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 is presented first and in detail for deployment mode examples, with Windows-style file paths (e.g., c:\MyTemplates\storage.json) used in the PowerShell example. The CLI example is provided, but the PowerShell workflow is prioritized and referenced in the 'Next steps' section. There is no mention of Linux-specific considerations, such as Bash scripting, Linux file paths, or shell environments, and no examples tailored for Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid Windows-first bias.
  • Use platform-neutral file paths (e.g., ./MyTemplates/storage.json) in examples, or provide both Windows and Linux path variants.
  • Explicitly mention that Azure CLI works cross-platform and provide Bash shell usage notes where relevant.
  • Add links to Linux-specific deployment guides in the 'Next steps' section.
  • Include a note clarifying that both PowerShell and CLI are available on Windows, Linux, and macOS, and provide installation guidance for non-Windows platforms.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in templates | Microsoft Docs .../templates/deployment-script-template-configure-dev.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 bias toward Windows and PowerShell workflows. PowerShell is used as the primary scripting example for both Azure PowerShell and Azure CLI container scenarios, with all deployment and upload steps shown only in PowerShell. The Docker section uses Windows-style drive letter mapping (e.g., d:/docker), which is specific to Windows environments, and does not provide equivalent Linux or macOS commands or file path examples. There are no Bash or Linux-native upload/deployment examples, and the use of PowerShell cmdlets (e.g., Set-AzStorageFileContent) further reinforces a Windows-centric approach.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all deployment and upload steps, especially for Linux/macOS users.
  • In Docker instructions, include Linux/macOS volume mount syntax (e.g., /home/user/docker:/data) alongside Windows examples.
  • Clarify that PowerShell examples are for Windows users and offer parallel instructions for Linux/macOS environments.
  • Highlight cross-platform compatibility of Azure CLI and PowerShell, and link to installation guides for both on all major OSes.
  • Add notes or sections that address common Linux/macOS patterns, such as using Bash scripts, shell commands, and file system paths.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Azure Resource Manager templates ...source-manager/templates/deployment-script-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by predominantly featuring PowerShell examples, using Windows-centric tools and terminology, and providing step-by-step instructions and sample scripts primarily in PowerShell before mentioning Azure CLI/bash equivalents. References to Windows APIs (e.g., CommandLineToArgvW) and tools (e.g., ARMClient in PowerShell) further reinforce this bias. Linux/bash examples are present but less emphasized, and there are few, if any, direct bash script samples or troubleshooting steps compared to PowerShell.
Recommendations
  • Provide equal numbers of Azure CLI/bash script examples alongside PowerShell samples, including full ARM template snippets and output handling.
  • Ensure that step-by-step instructions (e.g., 'Try it' sections) offer both PowerShell and Azure CLI/bash workflows, with clear guidance for Linux/macOS users.
  • Mention Azure CLI/bash options first or in parallel with PowerShell, especially in introductory and sample sections.
  • Replace or supplement Windows-specific references (e.g., CommandLineToArgvW) with cross-platform alternatives or explanations.
  • Include troubleshooting and resource management examples using Azure CLI/bash, not just PowerShell.
  • Highlight the underlying Linux container environment more explicitly, and clarify any differences or limitations for script execution between PowerShell and bash.
  • Add links to Linux/macOS setup guides for Azure CLI and scripting environments.
GitHub Create Pull Request
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its credential precedence and authentication examples. Azure PowerShell is mentioned explicitly and prioritized alongside Azure CLI, with no mention of Linux-native alternatives or shell environments. All examples and references assume the use of Azure CLI or Azure PowerShell, which are most commonly used on Windows. There are no examples or guidance for Linux-specific tools, shell environments, or authentication workflows.
Recommendations
  • Include examples and references for Linux shell environments (e.g., Bash, zsh) and clarify that Azure CLI is cross-platform.
  • Mention Linux-native credential management options and workflows, such as using environment variables or managed identities in cloud-native Linux deployments.
  • Add explicit notes or examples showing how to configure and use Bicep with Linux and macOS, including installation and authentication steps.
  • Balance the mention of Azure PowerShell with alternatives more common on Linux, such as Bash scripts using Azure CLI.
  • Clarify that both Azure CLI and Azure PowerShell are available on multiple platforms, and provide links to platform-specific installation guides.
GitHub Create Pull Request
Azure Resource Manager Bicep functions for Bicep parameters files ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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, particularly in the 'readEnvironmentVariable' section, where only PowerShell commands and .NET/Windows-specific methods are provided for setting environment variables. There are no examples or instructions for setting environment variables on Linux or macOS systems, and the references are exclusively to Windows tooling and APIs.
Recommendations
  • Provide equivalent Linux/macOS shell examples (e.g., using 'export VAR=value' in bash) alongside PowerShell commands for setting environment variables.
  • Mention cross-platform considerations, such as differences in environment variable persistence and scope between Windows and Unix-like systems.
  • Include references to Linux/macOS documentation for environment variables, such as bash or zsh documentation.
  • When referencing .NET/Windows-specific APIs, clarify their applicability and provide alternatives or notes for non-Windows users.
  • Ensure that all code examples and instructions are presented in a platform-neutral way or with parity between Windows and Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Decompile a JSON Azure Resource Manager template to Bicep ...ain/articles/azure-resource-manager/bicep/decompile.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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. Examples for exporting templates are given for Azure CLI, Azure PowerShell, and Azure Portal, but PowerShell (a Windows-centric tool) is given a dedicated tab and example, and Visual Studio Code (often used on Windows) is referenced repeatedly as the primary editor. There are no explicit Linux shell examples (e.g., Bash), and Windows tools/patterns (PowerShell, VS Code) are mentioned before any Linux equivalents or alternatives. The documentation does not mention platform-specific considerations for Linux users, nor does it provide parity for Linux-native workflows.
Recommendations
  • Add explicit Bash or Linux shell examples for exporting and decompiling templates, e.g., using Bash redirection and command-line utilities.
  • Clarify that Azure CLI and Bicep CLI are cross-platform, and provide instructions for installing and running them on Linux and macOS.
  • Mention Linux-native editors (e.g., Vim, VS Code on Linux) and workflows alongside Visual Studio Code.
  • Where PowerShell is referenced, note that it is available cross-platform, but provide Bash equivalents for Linux users.
  • Add a section or note on platform-specific differences, such as file paths, shell syntax, and permissions, to ensure Linux users are not disadvantaged.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to management group ...e-resource-manager/bicep/deploy-to-management-group.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides deployment command examples for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence and detail as the CLI example. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux users. The references to Cloud Shell do not clarify Bash vs PowerShell usage, and the CLI example uses backslashes for line continuation, which is more familiar to Windows users. There is no explicit mention of Linux tools or patterns, and Windows-centric tools (PowerShell) are featured as a primary method.
Recommendations
  • Add explicit Bash examples for Azure CLI, using Linux-style line continuation (\ or \ at end of line) and environment variable usage.
  • Clarify that Azure CLI works cross-platform and provide sample commands for Bash and/or zsh.
  • In the Cloud Shell section, specify both Bash and PowerShell options, and provide examples for each.
  • Consider listing Azure CLI (Bash) examples before PowerShell to reduce perceived Windows-first bias.
  • Add notes or callouts for Linux/macOS users regarding command syntax differences and environment setup.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to resource groups ...ure-resource-manager/bicep/deploy-to-resource-group.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Azure PowerShell examples for deploying Bicep files, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific usage patterns or considerations. The documentation does not reference Linux tools or provide guidance for Linux users beyond the Azure CLI, which is cross-platform but often used in bash/zsh environments on Linux. The order of presentation does not favor Windows, but the inclusion of PowerShell as a primary example and lack of bash-specific examples suggests a mild Windows bias.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, showing command syntax as typically used on Linux.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide notes or examples for common Linux shells.
  • Consider adding a section or note about using Bicep deployments from Linux environments, including installation and usage tips.
  • If PowerShell is included, clarify its cross-platform availability, but avoid implying it is the default or only option for scripting deployments.
GitHub Create Pull Request
← Previous Page 12 of 52 Next →