Azure Resource Manager

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

Bias Trend Over Time

Pages with Bias Issues

492 issues found
Showing 326-350 of 492 flagged pages
Azure Resource Manager Decompile a JSON Azure Resource Manager template to Bicep ...ain/articles/azure-resource-manager/bicep/decompile.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting templates, with Azure CLI (cross-platform) shown first. However, PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias. The instructions for renaming variables reference Visual Studio Code features (right-click, F2 hotkey) that are available cross-platform, but do not mention Linux/macOS-specific alternatives or CLI-based workflows. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no explicit mention of platform differences or parity.
Recommendations
  • Add explicit Bash/shell examples for exporting and decompiling templates to demonstrate Linux parity.
  • Clarify that Azure CLI works on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Include a note or section on using the Bicep CLI directly in Linux/macOS environments (e.g., with Bash, zsh).
  • Mention any platform-specific caveats for Visual Studio Code features, if applicable.
  • Consider listing Azure CLI and Bash examples before PowerShell to reinforce cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files with Cloud Shell ...les/azure-resource-manager/bicep/deploy-cloud-shell.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for deploying Bicep files in Azure Cloud Shell. However, PowerShell (commonly associated with Windows) is given equal prominence to Bash, and follow-up links highlight PowerShell before Linux-specific alternatives. There is a subtle bias towards Windows/PowerShell usage, but Linux users can complete all tasks using Bash/Azure CLI.
Recommendations
  • Ensure Azure CLI (Bash) examples are shown first, as Bash is the default shell for many Linux/macOS users.
  • Add explicit notes clarifying that all steps work identically in Bash (Linux/macOS) and PowerShell (Windows), and highlight any differences if they exist.
  • Include troubleshooting tips or links relevant to Linux/macOS users, not just PowerShell/Windows.
  • Balance follow-up links so that CLI (Bash) and PowerShell resources are presented equally.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to create a new resource group .../azure-resource-manager/bicep/create-resource-group.md
Low 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 provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes with more detail. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is mentioned as a primary method, which may create friction for non-Windows users. The CLI examples are cross-platform, but the lack of explicit Linux/macOS context or troubleshooting tips is a minor bias.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for multi-line commands.
  • Clarify that Azure CLI works cross-platform and highlight installation or usage notes for Linux/macOS.
  • Reorder examples to show Azure CLI first, as it is more universally available.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., line continuation differences, authentication).
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to management group ...e-resource-manager/bicep/deploy-to-management-group.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files to management groups. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and is presented immediately after the CLI example. There are no Linux/macOS-specific instructions or notes, and no mention of Bash scripting or Linux-native tooling. The CLI example is cross-platform, but the inclusion and prominence of PowerShell may suggest a slight Windows bias.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
  • Consider listing Azure CLI examples first, as it is the most universally available tool.
  • Add a brief note for Linux/macOS users confirming that all CLI commands work natively in their environments.
  • If PowerShell is shown, clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions.
  • Include a Bash script example for automation on Linux/macOS, or mention how to use the commands in shell scripts.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to subscription ...azure-resource-manager/bicep/deploy-to-subscription.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files at the subscription scope. However, PowerShell examples are given equal prominence and are presented immediately after CLI, with dedicated sections and links. There is no explicit mention of Linux or macOS environments, nor are there any examples using Bash scripting or references to platform-specific differences. The CLI examples are cross-platform, but the presence and emphasis on PowerShell (a Windows-centric tool, though available on Linux/macOS) may create a perception of Windows bias.
Recommendations
  • Explicitly state that Azure CLI examples work on Linux, macOS, and Windows.
  • Add Bash shell examples or clarify that CLI commands are intended for all platforms.
  • Mention that PowerShell is available cross-platform, or provide links to installation instructions for Linux/macOS.
  • Consider listing CLI examples first, as they are more universally available.
  • Add a note about platform compatibility for both CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files by using GitHub Actions .../azure-resource-manager/bicep/deploy-github-actions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for resource group creation and deletion, but PowerShell (a Windows-centric tool) is given equal prominence and is listed immediately after CLI in each case. No Linux-specific shell examples (e.g., Bash) are provided, and there is no explicit mention of Linux/macOS compatibility for the PowerShell commands. The workflow examples use 'ubuntu-latest' runners, which is cross-platform friendly, but the local setup instructions lean toward Windows/PowerShell users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Add Bash shell examples or clarify that Azure CLI commands can be run in Bash on Linux/macOS.
  • Note that PowerShell examples are primarily for Windows users, and provide guidance for Linux/macOS users if they wish to use PowerShell Core.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Add a section or note about Linux/macOS environment setup if any steps differ.
