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 426-450 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/create-visual-studio-deployment-project.md ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All examples and instructions assume the use of Visual Studio (a Windows-centric IDE), and deployment scripts are exclusively shown using PowerShell (Windows-native). There is no mention of Linux or cross-platform alternatives, nor are there examples for Linux users or those using non-Windows environments. The workflow relies on Windows tools and patterns, such as Visual Studio project templates and PowerShell scripts, without providing parity for Linux or CLI-based workflows.
Recommendations
  • Add equivalent instructions for deploying Azure Resource Group projects using cross-platform tools such as VS Code, Azure CLI, or ARM templates directly.
  • Provide Linux/macOS examples for deployment, including bash scripts or Azure CLI commands.
  • Mention and link to alternative workflows for users who do not use Visual Studio or Windows, such as using GitHub Actions, Azure DevOps, or other CI/CD tools.
  • Clarify which steps are Windows-specific and offer guidance for non-Windows environments.
  • Include a section comparing Windows and Linux approaches to deploying resource groups, highlighting any differences and best practices.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/data-types.md ...rticles/azure-resource-manager/templates/data-types.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the example command-line tool for ARM template deployment and integer range limitations, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific examples or notes are provided, and Windows tooling is discussed first and exclusively.
Recommendations
  • Include Linux/Unix equivalents (e.g., Azure CLI, Bash) when discussing command-line tools and SDKs.
  • Add examples or notes about integer range limitations for Azure CLI and other non-Windows deployment tools.
  • Present cross-platform guidance by listing both Windows and Linux tools together, or in a neutral order.
  • Explicitly mention that ARM templates can be deployed from Linux, macOS, and Windows, and provide parity in examples.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cli.md ...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides Azure CLI examples for ARM template deployment, but several sections show a Windows-first bias. Windows-specific shells (CMD, PowerShell) are mentioned before Linux equivalents, and example syntax for Windows is given more prominence or detail. There are references to escaping quotes and passing arrays/objects in Windows shells, but Linux/Bash alternatives are less detailed or sometimes omitted. No explicit Linux tools or patterns are highlighted, and the documentation does not provide parity in example coverage for Linux users.
Recommendations
  • Ensure that examples for Bash/Linux shells are given equal prominence and detail as Windows CMD/PowerShell examples.
  • When describing parameter passing, provide explicit Bash/Linux syntax first or alongside Windows syntax, rather than after.
  • Include troubleshooting tips or notes for common Linux/Bash issues (e.g., quoting, file paths) as are done for Windows.
  • Add references to Linux-specific tools or patterns where relevant (e.g., using curl, jq, or other CLI utilities).
  • Review all example blocks to ensure Linux users are not required to infer syntax from Windows examples.
  • Consider a dedicated section for cross-platform differences, or use tabs/switchers for Windows/Linux/Mac examples.
GitHub Create Pull Request
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-09 00:34
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 shell commands. No Linux tools or cross-platform alternatives are mentioned for this step, and the PowerShell example is presented as the default method. This may hinder Linux users who need parity in instructions.
Recommendations
  • Add a Linux/macOS shell example for URL encoding, such as using `python3 -c 'import urllib.parse; print(urllib.parse.quote("<url>"))'` or `jq -sRr @uri <<< "<url>"`.
  • Explicitly mention that URL encoding can be performed on any platform and provide platform-agnostic or cross-platform solutions.
  • Present both Windows and Linux/macOS examples side-by-side, or use a tabbed format for platform-specific instructions.
  • Avoid implying PowerShell is the only or preferred method for common tasks like URL encoding.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-what-if.md ...les/azure-resource-manager/templates/deploy-what-if.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 consistently presented before Azure CLI in command sections and examples, and output samples are shown in PowerShell format. The installation instructions and command references for PowerShell are more detailed and prominent than those for Azure CLI. Output screenshots and text samples use PowerShell syntax and conventions, which may be less familiar to Linux users. There is no explicit mention of Linux-specific shell environments (e.g., bash, zsh), nor are there any examples tailored for Linux users beyond generic Azure CLI usage.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is sometimes presented first.
  • Provide output samples in both PowerShell and Azure CLI formats, or use CLI output as the default.
  • Include explicit references to Linux environments (e.g., bash, zsh) in CLI examples, and clarify that Azure CLI is cross-platform.
  • Add troubleshooting notes or installation instructions specific to Linux (e.g., apt, yum, snap) for Azure CLI.
  • Ensure that screenshots and text outputs are shown for both PowerShell and CLI, or use CLI as the primary example.
  • Mention that PowerShell Core is available on Linux, if PowerShell examples are retained, and provide guidance for Linux users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-script-template.md ...source-manager/templates/deployment-script-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is consistently presented first and most examples use PowerShell, with CLI/bash examples appearing later and less frequently. Windows-specific tools and APIs (e.g., CommandLineToArgvW, ARMClient in PowerShell) are referenced without Linux alternatives. The 'Try it' instructions and troubleshooting sections focus on PowerShell, and there is limited coverage of bash scripting patterns or Linux-native troubleshooting. There are few, if any, examples using Linux shell scripting idioms, and the external script section prioritizes PowerShell (.ps1) files over bash scripts.
