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 376-400 of 1281 flagged pages
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-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. Azure PowerShell examples are consistently presented first in every code tab, followed by Azure CLI and then Azure portal (which is often not implemented for deployment stacks). The use of PowerShell-specific syntax and terminology (e.g., backticks for line continuation, PowerShell cmdlet names) presumes familiarity with Windows tooling. There is no mention of Linux-specific shell environments, nor are there any Bash or shell script examples, even though Azure CLI is cross-platform. The documentation refers to 'Azure PowerShell' and 'Azure CLI' as the main automation interfaces, but always lists PowerShell first, and some explanations are tailored to PowerShell usage patterns (e.g., piping output, debug mode).
Recommendations
  • Alternate the order of code tabs so that Azure CLI examples are presented first or equally with PowerShell, especially since Azure CLI is cross-platform and more commonly used on Linux.
  • Add explicit Bash/shell script examples for Azure CLI commands, showing line continuations with backslashes and usage in Linux/macOS terminals.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, and provide guidance for shell differences (e.g., quoting, environment variables).
  • Avoid PowerShell-specific terminology (such as 'cmdlet', backtick line continuation) in general explanations, or provide equivalent Bash/shell notes.
  • Where output examples are shown, include both PowerShell and Bash/CLI output formats if they differ.
  • Explicitly mention Linux and macOS support for Azure CLI and Bicep, and link to installation guides for these platforms.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/export-bicep-portal.md ...es/azure-resource-manager/bicep/export-bicep-portal.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 alongside Azure CLI when discussing export options, and by listing PowerShell before CLI in the 'Next steps' section. There are no explicit Linux-specific examples or mentions of Linux tools, and the instructions focus on the Azure portal (web-based, cross-platform) but do not provide parity guidance for Linux users who may prefer CLI workflows. The page does not mention platform-specific nuances or provide examples for Linux shell environments.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux users.
  • Add explicit Linux shell (bash) usage examples for exporting ARM templates and decompiling to Bicep, including command-line instructions.
  • Clarify that both Azure CLI and PowerShell are available on Windows, macOS, and Linux, and provide installation links for each platform.
  • Avoid listing PowerShell before CLI in sections where cross-platform parity is important, or alternate the order.
  • Include notes or sections addressing platform-specific considerations, such as file paths, shell syntax, or tool availability on Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific scenarios (e.g., WinRM on Windows VM), presenting Azure PowerShell examples alongside Azure CLI, and mentioning Windows tools and patterns. While Azure CLI is cross-platform, the inclusion and equal prominence of Azure PowerShell (primarily used on Windows) and references to Windows VM scenarios suggest a Windows-centric approach. There are no explicit Linux examples, nor are Linux-specific patterns or tools mentioned.
Recommendations
  • Add explicit Linux-focused examples, such as deploying secrets to Linux VMs or referencing Linux-specific quickstart templates.
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Include Bash script examples for common tasks, especially for secret retrieval and deployment, to demonstrate parity with PowerShell.
  • Reference Linux VM scenarios in the 'Related content' and example links, not just Windows VM scenarios.
  • Where PowerShell is used, note its availability on Linux and macOS, or provide alternative Bash/CLI instructions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md ...ep/linter-rule-admin-username-should-not-be-literal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias towards Windows by exclusively using admin user names ('adminUsername', 'administrator') that are typical for Windows systems, and by referencing the 'Microsoft.Compute/virtualMachines' resource without clarifying Linux-specific admin user name conventions. There are no examples or notes for Linux VM scenarios, such as using 'azureuser' or other common Linux admin names. The documentation implicitly assumes Windows patterns and does not provide parity for Linux users.
Recommendations
  • Include Linux-specific examples, such as using 'azureuser' or other typical Linux admin user names in the Bicep resource definitions.
  • Add a note or section clarifying differences between Windows and Linux VM admin user name conventions.
  • Ensure examples and explanations cover both Windows and Linux VM scenarios, or explicitly state when an example is Windows-specific.
  • Reference Linux VM documentation or provide links for further reading on Linux admin user name best practices.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.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. Windows-specific tools (Visual Studio, Chocolatey, Winget) and PowerShell examples are presented in detail, with multiple installation options and scripts. Windows installation methods are listed last but are more numerous and detailed than Linux/macOS. PowerShell is referenced as a primary deployment method, and Windows-centric patterns (e.g., registry edits, environment variable handling) are described. There is less emphasis on Linux/macOS package managers (e.g., apt, yum), and Linux installation is limited to a curl-based script. The troubleshooting and configuration sections also assume familiarity with Windows conventions.