GitHub Create Pull Request
Azure Resource Manager Develop a deployment script in Bicep ...re-resource-manager/bicep/deployment-script-develop.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI (Bash) and Azure PowerShell examples for all major scenarios, but there are subtle signs of Windows bias. Windows/PowerShell tools and patterns are referenced (e.g., CommandLineToArgvW, Connect-AzAccount, Start-Sleep) and sometimes mentioned before their Linux equivalents. The documentation assumes familiarity with Windows concepts and tools, and references to PowerShell-specific behaviors (like $ErrorActionPreference) are more detailed than Bash equivalents. However, Linux/Bash examples are present throughout, and container images are based on Ubuntu, reducing the overall impact.
Recommendations
  • When referencing system calls (e.g., CommandLineToArgvW), also mention the equivalent Linux/Bash parsing or clarify that this is an implementation detail not relevant to script authors.
  • Provide equal detail for Bash error handling (e.g., set -e, trap) as is given for PowerShell ($ErrorActionPreference).
  • When mentioning troubleshooting steps (e.g., Start-Sleep for keeping containers alive), offer Bash alternatives (e.g., sleep) alongside PowerShell.
  • Avoid referencing Windows-specific APIs or tools (like Connect-AzAccount) without clarifying their cross-platform nature or providing Bash/CLI equivalents.
  • Ensure that CLI/Bash examples are presented first or in parallel with PowerShell, rather than defaulting to Windows-first ordering.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to tenant ...icles/azure-resource-manager/bicep/deploy-to-tenant.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for role assignment and tenant deployment commands, but PowerShell is consistently shown before CLI in key permission setup steps. The initial example for assigning permissions uses PowerShell first, and the PowerShell command is presented with syntax highlighting and explanation before the CLI equivalent. There is no mention of Linux-specific considerations, nor are Linux/macOS shell patterns (e.g., bash, zsh) discussed. However, Azure CLI is cross-platform and examples are provided for it, so Linux users can complete all tasks.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links or notes for installing Azure CLI on those platforms.
  • Add a brief note that PowerShell examples are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Ensure that any references to Cloud Shell clarify that both Bash and PowerShell environments are available.
GitHub Create Pull Request
Azure Resource Manager Install Bicep tools .../main/articles/azure-resource-manager/bicep/install.md
Low 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 comprehensive installation instructions for Bicep CLI across Windows, Linux, and macOS, but Windows-specific tools (Chocolatey, Winget, Windows Installer) and PowerShell-based manual installation are described in greater detail and with more options than Linux/macOS equivalents. Windows installation methods are listed last, but the Windows section is notably longer and more tool-centric. PowerShell commands are used for manual installation on Windows, while Linux/macOS use shell scripts. There is a slight bias toward Windows tooling and patterns.
Recommendations
  • Provide parity by listing equivalent package manager options for Linux (e.g., apt, yum, snap) and macOS (e.g., MacPorts) if available.
  • Add more detail to Linux/macOS installation sections, such as troubleshooting, PATH updates, and verification steps.
  • Include shell script examples for Windows (e.g., using Git Bash or WSL) to demonstrate cross-platform flexibility.
  • Consider listing installation methods in parallel tables or grouped by method rather than OS, to avoid implicit prioritization.
  • Add explicit notes about Linux/macOS package managers and their availability/status for Bicep CLI.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but PowerShell examples are always shown immediately after CLI, and the introductory quickstart link references a Windows VM scenario. There is a subtle Windows bias in the ordering and in the use of PowerShell, which is primarily a Windows tool, though it is available cross-platform. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the only quickstart template referenced is for Windows VM WinRM, not a Linux equivalent.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users where Azure CLI is shown, demonstrating usage in a typical Linux environment.
  • Reference both Windows and Linux VM quickstart templates when discussing VM scenarios.
  • Where PowerShell is used, clarify that Azure PowerShell is cross-platform, or provide Bash alternatives for common tasks.
  • Consider alternating the order of CLI and PowerShell examples, or grouping them together to avoid implicit prioritization.
