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 351-375 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/request-limits-and-throttling.md ...ce-manager/management/request-limits-and-throttling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 in several ways. PowerShell examples are given in detail, including debugging output and links to full scripts, while Linux-specific shell examples (such as Bash or curl) are missing. The PowerShell examples are presented before Azure CLI, and there is no mention of Linux tools or patterns for retrieving HTTP headers (e.g., using curl, jq, or Bash). This prioritizes Windows-centric tooling and workflows, making it less accessible for Linux users.
Recommendations
  • Add equivalent Linux shell examples using curl and jq to show how to retrieve rate limit headers from Azure Resource Manager responses.
  • Include Bash scripts or command-line snippets for common Linux environments alongside PowerShell and Azure CLI examples.
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering, as Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI and REST API calls work on Linux, macOS, and Windows, and provide troubleshooting tips for Linux users.
  • Link to cross-platform sample scripts and documentation, not just PowerShell-specific resources.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub.md ...-manager/management/relocation/relocation-event-hub.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 explicit PowerShell instructions and references, while lacking equivalent Linux or cross-platform CLI examples. The PowerShell tab is present, but there is no Bash or Azure CLI tab for Linux users. Additionally, when discussing how to obtain region codes, only the PowerShell command is shown, with no mention of the Azure CLI equivalent. Throughout the page, instructions and screenshots are oriented toward the Azure portal and PowerShell, with no Linux-specific guidance or parity.
Recommendations
  • Add Azure CLI (bash) examples and tabs alongside PowerShell for all template modification and deployment steps.
  • When referencing commands to obtain region codes, include both PowerShell and Azure CLI equivalents (e.g., 'az account list-locations').
  • Ensure all instructions and screenshots are platform-neutral or provide Linux-specific alternatives where relevant.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Review and update the documentation to avoid assuming Windows as the default environment for automation and scripting.
GitHub Create Pull Request
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-09 00:34
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 Azure PowerShell before Azure CLI and REST API when discussing supported versions for zero-count copy loops. The 'Next steps' section links only to a PowerShell deployment guide, omitting Linux-friendly or cross-platform CLI deployment guides. No Linux-specific examples, shell commands, or CLI walkthroughs are provided, and PowerShell is mentioned more prominently than CLI.
Recommendations
  • Add explicit Azure CLI deployment instructions and examples alongside PowerShell, especially in the 'Next steps' section.
  • When listing supported tools or versions, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Include cross-platform deployment examples using Bash or shell scripts to demonstrate Linux parity.
  • Provide links to CLI-based tutorials and documentation in addition to PowerShell-focused resources.
  • Clarify that both CLI and PowerShell are supported equally for ARM template deployment, and avoid implying preference for Windows tools.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-mission-critical-workload.md ...ce-manager/management/tag-mission-critical-workload.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 by listing Azure PowerShell as the first automation tool for tagging resources, and by referencing PowerShell specifically in the guidance. There is a lack of explicit Linux shell (bash) examples or mention of Linux-specific workflows, and the CLI is listed after PowerShell. The documentation also references tools (PowerShell) that are primarily associated with Windows environments, without balancing with Linux-native equivalents or examples.
Recommendations
  • List Azure CLI before Azure PowerShell to avoid implying Windows-first workflows.
  • Include explicit bash/Linux shell examples for tagging resources using Azure CLI.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide links or examples for using tagging in Linux automation contexts (e.g., shell scripts, cron jobs).
  • Balance references to PowerShell with references to bash/zsh or other Linux-native tools.
  • Consider including a section or note for Linux users, highlighting best practices for tagging in Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/best-practices.md ...les/azure-resource-manager/templates/best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets) are mentioned before Linux equivalents, and Windows connection methods are listed before Linux ones. There is a specific section discussing PowerShell parameter conflicts, but no equivalent mention of Azure CLI or Linux shell usage. The references to connecting to VMs prioritize Windows methods and tools, with Linux mentioned last. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows development environments.
