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 126-150 of 1281 flagged pages
Azure Resource Manager Linter rule - no location expressions outside of parameter default values ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority View Details →
Scanned: 2026-01-11 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 provides deployment guidance focused exclusively on Azure PowerShell commands, which are primarily used on Windows. It does not mention or provide examples for cross-platform tools such as Azure CLI, nor does it address Linux or macOS usage scenarios. The deployment command discussion is Windows-centric and omits Linux equivalents, creating a bias toward Windows users.
Recommendations
  • Add equivalent Azure CLI examples for deployment scenarios, including how to handle parameter naming conflicts.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users.
  • Reorder deployment tool discussions to present Azure CLI before or alongside PowerShell, emphasizing platform neutrality.
  • Include notes or examples for deploying Bicep templates from Linux/macOS environments.
  • Clarify any differences in parameter handling between PowerShell and CLI to help users on all platforms avoid conflicts.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all examples, referencing Windows PowerShell and Azure PowerShell as primary tools, and omitting explicit Linux/macOS shell examples (e.g., Bash, sh). While Azure CLI is cross-platform, the CLI examples also use Windows paths and do not provide Linux/macOS path alternatives or notes. The documentation does not mention or show Linux-specific tools, nor does it provide parity in instructions for Linux users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples in all code snippets (e.g., C:\templates\main.bicep and ~/templates/main.bicep).
  • Explicitly state that Azure CLI commands work on all platforms, and show Bash shell syntax (with export, $(), etc.) where appropriate.
  • Add notes or tabs for Linux/macOS users, especially where file paths or environment variables differ.
  • Mention and link to installation instructions for Azure CLI and PowerShell on Linux/macOS.
  • Avoid assuming Windows as the default environment; use neutral language and examples where possible.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide Bash equivalents for common tasks.
GitHub Create Pull Request
Azure Resource Manager Create a custom resource provider ...rce-manager/custom-providers/create-custom-provider.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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, ensuring cross-platform coverage for most users. However, the PowerShell section recommends and demonstrates the use of ARMClient (armclient.exe), a Windows-specific tool, without mentioning Linux-compatible alternatives or how to use ARMClient on Linux. There are no Bash/cURL or other native Linux shell examples for REST calls, and the documentation does not clarify ARMClient's cross-platform support. This may disadvantage Linux users who do not use PowerShell or ARMClient.
Recommendations
  • Add explicit Bash/cURL examples for REST operations alongside Azure CLI and PowerShell, especially in sections where ARMClient is used.
  • Clarify whether ARMClient is cross-platform and, if not, suggest Linux-compatible alternatives (e.g., httpie, curl, or using Azure CLI's az rest).
  • When introducing tools like ARMClient, mention installation and usage instructions for both Windows and Linux.
  • Consider including a table or section comparing available tools for REST operations on both Windows and Linux.
  • Review the PowerShell examples to ensure they do not assume a Windows environment (e.g., file paths, executable extensions) and provide notes for Linux PowerShell users if needed.
GitHub Create Pull Request
Azure Resource Manager Bicep functions for Bicep parameters files ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias, particularly in the 'readEnvironmentVariable' section, where all examples for setting environment variables use PowerShell commands and .NET APIs, which are specific to Windows environments. There are no equivalent Linux/macOS shell examples (e.g., Bash export), and Windows tools and patterns are mentioned exclusively and first. No Linux or cross-platform guidance is provided for environment variable manipulation.
Recommendations
  • Add equivalent Linux/macOS shell examples (e.g., export VAR=value) alongside PowerShell commands for setting environment variables.
  • Mention both Windows and Linux/macOS methods when discussing environment variable manipulation, and avoid presenting Windows tools exclusively or first.
  • Where .NET/PowerShell APIs are referenced, provide analogous commands or references for Bash/zsh or other common shells.
  • Explicitly state that the examples are platform-specific and provide parity for all major supported platforms.
  • Consider including a table or section summarizing environment variable setting commands across Windows, Linux, and macOS.
GitHub Create Pull Request
Azure Resource Manager Decompile a JSON Azure Resource Manager template to Bicep ...ain/articles/azure-resource-manager/bicep/decompile.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned prominently and often before Linux alternatives. Examples for exporting templates are given for Azure CLI, Azure PowerShell, and Azure portal, but PowerShell (a Windows-first tool) is featured in its own tab and described in detail. Visual Studio Code, a cross-platform editor but with a strong Windows user base, is referenced repeatedly for Bicep operations. There is no explicit mention of Linux shell equivalents (e.g., Bash, zsh) or guidance for Linux users beyond Azure CLI, nor are Linux-specific patterns or troubleshooting tips provided.
Recommendations
  • Add explicit Linux shell (Bash/zsh) examples for exporting and decompiling templates, including file redirection and command chaining.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide notes on platform differences if any exist.
  • Include alternative editors (such as Vim, Emacs, or VS Code on Linux) for Bicep editing and decompilation, or at least acknowledge their use.
  • Add troubleshooting tips for common Linux issues (e.g., file permissions, path separators) when working with Bicep CLI.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell), or group them together with clear platform guidance.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files with the Azure CLI ...in/articles/azure-resource-manager/bicep/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Bash First Windows Shell Notes Windows Shell Examples
