Azure Resource Manager

504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1281 issues found
Showing 251-275 of 1281 flagged pages
Azure Resource Manager Move Azure resources to a new resource group or subscription ...ger/management/move-resource-group-and-subscription.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most operations, but PowerShell is given equal or greater prominence, and some PowerShell examples use Windows-specific syntax (e.g., variable assignment with $var=). There is no explicit mention of Linux or macOS environments, nor are there Bash-specific examples or notes about differences in command usage between platforms. The PowerShell examples are not clearly marked as cross-platform (PowerShell Core), and there are no Linux shell (bash) or macOS-specific instructions, which may disadvantage non-Windows users.
Recommendations
  • Clearly indicate when PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide separate notes if there are differences.
  • Provide explicit Bash shell examples for Azure CLI commands, especially where variable assignment or command syntax may differ between Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
  • Add a section or callout clarifying that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation instructions for each OS.
  • Where PowerShell is presented, ensure that it is not assumed to be the default or primary automation tool, and avoid using Windows-specific idioms unless necessary.
  • Include troubleshooting or environment setup notes for Linux/macOS users, such as authentication differences or file path conventions.
GitHub Create Pull Request
Azure Resource Manager Evaluate a cloud workload for relocation ...azure-resource-manager/management/relocate-evaluate.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as PowerShell for moving Azure Public IP configurations, and by omitting Linux-specific examples or equivalent CLI commands. All examples and tool recommendations are focused on Azure Portal or Windows-based utilities, with no mention of Linux shell commands, cross-platform scripting, or open-source alternatives. The documentation assumes users are operating in a Windows environment and does not provide guidance for Linux users.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside or instead of PowerShell references, especially for tasks like moving Azure Public IP configurations.
  • Explicitly mention cross-platform tools and approaches, such as Azure CLI, which work on both Windows and Linux.
  • Provide guidance or links for performing discovery and migration tasks from Linux environments.
  • Ensure that tool recommendations (e.g., Azure Resource Explorer, Resource Graph) include instructions for both Windows and Linux users.
  • Add examples of automation scripts in bash or Python, not just PowerShell.
  • Review all referenced documentation links to ensure they include Linux-compatible instructions.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by frequently presenting PowerShell commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash or Linux shell examples. Windows/PowerShell tools are mentioned before or instead of cross-platform alternatives, and some command examples are only given in PowerShell. There is a lack of explicit Linux/Bash examples for key steps, and the use of Windows-centric tools and patterns is prevalent throughout the guide.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for Azure CLI and resource management steps.
  • When listing commands, present Azure CLI (cross-platform) examples first, followed by PowerShell alternatives.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and clarify any platform-specific requirements.
  • Include sample scripts for Linux environments where automation is discussed, not just PowerShell.
  • Review and update references to tools or patterns that are Windows-specific to ensure Linux parity (e.g., avoid Set-AzAksCluster without showing az aks update-acr equivalent).
GitHub Create Pull Request
Azure Resource Manager Relocate Azure App Services to another region ...anager/management/relocation/relocation-app-service.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific paths and terminology (e.g., %HOME%\site), references to Windows-centric tools (Kudu, FTP credentials), and PowerShell being highlighted in next steps and resource links. Linux equivalents, such as Linux file paths, SSH/SFTP, or bash/CLI examples, are missing or mentioned after Windows tools. The page lacks explicit Linux-focused guidance or parity in examples and tool references.
Recommendations
  • Include Linux-specific examples and terminology, such as $HOME/site and Linux file system paths.
  • Provide guidance for accessing files and deploying via SSH/SFTP, not just FTP/Kudu.
  • Add Azure CLI and bash script examples alongside or before PowerShell examples.
  • Reference Linux-native tools and deployment patterns (e.g., rsync, SCP, tar) for backup/restore and file transfer.
  • Ensure documentation links and next steps include Linux and cross-platform options, not just PowerShell.
  • Clarify that App Service supports both Windows and Linux, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently lists Windows-centric tools (Azure PowerShell, Azure portal) before cross-platform or Linux-friendly options (Azure CLI). In several places, PowerShell is mentioned alongside the Azure portal and before the Azure CLI, and there are no Linux-specific examples or guidance. The documentation assumes familiarity with Windows tooling and patterns, which may disadvantage Linux users.
