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 326-350 of 1281 flagged pages
Azure Resource Manager Create a template spec with linked templates ...urce-manager/templates/template-specs-create-linked.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Windows Path Examples 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., c:\Templates\...), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues and tools. There is no mention of Linux/MacOS file system conventions, nor are there examples using Bash or Linux-native patterns. The tutorial assumes a Windows environment for local file storage and scripting.
Recommendations
  • Include Linux/MacOS path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid Windows-first bias.
  • Add Bash shell examples for variable assignment and command execution, especially in CLI sections.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/MacOS users (e.g., directory creation commands, file saving locations).
  • Note any platform-specific issues for both Windows and Linux/MacOS, not just Windows PowerShell.
GitHub Create Pull Request
Azure Resource Manager Deploy a template spec as a linked template ...ger/templates/template-specs-deploy-linked-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, presenting PowerShell examples before Azure CLI, and referencing Windows PowerShell-specific issues. There are no Linux/macOS-specific instructions, file path formats, or troubleshooting notes, and all examples use Windows-centric tools and conventions.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Templates/deployTS/azuredeploy.json) alongside Windows paths.
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid implicit prioritization.
  • Add troubleshooting notes relevant to Linux/macOS environments, not just Windows PowerShell.
  • Explicitly state that the examples work on Linux/macOS and provide any necessary adjustments (such as path formats or shell syntax).
  • Reference cross-platform tools and patterns equally, and avoid assuming a Windows environment by default.
GitHub Create Pull Request
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is referenced first and more frequently than Azure CLI, including in parameter descriptions (e.g., 'Get it by using Get-AzSubscription cmdlet'). The instructions and examples for creating and deploying template specs prioritize PowerShell, and Windows-specific tools and patterns (such as Visual Studio Code, which is cross-platform but often associated with Windows) are mentioned. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific considerations or parity in command usage.
Recommendations
  • Provide Linux/bash equivalents for commands where PowerShell is referenced, especially for obtaining values like tenantId and objectId.
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and clarify any OS-specific differences if present.
  • Include examples using native Linux tools (e.g., bash scripts, grep, jq) where appropriate.
  • Avoid referencing only Windows-centric cmdlets in parameter descriptions; include Azure CLI or REST API alternatives.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager template specs ...les/azure-resource-manager/templates/template-specs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is consistently presented as the first example in all command sections, and PowerShell-specific guidance (such as required versions) is called out before Azure CLI. The use of PowerShell as a primary scripting tool and the repeated mention of PowerShell commands and patterns may favor Windows users. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments (such as file paths, shell syntax, or Linux package management). The documentation assumes parity between PowerShell and Azure CLI, but the ordering and emphasis suggest a Windows-first approach.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to reflect cross-platform usage.
  • Explicitly mention that Azure CLI commands are cross-platform and provide Bash-specific syntax or notes where relevant.
  • Include notes or examples for Linux/macOS users, such as file path conventions, shell variable usage, and installation instructions for Azure CLI and PowerShell on non-Windows systems.
  • Avoid language that implies PowerShell is the default or preferred tool; clarify that both PowerShell and CLI are supported equally.
  • Where possible, add troubleshooting or usage tips for Linux environments (e.g., permissions, file system differences).
