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 26-50 of 1281 flagged pages
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced first and more frequently than Azure CLI, especially for tasks like retrieving tenantId and objectId, and for creating template specs. The instructions for obtaining Azure Active Directory object IDs exclusively mention PowerShell cmdlets (Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) without CLI or cross-platform alternatives. Visual Studio Code is mentioned as an editor, but no Linux-specific tools or workflows are highlighted. There are no explicit Linux examples or shell commands, and the overall flow assumes familiarity with Windows-centric tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for retrieving tenantId and objectId (e.g., az account show, az ad user show, az ad sp show).
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention cross-platform editors (such as Vim, nano, or gedit) alongside Visual Studio Code.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide shell syntax examples (bash/zsh) where appropriate.
  • Add notes or sections for Linux users, including file management and environment setup tips.
  • Ensure screenshots and instructions do not assume a Windows environment.
GitHub Create Pull Request
Azure Resource Manager Bicep CLI commands ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
High 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 exhibits Windows bias in several ways: file path examples consistently use Windows-style paths (e.g., c:\jsontemplates) without providing Linux/macOS equivalents; installation and usage instructions frequently reference Azure PowerShell and Windows-specific conventions before or instead of Linux alternatives; and some commands (e.g., install, upgrade, list-versions) are only shown for Azure CLI, which is cross-platform but often associated with Windows. Cache location examples do mention Linux and Mac, but command examples and file paths are predominantly Windows-centric.
Recommendations
  • For every example using a Windows file path (e.g., c:\jsontemplates), provide a Linux/macOS equivalent (e.g., /home/user/jsontemplates) side-by-side.
  • When referencing installation methods, mention Linux and macOS processes equally alongside Windows and PowerShell.
  • Ensure that command examples and explanations do not assume Windows as the default environment; use generic or platform-neutral paths and conventions where possible.
  • Add explicit notes or tabs for Linux/macOS users where behavior, paths, or conventions differ.
  • In sections about named pipes and sockets, clarify platform differences and provide examples for both Windows and Unix-like systems.
  • Review all examples and ensure parity in coverage and clarity for Linux/macOS users.
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-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 Windows bias, particularly in the 'readEnvironmentVariable' section, where all examples for setting environment variables use PowerShell commands and .NET APIs. There are no equivalent Linux/macOS shell examples (e.g., Bash export), and Windows tools and patterns are mentioned exclusively. This may hinder Linux users' understanding and parity.
Recommendations
  • Add equivalent Linux/macOS shell (e.g., Bash) examples for setting environment variables, such as 'export testEnvironmentVariable="Hello World!"'.
  • Include notes on differences in environment variable persistence and scope between Windows and Linux/macOS.
  • Present both Windows (PowerShell/CMD) and Linux/macOS (Bash/Zsh) commands side by side or in tabs to ensure parity.
  • Reference relevant Linux documentation (e.g., man pages for 'export', 'env') alongside Windows/.NET references.
  • Review other sections for implicit Windows assumptions and add cross-platform clarifications where needed.
GitHub Create Pull Request
Azure Resource Manager Data types in ARM templates ...rticles/azure-resource-manager/templates/data-types.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the example command-line tool for ARM template deployment and integer range limitations, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific examples or parity guidance are provided.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell when discussing deployment tools and parameter limitations.
  • Clarify whether integer range limitations apply to Azure CLI, Bash, or other Linux-native tools.
  • Add a section or note explicitly addressing cross-platform usage and differences, ensuring Linux users are equally supported.
  • Present examples and tool references in a neutral or parallel order (e.g., "PowerShell or Azure CLI") rather than Windows-first.
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-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 moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned and described before or more prominently than Linux alternatives. Examples are given for both Azure CLI and Azure PowerShell, but PowerShell is featured as a primary tab and is not explicitly contextualized as Windows-only. Visual Studio Code (a cross-platform tool, but often associated with Windows) is referenced repeatedly, and Windows-specific patterns (e.g., right-click, F2 hotkey) are described without Linux alternatives. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific workflows or editors.
Recommendations
  • Add explicit Bash shell examples for decompiling and exporting templates, especially for Linux users.
  • Clarify that Azure PowerShell is primarily a Windows tool and suggest cross-platform alternatives (e.g., Azure CLI, Bash).
  • When describing editor actions (e.g., renaming symbols), mention equivalent shortcuts or actions for Linux/Mac (e.g., VS Code on Linux uses the same F2 hotkey, but right-click behavior may differ).
  • Include references to Linux-native editors (e.g., Vim, Nano) or workflows for users who do not use Visual Studio Code.
  • Ensure that cross-platform tools are described before or alongside Windows-specific tools, and avoid implying Windows as the default environment.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Bash First Windows Shell Guidance Windows Shell Examples Windows Shell Format Notes
