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 176-200 of 492 flagged pages
Azure Resource Manager Relocate Azure Virtual Machine Scale Sets to another region ...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell as Infrastructure as Code (IAC) tools for redeploying resources, but does not provide explicit Linux/macOS-specific instructions or examples. The export and manipulation of templates is described using the Azure portal (GUI), which is platform-agnostic, but the CLI tooling is mentioned in a way that may imply PowerShell (Windows) as a primary option. No Linux shell (bash) or macOS-specific guidance is provided, and examples are not shown for non-Windows environments.
Recommendations
  • Explicitly mention and provide examples for Azure CLI usage in bash or other Linux/macOS shells.
  • List Azure CLI before PowerShell when describing IAC tools to avoid Windows-first impression.
  • Add step-by-step instructions or code snippets for Linux/macOS users, such as using Azure CLI in bash to export and deploy templates.
  • Clarify that all steps can be performed on Linux/macOS, and highlight any differences or limitations.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Network to another region ...er/management/relocation/relocation-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Azure PowerShell. All command-line examples are exclusively PowerShell-based, with no mention of Azure CLI or Bash, which are preferred by many Linux/macOS users. The PowerShell tab appears before any potential CLI or Bash alternatives, and there are no Linux-specific or cross-platform command-line instructions. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line steps, including exporting, editing, and redeploying templates.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash-friendly commands and file editing instructions.
  • Ensure that the documentation tabs include 'Azure CLI' and/or 'Bash' options, not just 'Portal' and 'PowerShell'.
  • Reference common Linux/macOS editors (e.g., vim, nano) when instructing users to edit JSON files.
  • Clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is often more convenient for those platforms.
GitHub Create Pull Request
Azure Resource Manager Understand how Azure Resource Manager throttles requests ...ce-manager/management/request-limits-and-throttling.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides code examples for retrieving throttling header values primarily in C# and PowerShell, with PowerShell examples appearing first and in greater detail. While Azure CLI examples are included (which are cross-platform), there are no Linux-specific shell (e.g., Bash/curl) examples, and the PowerShell examples dominate the scripting guidance. This creates a subtle Windows bias, especially for users who prefer or require Linux-native tools.
Recommendations
  • Add Linux-native shell examples, such as using curl or wget to retrieve headers from the Azure REST API.
  • Include Bash scripting examples for parsing response headers.
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform usage.
  • Clarify that Azure CLI and REST API calls work identically on Linux/macOS and Windows, and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Azure Resource Manager Migrating to TLS 1.2 for Azure Resource Manager ...icles/azure-resource-manager/management/tls-support.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias. Quick tips and migration guidance focus on Windows versions and .NET Framework, with examples and recommendations centered on Windows tools (Fiddler, Visual Studio, PowerShell). There is no mention of Linux/macOS equivalents, nor are there examples for non-Windows platforms. All troubleshooting and next steps are Windows-centric, leaving Linux/macOS users without clear guidance.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to verify and configure TLS 1.2 support on those platforms.
  • Include examples for popular Linux tools (e.g., OpenSSL, curl) to check TLS versions.
  • Mention relevant package/library updates for Linux/macOS (e.g., OpenSSL, Python, Java).
  • Provide troubleshooting steps for Linux/macOS environments, such as checking TLS support in Apache, Nginx, or other common services.
  • Balance references to Windows tools (Fiddler, PowerShell) with Linux/macOS alternatives (Wireshark, tcpdump, curl).