GitHub Create Pull Request
Azure Resource Manager Template with dependent resources ...ate-tutorial-create-templates-with-dependent-resources.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing exclusively on deploying a Windows VM, referencing only the 'Deploy a simple Windows VM' template, and mentioning RDP (a Windows-specific remote access protocol) as the verification method. There are no examples or instructions for deploying a Linux VM, nor is SSH (the standard Linux remote access method) mentioned. The template selection and verification steps are Windows-centric, and Linux parity is not addressed.
Recommendations
  • Include parallel instructions and examples for deploying a Linux VM, such as referencing the 'Deploy a simple Linux VM' template.
  • Add SSH-based verification steps for Linux VMs alongside RDP instructions for Windows VMs.
  • Present both Windows and Linux options for template selection and deployment, or provide a choice at the beginning of the tutorial.
  • Ensure that resource definitions and parameter explanations cover both Windows and Linux scenarios, including differences in admin credentials and access methods.
  • Clarify in the prerequisites and deployment sections that the tutorial applies to both Windows and Linux environments, and update screenshots and references accordingly.
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. The only supported deployment script type is PowerShell, with no mention of Bash or other Linux-native scripting options. Script examples, troubleshooting steps, and explanations are all PowerShell-centric. While Azure CLI examples are provided for some steps, the core deployment script is exclusively PowerShell, and references to PowerShell quoting rules and escape characters further reinforce the Windows-first approach. There is no guidance or parity for Linux shell scripting, nor any mention of how to achieve similar outcomes using Bash or other Linux tools.
Recommendations
  • Add support and examples for Bash deployment scripts in ARM templates, if available.
  • Provide equivalent Bash scripts for all PowerShell examples, especially for deployment scripts and troubleshooting.
  • Reference Linux shell quoting and escape rules alongside PowerShell-specific notes.
  • Clarify which features are Windows/PowerShell-only and suggest Linux alternatives or workarounds.
  • Ensure troubleshooting steps include Linux/Bash context, such as examining script outputs and errors in a Linux environment.
  • Explicitly mention platform limitations and roadmap for Linux parity if Bash scripting is not yet supported.
GitHub Create Pull Request
Azure Resource Manager Use condition in templates ...-manager/templates/template-tutorial-use-conditions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively using a Windows VM template for the example, providing only PowerShell deployment scripts, and referencing Windows-centric resource names and patterns. There are no Linux VM examples, nor are Azure CLI or Bash deployment instructions provided, despite mentioning Bash as an option in Cloud Shell.
Recommendations
  • Include a parallel example using a Linux VM template, such as 'Deploy a simple Linux VM', to provide parity.
  • Provide Azure CLI/Bash deployment instructions alongside PowerShell, especially in the 'Deploy the template' and 'Clean up resources' sections.
  • Reference both Windows and Linux Quickstart templates in the 'Open a Quickstart template' section.
  • Clarify that the template and deployment steps are applicable to both Windows and Linux environments, or specify any differences.
  • Ensure screenshots and resource naming conventions are not Windows-specific where possible.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Create and deploy template ...r/templates/template-tutorial-create-first-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows tools and patterns (PowerShell, Windows paths, screenshots) are presented first or exclusively. The installation instructions list Windows before Linux and macOS. PowerShell is given equal or greater prominence to Azure CLI, and CLI examples are written for Bash but include notes about adapting for Windows, with no equivalent notes for Linux users. There are no Linux-specific screenshots or workflow guidance, and the editor instructions use Windows-centric terminology (e.g., 'workstation', Visual Studio Code screenshots from Windows).
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Include Linux-specific notes and screenshots, such as file path conventions and terminal environments.
  • Add explicit instructions for running CLI commands in Linux shells (e.g., bash, zsh), including handling file paths and environment variables.
  • Balance installation instructions by listing Linux and macOS before or alongside Windows, or group them together neutrally.
  • Use neutral terminology (e.g., 'computer' or 'machine' instead of 'workstation') and avoid Windows-centric language.
  • Provide equivalent adaptation notes for Linux users when discussing command-line syntax differences.
  • Include screenshots of Visual Studio Code on Linux or macOS, or use generic editor screenshots.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows. All examples use Windows VMs, PowerShell scripts, and Windows-specific tools (e.g., Install-WindowsFeature, powershell.exe). There is no mention of Linux VM extensions, Bash scripts, or Linux configuration patterns. The tutorial exclusively demonstrates deploying a Windows VM and configuring IIS, with no Linux alternatives or parity.
