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 376-400 of 492 flagged pages
Azure Resource Manager Set resource location in ARM template .../azure-resource-manager/templates/resource-location.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for retrieving resource locations, but PowerShell is presented first, which may subtly prioritize Windows users. There is no explicit mention of Linux/macOS-specific considerations, but the inclusion of Azure CLI ensures Linux parity for the main task.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to better reflect cross-platform usage.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide any OS-specific notes if relevant.
  • Add a brief section or note confirming that all shown commands are cross-platform, or link to installation guides for CLI on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Scope on extension resource types ...esource-manager/templates/scope-extension-resources.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 ARM templates, but consistently lists PowerShell examples immediately after Azure CLI, and tags the page with 'devx-track-azurepowershell' before 'devx-track-azurecli'. There are no Linux-specific instructions or notes, and PowerShell is a Windows-centric tool, though it is available on Linux. No explicit Windows-only tools are mentioned, but the prominence of PowerShell may signal a slight Windows bias.
Recommendations
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify installation instructions for Linux/macOS users.
  • Consider listing Azure CLI examples first, as it is natively cross-platform and more commonly used on Linux/macOS.
  • Add a note or section highlighting any platform-specific considerations (e.g., authentication, environment setup) for Linux/macOS users.
  • Ensure that all examples work identically on Linux/macOS and provide troubleshooting tips for non-Windows environments if needed.
GitHub Create Pull Request
Azure Resource Manager Deploy ARM template with SAS token - Azure Resource Manager | Microsoft Docs ...ce-manager/templates/secure-template-with-sas-token.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Path Missing Linux Specific Notes
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major steps, ensuring cross-platform coverage. However, PowerShell examples are consistently presented first, and the upload example uses a Windows-style file path (c:\Templates\azuredeploy.json) without mentioning Linux/macOS equivalents. There are no explicit notes or examples for Linux/macOS users regarding file paths or shell differences, and the CLI section briefly mentions Bash but does not address other shells or platforms.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows prioritization.
  • Include Linux/macOS file path examples (e.g., ~/Templates/azuredeploy.json) alongside Windows paths.
  • Add explicit notes or examples for Linux/macOS users regarding shell syntax differences, especially for date/time formatting and environment variables.
  • Clarify that both PowerShell and CLI are cross-platform, and provide links or guidance for installing them on Linux/macOS.
  • Where relevant, mention that Azure CLI commands work natively on Linux/macOS and in WSL.
GitHub Create Pull Request
Azure Resource Manager Roll back on error to successful deployment .../azure-resource-manager/templates/rollback-on-error.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 presents PowerShell (a Windows-centric tool) examples before Azure CLI, and uses Windows-style file paths (e.g., c:\MyTemplates\azuredeploy.json) in PowerShell examples. There is no mention of Linux/macOS equivalents for PowerShell, nor are cross-platform considerations discussed for file paths or scripting environments. While Azure CLI is cross-platform and examples are provided, the ordering and PowerShell emphasis may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly note that PowerShell examples are for Windows and suggest using Azure CLI on Linux/macOS.
  • Use platform-neutral file paths in examples (e.g., ./MyTemplates/azuredeploy.json).
  • Add a note clarifying cross-platform support and recommend tools for each OS.
  • Consider including Bash or shell script examples for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Resource Manager Understand the structure and syntax of ARM templates ...in/articles/azure-resource-manager/templates/syntax.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 page is largely platform-neutral, focusing on the JSON structure and syntax of ARM templates. However, there is mild Windows bias in the section describing JSON schema selection, where Visual Studio Code (cross-platform) is mentioned first, but Visual Studio (Windows-only) is referenced as an alternative editor. Additionally, the only editor-specific guidance is for Visual Studio and Visual Studio Code, with no mention of Linux/macOS-specific editors. There are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents. The CLI instructions and examples are generic and do not favor Windows.
