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 476-500 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-azure-button.md ...e-resource-manager/templates/deploy-to-azure-button.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a PowerShell-only example for URL encoding, omitting equivalent Linux/macOS commands (such as curl, python, or bash). This prioritizes Windows tooling and patterns, potentially disadvantaging users on Linux or macOS platforms. No Linux-specific tools or examples are mentioned, and the PowerShell example is presented as the sole method for command-line URL encoding.
Recommendations
  • Add Linux/macOS command-line examples for URL encoding, such as using 'python3 -c "import urllib.parse; print(urllib.parse.quote(input()))"', 'jq', or 'curl'.
  • Explicitly mention that PowerShell is one option and provide parity with Linux shell commands.
  • Consider a cross-platform table or section listing equivalent commands for Windows (PowerShell), Linux (bash), and macOS.
  • Review other sections for similar single-platform examples and ensure Linux/macOS parity throughout.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-modes.md ...s/azure-resource-manager/templates/deployment-modes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell example first, referencing a Windows file path (c:\MyTemplates\storage.json), and listing Azure PowerShell as the primary deployment method in the 'Next steps' section. The CLI example is present but secondary, and there are no explicit Linux shell or cross-platform file path examples.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implying priority.
  • Use platform-neutral file paths (e.g., ./MyTemplates/storage.json) in examples, or provide both Windows and Linux/Mac path formats.
  • Include Bash or shell script examples where appropriate, especially for CLI usage.
  • In 'Next steps', link to both PowerShell and CLI deployment guides equally, and consider referencing cross-platform tools.
  • Explicitly state that both PowerShell and CLI are available on Windows, Linux, and Mac, and provide installation links for each platform.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/parameter-files.md ...es/azure-resource-manager/templates/parameter-files.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI (cross-platform) is covered, Windows-specific tools and workflows are mentioned more prominently. PowerShell examples are given, and file paths in PowerShell use Windows conventions (C:\MyTemplates\...). Visual Studio (Windows-centric) is referenced, and parameter name conflict guidance is focused on PowerShell. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-native editors or workflows.
Recommendations
  • Add Linux/Bash shell examples for deploying templates with parameter files, using Linux-style file paths (e.g., /home/user/storage.parameters.json).
  • Include guidance for using parameter files with Linux-native editors (e.g., vim, nano) and workflows.
  • When referencing PowerShell, clarify that Azure CLI is cross-platform and provide parity in examples.
  • If mentioning Visual Studio, also mention cross-platform alternatives (e.g., VS Code) and their parameter file handling.
  • Add a note that the Azure CLI commands work identically on Linux, macOS, and Windows, and show sample file paths for each.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-resource-quota.md ...source-manager/troubleshooting/error-resource-quota.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for checking quotas, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and no explicit Linux shell examples (such as Bash or native Linux commands) are provided. The portal instructions are platform-neutral, but the command-line guidance lacks Linux-specific context or parity.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, clarifying that Azure CLI is cross-platform and showing usage in a Linux terminal.
  • Clearly state that PowerShell examples are for Windows or for users who have PowerShell Core installed on Linux/macOS.
  • Consider listing Azure CLI (which is cross-platform) before PowerShell to avoid Windows-first impression.
  • Mention installation and usage notes for Azure CLI and PowerShell on Linux/macOS where relevant.
  • If there are any platform-specific limitations or differences, note them in the documentation.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deployment-script.md ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. PowerShell is the only scripting language used for deployment scripts, with no mention of Bash or other Linux-native scripting options. The deployment script example is exclusively written in PowerShell, and references to PowerShell quoting rules and escape characters are provided, while Linux shell equivalents are omitted. The tutorial's workflow and troubleshooting steps focus on PowerShell and Windows-centric tools, with CLI examples present but secondary. There is no guidance for authoring deployment scripts in Bash or for Linux users who may prefer non-PowerShell approaches.
