Azure Resource Manager

1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

492 issues found
Showing 226-250 of 492 flagged pages
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 (Linux-friendly) and Azure PowerShell (Windows-centric) examples for most tasks, but often presents PowerShell examples first or with more detail. The deployment and management instructions (e.g., deploying the Bicep file) are shown only with Azure PowerShell, with no Linux/macOS equivalent (such as Azure CLI or Bash). ARMClient usage is shown only with PowerShell syntax. There is a lack of parity in step-by-step deployment instructions for Linux/macOS users, and PowerShell is frequently referenced as the default scripting and management tool.
Recommendations
  • Add explicit Azure CLI or Bash examples for deploying Bicep files and managing deployment scripts, especially in sections currently showing only PowerShell commands.
  • Present CLI and PowerShell examples side-by-side or alternate which is shown first, to avoid implicit prioritization.
  • Clarify that both Azure CLI and PowerShell are supported on all platforms, and provide platform-agnostic instructions where possible.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI for deployment tasks.
  • Show ARMClient usage with CLI or REST examples, not just PowerShell.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot problems with Bicep installation ...re-resource-manager/bicep/installation-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and patterns. For example, the command prompt is mentioned rather than a Linux terminal, and the 'where bicep' command (Windows-only) is used to locate installations, with no mention of the Linux/macOS equivalent ('which bicep'). The PATH modification instructions reference Windows environment variables and locations (e.g., %USERPROFILE%\.Azure\bin) without providing Linux/macOS alternatives. No Linux/macOS-specific examples or instructions are given.
Recommendations
  • Include Linux/macOS equivalents for all commands, such as using 'which bicep' instead of 'where bicep'.
  • Provide instructions for modifying the PATH variable on Linux/macOS (e.g., editing ~/.bashrc or ~/.zshrc).
  • Mention the default installation locations for Azure CLI-managed Bicep on Linux/macOS.
  • Add screenshots or descriptions relevant to Linux/macOS environments where appropriate.
  • Ensure troubleshooting steps are platform-agnostic or clearly separated by OS.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Use MSBuild tasks to convert Bicep files and parameters to JSON ...les/azure-resource-manager/bicep/msbuild-bicep-file.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a notable Windows bias. Windows/PowerShell examples are shown first and exclusively in key sections, such as project creation, directory navigation, and cleanup. The use of PowerShell commands is pervasive, with no equivalent bash or Linux/macOS shell examples provided. Directory paths and project setup instructions consistently use Windows conventions (e.g., C:\msBuildDemo), and the Classic framework example is only relevant to Windows. While the documentation mentions cross-platform NuGet packages and provides some Linux/macOS references for the Bicep CLI, practical step-by-step instructions and code samples are almost entirely Windows-centric.
Recommendations
  • Provide Linux/macOS shell (bash/zsh) equivalents for all PowerShell commands, including directory creation, navigation, and cleanup.
  • Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) alongside Windows paths.
  • Include explicit instructions for using Visual Studio Code or terminal on Linux/macOS, not just Windows.
  • Add project file examples referencing Azure.Bicep.CommandLine.linux-x64 and Azure.Bicep.CommandLine.osx-x64, not just win-x64.
  • Where tabs are used for .NET versions, also provide tabs for OS-specific instructions (Windows, Linux, macOS).
  • Clarify which steps are OS-agnostic and which require adaptation, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid system topics to another region ...ment/relocation/relocation-event-grid-system-topics.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (web UI) for all steps, with no mention of CLI, PowerShell, or automation tools. While this avoids explicit Windows-only tools, the examples and screenshots are tailored to the Azure Portal, which is equally available on all platforms. However, there are no examples for Linux/macOS users who may prefer command-line automation (Azure CLI, ARM templates via CLI, or scripting). The documentation does not mention or show how to perform these tasks using Azure CLI, which is cross-platform, nor does it provide parity for users who avoid GUIs.
Recommendations
  • Add equivalent instructions using Azure CLI for exporting, modifying, and redeploying Resource Manager templates.
  • Include sample commands for deleting resource groups via Azure CLI.
  • Provide links to relevant Azure CLI documentation for ARM template deployment and resource management.
  • Clarify that all steps can be performed via CLI or PowerShell, and provide references or examples for those approaches.