Recommendations
  • Add Linux package manager installation instructions (e.g., apt, yum, zypper) for Bicep CLI where available.
  • Provide parity in installation options for Linux/macOS (e.g., Snap, Flatpak, MacPorts) similar to Chocolatey/Winget for Windows.
  • Include Bash and shell script examples for configuration and troubleshooting, not just PowerShell.
  • Balance the detail and number of installation methods across platforms; avoid listing more Windows options than Linux/macOS.
  • Highlight cross-platform editors and tools (e.g., VS Code) before platform-specific ones (e.g., Visual Studio).
  • Ensure troubleshooting and configuration steps include Linux/macOS equivalents, not just Windows registry or environment variable instructions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md ...anager/bicep/linter-rule-no-loc-expr-outside-params.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 Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell commands (e.g., New-AzDeployment), which are primarily used on Windows. There are no examples or mentions of cross-platform deployment tools such as Azure CLI, nor are Linux-specific instructions or patterns provided. The guidance and troubleshooting focus on PowerShell parameter naming conflicts, without addressing equivalent issues or solutions for Linux users or CLI users.
Recommendations
  • Add equivalent Azure CLI examples for deploying Bicep templates, including parameter naming considerations.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users.
  • Discuss any parameter naming conflicts or best practices relevant to Azure CLI or other cross-platform tools.
  • Reorder sections to present cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, to avoid Windows-first bias.
  • Include notes or examples for deploying from Linux/macOS environments, not just Windows/PowerShell.
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-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 PowerShell-specific instructions and links (such as the export guide), mentioning Azure PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command-line examples. There are no CLI (az) or Bash examples or references, and the only export instructions point to a PowerShell-centric workflow.
Recommendations
  • Provide equivalent Azure CLI (az) commands and examples alongside or before PowerShell instructions for all steps, especially for exporting blueprint definitions and configuring DenySettingsMode.
  • Update references and links to include both PowerShell and CLI documentation, or use cross-platform instructions where possible.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and clarify any OS-specific requirements.
  • Include sample Bash or shell scripts for Linux/macOS users where scripts or command-line actions are demonstrated.
  • Ensure that tool recommendations (e.g., for exporting, managing resources) are not Windows-centric and highlight cross-platform tools first.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-safe-dereference.md ...re-resource-manager/bicep/operator-safe-dereference.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 Windows bias in the 'Next steps' section, where Azure PowerShell is mentioned as a primary tool for deploying Bicep files, and Visual Studio Code is referenced as the editor for creating Bicep files. Azure CLI is mentioned, but Azure PowerShell appears first, and there is no mention of Linux-native editors or deployment patterns. The examples and instructions do not provide parity for Linux users or alternative workflows.
Recommendations
  • List Azure CLI before Azure PowerShell when describing deployment options, as CLI is cross-platform.
  • Explicitly mention Linux and macOS compatibility for both Azure CLI and Bicep tooling.
  • Include instructions or links for deploying Bicep files on Linux (e.g., using Bash scripts, VS Code on Linux, or other editors like Vim or Emacs).
  • Provide examples of Bicep deployment using Bash or Linux terminal commands.
  • Reference cross-platform editors and workflows, not just Visual Studio Code.
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-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 Windows bias by frequently mentioning Windows-specific tools and patterns (such as Azure PowerShell and Visual Studio Code commands with Windows keybindings), listing Windows options before Linux equivalents, and omitting explicit Linux-focused examples or alternatives. Azure PowerShell is referenced alongside Azure CLI, but Linux-specific shell usage (e.g., Bash) is not discussed. Keybindings are described as 'Ctrl+Shift+P on Windows and Linux,' but no Linux terminal examples are provided. Resource export examples and troubleshooting steps reference Windows-centric extensions and tools, with no mention of Linux-native workflows.
Recommendations
  • Provide explicit Linux shell (Bash) examples for resource export and Bicep operations, alongside Azure CLI and PowerShell.
  • List Azure CLI (cross-platform) before Azure PowerShell when presenting options, or present them together without ordering bias.
  • Include Linux-specific troubleshooting steps and workflows, such as using native editors (e.g., Vim, nano) and command-line utilities.
  • Add examples of using Bicep tooling in Linux environments, including installation and usage from Bash.
  • Clarify that Visual Studio Code keybindings are the same for Windows and Linux, but also mention alternative editors for Linux users.
  • Reference Linux-native tools or patterns where applicable, such as using shell scripts for automation.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-null-forgiving.md ...zure-resource-manager/bicep/operator-null-forgiving.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 references Azure CLI and Azure PowerShell as deployment options, listing Azure PowerShell (a Windows-centric tool) before Azure CLI. There are no explicit Linux shell (e.g., Bash) or cross-platform examples, nor is there mention of Linux-native tooling or deployment patterns. The guidance assumes familiarity with PowerShell and Visual Studio Code, both of which are more commonly associated with Windows environments, and does not provide parity for Linux users.