Recommendations
  • Provide examples and guidance for Azure CLI and Bash shell usage alongside PowerShell, especially when discussing parameter conflicts and deployment commands.
  • When listing connection methods to VMs, present Linux and Windows options with equal prominence, or group them together for parity.
  • Mention Linux-native editors (such as Vim, Emacs, or VS Code on Linux) when recommending tooling, to reinforce cross-platform support.
  • Ensure that any references to Windows-specific tools or patterns are complemented by Linux equivalents, and avoid listing Windows options first unless contextually necessary.
  • Add explicit examples of ARM template deployment using Azure CLI and Bash, not just PowerShell.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/rollback-on-error.md .../azure-resource-manager/templates/rollback-on-error.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell examples before Azure CLI examples, and uses Windows-style file paths (e.g., c:\MyTemplates\azuredeploy.json) in PowerShell commands. PowerShell is a Windows-centric tool, and the use of Windows file paths may confuse Linux users. There are no Linux shell (bash) or cross-platform PowerShell Core examples, nor are Linux-specific considerations mentioned.
Recommendations
  • Provide Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Include Linux-style file paths (e.g., /home/user/templates/azuredeploy.json) in CLI and PowerShell examples.
  • Mention that PowerShell Core is available on Linux and macOS, and provide examples using Linux paths.
  • Add notes or examples for running these commands in bash or other Linux shells.
  • Clarify any platform-specific requirements or differences in deployment tooling.
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: 2026-01-09 00:34
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 provided alongside Azure CLI for every operation, and references to Windows-specific scenarios (such as installing certificates on Windows VMs) appear early. The use of PowerShell is emphasized, and Windows-centric terminology and patterns (e.g., backtick line continuations, ConvertTo-SecureString) are present. There is no mention of Linux-specific shell patterns, nor are there examples tailored to Linux environments (such as Bash scripting or Linux VM scenarios).
Recommendations
  • Add explicit Bash shell examples for all CLI commands, including Linux-style line continuations and environment variable usage.
  • Include Linux VM scenarios in references and quickstart links, not just Windows VM certificate installation.
  • Avoid Windows-centric terminology (e.g., backtick for line continuation) in PowerShell examples, or provide equivalent Bash syntax.
  • Mention cross-platform compatibility for all commands and clarify any OS-specific behaviors.
  • Ensure that references to tools and tutorials are balanced between Windows and Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses exclusively on ARM template functions and provides JSON examples, which are platform-neutral. However, in the 'Next steps' section, deployment guidance is given only for Azure PowerShell, with no mention of Azure CLI or Linux-native tools. This suggests a Windows-first and PowerShell-heavy bias, and there is a lack of parity for Linux users due to missing Azure CLI examples and links.
Recommendations
  • Add links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux.
  • In the 'Next steps' section, mention both Azure PowerShell and Azure CLI deployment guides, giving equal prominence to each.
  • Where deployment instructions are referenced, provide sample commands for both PowerShell and Azure CLI.
  • Review other related documentation pages to ensure Linux and cross-platform tools are represented alongside Windows/PowerShell options.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-modes.md ...s/azure-resource-manager/templates/deployment-modes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 follows, but there are no explicit Linux shell examples or references to Linux-specific patterns. The 'Next steps' section prioritizes PowerShell-based deployment guidance, and there is no mention of Bash, Linux, or cross-platform scripting approaches.
Recommendations
  • Provide Bash or Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Use platform-neutral file paths in examples (e.g., ./MyTemplates/storage.json) or show both Windows and Linux path styles.
  • In 'Next steps', include links to documentation for deploying resources with Azure CLI and Bash, not just PowerShell.
  • Explicitly state that Azure CLI works cross-platform and can be used on Linux, macOS, and Windows.
  • Where PowerShell is mentioned, clarify that it is available on Linux and macOS as well, or provide alternative instructions for those platforms.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deployment-script.md ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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/PowerShell bias. All deployment script examples use PowerShell exclusively, and the only supported script kind is 'AzurePowerShell'. The tutorial and explanations focus on PowerShell syntax, quoting rules, and error messages. While Azure CLI examples are provided for template deployment, there are no examples or guidance for authoring or running deployment scripts using Bash or other Linux-native tools. The documentation does not mention or demonstrate Linux scripting patterns, and PowerShell is presented as the default and only option for deployment scripts.