GitHub Create Pull Request
Azure Resource Manager Bicep null-forgiving operator ...zure-resource-manager/bicep/operator-null-forgiving.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and Azure CLI for deploying Bicep files, but lists Azure PowerShell before Azure CLI and does not provide explicit Linux/macOS instructions or examples. The guidance assumes familiarity with Windows tools and workflows, and does not mention Linux-specific deployment methods or considerations.
Recommendations
  • List Azure CLI before Azure PowerShell, as CLI is cross-platform and preferred on Linux/macOS.
  • Explicitly state that Azure CLI works on Linux/macOS and provide example commands for those platforms.
  • Add a note or section for Linux/macOS users, including any relevant setup or usage differences.
  • Avoid implying that Visual Studio Code is the only editor; mention alternatives available on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Create a parameters file for bicep deployment ...ticles/azure-resource-manager/bicep/parameter-files.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for deploying Bicep files with parameters. However, the PowerShell examples use Windows-style file paths (e.g., C:\MyTemplates\...), and PowerShell is a Windows-centric tool, with no mention of Bash or Linux-native alternatives. The CLI examples are cross-platform, but PowerShell is presented as an equal deployment method without clarifying its limited use on Linux/macOS. Additionally, file path examples and tool references (Visual Studio Code, PowerShell) are Windows-first or Windows-only, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside PowerShell examples.
  • Use cross-platform file path examples (e.g., ./MyTemplates/storage.bicep) or clarify path differences for each OS.
  • Clarify that Azure PowerShell is available on Linux/macOS, but usage and installation may differ.
  • Mention Linux/macOS alternatives for Visual Studio Code, or reference other editors where applicable.
  • Ensure that CLI examples are shown before PowerShell, or at least clarify cross-platform applicability.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, without providing Linux/macOS equivalents. All command examples reference these Windows paths, and there is no mention of Linux/macOS file path syntax or usage. Additionally, the only editor mentioned is Visual Studio Code, which is cross-platform, but the documentation does not clarify file path differences or provide explicit Linux/macOS instructions. There is a note about a known issue with PowerShell, but no Linux-specific caveats or guidance.
Recommendations
  • Provide Linux/macOS file path examples (e.g., /home/user/templates/main.bicep) alongside Windows examples in all CLI and PowerShell commands.
  • Add a note or section explaining file path differences between Windows and Linux/macOS, and how to adapt commands accordingly.
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and clarify any OS-specific behaviors or issues.
  • Where possible, use environment variables or relative paths in examples to increase portability.
  • Include troubleshooting tips for Linux/macOS users if any commands behave differently.
GitHub Create Pull Request
Azure Resource Manager Publish modules to private module registry ...ce-manager/bicep/quickstart-private-module-registry.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides examples for Azure CLI and Azure PowerShell, but omits explicit Linux/macOS shell examples. PowerShell is a Windows-centric tool, and its usage is shown alongside Azure CLI throughout. Additionally, instructions for setting up the environment reference Visual Studio and Visual Studio Code, which are available cross-platform but are more commonly associated with Windows. No Bash or shell script examples are provided, and there is no mention of Linux-specific patterns or tools.
Recommendations
  • Add Bash (Linux/macOS) shell examples for all Azure CLI commands, showing usage with standard shell variable syntax (e.g., export, $VAR, etc.).
  • Clarify that Azure CLI commands work cross-platform and provide explicit instructions for Linux/macOS users (e.g., using bash, zsh, etc.).
  • Mention Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code and Visual Studio.
  • Include notes about installing Azure CLI and Bicep CLI on Linux/macOS, with links to relevant documentation.
  • Ensure that PowerShell is not presented as the default or only scripting option, and clarify its cross-platform availability.
GitHub Create Pull Request
Azure Resource Manager Create multiple resource instances in Bicep ...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment and cleanup instructions using Azure CLI and Azure PowerShell, but does not include explicit Linux/macOS shell examples (e.g., Bash). While Azure CLI is cross-platform, the examples use Windows-style variable assignment (resourceGroupName = "{...}") rather than Bash syntax (export or variable assignment with no spaces). PowerShell examples are given equal prominence, and Visual Studio Code is recommended (cross-platform), but there is no mention of Linux-specific setup or shell usage. The CLI examples could confuse Linux users due to syntax differences.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, using Linux/macOS variable assignment (e.g., resourceGroupName="..." or export resourceGroupName=...)
  • Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific syntax where relevant
  • Mention Linux/macOS prerequisites (e.g., installation of Azure CLI on Linux, using Bash or Zsh)
  • Consider providing a tabbed interface for Bash, PowerShell, and CMD where command syntax differs
  • Ensure that all instructions are clear for users on non-Windows platforms
