Azure Resource Manager

1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

492 issues found
Showing 126-150 of 492 flagged pages
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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. Credential precedence and authentication examples prioritize Azure CLI and Azure PowerShell, both of which are Windows-centric tools (especially PowerShell). The credential precedence list and explanatory text mention Azure PowerShell before other cross-platform options. There are no explicit Linux/macOS examples or references to Linux-native authentication workflows, and no mention of platform-specific considerations for Linux/macOS users.
Recommendations
  • Include explicit examples or notes for Linux/macOS users, such as using Azure CLI (which is cross-platform) and Environment credentials.
  • Reorder credential precedence examples to show cross-platform options (AzureCLI, Environment, ManagedIdentity) before Windows-specific ones (AzurePowerShell, VisualStudio).
  • Add a section or note clarifying that Azure CLI and Bicep are cross-platform, and provide links or instructions for installation and usage on Linux/macOS.
  • Mention any platform-specific differences or caveats, such as authentication flows or environment variable setup for EnvironmentCredential on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to create a new resource group .../azure-resource-manager/bicep/create-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is always presented immediately after Azure CLI, and with equal prominence. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there any mention of platform differences or requirements for PowerShell on non-Windows systems. The documentation assumes familiarity with PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for non-Windows users.
  • Add Bash shell examples for Linux/macOS users, especially for multi-line commands.
  • Clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is typically more native.
  • Consider listing Azure CLI examples before PowerShell, or grouping platform-specific instructions.
  • Add a note about prerequisites for each platform (e.g., installing Azure CLI on Linux/macOS).
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in Bicep | Microsoft Docs ...manager/bicep/deployment-script-bicep-configure-dev.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias. PowerShell is used extensively for scripting and resource deployment examples, including uploading files to Azure Storage and deploying Bicep files, with no equivalent Bash or cross-platform CLI examples provided. Docker volume mounting instructions use Windows-style paths and drive letters (e.g., d:/docker), which are not applicable to Linux/macOS. The order of presentation often favors PowerShell/Windows approaches first, and Linux/macOS users must infer or adapt steps themselves.
Recommendations
  • Provide Bash/Azure CLI equivalents for all PowerShell deployment and upload commands, especially for uploading files to Azure Storage and deploying Bicep files.
  • Include Docker volume mounting examples using Linux/macOS paths (e.g., /home/user/docker:/data) alongside Windows examples.
  • Clarify cross-platform compatibility for all steps, explicitly noting differences or requirements for Linux/macOS users.
  • Where PowerShell is used, mention how to run these scripts on Linux/macOS (e.g., via pwsh), or provide alternative Bash scripts.
  • Reorder examples or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric steps.
GitHub Create Pull Request
Azure Resource Manager Data types in Bicep ...in/articles/azure-resource-manager/bicep/data-types.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is mostly platform-neutral, but it contains a notable Windows bias in the 'Integers' section, where PowerShell is mentioned as the example deployment tool and its integer range limitation is discussed. No equivalent mention is made of Linux/macOS tools (such as Azure CLI or Bash), nor are their behaviors or limitations described. Additionally, links to Bicep CLI installation reference Visual Studio Code and its Bicep extension, which is often associated with Windows, and do not mention cross-platform installation or usage.
Recommendations
  • Include information about deploying Bicep files using Azure CLI on Linux/macOS, and specify any integer range limitations or differences for those platforms.
  • When discussing command-line tools, mention both PowerShell (Windows) and Azure CLI (cross-platform) equally, or provide examples for both.
  • Add installation and usage instructions for Bicep CLI on Linux/macOS, and clarify that Visual Studio Code and the Bicep extension are available cross-platform.
  • Review all tool references to ensure parity and avoid implying Windows is the default or only supported platform.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides extensive examples for Azure CLI and Azure PowerShell, but PowerShell examples are shown alongside CLI in nearly every section and sometimes first. There are no explicit Linux/macOS shell examples (e.g., bash, zsh), and PowerShell is a Windows-centric tool (despite cross-platform support, most Linux users prefer bash). Visual Studio Code is mentioned, but not in a way that addresses OS-specific usage. The cleanup section refers to 'Azure CLI or Azure PowerShell', but the CLI tab is labeled 'CLI' rather than 'Azure CLI', which could cause confusion. No Linux-specific patterns, troubleshooting, or environment setup are discussed.