Recommendations
  • List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Provide explicit Bash or shell examples for deploying Bicep files on Linux.
  • Mention Linux-native editors (e.g., Vim, VS Code on Linux) when referencing file creation.
  • Clarify that both Azure CLI and PowerShell are available cross-platform, and provide links to Linux installation guides.
  • Add a section or note for Linux users outlining recommended tools and workflows.
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-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 consistently presenting Windows-specific instructions, examples, and tooling first or exclusively. PowerShell is used as the default shell in all command-line examples, and directory paths use Windows conventions (e.g., C:\msBuildDemo). Linux and macOS equivalents are only briefly mentioned in package lists, with no corresponding shell or filesystem examples. The project file examples and build instructions focus on Windows tools (Visual Studio, PowerShell, MSBuild.exe), with no demonstration of Linux-native workflows (e.g., Bash, Linux paths, dotnet CLI usage on Linux). Clean-up instructions and environment variable configuration also use Windows syntax and paths.
Recommendations
  • Provide parallel Linux/macOS examples for all command-line instructions, using Bash and POSIX paths (e.g., /home/user/msBuildDemo).
  • Include instructions for using common Linux shells (e.g., Bash, zsh) and terminal applications.
  • Show how to install prerequisites (e.g., .NET SDK, Bicep CLI) on Linux and macOS, including package manager commands.
  • Demonstrate project creation and build steps using Linux-native tools and commands (e.g., dotnet CLI, MSBuild via mono if applicable).
  • Add clean-up instructions using Linux commands (e.g., rm -rf ~/msBuildDemo).
  • Ensure environment variable configuration examples are provided for Linux/macOS (e.g., export BicepPath=/usr/local/bin/bicep).
  • Use cross-platform language in instructions and avoid assuming Windows as the default environment.
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-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 Windows bias primarily in the 'Next steps' section, where Azure PowerShell and Visual Studio Code are mentioned as the primary 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. All examples are platform-agnostic, but the tooling guidance favors Windows-centric tools and patterns.
Recommendations
  • Explicitly mention Linux-compatible editors (e.g., Vim, VS Code on Linux) and deployment workflows.
  • List Azure CLI before Azure PowerShell when describing deployment options, as CLI is cross-platform.
  • Include links or instructions for deploying Bicep files on Linux/macOS, such as using Bash scripts or shell commands.
  • Avoid implying Visual Studio Code is the only editor; mention alternatives and clarify cross-platform support.
  • Add a note that all examples work identically on Linux, macOS, and Windows.
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-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 exhibits Windows bias primarily in the 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI for deploying Bicep files, but Linux-specific deployment tools or workflows are not referenced. There are no explicit Linux shell examples, and the guidance implicitly prioritizes Windows-centric tools (PowerShell, Visual Studio Code) without mentioning alternatives or parity for Linux users.
Recommendations
  • Include explicit Linux shell (bash) examples for deploying Bicep files using Azure CLI.
  • Mention Linux-compatible editors (such as VS Code on Linux, Vim, or other IDEs) when discussing file creation.
  • Clarify that Azure CLI is cross-platform and provide instructions for both Windows and Linux environments.
  • Add a note or section on how to deploy Bicep files from Linux/macOS terminals, including any prerequisites or differences.
  • Ensure parity in tool recommendations, e.g., suggest both Azure CLI and PowerShell, but clarify platform compatibility.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Examples for deploying Bicep files with parameters are provided for both Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and its usage is shown extensively. File paths in PowerShell examples use Windows-style (C:\MyTemplates\...), and no Linux/macOS equivalents are provided. Visual Studio Code is referenced as the primary editor, which is cross-platform, but no mention is made of alternative editors or shell environments. The documentation does not provide Bash or Linux shell examples for deployment commands, nor does it show Linux-style file paths. The order of presentation puts PowerShell after CLI, but the PowerShell section is detailed and uses Windows conventions throughout.