Recommendations
  • Add Bash examples for deployment scripts, especially for tasks like certificate creation and key vault management.
  • Document how to use 'AzureCLI' as the 'kind' property in deploymentScripts, and provide sample Bash scripts.
  • Include troubleshooting steps for Bash-based deployment scripts, such as where to find output and error logs.
  • Reference Linux shell quoting and escape rules alongside PowerShell equivalents.
  • Ensure CLI and Bash examples are given equal prominence to PowerShell, and avoid presenting Windows tools first.
  • Clarify platform requirements and limitations (e.g., if only PowerShell is supported, state this explicitly and provide roadmap for Bash support if planned).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-arm-deployment.md ...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, referencing PowerShell-specific commands, and listing PowerShell as a prerequisite tool. Visual Studio Code is recommended as the code editor, which is cross-platform but often associated with Windows workflows. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The order of examples and prerequisites tends to favor Windows tools or present them before their Linux equivalents.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in Linux/macOS environments.
  • Clarify that Azure CLI works natively on Linux/macOS and provide installation instructions or links for those platforms.
  • Include references to Linux-native editors (e.g., Vim, nano) or clarify that Visual Studio Code is cross-platform.
  • Present CLI examples before PowerShell examples, or alternate the order to avoid implicit prioritization.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell usage is required, and provide installation guidance.
  • Avoid language that implies Windows is the default environment for ARM template troubleshooting.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/data-types.md ...in/articles/azure-resource-manager/bicep/data-types.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Integers' section, where PowerShell is mentioned as the example deployment tool with specific integer range limitations. There is no mention of Linux or cross-platform alternatives (such as Azure CLI or Bash), nor are equivalent examples or caveats provided for non-Windows environments. The rest of the page is platform-neutral and focuses on Bicep syntax and features.
Recommendations
  • When discussing deployment tooling limitations (e.g., integer ranges), mention both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash) environments, including any differences in behavior.
  • Provide examples or notes for Linux/macOS users where relevant, such as how to deploy Bicep files using Azure CLI or Bash.
  • Avoid referencing Windows-specific tools or behaviors exclusively; ensure parity by including cross-platform alternatives in all relevant sections.
  • Consider adding a table or sidebar comparing deployment tool behaviors across platforms for common scenarios (e.g., parameter limits, encoding, file handling).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md ...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a noticeable Windows bias. PowerShell is heavily featured throughout, with most deployment and upload examples using Azure PowerShell scripts. Windows-specific patterns, such as drive letter notation (e.g., d:/docker), are used in Docker volume mount examples, and PowerShell is presented before Bash/CLI alternatives. There is a lack of Linux-native upload examples (e.g., using Bash or az CLI for file uploads), and the Docker instructions assume a Windows file system layout, potentially confusing Linux users.