Recommendations
  • Add Bash-based deployment script examples and guidance, especially for the 'Microsoft.Resources/deploymentScripts' resource, to demonstrate Linux parity.
  • Explicitly mention and demonstrate how to use 'AzureCLI' as the 'kind' for deployment scripts, including sample Bash scripts for the same scenario.
  • Balance the order of examples and explanations so that Linux/Bash/CLI options are presented alongside or before Windows/PowerShell options.
  • Include troubleshooting and debugging steps for Bash-based deployment scripts, not just PowerShell.
  • Clarify in the documentation which features are PowerShell-only and which are available for Bash/CLI, and update the tutorial to cover both platforms where possible.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows mild Windows bias. Azure PowerShell is mentioned before Azure CLI in prerequisites and deployment instructions, and PowerShell examples are given equal prominence to CLI examples. There are no explicit Linux shell examples (e.g., bash scripting), nor is there guidance for Linux-specific tooling or workflows. The use of Visual Studio Code is platform-neutral, but the overall pattern leans toward Windows-first and PowerShell-heavy approaches.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is platform-agnostic and more commonly used on Linux.
  • Include explicit bash shell scripting examples for template deployment and resource management.
  • Mention Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code.
  • Add guidance for using the Azure portal and CLI from Linux environments, including installation instructions for Azure CLI on Linux.
  • Clarify that all steps and tools are cross-platform unless otherwise noted, and highlight any platform-specific differences.
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-09 00:34
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 Azure PowerShell and Azure CLI as the primary credential sources, listing Azure PowerShell before alternatives, and omitting explicit Linux or cross-platform examples for authentication or module management. No Linux-specific tools, shell commands, or platform parity notes are provided.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are available on Linux and macOS, and provide links or notes about installation and usage on those platforms.
  • Include Linux shell (bash/zsh) examples for common operations, such as publishing or restoring modules, alongside any PowerShell examples.
  • Clarify that credential precedence and authentication work similarly across platforms, and highlight any platform-specific caveats.
  • Reference cross-platform editors (e.g., VS Code) and their authentication flows, not just Windows-centric tools.
  • Add a section or note about using Bicep and its configuration on Linux, including file paths, environment variables, and common patterns.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-cli.md ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias primarily through the use of Windows-style paths (e.g., c:\jsontemplates) in all file path examples, with no equivalent Linux/macOS examples provided. Windows paths are shown first and exclusively in command samples, and installation references prioritize Azure PowerShell (a Windows-centric tool). The local cache location is described for Windows first and in more detail, while Linux and Mac are mentioned briefly and generically. There are no explicit Linux/macOS command examples for file paths, and PowerShell is referenced in installation guidance and next steps, but Bash or Linux shell alternatives are not.
Recommendations
  • Provide Linux/macOS path examples (e.g., /home/user/jsontemplates or ~/jsontemplates) alongside Windows paths in all command samples.
  • Alternate the order of platform-specific examples so Linux/macOS is not always listed after Windows.
  • Include installation and usage instructions for Bash/Linux shell environments, not just Azure PowerShell.
  • Reference Linux tools and conventions (such as environment variables, file system paths) equally with Windows equivalents.
  • In 'Next steps', add links to Linux/Bash deployment guides if available, or clarify parity between platforms.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 section on setting environment variables. All provided shell examples use PowerShell syntax, and only Windows-specific methods (such as [System.Environment]::SetEnvironmentVariable) are mentioned. There are no examples or instructions for setting environment variables in Linux or macOS shells (e.g., Bash, zsh), and Windows tools and patterns are referenced exclusively.