Recommendations
  • Add Linux/macOS shell examples for deployment commands, using Bash syntax and Linux-style file paths (e.g., /home/user/templates/storage.bicep).
  • Include notes or examples for using Azure CLI and Bicep CLI in Linux/macOS environments, including file path conventions.
  • When showing PowerShell examples, clarify that these are for Windows and provide equivalent Bash examples for Linux/macOS users.
  • Mention cross-platform editors and shell environments where appropriate, not just Visual Studio Code.
  • Ensure that references to file paths and tooling are not exclusively Windows-centric; provide parity for Linux/macOS users.
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-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 exhibits a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and the documentation refers to Windows-specific tools and environment variables (e.g., %USERPROFILE%). There is a lack of parity in some explanations, such as more detailed Windows path examples compared to Linux. No Linux shell (bash) or scripting examples are provided, and the overall structure assumes familiarity with Windows conventions.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) examples first to avoid implicit prioritization of Windows.
  • Provide bash shell scripting examples alongside PowerShell, especially for automation scenarios.
  • Ensure that all path examples are equally detailed for Windows, Linux, and Mac, and use environment variables that are platform-appropriate (e.g., $HOME for Linux/Mac).
  • Explicitly state that Azure CLI commands work identically on Windows, Linux, and Mac, and provide any necessary platform-specific notes.
  • Where possible, avoid referencing Windows-specific tools or patterns exclusively; mention cross-platform alternatives.
  • Include a section or callout for Linux users, highlighting any differences or additional steps required.
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-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 mild Windows bias. While it does provide both Azure CLI and Azure PowerShell examples for deployment and cleanup, it references PowerShell and Windows tools (Visual Studio, Visual Studio Code) prominently and often lists PowerShell alongside or before CLI. The use of Visual Studio Code is cross-platform, but the documentation does not mention Linux or macOS environments, nor does it provide any Linux-specific guidance or examples (such as shell commands, terminal usage, or OS-specific installation notes). There is no mention of Linux tools, nor are there screenshots or instructions tailored to Linux users.
Recommendations
  • Explicitly mention that Visual Studio Code and the Bicep extension are available on Linux and macOS, and provide installation links or notes for those platforms.
  • Include screenshots or instructions showing the use of VS Code and Bicep extension on Linux (e.g., Ubuntu) and/or macOS.
  • Add examples of common Linux shell commands (e.g., using bash/zsh) for file creation, navigation, and running Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and may be preferred by Linux users, and consider listing CLI examples before PowerShell.
  • If any steps differ on Linux (e.g., right-click behavior, keyboard shortcuts), note these differences in the documentation.
  • Avoid referring to PowerShell as the default or primary method unless justified by usage statistics; otherwise, present CLI and PowerShell as equal options.
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.md ...ger/bicep/quickstart-create-bicep-use-visual-studio.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 Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Visual Studio (a Windows-centric IDE) for Bicep file authoring, listing Visual Studio and its extension as primary prerequisites, and presenting PowerShell examples alongside Azure CLI for deployment and cleanup. Windows tools and patterns are mentioned first or exclusively, with no mention of Linux-native editors (other than a brief link to VS Code), nor any Linux-specific considerations for Visual Studio usage. The page does not provide parity for Linux users in terms of setup or alternative workflows.
Recommendations
  • Add explicit guidance for Linux users, such as recommending VS Code (which is cross-platform) for Bicep authoring and linking to relevant setup instructions.
  • Clarify that Visual Studio is Windows-only and suggest alternatives for Linux and macOS users.
  • Provide Linux-specific instructions or notes for Bicep deployment, including shell commands and environment setup.
  • Reorder prerequisites and examples to present cross-platform tools (e.g., Azure CLI, VS Code) before Windows-specific ones.
  • Include screenshots and workflow steps for VS Code on Linux, and mention any differences in extension installation or usage.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all command examples, regardless of whether the tool is cross-platform. There are no explicit Linux/macOS path examples or notes on path differences. Additionally, the documentation references Visual Studio Code (cross-platform) but does not mention any Linux/macOS-specific considerations or alternatives. The PowerShell examples are presented before CLI examples, and the CLI examples also use Windows paths, which may confuse Linux/macOS users. There is also a reference to a PowerShell-specific tutorial for role assignment, with no mention of CLI or portal alternatives.