Recommendations
  • Provide parallel examples for Linux VMs, such as deploying a Custom Script Extension to install Apache or Nginx using Bash scripts.
  • Include Linux-specific commands and configuration patterns (e.g., using bash, apt-get, systemctl) alongside PowerShell examples.
  • Reference both Windows and Linux extension documentation and quickstart templates, giving equal prominence.
  • Show how to retrieve the public IP address using both PowerShell and Bash/Azure CLI.
  • Clarify in the introduction that the tutorial focuses on Windows, and link to a Linux-focused equivalent if available.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Export and use Azure portal templates ...manager/templates/template-tutorial-export-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI) in both prerequisites and deployment instructions. PowerShell is listed first in the deployment section, and Visual Studio Code is recommended as the editor, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell examples (e.g., bash), and the portal instructions do not mention platform-specific differences, but the overall flow and tool recommendations lean toward Windows users.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI first to better reflect Linux workflows.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide bash/zsh shell examples where appropriate.
  • Include guidance for using other editors common on Linux (e.g., Vim, Emacs) or clarify that Visual Studio Code is cross-platform.
  • Add notes or links about platform-specific installation and usage for both Azure CLI and PowerShell.
  • Ensure that all instructions (including resource group management and template editing) are equally accessible and clear for Linux users.
GitHub Create Pull Request
Azure Resource Manager Use template reference .../templates/template-tutorial-use-template-reference.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Visual Studio Code is listed as a prerequisite without mention of Linux alternatives. File operations (open/save) are described using GUI steps typical of Windows environments. In deployment instructions, both PowerShell and Azure CLI examples are provided, but PowerShell is listed first and in more detail, which may suggest a Windows-first approach. There are no explicit Linux-specific instructions or examples for file handling, editor usage, or resource cleanup, and no mention of Linux-native tools or workflows.
Recommendations
  • Add explicit instructions for Linux users, such as using editors like Vim, Nano, or VS Code on Linux, and file operations via command line (e.g., wget/curl for downloading templates).
  • Ensure parity in example ordering: present Azure CLI (Bash) examples before or alongside PowerShell, and clarify that CLI works cross-platform.
  • Include resource cleanup instructions using Azure CLI commands, not just portal GUI steps.
  • Mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.
  • Where GUI steps are described, provide equivalent command-line steps for Linux users.
GitHub Create Pull Request
Azure Resource Manager Use ARM template test toolkit ...icles/azure-resource-manager/templates/test-toolkit.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell for all platforms (Windows, Linux, macOS) and providing only PowerShell-based usage examples. Windows installation instructions are listed first, and Windows-specific concepts (such as execution policy) are referenced throughout. There are no examples using native Linux tools or shell scripting, nor is there mention of alternative Linux-first workflows.
Recommendations
  • Provide examples using native Linux shell tools (e.g., bash scripts) where possible, or clarify if PowerShell is the only supported method.
  • Consider listing Linux installation instructions before or alongside Windows to avoid implicit prioritization.
  • If PowerShell is a strict requirement, explicitly state this early in the documentation and explain why.
  • Offer guidance on integrating the toolkit with common Linux CI/CD tools (e.g., shell scripts, cron jobs) in addition to Azure Pipelines.
  • Reference Linux-specific patterns for file extraction, navigation, and permission handling, not just Windows-centric approaches.
  • If feasible, develop and document a cross-platform CLI wrapper or native Linux tool for ARM template testing.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by prioritizing Azure PowerShell (typically associated with Windows environments) for enabling debug logging, with no equivalent method available for Azure CLI (commonly used on Linux/macOS). All example commands for enabling debug logging use PowerShell, and the ability to enable debug logging is explicitly unavailable in Azure CLI. There are no references to Linux-specific tools, shell environments, or cross-platform alternatives for the debug logging setup process.
Recommendations
  • Work with the Azure CLI team to add support for enabling debug logging via CLI, ensuring parity with PowerShell functionality.
  • If CLI support is not possible, provide clear guidance or workarounds for Linux/macOS users, such as using REST API calls or ARM template properties directly.
  • Include example commands or scripts for enabling debug logging using Bash, REST API, or other cross-platform tools.
  • Explicitly state platform limitations and suggest alternatives for non-Windows users.
  • Ensure that documentation sections do not assume PowerShell as the default or only method, and present CLI or cross-platform options first or equally.
