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 51-75 of 1281 flagged pages
Azure Resource Manager Create a parameters file for bicep deployment ...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI examples are provided (which are cross-platform), all PowerShell examples use Azure PowerShell cmdlets with Windows-style paths (e.g., C:\MyTemplates\...), and there is no mention of Linux-specific shell environments or examples using Bash or other Linux-native tools. Visual Studio Code is referenced as the primary editor, which is cross-platform, but no mention is made of Linux-specific editors or shell usage. Windows-style paths and PowerShell are presented before any Linux alternatives, and there are no explicit Linux/Bash examples for deployment commands.
Recommendations
  • Add Linux/Bash shell examples for deployment commands, using typical Linux path formats (e.g., /home/user/templates/storage.bicep).
  • Include notes or examples for using Azure CLI and Bicep CLI in Linux environments, such as running commands in Bash or zsh.
  • Provide guidance for Linux users on installing and using the Bicep CLI and Azure CLI, including any differences in environment variables or file paths.
  • Mention Linux-native editors (such as Vim or VS Code on Linux) where appropriate.
  • Ensure that all examples using file paths show both Windows and Linux formats, or use environment-agnostic paths.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit cross-platform instructions where relevant.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Create Bicep files with Visual Studio Code ...icep/quickstart-create-bicep-use-visual-studio-code.md
High 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 page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned before or alongside cross-platform alternatives, and PowerShell examples are given equal prominence to Azure CLI. The workflow assumes familiarity with right-click context menus and UI patterns typical of Windows environments. There are no explicit Linux-specific instructions or examples, and the documentation does not address platform differences in setup or usage.
Recommendations
  • Add explicit notes clarifying that Visual Studio Code and the Bicep extension are fully supported on Linux and macOS, not just Windows.
  • Include Linux/macOS-specific instructions for launching Visual Studio Code and interacting with files (e.g., using terminal commands rather than right-click context menus).
  • Provide CLI-only workflows for deployment and resource management, emphasizing that Azure CLI is cross-platform and can be used on Linux/macOS.
  • Mention alternative editors (e.g., Vim, VS Codium) that support Bicep via extensions, for users who do not use Visual Studio Code.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
  • Add screenshots or examples from Linux/macOS environments to visually reinforce cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Publish modules to private module registry ...ce-manager/bicep/quickstart-private-module-registry.md
High Priority View Details →
Scanned: 2026-01-12 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 by consistently providing Azure PowerShell examples alongside Azure CLI, referencing Windows-centric tools (Visual Studio, Visual Studio Code), and omitting explicit Linux/macOS shell examples (e.g., Bash). The instructions and screenshots focus on Visual Studio Code and Visual Studio, which are more commonly used on Windows, and do not mention Linux-native editors or shell usage. There is no guidance for Linux-specific environments, nor are there examples using Bash or other Linux command-line conventions.
Recommendations
  • Add explicit Bash shell examples for all Azure CLI commands, showing Linux/macOS syntax (e.g., export, $VAR, file paths with /).
  • Include instructions for using Bicep CLI and Azure CLI in Linux/macOS terminals, noting any differences in environment setup or file paths.
  • Mention Linux-native editors such as Vim, Emacs, or GNOME Text Editor as alternatives to Visual Studio Code.
  • Clarify that Visual Studio Code is cross-platform and provide installation guidance for Linux/macOS.
  • Add notes about running Azure CLI and Bicep CLI on Linux/macOS, including package manager installation commands (apt, yum, brew).
  • Ensure screenshots and examples do not assume a Windows environment (e.g., avoid Windows-style file paths, PowerShell variables).