Summary
The documentation page primarily presents Azure CLI usage in Bash, with explicit notes and examples for Windows shells (PowerShell and cmd) only as secondary clarifications. While the main examples are Bash-centric, the documentation does provide guidance for Windows users, but Linux/Bash is clearly prioritized. There are no PowerShell-only examples, but Windows shell usage is repeatedly mentioned as an alternative, and some syntax differences are explained for PowerShell/cmd. No Linux-specific tools or patterns are missing, but the documentation could better balance parity by providing explicit Linux and Windows examples side-by-side.
Recommendations
  • Provide parallel example blocks for Bash (Linux/macOS) and PowerShell/cmd (Windows) for each major command or pattern.
  • Use tabs or callouts to let users select their shell/OS, ensuring equal visibility for Linux and Windows users.
  • Clarify that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash), and provide explicit instructions for running Bash on Windows if relevant.
  • Where syntax differs, show both versions in code blocks rather than only describing the difference in text.
  • Add a summary table of shell/OS compatibility for Azure CLI commands at the start of the page.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to resource groups ...ure-resource-manager/bicep/deploy-to-resource-group.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 associated with Windows. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The documentation does not clarify cross-platform compatibility for the commands, and references to Cloud Shell do not specify shell type. This may lead to a perception of Windows bias, especially for users seeking Linux-first guidance.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, demonstrating deployment from a Linux environment.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide notes on any OS-specific considerations.
  • When referencing Cloud Shell, specify both Bash and PowerShell options, and provide examples for each.
  • Consider listing Azure CLI (bash) examples before PowerShell examples, or provide a tabbed interface with clear OS/shell distinctions.
  • Mention Linux-native tools or patterns where relevant, such as scripting deployments with bash or using automation tools common in Linux environments.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to management group ...e-resource-manager/bicep/deploy-to-management-group.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment command examples for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence and detail as the CLI example. There is no mention of Linux-specific shell usage (e.g., Bash), nor any explicit Linux or macOS command-line patterns. The references to Cloud Shell do not clarify that it supports Bash or PowerShell, and no Linux-specific instructions or troubleshooting are provided. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not address potential differences or considerations for Linux users.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, including syntax for common Linux shells.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide notes on any OS-specific considerations.
  • Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide links or examples for each.
  • Ensure troubleshooting and usage notes include Linux-specific guidance where relevant (e.g., file paths, environment variables).
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or group them together with clear OS applicability.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to subscription ...azure-resource-manager/bicep/deploy-to-subscription.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 PowerShell is featured as a primary tab and is given equal prominence to Azure CLI. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as Bash scripts or references to Linux tools). The documentation does not clarify that Azure CLI is cross-platform and does not provide guidance for Linux users who may not have PowerShell installed.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide Bash shell examples alongside Azure CLI commands to demonstrate usage in Linux environments.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users.
  • Add a note or section about using Azure Cloud Shell, which is platform-agnostic and accessible from any browser.
  • Ensure that references to deployment tools do not imply Windows as the default platform, and avoid listing PowerShell before CLI unless justified by usage statistics.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, often listing PowerShell first or equally, and providing detailed PowerShell-specific instructions (such as module installation and usage). There are no explicit Linux shell examples (e.g., Bash), and the CLI instructions do not clarify cross-platform usage or mention Linux-specific considerations. The documentation assumes familiarity with PowerShell and Windows-centric tooling, while Linux users may need additional context or instructions.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and clarify any platform-specific differences.
  • Add Bash shell examples for key operations, especially for scripting and programmatic evaluation of what-if results.
  • Include installation instructions for Azure CLI on Linux and macOS, not just a generic link.
  • Mention alternative editors (e.g., VS Code on Linux/macOS) and cross-platform usage where relevant.
  • Where PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS, or provide Bash equivalents.
  • Ensure that cleanup and automation examples include Bash and/or other Linux-native tooling.