GitHub Create Pull Request
Azure Resource Manager Create and deploy template specs in Bicep ...rticles/azure-resource-manager/bicep/template-specs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and references PowerShell scripts and usage patterns throughout. There is a notable emphasis on PowerShell as a deployment tool, and PowerShell-specific instructions are given for tasks such as creating, viewing, and deploying template specs. No Linux/macOS-specific shell examples (e.g., Bash) or platform-specific notes are provided, and the CLI examples are generic, not tailored to Linux/macOS environments.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is shown before PowerShell in some sections.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide platform-specific notes or tips where relevant (e.g., file paths, environment variables).
  • Include Bash or shell script examples for common tasks, especially for automation scenarios.
  • Clarify that PowerShell is available cross-platform, but highlight any differences or limitations on Linux/macOS.
  • Add troubleshooting or installation notes for Linux/macOS users where PowerShell is referenced.
  • Avoid language that implies PowerShell is the default or preferred tool unless justified by functionality.
GitHub Create Pull Request
Azure Resource Manager Create a custom resource provider ...rce-manager/custom-providers/create-custom-provider.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, maintaining parity in most areas. However, the PowerShell tab recommends and demonstrates the use of ARMClient, a Windows-centric tool (armclient.exe), without mentioning Linux/macOS alternatives or ARMClient's cross-platform capabilities. There are no examples using Linux-native tools like curl, httpie, or bash scripting for REST calls, and the documentation does not clarify whether ARMClient works on Linux/macOS. This creates friction for non-Windows users who prefer or require native tooling.
Recommendations
  • Explicitly state whether ARMClient is cross-platform, and provide installation instructions for Linux/macOS if supported.
  • Add Linux/macOS examples using curl or httpie for REST API calls, especially in sections where ARMClient is used.
  • Mention alternative tools for REST operations that are available on Linux/macOS.
  • Clarify that PowerShell Core (v7+) is cross-platform, and provide guidance for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Resource Manager Tutorial - custom actions & resources ...ns/tutorial-create-managed-app-with-custom-provider.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a detailed PowerShell script for packaging and uploading the managed application artifacts to Azure Storage, without offering an equivalent Bash/Azure CLI example for Linux/macOS users. The PowerShell script is presented before the Azure CLI deployment steps, and there is no mention of cross-platform alternatives for the packaging/upload process. This may create friction for users on non-Windows platforms.
Recommendations
  • Add a Bash/Azure CLI example for packaging and uploading the zip archive to Azure Storage, using az storage commands.
  • Clearly indicate that the PowerShell script is Windows-specific and provide guidance for Linux/macOS users.
  • Present cross-platform (CLI) examples before or alongside Windows/PowerShell examples to ensure parity.
  • Reference documentation for az storage blob upload and container creation for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Move Microsoft.Resources resources to new region ...manager/management/microsoft-resources-move-regions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by using Windows-style file paths (e.g., c:\export), presenting examples with Windows conventions first, and omitting Linux/macOS-specific guidance for file paths and usage. Both Azure PowerShell and Azure CLI examples use Windows paths, and there is no mention of Linux/macOS equivalents or considerations.
Recommendations
  • Provide examples using Linux/macOS file paths (e.g., /home/user/export) alongside Windows paths.
  • Explicitly mention that Azure CLI and PowerShell are cross-platform and provide OS-specific usage notes.
  • Add notes or examples for running commands on Linux/macOS, including differences in file system paths and shell usage.
  • Ensure links to deployment instructions include Linux/macOS guidance 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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are used exclusively in examples, with no Azure CLI or Bash equivalents shown alongside. References to remote desktop and remote PowerShell traffic for Windows VMs are given before mentioning SSH for Linux VMs. The migration section lists PowerShell before CLI, and the 'Next steps' link points only to PowerShell deployment instructions. There are no Linux/macOS-specific instructions or examples, and CLI/Bash usage is not demonstrated.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands, especially in code blocks and migration instructions.
  • Include links to both PowerShell and CLI documentation in 'Next steps' and migration sections.
  • Mention SSH connectivity for Linux VMs equally and before/alongside RDP/PowerShell for Windows VMs.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure diagrams and examples are not Windows-centric (e.g., reference both Windows and Linux VM architectures).
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation frequently mentions Windows-centric tools (Azure PowerShell) and lists them before cross-platform alternatives (Azure CLI, Azure portal). In several sections, PowerShell is referenced alongside the Azure portal and CLI, but there are no explicit Linux/macOS shell examples or guidance. The documentation assumes familiarity with Windows tooling and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS shell examples where PowerShell is mentioned, such as Bash commands for Azure CLI.
  • When listing tools, alternate the order or explicitly state cross-platform compatibility (e.g., 'Azure CLI (cross-platform), Azure PowerShell (Windows/macOS), Azure portal').
  • Include screenshots or instructions for Linux/macOS environments when referencing the Azure portal or CLI.
  • Add a section clarifying that Azure CLI is fully supported on Linux/macOS and provide installation links.
  • Avoid defaulting to PowerShell in examples unless necessary; prefer Azure CLI for cross-platform parity.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Automation to another region ...manager/management/relocation/relocation-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-specific instructions and references (such as using Export-AzAutomationRunbook) without mentioning or providing equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). Additionally, PowerShell is listed as a primary deployment method, and no Linux-native tools or workflows are described.