GitHub Create Pull Request
Azure Resource Manager Use Bicep linter ...b/main/articles/azure-resource-manager/bicep/linter.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page references Visual Studio Code and the Bicep CLI, both of which are cross-platform tools. However, there is a subtle Windows bias in the linter rule 'use-recent-az-powershell-version', which references Azure PowerShell—a tool most commonly associated with Windows environments. No explicit Linux/macOS examples, screenshots, or tool mentions are provided, but the overall instructions are not Windows-exclusive.
Recommendations
  • Clarify that Bicep CLI and Visual Studio Code are available on Linux and macOS, and provide installation or usage notes for those platforms.
  • If referencing Azure PowerShell, mention Azure CLI as an alternative for Linux/macOS users, or clarify the cross-platform availability of Azure PowerShell.
  • Include screenshots or terminal examples from Linux/macOS environments to demonstrate parity.
  • Add a section or note about using the linter in non-Windows environments, especially for CI/CD integration.
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
Low 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 mild Windows bias. Windows tools and patterns (such as Azure PowerShell and Visual Studio Code shortcuts) are mentioned before or alongside their Linux/macOS equivalents, but Linux and macOS are not excluded. Examples and instructions often list Windows first, and PowerShell is highlighted as a primary method for resource export. There is no explicit omission of Linux/macOS functionality, but the ordering and emphasis may create friction for non-Windows users.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility for all tools and commands, especially for resource export and Bicep decompilation.
  • Provide Linux/macOS-specific instructions or screenshots where relevant (e.g., Visual Studio Code shortcuts, terminal commands).
  • Avoid listing Windows tools or shortcuts first unless there is a technical reason.
  • Add a section or note highlighting cross-platform support and any OS-specific caveats.
GitHub Create Pull Request
Azure Resource Manager Bicep null-forgiving operator ...zure-resource-manager/bicep/operator-null-forgiving.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell alongside Azure CLI as deployment methods, and recommends Visual Studio Code for authoring Bicep files. While Azure CLI is cross-platform, Azure PowerShell and Visual Studio Code are often associated with Windows environments. No explicit Linux/macOS examples or alternatives are provided, and Windows tools are mentioned first.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS-specific deployment instructions or examples.
  • Include alternative editors for Bicep files, such as Vim or VS Codium, especially for Linux users.
  • If referencing Azure PowerShell, clarify its availability on Linux/macOS or provide Bash examples.
  • Ensure parity in tool recommendations and ordering, e.g., list Azure CLI before Azure PowerShell.
GitHub Create Pull Request
Azure Resource Manager Bicep accessor operators ...icles/azure-resource-manager/bicep/operators-access.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is largely platform-neutral in its technical content and examples, which focus on Bicep syntax. However, in the 'Next steps' section, Azure PowerShell is mentioned alongside Azure CLI as a deployment method, and Visual Studio Code is referenced as the editor, both of which are commonly associated with Windows workflows. There is no explicit mention of Linux/macOS-specific tools or deployment patterns, nor are Linux-first instructions or examples provided.
Recommendations
  • Explicitly mention that Azure CLI and Visual Studio Code are cross-platform and provide links or notes for Linux/macOS installation.
  • Include deployment instructions or examples for Linux/macOS users, such as using Bash or shell scripts.
  • Reference other editors or command-line tools that are popular on Linux/macOS, if relevant.
  • Clarify that Bicep can be used on all major platforms and provide parity in guidance for non-Windows environments.
GitHub Create Pull Request
Azure Resource Manager Bicep numeric operators ...cles/azure-resource-manager/bicep/operators-numeric.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Azure CLI or Azure PowerShell' as the tools to deploy Bicep files, listing PowerShell (a Windows-centric tool) alongside Azure CLI, and does not clarify cross-platform usage or provide Linux/macOS-specific guidance. However, the actual operator examples are platform-neutral and do not show Windows-specific commands or tools.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Provide links or notes on how to install and use Azure CLI on Linux/macOS.
  • If mentioning Azure PowerShell, also mention Bash or other Linux-native shells for parity.
  • Consider listing Azure CLI first, as it is the most cross-platform tool.
  • Add a brief section or note confirming that all examples work identically on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Azure Resource Manager Bicep safe-dereference operator ...re-resource-manager/bicep/operator-safe-dereference.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell and Visual Studio Code as primary tools for deploying and authoring Bicep files, both of which are traditionally associated with Windows environments. Azure CLI is mentioned, but PowerShell is listed first and Visual Studio Code is emphasized without mention of alternative editors or Linux-specific workflows.