Recommendations
  • Alternate the order of tool mentions (e.g., list Azure CLI before PowerShell in some sections, or group them as 'Azure CLI or PowerShell').
  • Provide explicit Linux command-line examples using Azure CLI, especially for common tasks like creating VNets, subnets, and Cosmos DB accounts.
  • Include screenshots or references to Linux terminals where appropriate.
  • Add a section or callout for Linux users, highlighting any differences or additional steps.
  • Ensure parity in instructions and links for both Azure CLI and PowerShell, avoiding the implication that PowerShell is the default or preferred method.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention of Azure CLI (cross-platform) or Bash scripting. All automation and scripting guidance is given in PowerShell, which is traditionally Windows-centric, and there are no Linux-specific instructions or examples. The structure and ordering of examples also place PowerShell before any Linux-friendly alternatives, and there is no reference to Linux tools or patterns.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash scripting examples where appropriate, especially for template manipulation and deployment.
  • Explicitly mention that the guidance applies to both Windows and Linux environments, and clarify any OS-specific requirements.
  • Provide links to documentation on using Azure CLI and Bash for resource export, modification, and deployment.
  • Consider adding a 'Linux' or 'Cross-platform' tab alongside 'Azure portal' and 'PowerShell' for each step.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Hubs to another region ...-manager/management/relocation/relocation-event-hub.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a dedicated PowerShell tab for template modification, referencing PowerShell-specific commands (Get-AzLocation), and omitting equivalent Linux/bash/CLI examples. The Azure portal is platform-agnostic, but the scripting and automation guidance is focused on PowerShell, with no mention of Bash, Azure CLI, or Linux shell alternatives. This may disadvantage users on Linux or macOS who do not use PowerShell.
Recommendations
  • Add a Linux/bash/Azure CLI tab alongside the PowerShell tab for template modification and deployment steps.
  • Include Azure CLI commands for obtaining region codes (e.g., 'az account list-locations').
  • Ensure all scripting examples are available in both PowerShell and Bash/Azure CLI formats.
  • Explicitly mention cross-platform support and provide links to Azure CLI documentation.
  • Review all references to PowerShell and ensure parity with Azure CLI or Bash alternatives.
GitHub Create Pull Request
Azure Resource Manager Relocate your Azure Functions app to another Azure region ...-manager/management/relocation/relocation-functions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific environment variables (e.g., %HOME%), mentioning Azure PowerShell and Azure CLI together (with PowerShell listed first), and omitting explicit Linux shell examples or Linux-specific considerations. While containers and Linux hosting are briefly mentioned, there are no concrete Linux command-line examples, nor is there guidance for Linux users on equivalent file paths or deployment patterns.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell/CLI instructions, including file path conventions (e.g., $HOME/site instead of %HOME%\site).
  • Mention Linux tools and deployment patterns (such as az CLI in bash, scp/rsync for file transfer, etc.) where relevant.
  • Ensure that references to environment variables and file paths include both Windows and Linux formats.
  • When listing Azure CLI and PowerShell, alternate the order or clarify that both are cross-platform, and provide Linux-specific usage notes if needed.
  • Add a section or callouts for Linux users, especially regarding persistent storage, file system access, and deployment methods.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Storage Account to another region ...er/management/relocation/relocation-storage-account.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for all major steps (exporting, modifying, deploying, and deleting resources) without offering equivalent CLI (az), Bash, or Linux shell examples. The PowerShell instructions are presented as the only command-line option, and there is no mention of Linux-specific tools or workflows. This may hinder Linux users or those who prefer cross-platform Azure CLI usage.