Recommendations
  • Include Azure CLI and/or Bash examples for exporting and importing runbooks, alongside PowerShell instructions.
  • Reference cross-platform tools (e.g., REST API, Terraform) for deployment and resource management.
  • Explicitly state which instructions are platform-agnostic and which are Windows-specific.
  • Reorder examples so that platform-neutral or Linux-compatible methods are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. Several key examples use PowerShell commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without providing equivalent Bash or Azure CLI alternatives. In some sections, PowerShell commands are mentioned before Azure CLI, and Windows-centric tooling is referenced more frequently. While Azure CLI examples are present, Linux/macOS users may encounter friction due to the lack of parity in command examples and scripting guidance.
Recommendations
  • Provide Bash/Azure CLI equivalents for all PowerShell commands, especially for repository listing, image import, and AKS integration.
  • Ensure that Azure CLI examples are shown first or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Add explicit notes or sections for Linux/macOS users, clarifying how to perform each step using cross-platform tools.
  • Review scripting examples to ensure they use platform-neutral syntax (e.g., Bash scripts, Azure CLI) wherever possible.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Hubs to another region ...-manager/management/relocation/relocation-event-hub.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. It provides explicit PowerShell examples and references to PowerShell commands (e.g., Get-AzLocation) without offering equivalent Azure CLI or bash examples, which are more common on Linux/macOS. The tabs for modifying templates are 'portal' and 'PowerShell', with no mention of Azure CLI or bash scripting. Windows tools and patterns (PowerShell) are referenced before any Linux-friendly alternatives, and there are no explicit Linux/macOS-specific instructions or examples.
Recommendations
  • Add Azure CLI examples for all steps currently shown with PowerShell, especially for obtaining region codes and deploying templates.
  • Include bash script snippets where relevant, particularly for template manipulation and deployment.
  • Present Azure CLI and PowerShell examples side-by-side, or use tabs for 'Azure CLI', 'PowerShell', and 'Portal' to ensure parity.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Reference cross-platform tools (e.g., az command) before or alongside Windows-specific tools.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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. Azure PowerShell is featured prominently and often presented alongside or before Azure CLI, with PowerShell-specific instructions and examples. The CLI examples mention Bash compatibility but also reference running them in Azure PowerShell consoles, which may confuse Linux users. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), and no mention of platform-specific considerations for Linux/macOS users. Windows tools and patterns (PowerShell, Azure PowerShell console) are referenced more frequently than Linux equivalents.
Recommendations
  • Add explicit Bash/zsh examples and clarify CLI usage in Linux/macOS terminals.
  • Present Azure CLI examples before PowerShell, or side-by-side, to emphasize cross-platform parity.
  • Avoid referring to 'Azure PowerShell console' when discussing CLI usage; clarify that Azure CLI works natively in Linux/macOS shells.
  • Include notes about platform compatibility for each tool, especially CLI and PowerShell.
  • Consider adding troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure App Services to another region ...anager/management/relocation/relocation-app-service.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 paths (e.g., %HOME%\site) and terminology are used throughout, and PowerShell is referenced as a primary automation tool. Examples and references to Windows-centric tools (such as Kudu, which is more familiar to Windows users) are present, while Linux/macOS equivalents or cross-platform CLI examples are missing or mentioned after Windows options. The 'Next steps' section highlights PowerShell for app cloning, with no mention of Azure CLI or other cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell examples for all automation steps.
  • Use platform-neutral environment variables and paths, or provide both Windows and Linux/macOS syntax (e.g., $HOME/site for Linux).
  • Reference cross-platform tools and workflows (e.g., Azure CLI, REST API) equally or before Windows-specific tools.
  • Include explicit instructions or links for Linux/macOS users, especially for scripting and automation tasks.
  • Ensure that all referenced tools (such as Kudu) are described in a way that is accessible to users on all platforms.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Backup to another region ...rce-manager/management/relocation/relocation-backup.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 mild Windows bias. Windows terminology and update instructions are presented before Linux equivalents, and scripting examples reference Azure PowerShell without showing CLI or Bash alternatives. The guidance for certificate updates and troubleshooting errors is Windows-centric, with Linux instructions relegated to generic 'refer to distributor guidance'. There are no explicit Linux command examples or screenshots, and on-premises backup instructions focus on Microsoft tools (MARS agent), which are Windows-only.