Recommendations
  • Add explicit bash/zsh examples for Linux/macOS users, especially for scripting and output parsing.
  • Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes (e.g., quoting, environment variables).
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path separators).
  • Mention cross-platform editors (e.g., VS Code on Linux/macOS) and provide links to relevant setup guides.
  • Reorder examples so Azure CLI (which is cross-platform) appears before PowerShell, or alternate the order.
  • Label tabs and code blocks clearly as 'Azure CLI (Windows/macOS/Linux)' and 'PowerShell (Windows/macOS/Linux)' to reduce ambiguity.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 (Linux-friendly) and Azure PowerShell (Windows-centric) examples for deployment scripts in Bicep, but consistently presents PowerShell examples immediately after CLI, and in some cases, only PowerShell deployment commands are shown for deploying Bicep files. Script management sections give equal coverage to Azure CLI and PowerShell, but deployment instructions are PowerShell-only. There is no explicit Linux shell (bash) or macOS Terminal example for deploying Bicep files, nor are there instructions for using non-Windows tools (e.g., Bash, zsh, or cross-platform alternatives) to deploy scripts. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash (Linux/macOS) examples for deploying Bicep files, using 'az deployment group create' or similar Azure CLI commands.
  • Present CLI (cross-platform) examples before PowerShell examples to reduce Windows-first bias.
  • Clarify that Azure CLI commands work on Linux/macOS and provide terminal instructions for those platforms.
  • Where PowerShell scripts are shown for deployment, provide equivalent Bash/CLI commands.
  • Mention cross-platform development environments and tools (e.g., VS Code, Docker, native shells) for script development and deployment.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on Visual Studio, which is primarily a Windows application, and does not provide Linux/macOS alternatives for authoring Bicep files. While deployment instructions include both Azure CLI and PowerShell, the authoring workflow is Windows-centric, and Linux users are only briefly referenced via a link to Visual Studio Code documentation.
Recommendations
  • Explicitly state that Visual Studio is Windows-only and recommend Visual Studio Code for Linux/macOS users.
  • Add a short section summarizing how Linux/macOS users can author Bicep files (e.g., using VS Code or other editors).
  • Ensure that all critical steps (authoring, deployment, cleanup) have clear Linux/macOS-compatible instructions or links.
  • Consider reordering or visually separating Windows-only instructions from cross-platform steps.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. File path examples consistently use Windows-style paths (e.g., C:\templates\main.bicep) without showing Linux/macOS alternatives. While both Azure PowerShell and Azure CLI are covered, PowerShell examples and references appear first in most sections, and PowerShell is a Windows-centric tool. There is no explicit mention or example of Linux/macOS file paths, shell environments, or platform-specific considerations for CLI usage. The 'Grant access' section links only to a PowerShell tutorial, omitting CLI or portal alternatives. There is a note about a known issue with PowerShell, but no guidance for Linux users. Overall, Linux/macOS users can complete the tasks, but may encounter friction due to Windows-centric patterns and lack of parity in examples.
Recommendations
  • Provide Linux/macOS file path examples (e.g., /home/user/templates/main.bicep) alongside Windows paths.
  • Explicitly mention that Azure CLI commands work cross-platform and note any platform-specific differences.
  • Include links to CLI and portal tutorials for role assignment, not just PowerShell.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to reflect its cross-platform nature.
  • Add notes or callouts for any platform-specific issues or workarounds, especially for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Publish modules to private module registry ...ce-manager/bicep/quickstart-private-module-registry.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for all commands, but PowerShell is a Windows-centric tool and is presented as a primary alternative to Azure CLI. The tooling recommendations focus on Visual Studio and Visual Studio Code, which, while cross-platform, are often associated with Windows workflows. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific patterns or considerations. The use of PowerShell throughout, and the absence of Linux/macOS shell alternatives, creates friction for non-Windows users.