Recommendations
  • Add equivalent Azure CLI (az) examples for all steps currently covered by PowerShell, including exporting, modifying, deploying, and deleting resources.
  • Include Bash shell command examples where appropriate, especially for scripting tasks.
  • Explicitly mention that AzCopy and Azure CLI are cross-platform, and provide sample commands for Linux/macOS environments.
  • Reorder or parallelize instructions so that CLI and PowerShell examples are presented together, rather than PowerShell-only tabs.
  • Add notes or guidance for Linux/macOS users regarding installation and usage of required tools.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure HDInsight clusters to another region ...-manager/management/relocation/relocation-hdinsight.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell methods and tools alongside or before Azure CLI, with no mention of Linux-specific patterns or shell examples. All command-line examples are either Azure CLI (cross-platform) or Azure PowerShell (Windows-centric), but there are no Bash or Linux shell script examples, nor references to Linux-native tools. The page does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
  • Include explicit Bash shell examples for template export and deployment, demonstrating usage on Linux or macOS.
  • Clarify that Azure CLI is cross-platform and provide examples of running CLI commands in Bash or other Linux shells.
  • Where PowerShell is mentioned, also provide equivalent Bash or shell script instructions, especially for deployment and automation steps.
  • Add notes or sections highlighting Linux compatibility and best practices for HDInsight relocation.
  • Review referenced links to ensure Linux users are not directed to Windows-only instructions.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Network to another region ...er/management/relocation/relocation-virtual-network.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, with extensive PowerShell examples and references to Windows-centric tools (e.g., Notepad). There are no CLI (az), Bash, or Linux-native examples, nor is there mention of cross-platform scripting options. The PowerShell instructions assume a Windows environment and do not address Linux or macOS users, which may hinder accessibility for those on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for all steps, including exporting, editing, and deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Replace or supplement references to Notepad with instructions for using cross-platform editors (e.g., VS Code, nano, vim), or simply refer to 'your preferred text editor'.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide any necessary installation or usage notes for non-Windows environments.
  • Where possible, use generic file manipulation and command-line patterns that work across platforms, or provide parallel instructions for Bash/shell environments.
  • Review and update prerequisites and tool recommendations to ensure parity for Linux/macOS users, including links to relevant documentation for Azure CLI and PowerShell Core.
GitHub Create Pull Request
Azure Resource Manager Azure resource providers and types ...rce-manager/management/resource-providers-and-types.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Azure Service Management API' in a security context, which is a legacy Windows-centric tool. The Azure PowerShell section is presented before Azure CLI, and PowerShell is traditionally associated with Windows environments. There are no explicit Linux shell (bash) or cross-platform scripting examples, nor are Linux-specific tools or patterns mentioned. The page does include Azure CLI and Python examples, which are cross-platform, but the ordering and legacy references favor Windows.
Recommendations
  • Remove or clarify references to 'Windows Azure Service Management API' to avoid implying Windows-only management.
  • Present Azure CLI examples before PowerShell, as CLI is more commonly used in Linux/macOS environments.
  • Add bash shell scripting examples for key tasks to demonstrate Linux parity.
  • Explicitly state that Azure CLI and Python examples work on Linux, macOS, and Windows.
  • Avoid legacy terminology like 'Windows Azure' unless historically necessary.
  • Consider adding a section on managing resource providers using REST API calls with curl or similar Linux-native tools.
GitHub Create Pull Request
Azure Resource Manager Understand how Azure Resource Manager throttles requests ...ce-manager/management/request-limits-and-throttling.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and references, including debugging and header retrieval, but does not offer equivalent Linux shell (bash/curl) examples. PowerShell is presented first and most extensively, with Azure CLI mentioned only briefly and without explicit Linux context. There is no mention of Linux-specific tools or patterns for header retrieval, and the documentation assumes familiarity with Windows-centric tooling.
Recommendations
  • Add bash/curl examples for retrieving response headers, showing how to parse x-ms-ratelimit headers in a Linux shell.
  • Provide Linux-specific Azure CLI usage notes, clarifying any differences in output or usage between platforms.
  • Include examples using popular Linux scripting languages (e.g., Python with requests, bash with curl/grep) to demonstrate parity.
  • Ensure that PowerShell and Windows-centric examples are balanced with Linux alternatives, and avoid presenting Windows tools first unless justified by user demographics.
  • Explicitly mention cross-platform compatibility for Azure CLI and SDKs, and link to relevant Linux documentation where appropriate.