Recommendations
  • Provide Bash/az CLI examples for uploading deployment scripts to Azure Storage, alongside PowerShell.
  • In Docker instructions, include Linux/macOS volume mount syntax (e.g., /home/user/docker:/data) and clarify platform differences.
  • Ensure that CLI/Bash examples are presented with equal prominence and order as PowerShell examples.
  • Avoid Windows-specific terminology (like drive letters) without also showing Linux/macOS equivalents.
  • Where possible, use platform-neutral language and examples, or clearly label which examples are for Windows and which are for Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md ...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured as a primary automation option throughout, and is listed as a prerequisite alongside Azure CLI. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows bias. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of Linux-native editors or shell environments. There are no Linux-specific instructions, troubleshooting, or notes about platform differences. The documentation does not provide explicit Linux shell examples (e.g., bash scripts), nor does it mention WSL or Linux package managers for installation.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work natively on Linux/macOS and Windows, and provide any necessary platform-specific instructions (e.g., file path syntax, line continuation differences).
  • Include bash shell script examples or highlight usage in Linux terminal environments where appropriate.
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code, or clarify VS Code's cross-platform support.
  • Provide installation instructions for Azure CLI and Bicep on Linux (e.g., apt, yum, snap) in the prerequisites section.
  • If PowerShell is included, clarify that PowerShell Core is cross-platform, and provide installation instructions for Linux/macOS.
  • Add troubleshooting notes for common Linux-specific issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/export-bicep-portal.md ...es/azure-resource-manager/bicep/export-bicep-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell and Azure CLI as alternatives to the Azure portal for exporting ARM JSON templates, but it lists Azure PowerShell before Azure CLI, which may suggest a Windows-first bias. There are no explicit Linux-specific examples or mentions of Linux tools or shell environments (e.g., Bash), and no screenshots or instructions for Linux users. The page does not provide parity in examples or guidance for Linux users, nor does it clarify cross-platform usage for the CLI.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform options, as CLI is natively cross-platform.
  • Include explicit examples and screenshots for exporting templates using Azure CLI on Linux/macOS.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide shell-specific command examples (e.g., Bash).
  • Add a section or note for Linux users, highlighting any differences or considerations when exporting templates.
  • Avoid implying that PowerShell is the primary or default method unless it is truly platform-neutral.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/create-custom-provider.md ...rce-manager/custom-providers/create-custom-provider.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations. However, in the PowerShell sections, it recommends and demonstrates the use of ARMClient (armclient.exe), a Windows-centric tool, without mentioning Linux alternatives or cross-platform REST tools. There are no examples using curl or other standard Linux/Unix tools for REST calls, and ARMClient is presented as the default for PowerShell users, which may exclude Linux users who use PowerShell Core. This creates a subtle Windows bias in tooling recommendations and example coverage.
Recommendations
  • Include examples using curl or httpie for REST operations, especially in sections where ARMClient is recommended.
  • Clarify whether ARMClient works on Linux and macOS, or suggest cross-platform alternatives for PowerShell users.
  • Add explicit Linux/Unix shell examples for REST calls, such as using curl, to ensure parity for non-Windows environments.
  • When recommending tools, mention platform compatibility and provide installation instructions for Linux/macOS as well as Windows.
  • Consider adding a 'Linux/macOS' tab alongside Azure CLI and PowerShell, or clarify that Azure CLI examples are cross-platform.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md ...aged-applications/deploy-service-catalog-quickstart.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples (which are most commonly used on Windows) are consistently presented before Azure CLI examples. Instructions for opening terminals specify PowerShell first and reference Visual Studio Code, which is more popular on Windows. There is heavy use of PowerShell-specific syntax and escape characters, and explanations for JSON formatting focus on PowerShell conventions before Bash/Linux conventions. No Linux-specific tools or patterns (such as native Linux shells or editors) are mentioned, and the CLI examples are presented as secondary. There are no missing Linux examples, but the overall flow and tool selection favor Windows users.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI first in some sections to balance exposure.
  • Explicitly mention Linux and macOS compatibility for Azure CLI, and provide instructions for opening terminals in those environments (e.g., Terminal on macOS, GNOME Terminal on Linux).
  • Include references to popular Linux editors (e.g., Vim, Nano) alongside Visual Studio Code.
  • Clarify that Azure CLI is cross-platform and can be used natively on Linux/macOS, not just via Git Bash on Windows.
  • Add notes on differences in escape characters and line continuation between PowerShell and Bash, and provide troubleshooting tips for Linux users.
  • Where PowerShell-specific syntax is explained, provide equivalent Bash/Linux explanations with equal detail.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/create-storage-customer-managed-key.md ...ed-applications/create-storage-customer-managed-key.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and workflows (Azure PowerShell, Visual Studio Code) are mentioned before or more prominently than their Linux equivalents. The only explicit command-line examples provided are for PowerShell and Azure CLI, but no Linux shell (bash) or cross-platform scripting examples are shown. The instructions for creating resources (Key Vault, managed identity, role assignments, etc.) are exclusively portal-based or reference PowerShell/CLI, with no mention of Linux-specific nuances or alternative editors. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows workflows.