GitHub Create Pull Request
Azure Resource Manager Create and deploy a deployment stack with Bicep ...e-manager/bicep/quickstart-create-deployment-stacks.md
High 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 provides both Azure CLI and Azure PowerShell examples for all operations, which is good for cross-platform parity. However, there is a subtle Windows bias: PowerShell is featured equally alongside CLI, despite being primarily a Windows-centric tool (even though PowerShell Core is cross-platform, most users associate it with Windows). Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of Linux-specific editors or shell environments. The documentation does not provide any Linux-specific guidance, troubleshooting, or notes, and PowerShell is listed as a prerequisite before Azure CLI, subtly prioritizing Windows tooling.
Recommendations
  • Explicitly mention that Azure CLI works natively on Linux/macOS and is recommended for those platforms.
  • Clarify that PowerShell Core is cross-platform, but most Linux/macOS users will prefer Azure CLI.
  • Add a note or section for Linux/macOS users, including common shell environments (bash/zsh) and editor alternatives (e.g., Vim, nano, etc.).
  • List Azure CLI before PowerShell in prerequisites to reflect its cross-platform nature.
  • Provide troubleshooting tips or links for Linux/macOS users (e.g., file permissions, path formats, installation guides).
GitHub Create Pull Request
Azure Resource Manager Create and deploy template specs in Bicep ...rticles/azure-resource-manager/bicep/template-specs.md
High 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 consistently presents Azure PowerShell examples before Azure CLI, and all command-line examples are given only for Azure PowerShell and Azure CLI, with no mention of Linux-specific shell usage or cross-platform nuances. There are no explicit Linux shell (bash/zsh) examples, nor any notes about platform differences. The documentation assumes familiarity with PowerShell, a Windows-centric tool, and does not acknowledge Linux or macOS environments, which may use different shell conventions or require different setup steps.
Recommendations
  • Add explicit bash/zsh examples for Linux/macOS users alongside PowerShell and Azure CLI examples.
  • Include notes about platform-specific differences, such as command syntax, file paths, and environment setup for Linux/macOS.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • Avoid always presenting PowerShell examples first; alternate or group examples by platform.
  • Mention prerequisites or troubleshooting steps for Linux/macOS environments, such as permissions or shell compatibility.
GitHub Create Pull Request
Azure Resource Manager Create a custom resource provider ...rce-manager/custom-providers/create-custom-provider.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations. However, in the PowerShell sections, it exclusively references and demonstrates the use of ARMClient, a Windows-centric executable, for REST operations. There is no mention of Linux-friendly alternatives (such as curl or httpie), nor guidance for running PowerShell or ARMClient on Linux/macOS. This creates a bias towards Windows users in the PowerShell workflow and REST tooling.
Recommendations
  • Add Linux/macOS instructions for REST operations in PowerShell, including how to install and use ARMClient (if possible) or suggest alternatives like curl or httpie.
  • Mention that PowerShell 7+ is cross-platform and provide explicit steps for Linux/macOS users, including installation and usage notes.
  • Where ARMClient is referenced, clarify its platform support and suggest alternatives for non-Windows environments.
  • Provide example REST calls using curl or httpie alongside ARMClient in PowerShell sections, or at least in a separate tab or note.
  • Review and update prerequisites to include Linux/macOS-specific guidance for environment setup and tooling.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, without providing Linux/macOS equivalents. The examples and instructions assume a Windows environment, and there is no mention of Linux-specific considerations or alternative paths. Additionally, the only editor recommended is Visual Studio Code, which, while cross-platform, is often associated with Windows development. There is also a reference to a known issue with PowerShell on Windows, but no guidance for Linux users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples in all CLI and PowerShell commands (e.g., C:\templates\main.bicep and ~/templates/main.bicep).
  • Explicitly state that the Azure CLI and Bicep tools are cross-platform, and provide any necessary Linux/macOS installation or usage notes.
  • Include notes or tabs for Bash shell usage, especially for variable assignment and command syntax differences.
  • When referencing issues or known problems, clarify if they are Windows-specific and provide Linux/macOS alternatives if available.
  • Consider recommending additional cross-platform editors or tools, or clarify that Visual Studio Code is available on all major operating systems.
