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 201-225 of 492 flagged pages
Azure Resource Manager Use ARM template test toolkit ...icles/azure-resource-manager/templates/test-toolkit.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell on all platforms (Windows, Linux, macOS) to use the ARM template test toolkit. All usage examples, including those for pipelines and custom tests, are exclusively in PowerShell. Windows installation instructions are presented first, and there is no mention of alternative Linux-native tools or shell scripting options. Linux and macOS sections simply instruct users to install PowerShell, rather than providing parity with native shell environments.
Recommendations
  • Provide examples using native Linux/macOS shells (e.g., Bash, zsh) if possible, or clarify that PowerShell is a hard requirement.
  • Explicitly state in the introduction that the toolkit is PowerShell-only and there are no Bash or other shell alternatives.
  • Offer guidance for integrating with Linux-native CI/CD tools (e.g., GitHub Actions, Jenkins) using PowerShell, or note limitations.
  • Consider developing or linking to cross-platform alternatives or wrappers for users who prefer not to install PowerShell.
  • Reorder installation instructions to present all platforms equally, or group by 'PowerShell required' rather than 'Windows first'.
GitHub Create Pull Request
Azure Resource Manager Deployment quota exceeded ...e-manager/troubleshooting/deployment-quota-exceeded.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (with Bash shell) and PowerShell examples for managing deployment quotas. However, the PowerShell section is presented as an equal alternative, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux/macOS alternatives for PowerShell, nor is there guidance for users who may not have access to PowerShell. The CLI examples assume Bash, which is available on Linux/macOS and Windows (via WSL or Git Bash), but this is not clarified. The documentation does not mention cross-platform considerations or recommend CLI for non-Windows users.
Recommendations
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Note that PowerShell is primarily a Windows tool, and recommend Azure CLI for Linux/macOS users.
  • Explicitly state shell requirements for each example (e.g., Bash for CLI, PowerShell for Windows).
  • Consider providing links or brief instructions for installing Azure CLI and Bash on Windows, and PowerShell Core on Linux/macOS if relevant.
  • Add a short section on platform compatibility to guide users to the best tool for their OS.
GitHub Create Pull Request
Azure Resource Manager SKU not available errors ...rce-manager/troubleshooting/error-sku-not-available.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides troubleshooting steps for 'SKU not available' errors in Azure. It presents examples and scripts for both Azure CLI and Azure PowerShell, but the PowerShell section is notably more detailed, with advanced scripting and output formatting. The CLI section is simpler and lacks equivalent depth. The PowerShell examples use Windows-centric tools and patterns, and the CLI examples use Windows path separators (e.g., .\sku-list.json) in the REST section. The ordering of tabs places Azure CLI before PowerShell, but the PowerShell content is more comprehensive. There are no explicit Linux/macOS examples, nor are cross-platform considerations (like shell differences or path formats) discussed.
Recommendations
  • Expand Azure CLI examples to match the depth and functionality of PowerShell scripts, including advanced filtering and output formatting.
  • Provide explicit Linux/macOS shell examples, especially for file paths (e.g., use ./sku-list.json for REST output).
  • Discuss cross-platform differences where relevant, such as command syntax, output formatting, and scripting approaches.
  • Include notes or examples for Bash, zsh, or other common Linux/macOS shells.
  • Ensure parity in troubleshooting steps and script complexity between CLI and PowerShell sections.
GitHub Create Pull Request
Azure Resource Manager Resource quota errors ...source-manager/troubleshooting/error-resource-quota.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for checking quotas, but the PowerShell example is given equal prominence despite being Windows-centric. No explicit Linux/macOS shell examples (e.g., Bash) are provided, nor is there mention of platform-specific differences or guidance for Linux users. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows tools.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, clarifying that Azure CLI is cross-platform.
  • Clearly indicate that PowerShell is available on Linux/macOS, or provide alternative shell commands for those platforms.
  • Where possible, show Azure CLI examples first, as it is cross-platform, or clarify platform applicability for each example.
  • Include a brief note on platform compatibility for both Azure CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Bicep functions for Bicep parameters files ...ource-manager/bicep/bicep-functions-parameters-file.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows a notable Windows bias in the 'readEnvironmentVariable' section, where only PowerShell commands and .NET methods for setting environment variables are provided. There are no Linux/macOS shell equivalents (e.g., bash, export, env) or explanations for non-Windows users. The examples and references are Windows-centric, which may create friction for Linux/macOS users trying to follow along.