GitHub Create Pull Request
Azure Resource Manager Best practices for templates ...les/azure-resource-manager/templates/best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is largely platform-neutral, focusing on ARM template best practices. However, there is a notable Windows bias in the 'Parameters' section, where PowerShell deployment command conflicts are discussed in detail, referencing the New-AzResourceGroupDeployment cmdlet and its parameter naming. Additionally, in the 'Resources' section, links to Windows VM connection methods are listed before Linux equivalents, and WinRM setup is mentioned explicitly for Windows. No Linux shell or CLI examples are provided, and Windows tools are referenced before Linux alternatives.
Recommendations
  • Include examples and discussion for deploying ARM templates using Azure CLI (az deployment), especially for Linux/macOS users.
  • When discussing parameter naming conflicts, also mention how Azure CLI handles such cases, not just PowerShell.
  • In the VM connection section, present Linux connection methods (SSH, az vm ssh) before or alongside Windows methods, and provide parity in detail.
  • Reference cross-platform tools (e.g., Visual Studio Code, Azure CLI) equally, and avoid assuming PowerShell as the default.
  • Add explicit Linux/macOS command-line examples where relevant, especially in sections discussing deployment commands.
GitHub Create Pull Request
Azure Resource Manager CI/CD with Azure Pipelines and templates ...e-manager/templates/add-template-to-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: PowerShell is the only scripting example provided, and Windows-specific tools (Azure PowerShell, AzureFileCopy) are used throughout. YAML pipeline examples use 'windows-latest' VM images for file copy and deployment tasks, with no mention of Linux/macOS alternatives or cross-platform scripting. There are no Bash or Linux-native examples, and Windows-centric patterns (such as .ps1 scripts and backslash paths) are shown exclusively or first.
Recommendations
  • Add equivalent Bash or cross-platform script examples for ARM template deployment.
  • Show how to use Linux/macOS agents (e.g., 'ubuntu-latest') for file copy and deployment tasks.
  • Mention and demonstrate Linux-native tools (e.g., AzCopy CLI, Bash scripts) for artifact staging.
  • Provide guidance on adapting PowerShell scripts for Bash or other shells.
  • Ensure all YAML examples use forward slashes for paths or clarify path differences between OSes.
  • Explicitly state platform compatibility for each task and script.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of an output value ...icles/azure-resource-manager/templates/copy-outputs.md
Medium 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 mentions Azure PowerShell before Azure CLI when discussing version requirements for zero-count support, and the 'Next steps' section links only to a PowerShell deployment guide, omitting equivalent Linux/macOS-friendly CLI or REST API deployment guides. No Linux/macOS-specific examples or tools are referenced.
Recommendations
  • List Azure CLI before PowerShell when mentioning supported versions, or mention both together to avoid perceived priority.
  • In the 'Next steps' section, add links to guides for deploying ARM templates using Azure CLI and REST API, not just PowerShell.
  • Explicitly state that both CLI and PowerShell are cross-platform, and provide examples or links for each.
  • Consider including a brief example of deploying the template with Azure CLI, alongside PowerShell.
GitHub Create Pull Request
Azure Resource Manager Data types in ARM templates ...rticles/azure-resource-manager/templates/data-types.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is mostly platform-neutral, but it contains a notable Windows bias in the 'Integers' section, where PowerShell is mentioned as the example command-line tool for deploying templates and its integer limits are described. No equivalent information is provided for Linux/macOS tools (such as Azure CLI or Bash), nor are their limits or usage patterns discussed. This may create friction for non-Windows users seeking parity or clarity.
Recommendations
  • Add equivalent information about integer limits for Azure CLI and other Linux/macOS-compatible SDKs or tools.
  • Provide examples or notes for deploying templates using Azure CLI or Bash, especially where platform-specific behavior may differ.
  • When mentioning command-line tools, list cross-platform options first or together (e.g., 'Azure CLI and PowerShell').
  • Review other sections for implicit tool bias and ensure parity in examples and notes.
GitHub Create Pull Request
Azure Resource Manager Deploy to Azure button ...e-resource-manager/templates/deploy-to-azure-button.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for URL encoding, omitting equivalent Linux/macOS command-line methods (e.g., curl, python, or bash). This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS. No Linux or cross-platform alternatives are mentioned for this step.
Recommendations
  • Add Linux/macOS command-line examples for URL encoding, such as using Python, curl, or bash.
  • Explicitly mention that PowerShell is just one option and provide parity for other platforms.
  • Consider a cross-platform tool or script for URL encoding, or link to online tools with platform-neutral instructions.