Recommendations
  • Explicitly mention that Azure CLI is fully cross-platform and provide Linux/macOS-specific instructions or examples for deploying Bicep files.
  • Include references to alternative editors (e.g., Vim, Emacs) or note that Visual Studio Code is available on Linux/macOS.
  • Ensure that PowerShell is not listed before Azure CLI unless there is a technical reason; consider listing CLI first or equally.
  • Add a section or note confirming that all steps and tools are supported on Linux/macOS, and link to relevant installation guides.
GitHub Create Pull Request
Azure Resource Manager Bicep spread operator ...ticles/azure-resource-manager/bicep/operator-spread.md
Low 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 is largely platform-neutral in its technical content and Bicep examples. However, in the 'Next steps' section, Windows-centric tools (Azure PowerShell, Visual Studio Code) are mentioned before or instead of Linux/macOS alternatives. There is no mention of Linux-specific deployment methods (e.g., Bash, shell scripting), nor is there guidance for using Bicep with editors other than Visual Studio Code.
Recommendations
  • Explicitly mention that Azure CLI works cross-platform and provide Bash/shell examples for Linux/macOS users.
  • Include instructions or links for deploying Bicep files using Bash or other Linux-native tools.
  • List Visual Studio Code as one option, and suggest other editors (e.g., Vim, Emacs, JetBrains IDEs) for creating Bicep files.
  • Clarify that Azure PowerShell is available on Linux/macOS, or provide CLI-first instructions for parity.
GitHub Create Pull Request
Azure Resource Manager Bicep comparison operators ...s/azure-resource-manager/bicep/operators-comparison.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Azure CLI or Azure PowerShell' as the methods to run examples, listing PowerShell (a Windows-centric tool) alongside Azure CLI, and links to a deployment guide that may be Windows-focused. However, all example code is in Bicep and platform-neutral, with no command-line examples or tool-specific instructions given. No explicit Windows-only tools or PowerShell-heavy bias is present, but Windows/PowerShell is mentioned before Linux alternatives.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
  • If linking to deployment guides, ensure those guides include Linux/macOS instructions and examples.
  • Explicitly mention that Bicep files can be deployed from any OS using Azure CLI.
  • Consider listing Azure CLI before Azure PowerShell to reflect its cross-platform nature.
GitHub Create Pull Request
Azure Resource Manager Parameters in Bicep ...in/articles/azure-resource-manager/bicep/parameters.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is largely platform-neutral in its technical content, focusing on Bicep syntax and concepts. However, in the 'Next steps' section, deployment guidance references Azure CLI and Azure PowerShell, listing CLI first but still giving PowerShell equal prominence. There are no Linux/macOS-specific examples, nor is there mention of platform-specific tooling or patterns outside of CLI/PowerShell. No Windows-only tools or instructions are present, but the inclusion of PowerShell as a primary deployment method may subtly favor Windows users.
Recommendations
  • Add explicit examples or links for deploying Bicep files on Linux/macOS, such as using Azure CLI in Bash or zsh.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Bash/shell environments.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider adding a brief section or note on platform compatibility for all deployment tools.
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
Low 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 frequently presents Azure PowerShell (Windows-centric) examples before Azure CLI, and references PowerShell-specific cmdlets and patterns. While Azure CLI examples are provided (which work cross-platform), the ordering and emphasis on PowerShell may create friction for Linux/macOS users. The local cache path examples do include Linux and macOS, but Windows is listed first. No critical steps are Windows-only, but the documentation leans toward Windows tools and workflows.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add explicit notes that Azure CLI commands work on Linux/macOS and Windows.
  • Balance example ordering: alternate or group CLI and PowerShell examples together.
  • Where possible, minimize reliance on PowerShell-specific cmdlets and highlight CLI as the default.
  • In path examples, consider listing Linux/macOS first or equally.
  • Add a short section for Linux/macOS users with tips or links to relevant setup guides.