Recommendations
  • Provide both Windows and Linux/macOS path examples for all file operations (e.g., use C:\templates\main.bicep and ~/templates/main.bicep or ./templates/main.bicep).
  • Add notes or tabs clarifying file path differences between Windows and Linux/macOS.
  • When referencing tools, ensure parity by mentioning cross-platform alternatives (e.g., Azure CLI, Bash) alongside PowerShell.
  • In sections where PowerShell and CLI are presented, alternate the order or clarify that both are cross-platform, and highlight any OS-specific issues.
  • For role assignment and other tasks, provide CLI and portal links in addition to PowerShell tutorials.
  • Explicitly state that the Azure CLI and Bicep tools are cross-platform, and provide guidance for Linux/macOS users where behaviors or commands differ.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md ...e-manager/bicep/quickstart-create-deployment-stacks.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 provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is featured equally alongside CLI, and is referenced in the prerequisites and throughout. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially for users on Linux or macOS. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of alternative editors or shell environments. There are no explicit Linux shell examples (e.g., bash), nor are there notes about platform-specific differences or recommendations for Linux users.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and highlight this in the prerequisites.
  • Add explicit bash/zsh shell examples for Linux/macOS users, especially for command-line operations (e.g., using export for environment variables, using forward slashes, etc.).
  • Mention that PowerShell Core is available cross-platform, but note that Azure CLI is often preferred on Linux/macOS.
  • Include notes about installing Azure CLI and Bicep on Linux/macOS, with links to platform-specific instructions.
  • Suggest alternative editors (e.g., Vim, Sublime Text) for users who do not use Visual Studio Code.
  • Consider reordering examples to show Azure CLI (Linux/macOS friendly) first, or clarify that both CLI and PowerShell are supported equally across platforms.
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-09 00:34
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 examples, and relies heavily on PowerShell syntax and patterns throughout. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The use of PowerShell as the primary scripting language and the absence of references to Linux tools or shell environments indicate a Windows bias.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform and native to Linux) before PowerShell.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash shell usage (e.g., variable assignment, command chaining).
  • Include notes or sections for Linux/macOS users, such as differences in file paths, shell syntax, or environment setup.
  • Avoid exclusive reliance on PowerShell scripting patterns (e.g., use of backticks for line continuation, variable assignment syntax) and show equivalent Bash syntax where appropriate.
  • Add troubleshooting or setup tips for Linux environments, such as installation instructions for Azure CLI on Ubuntu or Fedora.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/create-custom-provider.md ...rce-manager/custom-providers/create-custom-provider.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations. However, in the PowerShell sections, it exclusively recommends and demonstrates the use of ARMClient, a Windows-centric tool (armclient.exe), without mentioning or providing Linux alternatives for REST operations. There is no mention of cross-platform REST tools (e.g., curl, httpie) in the prerequisites or examples, and ARMClient is not natively available for Linux. This creates a bias toward Windows users in the PowerShell workflow and REST tooling recommendations.
