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 501-525 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md ...e-manager/templates/template-tutorial-use-key-vault.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 strong Windows bias. All code examples for interacting with Azure Key Vault and deploying ARM templates use Azure PowerShell, with no Azure CLI or Bash equivalents provided. The tutorial centers on deploying a Windows VM, referencing Windows-specific password requirements and RDP for validation. Linux VM scenarios, password requirements, and SSH connection instructions are absent. The use of PowerShell is exclusive throughout, and Windows tools/patterns (such as RDP) are mentioned without Linux alternatives.
Recommendations
  • Provide Azure CLI and Bash script equivalents alongside PowerShell examples for all resource creation, deployment, and validation steps.
  • Include a parallel tutorial or examples for deploying a Linux VM, referencing Linux-specific password/SSH key requirements.
  • Add instructions for connecting to a Linux VM using SSH, including how to retrieve the password or SSH key from Key Vault.
  • Reference both Windows and Linux VM password requirements, and link to relevant documentation for each.
  • Ensure that Cloud Shell instructions explicitly show both PowerShell and Bash usage, and alternate examples where possible.
  • Balance the use of Windows tools (RDP) with Linux tools (SSH) in validation and connection steps.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md ...ger/troubleshooting/create-troubleshooting-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 Windows bias by mentioning Azure PowerShell (a Windows-centric tool) before Azure CLI, and by referencing PowerShell-specific commands and links. There are no explicit Linux shell examples (e.g., Bash), nor is there guidance for Linux users regarding command syntax or environment differences. The troubleshooting workflow and deletion steps do not mention platform-specific commands or alternatives for Linux users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Include explicit Bash/Linux shell command examples for deploying ARM/Bicep templates.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide installation/use links for each.
  • When referencing resource group deletion, provide both PowerShell and CLI commands, and note platform differences.
  • Avoid language that implies PowerShell is the default or preferred method, and encourage use of cross-platform tools.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/decompile.md ...ain/articles/azure-resource-manager/bicep/decompile.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 mild Windows bias. While Azure CLI (cross-platform) is used for most examples, PowerShell is given a dedicated tab and example, and Visual Studio Code (a cross-platform but Windows-popular tool) is emphasized. The PowerShell example is presented before the Azure portal example, and there are no explicit Linux/macOS shell (e.g., Bash) examples or notes about platform differences. The use of Windows-centric patterns (e.g., right-click, F2 hotkey) and lack of Linux-specific guidance or parity in tooling references further reinforce the bias.
Recommendations
  • Add explicit Bash or Linux/macOS shell examples alongside Azure CLI and PowerShell, especially for file redirection and command usage.
  • When referencing hotkeys or UI actions (e.g., right-click, F2), clarify platform differences or provide alternatives for Linux/macOS users.
  • Ensure that PowerShell is not given priority over cross-platform tools; consider listing Azure CLI and Bash examples before PowerShell.
  • Mention any platform-specific considerations for installing or using the Bicep CLI.
  • Highlight that Visual Studio Code is cross-platform and provide links or tips for Linux/macOS installation if referenced.
  • Where possible, include screenshots or instructions that reflect both Windows and Linux/macOS environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-bicep.md ...zure-resource-manager/bicep/deployment-script-bicep.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 demonstrates a moderate Windows bias. PowerShell examples and references are given equal or greater prominence than Azure CLI (Linux) examples, and Windows-centric tools and patterns (such as PowerShell, Connect-AzAccount, and Azure PowerShell cmdlets) are frequently mentioned. Script deployment instructions and management examples are provided for both Azure CLI and PowerShell, but PowerShell is often presented first or with more detail. There is a lack of explicit Linux shell script examples outside of Azure CLI, and no mention of Bash or other Linux-native scripting environments. The instructions for deploying scripts use Azure PowerShell without offering a CLI or Bash alternative, and troubleshooting steps do not discuss Linux-specific tools or workflows.