GitHub Create Pull Request
Azure Resource Manager Resource declaration in Bicep ...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying supported resource locations, but the PowerShell example is presented first. No other Windows-specific tools or patterns are mentioned, and Linux/macOS users are not excluded from completing any tasks.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to avoid perceived platform bias.
  • Consider providing Bash or shell script snippets for common tasks, where appropriate.
GitHub Create Pull Request
Azure Resource Manager Create and deploy template specs in Bicep ...rticles/azure-resource-manager/bicep/template-specs.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and PowerShell is referenced frequently throughout. While Azure CLI is cross-platform and examples are provided, the ordering and emphasis may create friction for Linux/macOS users by implicitly prioritizing Windows tooling. No Windows-only tools or commands are present, and all tasks can be completed with Azure CLI.
Recommendations
  • Alternate the order of examples so Azure CLI is shown first in some sections.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a short note at the beginning clarifying that all tasks can be performed on Linux/macOS using Azure CLI.
  • Reduce the frequency of PowerShell-specific tips unless there is a unique capability.
  • Where possible, provide Bash script snippets for common workflows (e.g., retrieving template spec IDs).
GitHub Create Pull Request
Azure Resource Manager Create Bicep files with Visual Studio Code ...les/azure-resource-manager/bicep/visual-studio-code.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains cross-platform neutrality, but there are subtle Windows biases. In several places, Windows conventions (e.g., Ctrl+Shift+P, Ctrl+Z) are mentioned first, with macOS alternatives as parentheticals or afterthoughts. When showing how to retrieve Azure resource IDs, Azure CLI and Azure PowerShell are both presented, but PowerShell is given its own tab, and Windows-centric tools (PowerShell, Azure portal) are mentioned before Linux alternatives. No explicit Linux/macOS examples or screenshots are provided, and the documentation does not highlight Linux-specific workflows or issues.
Recommendations
  • Present keyboard shortcuts for Windows and macOS equally (e.g., Ctrl+Shift+P / Cmd+Shift+P) in all instances.
  • When listing command-line tools, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform.
  • Include Linux/macOS-specific notes or screenshots where relevant (e.g., file dialogs, terminal usage).
  • Add troubleshooting tips for Linux/macOS users, such as permissions or path differences.
  • Explicitly state that all features and commands work on Linux/macOS, or note any exceptions.
GitHub Create Pull Request
Azure Resource Manager Create Azure Managed Application that deploys storage account encrypted with customer-managed key ...ed-applications/create-storage-customer-managed-key.md
Low 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 provides command-line build instructions for Bicep files using both PowerShell and Azure CLI, but the PowerShell example is presented first and explicitly labeled, while the Azure CLI example is shown second. There are no Linux/macOS-specific instructions or examples for tasks such as installing prerequisites, using the Azure portal, or verifying deployment. The documentation assumes Visual Studio Code as the editor, which is cross-platform, but does not mention any Linux/macOS-specific considerations or alternative editors. All portal instructions are platform-neutral, but command-line examples and tool mentions lean toward Windows-first presentation.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly mention that all command-line instructions work on Linux/macOS, and provide any necessary platform-specific notes (e.g., installation commands, path differences).
  • Include Linux/macOS-specific installation instructions for Azure CLI and Bicep, or link to them.
  • Clarify that Visual Studio Code is available on Linux/macOS and mention alternative editors if relevant.
  • Add a note that all portal-based steps are platform-agnostic.
GitHub Create Pull Request
Azure Resource Manager Create and publish Azure Managed Application in service catalog ...er/managed-applications/publish-service-catalog-app.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for all command-line tasks, with PowerShell (Windows-centric) examples consistently shown before CLI (cross-platform) examples. PowerShell-specific concepts like 'splatting' are explained, but no equivalent Bash/Linux scripting tips are provided. The use of Visual Studio Code is platform-neutral, and Azure CLI instructions reference Bash, but the ordering and extra detail for PowerShell may subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Add Bash scripting tips or explanations for CLI examples (e.g., variable assignment, line continuation) similar to the PowerShell splatting explanation.
  • Explicitly state that all CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
  • Ensure parity in depth of explanation for both PowerShell and CLI sections.
  • Consider adding a short section on using native Linux tools for packaging (e.g., zip) if relevant.
GitHub Create Pull Request
← Previous Page 14 of 20 Next →