GitHub Create Pull Request
Azure Resource Manager Deploy resources to subscription ...e-resource-manager/templates/deploy-to-subscription.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates at the subscription level. However, PowerShell examples are given equal prominence and detail as Azure CLI, and are presented in dedicated sections. There is no explicit mention of Linux/macOS environments, nor are there examples showing Linux-specific shell usage (e.g., bash, zsh), nor any discussion of platform differences. The documentation assumes that Azure CLI and PowerShell are equally available and familiar to all users, which is not the case for many Linux/macOS users, as PowerShell is less commonly used or installed by default. Additionally, the ordering of examples sometimes places PowerShell before or alongside CLI, rather than prioritizing CLI for cross-platform parity.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and available on Linux/macOS, while PowerShell may require additional installation on those platforms.
  • Provide Linux/macOS-specific CLI examples (e.g., bash syntax for environment variables, quoting, and parameter passing).
  • Add notes or links for installing Azure CLI and PowerShell on Linux/macOS, clarifying platform support.
  • Prioritize Azure CLI examples before PowerShell, or clearly mark PowerShell as Windows-centric.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, shell quoting).
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Azure Resource Manager templates ...source-manager/templates/deployment-script-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell examples and terminology are presented first and most frequently, with detailed inline and external script samples using PowerShell. CLI/bash support is mentioned but less emphasized, and Linux/macOS-specific guidance is sparse. Windows tools (e.g., CommandLineToArgvW) and PowerShell-centric troubleshooting are referenced without Linux equivalents. The 'Try it' instructions and management sections prioritize PowerShell, and some sample scripts are PowerShell-only, with CLI/bash examples appearing later or less prominently.
Recommendations
  • Provide equal, side-by-side examples for both PowerShell and Azure CLI/bash throughout the documentation, especially in sample templates and inline/external script sections.
  • Ensure 'Try it' instructions and management workflows include both PowerShell and Azure CLI commands, with clear guidance for Linux/macOS users.
  • Reference Linux/macOS tools and patterns where Windows-specific ones are mentioned (e.g., explain argument parsing for bash, alternatives to CommandLineToArgvW).
  • Clarify that Azure CLI/bash scripts can be used on all platforms, and highlight any platform-specific considerations.
  • Add troubleshooting and development environment setup instructions for Linux/macOS users, not just PowerShell/Windows.
  • When listing supported script types, present Azure CLI/bash first or equally with PowerShell.
GitHub Create Pull Request
Azure Resource Manager Template deployment what-if ...les/azure-resource-manager/templates/deploy-what-if.md
Medium Priority View Details →
Scanned: 2026-01-12 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 examples and terminology are presented first throughout, and output samples use PowerShell syntax. The installation and usage instructions for Azure PowerShell are detailed and prominent, with CLI instructions following. Output screenshots and text samples are in PowerShell format, and confirmation prompts use Windows/PowerShell conventions. There is no mention of Linux-specific shell environments (e.g., Bash, zsh), nor are there examples tailored to Linux/macOS users beyond generic Azure CLI usage.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is shown first in some sections.
  • Provide output samples in both PowerShell and Azure CLI formats, or use CLI as the default where possible.
  • Explicitly mention that Azure CLI works cross-platform and provide examples of running commands in Bash/zsh.
  • Add notes or sections for Linux/macOS users, such as shell-specific tips (e.g., environment variable syntax, line continuation differences).
  • Ensure screenshots and text outputs include CLI output, not just PowerShell.
  • Clarify that PowerShell Core is available on Linux/macOS, but most users on those platforms will use CLI.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in templates | Microsoft Docs .../templates/deployment-script-template-configure-dev.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is used as the primary scripting example throughout, including for tasks that could be performed with cross-platform tools. Uploading scripts to Azure Storage is shown only with PowerShell commands, with no equivalent Bash/Azure CLI example. Docker volume mounting instructions use Windows-style drive letters and folder paths (e.g., d:/docker), and do not provide Linux/macOS mounting syntax. The order of examples and instructions generally favors Windows/PowerShell first, with Linux/macOS alternatives missing or mentioned only in passing.