Recommendations
  • Add equivalent Linux/macOS shell examples (e.g., export testEnvironmentVariable="Hello World!") alongside PowerShell commands.
  • Mention both Windows and Linux/macOS approaches when describing how to set environment variables at process, user, and machine/session levels.
  • Provide links to relevant Linux/macOS documentation (e.g., Bash environment variable guides) in addition to Windows/.NET references.
  • Ensure that examples and explanations are platform-neutral where possible, or clearly indicate when a command is platform-specific.
  • Consider presenting Linux/macOS examples before or alongside Windows examples to avoid a 'Windows-first' impression.
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-09 00:34
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 moderate Windows bias. PowerShell is given its own tab alongside Azure CLI and Azure Portal, but there is no explicit mention of Linux or macOS-specific workflows, nor are Bash or shell examples provided. Visual Studio Code is referenced as the primary editor, which is cross-platform, but the guidance and examples (such as right-clicking and F2 hotkey) are more familiar to Windows users. The Azure CLI examples are platform-agnostic, but the absence of explicit Linux/macOS shell examples or notes about cross-platform usage may leave non-Windows users underserved.
Recommendations
  • Add explicit Bash/shell examples for Linux/macOS users, especially where file redirection or command chaining is shown (e.g., use 'az group export --name ... > main.json' in a Bash context).
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide notes or tabs for Linux/macOS where appropriate.
  • When referencing Visual Studio Code features, mention that these features are available on all supported platforms, and clarify any differences in keyboard shortcuts (e.g., F2 may differ on macOS).
  • Include a section or tab for Linux/macOS users in the 'Export template and convert' section, or at least mention that the steps are the same across platforms.
  • Avoid putting PowerShell before Bash/Azure CLI unless there is a specific reason; consider listing Azure CLI (cross-platform) first, then PowerShell, then Portal.
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-09 00:34
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 notes on how to adapt commands for Windows PowerShell or Command Prompt. While Bash is presented as the default shell, Windows shells are mentioned as alternatives, and specific adaptations for PowerShell/cmd are included in several sections. However, there is no explicit Linux bias; rather, the page assumes Bash as the main shell, which is common on both Linux and macOS, but not on Windows by default. Windows-specific instructions are provided only as needed, and there are no PowerShell-exclusive examples or Windows-only tools discussed.
Recommendations
  • Provide explicit PowerShell and Command Prompt examples alongside Bash examples, not just adaptation notes.
  • Add a table or section comparing Bash, PowerShell, and Command Prompt syntax for common deployment scenarios.
  • Clarify that Bash is available on Windows via WSL or Git Bash, and provide installation guidance for users on Windows.
  • Ensure parity by including Linux/macOS-specific notes where relevant (e.g., file path formats, environment variable syntax).
  • Consider reordering sections to present Bash, PowerShell, and Command Prompt examples together for each scenario, rather than focusing on Bash first.
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-09 00:34
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 to the CLI example, despite PowerShell being primarily a Windows tool. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any examples tailored for Linux users. The documentation does not reference Linux tools or patterns, and the CLI example is generic rather than explicitly showing Bash or Linux terminal usage. The references to Cloud Shell are present but not explained in terms of platform parity.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including syntax and environment notes.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux/Mac users (e.g., differences in line continuation, installation).
  • Reduce emphasis on PowerShell or move PowerShell examples after CLI/Bash examples to avoid Windows-first perception.
  • Include notes or links for Linux users about running Bicep deployments from Bash, Zsh, or other common shells.
  • Reference Linux-specific documentation or troubleshooting guides where relevant.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents deployment commands for both Azure CLI and Azure PowerShell, but lists Azure CLI first. However, the PowerShell example is given equal prominence and detail. There is no mention of Linux-specific tools, shell environments, or examples using Bash or other Linux-native scripting. The 'Cloud Shell' reference is generic and does not clarify parity between Bash and PowerShell experiences. No explicit Windows-only tools are referenced, but the lack of Linux/Bash examples and the presence of PowerShell commands may imply a slight Windows bias.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, showing usage in Linux/macOS environments (e.g., with standard Bash syntax and line continuations).
  • Clarify that Azure CLI works cross-platform and provide notes or examples for Linux/macOS users, such as installation instructions or shell-specific tips.
  • Expand the 'Cloud Shell' reference to distinguish between Bash and PowerShell environments, and provide examples for both.
  • Consider including a table or section comparing command usage across Windows (PowerShell), Linux (Bash), and macOS, to reinforce cross-platform parity.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives where appropriate.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-subscription.md ...azure-resource-manager/bicep/deploy-to-subscription.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 PowerShell, but the PowerShell example is given equal prominence and is listed immediately after the CLI example. There are no explicit Linux-specific instructions or examples, and the documentation does not mention Bash, shell scripting, or Linux-specific considerations. The references to Cloud Shell do not clarify that it supports Bash and PowerShell, nor do they provide Bash-specific examples. This may lead to a perception that Windows/PowerShell usage is as primary or more primary than Linux/Bash usage, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
  • Add explicit Bash examples alongside Azure CLI examples, especially for parameter passing and scripting.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and highlight Bash usage for Linux users.
  • In the 'Deployment commands' section, mention that PowerShell is available on Linux, but also provide Bash script equivalents for common tasks.
  • In references to Cloud Shell, specify that both Bash and PowerShell are supported, and provide links or examples for Bash usage.
  • Consider listing Azure CLI/Bash examples before PowerShell examples to reflect the cross-platform nature of Azure CLI.
  • Add a note or section addressing Linux/macOS users, including any OS-specific considerations for Bicep deployments.
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-09 00:34
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, with PowerShell commands and patterns featured as primary options. There is a lack of explicit Linux or Bash shell examples, and installation instructions reference PowerShell modules without mentioning Linux-specific setup. The CLI examples are generic and do not clarify cross-platform usage, while PowerShell (a Windows-centric tool) is given equal or greater prominence throughout. No Linux-specific tools, shell patterns, or troubleshooting are discussed.
Recommendations
  • Add explicit Bash and Linux shell examples for all CLI commands, including environment setup and variable assignment.
  • Clarify that Azure CLI is cross-platform and provide instructions for installation and usage on Linux and macOS.
  • Include troubleshooting or configuration notes relevant to Linux environments (e.g., file permissions, path separators, environment variables).
  • Present CLI/Bash examples before PowerShell examples to reduce Windows-first bias.
  • Reference Linux-native editors and tools (e.g., Vim, Nano) when discussing editing Bicep files.
  • Mention that PowerShell Core is available cross-platform, but clarify differences in usage between Windows and Linux.
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-09 00:34
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. Azure PowerShell examples and references are given equal or greater prominence than Azure CLI (Linux) equivalents, with PowerShell-specific instructions, code samples, and tool usage appearing throughout. In several sections, PowerShell examples are presented before or alongside CLI examples, and Windows-centric tools (e.g., PowerShell, ARMClient in PowerShell mode) are referenced. There is a lack of explicit Linux shell (bash) deployment examples outside of Azure CLI, and no mention of Linux-native scripting environments or deployment patterns beyond the CLI. The deployment instructions for Bicep files use Azure PowerShell exclusively, with no az CLI or bash alternatives provided.
Recommendations
  • Provide Linux-native deployment instructions (e.g., az CLI commands or bash scripts) alongside PowerShell examples for deploying Bicep files.
  • Ensure that Azure CLI (Linux) examples are presented first or at least equally with PowerShell examples in all code sample sections.
  • Include explicit bash shell script examples for common deployment tasks, not just Azure CLI usage.
  • Reference Linux tools and patterns (e.g., bash, shell scripting, Linux containers) where appropriate, and clarify platform support for deployment scripts.
  • Add a section comparing development and troubleshooting workflows on Windows vs. Linux, highlighting any differences and best practices for each.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-tenant.md ...icles/azure-resource-manager/bicep/deploy-to-tenant.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 by presenting PowerShell examples and tools before their Linux-friendly equivalents (Azure CLI). The role assignment example lists PowerShell first, and references to PowerShell modules and commands are prominent. There is no mention of Linux-specific shell environments, nor are there Bash or cross-platform shell examples. The documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to emphasize platform neutrality.
  • Include explicit Bash shell examples for Linux/macOS users, especially for command-line operations.
  • Mention that Azure CLI is available on all major platforms and can be used in Bash, PowerShell, or CMD.
  • Reference Cloud Shell as a cross-platform option and clarify its shell support.
  • Avoid assuming users have access to PowerShell or Windows tools; provide parity in instructions for 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-configure-dev.md ...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 a Windows bias by prioritizing PowerShell examples and Windows-centric tooling. PowerShell scripts and Azure PowerShell commands are presented first and in greater detail, with CLI/bash examples following. Uploading scripts to Azure Storage is shown only with PowerShell, and Docker volume mount examples use Windows drive letter syntax (e.g., d:/docker), with no Linux path equivalents. There is a lack of Linux-native examples for common tasks such as uploading files or mounting directories, and Windows/PowerShell tooling is referenced more frequently than Linux alternatives.