GitHub Create Pull Request
Azure Resource Manager Create Azure Managed Application that deploys storage account encrypted with customer-managed key ...ed-applications/create-storage-customer-managed-key.md
High 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 demonstrates a moderate Windows bias. PowerShell is presented as the first and primary example for building Bicep files, with Azure CLI as a secondary option. There are no explicit Linux/macOS instructions or screenshots, and the workflow assumes familiarity with Windows-centric tools (e.g., Visual Studio Code, PowerShell). The portal instructions and screenshots do not address cross-platform differences, and there is no mention of Linux-specific considerations or alternative editors.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if needed.
  • Include screenshots or instructions for Linux/macOS environments where UI or tool behavior may differ.
  • Suggest alternative editors (e.g., VS Code is cross-platform, but mention alternatives like Vim, nano, etc. for Linux users).
  • Add a section or callout for Linux/macOS users, confirming parity and noting any differences in setup or workflow.
  • Avoid language that implies Windows is the default platform (e.g., avoid 'open PowerShell' as the only shell option).
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy an Azure Managed Application definition ...anager/managed-applications/deploy-bicep-definition.md
High 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 page demonstrates a mild Windows bias. PowerShell examples and terminology are consistently presented before Azure CLI (Linux-friendly) alternatives. Visual Studio Code is recommended as the editor, with no mention of Linux-specific editors or environments. The use of PowerShell-specific concepts (such as splatting) and variable syntax ($mrgname) is explained in detail, while Bash/CLI equivalents are less emphasized. There is no explicit mention of Linux or cross-platform considerations, and Windows-centric tools and patterns are referenced throughout.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first in some sections to avoid Windows-first bias.
  • Explicitly mention that all steps and tools are cross-platform, and clarify that Azure CLI and VS Code are available on Linux and macOS.
  • Include references to Linux-native editors (such as Vim, Nano) or terminal environments where appropriate.
  • Provide additional context or explanations for Bash/CLI commands, similar to the detail given for PowerShell (e.g., explain Bash variable syntax and command chaining).
  • Add a short section or note on running these steps in Linux/macOS environments, including any platform-specific considerations.
  • Avoid PowerShell-specific terminology (like 'splatting') without offering equivalent Bash explanations.
GitHub Create Pull Request
Azure Resource Manager Use APIs to create a private link for managing Azure resources ...ager/management/create-private-link-access-commands.md
High 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 provides both Azure CLI and PowerShell examples for resource creation and association, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There is no mention of Linux-specific tools or shell scripting, and PowerShell is referenced before REST in some sections. The 'Create private endpoint' section links to PowerShell documentation before CLI, and does not mention Linux shell or scripting alternatives. No Linux-specific context or troubleshooting is provided.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux users where appropriate.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS.
  • List CLI examples before PowerShell to avoid implicit Windows-first ordering.
  • Include links to Linux-specific documentation, troubleshooting, or environment setup.
  • Mention that PowerShell Core is available cross-platform, but clarify differences for Linux users.
  • Ensure parity in example depth and troubleshooting for both CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Deploy a service catalog managed application ...aged-applications/deploy-service-catalog-quickstart.md
High 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 page demonstrates a moderate Windows bias. PowerShell examples (which are Windows-centric) are consistently presented before Azure CLI (Bash/Linux) examples in each code section. Visual Studio Code is recommended as the editor, but the terminal instructions default to PowerShell first, with Bash mentioned as an alternative only for Azure CLI. There is frequent reference to PowerShell-specific syntax (e.g., backtick for line continuation, PowerShell escape characters) and Windows patterns, while Linux/Bash equivalents are explained second. No explicit Linux-only tools or workflows are discussed, and the overall structure prioritizes Windows/PowerShell users.
Recommendations
  • Alternate the order of examples so that Azure CLI/Bash instructions are presented first in some sections, or present both side-by-side.
  • Explicitly mention Linux and macOS compatibility in prerequisites and instructions, including guidance for using Bash terminals on those platforms.
  • Provide examples using native Linux editors (e.g., Vim, Nano) or clarify that Visual Studio Code is cross-platform.
  • Discuss differences in command syntax and environment setup between Windows and Linux/macOS more thoroughly.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, environment variables).
  • Where PowerShell-specific syntax is explained, provide parallel explanations for Bash/Linux syntax and escape characters.