GitHub Create Pull Request
Azure Resource Manager Use tags to organize your Azure resources and management hierarchy ...les/azure-resource-manager/management/tag-resources.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. Azure PowerShell is mentioned as a primary tool for tag operations, and access roles are described in terms of Azure PowerShell and REST API, with no mention of Azure CLI or Linux shell equivalents in those sections. The 'Next steps' section lists Azure PowerShell before Azure CLI, and there are no explicit Linux/bash examples or references to Linux-specific workflows. Windows-centric tools and terminology are prioritized or exclusively mentioned in several places.
Recommendations
  • Include Azure CLI examples and references alongside or before Azure PowerShell, especially in sections describing tag operations and access roles.
  • Provide explicit Linux/bash command examples for common tagging tasks.
  • Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux users.
  • Balance the order of tool references (e.g., list Azure CLI before PowerShell in 'Next steps' or alternate their order in different sections).
  • Add notes or links for Linux users on how to perform equivalent operations using bash, shell scripts, or other Linux-native tools.
GitHub Create Pull Request
Azure Resource Manager Migrating to TLS 1.2 for Azure Resource Manager ...icles/azure-resource-manager/management/tls-support.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows versions and tools first, focusing on .NET Framework and Visual Studio (Windows-only technologies), and providing guidance and troubleshooting steps primarily for PowerShell and WinHTTP (Windows-specific). There are no Linux-specific examples, tools, or troubleshooting steps mentioned, and no guidance for common Linux environments or tools.
Recommendations
  • Add explicit guidance for Linux clients, including how to verify and configure TLS 1.2 support on popular distributions (e.g., Ubuntu, CentOS).
  • Include examples for Linux command-line tools (e.g., curl, openssl, wget) to check TLS versions.
  • Mention how to update or configure TLS settings for common Linux libraries and frameworks (e.g., OpenSSL, Python, Java).
  • List Linux equivalents for troubleshooting tools, such as using 'ssldump', 'openssl s_client', or 'curl -v' to inspect TLS connections.
  • Balance references to Windows and Linux environments throughout the document, ensuring parity in examples and recommendations.
GitHub Create Pull Request
Azure Resource Manager Best practices for templates ...les/azure-resource-manager/templates/best-practices.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets and Windows VM connection guides) are mentioned before or more prominently than their Linux equivalents. The only deployment command conflict discussed is with a PowerShell cmdlet, and the links for connecting to VMs list Windows options first and in greater detail. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. Linux examples and tools are present but less emphasized.
Recommendations
  • Include examples of deployment command conflicts for Azure CLI and Bicep, not just PowerShell.
  • When listing VM connection guides, alternate or balance the order of Windows and Linux links, and provide equal detail for both.
  • Mention Linux-native editors (such as Vim, Emacs, or VS Code on Linux) alongside Visual Studio Code.
  • Reference Linux shell commands (e.g., az CLI) where relevant, especially in sections discussing deployment or scripting.
  • Ensure that any discussion of tools or patterns includes both Windows and Linux equivalents, or clarifies cross-platform compatibility.