Recommendations
  • Include references to popular Linux/macOS editors (e.g., Vim, Emacs, Sublime Text, JetBrains IDEs) and how to configure ARM template schema validation in those environments.
  • Explicitly mention that Visual Studio Code is available on Windows, Linux, and macOS to reinforce cross-platform support.
  • Add a note or section on deploying ARM templates using Linux/macOS shell environments, if relevant.
  • Ensure any future examples or tooling references include parity for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Template functions - deployment ...rce-manager/templates/template-functions-deployment.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 page is generally platform-neutral, focusing on ARM template functions with JSON-based examples. However, in the 'environment' section, the tip for listing registered environments mentions both the Azure CLI ('az cloud list') and PowerShell ('Get-AzEnvironment'), but lists the CLI command first. The PowerShell cmdlet is referenced, but there are no Linux/macOS-specific notes or examples. No explicit Windows-only tools or patterns are used, but the presence of PowerShell references and lack of Linux/macOS shell examples (e.g., Bash) introduces minor Windows bias.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users where command-line tools are referenced.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux/macOS.
  • Where PowerShell cmdlets are mentioned, also mention equivalent Azure CLI commands and note their platform compatibility.
  • Consider adding a note that all JSON template examples are platform-agnostic and can be used from any OS.
GitHub Create Pull Request
Azure Resource Manager Template functions - resources ...ource-manager/templates/template-functions-resource.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias in the section describing how to discover which resource types have a list operation. The PowerShell example (Get-AzProviderOperation) is presented before the Azure CLI example, and only these two are given. PowerShell is primarily a Windows tool, and its precedence may signal a Windows-first approach. However, the rest of the documentation is platform-neutral, focusing on ARM template syntax and JSON examples.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, but CLI is more commonly used on Linux/macOS.
  • Consider adding Bash or shell script examples for Linux users where relevant.
  • Where PowerShell is mentioned, clarify that it is available cross-platform, but CLI may be preferred for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager template specs ...les/azure-resource-manager/templates/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 provides both Azure PowerShell and Azure CLI examples for all major operations, but consistently lists PowerShell (a Windows-centric tool) examples before CLI, and uses PowerShell-specific notes and recommendations. There is no explicit mention of Linux/macOS environments, nor are there examples using Bash, shell scripting, or platform-specific CLI nuances. The documentation assumes parity between CLI and PowerShell, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support cross-platform users.
  • Add explicit notes confirming that Azure CLI commands work identically on Linux, macOS, and Windows, and clarify any platform-specific differences if they exist.
  • Include example shell scripts (Bash) for common tasks, especially for parameter passing and file handling.
  • Add a section or note about installing and using Azure CLI on Linux/macOS, with links to official installation guides.
  • Avoid PowerShell-specific recommendations unless there is a functional difference; otherwise, generalize instructions to cover all platforms.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add a resource to your Azure Resource Manager template ...ce-manager/templates/template-tutorial-add-resource.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 presents Azure PowerShell deployment instructions before Azure CLI, and uses PowerShell syntax and conventions (e.g., `$templateFile` variable) in both the prerequisites and deployment sections. While Azure CLI instructions are provided, there is a subtle preference for Windows/PowerShell tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell to avoid implicit prioritization of Windows tools.
  • Clarify that `$templateFile` is a shell variable and provide equivalent Bash syntax for Linux/macOS users (e.g., `templateFile=path/to/template.json`).
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide links or notes about installation and usage on Linux/macOS.
  • Include screenshots or examples of the Azure portal on non-Windows platforms if relevant.
  • Review terminology to avoid Windows-centric language (e.g., avoid assuming use of backticks for line continuation, which is PowerShell-specific).
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add template functions to your Azure Resource Manager template ...e-manager/templates/template-tutorial-add-functions.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 presents both Azure PowerShell and Azure CLI examples for deploying the template, but the PowerShell example is shown first and is more visually prominent. There is no explicit mention of Linux/macOS-specific instructions, nor are there any examples of using Linux-native tools or shell environments. The prerequisites mention both Azure PowerShell and Azure CLI, but do not clarify platform differences or recommend cross-platform approaches.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or default to CLI first, as it is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide shell-specific instructions (e.g., bash syntax for variables).
  • Add a note clarifying that PowerShell is primarily used on Windows, while CLI is recommended for Linux/macOS users.
  • Include examples of setting the templateFile variable in bash/zsh.
  • Reference Linux/macOS installation guides for Azure CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add outputs to your Azure Resource Manager template ...rce-manager/templates/template-tutorial-add-outputs.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 presents Azure PowerShell deployment instructions before Azure CLI, and references 'Azure PowerShell' as a primary tool. While both Windows (PowerShell) and cross-platform (CLI) examples are provided, the ordering and emphasis subtly favor Windows users. There are no Linux/macOS-specific instructions or screenshots, and no mention of shell environments outside PowerShell.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide shell-specific guidance (e.g., bash syntax for variables).
  • Include screenshots or references for Linux/macOS environments where relevant.
  • Clarify that Visual Studio Code and Azure CLI are available on all major platforms.
  • Avoid implying PowerShell is the default or preferred method unless justified.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add parameters to your Azure Resource Manager template ...-manager/templates/template-tutorial-add-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 presents both Azure PowerShell and Azure CLI examples for deploying ARM templates, but PowerShell examples are consistently shown first in each section. There is a slight emphasis on PowerShell, which is more commonly used on Windows, and the documentation refers to 'Azure PowerShell or the Azure CLI' with PowerShell mentioned first. However, Linux/macOS users can fully complete all tasks using the Azure CLI examples provided.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add a brief note clarifying that both tools are supported on all platforms, but CLI is often pre-installed or easier to use on Linux/macOS.
  • Ensure that any references to prerequisites or tool installation link to platform-specific instructions for both Windows and Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Create and deploy template ...r/templates/template-tutorial-create-first-template.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 provides both Azure PowerShell and Azure CLI examples for deployment tasks, but PowerShell (a Windows-centric tool) is consistently listed first in code tabs and explanations. Installation instructions for Azure CLI are separated by OS, but the Windows link appears before Linux/macOS. There are minor references to Windows-specific shell behaviors (e.g., line continuation differences), but overall, Linux parity is maintained with CLI examples and explicit Bash shell notes.