Recommendations
  • In the PowerShell prerequisites, mention and provide examples for cross-platform REST tools such as curl or httpie, which are available on both Windows and Linux.
  • Clarify whether ARMClient can be used on Linux (e.g., via .NET Core), or suggest alternative approaches for Linux users.
  • Add explicit Linux/WSL instructions for PowerShell users, or recommend using Azure CLI for Linux environments.
  • Where REST operations are demonstrated, provide examples using curl or httpie alongside ARMClient, especially for users who may not have ARMClient available.
  • Review and update documentation to ensure that all tooling and examples are accessible and functional on both Windows and Linux platforms.
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-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 demonstrates a Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI, referencing Windows-centric tools (Visual Studio, Visual Studio Code), and omitting explicit Linux/macOS shell examples. There is no mention of Bash, zsh, or Linux-specific patterns, and the guidance assumes familiarity with PowerShell syntax and Windows-based development environments. The order of examples often places PowerShell immediately after CLI, reinforcing Windows-first patterns.
Recommendations
  • Add explicit Bash/zsh examples for all CLI commands, showing syntax differences (e.g., variable assignment, quoting).
  • Include instructions for installing and using Bicep CLI and Azure CLI on Linux/macOS, with links to platform-specific guides.
  • Mention cross-platform editors such as VS Code for Linux/macOS, and clarify that Visual Studio is Windows-only.
  • Where PowerShell is referenced, clarify its cross-platform availability or provide alternative shell instructions.
  • Ensure screenshots and step-by-step instructions do not assume a Windows environment (e.g., file paths, UI elements).
  • Add a section or note highlighting Linux/macOS compatibility and any platform-specific caveats.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/create-storage-customer-managed-key.md ...ed-applications/create-storage-customer-managed-key.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 demonstrates a Windows bias in several ways. PowerShell is presented first and more prominently than Azure CLI for building Bicep files, and there are no explicit Linux or macOS-specific instructions or examples. The use of Visual Studio Code is platform-neutral, but the lack of mention of Linux-specific tools, shell environments, or alternative editors further reinforces a Windows-centric approach. Portal instructions are platform-agnostic, but command-line examples and tool recommendations favor Windows users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide shell-specific instructions where relevant.
  • Include Linux/macOS-specific notes or screenshots where UI or tool behavior may differ.
  • Recommend alternative editors (e.g., Vim, nano) for users who may not use Visual Studio Code.
  • Add a section or callout for Linux users, highlighting any differences in setup or usage.
  • Where PowerShell is referenced, clarify that Azure CLI is equally supported and may be preferred on non-Windows platforms.
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-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 are consistently presented before Azure CLI (which is more cross-platform), and instructions for opening terminals reference PowerShell and Visual Studio Code, which are more commonly used on Windows. The use of PowerShell-specific features (like splatting) and terminology (e.g., 'PowerShell terminal') further reinforces a Windows-centric approach. There is no mention of Linux-specific editors, shells (other than Bash), or alternative workflows for Linux users. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. No explicit Linux examples or troubleshooting notes are provided.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI examples so CLI is presented first in some sections, or default to CLI where possible.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for opening terminals on Linux (e.g., GNOME Terminal, Konsole) and macOS (Terminal.app).
  • Add notes or links for installing and using Bicep and Azure CLI on Linux and macOS, including editor recommendations (e.g., Vim, Emacs, or VS Code on Linux).
  • Avoid PowerShell-specific terminology (like 'PowerShell terminal') in general instructions; use neutral terms such as 'terminal' or 'command prompt'.
  • Where PowerShell splatting or other Windows-centric features are used, provide equivalent CLI or Bash scripting examples for Linux users.
  • Add troubleshooting or environment setup notes for Linux and macOS users, especially for file paths, permissions, and shell differences.
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-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 are consistently presented before Azure CLI examples, and PowerShell-specific concepts (such as splatting) are explained in detail, while Linux/Bash equivalents are not. Visual Studio Code is recommended as the editor, but no mention is made of alternative editors more common on Linux. There is a brief mention of a Git Bash for Windows-specific error, but no discussion of Linux shell issues. The documentation does not provide Linux-specific troubleshooting, nor does it highlight differences in experience between Windows and Linux environments.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Include explanations of Bash/Linux shell concepts (such as environment variables, quoting, and line continuation) similar to the PowerShell splatting explanation.
  • Mention alternative editors (e.g., Vim, Nano, Emacs) for Linux users alongside Visual Studio Code.
  • Provide troubleshooting tips for common Linux shell issues (e.g., file permissions, path separators, environment variable expansion) in addition to the Git Bash for Windows note.
  • Clarify that all CLI commands are cross-platform and highlight any platform-specific caveats.
  • Add a note or section on how to install and use Azure CLI and Bicep on Linux distributions, including package manager instructions.
GitHub Create Pull Request
← Previous Page 16 of 52 Next →