GitHub Create Pull Request
Azure Resource Manager Resource not found errors ...re-resource-manager/troubleshooting/error-not-found.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and Azure CLI together, but mentioning PowerShell (a Windows-centric tool) first. There are no explicit Linux shell (bash) examples or instructions, and no mention of Linux-specific tools or patterns. The guidance for changing subscriptions references Set-AzContext (PowerShell) before az account set (CLI), and does not provide parity for Linux users in terms of shell usage or command syntax. All examples are platform-neutral (Bicep/JSON), but management task instructions and tool references favor Windows.
Recommendations
  • Provide explicit bash/Linux shell examples alongside PowerShell and Azure CLI, especially for common management tasks.
  • Alternate the order of tool references (e.g., mention Azure CLI before PowerShell, or present both equally).
  • Include notes or examples for Linux/macOS users, such as using bash or zsh, and clarify any platform-specific differences.
  • Ensure that troubleshooting steps and tool references do not assume a Windows environment, and mention cross-platform compatibility where relevant.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot common Azure deployment errors ...ce-manager/troubleshooting/common-deployment-errors.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page displays mild Windows bias. In several instances, Windows-specific tools (PowerShell) are mentioned before or instead of Linux equivalents (Azure CLI). For example, in the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are referenced, but PowerShell is listed second. In the 'AllocationFailed' error, troubleshooting links for both Linux and Windows are provided, but Windows is not prioritized. However, there are some cases where Windows-specific documentation (e.g., multiple NICs for Windows VMs) is listed before Linux equivalents. Overall, the page does not provide Linux shell or command examples, and references to Windows tools are more prominent than Linux alternatives.
Recommendations
  • Ensure that Linux tools (such as Azure CLI) are mentioned before or alongside Windows tools (PowerShell) in all relevant sections.
  • Provide Linux shell command examples where PowerShell examples are given, or at least reference both equally.
  • When linking to troubleshooting guides, alternate the order of Windows and Linux links or group them together to avoid perceived prioritization.
  • Add explicit references to Linux troubleshooting tools and patterns where applicable.
  • Review all error mitigation steps to ensure Linux users are equally supported and not required to use Windows-specific tools.
GitHub Create Pull Request
Azure Resource Manager Deployment quota exceeded ...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, and the CLI examples rely on Bash scripting, which is not natively available on Windows. There is no explicit mention of Windows or Linux, but the CLI examples assume a Bash environment, potentially excluding Windows users who do not have WSL or Git Bash installed. Conversely, the PowerShell examples are Windows-centric and do not mention cross-platform PowerShell Core usage. There is no explicit Linux example or guidance for users on Linux systems beyond the Bash scripting in the CLI section.
Recommendations
  • Explicitly state that the Azure CLI examples require a Bash environment and provide equivalent Windows Command Prompt or PowerShell Core examples for CLI usage.
  • Clarify that PowerShell examples can be run on PowerShell Core, which is cross-platform, and provide instructions for Linux/macOS users if applicable.
  • Add a note or section describing how to perform these actions on Linux systems, including installation prerequisites for Azure CLI and PowerShell Core.
  • Ensure that both Windows and Linux usage patterns are covered equally, and avoid assuming the user's operating system.
GitHub Create Pull Request
Azure Resource Manager SKU not available errors ...rce-manager/troubleshooting/error-sku-not-available.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal or greater prominence compared to Azure CLI, and Windows/PowerShell tools are mentioned first in the error description and troubleshooting sections. The REST example uses a Windows-style file path ('.\sku-list.json'), and there is no explicit mention of Linux-specific shell usage or file path conventions. No Linux shell scripting examples (e.g., Bash, zsh) are provided, and the PowerShell tab includes a lengthy script, whereas the CLI tab only covers basic commands.
Recommendations
  • Add Linux/Bash shell scripting examples for filtering and processing Azure CLI output, matching the complexity of the PowerShell script.
  • Ensure file path examples in REST/CLI sections use cross-platform notation or provide both Windows and Linux variants (e.g., '.\sku-list.json' and './sku-list.json').
  • In error descriptions and command references, mention Azure CLI before PowerShell, or present both equally.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide usage notes for common Linux shells.
  • Where advanced PowerShell scripting is shown, offer equivalent Bash or Python examples for Linux users.