GitHub Create Pull Request
Azure Resource Manager What are the resource providers for Azure services ...anager/management/azure-services-resource-providers.md
High 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 page exhibits mild Windows bias. In the 'Find resource provider' section, examples are given for Azure CLI (cross-platform), PowerShell (Windows-centric), and Python (cross-platform). However, PowerShell is presented before Python, and no explicit Linux shell (bash) example is provided. The registration section references the 'Windows Azure Service Management API', and several resource providers and services are named with 'Windows' (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP), but Linux equivalents are not highlighted or mentioned. There is no explicit Linux shell or scripting example, and Windows terminology appears before or instead of Linux alternatives.
Recommendations
  • Add a bash shell example for listing resources using Azure CLI, to explicitly show Linux usage.
  • When listing scripting examples, alternate the order or explicitly mention cross-platform compatibility.
  • In the registration section, clarify that the Azure Service Management API is not Windows-only, or mention Linux/Unix management APIs if applicable.
  • For resource providers with Windows-specific names, consider mentioning Linux equivalents or clarifying platform support.
  • Ensure that documentation does not imply Windows is the default or preferred platform, and highlight cross-platform capabilities where relevant.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources ...azure-resource-manager/management/deployment-models.md
High 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 Windows bias in several ways: PowerShell is the only command-line example given, with no Azure CLI or Linux shell equivalents. Windows tools and patterns (such as remote desktop and remote PowerShell traffic) are mentioned before Linux alternatives (SSH), and the example diagrams and links focus on Windows VMs. The migration guidance and next steps also prioritize PowerShell over cross-platform tools, and there is a lack of Linux-specific examples or parity in instructions.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell commands for all resource management operations.
  • Ensure that Linux-specific scenarios (such as SSH access, Linux VM deployment, and migration) are described with equal detail and prominence as Windows scenarios.
  • Add links to Linux VM reference architectures and migration guides, not just Windows VM resources.
  • When listing remote access methods, mention SSH for Linux before or alongside RDP/PowerShell for Windows.
  • Balance the use of Windows-centric terminology and tools with cross-platform alternatives throughout the documentation.
GitHub Create Pull Request
Azure Resource Manager Manage resource management private links ...ager/management/manage-private-link-access-commands.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI, but there are no examples for Linux-native shells (e.g., Bash scripts, curl, or other Linux command-line tools) beyond the generic Azure CLI and REST API calls. The login instructions reference Connect-AzAccount (PowerShell) before az login (CLI), and PowerShell is presented as a primary automation option, which may signal a Windows bias. There are no explicit Linux-specific examples or instructions.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux-native usage.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding a section or tab for Bash scripting to show parity with PowerShell automation.
  • Avoid presenting PowerShell as the default or primary automation tool; balance with Linux-native alternatives.
  • Mention installation and usage instructions for Azure CLI on Linux systems.
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using the REST API ...e-resource-manager/management/manage-resources-rest.md
High Priority View Details →
Scanned: 2026-01-12 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 provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell examples are given equal prominence and detail, despite PowerShell being primarily a Windows tool. There are references to Visual Studio Code and PowerShell for template deployment, but no mention of Linux-native editors or tools. The documentation does not provide explicit Linux shell (bash) examples beyond Azure CLI, nor does it reference Linux-specific patterns or alternatives to Windows-centric tools. The order of examples sometimes places PowerShell before or alongside CLI, which may suggest Windows-first thinking. There are no explicit Linux or macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add explicit bash shell examples for REST calls and authentication, especially for steps that use PowerShell.
  • Reference Linux-native editors (e.g., Vim, Nano) or cross-platform alternatives alongside Visual Studio Code.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Provide troubleshooting notes or tips for Linux/macOS users where file paths, environment variables, or authentication flows may differ.
  • Avoid referencing PowerShell as the default or primary method; present Azure CLI or bash examples first when possible.
  • Include links to Linux/macOS installation guides for Azure CLI and other required tools.