Summary
The documentation primarily provides Azure CLI examples in Bash syntax, with explicit notes and guidance for users on Windows (PowerShell/cmd) about how to adapt commands and parameter formats. While Linux/Bash is the default, Windows shell usage is acknowledged and supported, but examples and instructions for Windows shells are secondary and less detailed. There are no PowerShell/cmd-specific code blocks, and Linux tools/patterns are not highlighted beyond Bash.
Recommendations
  • Add explicit PowerShell and Command Prompt (cmd) code blocks for key examples, especially where syntax differs significantly.
  • Provide a table or section summarizing differences in parameter passing and quoting between Bash, PowerShell, and cmd.
  • Include Linux-specific notes or troubleshooting tips, such as file path conventions or permissions.
  • Ensure parity by giving equal prominence to Windows and Linux shell usage in examples and explanations.
  • Consider adding a 'Platform differences' section early in the document to clarify how commands and file handling vary across OSes.
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-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 provides deployment command examples for both Azure CLI and PowerShell, but the PowerShell example is given equal prominence as the CLI example, and there is no mention of Linux-specific shell usage (e.g., Bash) or cross-platform considerations. The references to Azure CLI are platform-neutral, but PowerShell is traditionally a Windows-first tool, and no explicit Linux/Bash examples or notes are provided. There is also no mention of running these commands in a Linux environment or Cloud Shell context, nor are there instructions for using Bash scripts or Linux-native tools.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Add notes or examples for running deployment commands in Azure Cloud Shell (which is Linux-based by default).
  • If PowerShell is mentioned, clarify that Azure PowerShell is available on Linux/macOS and provide installation or usage notes for those platforms.
  • Consider listing Azure CLI (Bash) examples before PowerShell to avoid implicit Windows-first ordering.
  • Include troubleshooting or environment setup notes for Linux users, such as authentication methods or file path differences.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents deployment commands for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given its own section and example, while Linux-native tools or shell examples (e.g., Bash) are not provided. The Azure CLI example is present, but there is no explicit mention of running it on Linux or macOS, nor are there Bash script examples or references to Linux-specific usage patterns. The 'Next steps' and references focus on PowerShell and CLI, with PowerShell listed after CLI, but no Linux shell or automation examples are included.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, showing usage in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include references or links to Linux/macOS setup guides for Azure CLI.
  • If mentioning PowerShell, also mention Bash or other Linux-native shells where appropriate.
  • Ensure parity in troubleshooting and environment setup instructions for Linux users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents deployment commands for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and no explicit Linux shell examples (e.g., Bash, zsh) are provided. There is no mention of Linux-specific considerations, nor are there examples using Linux-native tools or scripting patterns. The page assumes parity between Azure CLI and PowerShell, but PowerShell is still primarily a Windows tool, and its inclusion without Linux alternatives or notes may suggest a Windows bias.
Recommendations
  • Add explicit Bash/zsh shell examples for Azure CLI commands, showing usage in typical Linux environments.
  • Clarify that Azure CLI works cross-platform and is the recommended tool for Linux/macOS users.
  • Note that PowerShell is available on Linux, but is less commonly used than Bash/zsh; consider providing Bash equivalents for any PowerShell examples.
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI via package managers.
  • Review linked articles to ensure Linux parity and avoid Windows-centric instructions or screenshots.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to tenant ...icles/azure-resource-manager/bicep/deploy-to-tenant.md
High 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 presenting PowerShell examples and tools before or alongside Azure CLI, referencing PowerShell-specific commands (e.g., New-AzRoleAssignment, New-AzTenantDeployment), and using Windows-centric terminology and patterns. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The documentation assumes familiarity with PowerShell and Windows tools, potentially disadvantaging Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples for all command-line instructions, especially for Azure CLI usage.
  • Where PowerShell commands are given, provide equivalent Bash/CLI commands side-by-side, and clarify which platforms each example targets.
  • Avoid using Windows-centric terminology (e.g., PowerShell) as the default; instead, present Azure CLI (cross-platform) examples first.
  • Include notes or sections on running these commands from Linux/macOS environments, including any platform-specific considerations.
  • Reference Cloud Shell as a cross-platform option and clarify its underlying shell (Bash or PowerShell).