Recommendations
  • Alternate the order of PowerShell and Azure CLI/bash examples so that Linux users see parity in guidance.
  • Provide equivalent bash script examples for every PowerShell example, including inline and external script scenarios.
  • Include Linux-native troubleshooting steps and tools (e.g., using tail, grep, jq) alongside PowerShell-centric guidance.
  • Reference Linux system calls or APIs (e.g., exec, getopt) where CommandLineToArgvW is mentioned, or clarify cross-platform behavior.
  • Expand the 'Try it' and quickstart sections to include Azure CLI/bash instructions and outputs.
  • Ensure external script examples and sample URIs include both .ps1 and .sh files, and clarify extension requirements for bash scripts.
  • Highlight that all deployment scripts run in Linux containers, and provide best practices for bash scripting in that environment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-tutorial-local-template.md ...anager/templates/deployment-tutorial-local-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Azure PowerShell is presented as a primary tool alongside Azure CLI, which is cross-platform, but PowerShell is traditionally Windows-centric. Installation instructions for Azure CLI list Windows before Linux and macOS. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. The Azure portal instructions for resource cleanup use GUI steps, which are more familiar to Windows users. There are no explicit Linux-specific examples or mentions of Linux-native editors or shell environments beyond Bash for CLI examples.
Recommendations
  • Present installation instructions for Azure CLI in a neutral order (e.g., Linux, macOS, Windows) or group them together.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide Bash/Pwsh alternatives where relevant.
  • Include examples using Linux-native editors (e.g., Vim, Nano) for editing JSON templates.
  • Provide resource cleanup instructions using CLI commands (az group delete) in addition to portal GUI steps.
  • Clarify that Bash shell examples work on Linux/macOS and Windows (with WSL or Git Bash), and consider providing Zsh or other shell variants if relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-script-template-configure-dev.md .../templates/deployment-script-template-configure-dev.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing PowerShell-heavy examples, using Windows-centric tooling (PowerShell, drive letters), and presenting Windows patterns before Linux equivalents. While Azure CLI and bash examples are present, key operations such as uploading scripts and deploying templates are shown only with PowerShell commands, with Linux-native alternatives missing or relegated to secondary mentions. Docker usage examples also default to Windows-style volume mounts (drive letters), and there is no explicit Linux shell or file system example for these steps.