Recommendations
  • Add explicit bash examples for Azure CLI commands, showing usage on Linux/macOS terminals.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary platform-specific notes (e.g., file paths, environment setup).
  • Include instructions for using alternative editors (such as Vim, nano, or other Linux-native editors) for creating Bicep/JSON files.
  • When listing prerequisites, mention Linux and macOS as supported platforms for Azure CLI and Bicep, and provide links to installation instructions for those platforms.
  • Where PowerShell is mentioned, clarify that Azure CLI is fully supported and often preferred on Linux/macOS.
  • Consider adding screenshots or terminal output from Linux environments to demonstrate parity.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/tutorial-create-managed-app-with-custom-provider.md ...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for packaging and uploading the managed application artifacts, while omitting equivalent Linux/macOS shell (bash) examples. Windows tools and patterns (e.g., PowerShell cmdlets like New-AzStorageAccount, Set-AzStorageBlobContent) are used exclusively or before any mention of cross-platform alternatives. There is no guidance for Linux users on how to perform these steps using bash, az CLI, or other platform-agnostic tools, which may hinder parity and accessibility for non-Windows users.
Recommendations
  • Provide equivalent bash (Linux/macOS) scripts for packaging and uploading the application artifacts using Azure CLI commands (e.g., az storage account create, az storage container create, az storage blob upload).
  • Clearly indicate which scripts are platform-specific and offer alternatives for each major OS.
  • Avoid using Windows-specific tools (PowerShell cmdlets) as the only example; always include cross-platform Azure CLI commands where possible.
  • Add a section or tab for Linux/macOS users in all code/script examples, especially for deployment and artifact upload steps.
  • Review all instructions and ensure terminology and tooling are inclusive of Linux and macOS environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/microsoft-resources-move-regions.md ...manager/management/microsoft-resources-move-regions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively using Windows-style file paths (e.g., c:\export), omitting Linux/macOS equivalents. All CLI and PowerShell examples use Windows paths and do not mention or show Linux alternatives. The export and create commands for both Azure PowerShell and Azure CLI use Windows conventions, and there is no guidance for Linux users regarding file system differences or shell syntax.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples, especially for file paths (e.g., use /home/user/export or ./export).
  • Add notes or sections clarifying differences in command usage and file system paths between Windows and Linux/macOS.
  • Ensure that Azure CLI examples use cross-platform compatible syntax and paths.
  • Explicitly mention that PowerShell examples are for Windows, and suggest Bash or other shell alternatives for Linux users where appropriate.
  • Review linked articles (e.g., deploy-powershell.md) to ensure Linux parity in referenced documentation.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub.md ...-manager/management/relocation/relocation-event-hub.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing a dedicated PowerShell tab and referencing PowerShell commands (e.g., Get-AzLocation) for region codes, but does not offer equivalent examples for Linux users (such as Bash/Azure CLI). The instructions for exporting and deploying templates are centered around the Azure portal and PowerShell, with no explicit mention or examples for Linux shell environments or cross-platform CLI usage. This can make it less accessible for users working on Linux or macOS systems.
Recommendations
  • Add a Bash/Azure CLI tab alongside the PowerShell tab in all code sections, showing equivalent commands for Linux/macOS users.
  • Reference Azure CLI commands for obtaining region codes (e.g., 'az account list-locations') in addition to PowerShell.
  • Ensure that all steps involving scripting or command-line tools include both PowerShell and Bash/Azure CLI examples.
  • Explicitly mention that the Azure portal and Azure CLI are cross-platform, and clarify any platform-specific differences.
  • Review all instructions and images to ensure they are not Windows-centric (e.g., file paths, screenshots) and provide alternatives where needed.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-support-resources.md ...-resource-manager/management/move-support-resources.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. It references PowerShell scripts as the method for region moves (e.g., for Azure Automation accounts), and in the SQL Virtual Machine section, it links only to Windows-specific instructions for deleting and re-registering the SQL IaaS Agent extension. There is no mention of Linux CLI equivalents or parity for these operations. Windows tools and patterns (PowerShell, Windows VM extension) are mentioned exclusively or before any Linux alternatives.