GitHub Create Pull Request
Azure Resource Manager Tag support for Azure resources ...icles/azure-resource-manager/management/tag-support.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is primarily a reference table listing Azure resource types and their tag support. However, the few places where command-line tooling is mentioned (e.g., 'Set-AzVm -Generalized' for PowerShell, and 'az vm generalize' for Azure CLI) list the Windows PowerShell command first, and reference Windows-centric tools. There is no mention of Linux-specific tools, nor are Linux shell examples provided. Additionally, the only explicit tool references outside the tables are Windows-oriented (PowerShell), and Windows terminology appears before cross-platform alternatives.
Recommendations
  • When referencing command-line tools, always present cross-platform options (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Include Linux shell examples (e.g., Bash) where command-line usage is discussed, especially for resource management tasks.
  • If mentioning Windows tools or patterns, explicitly note Linux equivalents or alternatives.
  • Review all notes and examples to ensure parity between Windows and Linux, and avoid listing Windows-centric commands first unless there is a technical reason.
  • Consider adding a section or links for Linux users, highlighting any differences or additional steps required for tag management on Linux.
GitHub Create Pull Request
Azure Resource Manager CI/CD with Azure Pipelines and templates ...e-manager/templates/add-template-to-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It focuses almost exclusively on PowerShell scripts and Windows-based tools (such as Azure PowerShell and AzureFileCopy), with all code examples using PowerShell and referencing Windows-specific VM images. There are no Bash or Linux shell script examples, and Linux alternatives (such as AzCopy CLI usage or Bash scripting) are not mentioned. The documentation also presents Windows-based approaches first and does not provide parity for Linux users.
Recommendations
  • Add equivalent Bash or shell script examples for deploying ARM templates, using the Azure CLI (az) instead of PowerShell.
  • Include YAML pipeline examples that use 'ubuntu-latest' or other Linux VM images, demonstrating cross-platform compatibility.
  • Document usage of AzCopy from Linux, and provide instructions for copying files using native Linux tools.
  • Mention and link to Linux-friendly tools and patterns alongside Windows options, ensuring both are covered equally.
  • Reorder sections or provide parallel examples so that Linux and Windows approaches are presented together, not with Windows first.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of an output value ...icles/azure-resource-manager/templates/copy-outputs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell before Azure CLI when discussing supported versions for zero-count copy loops, and the 'Next steps' section links only to a PowerShell deployment guide, omitting Linux/CLI alternatives. There are no examples or guidance for Linux-specific tools or shell environments, and no parity in deployment instructions for non-Windows platforms.
Recommendations
  • Mention Azure CLI before or alongside Azure PowerShell when listing supported tools and versions.
  • Add links to documentation for deploying ARM templates using Azure CLI, Bash, or other Linux-native tools in the 'Next steps' section.
  • Provide example deployment commands for both PowerShell and Azure CLI/Bash to ensure platform parity.
  • Explicitly state that the instructions and templates are platform-agnostic, and highlight cross-platform deployment options.
GitHub Create Pull Request
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all instructions and examples assuming the use of Visual Studio (a Windows-centric IDE) and PowerShell scripts for deployment. There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor are alternative tools (such as Azure CLI, VS Code, or Bash scripts) mentioned. The workflow is tightly coupled to Windows tooling and patterns, and Linux users are not addressed.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as how to create and deploy resource group projects using VS Code, Azure CLI, or other cross-platform tools.
  • Provide Bash script examples for deployment alongside PowerShell scripts.
  • Mention and link to cross-platform alternatives to Visual Studio, such as Visual Studio Code with the Azure Resource Manager Tools extension.
  • Clarify which steps are Windows-specific and offer alternative steps for non-Windows environments.
  • Include notes or sections on how to perform deployments using the Azure CLI, which is available on all platforms.
  • Ensure that all code snippets and deployment instructions have Linux/macOS equivalents where possible.
GitHub Create Pull Request
Azure Resource Manager Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs ...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI is inherently cross-platform, the page repeatedly references Windows-specific shells (CMD, PowerShell) and provides explicit instructions for Windows users before or instead of Linux equivalents. Examples for Bash are present, but guidance for Windows users is often more detailed, and Linux-specific nuances are not equally addressed. There is little mention of Linux tools or shell environments outside Bash, and no explicit parity for Linux/Unix command-line patterns beyond basic Bash usage.
Recommendations
  • Ensure all command-line examples are provided for both Bash (Linux/macOS) and PowerShell/CMD (Windows), with equal detail and clarity.
  • When referencing shell-specific syntax (e.g., arrays, variables), provide side-by-side examples for Bash, PowerShell, and CMD.
  • Explicitly mention Linux/macOS environments in prerequisites and instructions, not just Windows.
  • Include troubleshooting tips or notes for common Linux/macOS issues (e.g., file permissions, path formats).
  • Reference Linux tools (e.g., curl, jq) where appropriate, and avoid assuming Windows as the default environment.
  • Add a section or table summarizing differences in Azure CLI usage between Windows and Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Template deployment what-if ...les/azure-resource-manager/templates/deploy-what-if.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is featured prominently throughout, with examples and explanations often presented before Azure CLI equivalents. The output samples and walkthroughs use PowerShell syntax and conventions, and the confirmation prompts are shown in PowerShell style. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there any examples tailored for Linux users (such as shell scripting or differences in CLI usage on Linux). The installation instructions for Azure CLI are platform-neutral, but PowerShell module installation is described in detail, reinforcing a Windows-first approach.
Recommendations
  • Include explicit Bash/Linux shell examples alongside PowerShell, especially for output parsing and scripting.
  • Present Azure CLI examples before PowerShell in sections where both are supported, or alternate the order.
  • Add notes on platform differences (e.g., how to install PowerShell Core on Linux, or how CLI output may differ on Linux terminals).
  • Show screenshots and output samples from both Windows (PowerShell) and Linux (Bash/CLI) environments.
  • Reference Linux tools and patterns (e.g., jq for JSON parsing, grep/awk for text processing) in programmatic sections.
  • Clarify that all CLI commands work cross-platform and highlight any platform-specific caveats.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents Windows-centric tooling (PowerShell) alongside Azure CLI, often giving PowerShell examples equal or greater prominence. There are no explicit Linux shell (bash) or macOS-specific examples, and installation instructions for Azure CLI and PowerShell do not address platform differences. The examples and command syntax assume either PowerShell or Azure CLI, but do not show Linux-native usage (e.g., bash scripting, environment variables, or package managers like apt/yum/homebrew). There is no mention of Linux-specific considerations, nor are Linux tools or shell patterns (such as piping, jq, or curl) used or referenced.
Recommendations
  • Add explicit Linux (bash) examples for all CLI commands, showing usage in a Linux shell, including environment variable handling and output parsing (e.g., using jq).
  • Clarify installation instructions for Azure CLI and PowerShell by specifying platform-specific steps (e.g., apt/yum/homebrew for CLI, and note that PowerShell is not native to Linux).
  • When presenting command tabs, default to Azure CLI (cross-platform) first, and clarify that PowerShell is primarily a Windows tool (with limited Linux support).
  • Include notes or sections on Linux/macOS compatibility, especially for scripting and automation scenarios.
  • Show how to use REST API examples with curl, and SDK examples in a Linux context.
  • Avoid assuming PowerShell is the default scripting environment; highlight bash/zsh/fish alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Integrate Bicep with Azure Pipelines ...ource-manager/bicep/add-template-to-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for resource cleanup, but the PowerShell example is given equal prominence, which can suggest Windows bias. Additionally, the YAML pipeline examples use bash scripting and Ubuntu runners, which is Linux-friendly, but the inline script for Azure CLI uses backticks (`) for line continuation, which is a Windows PowerShell convention and not valid in bash. This can confuse Linux users and suggests a Windows-first approach. There are no explicit Linux-only examples or references to Linux-specific tools, but the presence of PowerShell and Windows-style scripting patterns indicates some Windows bias.
Recommendations
  • Remove or clarify the use of backticks (`) for line continuation in the Azure CLI bash script example; use standard bash line continuation (\) instead.
  • Ensure that CLI examples use syntax appropriate for the specified shell (bash for Linux/macOS, PowerShell for Windows).
  • If PowerShell is included, clearly indicate its platform specificity and provide Linux/macOS equivalents where appropriate.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-only) examples to avoid Windows-first impression.
  • Add explicit notes or sections for Linux/macOS users where there may be platform-specific differences.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are given equal prominence to Azure CLI, but Windows-centric tools and patterns (such as PowerShell scripting, Connect-AzAccount, and ARMClient usage via PowerShell) are featured throughout. Script deployment instructions and management examples are provided for both Azure CLI and PowerShell, but Linux-native shell scripting and deployment via Bash or other Linux tools are not shown. The PowerShell deployment example is given as a full script, while the CLI equivalent is missing. There is no explicit example of deploying with Bash or Linux-native tools, and troubleshooting/monitoring instructions do not mention Linux-specific workflows.
Recommendations
  • Add explicit Bash/Linux shell script examples for deploying Bicep files and managing deployment scripts, not just Azure CLI.
  • Provide parity in deployment instructions: show how to deploy using Bash and Azure CLI, not just PowerShell.
  • Include troubleshooting and monitoring steps using Linux-native tools (e.g., jq, curl, Bash scripting) alongside PowerShell.
  • Clarify that deployment scripts can be authored and run in Linux environments, and provide examples of Linux-based development workflows.
  • Avoid using Windows-centric tools (e.g., ARMClient via PowerShell) exclusively; mention cross-platform alternatives or usage in Bash.
  • Ensure that all code tabs (CLI, PowerShell) are accompanied by Linux-native equivalents where possible.
GitHub Create Pull Request
← Previous Page 11 of 52 Next →