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 451-475 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/test-toolkit.md ...icles/azure-resource-manager/templates/test-toolkit.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell on all platforms (Windows, Linux, macOS) to use the ARM template test toolkit. All usage examples, customization, and pipeline integration instructions are provided only in PowerShell, with no alternatives using native Linux tools or shells (e.g., Bash). The Windows installation instructions are presented before Linux and macOS, and Windows-specific concepts like execution policy are referenced throughout. There is no mention of using the toolkit with other scripting environments or providing Bash-native examples.
Recommendations
  • Provide Bash or shell script examples for Linux and macOS users, where possible.
  • Clarify if the toolkit can be used with other scripting environments (e.g., Python, Bash) or if PowerShell is strictly required.
  • Offer instructions for running the toolkit via Docker or containerized environments to simplify cross-platform usage.
  • Add Linux-first or platform-neutral sections, and avoid always listing Windows instructions first.
  • Reference Linux-native tools and patterns (e.g., unzip, tar) for extracting files, rather than only PowerShell commands.
  • Discuss any limitations or differences in PowerShell usage on Linux/macOS versus Windows.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/common-deployment-errors.md ...ce-manager/troubleshooting/common-deployment-errors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second. However, PowerShell is referenced throughout, and links to Windows-specific troubleshooting (e.g., allocation failures) are provided alongside Linux equivalents. In the 'SubnetsNotInSameVnet' error, the Windows VM link is listed before the Linux VM link. There is a general tendency to mention Windows tools (PowerShell) and Windows-specific documentation, sometimes before or alongside Linux equivalents, but not always with equal prominence or detail.
Recommendations
  • Ensure Linux examples (e.g., Azure CLI) are always presented with equal prominence and detail as Windows/PowerShell examples.
  • When listing platform-specific troubleshooting links (e.g., VM allocation issues), alternate or randomize the order, or present both platforms together without prioritizing Windows.
  • Where PowerShell is mentioned, always include the equivalent Azure CLI (Linux-friendly) command and documentation.
  • Audit all referenced links and ensure Linux documentation is as comprehensive and accessible as Windows documentation.
  • Consider adding explicit notes or sections for Linux users where platform differences may affect troubleshooting steps.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/enable-debug-logging.md ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) for enabling debug logging, with no equivalent method available via Azure CLI (commonly used on Linux/macOS). PowerShell examples and tools are presented first and in greater detail, while Linux-native patterns or alternatives are not discussed. The lack of parity in debug logging capabilities between PowerShell and Azure CLI, and the absence of any mention of Linux shell scripting or cross-platform alternatives, further reinforce the bias.
Recommendations
  • Advocate for feature parity: Request that debug logging capabilities (such as setting DeploymentDebugLogLevel) be added to Azure CLI, which is cross-platform.
  • Provide Linux/bash examples: Where possible, include bash or shell scripting examples for common deployment and troubleshooting tasks.
  • Balance tool coverage: Present Azure CLI examples before or alongside PowerShell examples, especially for tasks that can be performed on both platforms.
  • Explicitly note platform limitations: Clearly state when a feature is only available on Windows/PowerShell, and suggest workarounds or alternatives for Linux/macOS users.
  • Reference cross-platform tools: Mention or link to other cross-platform deployment tools or SDKs that can be used for similar troubleshooting tasks.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-sku-not-available.md ...rce-manager/troubleshooting/error-sku-not-available.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by consistently presenting PowerShell examples and references before Azure CLI equivalents, and by providing detailed PowerShell scripts for filtering and formatting output. The use of Windows-style file paths (e.g., .\sku-list.json) and exclusive mention of PowerShell cmdlets further reinforces the bias. Linux-specific patterns, shell scripting, or file path conventions are not addressed, and there are no Bash or Linux shell examples provided.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples, or at least in parallel, to avoid implying Windows is the primary platform.
  • Include Linux/Bash shell scripting examples for filtering and formatting output, such as using jq or grep with az CLI output.
  • Use platform-neutral file paths (e.g., ./sku-list.json) in CLI examples.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux environments.
  • Where PowerShell scripts are provided, offer equivalent Bash scripts for Linux users.
  • Add notes or tabs for Linux-specific guidance where relevant, especially for scripting and automation.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/deployment-quota-exceeded.md ...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (with Bash scripting) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, and there is no explicit mention of Linux or macOS environments. The Bash examples in the Azure CLI section assume a Bash shell but do not clarify cross-platform compatibility or alternatives for Windows users. The PowerShell examples are Windows-centric and do not offer Linux PowerShell Core guidance. There is no mention of Linux-specific tools or considerations, and the documentation does not address shell differences or provide parity guidance.