Recommendations
  • Provide equivalent bash/Azure CLI commands for uploading deployment scripts to Azure Storage, alongside PowerShell examples.
  • Include Linux-native Docker volume mount examples (e.g., /home/user/docker:/data) and clarify platform differences.
  • Present both PowerShell and bash/CLI examples in parallel, or alternate their order to avoid Windows-first bias.
  • Explicitly mention and demonstrate how Linux/macOS users can perform each step, especially for local development and file sharing.
  • Clarify that PowerShell is available cross-platform, but provide guidance for users who prefer bash or other shells.
  • Add screenshots or terminal output from Linux/macOS environments where appropriate.
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-09 00:34
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 and scripts for storing and deploying templates, with PowerShell presented first and in more depth. Windows-specific tools and patterns (e.g., PowerShell, Write-Host, Read-Host) are used exclusively for the storage/upload steps, while Linux/CLI equivalents are only shown for deployment and not for the full workflow. The Azure CLI example is presented after the PowerShell example, and there is no Bash or Linux shell script for the template upload/storage step, nor any mention of cross-platform differences in the PowerShell workflow.
Recommendations
  • Provide equivalent Azure CLI/Bash examples for all steps, including storing/uploading templates to storage accounts, not just deployment.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention any platform-specific differences or requirements for both Windows and Linux/macOS users.
  • Avoid exclusive use of Windows tools (e.g., PowerShell) for critical workflow steps; ensure Linux users can follow along with native tools.
  • Add notes or links to cross-platform documentation for storage and deployment operations.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/overview.md .../articles/azure-resource-manager/templates/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions both PowerShell and Bash for deployment scripts, it emphasizes PowerShell in tooling (arm-ttk test kit is only available as a PowerShell script), lists PowerShell before Azure CLI in deployment options, and highlights Windows-centric authoring tools (Visual Studio, Visual Studio Code) without mentioning Linux-native alternatives. There are no explicit Linux command-line examples, and some tools (like arm-ttk) are not presented with Linux usage guidance.
Recommendations
  • Provide equal prominence to Azure CLI and Bash examples alongside PowerShell, especially in sections discussing deployment scripts and testing.
  • Clarify if arm-ttk and other PowerShell-based tools can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide Linux installation/use instructions if possible.
  • Include Linux-native or cross-platform authoring tools (e.g., mention that Visual Studio Code is available on Linux/macOS, or suggest other editors).
  • When listing deployment options, alternate the order or explicitly state that all options are cross-platform.
  • Add explicit Linux/Bash command-line examples where relevant, especially in sections discussing deployment, validation, and testing.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool. The Visual Studio tip references a Windows-only IDE. The PowerShell example and related notes appear after the CLI example, but Windows tools and patterns (PowerShell, Visual Studio) are mentioned without Linux equivalents or parity notes. There are no explicit Linux shell examples (e.g., Bash), and no mention of cross-platform editors or file path conventions.
Recommendations
  • Add explicit Linux shell (Bash) examples for deploying templates, including file paths using forward slashes.
  • Clarify that Azure CLI is cross-platform and show examples with Linux/macOS file paths.
  • Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio, and provide equivalent instructions for Linux/macOS users.
  • Note that PowerShell Core is available cross-platform, and provide examples using PowerShell on Linux/macOS.
  • Avoid using Windows-specific file paths in examples, or provide both Windows and Linux/macOS path formats.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-template-specs.md ...-manager/templates/quickstart-create-template-specs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias in several ways: file paths are consistently shown in Windows format (e.g., C:\Templates\...), with no mention of Linux/macOS alternatives; all examples for saving files and referencing templates use Windows paths; and there is no guidance for Linux/macOS users on file locations or shell differences. While both PowerShell and Azure CLI examples are provided, the CLI examples also use Windows-style paths, and there is no explicit mention or demonstration of Linux shell usage or file conventions. Additionally, references to PowerShell and links to PowerShell-specific tutorials are present, but there are no equivalent links or notes for Bash or Linux environments.