GitHub Create Pull Request
Azure Resource Manager Export Bicep files in Azure portal ...es/azure-resource-manager/bicep/export-bicep-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by mentioning Azure PowerShell alongside Azure CLI as the primary command-line export options, but does not provide explicit Linux-oriented examples or highlight Linux-native tools. The order of mention ('Azure CLI', then 'Azure PowerShell') is reasonable, but the lack of Linux-specific instructions or screenshots, and the absence of explicit cross-platform guidance, may leave Linux users underserved.
Recommendations
  • Add explicit notes clarifying that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Include example commands for exporting ARM templates using Azure CLI on Linux (e.g., bash shell), and clarify how to download and decompile them to Bicep.
  • Provide screenshots or terminal snippets showing the process on Linux systems.
  • Mention installation and usage differences for Azure CLI and PowerShell on Linux versus Windows, if relevant.
  • Ensure REST API examples include curl or other Linux-native tools.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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 bias towards Windows and PowerShell environments. PowerShell examples are provided first and in greater detail, including all deployment and upload steps. Scripts for uploading files to Azure Storage use PowerShell exclusively, with no Bash or Linux-native alternatives. Docker volume mounting examples use Windows-style paths (e.g., d:/docker), and instructions reference 'host drive letter', which is specific to Windows. There are no Linux-specific examples for file upload or Docker volume mounting, and the overall flow assumes familiarity with Windows tools and conventions.
Recommendations
  • Provide Bash or Azure CLI examples for uploading files to Azure Storage, especially for Linux/macOS users.
  • Include Docker volume mounting examples using Linux/macOS path syntax (e.g., /home/user/docker:/data) alongside Windows examples.
  • Present PowerShell and CLI/Bash examples in parallel, or alternate which comes first to avoid implicit prioritization.
  • Clarify that instructions apply to both Windows and Linux, and explicitly mention platform differences where relevant.
  • Add notes or sections for Linux/macOS users, including common troubleshooting tips and environment setup steps.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority View Details →
Scanned: 2026-01-11 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. PowerShell examples and tooling are presented alongside Azure CLI, but PowerShell is often given equal or greater prominence, and Windows-centric tools (e.g., Azure PowerShell, ARMClient in PowerShell context) are used for deployment and management tasks. Script deployment instructions are provided only for Azure PowerShell, with no Linux-native shell or cross-platform alternatives (e.g., Bash, Bash+az CLI, or Linux scripting). There is no explicit example of deploying Bicep files using Bash or Linux-native commands, and PowerShell is referenced for authentication and management tasks before CLI equivalents. The documentation does not provide parity for Linux-first or cross-platform workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for deploying Bicep files, using az CLI commands (e.g., az group create, az deployment group create).
  • Present CLI and PowerShell examples in parallel, rather than PowerShell-first or exclusively.
  • Include instructions for script deployment and management using Linux-native tools and workflows.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
  • Clarify that both Azure CLI and PowerShell are supported and provide guidance for users on both platforms.
  • Where ARMClient is referenced, provide CLI usage examples or alternatives.
  • Ensure that all code samples and management instructions are available for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault to pass a secret as a parameter during Bicep deployment ...es/azure-resource-manager/bicep/key-vault-parameter.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific scenarios (such as WinRM on Windows VM) are referenced in the introduction, and Azure PowerShell examples are provided alongside Azure CLI throughout. The PowerShell examples use Windows-centric patterns (e.g., backticks for line continuation, ConvertTo-SecureString), and the only quickstart template linked is for Windows VM. There is no mention of Linux VM scenarios, nor are Linux-specific tools or shell patterns (e.g., Bash, sh) referenced. The ordering of examples sometimes places PowerShell before CLI, and Windows tools are referenced without Linux equivalents.