Recommendations
  • Ensure that Azure CLI (Linux) examples are presented before or alongside PowerShell examples throughout the documentation.
  • Provide explicit Bash script examples and instructions for deploying scripts using Bash or the Azure CLI, not just PowerShell.
  • When referencing authentication methods, include Linux-native equivalents (e.g., az login in Bash) and avoid assuming PowerShell as the default.
  • Add troubleshooting and management instructions using Linux tools and workflows, such as jq, curl, or shell scripting.
  • Clarify that deployment scripts can be authored and executed in Linux environments, and provide guidance for setting up Linux-based development environments.
  • Avoid using Windows-specific terminology or tools (e.g., Write-Host, PowerShell cmdlets) without offering Linux alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-config-modules.md ...s/azure-resource-manager/bicep/bicep-config-modules.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 Windows bias primarily by referencing Azure PowerShell and Azure CLI as the default credential sources, listing Azure PowerShell before other options, and omitting explicit Linux-specific examples or guidance. There are no examples of Linux shell usage, nor is there mention of Linux-specific authentication patterns or parity for credential precedence. The documentation assumes familiarity with Windows-centric tools and does not provide alternative instructions for Linux users.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are cross-platform, and clarify any platform-specific differences in usage or installation.
  • Provide Linux shell (bash/zsh) examples for authentication and module publishing/restoring, including environment variable usage for credentials.
  • Include guidance for using Environment credential type with Linux, such as setting environment variables for service principal authentication.
  • List credential types in a neutral order (e.g., alphabetical) rather than prioritizing Windows tools.
  • Reference Linux-native editors and authentication flows (e.g., VS Code on Linux, SSH-based authentication) where relevant.
  • Add a section or note highlighting Linux support and any caveats or best practices for Linux users.
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: 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 consistently presenting Azure PowerShell examples alongside Azure CLI, often giving PowerShell equal or greater prominence. There are no explicit Linux shell (bash) examples, and installation instructions focus on PowerShell and Azure CLI without mentioning Linux-specific details. The use of PowerShell syntax and terminology is pervasive, and Windows-centric tools (PowerShell) are featured as primary options for interacting with Bicep what-if operations. There is no mention of Linux-native scripting, nor are Linux-specific usage patterns (e.g., bash scripting, environment setup) provided.
Recommendations
  • Add explicit bash (Linux shell) examples for all CLI commands, including variable assignment and output parsing.
  • Include installation instructions for Azure CLI on Linux, and clarify cross-platform compatibility for all tools.
  • When presenting command tabs, list Azure CLI (bash) first, then PowerShell, to avoid Windows-first ordering.
  • Provide guidance for using what-if operations in Linux environments, including troubleshooting and environment setup.
  • Mention that Azure CLI is cross-platform and highlight usage on Linux/macOS as well as Windows.
  • Avoid PowerShell-exclusive code blocks for output parsing; provide equivalent bash/jq examples.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-resource-group.md ...ure-resource-manager/bicep/deploy-to-resource-group.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 Azure PowerShell examples for deploying Bicep files, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux/macOS environments or shell-specific considerations. The CLI example is cross-platform, but the PowerShell example is Windows-centric. There are no bash or Linux-specific examples, nor any mention of running these commands in a Linux shell or Cloud Shell (except in a link). This may subtly reinforce a Windows-first or PowerShell-heavy bias.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and can be run from Bash, PowerShell, or Cloud Shell.
  • Add example commands for Bash (Linux/macOS) environments, especially for common deployment scenarios.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest using Azure CLI for cross-platform compatibility.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or group them under 'Windows' and 'Linux/macOS' headings.
  • Add notes or links to documentation about using Bicep deployments from Linux/macOS terminals.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-management-group.md ...e-resource-manager/bicep/deploy-to-management-group.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 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 environments (such as Bash) or explicit Linux command-line patterns. The references to Cloud Shell do not clarify parity between Bash and PowerShell environments, and there are no Linux-specific troubleshooting or usage notes. The documentation implicitly assumes familiarity with PowerShell, which is primarily a Windows tool, and does not offer guidance for Linux users beyond the generic Azure CLI example.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and clarify any OS-specific prerequisites.
  • Add Bash-specific examples or notes where appropriate, especially for deployment commands and scripting.
  • Clarify that Cloud Shell supports both Bash and PowerShell, and provide links or examples for both environments.
  • Avoid giving PowerShell examples equal or greater prominence than CLI/Bash unless justified by feature parity.
  • Include troubleshooting notes or tips for Linux users, such as file path differences or authentication nuances.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-cli.md ...in/articles/azure-resource-manager/bicep/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Bash First Windows Shell Notes Windows Shell Examples