Recommendations
  • Add Bash shell examples alongside Azure CLI commands to demonstrate usage in typical Linux/macOS environments.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, and provide any OS-specific notes if needed.
  • Mention cross-platform editors (e.g., VS Code) explicitly as available on Linux/macOS, and consider referencing alternatives like Vim or JetBrains IDEs.
  • If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide Bash equivalents.
  • Ensure screenshots and instructions do not assume Windows-only workflows.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Azure Resource Manager templates ...source-manager/templates/deployment-script-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows/PowerShell bias. PowerShell examples are consistently presented first and in greater detail, with inline and external script samples almost exclusively using PowerShell (.ps1) syntax. The main walkthrough for running scripts in Cloud Shell uses Azure PowerShell, and the troubleshooting and output handling sections focus on PowerShell variables and patterns. While Azure CLI/bash is supported and referenced, CLI examples are less prominent, and Linux/macOS users may need to infer or adapt from PowerShell-centric instructions.
Recommendations
  • Provide parallel Azure CLI/bash examples for every PowerShell example, including inline and external script samples.
  • Alternate the order of examples so that Azure CLI/bash is sometimes shown first.
  • Expand the walkthroughs and troubleshooting sections to include CLI/bash-specific instructions and output handling.
  • Clarify that both PowerShell and CLI scripts run in Linux containers, and highlight cross-platform development environments.
  • Add explicit notes or sections for Linux/macOS users, including tips for adapting PowerShell-centric instructions.
GitHub Create Pull Request
Azure Resource Manager Develop ARM templates for cloud consistency ...source-manager/templates/template-cloud-consistency.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias, especially in its scripting and tooling examples. PowerShell commands are frequently presented, often before or alongside Azure CLI equivalents, but Linux/macOS shell alternatives are not shown. Several examples reference Windows-specific paths, scripts, and VM images, with little mention of Linux equivalents. The use of Windows-centric tools (PowerShell, Visual Studio) is emphasized, and examples for Linux VM images, shell scripts, or Linux-based development environments are absent.
Recommendations
  • Provide Bash or shell script equivalents for PowerShell commands, especially for tasks like verifying template functions, listing resource providers, VM images, and VM sizes.
  • Include Linux VM image examples alongside Windows VM image references in ARM template samples.
  • Reference Linux/macOS-compatible development tools (such as VS Code, JetBrains IDEs) in the testing and automation section, not just Visual Studio.
  • Show examples of using Linux shell scripts with Custom Script Extensions, not only PowerShell scripts.
  • Ensure that documentation sections presenting commands or scripts alternate or balance Windows and Linux/macOS examples, or present them side-by-side.
  • Explicitly mention cross-platform support for Azure CLI and provide guidance for Linux/macOS users where workflows differ.
GitHub Create Pull Request
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is mentioned first in both prerequisites and example commands for creating and updating template specs. The documentation references Windows-specific cmdlets (Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) in parameter descriptions, and PowerShell examples are shown before Azure CLI equivalents. However, Azure CLI examples are provided, and no steps are strictly Windows-only; Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Reference Azure CLI commands for obtaining tenantId and objectId (e.g., az account show, az ad user show) in parameter descriptions, not just PowerShell cmdlets.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Where possible, use generic terminology (e.g., 'command line') instead of 'PowerShell' when not required.
GitHub Create Pull Request
Azure Resource Manager Create and deploy Azure deployment stacks in Bicep ...cles/azure-resource-manager/bicep/deployment-stacks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides Azure PowerShell and Azure CLI examples for all operations, with PowerShell examples always shown first. There is a strong emphasis on PowerShell, which is traditionally a Windows-centric tool, and no explicit mention of Linux/macOS shell environments or examples using Bash, zsh, or other native Linux tools. There are no references to Linux-specific patterns, nor any guidance for Linux/macOS users on installing or using PowerShell cross-platform. The documentation assumes familiarity with PowerShell syntax and conventions, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly state that Azure PowerShell is available cross-platform and provide installation links for Linux/macOS.
  • Add example command lines using Bash/zsh syntax for Azure CLI, including common shell idioms (e.g., environment variables, piping output to jq).
  • Where PowerShell is referenced, clarify that it is not Windows-only and provide brief instructions for Linux/macOS users.
  • Consider showing Azure CLI examples first, as CLI is natively cross-platform and more familiar to Linux/macOS users.
  • Add a short section or note on platform compatibility for all tools mentioned.