GitHub Create Pull Request
Azure Resource Manager Overview of deployment troubleshooting for Bicep files and ARM templates ...les/azure-resource-manager/troubleshooting/overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell before Azure CLI when discussing error investigation, and by providing PowerShell command examples without equivalent Linux shell (bash) examples. There is no discussion of platform-specific considerations, nor are Linux or macOS environments referenced in troubleshooting workflows or tool usage. The use of Visual Studio Code is platform-neutral, but the command-line troubleshooting guidance leans toward Windows tools and patterns.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side, or mention Azure CLI first to balance platform representation.
  • Explicitly state that all tools (VS Code, CLI, PowerShell) are cross-platform and provide guidance for Linux/macOS users.
  • Include bash shell examples for troubleshooting commands, especially for error investigation and deployment operations.
  • Reference Linux/macOS environments in troubleshooting sections, and clarify any platform-specific differences in tool usage or error output.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot Bicep file deployments ...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks, but PowerShell is a Windows-centric tool and is presented as an equal alternative to the cross-platform Azure CLI. There are no explicit Linux shell (bash/zsh) examples, nor are Linux-specific patterns or tools (such as shell scripting, environment variables, or package managers) mentioned. The prerequisites mention Visual Studio Code and PowerShell, which are available on Linux, but the overall example set and tool references lean toward Windows users.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and provide any necessary shell-specific guidance (e.g., line continuation differences, environment variable usage).
  • Add bash/zsh shell script examples for deployment and cleanup steps, showing how Linux users can automate these tasks.
  • Clarify that PowerShell is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
  • Include troubleshooting steps or tips specific to Linux environments (e.g., file permissions, path differences).
  • Ensure that screenshots and instructions do not assume Windows-only environments (e.g., avoid referencing Windows file paths or UI elements unless cross-platform).
GitHub Create Pull Request
Azure Resource Manager Troubleshoot ARM template JSON deployments ...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, referencing Windows-centric tools (Visual Studio Code, Azure PowerShell), and listing PowerShell commands before or equally with CLI commands. There is no mention of Linux-specific editors, shell environments, or troubleshooting patterns, and PowerShell is treated as a default cross-platform tool despite its Windows origins.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and provide shell-specific notes (e.g., bash, zsh).
  • Include examples using bash scripts or Linux shell commands where appropriate, especially for file operations and troubleshooting.
  • Reference Linux-native editors (e.g., Vim, Nano, Emacs) in addition to Visual Studio Code, or clarify VS Code's cross-platform nature.
  • Clarify that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
  • Add troubleshooting steps or screenshots from Linux environments (e.g., terminal error output, file navigation).
  • Ensure that instructions for installing tools (Azure CLI, PowerShell) include Linux/macOS-specific guidance and links.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-loops.md ...icles/azure-resource-manager/bicep/quickstart-loops.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 Windows bias by consistently mentioning and providing examples for Azure PowerShell alongside Azure CLI, with PowerShell examples given equal prominence. The prerequisites emphasize Visual Studio Code (a cross-platform tool but often associated with Windows) and the Azure PowerShell module, which is primarily used on Windows. There are no explicit Linux-specific instructions, nor are Linux-native tools or shell patterns (e.g., Bash) referenced. The CLI examples are generic, but the presence and parity of PowerShell examples indicate a Windows-first approach.