Recommendations
  • Provide explicit Linux/macOS examples for scripting and automation, such as Azure CLI or Bash equivalents alongside PowerShell.
  • Include step-by-step instructions for updating certificates and CRLs on Linux, referencing common distributions (Ubuntu, RHEL, etc.).
  • Add screenshots and walkthroughs for Linux environments where applicable.
  • Mention and link to cross-platform backup agents or alternatives for on-premises Linux servers.
  • Ensure troubleshooting sections include Linux-specific error messages and solutions.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed guidance for relocating Azure Firewall, but all command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS workflows. The PowerShell examples are presented as the only scripting option, and references to creating firewall policies and migrations also link to PowerShell-based guides. There are no Linux/macOS-specific instructions or parity examples, and the portal instructions are platform-neutral but the scripting guidance is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include Bash shell instructions for template manipulation and deployment, especially for users on Linux/macOS.
  • Reference documentation for both PowerShell and Azure CLI when linking to migration or policy creation guides.
  • Explicitly state that the steps can be performed on Linux/macOS using Azure CLI, and provide links to installation/setup guides for those platforms.
  • Consider reordering examples so that cross-platform options (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure NSG to another region ...anagement/relocation/relocation-virtual-network-nsg.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for relocating an Azure NSG using the Azure Portal and PowerShell. All command-line examples use PowerShell cmdlets, which are native to Windows and not available by default on Linux/macOS. There are no CLI (az) or Bash examples, nor any mention of Linux/macOS-specific workflows. Additionally, file editing instructions reference Notepad, a Windows tool, without alternatives for other platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell steps, as Azure CLI is cross-platform and available on Linux/macOS.
  • Include Bash shell commands for file manipulation and editing, or reference cross-platform editors (e.g., nano, vim, VS Code) instead of Notepad.
  • Explicitly state that PowerShell Core is available on Linux/macOS, or provide guidance for installing it, if PowerShell must be used.
  • Ensure that all instructions and screenshots (if any) are platform-neutral or provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager CI/CD with Azure Pipelines and templates ...e-manager/templates/add-template-to-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It relies heavily on PowerShell scripts for ARM template deployment and references Windows-centric tools and patterns (e.g., AzureFileCopy, PowerShell scripts, Windows VM images). Linux/macOS alternatives (such as Bash, AzCopy CLI, or cross-platform scripting) are not mentioned, and examples use Windows VM images and Windows paths. There are no Linux/macOS-specific instructions or parity examples, making it harder for non-Windows users to follow or adapt the guidance.
Recommendations
  • Provide equivalent Bash or cross-platform script examples for ARM template deployment.
  • Include instructions and YAML samples using Linux VM images (e.g., 'ubuntu-latest') for all tasks, not just PowerShell.
  • Mention and demonstrate use of AzCopy CLI directly, which is cross-platform, instead of only AzureFileCopy (which is Windows-centric).
  • Clarify which tasks and scripts are cross-platform and which are Windows-only; suggest alternatives for Linux/macOS users.
  • Show Linux/macOS file path conventions in examples alongside Windows paths.
  • Add a section or notes on adapting the pipeline for Linux/macOS agents.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Key Vault to another region ...-manager/management/relocation/relocation-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed step-by-step instructions for Azure Portal and Azure PowerShell, but omits equivalent Azure CLI examples, which are more commonly used on Linux/macOS. PowerShell is featured prominently, and instructions for PowerShell appear before any mention of CLI. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer CLI/bash workflows.
Recommendations
  • Add Azure CLI examples for all major steps (exporting, modifying, and deploying templates) alongside PowerShell and Portal instructions.
  • Ensure CLI instructions are presented with equal prominence and detail as PowerShell, ideally in parallel tabbed sections.
  • Where region codes are discussed, show how to obtain them using Azure CLI (e.g., 'az account list-locations').
  • Explicitly note that PowerShell commands can be run on Linux/macOS, but recommend CLI for those platforms.
  • Review all sections for references to Windows-specific tools or workflows and provide Linux/macOS alternatives.
GitHub Create Pull Request
← Previous Page 10 of 20 Next →