Summary
The documentation page primarily provides Azure CLI examples in Bash syntax, with explicit notes that adjustments may be needed for Windows PowerShell or Command Prompt. While some Windows-specific formats and variable assignments are mentioned, the examples and instructions are consistently Bash-first, with Windows alternatives described only in text and not shown as full code blocks. There are no PowerShell or cmd code blocks, and Linux tools are not discussed beyond Bash. This results in a bias toward Bash/Linux users, but Windows users are not fully supported with equivalent examples.
Recommendations
  • Provide full code block examples for Windows PowerShell and Command Prompt alongside Bash examples, especially for parameter passing and variable assignment.
  • Clearly label each code block with the target shell (e.g., Bash, PowerShell, cmd) to improve clarity.
  • Include a section summarizing key differences and common pitfalls when using Azure CLI commands on Windows shells.
  • Consider parity in troubleshooting tips and environment setup instructions for both Linux and Windows users.
  • Where Bash-specific syntax is used (e.g., $RANDOM, $(date)), offer Windows equivalents (e.g., using Get-Random or Get-Date in PowerShell).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-stacks.md ...cles/azure-resource-manager/bicep/deployment-stacks.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 consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and uses PowerShell-specific syntax and terminology throughout. There is a strong emphasis on PowerShell commands and switches, with Azure CLI examples provided but always after PowerShell. No Linux-specific shell examples (e.g., bash, zsh) or guidance are given, and the documentation assumes familiarity with PowerShell patterns and conventions. This ordering and focus may make the documentation less approachable for Linux users, who are more likely to use Azure CLI in bash/zsh environments.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate the order to avoid implicit prioritization.
  • Include explicit bash/zsh shell examples for Azure CLI commands, demonstrating usage in typical Linux environments (e.g., variable assignment, quoting, piping output to jq).
  • Add notes clarifying that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is more common on Windows.
  • Avoid PowerShell-specific terminology (e.g., 'switch', backtick line continuation) in general documentation sections, or provide equivalent Linux shell explanations.
  • Where possible, add troubleshooting or usage tips for Linux users (e.g., file paths, environment variables, output parsing).
  • Consider a dedicated section or tab for Linux/macOS usage patterns if significant differences exist.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/key-vault-parameter.md ...es/azure-resource-manager/bicep/key-vault-parameter.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 scenarios (WinRM on a Windows VM) are referenced as quickstart examples, and Azure PowerShell is given equal prominence to Azure CLI throughout, with detailed PowerShell scripts provided for all operations. There is no explicit mention of Linux-specific scenarios or tools, and Windows VM use cases are referenced before any Linux equivalents (which are absent). The documentation does not provide parity for Linux users in terms of examples or context.