GitHub Create Pull Request
Azure Resource Manager Create and deploy Azure deployment stacks in Bicep ...cles/azure-resource-manager/bicep/deployment-stacks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. Azure PowerShell is featured prominently and consistently, with PowerShell examples always presented before Azure CLI equivalents. The use of PowerShell (a Windows-centric tool) and the explicit mention of PowerShell-specific switches and output formats reinforce this bias. There are no Linux-specific shell examples (e.g., Bash), nor is there any mention of Linux-specific tooling or considerations. The CLI examples are generic and do not address platform-specific nuances, such as shell quoting or environment setup differences. The documentation assumes familiarity with PowerShell patterns and terminology, which may disadvantage Linux users.
Recommendations
  • Provide Bash-specific examples alongside PowerShell and Azure CLI, especially for common Linux scenarios.
  • Clarify that Azure CLI commands are cross-platform and provide notes on shell differences (e.g., quoting, line continuation) between Windows (CMD/PowerShell) and Linux (Bash/zsh).
  • Avoid presenting PowerShell examples first; alternate the order or present CLI examples first to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI is available and supported on Linux/macOS, and link to installation instructions for those platforms.
  • Where PowerShell output is shown, also show equivalent CLI output in JSON or other formats commonly used on Linux.
  • Add troubleshooting or environment setup notes for Linux users, especially where file paths, permissions, or shell syntax may differ.
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-12 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 exhibits a noticeable Windows bias. PowerShell is heavily featured throughout, with most scripting and deployment examples using PowerShell syntax and Azure PowerShell cmdlets. File upload instructions and Bicep deployments are shown using PowerShell, and Docker volume mount examples use Windows-style paths (e.g., d:/docker:/data) without showing Linux equivalents. There are no Bash or Linux shell examples for uploading files or deploying resources, and Linux-specific instructions are missing or mentioned only as alternatives. The page assumes familiarity with Windows tools and patterns, and Linux parity is not fully achieved.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell scripts, especially for uploading files and deploying Bicep templates.
  • Show Docker volume mount examples using Linux paths (e.g., /home/user/docker:/data) alongside Windows paths.
  • Explicitly mention Linux prerequisites and environment setup steps, such as using Bash or zsh terminals.
  • Ensure that instructions for using Azure CLI are as detailed and prominent as those for PowerShell.
  • Add notes or callouts for platform-specific differences, such as file path formats and shell commands.
  • Consider reordering sections so that Azure CLI and Bash examples are presented before or alongside PowerShell examples, not after.
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-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 the Azure portal (which is commonly used on Windows) before mentioning Azure CLI or REST API. PowerShell is a Windows-centric tool, and its mention alongside CLI as the primary export methods suggests a preference for Windows workflows. There are no explicit Linux-specific examples or references to Linux-native tools or patterns, and the order of presentation puts Windows tools first.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide usage examples for Linux environments.
  • Include screenshots or instructions that show the export process on Linux systems (e.g., using Azure CLI in a Bash shell).
  • Avoid implying that PowerShell is the default or preferred method; clarify platform compatibility for each tool.
  • Add a section on exporting Bicep files using Linux-native workflows, if possible, or clarify any limitations.
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-12 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., using 'where bicep', referencing '%USERPROFILE%\.Azure\bin', and omitting Linux/macOS equivalents such as 'which bicep' or '$HOME/.azure/bin'). There are no examples or troubleshooting steps for Linux or macOS users, and Windows tools and patterns are mentioned exclusively.
Recommendations
  • Include equivalent Linux/macOS commands (e.g., 'which bicep' instead of only 'where bicep').
  • Provide instructions for updating PATH on Linux/macOS (e.g., modifying ~/.bashrc or ~/.zshrc).
  • Mention the default installation paths for Bicep CLI on Linux/macOS (e.g., $HOME/.azure/bin).
  • Add troubleshooting steps and screenshots relevant to Linux/macOS environments.
  • Ensure all steps and examples are presented for both Windows and Linux/macOS, or clearly indicate platform-specific instructions.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides installation instructions for Bicep tools across Windows, Linux, and macOS, but Windows-specific tools and patterns (such as Chocolatey, Winget, and PowerShell scripts) are given more prominence and detail. The Windows section lists three separate installer options (Windows Installer, Chocolatey, Winget) before presenting a manual PowerShell method, while Linux and macOS primarily focus on direct binary downloads and Homebrew. PowerShell is used heavily for Windows manual installation, and Windows installer options are described in more detail than Linux equivalents. In some sections, Windows instructions or tools are listed before Linux/macOS, and Windows-centric terminology (e.g., %UserProfile%) is used without equivalent Linux/macOS context.