Recommendations
  • Explicitly state that Azure CLI examples are intended for Bash (Linux/macOS) and provide equivalent Windows Command Prompt or PowerShell Core examples for cross-platform clarity.
  • Clarify that PowerShell examples can be run on PowerShell Core on Linux/macOS, or provide notes about any platform-specific differences.
  • Add a section or note on how to perform these tasks on Linux and macOS, including any prerequisites or differences in shell behavior.
  • Ensure that Linux and macOS users are addressed directly in the documentation, not just implicitly through Bash examples.
  • Consider providing a table or summary comparing commands across Windows (PowerShell, CMD) and Linux/macOS (Bash, PowerShell Core) for better parity.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-not-found.md ...re-resource-manager/troubleshooting/error-not-found.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell and Azure CLI together, but mentioning PowerShell (a Windows-centric tool) first. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or tools discussed. The guidance for changing subscriptions references PowerShell's Set-AzContext before az account set, and no bash-specific context or examples are provided. All portal instructions are platform-neutral, but command-line examples lack Linux parity.
Recommendations
  • Provide explicit bash examples for Azure CLI commands, showing usage in Linux/macOS terminals.
  • Alternate the order of PowerShell and Azure CLI references, or group them together as cross-platform tools.
  • Mention Linux-specific considerations for Azure CLI usage, such as authentication or environment setup.
  • Include notes or examples for Linux users where command syntax or behavior may differ.
  • Ensure that all command-line instructions are equally accessible and clear for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-resource-quota.md ...source-manager/troubleshooting/error-resource-quota.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting steps for Azure resource quota errors, with command-line examples for both Azure CLI and PowerShell. However, the PowerShell example is given equal prominence to the Azure CLI, despite PowerShell being primarily a Windows tool. There is no mention of Linux-specific tools or shell patterns (e.g., Bash), nor is there guidance for users who may be working on Linux or macOS. The portal instructions are platform-neutral, but the command-line guidance is Windows-centric.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, clarifying cross-platform compatibility.
  • Note that Azure CLI works natively on Linux/macOS and provide installation links or references.
  • Clarify that PowerShell Core is cross-platform, but most users on Linux/macOS will use Azure CLI.
  • Consider listing Azure CLI (Bash) examples before PowerShell to avoid implicit Windows-first bias.
  • Add a short section or note for Linux/macOS users, confirming that all steps (except PowerShell) are applicable.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-arm-deployment.md ...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, referencing PowerShell-specific commands, and listing Windows-centric tools like Visual Studio Code and Azure PowerShell in prerequisites. There is no mention of Linux-specific editors, shell environments, or alternative tooling, and PowerShell examples are given equal prominence to CLI, which is cross-platform but often associated with Linux/macOS users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include Linux/macOS-specific instructions for installing Azure CLI and running commands (e.g., bash syntax, package manager instructions).
  • Reference Linux-friendly editors such as Vim, Emacs, or even VS Code on Linux, not just Visual Studio Code generically.
  • Clarify that PowerShell is available on Linux/macOS, or provide bash/zsh equivalents for all PowerShell examples.
  • Ensure that CLI examples appear before PowerShell, or provide tabs for bash, PowerShell, and Windows Command Prompt where relevant.
  • Mention Linux-specific troubleshooting tools or patterns where applicable (e.g., using jq for JSON parsing, tailing logs, etc.).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md ...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and resource management tasks. However, PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) can signal a Windows bias, especially since no explicit Linux shell examples (e.g., Bash) are given. The documentation does not mention Linux-specific patterns, nor does it address platform differences in command usage, installation, or troubleshooting. Visual Studio Code is referenced as the editor, which is cross-platform, but the troubleshooting steps and screenshots do not clarify platform-specific behaviors.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in a Linux terminal.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and note any platform-specific differences if present.
  • Include installation instructions or troubleshooting notes for Azure CLI and Bicep extension on Linux and macOS, not just Windows.
  • If referencing PowerShell, note that it is available cross-platform, but highlight that Bash is the default shell on most Linux systems.
  • Add screenshots or notes showing troubleshooting steps in Linux environments (e.g., terminal error messages, file navigation).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-subscription.md ...azure-resource-manager/bicep/deploy-to-subscription.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 given equal prominence despite being primarily a Windows tool. There is no mention of Bash or Linux-native scripting, and no explicit Linux-specific guidance or troubleshooting. The examples and references focus on Azure CLI (cross-platform) and PowerShell (Windows-centric), with no mention of Linux shell environments or alternative Linux tools. This may make the documentation less approachable for Linux users and reinforce a Windows-centric workflow.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands for Bash (e.g., using export for environment variables, or showing the same az deployment sub create command in a Linux terminal context).
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users (e.g., Bash, zsh).
  • Add troubleshooting notes or tips for Linux environments, such as file path differences, permission issues, or installation instructions for Azure CLI on Linux.
  • Consider adding a section or tab for Bash/Linux shell examples alongside PowerShell and Azure CLI, to demonstrate parity and inclusivity.
  • Where references are made to Cloud Shell, clarify that it supports both Bash and PowerShell, and provide examples for both.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a noticeable Windows bias. PowerShell examples are given equal or greater prominence, and Windows/PowerShell-specific tools and APIs (e.g., Connect-AzAccount, CommandLineToArgvW, Start-Sleep) are referenced without Linux equivalents or alternatives. Windows/PowerShell patterns (such as $ErrorActionPreference and Start-Sleep) are explained in detail, while Linux/Bash error handling (e.g., set -e) is mentioned only briefly. Some system calls and troubleshooting advice are Windows-centric, and references to Windows APIs (CommandLineToArgvW) are present without Linux alternatives.