Recommendations
  • Provide Azure CLI and/or Bash script examples alongside PowerShell for move operations, especially in sections referencing PowerShell scripts.
  • For SQL Virtual Machine move instructions, include links and guidance for Linux-based SQL VMs, or clarify if the process is identical or different.
  • Audit all references to scripts and tooling to ensure Linux and cross-platform options are presented equally and not as an afterthought.
  • Where Windows-specific limitations or steps are described, explicitly state whether Linux has the same or different requirements.
  • Encourage use of platform-neutral Azure Resource Manager templates and Azure CLI in examples and guidance.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-hdinsight.md ...-manager/management/relocation/relocation-hdinsight.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell as a primary method for exporting and deploying templates, often before or alongside Azure CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or workflows mentioned. The use of PowerShell and references to VS Code (commonly used on Windows) further reinforce the bias, while Linux-native approaches (e.g., Bash scripting, Linux command line) are absent.
Recommendations
  • Add explicit bash/Linux shell examples for exporting and deploying ARM/Bicep templates using Azure CLI.
  • Ensure that Azure CLI commands are presented before or alongside PowerShell commands, highlighting cross-platform compatibility.
  • Include references to Linux-native editors (e.g., Vim, Nano) and terminal environments in deployment instructions.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
  • Review and update all step-by-step instructions to ensure parity between Windows and Linux users, avoiding assumptions of a Windows environment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-network.md ...er/management/relocation/relocation-virtual-network.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, with all command-line examples and automation focused exclusively on PowerShell. There are no examples or guidance for Linux-native tools, such as Azure CLI or Bash scripting, nor are cross-platform considerations mentioned. PowerShell is presented as the sole automation option, which may disadvantage Linux users or those preferring Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell command-line steps, including exporting, editing, and redeploying ARM templates.
  • Explicitly mention that Azure CLI is available and supported on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
  • Where file editing is discussed, suggest cross-platform editors (e.g., vim, nano, VS Code) in addition to Notepad.
  • Ensure that automation and scripting instructions are not Windows-centric; provide Bash script samples or note platform-agnostic approaches.
  • Review and update any references to tools or workflows that are exclusive to Windows or PowerShell to include Linux alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md ...nager/templates/deployment-tutorial-linked-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed Azure PowerShell instructions for storing and deploying templates, with PowerShell examples and workflow presented first and in more detail than the Azure CLI equivalent. The storage/upload workflow is only shown using PowerShell, and Windows-specific tools (e.g., Invoke-WebRequest, Set-AzStorageBlobContent) are used without Linux or cross-platform alternatives. The Azure CLI example is only provided for deployment, not for the storage/upload step, and there is no mention of Linux shell tools or workflows for uploading templates.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all steps, including uploading templates to storage accounts.
  • Mention cross-platform tools and workflows (e.g., curl, az storage blob upload) alongside PowerShell commands.
  • Avoid presenting Windows/PowerShell workflows first; alternate or parallelize with Linux/CLI examples.
  • Clarify which commands are cross-platform and which are Windows-specific, and offer alternatives for Linux/macOS users.
  • Add notes or sections for Linux/macOS users, especially for file paths and shell commands.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/add-template-to-azure-pipelines.md ...e-manager/templates/add-template-to-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. PowerShell scripts are the primary example for deploying ARM templates, with no mention of Bash or cross-platform alternatives. The Azure PowerShell task is featured prominently, and references to Visual Studio and Windows-specific tools (such as AzureFileCopy) are made without Linux equivalents. YAML examples use 'windows-latest' VM images for key tasks, and there are no Linux shell script or AzCopy CLI pipeline examples. Linux users are not shown how to perform these tasks using native tools or Bash scripts.