Recommendations
  • Add explicit Linux VM scenarios and quickstart links (e.g., SSH on Linux VM with Key Vault secrets).
  • Ensure Azure CLI examples use Bash-style line continuations and variables to demonstrate Linux shell usage.
  • Balance example ordering by consistently presenting Azure CLI (cross-platform) before PowerShell, or clarify platform applicability.
  • Reference Linux tools or patterns where relevant (e.g., Bash, sh, environment variables) and note cross-platform compatibility.
  • Include notes or sections on how these steps apply to Linux environments, especially for VM property settings and secret retrieval.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot problems with Bicep installation ...re-resource-manager/bicep/installation-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 command-line instructions and environment variable paths that are specific to Windows (e.g., 'where bicep', '%USERPROFILE%\.Azure\bin'), without mentioning or providing equivalent Linux/macOS commands (such as 'which bicep', '$HOME/.azure/bin'). The troubleshooting steps and examples focus on Windows tools and patterns, omitting Linux alternatives.
Recommendations
  • Include Linux/macOS equivalents for all command-line instructions, such as using 'which bicep' instead of 'where bicep'.
  • Mention Linux/macOS environment variable paths (e.g., '$HOME/.azure/bin') alongside Windows paths.
  • Clarify steps for modifying the PATH variable on Linux/macOS (e.g., editing ~/.bashrc or ~/.zshrc).
  • Add troubleshooting notes relevant to Linux/macOS users, especially for installation conflicts and VS Code settings.
  • Ensure all examples and instructions are presented for both Windows and Linux/macOS, or clearly indicate platform-specific steps.
GitHub Create Pull Request
Azure Resource Manager Migrate Azure resources and JSON ARM templates to use Bicep .../main/articles/azure-resource-manager/bicep/migrate.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias by frequently mentioning Azure PowerShell and Windows-specific tools before or alongside cross-platform alternatives, such as Azure CLI. Examples and instructions often reference Windows keybindings and tools, with little to no explicit mention of Linux-specific workflows, shell environments, or alternative editors. There are no Linux-specific examples or guidance for common Linux scenarios, and Windows-centric resource types (e.g., DependencyAgentWindows) are referenced without Linux equivalents.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell examples for Azure CLI and Bicep commands.
  • Mention Linux resource types and extensions (e.g., DependencyAgentLinux) when discussing VM extensions.
  • Clarify that Azure CLI and Visual Studio Code are cross-platform, and include Linux/macOS installation and usage notes where relevant.
  • Add Linux/macOS specific keyboard shortcuts and workflows in addition to Windows ones.
  • Reference Linux-native editors (e.g., Vim, nano) and how Bicep files can be authored/tested in those environments.
  • Ensure parity in troubleshooting and rollback guidance for Linux-based Azure resources.