Recommendations
  • Alternate the order of PowerShell and Azure CLI tabs or default to CLI first, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and highlight its parity with PowerShell.
  • Provide more examples or screenshots from Linux/macOS environments (e.g., terminal output, file navigation).
  • Clarify that Visual Studio Code is available on all platforms, not just Windows.
  • Add a brief section or note for users who prefer native Linux editors (e.g., Vim, Nano) for template editing.
GitHub Create Pull Request
Azure Resource Manager Create multiple resource instances ...mplates/template-tutorial-create-multiple-instances.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 presents both Azure CLI (Bash) and PowerShell examples for deployment and resource listing, but PowerShell examples are shown first in tab order and are given equal prominence. Visual Studio Code is the only editor mentioned, which is cross-platform, but no Linux-specific tools or workflows are referenced. The Azure portal instructions for resource cleanup are platform-neutral. Overall, there is a slight preference for Windows/PowerShell in example ordering and presentation, but Linux users can complete all tasks using the CLI examples provided.
Recommendations
  • Present CLI (Bash) examples before PowerShell examples to better reflect cross-platform usage.
  • Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.
  • Include notes or links for Linux/macOS users about uploading files to Azure Cloud Shell (e.g., using SCP or browser upload).
  • Ensure that all screenshots and instructions are platform-neutral or provide platform-specific variants if needed.
GitHub Create Pull Request
Azure Resource Manager Use template reference .../templates/template-tutorial-use-template-reference.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 demonstrates a mild Windows bias by presenting PowerShell examples alongside Azure CLI, mentioning PowerShell first in Cloud Shell, and omitting explicit Linux/macOS instructions for file operations (e.g., uploading and saving files). While Azure CLI is cross-platform and Bash is mentioned, the tutorial assumes familiarity with Windows-centric tools and workflows, such as Visual Studio Code and PowerShell, and does not provide Linux-specific alternatives for steps like file saving or uploading.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux/macOS, or suggest alternatives like Vim, nano, or other editors.
  • Provide Linux/macOS-specific instructions for saving and uploading files (e.g., using terminal commands or native file dialogs).
  • Present CLI/Bash examples before PowerShell, or side-by-side, to avoid Windows-first ordering.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows.
  • Include screenshots or instructions showing the process on Linux/macOS where relevant.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot common Azure deployment errors ...ce-manager/troubleshooting/common-deployment-errors.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 parity between Windows and Linux, especially in error mitigation links (e.g., AllocationFailed, SubnetsNotInSameVnet). However, there is a subtle Windows bias in the 'ResourceGroupNotFound' error, where PowerShell is mentioned alongside Azure CLI, but Linux/macOS shell examples are not explicitly referenced. Additionally, in some cases, Windows links are listed before Linux equivalents.