Recommendations
  • Provide Bash/Azure CLI examples for uploading deployment scripts to Azure Storage, alongside PowerShell.
  • Include Docker volume mounting instructions for Linux and macOS (e.g., /home/user/docker:/data), not just Windows drive letters.
  • Balance the order of examples so that Linux/macOS and Windows users are equally represented, or explicitly call out platform-specific instructions.
  • Add notes or sections clarifying cross-platform compatibility of PowerShell Core (pwsh) and Azure CLI, and provide usage instructions for non-Windows environments.
  • Where screenshots or commands are Windows-specific, add Linux/macOS equivalents.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a linked template ...nager/templates/deployment-tutorial-linked-template.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias by providing only Azure PowerShell scripts for key steps such as downloading and uploading templates to Azure Storage, with no equivalent Bash or Azure CLI examples for Linux/macOS users. The PowerShell script is presented first and is the only option for storing templates, and instructions reference Windows-centric patterns (e.g., $home variable, right-click to paste, Cloud Shell defaults). While deployment is covered for both PowerShell and CLI, the initial setup is Windows/PowerShell-only.
Recommendations
  • Add Bash/Azure CLI examples for downloading templates from GitHub and uploading them to Azure Storage, suitable for Linux/macOS users.
  • Present CLI/Bash examples alongside PowerShell, or even before PowerShell, to ensure parity and inclusivity.
  • Avoid Windows-specific instructions (e.g., right-click to paste) or provide alternatives for Linux/macOS terminals.
  • Clarify that Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Use cross-platform environment variables (e.g., $HOME or ~) and commands in examples.
GitHub Create Pull Request
Azure Resource Manager Create parameter file ...es/azure-resource-manager/templates/parameter-files.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying templates with parameter files. However, the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and the PowerShell section appears after the CLI example but includes additional detail about parameter name conflicts specific to PowerShell. There is also a tip referencing Visual Studio, a Windows-centric tool, without mentioning cross-platform alternatives. No Linux/macOS-specific examples, file paths, or editor recommendations are provided.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/storage.parameters.json) alongside Windows paths.
  • Mention cross-platform editors (e.g., VS Code) in tips, not just Visual Studio.
  • Clarify that Azure CLI works on all platforms and show example usage on Linux/macOS.
  • Add notes or examples for deploying from Linux/macOS environments, including shell syntax.
  • If referencing PowerShell, mention that PowerShell Core is cross-platform and show non-Windows path examples.
GitHub Create Pull Request
Azure Resource Manager Create and deploy template spec ...-manager/templates/quickstart-create-template-specs.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:\Templates\...) in all code examples and instructions, without mentioning Linux/macOS alternatives. There are no explicit Linux/macOS file path examples, nor any notes about adapting commands for those platforms. While Azure CLI and PowerShell are cross-platform, the documentation assumes a Windows environment throughout, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • Include Linux/macOS file path examples (e.g., ~/Templates/createStorageV1.json) alongside Windows paths.
  • Add notes clarifying that file paths should be adapted for the user's OS.
  • Where possible, show both Windows and Linux/macOS command variants, especially for file operations.
  • Explicitly state that Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux/macOS.
  • Avoid using only Windows-centric terminology and examples (e.g., C:\) in cross-platform documentation.