GitHub Create Pull Request
Azure Resource Manager Install Bicep tools .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias. Windows tools (Chocolatey, Winget, PowerShell) are given prominent installation methods for Bicep, and the PowerShell example is more detailed than the Linux/macOS equivalents. The Windows section lists three installer options before mentioning manual install, while Linux and macOS focus on manual and Homebrew methods. In the Azure PowerShell section, only Windows command syntax is shown, with no mention of Linux PowerShell or cross-platform alternatives. The order of presentation in some sections (e.g., Azure CLI install links) lists Windows first.
Recommendations
  • Add Linux and macOS PowerShell installation instructions or clarify cross-platform PowerShell support.
  • Balance the detail level in installation instructions across platforms; e.g., provide Linux package manager options (apt, yum) if available.
  • Present installation options for all platforms in parallel, rather than listing Windows tools first.
  • Include Bash and shell script examples for Windows (using WSL) where appropriate.
  • Explicitly mention cross-platform compatibility for CLI commands and tools.
  • Where Windows-specific tools are mentioned (Chocolatey, Winget), consider listing Linux/macOS equivalents (Homebrew, Snap, etc.) in the same section.
GitHub Create Pull Request
Azure Resource Manager Migrate blueprints to deployment stacks ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2026-01-11 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 in the main migration steps and linking to a PowerShell-specific export guide, without mentioning or providing equivalent Azure CLI or Linux shell examples. The instructions for configuring DenySettingsMode mention both Azure CLI and Azure PowerShell, but the primary export workflow is PowerShell-centric. No Linux or cross-platform command-line examples are provided, and the sample migration file is platform-neutral (Bicep), but the supporting steps are Windows-oriented.
Recommendations
  • Add Azure CLI examples for exporting blueprint definitions and assignments, alongside PowerShell instructions.
  • Update links to reference both PowerShell and Azure CLI documentation for import/export operations.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
  • Ensure that instructions for configuring DenySettingsMode include full Azure CLI command syntax, not just PowerShell.
  • Review all referenced guides to ensure Linux parity and cross-platform accessibility.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias: examples and instructions consistently use Windows paths, PowerShell commands, and Windows-specific tooling (Visual Studio, MSBuild.exe, win-x64 packages). Linux equivalents (e.g., bash, Linux paths, linux-x64 packages) are mentioned only in passing, and there are no step-by-step instructions or code samples for Linux or macOS users. The workflow assumes a Windows environment, making it less accessible for developers on other platforms.
Recommendations
  • Provide parallel step-by-step instructions for Linux and macOS, using bash/zsh commands and appropriate file paths (e.g., /home/user/msBuildDemo).
  • Include examples using the Azure.Bicep.CommandLine.linux-x64 and Azure.Bicep.CommandLine.osx-x64 NuGet packages in project file samples.
  • Show how to run MSBuild and dotnet CLI commands on Linux/macOS terminals, including installation notes for MSBuild on non-Windows platforms.
  • Replace or supplement PowerShell commands with bash equivalents (e.g., mkdir, cd, rm -rf) for directory and file management.
  • Clarify cross-platform compatibility in the prerequisites and throughout the guide, ensuring that Linux/macOS users are not left to infer the necessary changes.
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • Explicitly mention any platform-specific caveats or requirements (e.g., setting BicepPath, executable permissions) for non-Windows systems.
GitHub Create Pull Request
Azure Resource Manager Bicep null-forgiving operator ...zure-resource-manager/bicep/operator-null-forgiving.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell before Azure CLI in the deployment instructions, and by referencing Visual Studio Code (a Microsoft tool commonly associated with Windows) as the primary editor for Bicep files. There are no explicit Linux examples or mentions of Linux-native tools or workflows, and the guidance assumes familiarity with Windows-centric tooling.
Recommendations
  • Mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Include explicit instructions or examples for deploying Bicep files on Linux systems, such as using Bash or shell scripts.
  • Reference alternative editors (such as Vim, Emacs, or VS Code on Linux) to demonstrate cross-platform compatibility.
  • Clarify that Bicep and its tooling are supported on Linux and macOS, not just Windows.
  • Add links or notes about installing and using Bicep on Linux, including package managers and setup steps.