Recommendations
  • Ensure that command-line examples reference both Azure CLI and PowerShell, and clarify that Azure CLI works cross-platform (Linux, macOS, Windows).
  • When listing troubleshooting links for OS-specific issues, alternate the order or present Linux and Windows equally.
  • Add explicit Linux/macOS shell examples where PowerShell is mentioned.
  • Review all linked articles to ensure Linux/macOS users are not directed to Windows-centric solutions.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Use Azure Quickstart Templates ...ger/templates/template-tutorial-quickstart-template.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 presents both Azure PowerShell and Azure CLI examples for template deployment, but PowerShell is shown first and in greater detail. The prerequisites mention 'Azure PowerShell or the Azure CLI' without clarifying platform parity, and the resource cleanup instructions use the Azure Portal (web UI), which is platform-neutral. No Linux-specific tools or shell examples are provided, and there is no mention of macOS. The bias is minor, mainly in ordering and emphasis.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or show CLI first to better reflect cross-platform usage.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide shell-specific instructions where relevant.
  • Add a brief note or section for Linux/macOS users, confirming that all steps (including deployment and cleanup) can be performed from their platforms.
  • Where variables like $templateFile are used, clarify syntax differences (e.g., $templateFile in PowerShell, $templateFile or ./template.json in Bash).
GitHub Create Pull Request
Azure Resource Manager Tutorial - Use parameter files to deploy Azure Resource Manager templates ...ager/templates/template-tutorial-use-parameter-file.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 presents both Azure PowerShell and Azure CLI examples for deployment, but PowerShell examples are shown first in each section. This ordering subtly prioritizes Windows users, as PowerShell is most commonly used on Windows. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and no mention of shell differences (e.g., quoting, path separators) that might affect Linux/macOS users. However, Azure CLI examples are present and correct, so Linux/macOS users can complete all tasks.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Add a brief note clarifying that Azure CLI works cross-platform and is recommended for Linux/macOS.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path formats).
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant.
  • Ensure that all example commands work as written on Linux/macOS (e.g., variable assignment syntax, quoting).
GitHub Create Pull Request
Azure Resource Manager Create a troubleshooting template ...ger/troubleshooting/create-troubleshooting-template.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 demonstrates a mild Windows bias by mentioning Azure PowerShell (a Windows-centric tool) before Azure CLI when describing how to deploy the troubleshooting template. The use of PowerShell is highlighted first, and no explicit Linux/macOS-specific instructions or examples are provided, though Azure CLI is cross-platform.
Recommendations
  • List Azure CLI before Azure PowerShell when describing deployment commands, as CLI is cross-platform.
  • Provide explicit command examples for both Azure CLI and Azure PowerShell, clarifying which platforms they support.
  • Add a note that Azure CLI works on Windows, Linux, and macOS, while Azure PowerShell is primarily used on Windows.
  • Consider including bash shell examples for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Resource Manager Resource not found errors ...re-resource-manager/troubleshooting/error-not-found.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 PowerShell and Azure CLI for subscription context management, listing PowerShell's Set-AzContext before az account set. No explicit Linux bias is present, but Windows tools are referenced first, and no Linux/macOS-specific examples or considerations are given.
Recommendations
  • List Azure CLI commands before PowerShell commands, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Provide examples or notes for Linux/macOS users where command syntax or environment may differ.
  • Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid showing Windows-only UI elements).