Recommendations
  • Add explicit Bash shell examples for Linux/Mac users, using standard Bash variable syntax and command invocation.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Mention and link to Linux installation instructions for Bicep and Azure CLI.
  • Include notes or tabs for Linux-specific environment setup, such as using native editors (e.g., Vim, nano) and shell commands.
  • De-emphasize PowerShell as the default or primary scripting environment, or ensure Bash examples are presented first or with equal prominence.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/virtual-machines-move-limitations.md .../move-limitations/virtual-machines-move-limitations.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 both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some cases, PowerShell commands are mentioned first or exclusively for certain tasks (e.g., accepting Marketplace terms). There is a notable emphasis on PowerShell scripting, which is more commonly used on Windows. There are no Linux-specific shell examples (e.g., Bash), nor any mention of Linux-native tools or patterns. The documentation assumes parity between CLI and PowerShell, but does not address Linux user workflows explicitly.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate Linux usage, including variable assignment and command chaining.
  • Clarify that Azure CLI is cross-platform and highlight its usage on Linux/macOS, possibly with terminal screenshots or notes.
  • Where PowerShell is mentioned for scripting, offer equivalent Bash scripts for Linux users.
  • Avoid presenting PowerShell as the primary or default scripting tool; alternate the order of examples or group them under 'Windows' and 'Linux/macOS' headings.
  • Mention Linux-specific considerations, such as file system paths, environment variables, or authentication methods where relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-resource-group-and-subscription.md ...ger/management/move-resource-group-and-subscription.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. Azure PowerShell is given equal or greater prominence than Azure CLI, and PowerShell examples are provided throughout. The CLI examples are described as working in Bash or Azure PowerShell, but there are no explicit Linux shell script examples or references to Linux-specific environments. The PowerShell tab is consistently presented alongside or before CLI, and there is no mention of Linux tools, patterns, or considerations. There are no examples using native Linux tools or shell scripting beyond Azure CLI, and the Python examples use Azure CLI credentials, which may be less common in Linux environments.
Recommendations
  • Explicitly mention that Azure CLI examples work natively in Linux/macOS Bash shells, and provide sample Bash scripts for common operations.
  • Add notes or examples for Linux users, such as using environment variables, authentication methods, or shell scripting patterns specific to Linux.
  • Clarify that PowerShell is available cross-platform, but provide guidance for Linux users who may prefer Bash or other shells.
  • Consider adding a section or tab for Linux-specific considerations, troubleshooting, or best practices when moving resources.
  • Ensure that CLI examples do not assume PowerShell syntax (e.g., variable assignment), and provide pure Bash alternatives where relevant.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md ...nt/move-limitations/cloud-services-extended-support.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 Powershell Heavy
Summary
The documentation references Azure PowerShell before Azure CLI when listing move operation methods, which subtly prioritizes Windows-centric tooling. There are no explicit Linux-specific instructions or examples, and PowerShell is traditionally associated with Windows environments. No Linux shell (bash) or platform-specific guidance is provided.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning cross-platform tools, or present them together to avoid perceived prioritization.
  • Provide explicit examples for both Azure PowerShell and Azure CLI, including bash shell usage for Linux users.
  • Include a note clarifying that both Azure CLI and PowerShell are cross-platform, with links to installation guides for Linux and macOS.
  • Add troubleshooting or operational guidance relevant to Linux environments, such as file path formats or authentication nuances.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-app-service.md ...anager/management/relocation/relocation-app-service.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 exhibits Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Kudu and FTP credentials without clarifying Linux alternatives, and linking to PowerShell-based cloning guidance as the only explicit next step. While Azure CLI is mentioned as an option for some tasks, examples and step-by-step instructions are either Windows-centric or omit Linux-specific guidance. There are no explicit Linux shell (bash) examples, nor is parity established for Linux-based workflows or tools.
Recommendations
  • Add explicit Linux/Bash examples alongside PowerShell, especially for scripting and automation tasks.
  • Clarify that %HOME%\site is mapped to /home/site on Linux-based App Service plans.
  • Include references and links to Linux-native tools and workflows (e.g., SCP, rsync, Azure CLI in bash).
  • Ensure that next steps and deep links include both PowerShell and Azure CLI/Bash alternatives for cloning and migration.
  • Document any differences in Kudu, FTP, and file system access between Windows and Linux App Service plans.
  • Review all examples and instructions to ensure Linux users are equally supported and not required to adapt Windows-centric guidance.
GitHub Create Pull Request
← Previous Page 14 of 52 Next →