GitHub Create Pull Request
Azure Resource Manager Template functions - scope ...resource-manager/templates/template-functions-scope.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is generally platform-neutral in its main content, focusing on ARM template functions and JSON syntax. However, the only explicit reference to deployment tooling in the 'Next steps' section points users to Azure PowerShell, which is primarily associated with Windows environments. There is no mention of Linux/macOS-friendly alternatives like Azure CLI, nor are cross-platform deployment instructions provided.
Recommendations
  • Include links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • In the 'Next steps' section, provide parity by referencing both Azure PowerShell and Azure CLI deployment guides.
  • Explicitly state that ARM templates and Bicep are platform-agnostic, and highlight cross-platform tooling.
  • Consider ordering deployment tool references alphabetically or by platform neutrality, rather than defaulting to Windows-centric tools.
GitHub Create Pull Request
Azure Resource Manager Develop ARM templates for cloud consistency ...source-manager/templates/template-cloud-consistency.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is frequently used for scripting and verification tasks, with detailed PowerShell cmdlet examples provided throughout. In most cases, Windows/PowerShell examples are given before Azure CLI equivalents, and some tasks (such as verifying template functions in Azure Stack) are only described using PowerShell, with no Linux/macOS alternative. Additionally, references to Windows-specific tooling (e.g., Visual Studio, PowerShell DSC, Windows VM images) are prevalent, while Linux equivalents are not mentioned or are given less prominence.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for verification tasks and template function checks.
  • Ensure Linux/macOS users are explicitly supported in automation and testing sections, including recommendations for compatible IDEs and tools.
  • Include examples of ARM templates deploying Linux VM images and using Linux VM extensions, not just Windows-centric ones.
  • Mention cross-platform alternatives to Windows-specific tools (e.g., VS Code instead of Visual Studio, Bash instead of PowerShell).
  • Where PowerShell is used, clarify whether the script can be run on PowerShell Core (cross-platform) or only Windows PowerShell.
GitHub Create Pull Request
Azure Resource Manager Convert portal template to template spec ...re-resource-manager/templates/template-spec-convert.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only PowerShell-based automation for converting templates, referencing a .ps1 script and showing PowerShell examples exclusively. There are no CLI, Bash, or Linux/macOS-specific instructions or examples. The automated migration path is Windows-centric, with Linux users left to use the manual portal method or seek their own workarounds.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for template migration.
  • Clarify whether the PowerShell script can run on PowerShell Core (cross-platform) and document any requirements.
  • Offer instructions or links for Linux/macOS users to automate migration, or explicitly state limitations.
  • Present manual and automated methods in a platform-neutral order, or note platform applicability up front.
GitHub Create Pull Request
Azure Resource Manager Create a template spec with linked templates ...urce-manager/templates/template-specs-create-linked.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. File path examples use Windows-style paths (e.g., c:\Templates\...), and instructions assume a Windows file system. PowerShell examples are presented first in each code tab, and there is a lack of explicit Linux/macOS file path examples or shell commands for directory creation. While Azure CLI examples are provided, the overall structure and examples favor Windows users.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Templates/...) alongside Windows paths.
  • Provide shell commands for directory creation (e.g., mkdir artifacts) for Linux/macOS users.
  • Alternate the order of PowerShell and CLI tabs, or present CLI examples first to reduce Windows-first bias.
  • Add notes clarifying that the instructions apply to all platforms and specify platform differences where relevant.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS environments.