GitHub Create Pull Request
Azure Resource Manager Request disallowed by policy error ...ubleshooting/error-policy-requestdisallowedbypolicy.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 investigating policy errors, but the PowerShell section is given equal prominence and detail, despite PowerShell being primarily a Windows tool (though available on Linux/macOS). There are no Linux-specific shell examples (e.g., Bash), and PowerShell examples use Windows-centric patterns and cmdlets. The CLI section is present, but PowerShell is not clearly marked as cross-platform, and no Linux/macOS-specific notes or alternatives are provided.
Recommendations
  • Clarify that PowerShell examples work cross-platform, or provide Bash equivalents for common tasks.
  • Add explicit notes or examples for Linux/macOS users, such as using Bash with Azure CLI.
  • Consider listing Azure CLI (which is more universal) before PowerShell, or marking PowerShell as optional.
  • Avoid deep PowerShell-specific explanations unless parity is given for Bash/CLI users.
GitHub Create Pull Request
Azure Resource Manager Resource provider registration errors ...er/troubleshooting/error-register-resource-provider.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 resolving resource provider registration errors, with PowerShell examples given equal prominence. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. The ordering of examples places Azure CLI first, but the presence of detailed PowerShell instructions may imply a Windows-centric approach. No Windows-only tools are mentioned, and the Azure Portal instructions are platform-neutral.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add Bash or shell script examples for Linux/macOS users, especially for filtering and querying output.
  • Clarify that PowerShell Core is available cross-platform, or provide links to installation instructions for Linux/macOS.
  • Consider adding a brief section on troubleshooting with native Linux tools if relevant.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot ARM template JSON deployments ...ubleshooting/quickstart-troubleshoot-arm-deployment.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 deployment and cleanup tasks, but PowerShell is highlighted as a primary tool alongside Azure CLI in prerequisites and examples. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows-first approach. However, Azure CLI examples are present and shown first in each code tab, and Visual Studio Code is cross-platform. No critical Linux/macOS omissions are present, but the prominence of PowerShell may create mild friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux/macOS and is often preferred for cross-platform scripting.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell examples are retained.
  • Consider adding a note or section for Linux/macOS users, highlighting installation steps for Azure CLI and PowerShell Core on those platforms.
  • Ensure that CLI examples are always shown first and are complete.
  • Avoid language that implies PowerShell is required or preferred unless justified.
GitHub Create Pull Request
Azure Resource Manager Overview of deployment troubleshooting for Bicep files and ARM templates ...les/azure-resource-manager/troubleshooting/overview.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 references both Azure PowerShell and Azure CLI for troubleshooting, but PowerShell commands are mentioned before CLI equivalents, and more detail is given to PowerShell (with direct command links). There are no explicit Linux/macOS examples or references to platform-specific considerations, and the troubleshooting tools listed (Visual Studio Code, Bicep linter, ARM template test toolkit) are cross-platform, but the command-line troubleshooting section subtly prioritizes Windows/PowerShell.
Recommendations
  • Present Azure CLI commands before or alongside PowerShell commands to avoid implicit prioritization of Windows tools.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide examples for Linux/macOS environments where relevant.
  • Include notes or examples for troubleshooting on Linux/macOS, such as shell usage or environment-specific considerations.
  • Ensure parity in detail and linking for CLI commands as is done for PowerShell commands.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot Bicep file deployments ...leshooting/quickstart-troubleshoot-bicep-deployment.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 deployment and cleanup tasks, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after CLI in every code tab. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of platform-specific considerations for Linux/macOS users. The prerequisites list PowerShell and CLI together, but PowerShell is a Windows tool, while CLI is cross-platform. There is no explicit Windows-only tooling, but the parity for Linux/macOS users could be improved.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples first, or providing Bash-specific examples where relevant.
  • Add notes or sections for Linux/macOS users, especially in the prerequisites and command usage.
  • Explicitly mention that PowerShell examples are for Windows users, and CLI is for all platforms.
  • Ensure screenshots and instructions do not assume Visual Studio Code on Windows (e.g., file paths, UI differences).
GitHub Create Pull Request
← Previous Page 16 of 20 Next →