GitHub Create Pull Request
Azure Resource Manager Move guidance for Cloud Services (extended support) deployment model resources ...nt/move-limitations/cloud-services-extended-support.md
High 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 demonstrates Windows bias by listing Azure PowerShell before Azure CLI and REST API when describing move operations, implicitly prioritizing Windows-centric tools. There are no explicit Linux-specific examples or mentions of Linux tools or shell commands, and the guidance does not provide parity in example commands or workflows for Linux users.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform operations, or present them together to avoid implicit prioritization.
  • Provide explicit example commands for both Azure PowerShell and Azure CLI, highlighting usage on Linux/macOS terminals.
  • Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include links or references to Linux-specific documentation or troubleshooting guides where relevant.
  • Avoid using Windows-centric terminology or tools as defaults unless necessary, and clarify platform applicability.
GitHub Create Pull Request
Azure Resource Manager Configure data boundary ...re-resource-manager/management/manage-data-boundary.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI and REST API, referencing PowerShell-specific modules, and linking to PowerShell-centric role assignment documentation. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. Additionally, PowerShell examples and references often appear before or alongside CLI examples, rather than prioritizing cross-platform CLI tools.
Recommendations
  • Prioritize Azure CLI examples before PowerShell in all code tabs and sections, as CLI is natively cross-platform.
  • Add explicit notes clarifying that Azure CLI works on Linux, macOS, and Windows, while PowerShell may require additional setup on non-Windows platforms.
  • Where PowerShell is referenced, provide equivalent Bash or shell script examples for Linux users.
  • Review and update links to role assignment documentation to include CLI and REST API guides, not just PowerShell.
  • Consider removing or de-emphasizing PowerShell examples unless a specific Windows-only scenario is being described.
GitHub Create Pull Request
Azure Resource Manager Move Azure resources to a new resource group or subscription ...ger/management/move-resource-group-and-subscription.md
High Priority View Details →
Scanned: 2026-01-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 both Azure CLI and Azure PowerShell examples for most operations, but there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool. In several places, PowerShell is listed before CLI, and there are no explicit Linux/Bash-specific examples or notes about running commands in a Linux environment. The CLI examples are generic and do not clarify Linux-specific nuances (e.g., quoting, environment variables). There are also no references to Linux-native tools or shell scripting, and the PowerShell tab is sometimes shown before the CLI tab. This could make the documentation feel Windows-biased and less approachable for Linux users.
Recommendations
  • Ensure that Azure CLI examples are always presented before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
  • Add explicit notes or sections about running Azure CLI commands in Linux/Bash environments, including any differences in quoting, environment variables, or output parsing.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, but also provide Bash shell alternatives for scripting scenarios.
  • Include Linux/Bash-specific examples for common tasks, such as using environment variables, piping, and parsing output with jq.
  • Avoid using PowerShell syntax (e.g., $variable = ...) in CLI sections, as this can confuse Linux users who expect Bash syntax.
  • Where possible, mention Linux tools or patterns (e.g., using export for environment variables, using grep/jq for output processing) alongside Windows/PowerShell equivalents.
  • Add a short section or callout at the top clarifying that all CLI examples are cross-platform and tested on both Windows and Linux.