Recommendations
  • Provide file path examples for both Windows (C:\Templates\...) and Linux/macOS (/home/user/Templates/...) in all code snippets and instructions.
  • Add explicit notes or tabs for Linux/macOS users, clarifying where to save files and how to reference them in commands.
  • Include Bash-specific variable assignment and command examples where relevant (e.g., export, $(...) syntax).
  • Where PowerShell is mentioned or linked, provide equivalent Bash or cross-platform CLI references.
  • Ensure that screenshots and portal instructions are not Windows-centric (e.g., avoid showing Windows file dialogs only).
  • Add a general note at the top indicating that the guide applies to all platforms, and highlight any platform-specific differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/secure-template-with-sas-token.md ...ce-manager/templates/secure-template-with-sas-token.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented first, and file paths in examples use Windows conventions (e.g., c:\Templates\azuredeploy.json). There is an assumption of familiarity with Windows tools and environments, and the Azure CLI examples reference Bash only in passing, without explicit Linux file path examples or guidance for Linux users. No Linux-specific nuances or troubleshooting are discussed.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid implying a default preference for Windows.
  • Include Linux-style file paths (e.g., /home/user/Templates/azuredeploy.json) in Azure CLI examples to demonstrate parity.
  • Explicitly mention and provide guidance for running Azure CLI commands on Linux/macOS, including any differences in syntax or environment setup.
  • Add troubleshooting notes or tips for common Linux-specific issues (e.g., file permissions, environment variables).
  • Ensure that references to next steps or further reading include both PowerShell and Azure CLI resources equally.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-cloud-consistency.md ...source-manager/templates/template-cloud-consistency.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by consistently providing PowerShell examples before or alongside Azure CLI, referencing Windows-specific tools and patterns (such as PowerShell DSC and .ps1 scripts), and using Windows-centric terminology and artifacts (e.g., 'dotnet-core-music-windows', 'MicrosoftWindowsServer' images). There is a lack of Linux-specific examples, such as Bash scripts or Linux VM images, and Linux VM extension scenarios are not covered. The documentation assumes familiarity with Windows tooling and does not offer parity for Linux users.
Recommendations
  • Provide Linux/Bash equivalents for all PowerShell examples, especially for template function verification and resource provider queries.
  • Include examples using Linux VM images (e.g., Ubuntu, CentOS) and reference Linux publishers/offers/SKUs in template snippets.
  • Demonstrate VM extensions for Linux (e.g., Custom Script for Linux, OMSAgent) and show how to link to .sh scripts as artifacts.
  • Balance references to Windows tools (PowerShell, DSC) with Linux alternatives (Bash, cloud-init, Ansible).
  • Ensure that documentation sections mentioning Windows-specific patterns (such as .ps1 scripts) also mention or show Linux equivalents (.sh scripts).
  • Add notes or guidance for Linux users where tooling or workflow differs, including IDE recommendations and testing approaches.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-create-linked.md ...urce-manager/templates/template-specs-create-linked.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 by consistently using Windows-style file paths (e.g., c:\Templates\...), presenting PowerShell examples before Azure CLI, referencing Windows-specific issues, and omitting explicit Linux/macOS file path examples or shell usage. There are no instructions or examples tailored for Linux/macOS users, such as using forward slashes in paths or bash scripting.
Recommendations
  • Provide Linux/macOS-specific file path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
  • Add bash shell scripting examples where PowerShell is used, especially for variable assignment and command chaining.
  • Explicitly mention cross-platform compatibility for Azure CLI commands and clarify any differences in usage between Windows and Linux/macOS.
  • Address known issues for both Windows and Linux/macOS environments, not just Windows PowerShell.
  • Reorder examples or present them in parallel tabs (Windows/PowerShell and Linux/bash) to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-create-portal-forms.md ...anager/templates/template-specs-create-portal-forms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. PowerShell (a Windows-centric tool) is mentioned first in prerequisites and examples, with explicit references to PowerShell cmdlets for obtaining values (e.g., tenantId and objectId). The creation and update of template specs are shown with both PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI. There are no explicit Linux-only examples, nor are Linux-specific tools or shell patterns (e.g., bash, sh, or Linux file paths) mentioned. The documentation assumes familiarity with PowerShell and Windows tools, and does not provide parity for Linux users in terms of command-line environment or alternative methods for obtaining required values.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
  • Provide explicit instructions or examples for obtaining tenantId and objectId using Azure CLI (e.g., 'az account show', 'az ad user show'), not just PowerShell cmdlets.
  • Include notes or examples for Linux/macOS users, such as using bash shell, file paths, and command syntax.
  • Clarify that both Azure CLI and PowerShell are cross-platform, but highlight any differences in usage or output between Windows and Linux environments.
  • Add troubleshooting or environment setup guidance for Linux users, especially regarding file handling and command-line usage.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-deploy-linked-template.md ...ger/templates/template-specs-deploy-linked-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, referencing PowerShell and Azure CLI examples but defaulting to Windows conventions. PowerShell is presented first in all code tabs, and there is no mention of Linux shell equivalents (e.g., Bash), nor are Linux file path formats shown. There is also a note about a known issue with Windows PowerShell, but no equivalent troubleshooting for Linux environments.