Recommendations
  • Include Linux-specific scenarios and quickstart references (e.g., SSH on Linux VMs) alongside Windows VM examples.
  • Ensure that Azure CLI examples are presented first, as CLI is cross-platform, and clarify that PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there).
  • Add notes or examples for Linux users, such as using Bash scripts or integrating with Linux-based automation tools.
  • Reference Linux VM templates or use cases where secrets are passed from Key Vault, to balance the Windows VM example.
  • Review related links and ensure parity in guidance for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate.md .../main/articles/azure-resource-manager/bicep/migrate.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 mentioning Windows and PowerShell tools and patterns before their Linux equivalents, providing examples and shortcuts that are Windows-centric, and omitting explicit Linux shell or tool examples. References to exporting resources and using command palettes are described with Windows terminology first, and PowerShell is highlighted as a primary method for resource export. There are no explicit Linux shell (bash) or cross-platform CLI examples, and Windows-specific resource extensions (e.g., DependencyAgentWindows) are referenced without Linux alternatives.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell commands, especially when describing resource export or CLI usage.
  • Mention Linux tools and patterns (e.g., az CLI usage in bash, Linux-specific resource extensions) equally or before Windows equivalents.
  • Clarify that Azure CLI and Visual Studio Code are cross-platform, and provide OS-agnostic instructions where possible.
  • Include keyboard shortcuts for Linux and macOS equally, and avoid listing Windows shortcuts first.
  • Reference Linux-compatible resource extensions and scenarios when discussing VM extensions.
  • Add guidance for users working on Linux environments, such as using bash scripts for automation or deployment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates bias toward Windows by referencing only Azure PowerShell and linking to PowerShell-based export instructions, without mentioning or providing equivalent Azure CLI or Linux-native workflows. There are no Linux/CLI examples or explicit parity in tooling guidance.
Recommendations
  • Include Azure CLI commands and examples alongside or before PowerShell instructions for exporting blueprint definitions and configuring deployment stacks.
  • Update links and references to point to both PowerShell and CLI documentation where available.
  • Explicitly mention that all migration steps can be performed using Azure CLI on Linux/macOS, and provide sample commands.
  • Ensure that instructions for configuring DenySettingsMode and other stack features include both PowerShell and CLI workflows.
  • Add a note clarifying cross-platform support and recommend tools available on all major operating systems.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/msbuild-bicep-file.md ...les/azure-resource-manager/bicep/msbuild-bicep-file.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 demonstrates a Windows bias by consistently presenting Windows and PowerShell examples first and sometimes exclusively. Directory paths, terminal commands, and project setup instructions are shown using Windows conventions (e.g., C:\ paths, PowerShell commands), with no equivalent Linux/macOS shell examples. The Classic framework section is entirely Windows-specific, and cleanup instructions use PowerShell. While cross-platform NuGet packages are mentioned, practical usage and examples are Windows-centric, and Linux/macOS users are left to infer adaptations.
Recommendations
  • Provide equivalent Linux/macOS shell examples (e.g., bash/zsh commands) alongside PowerShell commands for all steps, including directory creation, navigation, and cleanup.
  • Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) in examples and instructions, not just Windows paths.
  • Include explicit instructions for running MSBuild and dotnet CLI on Linux/macOS, including installation prerequisites and platform-specific notes.
  • Add project file examples referencing Azure.Bicep.CommandLine.linux-x64 and Azure.Bicep.CommandLine.osx-x64, not just win-x64.
  • Where Visual Studio is referenced, mention cross-platform alternatives (e.g., Visual Studio Code, JetBrains Rider) and clarify which steps are platform-agnostic.
  • For cleanup, provide Linux/macOS equivalents (e.g., rm -rf ~/msBuildDemo) alongside Remove-Item PowerShell commands.
  • Consider using neutral language and ordering (e.g., 'On Windows', 'On Linux', 'On macOS') rather than presenting Windows first or exclusively.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md ...urce-manager/bicep/quickstart-create-template-specs.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 demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, and by not providing Linux/macOS equivalents. All examples assume a Windows environment, and there is no mention of Linux-specific considerations or examples (such as using ~/templates/main.bicep or /home/user/templates/main.bicep). Additionally, the documentation references PowerShell and Azure PowerShell heavily, which are more native to Windows, and the only editor mentioned is Visual Studio Code, which, while cross-platform, is often associated with Windows in Microsoft documentation.