Recommendations
  • Provide Linux/bash equivalents for all PowerShell script examples, especially for uploading files to Azure Storage (e.g., using az CLI or Azure Storage SDKs in bash).
  • Include Docker volume mount examples using Linux path syntax (e.g., /home/user/docker:/data) alongside Windows examples.
  • Present CLI/bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Reference Linux tools and patterns (e.g., bash scripting, az CLI) equally with Windows/PowerShell tools.
  • Clarify cross-platform compatibility in instructions and screenshots, noting any OS-specific differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for all major scenarios, maintaining parity in sample code. However, there are signs of Windows bias: PowerShell is consistently presented as an equal alternative to Bash, despite Bash being the default shell on most Linux systems. Windows-specific tools and APIs (e.g., CommandLineToArgvW, Connect-AzAccount, Start-Sleep) are referenced without mentioning Linux equivalents. PowerShell-specific error handling and scripting patterns are explained in detail, while Bash error handling is only briefly mentioned. The documentation sometimes references Windows APIs and tools before their Linux counterparts, and the use of PowerShell is normalized as a cross-platform scripting language, which may not reflect typical Linux workflows.
Recommendations
  • Explicitly mention that Bash/CLI scripting is the default and most common choice for Linux environments, and clarify PowerShell's cross-platform status.
  • When referencing Windows-specific APIs (e.g., CommandLineToArgvW), provide Linux equivalents or clarify their relevance only to Windows containers.
  • Expand Bash error handling guidance (e.g., set -e, trap) to match the detail given for PowerShell.
  • When discussing script execution, note differences in shell environments (e.g., Bash vs. PowerShell) and provide links to Linux shell scripting best practices.
  • Avoid normalizing PowerShell as the default scripting language for cross-platform scenarios; present it as an option, not the standard.
  • Where possible, include troubleshooting and debugging tips for Bash scripts, not just PowerShell.
  • Clarify that some referenced tools (e.g., Connect-AzAccount, Start-Sleep) are PowerShell-specific and suggest Linux alternatives if applicable.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/installation-troubleshoot.md ...re-resource-manager/bicep/installation-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing troubleshooting steps and examples that are specific to Windows environments. Commands such as 'where bicep' and references to the PATH variable use Windows syntax and locations (e.g., %USERPROFILE%\.Azure\bin), with no equivalent instructions for Linux or macOS. There are no examples using Linux tools (e.g., 'which bicep'), nor are Linux-specific installation paths or environment variable instructions provided.
Recommendations
  • Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' instead of 'where bicep').
  • Provide guidance on modifying the PATH variable for Linux/macOS (e.g., ~/.bashrc or ~/.zshrc).
  • Mention the default installation paths for Bicep CLI managed by Azure CLI on Linux/macOS.
  • Add screenshots or instructions relevant to Linux/macOS environments where applicable.
  • Ensure troubleshooting steps are presented for both Windows and Linux/macOS users, ideally side-by-side.
GitHub Create Pull Request
← Previous Page 15 of 52 Next →