GitHub Create Pull Request
Azure Resource Manager Bicep CLI commands ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of Windows-style file paths (e.g., c:\jsontemplates) in all command examples, even when the commands are cross-platform. Linux/macOS equivalents (e.g., /home/user/jsontemplates) are not provided alongside Windows examples. Windows paths are shown first and exclusively in most cases. The install, upgrade, and list-versions commands are only available via Azure CLI, which is cross-platform, but the documentation does not clarify OS-specific installation steps or nuances. The cache location section does mention Linux and Mac paths, but only after Windows. No PowerShell-specific commands are present, but Windows conventions dominate the examples.
Recommendations
  • Provide Linux/macOS path examples (e.g., /home/user/jsontemplates) alongside Windows paths in all CLI command samples.
  • Explicitly state that file paths should be adapted to the user's OS, and provide a note or table mapping Windows and Linux/macOS conventions.
  • When listing cache locations or file system paths, present all OSes equally, or use a tabbed format for each OS.
  • Clarify any OS-specific installation or usage differences, especially for commands only available via Azure CLI.
  • Avoid using Windows paths as the default in mixed-OS documentation.
GitHub Create Pull Request
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure CLI as the primary authentication methods, listing Azure PowerShell before Linux-friendly alternatives, and omitting explicit Linux/macOS-specific instructions or examples. The credential precedence and authentication sections focus on Windows-centric tools, with no mention of Linux-specific workflows or parity for non-Windows users.
Recommendations
  • Include explicit examples for Linux/macOS environments, such as bash shell usage and authentication workflows.
  • Clarify that Azure CLI is cross-platform and provide instructions for installing and using it on Linux/macOS.
  • Mention alternative credential sources (e.g., Environment variables, Managed Identity) that are platform-agnostic and highlight their use on Linux/macOS.
  • Avoid listing Windows tools (Azure PowerShell) before cross-platform options unless contextually necessary.
  • Add a note or section on platform compatibility for all authentication methods.
GitHub Create Pull Request
Azure Resource Manager Bicep functions for Bicep parameters files ...ource-manager/bicep/bicep-functions-parameters-file.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias in the 'readEnvironmentVariable' section, where all examples for setting environment variables use PowerShell syntax and reference .NET APIs. There are no equivalent Linux/macOS shell examples (e.g., Bash, export), nor is there mention of cross-platform methods for setting environment variables. This may create friction for users on non-Windows platforms.
Recommendations
  • Add Linux/macOS shell examples (e.g., export VARIABLE=value) alongside PowerShell examples for setting environment variables.
  • Clarify that environment variable setting is platform-dependent and provide guidance for Bash/zsh users.
  • Reference cross-platform documentation for environment variable management.
  • Avoid referencing Windows/.NET-specific APIs (like Environment.SetEnvironmentVariable) without Linux/macOS alternatives.