GitHub Create Pull Request
Azure Resource Manager Evaluate a cloud workload for relocation ...azure-resource-manager/management/relocate-evaluate.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by exclusively referencing Azure tools and workflows that are primarily accessed through the Azure portal or PowerShell, with no mention of Linux-specific tools, CLI workflows, or cross-platform scripting examples. The only explicit example for moving public IP configurations links to a PowerShell-based guide, and there are no Linux or Azure CLI equivalents provided. The documentation also omits any discussion of Linux-based automation, discovery, or scripting patterns, and does not mention open-source or cross-platform alternatives.
Recommendations
  • Provide Azure CLI examples alongside PowerShell, especially for tasks like moving public IP configurations, to ensure Linux users have parity.
  • Mention cross-platform automation and scripting options (such as Bash scripts, Ansible, or Terraform) when discussing updating scripts and infrastructure as code.
  • Include references to Linux-native tools or workflows for resource discovery and management, such as using Azure CLI on Linux, or open-source visualization tools.
  • Ensure that documentation links and examples are not exclusively PowerShell-based; always offer CLI or REST API alternatives.
  • Explicitly state that all tools and procedures can be performed on Linux as well as Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Handling special cases when moving virtual machines to resource group or subscription .../move-limitations/virtual-machines-move-limitations.md
High 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 provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally or slightly more heavily, and is referenced in several key steps (e.g., accepting Marketplace terms, recreating VMs) as the primary method. There is a subtle Windows bias in the use of PowerShell and Windows-centric terminology, with no explicit mention of Linux shell scripting or Linux-specific tools. The documentation does not provide bash or shell script examples, nor does it discuss Linux-specific patterns or considerations beyond referencing Azure Disk Encryption for Linux VMs.
Recommendations
  • Add bash/shell script examples alongside Azure CLI and PowerShell, especially for steps involving scripting or automation.
  • Explicitly mention that Azure CLI commands can be run natively on Linux/macOS, and provide guidance for Linux users where appropriate.
  • Where PowerShell is referenced as the primary method (e.g., accepting Marketplace terms), clarify that Azure CLI is cross-platform and provide equivalent CLI commands.
  • Include notes or sections highlighting any Linux-specific considerations, such as file system permissions, environment variables, or differences in command-line usage.
  • Review the order of examples to avoid always listing PowerShell first; alternate or lead with Azure CLI where possible, as it is more platform-neutral.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure App Services to another region ...anager/management/relocation/relocation-app-service.md
High Priority View Details →
Scanned: 2026-01-12 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 exhibits Windows bias in several ways: Windows-specific paths (e.g., %HOME%\site) are referenced without mention of Linux equivalents; Kudu and FTP credential management are described in a manner that assumes familiarity with Windows tooling; PowerShell is highlighted in the 'Next steps' section for app cloning, with no equivalent Azure CLI or Linux shell examples; and there is a general lack of Linux-specific guidance or examples throughout the document.
Recommendations
  • Include Linux-specific paths and environment variable references (e.g., $HOME/site for Linux).
  • Provide Azure CLI and Bash examples alongside PowerShell for all operations, especially in 'Next steps' and backup/restore procedures.
  • Clarify that Kudu and FTP management are cross-platform, and provide instructions for Linux users where relevant.
  • Explicitly mention that App Service supports both Windows and Linux, and highlight any differences in migration steps or tooling.
  • Ensure that all references to file systems, environment variables, and deployment tools are platform-neutral or have both Windows and Linux variants.
  • Add links to Linux-focused documentation or tutorials where available.