Recommendations
  • Provide Linux/Bash equivalents for Windows-specific APIs and system calls (e.g., mention how argument splitting works in Linux containers instead of only referencing CommandLineToArgvW).
  • Expand explanations of Bash/Linux error handling and debugging (e.g., discuss set -e, trap, and exit codes in more detail, similar to PowerShell's $ErrorActionPreference).
  • Include troubleshooting steps and patterns for Bash scripts, not just PowerShell (e.g., alternatives to Start-Sleep for keeping containers alive).
  • When referencing tools or commands, mention cross-platform alternatives or clarify platform-specific behavior (e.g., how environment variables are accessed in Bash vs. PowerShell).
  • Ensure that CLI/Bash examples are given equal prominence and detail as PowerShell examples, especially in sections discussing script execution, error handling, and output management.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page provides deployment guidance and examples exclusively using Azure PowerShell commands, which are primarily Windows-centric. There is no mention of cross-platform tools such as Azure CLI, nor are Linux shell examples provided. The guidance and conflict resolution focus on PowerShell command parameters, implicitly prioritizing Windows workflows and omitting equivalent Linux or cross-platform instructions.
Recommendations
  • Add Azure CLI examples alongside Azure PowerShell, showing how to deploy Bicep templates and handle location parameters.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for both Windows and Linux/macOS users.
  • Discuss any parameter naming conflicts or best practices relevant to Azure CLI, not just PowerShell.
  • Ensure that examples and troubleshooting steps are provided for both PowerShell and CLI, and avoid assuming the user is on Windows.
  • Consider including Bash or shell script snippets for Linux users where appropriate.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows tools and patterns (e.g., PowerShell, Chocolatey, Winget) are mentioned and given detailed instructions, sometimes before or more prominently than Linux/macOS equivalents. The PowerShell example is more elaborate than the Linux/macOS shell examples. The Azure PowerShell section is present, but there's no equivalent section for Bash or other Linux-native scripting environments. Windows installer and package manager options are listed before manual installation, and Windows-specific instructions are often more detailed.
Recommendations
  • Add parity for Linux-native scripting environments (e.g., Bash scripts for automation) alongside PowerShell instructions.
  • Ensure Linux and macOS package manager options (e.g., apt, yum, brew) are listed as prominently as Windows options like Chocolatey and Winget.
  • Provide Bash/Zsh installation and verification examples in as much detail as PowerShell examples.
  • Consider adding a section for Linux automation (e.g., using shell scripts in CI/CD) similar to the Azure PowerShell section.
  • Review ordering so that cross-platform or Linux/macOS instructions are not consistently listed after Windows instructions.
  • Where possible, use cross-platform commands and avoid Windows-specific terminology unless necessary.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/installation-troubleshoot.md ...re-resource-manager/bicep/installation-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line instructions using Windows tools (e.g., 'where bicep'), referencing Windows-specific environment variables (e.g., %USERPROFILE%), and omitting equivalent Linux/macOS commands (e.g., 'which bicep', '$HOME/.azure/bin'). No Linux or macOS troubleshooting steps or examples are provided, and Windows patterns are mentioned exclusively.
Recommendations
  • Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' for Linux/macOS).
  • Mention Linux/macOS environment variable paths (e.g., '$HOME/.azure/bin') alongside Windows paths.
  • Add troubleshooting steps and examples specific to Linux/macOS installations.
  • Ensure parity in guidance for modifying PATH variables on non-Windows systems.
  • Clearly indicate when instructions are platform-specific and provide alternatives for other platforms.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-logical.md ...cles/azure-resource-manager/bicep/operators-logical.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 introductory section, where it suggests using Azure CLI or Azure PowerShell to deploy Bicep files, with PowerShell (a Windows-centric tool) mentioned before CLI. There are no explicit Linux-specific instructions, nor are Linux shell examples (e.g., Bash) provided for deploying Bicep files. All code examples are Bicep language only, but the deployment context is Windows-oriented.
Recommendations
  • Mention Bash/Azure CLI usage explicitly alongside PowerShell, and provide example commands for both environments.
  • Ensure deployment instructions do not prioritize Windows tools; list Azure CLI (cross-platform) before PowerShell, or present both equally.
  • Add a section or note clarifying that all examples are platform-agnostic and can be run on Linux, macOS, or Windows.
  • Where relevant, provide links or references to Linux/macOS setup guides for Bicep and Azure CLI.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-safe-dereference.md ...re-resource-manager/bicep/operator-safe-dereference.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, and by referencing Visual Studio Code (a tool often associated with Windows environments) for Bicep file creation. There are no Linux-specific instructions, nor are alternative editors or deployment methods mentioned. The examples and guidance assume familiarity with Windows-centric tools and workflows.
Recommendations
  • Explicitly mention Azure CLI as a cross-platform tool and provide CLI-first instructions for deploying Bicep files.
  • Include examples or references for using Bicep with Linux-native editors (e.g., Vim, Emacs) or via command line.
  • Add a note clarifying that Visual Studio Code is available on Linux and macOS, and suggest alternative editors for those platforms.
  • Provide parity in instructions for both PowerShell and Bash, especially in deployment steps.
  • Ensure that references to tools and workflows do not assume a Windows environment by default.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-null-forgiving.md ...zure-resource-manager/bicep/operator-null-forgiving.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 listing Azure PowerShell before Azure CLI in deployment instructions, and by referencing Visual Studio Code (a Microsoft tool popular on Windows) as the primary editor for Bicep files. There are no explicit Linux shell examples or mentions of Linux-native tools or editors, and the guidance assumes familiarity with Windows-centric workflows.
Recommendations
  • List Azure CLI before Azure PowerShell when describing deployment options, as CLI is cross-platform and more commonly used on Linux.
  • Include explicit Linux shell (bash) examples for deploying Bicep files, such as using 'az deployment' commands in a bash terminal.
  • Mention alternative editors that are popular on Linux, such as Vim or VS Code on Linux, and clarify that Bicep development is cross-platform.
  • Add a note that all examples and tools work on Linux, macOS, and Windows, and provide links to platform-specific setup guides.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/azure-services-resource-providers.md ...anager/management/azure-services-resource-providers.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias. Windows-specific tools and terminology (such as PowerShell and references to the Windows Azure Service Management API) are present. In the 'Find resource provider' section, PowerShell is given as the only shell scripting example besides Azure CLI and Python, with no Bash or Linux shell example. The registration section references Windows Azure Service Management API and Windows terminology. Some resource providers and services are Windows-specific (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP), but Linux equivalents are not highlighted or mentioned.
Recommendations
  • Add Bash or Linux shell examples alongside PowerShell in the 'Find resource provider' section to improve parity.
  • When mentioning Windows-specific APIs or services, also reference Linux or cross-platform alternatives where applicable.
  • Ensure that examples and tooling instructions are presented in a platform-neutral order, or explicitly include both Windows and Linux options.
  • Highlight Linux-specific resource providers or services if available, or clarify platform support for each provider.
  • Review terminology to avoid unnecessary references to Windows when describing Azure-wide concepts.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-data-boundary.md ...re-resource-manager/management/manage-data-boundary.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides command-line examples for Azure CLI, PowerShell, and REST API, but PowerShell is given equal prominence to Azure CLI and is referenced frequently. PowerShell is a Windows-centric tool, and its inclusion as a primary example (alongside Azure CLI) may indicate a Windows bias. Additionally, links to further documentation (e.g., 'Assign Azure roles') point to PowerShell-specific pages. There is no mention of Linux-specific shell scripting or alternative Linux-native tools. The documentation does not explicitly state platform requirements, but the heavy use of PowerShell and references to Windows tools suggest a bias toward Windows environments.
Recommendations
  • Ensure Azure CLI examples are presented first, as it is cross-platform and more widely used on Linux.
  • Add explicit notes clarifying that Azure CLI commands work natively on Linux, macOS, and Windows.
  • Avoid linking only to PowerShell documentation; provide equivalent links to Azure CLI documentation.
  • Include Bash shell scripting examples where appropriate, especially for automation scenarios.
  • Clarify that PowerShell Core is available cross-platform, but avoid assuming users are on Windows.
  • Consider mentioning Linux-native tools or workflows where relevant, to improve parity.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-key-vault.md ...-manager/management/relocation/relocation-key-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for key operations (template export, modification, deployment) but omitting equivalent Azure CLI or Bash examples. PowerShell is featured as the only command-line automation option, and instructions for obtaining region codes reference PowerShell commands before mentioning the Azure Locations web page. There are no Linux-specific or cross-platform CLI instructions, and the use of PowerShell may alienate users on Linux or macOS who prefer Azure CLI or Bash scripting.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, including template export, modification, and deployment.
  • Provide Bash script snippets for common operations to support Linux/macOS users.
  • When referencing command-line tools, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Include guidance on installing and using Azure CLI on Linux/macOS.
  • Clarify that both PowerShell and Azure CLI are supported and provide links to relevant documentation for each.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-firewall.md ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, without any equivalent Azure CLI or Bash examples. The PowerShell instructions are given equal prominence to the Azure Portal, but there is no mention of Linux-native tools or workflows. References to migration and configuration steps also link to PowerShell-based guides, further reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, ensuring parity for Linux and macOS users.
  • Include Bash shell instructions for template export, modification, and deployment steps.
  • Reference migration guides that use cross-platform tools, such as Azure CLI, and avoid PowerShell-only links.
  • Explicitly state that all steps can be performed on Linux, macOS, or Windows, and clarify any OS-specific requirements.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions, or note the cross-platform compatibility of the commands.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily in the 'readEnvironmentVariable' section, where all environment variable manipulation examples use PowerShell syntax and reference .NET APIs, which are native to Windows. There are no equivalent examples for Linux or macOS shells (e.g., Bash), and Windows tooling is mentioned exclusively. No cross-platform guidance is provided for setting environment variables, which may confuse or exclude users on non-Windows platforms.
Recommendations
  • Add equivalent examples for setting environment variables in Bash (Linux/macOS), e.g., 'export testEnvironmentVariable="Hello World!"'.
  • Mention platform differences in environment variable persistence (process/user/machine) and how they map to Linux/macOS.
  • Provide links to official documentation for environment variable management on Linux/macOS.
  • Clearly indicate when examples are Windows-specific and provide parity for other platforms.
  • Consider including a table or section comparing environment variable management across PowerShell, Bash, and other common shells.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-github-actions.md .../azure-resource-manager/bicep/deploy-github-actions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 and PowerShell examples for resource group creation and deletion, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and no explicit Linux shell (bash) examples are provided. There is no mention of Linux-specific tools or workflows, and the PowerShell tab is present throughout, potentially signaling Windows as a primary platform. The workflow examples use 'ubuntu-latest' runners, which is cross-platform, but the local setup instructions and examples are Windows/PowerShell heavy.
Recommendations
  • Add explicit bash examples for resource group creation and deletion, highlighting Linux usage.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide instructions for installing Azure CLI on Linux.
  • Consider moving Azure CLI examples before PowerShell examples to signal cross-platform priority.
  • Remove or de-emphasize PowerShell tabs unless there is a specific Windows-only step.
  • Add a note about cross-platform compatibility for all tools and workflows mentioned.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/data-types.md ...rticles/azure-resource-manager/templates/data-types.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the example command-line tool for ARM template deployment and integer parameter limitations, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific examples or parity guidance are provided.
Recommendations
  • Include references to Azure CLI and Bash as alternative deployment tools, especially when discussing parameter limitations.
  • Provide examples or notes for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) usage where command-line tools are mentioned.
  • Clarify whether integer limitations apply to other platforms and tools, not just PowerShell.
  • Add a section or note on cross-platform considerations for ARM template deployment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-properties.md ...es/azure-resource-manager/templates/copy-properties.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific examples and tools more prominently than Linux equivalents. The only example template linked is for Windows VM deployment, and deployment instructions prioritize Azure PowerShell. There are no explicit Linux-focused examples or references to Linux deployment tools (e.g., Bash, Azure CLI on Linux), and Windows terminology appears first or exclusively in several places.
Recommendations
  • Add example templates for Linux VM deployments alongside Windows examples.
  • Include deployment instructions using Azure CLI on Linux and Bash scripts, not just PowerShell.
  • Ensure parity in references to both Windows and Linux tools and workflows throughout the documentation.
  • When listing supported tools (PowerShell, CLI, REST API), avoid listing Windows tools first or exclusively.
  • Provide links to Linux-focused quickstart templates and tutorials.
GitHub Create Pull Request
← Previous Page 19 of 52 Next →