GitHub Create Pull Request
Azure Resource Manager Data types in Bicep ...in/articles/azure-resource-manager/bicep/data-types.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, but there is a notable Windows bias in the 'Integers' section, where PowerShell is mentioned as the example SDK/command-line tool for Bicep deployments and its integer range limitation is described. No equivalent mention is made of Linux/macOS tools (such as Azure CLI), nor is their behavior or limitations discussed. This may lead Linux/macOS users to believe that PowerShell is the primary or only supported tool, or leave them uncertain about integer handling on their platforms.
Recommendations
  • Add information about integer range limitations for other deployment tools, such as Azure CLI (az), especially on Linux/macOS.
  • Explicitly mention that Bicep can be deployed using cross-platform tools, and provide parity in examples and tool references.
  • Where PowerShell is referenced, also reference Azure CLI and note any differences in behavior or limitations.
  • Consider including a table or section comparing deployment tool behaviors across platforms.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files with the Azure CLI ...in/articles/azure-resource-manager/bicep/deploy-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Bash First Windows Shell Notes Windows Shell Formatting
Summary
The documentation page primarily presents Azure CLI examples using Bash syntax and notes that adjustments are needed for Windows PowerShell or Command Prompt. It provides some guidance for Windows shell users (cmd/PowerShell) on parameter formatting, but all code samples are Bash-first, with Windows-specific instructions relegated to explanatory text. There are no full PowerShell/cmd examples, and Linux is referenced only in passing (e.g., cloud-init for Linux VMs).
Recommendations
  • Provide full PowerShell and Command Prompt examples alongside Bash samples, especially for parameter passing and variable usage.
  • Clearly label each example with the intended shell/platform.
  • Add a dedicated section for Windows shell users, outlining common differences and pitfalls.
  • Ensure parity in explanations for both Linux/macOS and Windows environments, including file path formats and quoting/escaping rules.
  • Consider including macOS-specific notes if there are any platform-specific caveats.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal or sometimes slightly more detailed coverage. PowerShell examples and explanations are consistently presented alongside Azure CLI, but CLI is not always prioritized or explained first. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there explicit mentions of Linux environments or tooling. The documentation assumes users are familiar with PowerShell, which is primarily a Windows tool, and does not offer parity for Linux-native scripting or package management. REST API and SDK options are mentioned, but not with platform-specific guidance.
Recommendations
  • Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide Bash-specific usage notes where relevant.
  • Include references to Linux/macOS environments in installation and usage instructions (e.g., package managers like apt, yum, or Homebrew for Azure CLI).
  • Add a note clarifying PowerShell Core is available cross-platform, but CLI is the default/preferred option for Linux/macOS.
  • Provide troubleshooting or environment setup tips for Linux/macOS users, especially for file paths and shell differences.
  • Where programmatic examples are given, show how to parse JSON output in Bash (e.g., using jq) in addition to PowerShell object handling.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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. While it acknowledges Azure CLI and Linux support, PowerShell examples and tooling are frequently presented first or exclusively, and deployment/management instructions are PowerShell-centric. There is a lack of parity in showing Linux/macOS terminal commands for deploying Bicep files, and PowerShell tools are referenced more often than their CLI equivalents.
Recommendations
  • Provide Linux/macOS shell (bash) examples for deploying Bicep files, using Azure CLI (e.g., az deployment group create).
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in deployment and management sections.
  • Add explicit instructions for Linux/macOS users, including prerequisites and environment setup.
  • Where PowerShell scripts are shown, offer equivalent bash/CLI commands.
  • Clarify that Azure CLI and PowerShell are both supported and highlight any platform-specific limitations.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in Bicep | Microsoft Docs ...manager/bicep/deployment-script-bicep-configure-dev.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is used extensively for scripting and deployment examples, with no equivalent Bash or Linux-native scripting for resource group and storage operations. Windows-style file paths and Docker volume mapping are shown first and exclusively (e.g., d:/docker:/data), and Linux/macOS alternatives are not provided. The upload and deployment steps rely on Azure PowerShell cmdlets, with only passing mention that Azure CLI or portal could be used, but no concrete CLI/bash examples. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/CLI workflows.