GitHub Create Pull Request
Azure Resource Manager Relocate your Azure Functions app to another Azure region ...-manager/management/relocation/relocation-functions.md
High Priority View Details →
Scanned: 2026-01-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 subtle Windows bias. When discussing scripting options for recreating infrastructure, 'Azure CLI/PowerShell scripts' are mentioned together, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI, and no explicit mention of Bash or Linux shell scripting. The use of Windows-style environment variables (e.g., '%HOME%\site') is present, with no Linux equivalent ($HOME/site) shown. There are no explicit Linux-specific examples or guidance, and the documentation does not provide parity for Linux users in terms of scripting or file path conventions.
Recommendations
  • Explicitly mention Bash/Linux shell scripting as an option alongside Azure CLI and PowerShell.
  • When referencing environment variables or file paths, provide both Windows ('%HOME%\site') and Linux ('$HOME/site') formats.
  • Include examples or notes for Linux container deployments and Linux-specific storage mounting patterns.
  • Ensure that CLI examples use cross-platform syntax and clarify any OS-specific differences.
  • Add guidance for Linux users where patterns or tools differ from Windows, such as authentication, file system access, or deployment methods.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Backup to another region ...rce-manager/management/relocation/relocation-backup.md
High 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 demonstrates a Windows bias in several ways: Windows-specific instructions and terminology (e.g., 'install the latest Windows updates') are presented before Linux equivalents, and Linux guidance is less detailed ('refer to distributor guidance'). Examples and scripts are given in Azure PowerShell format, with no mention of Bash or Linux CLI alternatives. The backup agent section references the MARS agent, which is Windows-only, with no mention of Linux backup solutions or agents. Screenshots and step-by-step instructions are focused on Windows environments.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions alongside Windows guidance, especially for certificate updates and VM preparation.
  • Include Bash/Azure CLI script examples for bulk VM protection and resource management, not just Azure PowerShell.
  • Clarify backup agent options for Linux on-premises resources, and reference Linux-compatible solutions where applicable.
  • Ensure that instructions for tasks like certificate management, firewall configuration, and backup agent installation are equally detailed for both Windows and Linux.
  • Add screenshots and walkthroughs for Linux environments where relevant.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.md
High Priority View Details →
Scanned: 2026-01-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 exhibits Windows bias by frequently providing PowerShell examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Linux/bash or cross-platform alternatives. PowerShell commands are mentioned before or instead of Azure CLI/bash examples, and some tasks (such as repository listing) use Windows-centric tools. There is a lack of explicit Linux/bash examples for several key steps, and the scripting guidance is inconsistent in platform parity.
Recommendations
  • Provide bash/Azure CLI examples alongside PowerShell commands for all tasks, especially for repository listing, image import, and AKS integration.
  • When introducing commands, present Azure CLI/bash examples first or in parallel with PowerShell, to avoid Windows-first ordering.
  • Clarify which commands are cross-platform and which are Windows-specific, and note any platform limitations.
  • Add explicit Linux/macOS instructions for tasks currently only described with PowerShell.
  • Ensure scripting examples (such as the import loop) are clearly marked as bash and provide PowerShell equivalents only as secondary options.
  • Review all tool references to ensure Linux tools (e.g., bash, Azure CLI) are given equal prominence to Windows tools.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Hubs to another region ...-manager/management/relocation/relocation-event-hub.md
High Priority View Details →
Scanned: 2026-01-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 demonstrates Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is given a dedicated tab for template modification, with explicit command examples (Get-AzLocation) and links to Azure PowerShell documentation, while no equivalent Bash, Azure CLI, or Linux shell examples are provided. The instructions for region code lookup reference PowerShell first and exclusively. There are no Linux-specific or cross-platform command-line examples for key steps such as template deployment or resource management. The Azure portal is referenced throughout, but when scripting is discussed, only PowerShell is shown.
Recommendations
  • Add Azure CLI examples and tabs alongside PowerShell for all command-line instructions, including region code lookup and template deployment.
  • Include Bash or shell script examples for Linux users where automation is discussed.
  • Reference Azure CLI documentation equally with PowerShell in all relevant sections.
  • Ensure that cross-platform tools and workflows are presented before or alongside Windows-specific ones, not after.
  • Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide parity in instructions.
GitHub Create Pull Request
← Previous Page 3 of 52 Next →