Recommendations
  • Provide Linux/Bash examples alongside PowerShell, including Linux file path conventions (e.g., /home/user/Templates/deployTS/azuredeploy.json).
  • Alternate the order of PowerShell and CLI tabs, or present CLI (which is cross-platform) first.
  • Add notes or troubleshooting guidance for Linux environments if relevant.
  • Explicitly state that Azure CLI commands work on Linux/macOS and show examples using Bash syntax and environment variables.
  • Avoid hardcoding Windows paths in examples; use generic or platform-neutral paths, or show both Windows and Linux formats.
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-09 00:34
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 exclusively providing PowerShell-based migration instructions and examples, referencing a PowerShell script as the primary automation method, and omitting any Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API). The manual steps are portal-based and platform-agnostic, but all scripting and automation guidance is Windows-centric.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for migrating templates, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention cross-platform options for automation, such as REST API or Azure CLI, and provide links or examples.
  • Indicate platform compatibility for the PowerShell script (e.g., if it works with PowerShell Core on Linux/macOS), or provide instructions for running it on non-Windows systems.
  • Reorder or supplement the automation section to present cross-platform methods alongside or before Windows-specific tools.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents both Azure PowerShell and Azure CLI examples for all operations, but PowerShell is always listed first and receives equal or greater emphasis. There are no explicit Linux-specific instructions, nor are there examples for Bash scripting, Linux shell environments, or platform-specific considerations. The use of PowerShell as a primary example and the absence of Linux/Bash-specific guidance may create a subtle bias toward Windows users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI commands work identically on Windows, Linux, and macOS, and provide sample Bash syntax where relevant (e.g., variable assignment, file paths).
  • Add notes or sections for Linux/macOS users, such as guidance on file permissions, path formats, and shell integration.
  • Include troubleshooting tips for common Linux-specific issues (e.g., case sensitivity, permission errors).
  • Clarify that PowerShell is available cross-platform, but that Bash is the default shell on most Linux distributions.
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-09 00:34
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 moderate Windows bias. Windows-specific tools and patterns (PowerShell, Windows paths, screenshots) are consistently presented, often before or with more detail than Linux equivalents. PowerShell is given equal or more prominence than Azure CLI, and installation instructions for CLI list Windows first. There is a lack of explicit Linux shell examples (e.g., no mention of Linux file paths, no screenshots from Linux environments), and Bash is referenced but not illustrated. The guidance for running CLI commands in Windows PowerShell/Command Prompt is present, but there's no similar guidance for Linux users. All screenshots are from Windows environments.
Recommendations
  • Provide Linux-specific examples and screenshots (e.g., using Linux file paths, terminal screenshots).
  • List installation instructions for Azure CLI in a neutral or alphabetical order, or prioritize cross-platform tools.
  • Add explicit guidance for running CLI commands in Linux shells (e.g., bash, zsh), including handling file paths and environment variables.
  • Include notes or tabs for macOS/Linux users where file operations or command syntax may differ.
  • Balance PowerShell and CLI coverage, or clarify CLI as the preferred cross-platform tool.
  • Use generic terminology (e.g., 'terminal' instead of 'Command Prompt') and avoid Windows-centric language where possible.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md ...ate-tutorial-create-templates-with-dependent-resources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively using a Windows VM template for the example, referencing RDP for verification (which is Windows-specific), and not providing a Linux VM equivalent or SSH verification steps. The template selection and deployment walkthrough focus on Windows resources and tools, with no mention of Linux alternatives or parity.
Recommendations
  • Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and provide the corresponding template URL.
  • Add SSH-based verification steps for Linux VMs, alongside RDP instructions for Windows VMs.
  • Mention both Windows and Linux VM deployment scenarios in the introduction and throughout the tutorial.
  • Ensure that resource cleanup and management instructions are applicable to both Windows and Linux environments.
  • Where possible, use generic terminology (e.g., 'connect to your VM') and provide platform-specific instructions in tabs or side notes.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased toward Windows. All examples and instructions focus exclusively on deploying VM extensions to Windows VMs, using PowerShell scripts and Windows-specific tooling (e.g., Install-WindowsFeature, powershell.exe). There is no mention of Linux VM extensions, Bash scripts, or Linux configuration patterns. The quickstart template and script examples are Windows-only, and the tutorial does not provide Linux equivalents or alternatives.