Recommendations
  • Add equivalent Linux/macOS shell commands (e.g., export testEnvironmentVariable="Hello World!") for setting environment variables.
  • Include notes or examples for common shells (bash, zsh, etc.) alongside PowerShell examples.
  • Reference cross-platform documentation for environment variable management.
  • Present examples for both Windows and Linux/macOS users, or clarify platform differences where relevant.
GitHub Create Pull Request
Azure Resource Manager Linter rule - no location expressions outside of parameter default values ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides deployment guidance and examples exclusively using Azure PowerShell cmdlets, which are primarily associated with Windows environments. There is no mention of equivalent Azure CLI commands or cross-platform deployment methods, and the discussion of parameter naming conflicts is framed solely around PowerShell usage. This creates friction for Linux/macOS users who typically use Azure CLI or other tools.
Recommendations
  • Add equivalent Azure CLI examples for deploying Bicep templates, including parameter naming considerations.
  • Clarify that the PowerShell guidance applies to users of Azure PowerShell, and provide parallel instructions for CLI users.
  • Mention cross-platform tools and patterns (e.g., Azure CLI, GitHub Actions) where relevant.
  • Reorder or balance examples so that Windows/PowerShell and Linux/CLI approaches are presented equally.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Visual Studio, a Windows-centric IDE, and does not provide Linux/macOS alternatives for authoring Bicep files. While deployment commands are shown for both Azure CLI (cross-platform) and PowerShell (Windows-heavy), the authoring workflow is only described for Visual Studio, with Linux-friendly options relegated to a 'Next steps' link. There are no instructions or screenshots for Linux/macOS environments, nor is Visual Studio Code (cross-platform) covered in the main content.
Recommendations
  • Include authoring instructions and screenshots for Visual Studio Code, which is available on Linux and macOS.
  • Explicitly mention platform compatibility for each tool in the prerequisites section.
  • Present cross-platform options (e.g., Visual Studio Code) alongside Visual Studio, not only as a next step.
  • Clarify that Azure CLI commands work on all platforms and highlight any platform-specific considerations for PowerShell.
  • Consider reordering or parallelizing sections so that Linux/macOS users see relevant guidance without needing to follow external links.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid custom topics to another region ...ment/relocation/relocation-event-grid-custom-topics.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal GUI for all instructions, with screenshots and step-by-step guidance. There are no CLI (az), PowerShell, or bash examples provided, nor is there mention of Linux/macOS-specific workflows. The reliance on the portal is platform-neutral in theory, but in practice, the documentation's screenshots and instructions are tailored to the Windows experience (e.g., zip file handling, editor choice), and there is no parity for users who prefer or require command-line automation, which is common on Linux/macOS.
Recommendations
  • Add equivalent instructions using Azure CLI (az) for exporting, editing, and deploying Resource Manager templates.
  • Include examples for deleting resources via CLI or PowerShell, with explicit notes on cross-platform compatibility.
  • Provide guidance for handling downloaded files (such as unzipping) on Linux/macOS, and mention suitable editors.
  • Consider reordering or supplementing the documentation so that CLI-based workflows are presented alongside or before GUI instructions.
GitHub Create Pull Request
Azure Resource Manager Relocate your Azure Functions app to another Azure region ...-manager/management/relocation/relocation-functions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and CLI scripts together, but lists PowerShell first and does not provide explicit Linux/macOS examples or guidance. The mention of local storage uses Windows-style environment variables (%HOME%), and there is no parity in showing Linux equivalents (e.g., $HOME). There are no explicit Linux/macOS command-line examples, nor are Linux-specific deployment or scripting patterns discussed, despite Azure Functions supporting Linux containers and Linux hosting.
Recommendations
  • Explicitly mention and provide examples for both Azure CLI and PowerShell, with CLI (cross-platform) shown first.
  • When referencing environment variables or file paths, include both Windows (%HOME%) and Linux/macOS ($HOME) syntax.
  • Add a section or callouts for Linux/macOS users, covering any differences in deployment, storage, and scripting.
  • Ensure that any tool or script references (e.g., IaC, deployment scripts) clarify cross-platform compatibility and provide examples for Linux/macOS terminals.
  • Highlight Linux container scenarios with specific instructions or links.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid domains to another region ...management/relocation/relocation-event-grid-domains.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions, with screenshots and step-by-step guidance. There are no examples or instructions for using cross-platform command-line tools such as Azure CLI, PowerShell, or ARM templates via scripts. There is no mention of Linux/macOS-specific workflows, nor are CLI commands provided for users who prefer or require non-GUI automation.