Recommendations
  • Provide Azure CLI/bash equivalents for all PowerShell deployment and upload scripts, including resource group creation, storage account/file share setup, and file uploads.
  • Show Docker volume mapping examples using Linux/macOS paths (e.g., /home/user/docker:/data) alongside Windows examples.
  • Present CLI/bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users where workflows differ.
  • Include screenshots or terminal output from Linux/macOS environments, not just Windows.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot problems with Bicep installation ...re-resource-manager/bicep/installation-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (e.g., 'where' command, %USERPROFILE% path), omitting equivalent Linux/macOS commands (such as 'which' or 'echo $HOME'), and presenting Windows instructions before considering other platforms. No Linux/macOS examples are provided for troubleshooting multiple Bicep CLI installations or modifying the PATH variable.
Recommendations
  • Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' instead of 'where bicep', and reference $HOME/.azure/bin for the Azure CLI-managed Bicep CLI location).
  • Provide explicit steps for modifying the PATH variable on Linux/macOS (e.g., editing ~/.bashrc, ~/.zshrc).
  • Add screenshots or descriptions relevant to Linux/macOS environments where appropriate.
  • Ensure troubleshooting steps are platform-agnostic or clearly separated by OS.
GitHub Create Pull Request
Azure Resource Manager Migrate blueprints to deployment stacks ...cles/azure-resource-manager/bicep/migrate-blueprint.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary tool for blueprint export, with no mention of Azure CLI or Linux/macOS alternatives. The export instructions link to a PowerShell-specific guide and do not provide equivalent CLI commands or workflows for non-Windows platforms. All migration steps and examples are platform-neutral after the export, but the initial step creates friction for Linux/macOS users.
Recommendations
  • Include Azure CLI instructions for exporting blueprint definitions alongside PowerShell steps.
  • Update links to reference both PowerShell and CLI documentation, or provide a cross-platform export guide.
  • Explicitly state that migration can be performed from any OS and highlight platform-agnostic tools where possible.
GitHub Create Pull Request
Azure Resource Manager Linter rule - no location expressions outside of parameter default values ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides deployment guidance and troubleshooting specifically for Azure PowerShell commands, referencing only Windows-centric tools and patterns. No examples or equivalent instructions are given for Linux/macOS users (e.g., Azure CLI or Bash), and the PowerShell deployment scenario is discussed exclusively and in detail.
Recommendations
  • Add equivalent deployment instructions and parameter naming guidance for Azure CLI (az deployment group/sub/mg/tenant create) with Linux/macOS shell examples.
  • Explicitly mention cross-platform tools and note any differences in parameter naming conflicts for Azure CLI.
  • Present examples for both PowerShell and CLI side-by-side, or clarify which instructions apply to which platforms.
  • Avoid assuming PowerShell as the default deployment tool; acknowledge platform diversity.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Use MSBuild tasks to convert Bicep files and parameters to JSON ...les/azure-resource-manager/bicep/msbuild-bicep-file.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents Windows and PowerShell-based instructions and examples first, with directory paths and commands tailored to Windows environments (e.g., C:\msBuildDemo, PowerShell commands). There are no explicit Linux/macOS shell examples for project setup, file creation, or cleanup, and the Classic framework section is Windows-only. While cross-platform NuGet packages are mentioned, practical Linux/macOS usage is not demonstrated.
Recommendations
  • Add Linux/macOS shell (bash/zsh) equivalents for all PowerShell commands (e.g., directory creation, navigation, cleanup).
  • Show Linux/macOS file paths (e.g., /home/user/msBuildDemo) alongside Windows paths.
  • Include explicit instructions for running MSBuild/dotnet CLI on Linux/macOS, including any prerequisites or differences in usage.
  • Present examples for Linux/macOS first or side-by-side with Windows, especially in quickstart and setup sections.
  • Clarify that Visual Studio Code and .NET CLI are cross-platform, and provide links or notes for Linux/macOS installation.
GitHub Create Pull Request
← Previous Page 6 of 20 Next →