GitHub Create Pull Request
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
Medium 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 references Windows-specific tools (PowerShell cmdlets like Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) in parameter descriptions and lists PowerShell examples before Azure CLI. This may create friction for Linux/macOS users who do not use PowerShell or its cmdlets.
Recommendations
  • For every mention of a PowerShell cmdlet (e.g., Get-AzSubscription, Get-AzADUser), provide the equivalent Azure CLI command (e.g., az account show, az ad user show) alongside or before the PowerShell example.
  • In parameter descriptions, avoid referencing only PowerShell tools for obtaining values; include CLI alternatives.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows-first bias.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI and VS Code.
  • Add a note clarifying that PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Deploy a template spec as a linked template ...ger/templates/template-specs-deploy-linked-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. File paths are shown in Windows format (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, with no mention of Linux/macOS equivalents. PowerShell examples and notes are presented before Azure CLI, and there is a specific note about a Windows PowerShell issue, but no mention of Linux/macOS-specific considerations. No Linux/macOS shell examples (e.g., bash) or file path formats are provided.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Templates/deployTS/azuredeploy.json) alongside Windows paths.
  • Add notes about any Linux/macOS-specific issues or considerations, similar to the Windows PowerShell note.
  • Present Azure CLI examples first or equally, as CLI is cross-platform, and clarify that both PowerShell and CLI are available on all major OSes.
  • Explicitly mention that the tutorial applies to Linux/macOS and Windows, and provide instructions for locating files on those platforms.
GitHub Create Pull Request
Azure Resource Manager Template with dependent resources ...ate-tutorial-create-templates-with-dependent-resources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using a Windows VM template for the main example and only referencing RDP (a Windows protocol) for verification. There is no mention of Linux VM templates or SSH access, which are standard for Linux users. The deployment instructions do provide both Azure CLI (usable on Linux/macOS) and PowerShell examples, but the core scenario is Windows-centric.
Recommendations
  • Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and provide the corresponding template URL.
  • Add instructions for verifying Linux VM deployment via SSH, including example SSH commands.
  • Clarify that the Azure CLI example works on Linux/macOS and provide any OS-specific notes if needed.
  • Mention both RDP and SSH as ways to access the VM, depending on the OS.
  • Consider alternating or balancing the order of Windows and Linux examples throughout the tutorial.
GitHub Create Pull Request
Azure Resource Manager Use condition in templates ...-manager/templates/template-tutorial-use-conditions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. The main template example is for a Windows VM, and all deployment and cleanup instructions use Azure PowerShell scripts exclusively, with no Azure CLI or Bash equivalents provided. The tutorial references Windows-centric resources and tools first, and does not offer Linux/macOS-specific guidance or examples, making it harder for non-Windows users to follow along.
Recommendations
  • Provide an equivalent ARM template example for deploying a Linux VM, or mention how to adapt the template for Linux.
  • Include Azure CLI (az) commands and Bash script examples alongside PowerShell for deployment and cleanup steps.
  • When referencing Quickstart templates, link to both Windows and Linux VM templates, or clarify that the process is similar for Linux.
  • Explicitly state that the tutorial applies to both Windows and Linux environments, and highlight any differences.
  • Ensure screenshots and instructions are not Windows-specific (e.g., Visual Studio Code usage is cross-platform, but file dialogs and shell instructions can differ).
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault in templates ...e-manager/templates/template-tutorial-use-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for interacting with Azure (creating the key vault, deploying templates, cleaning up resources) use Azure PowerShell, with no Azure CLI or Bash equivalents provided. The tutorial centers on deploying a Windows VM, with no mention of Linux VM templates or Linux-specific deployment steps. Even in Cloud Shell, PowerShell is presented as the default, and validation steps (such as retrieving secrets) use PowerShell-specific syntax. The instructions for connecting to the VM reference downloading an RDP file, which is only relevant for Windows VMs.
Recommendations
  • Provide Azure CLI/Bash equivalents for all PowerShell commands, especially for key vault creation, secret retrieval, template deployment, and resource cleanup.
  • Include a parallel example for deploying a Linux VM, referencing a suitable quickstart template and showing how to use Key Vault secrets for Linux admin credentials.
  • When discussing Cloud Shell, present both PowerShell and Bash options equally, and show how to select and use Bash.
  • For VM connection instructions, add SSH connection steps for Linux VMs.
  • Ensure that references to password requirements and admin credentials link to both Windows and Linux documentation.
GitHub Create Pull Request
← Previous Page 8 of 20 Next →