Recommendations
  • Provide parity for Linux/macOS package managers (e.g., apt, yum, zypper for Linux; MacPorts for macOS) if available, or explicitly state their absence.
  • Balance the detail level across platforms: expand Linux/macOS instructions to match the depth of Windows installer options, including troubleshooting and verification steps.
  • List installation methods in a consistent order (e.g., alphabetical by OS or grouped by method) to avoid implicit prioritization of Windows.
  • Where PowerShell is used for Windows, consider providing equivalent shell scripts for Linux/macOS for manual installation steps.
  • Clarify platform-specific environment variable usage (e.g., %UserProfile% for Windows, $HOME for Linux/macOS) in all relevant sections.
  • Add troubleshooting notes and screenshots for Linux/macOS installation similar to those provided for Windows.
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-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 moderate Windows bias. Windows-specific scenarios (such as WinRM on Windows VM) are referenced in the introduction and linked as examples, while no Linux VM equivalent is mentioned. Azure PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool and its usage is emphasized throughout. The documentation refers to Windows tools and patterns (e.g., PowerShell, WinRM) without mentioning or prioritizing Linux alternatives or parity.
Recommendations
  • Add references and examples for Linux VM scenarios (e.g., SSH certificate deployment via Key Vault) in the introduction and related links.
  • Ensure that Linux-centric tools (such as Bash, native Azure CLI usage in Linux shells) are mentioned and examples are provided where appropriate.
  • Where PowerShell is shown, clarify cross-platform support or provide Bash/Linux shell equivalents.
  • Avoid referencing Windows-specific quickstarts (such as WinRM on Windows VM) without also mentioning Linux equivalents.
  • Explicitly state that Azure CLI is cross-platform and show usage in Linux environments, including shell syntax (e.g., Bash).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell in the export instructions and linking to a PowerShell-specific guide for blueprint export. There is no mention of Linux or cross-platform alternatives such as Azure CLI in the migration steps, nor are examples provided for non-Windows environments. The instructions and tooling references are Windows-centric, which may hinder Linux users from following the migration process.