Recommendations
  • Add equivalent instructions for using Azure CLI to export, modify, and redeploy Event Grid domains, including sample commands.
  • Provide PowerShell examples as well, but ensure Azure CLI is shown first or alongside for Linux/macOS parity.
  • Explicitly mention that all steps can be performed via CLI and link to relevant Azure CLI documentation.
  • Include notes or sections for automation scenarios, which are common for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Understand how Azure Resource Manager throttles requests ...ce-manager/management/request-limits-and-throttling.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples and references, including debugging and retrieving header values, with links to PowerShell scripts. PowerShell is presented before Azure CLI, and no Linux/macOS-specific shell examples (e.g., Bash, curl, jq) are given. The Azure CLI examples are present, but PowerShell receives more in-depth coverage and is shown first, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl/jq examples for retrieving header values from REST API responses.
  • Present Azure CLI and Bash/curl examples before or alongside PowerShell to avoid Windows-first ordering.
  • Reference cross-platform scripting resources, not just PowerShell scripts.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting/debugging tips for Linux/macOS environments.
GitHub Create Pull Request
Azure Resource Manager Create parameter file ...es/azure-resource-manager/templates/parameter-files.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying templates with parameter files. However, the PowerShell example uses Windows-style paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool (despite cross-platform support, it's still most familiar to Windows users). Additionally, the section on parameter name conflicts is focused solely on PowerShell, with no mention of similar issues in Bash or Azure CLI. The Visual Studio tip is also Windows-specific. While Linux/macOS users can use Azure CLI, the documentation gives Windows tools and patterns more prominence.
Recommendations
  • Add explicit Linux/macOS path examples (e.g., /home/user/templates/storage.parameters.json) alongside Windows paths in PowerShell examples.
  • Clarify that PowerShell is available cross-platform, and provide Bash or shell script equivalents where possible.
  • Discuss parameter name conflicts in Azure CLI or other platforms, if applicable.
  • Move Azure CLI examples before PowerShell examples to reduce Windows-first bias.
  • Add a note or section for deploying from Linux/macOS environments, including editor/tooling recommendations.
GitHub Create Pull Request
Azure Resource Manager Templates overview .../articles/azure-resource-manager/templates/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates moderate Windows bias. PowerShell is mentioned as the primary example for testing templates (arm-ttk), and Windows-centric tools like Visual Studio are highlighted for authoring templates. The order of deployment options lists PowerShell before REST API and Cloud Shell, and the CI/CD integration section references Visual Studio and Azure DevOps pipelines, which are more commonly used on Windows. Bash is mentioned only as an alternative in deployment scripts, but no Linux-specific examples or tools are provided.
Recommendations
  • Provide Linux-specific examples and tools, such as using Bash scripts for testing and deployment.
  • Highlight cross-platform authoring tools (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio).
  • Include references to Linux package managers or scripting environments where relevant.
  • Offer parity in CI/CD integration examples, such as using GitHub Actions or other Linux-friendly pipelines.
  • List deployment options in a neutral order (e.g., Azure CLI, PowerShell, REST API, Cloud Shell) and clarify cross-platform compatibility.
GitHub Create Pull Request
Azure Resource Manager Roll back on error to successful deployment .../azure-resource-manager/templates/rollback-on-error.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents PowerShell (a Windows-centric tool) examples before Azure CLI, and PowerShell is highlighted as a primary method. File path examples in PowerShell use Windows-style paths (e.g., c:\MyTemplates\azuredeploy.json), reinforcing a Windows environment. There are no explicit Linux/macOS shell examples, nor is there mention of platform-specific considerations for non-Windows users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid Windows-first bias.
  • Include Linux/macOS shell examples (e.g., Bash) and use platform-neutral or Linux-style file paths in CLI examples.
  • Add notes clarifying that Azure CLI works cross-platform and provide guidance for Linux/macOS users where relevant.
  • Explicitly state that PowerShell Core is available cross-platform, or link to installation instructions for non-Windows systems.
GitHub Create Pull Request
Azure Resource Manager Use condition in templates ...-manager/templates/template-tutorial-use-conditions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. The primary example template is for a Windows VM, and all deployment and cleanup scripts are provided only in Azure PowerShell, with no Azure CLI (bash) equivalents. The instructions and screenshots reference Windows-centric workflows and tools, and Linux/macOS users are not given parallel guidance for deploying or managing resources using their preferred tools.
Recommendations
  • Provide equivalent Azure CLI (bash) commands for deployment and cleanup, alongside PowerShell examples.
  • Include a Linux VM template example or mention how to adapt the tutorial for Linux VMs.
  • Present both Windows and Linux examples in parallel, or alternate which is shown first.
  • Clarify that the tutorial applies to all platforms, and explicitly mention steps for Linux/macOS users where workflows differ.
  • Add notes or links to documentation for using ARM templates with Linux/macOS tools.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by relying heavily on Azure PowerShell for enabling debug logging, which cannot be done via Azure CLI. Azure PowerShell is most commonly used on Windows, and no Linux/macOS-specific alternatives or workarounds are provided for enabling debug logging. The page also exclusively references PowerShell cmdlets for critical operations, with Azure CLI only available for viewing or deleting logs, not for enabling them. This creates friction for Linux/macOS users who typically use Azure CLI.
Recommendations
  • Provide a Linux/macOS-compatible method for enabling debug logging, such as supporting this feature in Azure CLI or documenting REST API alternatives.
  • Explicitly mention platform limitations and suggest workarounds (e.g., using a Windows VM, Docker container, or cloud shell with PowerShell).
  • Advocate for parity in tooling so that key features are not exclusive to Windows/PowerShell environments.
  • Add a section clarifying platform support and limitations for each command.
GitHub Create Pull Request
Azure Resource Manager Bicep CLI commands ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation frequently uses Windows-style paths (e.g., c:\jsontemplates) in command examples and presents Windows path syntax before Linux/macOS equivalents. Some commands (install, upgrade, list-versions) are only available via Azure CLI, which is cross-platform but often associated with Windows. The documentation references Azure PowerShell and Windows-specific path conventions, while Linux/macOS paths are only mentioned in a few sections (e.g., restore cache location). There are no explicit Linux/macOS command examples for file paths in most sections, and Windows paths are shown first or exclusively in many cases.
Recommendations
  • For every command example using a Windows path (e.g., c:\jsontemplates), provide an equivalent Linux/macOS example (e.g., /home/user/jsontemplates) side-by-side.
  • When describing file paths, mention both Windows and Linux/macOS conventions, or use placeholder syntax (e.g., <output-directory>) and clarify with OS-specific notes.
  • Add explicit Linux/macOS installation and usage notes where relevant, especially for commands only available via Azure CLI.
  • Avoid referencing Windows tools (like PowerShell) before cross-platform alternatives unless necessary; provide parity in tool recommendations.
  • In sections listing cache locations or environment variables, always show all OS variants together.
GitHub Create Pull Request
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools (Azure PowerShell) and lists them before cross-platform alternatives (Azure CLI). The credential precedence example prioritizes AzureCLI and AzurePowerShell, without mentioning Linux/macOS-specific authentication flows or tools. There are no explicit Linux/macOS examples or guidance, and the authentication section assumes familiarity with Windows-centric tools.
Recommendations
  • Include Linux/macOS-specific examples for authentication, such as using environment variables or managed identities.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide links or examples for installation and usage on those platforms.
  • Mention other credential types (e.g., EnvironmentCredential) earlier and provide practical examples for Linux/macOS users.
  • Avoid listing Windows tools (Azure PowerShell) before cross-platform tools unless there is a technical reason.
  • Add a note or section explicitly addressing Linux/macOS usage and parity.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to create a new resource group .../azure-resource-manager/bicep/create-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes shown first. There are no Linux/macOS-specific notes or examples, and PowerShell is not natively available on most Linux/macOS systems. The documentation does not mention Bash scripting or other Linux-native tools, nor does it clarify cross-platform compatibility for the commands.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and available on Windows, Linux, and macOS.
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
  • Add notes clarifying that PowerShell examples require PowerShell Core on Linux/macOS, or suggest using Azure CLI for those platforms.
  • Include troubleshooting tips or links for installing Azure CLI and PowerShell Core on Linux/macOS.
  • Consider adding Bash script examples for common deployment scenarios.
GitHub Create Pull Request
Azure Resource Manager Decompile a JSON Azure Resource Manager template to Bicep ...ain/articles/azure-resource-manager/bicep/decompile.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting and decompiling ARM templates, with PowerShell (a Windows-centric tool) given its own section and example. Visual Studio Code features are highlighted, which are cross-platform, but no explicit Linux/macOS shell examples (e.g., bash) are provided. The Azure CLI commands are cross-platform, but the documentation does not clarify Linux-specific nuances (such as file path formats or shell redirection differences). Windows tools and patterns (PowerShell, Visual Studio Code) are mentioned before Linux equivalents, and Linux-specific guidance is missing.
Recommendations
  • Add explicit bash/zsh shell examples for Linux/macOS users, especially for file export and redirection.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific differences (e.g., file paths, permissions).
  • Provide guidance for using editors other than Visual Studio Code, or clarify VS Code's cross-platform support.
  • Reorder examples so that cross-platform (CLI) instructions appear before Windows-specific (PowerShell) ones.
  • Mention Linux/macOS tools (e.g., cat, mv) where relevant for file manipulation.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to resource groups ...ure-resource-manager/bicep/deploy-to-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment command examples for both Azure CLI and Azure PowerShell, but the PowerShell example (a Windows-centric tool) is presented as a primary tab alongside Azure CLI, rather than Bash or other Linux-native shells. There are no Bash or Linux shell-specific examples, and PowerShell is highlighted as the only alternative to Azure CLI. This ordering and selection may create friction for Linux/macOS users, as it implicitly prioritizes Windows tooling.
Recommendations
  • Add Bash or Linux shell examples for deployment commands, especially for users who prefer native Linux environments.
  • Explicitly state that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider reordering tabs or examples so that Azure CLI (cross-platform) is shown first, followed by PowerShell.
  • Mention Cloud Shell as a cross-platform, browser-based option for deployments.
  • Where PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to subscription ...azure-resource-manager/bicep/deploy-to-subscription.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 at the subscription scope. However, PowerShell (a Windows-centric tool) is given a dedicated section and is presented alongside Azure CLI, but there is no mention of Bash, Linux shell, or macOS-specific instructions. The references to Cloud Shell are generic and do not clarify Linux/macOS parity. The order of examples sometimes places PowerShell before or at equal prominence with CLI, which may subtly prioritize Windows workflows. There are no explicit Linux/macOS instructions or troubleshooting notes.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for deployment commands, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and can be run from Bash, zsh, etc., on Linux/macOS.
  • Where PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, and provide installation or usage links.
  • Include troubleshooting notes or links for common Linux/macOS issues (e.g., file permissions, line endings, CLI installation).
  • In the 'Deployment commands' section, present Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 all major operations, but PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor any mention of platform-specific considerations for non-Windows users. The CLI examples are generic and would work cross-platform, but the documentation does not clarify this, nor does it offer parity for Linux/macOS users in terms of troubleshooting, environment setup, or alternative tools. PowerShell is given equal or greater prominence, and some output examples are shown only in PowerShell syntax.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and clarify any platform-specific differences if present.
  • Add Bash/zsh shell examples for Linux/macOS users, especially for scripting and output parsing.
  • When showing output or scripting examples, alternate between PowerShell and Bash to demonstrate parity.
  • Include troubleshooting or installation notes for Azure CLI and PowerShell on Linux/macOS.
  • Avoid presenting PowerShell examples first or exclusively; lead with CLI or provide both side-by-side.
  • Mention that Visual Studio Code is cross-platform and highlight any Linux/macOS-specific setup steps if relevant.
GitHub Create Pull Request
Azure Resource Manager Migrate blueprints to deployment stacks ...cles/azure-resource-manager/bicep/migrate-blueprint.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 PowerShell-based export instructions and linking to a PowerShell-specific guide for exporting blueprint definitions. It mentions Azure PowerShell and Azure CLI for configuring locks, but PowerShell is listed first and is the only tool referenced in the critical export step. There are no explicit Linux/macOS command examples or guidance, and the migration workflow assumes familiarity with Windows-centric tooling.
Recommendations
  • Provide explicit Azure CLI instructions and examples for exporting blueprint definitions, alongside PowerShell.
  • Link to cross-platform documentation for both Azure CLI and PowerShell in all relevant steps.
  • Ensure Linux/macOS users are addressed in migration steps, including any platform-specific considerations.
  • Present CLI and PowerShell options together, or list CLI first to emphasize cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in Bicep | Microsoft Docs ...manager/bicep/deployment-script-bicep-configure-dev.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell examples and tooling are presented first and in greater detail, with all deployment and upload scripts shown only in PowerShell. Docker volume mount examples use Windows-style paths (e.g., d:/docker), and there are no Linux/macOS equivalents for these commands. The upload and deployment steps lack bash or cross-platform CLI examples, making it harder for Linux/macOS users to follow along without adaptation.
Recommendations
  • Provide bash or Azure CLI equivalents for all PowerShell scripts, especially for deployment and upload steps.
  • Include Linux/macOS examples for Docker volume mounting (e.g., -v ~/docker:/data).
  • Alternate the order of examples so that CLI/bash and PowerShell are given equal prominence.
  • Explicitly mention cross-platform compatibility and note any platform-specific differences.
  • Add notes or links to platform-agnostic tools where possible.
GitHub Create Pull Request
← Previous Page 9 of 20 Next →