Recommendations
  • Add parallel examples for deploying VM extensions to Linux VMs, including sample Bash scripts and usage of Linux-specific extensions (e.g., CustomScript for Linux).
  • Include a Linux quickstart template (e.g., 'Deploy a simple Linux VM') and show how to edit it to add a VM extension.
  • Provide instructions for running Bash scripts via the Custom Script extension on Linux, including sample commandToExecute values.
  • Mention Linux tools and patterns (e.g., apt-get for installing packages, systemctl for service management) alongside Windows examples.
  • Ensure that both Windows and Linux scenarios are covered equally throughout the tutorial, including prerequisites, deployment, and cleanup steps.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md ...e-manager/templates/template-tutorial-use-key-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias. All example scripts for resource creation, deployment, and cleanup 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 password requirements. The validation step instructs users to connect via RDP, which is Windows-specific, and does not mention SSH or Linux connection methods. Windows tools and patterns (PowerShell, RDP, Windows VM template) are referenced exclusively and/or before any Linux alternatives.
Recommendations
  • Provide Azure CLI and Bash script examples alongside PowerShell for all deployment, validation, and cleanup steps.
  • Include instructions and examples for deploying a Linux VM, referencing a Linux VM template from Azure Quickstart Templates.
  • Mention Linux VM password requirements and provide guidance for connecting to Linux VMs (e.g., SSH) in the validation section.
  • Balance references to Windows and Linux tools and patterns throughout the tutorial, ensuring Linux users have clear, equivalent steps.
  • Where possible, use cross-platform language (e.g., 'administrator account' instead of 'Windows administrator account') and avoid hardcoding Windows-specific values.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-template-reference.md .../templates/template-tutorial-use-template-reference.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. Visual Studio Code is listed as a prerequisite without mention of Linux alternatives or editors. File operations (open/save) are described using GUI steps typical of Windows environments. In deployment instructions, PowerShell is presented as an equal option to Bash/CLI, but the PowerShell example is more verbose and detailed, and the instructions reference Windows-style file paths and prompts. There is no mention of Linux-specific editors, file navigation, or alternative workflows. The clean-up section relies on Azure Portal GUI steps, which are platform-neutral but do not mention CLI alternatives that are popular on Linux.
Recommendations
  • Include Linux-specific instructions for file operations, such as using nano, vim, or command-line tools to open and save files.
  • Mention alternative editors (e.g., Vim, nano, Emacs) in the prerequisites section for Linux users.
  • Provide explicit Linux shell commands for downloading and saving the template file (e.g., using curl or wget).
  • Ensure CLI examples use Linux-friendly file paths and environment variables, and clarify any differences in shell syntax.
  • Add a CLI-based resource group deletion example in the clean-up section.
  • Consider reordering examples so that CLI/Bash instructions appear before PowerShell, or present both equally.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-conditions.md ...-manager/templates/template-tutorial-use-conditions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using a Windows VM template as the example, providing only PowerShell deployment scripts, and referencing Windows-centric tools and patterns. There are no Linux VM examples, nor are there Azure CLI or Bash deployment instructions, despite mentioning Bash as an option in Cloud Shell. The tutorial implicitly assumes a Windows-centric workflow throughout.
Recommendations
  • Add a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and show how the condition parameter works in that context.
  • Provide Azure CLI/Bash deployment instructions alongside PowerShell, including sample scripts for deploying the template and cleaning up resources.
  • Reference both Windows and Linux Quickstart templates, and explain any differences in template structure or deployment steps.
  • Ensure screenshots and walkthroughs are not Windows-specific (e.g., show Linux VM resource definitions, use neutral or cross-platform screenshots).
  • Clarify that the tutorial applies to both Windows and Linux deployments, and highlight any platform-specific considerations.
GitHub Create Pull Request
← Previous Page 18 of 52 Next →