GitHub Create Pull Request
Azure Resource Manager Bicep safe-dereference operator ...re-resource-manager/bicep/operator-safe-dereference.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio Code (a Microsoft product) as the primary tools for deploying and authoring Bicep files. Azure CLI is mentioned, but Azure PowerShell is listed first, and there are no explicit Linux-specific instructions or examples. The guidance assumes familiarity with Windows-centric tools and patterns, and does not mention Linux-native editors or shell environments.
Recommendations
  • Provide explicit Linux shell (bash/zsh) deployment examples using Azure CLI.
  • Mention and link to Linux-native editors (e.g., Vim, Emacs, VS Code on Linux) for authoring Bicep files.
  • Ensure that instructions for deploying Bicep files are platform-agnostic or include both Windows and Linux steps.
  • List Azure CLI before Azure PowerShell when describing deployment options, as CLI is cross-platform.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, shell differences).
GitHub Create Pull Request
Azure Resource Manager Bicep accessor operators ...icles/azure-resource-manager/bicep/operators-access.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell and Azure CLI as deployment methods, but lists Azure PowerShell before Azure CLI. There are no explicit Linux-specific examples, nor is there mention of Linux shell usage (e.g., Bash) or cross-platform deployment patterns. The examples and instructions do not show parity for Linux users, and the guidance implicitly prioritizes Windows tooling and workflows.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide example deployment commands using Bash (Linux/macOS) and PowerShell (Windows), or clarify that Azure CLI commands work in Bash.
  • List Azure CLI before Azure PowerShell in 'Next steps' to avoid Windows-first impression.
  • Add notes or links for Linux users on installing and using Azure CLI.
  • Ensure that all instructions and examples are platform-neutral or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager Bicep logical operators ...cles/azure-resource-manager/bicep/operators-logical.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 the methods to deploy Bicep files, but lists Azure PowerShell before Azure CLI and does not provide any explicit Linux-specific instructions or examples. There is an implicit Windows bias in deployment tooling, as PowerShell is traditionally associated with Windows, and no mention is made of Bash, shell scripts, or Linux-native workflows. All examples are Bicep code, so there is no direct OS-specific scripting, but the guidance for running examples is Windows-centric.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux (Bash).
  • List Azure CLI before Azure PowerShell when describing deployment options, as CLI is more universal.
  • Add a section or note on how to deploy Bicep files from Linux/macOS environments, including sample Bash commands.
  • Clarify that Bicep itself is platform-agnostic and provide parity in instructions for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager Parameters in Bicep ...in/articles/azure-resource-manager/bicep/parameters.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as a deployment method, with PowerShell listed explicitly and linked before any Linux-specific or cross-platform alternatives. There are no explicit Linux shell examples, nor is there mention of Linux-specific tools or workflows. The documentation does not provide parity in examples or guidance for Linux users, and the inclusion of PowerShell (a Windows-centric tool) without equivalent Bash or Linux shell examples reinforces the bias.
Recommendations
  • Include Linux/Bash shell examples for deploying Bicep files, especially in sections discussing deployment.
  • Mention cross-platform tools (such as Azure CLI) before Windows-specific tools like PowerShell, or present them together with equal prominence.
  • Add explicit guidance or links for Linux users, such as instructions for using Bash or shell scripts to deploy Bicep files.
  • Ensure that all example commands and workflows are shown for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Azure Resource Manager Bicep spread operator ...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority View Details →
Scanned: 2026-01-11 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 in the 'Next steps' section by listing Azure PowerShell before Azure CLI and referencing Visual Studio Code as the primary editor, which is often associated with Windows workflows. There are no explicit Linux-specific instructions or examples, and no mention of Linux-native tools or deployment patterns. The examples and instructions do not address Linux environments or shell usage, and PowerShell is mentioned before CLI, reinforcing a Windows-centric approach.
Recommendations
  • List Azure CLI before Azure PowerShell when suggesting deployment methods, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that all examples and deployment steps work equally on Linux, macOS, and Windows.
  • Include instructions or links for deploying Bicep files from Bash or other Linux shells.
  • Reference alternative editors (such as Vim, Emacs, or VS Code on Linux) to avoid implying Visual Studio Code is Windows-only.
  • Add a note or section highlighting cross-platform compatibility and any Linux-specific considerations.
GitHub Create Pull Request
← Previous Page 6 of 52 Next →