Recommendations
  • Include Azure CLI commands and examples alongside PowerShell for blueprint export and migration steps.
  • Update links to reference both PowerShell and Azure CLI documentation where available.
  • Add explicit notes or sections for Linux/macOS users, clarifying cross-platform compatibility of tools and scripts.
  • Ensure sample code and instructions are platform-neutral or provide alternatives for both Windows and Linux environments.
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-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 page demonstrates a Windows bias by frequently mentioning Windows-specific tools (such as Azure PowerShell), listing Windows before Linux in shortcut instructions, and referencing Windows-centric resource types (e.g., DependencyAgentWindows). There are no explicit Linux shell examples (such as Bash), and PowerShell is presented as a primary method for exporting resources. The documentation does not provide parity for Linux users in terms of CLI usage or resource types.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell commands for resource export and template conversion.
  • Avoid listing Windows before Linux in shortcut instructions; use neutral phrasing or alternate order.
  • Mention Linux-specific resource types or considerations where applicable, not just Windows-centric ones.
  • Include screenshots or instructions for Linux environments (e.g., terminal usage, file paths) where relevant.
  • Ensure that all tooling recommendations (such as Visual Studio Code commands) clarify cross-platform compatibility and usage.
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-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 Windows bias by mentioning Azure PowerShell before Azure CLI when describing how to run examples. It also references Visual Studio Code as the editor, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux examples or mentions of Linux-specific tools or workflows, and the guidance leans toward Windows-centric tooling and patterns.
Recommendations
  • Mention Azure CLI before Azure PowerShell, as CLI is more commonly used across platforms including Linux and macOS.
  • Explicitly state that all examples and tools (Azure CLI, Visual Studio Code) are available and supported on Linux and macOS, not just Windows.
  • Add a note or section on how to deploy Bicep files from Linux/macOS terminals, including sample commands.
  • Reference other cross-platform editors (e.g., Vim, Sublime Text) for creating Bicep files, or clarify that any text editor can be used.
  • Ensure that links and instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific paths or shell commands).
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-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 in its 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as the primary methods for deploying Bicep files. Additionally, Visual Studio Code is referenced as the editor for creating Bicep files, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-native tools or deployment patterns. The ordering and selection of tools suggest a Windows-centric approach.
Recommendations
  • Include explicit Bash or Linux shell examples for deploying Bicep files using Azure CLI.
  • Mention Linux-native editors (e.g., Vim, Emacs) or provide guidance for creating Bicep files on Linux systems.
  • Clarify that Azure CLI is cross-platform and can be used on Linux and macOS, not just Windows.
  • Add links or instructions for installing and using Bicep on Linux systems.
  • Balance the mention of Azure PowerShell with Linux alternatives, or note that PowerShell Core is available cross-platform.
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-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 primarily in the 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as the recommended tools for deploying Bicep files, with no explicit mention of Linux or cross-platform usage. There are no examples or instructions tailored for Linux users, and PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is cross-platform. No Linux-specific shell commands (e.g., Bash) or deployment patterns are shown.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide example deployment commands using Bash or shell scripts for Linux users.
  • Clarify that Azure PowerShell is available on Linux and macOS, but highlight Azure CLI as the default for cross-platform scenarios.
  • Add a note or section on how to deploy Bicep files from Linux environments, including prerequisites and sample commands.
  • Ensure all instructions and examples are platform-neutral or provide parity between Windows and Linux usage.
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-12 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 page exhibits a Windows bias by consistently presenting Windows and PowerShell examples first and exclusively, especially in command-line instructions and project setup. Directory paths, shell commands, and cleanup steps are all shown using Windows conventions (e.g., C:\ paths, PowerShell commands), with no equivalent Linux/macOS shell examples. Package references and environment variable configuration do mention Linux and macOS, but practical usage instructions and examples are Windows-centric. There are no bash/zsh or Linux/macOS terminal examples, and the workflow assumes Visual Studio or Visual Studio Code on Windows.
Recommendations
  • Provide equivalent Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands for directory creation, navigation, and cleanup.
  • Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) in addition to Windows paths.
  • Include instructions for running MSBuild and dotnet CLI on Linux/macOS, including any platform-specific considerations.
  • Demonstrate usage of Azure.Bicep.CommandLine.linux-x64 and osx-x64 in project file examples, not just win-x64.
  • Add guidance for installing prerequisites (e.g., .NET SDK, MSBuild) on Linux/macOS, including package manager commands.
  • Ensure all code and command examples are presented in platform-agnostic tabs or sections, so users can easily find instructions relevant to their OS.
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-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 Windows bias by referencing Azure PowerShell and Visual Studio Code (a Microsoft tool) as the primary means to deploy and create 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 workflows.
Recommendations
  • Provide explicit Linux deployment instructions, such as using Azure CLI on Linux or Bash shell examples.
  • List Azure CLI before Azure PowerShell to avoid implying Windows-first workflows.
  • Mention alternative editors (e.g., Vim, VS Code on Linux, or other cross-platform editors) for creating Bicep files.
  • Include notes or links for installing and using Bicep tooling on Linux and macOS.
  • Add example commands for both Windows (PowerShell) and Linux/macOS (Bash) environments.
GitHub Create Pull Request
Azure Resource Manager Bicep comparison operators ...s/azure-resource-manager/bicep/operators-comparison.md
High 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 a Windows bias by referencing Azure PowerShell alongside Azure CLI as the primary methods for deploying Bicep files, with PowerShell (a Windows-centric tool) mentioned first. There are no explicit Linux-specific instructions or examples, and the deployment guidance does not clarify cross-platform usage or provide parity for Linux users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Provide Linux/macOS-specific deployment instructions or examples, such as using bash or shell commands.
  • Avoid listing PowerShell before CLI unless contextually relevant, or alternate the order to avoid perceived prioritization.
  • Include a note or section on platform compatibility for Bicep tooling and deployment.
  • Where possible, add example commands for both PowerShell and bash/shell to ensure parity.
GitHub Create Pull Request
Azure Resource Manager Create a private container registry in Azure for Bicep modules ...zure-resource-manager/bicep/private-module-registry.md
High 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 demonstrates a mild Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI (cross-platform) examples. PowerShell is highlighted in both command and instructional sections, and the local cache path for Windows is described in more detail than for Linux/Mac. There are no Linux shell-specific examples or mentions of Linux-native tools, and the documentation assumes familiarity with Windows conventions.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is presented before Azure PowerShell, or present both together without preference.
  • Include Linux shell (bash) and MacOS-specific command examples where relevant, especially for file paths and environment variables.
  • Provide equal detail for Linux and Mac cache paths, including example full paths (e.g., /home/<username>/.bicep/br/<registry-name>.azurecr.io/<module-path>/<tag>).
  • Explicitly state that Azure CLI commands work identically on Windows, Linux, and MacOS, and encourage its use for cross-platform compatibility.
  • Where PowerShell is used, clarify that it is available on Linux and Mac as well, or provide bash equivalents if possible.
GitHub Create Pull Request
← Previous Page 2 of 52 Next →