Recommendations
  • Provide Linux/macOS equivalents for all file paths in CLI and PowerShell examples (e.g., ~/templates/main.bicep or /home/user/templates/main.bicep).
  • Explicitly mention that the CLI and PowerShell commands work on Linux/macOS, and note any differences in syntax or environment setup.
  • When referencing file paths in code samples, use environment-agnostic variables or provide both Windows and Linux/macOS path formats.
  • Include a note or section on running Azure CLI and PowerShell on Linux/macOS, including any prerequisites or differences.
  • Consider mentioning other editors that are popular on Linux/macOS, or clarify that Visual Studio Code is available cross-platform.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-spread.md ...ticles/azure-resource-manager/bicep/operator-spread.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 Windows bias in its 'Next steps' section by listing Azure PowerShell and Visual Studio Code (VS Code) as the primary tools for deploying and authoring Bicep files. Azure PowerShell is a Windows-centric tool, and VS Code is often associated with Windows workflows. There is no mention of Linux-native alternatives (e.g., Bash, cloud shell, or Linux editors), nor are Linux-specific deployment instructions or examples provided. The examples themselves are platform-neutral, but the guidance for running them favors Windows environments.
Recommendations
  • Include explicit instructions and examples for deploying Bicep files using Azure CLI in Bash or other Linux shells.
  • Mention Linux-native editors (such as Vim, Emacs, or VS Code on Linux) for authoring Bicep files.
  • Add links or references to documentation for running Bicep deployments in Azure Cloud Shell, which is platform-agnostic.
  • Ensure that both Azure CLI and Azure PowerShell are presented equally, or list Azure CLI first to avoid Windows-first bias.
  • Clarify that Bicep is cross-platform and can be used on Windows, Linux, and macOS.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md ...icep/quickstart-create-bicep-use-visual-studio-code.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. While both Azure CLI and Azure PowerShell examples are provided for deployment and cleanup, PowerShell is mentioned as an equal alternative to CLI in prerequisites and examples. The use of Visual Studio Code is platform-neutral, but the documentation refers to Visual Studio (Windows-only) as a similar experience and links to a separate quickstart for it. The order of presentation often lists PowerShell alongside or before CLI, and no explicit Linux-specific instructions, troubleshooting, or screenshots are provided. There is no mention of Linux-specific considerations, such as shell differences, nor are there examples using Bash or other Linux-native tools.
Recommendations
  • Explicitly mention that Visual Studio Code and the Bicep extension are cross-platform and supported on Linux and macOS, not just Windows.
  • Provide Linux/Bash-specific examples for deploying Bicep files, including command-line usage and troubleshooting tips (e.g., file path formats, permissions).
  • Include screenshots taken from Linux environments (e.g., Ubuntu desktop) to demonstrate parity.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux users, possibly listing CLI examples before PowerShell.
  • Add a note or section for Linux/macOS users, addressing any differences in setup, keyboard shortcuts, or environment variables.
  • Avoid referring to Visual Studio (Windows-only) as a primary alternative; instead, mention cross-platform editors first.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/private-module-registry.md ...zure-resource-manager/bicep/private-module-registry.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 demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and the documentation uses Windows-specific terminology and tools (e.g., PowerShell, %USERPROFILE% path) as defaults or primary references. Linux and Mac paths are included, but with less detail. There are no Bash or shell script examples, and the documentation assumes familiarity with Windows conventions.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) first to avoid implicit prioritization of Windows.
  • Include Bash or shell script equivalents where relevant, especially for common automation tasks.
  • Provide more detailed Linux and Mac path examples, matching the specificity given to Windows (e.g., show full Linux/Mac paths, not just the root folder).
  • Clarify that Azure CLI commands work identically on Windows, Linux, and Mac, and encourage its use for cross-platform compatibility.
  • Where possible, avoid Windows-specific environment variables (like %USERPROFILE%) in favor of cross-platform alternatives (like $HOME or ~).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md ...ce-manager/bicep/quickstart-private-module-registry.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 Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing examples and instructions only for Azure CLI and Azure PowerShell, with no mention of Linux-native tools or shell environments (e.g., Bash). The tooling recommendations focus on Visual Studio Code and Visual Studio, both of which are traditionally Windows-centric (though VS Code is cross-platform). There are no Bash or Linux shell command examples, nor is there guidance for using the Bicep CLI directly in a Linux environment. PowerShell examples are given equal prominence to Azure CLI, and Windows tools are referenced throughout, with no explicit Linux alternatives.