Recommendations
  • Add equivalent Bash script examples for deploying ARM templates, using the Azure CLI (az deployment group create) in addition to PowerShell.
  • Include YAML pipeline samples that use 'ubuntu-latest' VM images and demonstrate Linux-native approaches.
  • Show how to use AzCopy CLI directly in a Bash script for artifact staging, rather than relying solely on AzureFileCopy (which is Windows-centric).
  • Mention Visual Studio Code as a cross-platform alternative to Visual Studio for ARM template development.
  • Ensure that Linux and macOS users are given clear, step-by-step instructions for all tasks, not just Windows/PowerShell users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/rollback-on-error.md .../azure-resource-manager/templates/rollback-on-error.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell examples before Azure CLI examples, uses Windows-style file paths in PowerShell examples, and references PowerShell-specific tooling. This ordering and tooling may implicitly prioritize Windows users and workflows, even though Azure CLI and REST API are cross-platform. There are no explicit Linux shell examples (e.g., Bash), nor are Linux file path conventions shown.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • Include Linux/Bash-specific examples, especially for file paths and command usage.
  • Clarify that PowerShell examples are for Windows and provide equivalent Bash or shell examples for Linux/Mac users.
  • Use generic or platform-neutral file paths in examples (e.g., ./MyTemplates/azuredeploy.json instead of c:\MyTemplates\azuredeploy.json).
  • Explicitly mention cross-platform compatibility for Azure CLI and REST API sections.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-spec-convert.md ...re-resource-manager/templates/template-spec-convert.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation for converting portal templates to template specs, referencing a .ps1 script and PowerShell parameters. No Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API) are mentioned. The manual method relies on the Azure portal, which is platform-neutral, but all scripting and automation guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for Linux/macOS users.
  • Mention cross-platform tools or REST API options for template migration.
  • Clarify whether the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, and provide instructions if so.
  • Present scripting/automation options for both Windows and Linux users side-by-side, or indicate platform compatibility.
  • Avoid referencing only Windows-specific tools (.ps1 scripts) without alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs.md ...les/azure-resource-manager/templates/template-specs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given for every operation, often listed before Azure CLI equivalents. The use of PowerShell as a primary scripting tool and references to PowerShell-specific commands and patterns (e.g., parameter passing, object syntax) reinforce a Windows-centric approach. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as Bash scripts or notes about cross-platform differences). The CLI examples are present, but PowerShell is consistently highlighted and often appears first, suggesting a preference for Windows tooling.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to signal cross-platform parity.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific syntax or notes where relevant (e.g., variable assignment, file paths).
  • Add a short section or callout for Linux/macOS users, clarifying any differences in command usage, file paths, or environment setup.
  • Where PowerShell object syntax is used, provide equivalent Bash/CLI examples (e.g., for passing parameters, handling outputs).
  • Avoid language such as 'PowerShell script' as the default for automation; use 'script' or 'automation script' and clarify that both PowerShell and Bash are supported.
  • Consider including troubleshooting or setup notes for Linux environments (e.g., file permissions, path separators) if relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-first-template.md ...r/templates/template-tutorial-create-first-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. Windows tools and patterns (PowerShell, Windows paths, screenshots) are consistently presented first or exclusively. Installation instructions for Azure CLI list Windows before Linux and macOS. PowerShell is given equal or greater prominence than Azure CLI, despite CLI being cross-platform. Examples and notes often reference Windows-specific behaviors (e.g., backslashes in CLI commands). There are no explicit Linux shell screenshots, and some instructions (like file path selection) assume Windows conventions. There is no mention of Linux-native editors or shell environments beyond Bash for Azure CLI.
Recommendations
  • Alternate the order of tool presentation (sometimes show Azure CLI before PowerShell) to avoid Windows-first bias.
  • Include Linux-specific screenshots and file navigation instructions where relevant.
  • Explicitly mention Linux-native editors (e.g., Vim, nano, gedit) as alternatives to Visual Studio Code.
  • Provide examples for running Azure CLI commands in other shells (e.g., zsh, fish) and clarify cross-platform differences.
  • Add notes about file path conventions on Linux/macOS (forward slashes, home directory, etc.).
  • Ensure installation instructions for CLI tools do not prioritize Windows over Linux/macOS.
  • Consider including a section on deploying templates from Linux environments, possibly with automation scripts.
GitHub Create Pull Request
← Previous Page 20 of 52 Next →