Recommendations
  • Add Bash shell examples for all Azure CLI commands, demonstrating usage in a Linux environment.
  • Explicitly mention that Azure CLI commands can be run in Bash on Linux/macOS, and provide sample commands using Bash variables and syntax.
  • Include instructions for installing and using Bicep CLI on Linux and macOS, not just Windows.
  • Reference Linux-native editors (e.g., Vim, nano) for editing Bicep files, or clarify that VS Code is available cross-platform.
  • Avoid presenting PowerShell examples before or alongside CLI examples unless parity is maintained for Linux users.
  • Add a section or note on cross-platform compatibility, highlighting any differences or considerations for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/template-specs.md ...rticles/azure-resource-manager/bicep/template-specs.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 consistently presents Azure PowerShell examples before Azure CLI, and all command-line examples are limited to PowerShell and Azure CLI without explicit mention of Linux shell environments or cross-platform differences. There are no references to Linux-specific tools, shell syntax, or considerations for non-Windows users. The use of PowerShell is prominent, and there is an implicit assumption that users are familiar with PowerShell, which is primarily a Windows technology (though available on Linux, it is less commonly used there). No examples are given for Bash, zsh, or other Linux-native shells, nor are there notes about platform-specific differences.
Recommendations
  • Explicitly state that Azure CLI commands work on both Windows and Linux, and provide Bash/zsh syntax where relevant (e.g., use $() for command substitution in CLI examples).
  • Add notes or sections highlighting any platform-specific differences, such as file path formats, environment variable usage, or installation steps for Azure CLI and PowerShell on Linux.
  • Include examples using Bash shell syntax for Azure CLI, especially for variable assignment and command chaining.
  • Clarify that PowerShell is available on Linux but is less commonly used, and recommend Azure CLI for Linux users.
  • Consider adding troubleshooting tips or links for Linux users, such as dealing with file permissions or installing dependencies.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-access.md ...icles/azure-resource-manager/bicep/operators-access.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 Windows bias primarily in the 'Next steps' section, where Azure PowerShell is mentioned before Azure CLI and no explicit Linux shell examples are provided. The guidance for running examples references Azure PowerShell and Visual Studio Code, both of which are commonly associated with Windows environments, and does not mention Linux-native tools or workflows. No Linux-specific instructions or parity examples are present.
Recommendations
  • Explicitly mention Azure CLI as a cross-platform tool before Azure PowerShell, or provide equal prominence to both.
  • Include example commands for deploying Bicep files using Azure CLI in Bash or other Linux shells.
  • Add notes or links for Linux users, such as instructions for installing Bicep and running deployments on Linux.
  • Reference editors available on Linux (such as Visual Studio Code, Vim, etc.) when discussing Bicep file creation.
  • Ensure that all examples and instructions are clearly marked as cross-platform or provide platform-specific variants where necessary.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/parameter-files.md ...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias in several areas: deployment examples for Azure PowerShell use only Windows-style paths (e.g., C:\MyTemplates\...), and all PowerShell examples use the Windows-centric Azure PowerShell module. There is no mention of Linux equivalents (such as Bash or pwsh on Linux), nor are Linux file path formats (e.g., /home/user/...) provided. Visual Studio Code is referenced as the editor, which is cross-platform, but no explicit Linux-specific instructions or examples are given. Windows tools and patterns (PowerShell, Windows file paths) are mentioned exclusively and before any Linux alternatives.
Recommendations
  • Include Linux/Bash examples alongside PowerShell, especially for deployment commands (e.g., az deployment group create in Bash, pwsh, or sh).
  • Show file paths in both Windows (C:\...) and Linux (/home/user/...) formats for clarity.
  • Mention that Azure PowerShell and Bicep CLI are available cross-platform, and provide instructions/examples for installing and running them on Linux/macOS.
  • Add notes or examples for using pwsh (PowerShell Core) on Linux/macOS, not just Windows PowerShell.
  • Where Visual Studio Code is referenced, clarify cross-platform support and provide any Linux/macOS-specific setup notes if relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/deploy-bicep-definition.md ...anager/managed-applications/deploy-bicep-definition.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 consistently presents Windows-centric tools and patterns first, such as PowerShell and Visual Studio Code, and provides detailed PowerShell examples before their Azure CLI equivalents. Visual Studio Code is recommended as the primary editor, which is more common on Windows. There is no mention of Linux-specific editors or shell environments (e.g., native Bash, Vim, nano), nor any guidance for Linux users beyond suggesting 'Git Bash' for CLI usage. The documentation assumes familiarity with Windows conventions and tools, potentially making it less accessible for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections to avoid Windows-first bias.
  • Explicitly mention Linux and macOS compatibility for all steps, including editor and shell choices.
  • Recommend or reference Linux-native editors (e.g., Vim, nano, gedit) and terminal environments alongside Visual Studio Code.
  • Provide instructions for running Azure CLI commands in native Bash shells on Linux and macOS, not just Git Bash.
  • Include troubleshooting notes or environment setup tips specific to Linux (e.g., file permissions, path separators, package installation).
  • Clarify that both PowerShell and Azure CLI are cross-platform and provide installation links for Linux and macOS.
  • Add a note or section highlighting differences or considerations for Linux users, especially for steps that may behave differently on non-Windows systems.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/includes/tags.md ...les/azure-resource-manager/management/includes/tags.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 examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and no explicit Linux/bash or macOS shell examples are given. The ordering of examples consistently places Azure CLI first, followed by Azure PowerShell, and then Portal, which is a common but subtle Windows-first pattern. There are no references to Linux-specific tools, nor are there any bash or shell script examples, which may leave Linux users without guidance for shell integration or scripting beyond Azure CLI.
Recommendations
  • Add explicit bash/shell script examples for each scenario, demonstrating usage in Linux/macOS environments.
  • Clarify that Azure CLI commands work cross-platform and provide sample outputs or troubleshooting notes for Linux/macOS users.
  • Consider including links or references to Linux-native tools or scripting patterns where relevant.
  • If PowerShell is shown, note that PowerShell Core is available cross-platform, and provide installation or usage notes for Linux/macOS.
  • Review ordering of examples to avoid reinforcing Windows-first perceptions; alternate or randomize order, or group by platform type.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md ...ions/publish-service-catalog-bring-your-own-storage.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 consistently presents Windows/PowerShell examples before Linux/Azure CLI equivalents, and uses Windows-centric terminology and tools (e.g., PowerShell splatting, Visual Studio Code as the only editor, references to Git Bash for Windows). While Azure CLI examples are provided for Linux/macOS users, the ordering and explanations favor Windows users, and there is little mention of Linux-specific workflows or alternative editors/tools.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Explicitly mention Linux/macOS compatibility and workflows, including common editors (e.g., Vim, nano) and shell environments (e.g., Bash, Zsh).
  • Provide troubleshooting notes for Linux/macOS users (e.g., file permissions, line endings, shell differences), not just for Git Bash on Windows.
  • Reference cross-platform tools and extensions, and clarify that Visual Studio Code is available on Linux/macOS, or suggest alternatives.
  • Avoid Windows-specific terminology (e.g., splatting) without equivalent Linux/CLI explanations.
  • Include a parity checklist to ensure all steps and examples are equally accessible and clear for Linux users.
GitHub Create Pull Request
← Previous Page 21 of 52 Next →