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 151-175 of 492 flagged pages
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-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 the main deployment examples use cross-platform Azure CLI, all PowerShell examples use Windows-centric paths (e.g., C:\MyTemplates\...) and exclusively reference Azure PowerShell, which is primarily used on Windows. Visual Studio Code is referenced as the editor, which is cross-platform, but screenshots and prompts may implicitly assume Windows. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), and Windows-style file paths are shown first or exclusively in PowerShell sections.
Recommendations
  • Add Linux/macOS shell examples (e.g., Bash) for deployment commands, especially for file paths and CLI usage.
  • In PowerShell sections, include notes or examples for PowerShell Core on Linux/macOS, using POSIX-style paths (e.g., /home/user/templates/storage.bicep).
  • Where file paths are shown, provide both Windows (C:\...) and Linux/macOS (/home/...) variants.
  • Clarify that Azure CLI and Visual Studio Code are cross-platform, and provide screenshots or instructions relevant to Linux/macOS users.
  • Mention that Azure PowerShell is available on Linux/macOS via PowerShell Core, and provide installation links or guidance.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on Visual Studio, a Windows-centric IDE, and does not provide Linux/macOS alternatives for Bicep file authoring. While deployment instructions include both Azure CLI and PowerShell, the authoring workflow is exclusively described using Visual Studio, with only a brief mention of Visual Studio Code as an alternative (without details). There are no Linux/macOS-specific instructions or screenshots, and the prerequisites and steps assume a Windows environment.
Recommendations
  • Provide detailed instructions and screenshots for creating Bicep files using Visual Studio Code, which is cross-platform.
  • Clearly indicate platform compatibility for each tool and step.
  • Add a dedicated section for Linux/macOS users, including installation steps for the Bicep extension in VS Code and any relevant CLI commands.
  • Ensure parity in examples and screenshots for both Windows and Linux/macOS environments.
  • Consider reordering or balancing the prominence of Windows and cross-platform tools in the documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:\templates\main.bicep) in all command examples, even in Azure CLI sections, and does not provide Linux/macOS path equivalents. This can cause confusion or friction for non-Windows users. There are no explicit Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment for file management and command usage.
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).
  • Add a note clarifying that file paths should be adapted to the user's operating system.
  • Explicitly mention that Azure CLI works cross-platform and show examples for Bash (Linux/macOS) and PowerShell (Windows).
  • Where relevant, include instructions for running commands in Bash shells (e.g., export variables, use $HOME, etc.).
  • Review references to external tutorials (e.g., role assignment) to ensure Linux/macOS parity.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples exclusively for Azure CLI and Azure PowerShell, with PowerShell examples present throughout. There are no explicit Linux/macOS shell (e.g., Bash) examples, nor are there instructions for using native Linux tools or patterns. Visual Studio Code is recommended, but Visual Studio (Windows-only) is also mentioned. The order of examples often presents Azure CLI first, which is cross-platform, but PowerShell is Windows-centric and its inclusion without Bash alternatives creates friction for Linux/macOS users.
Recommendations
  • Add Bash shell examples alongside Azure CLI commands to demonstrate usage in native Linux/macOS environments.
  • Clarify that Azure CLI commands work on all platforms and provide platform-specific notes where relevant.
  • Remove or de-emphasize Visual Studio (Windows-only) in favor of cross-platform editors like Visual Studio Code.
  • Where PowerShell is used, provide equivalent Bash or shell script examples for Linux/macOS users.
  • Explicitly mention platform compatibility in prerequisites and tool installation sections.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides 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 = "value") rather than Bash syntax (resourceGroupName="value"). PowerShell examples are given equal prominence, and Visual Studio Code is recommended, which is cross-platform. However, there is a subtle Windows-first bias in the variable assignment style and the lack of explicit Bash/Linux shell examples.
Recommendations
  • Add explicit Bash examples for CLI commands, using Bash variable assignment syntax (e.g., resourceGroupName="value") and export statements if needed.
  • Clarify that Azure CLI commands work on Linux/macOS and provide platform-specific notes where relevant.
  • Consider listing Bash/Linux CLI examples before PowerShell, or at least side-by-side, to reinforce parity.
  • Mention alternative editors (e.g., Vim, nano) for users who may not use Visual Studio Code.
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-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, which is good for cross-platform parity. However, in the PowerShell sections, it recommends and uses ARMClient (armclient.exe), a Windows-centric tool, without mentioning Linux/macOS alternatives or clarifying ARMClient's cross-platform support. There are no examples using common Linux tools (e.g., curl, httpie) for REST operations, nor is there guidance for users who prefer Bash or native Linux/macOS shells. This creates friction for non-Windows users, especially those who do not use PowerShell.
Recommendations
  • Explicitly state whether ARMClient works on Linux/macOS, or provide installation instructions for those platforms.
  • Offer REST examples using curl or httpie for Linux/macOS users alongside Azure CLI and PowerShell.
  • Add a Bash shell tab or section for users who prefer Bash scripting.
  • Clarify that PowerShell Core (v7+) is cross-platform, but also provide non-PowerShell alternatives for REST operations.
  • Mention that Azure CLI works on all platforms and is recommended for Linux/macOS users.
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-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 a full PowerShell script for packaging and uploading the managed application artifacts to Azure Storage, but does not offer an equivalent Bash or cross-platform CLI example. The PowerShell script is presented first and in detail, while the Azure CLI instructions are only given for later deployment steps. There is no guidance for Linux/macOS users on how to upload the zip package, which is a critical step in the workflow.
Recommendations
  • Add a Bash/Azure CLI example for uploading the zip package to Azure Storage, including container creation and blob upload.
  • Clearly indicate which steps are platform-specific and provide alternatives for Linux/macOS users.
  • Consider presenting CLI examples before or alongside PowerShell scripts to emphasize cross-platform support.
  • Add notes or links to documentation on using Azure CLI or REST API for storage operations on non-Windows platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by primarily featuring PowerShell commands and examples, referencing Windows-based virtual machines before Linux-based ones, and omitting equivalent Linux/macOS CLI or Bash examples in key sections. The migration instructions and next steps also prioritize PowerShell, with CLI guidance mentioned only after PowerShell and not integrated into examples. This creates friction for Linux/macOS users who may prefer Bash, Azure CLI, or other non-Windows tools.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands, especially in sections demonstrating resource queries and migrations.
  • Reference Linux-based virtual machines equally and provide examples for SSH connectivity and Linux management tasks.
  • Ensure links and next steps include both PowerShell and CLI/Bash documentation, and avoid presenting Windows tools or workflows first unless contextually necessary.
  • Add explicit notes or tables comparing command-line options for Windows, Linux, and 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-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 consistently uses Windows-style paths (e.g., c:\export) in both Azure PowerShell and Azure CLI examples, and all examples use Windows-centric tooling and conventions. No Linux/macOS equivalents (such as /home/user/export or /tmp/export) are provided, and the CLI examples do not adjust for cross-platform path differences. The export and deployment instructions reference PowerShell and Windows file system conventions exclusively, which may confuse or hinder Linux/macOS users.
Recommendations
  • Provide Linux/macOS path examples (e.g., /home/user/export) alongside Windows paths in all CLI and PowerShell commands.
  • Explicitly state that Azure CLI and PowerShell are cross-platform, and show how commands would look on Linux/macOS (including path syntax and shell usage).
  • Add notes or callouts about differences in file system paths and shell conventions between Windows and Linux/macOS.
  • Ensure links to deployment instructions include both PowerShell and Bash/CLI options.
  • Consider reordering examples so that cross-platform CLI commands appear before PowerShell/Windows-specific ones.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only CLI tool mentioned for exporting/importing runbooks, and no Linux/macOS equivalents (such as Azure CLI or REST API) are provided. The deployment instructions reference PowerShell before other options, and there is no guidance for users on non-Windows platforms for key steps.
Recommendations
  • Add Azure CLI examples for exporting/importing runbooks and deploying templates.
  • Include REST API methods for runbook management and template deployment.
  • Explicitly mention cross-platform tools and provide step-by-step instructions for Linux/macOS users.
  • Reorder instructions to present platform-neutral or cross-platform methods first, followed by platform-specific options.
  • Clarify which steps are platform-agnostic and which require Windows-specific 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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions Azure PowerShell before Azure CLI and does not provide explicit Linux/macOS-specific guidance or examples. The ordering and emphasis on PowerShell may suggest a Windows-first approach, and there are no Linux/macOS terminal examples or clarifications.
Recommendations
  • Provide explicit Azure CLI examples for moving resources, including command syntax usable on Linux/macOS.
  • Reorder tool mentions to present Azure CLI before or alongside Azure PowerShell.
  • Add notes clarifying cross-platform compatibility and any OS-specific considerations.
  • Include screenshots or step-by-step instructions for Linux/macOS users where applicable.
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-12 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. Azure PowerShell is featured prominently and often presented alongside or before Azure CLI, with detailed PowerShell examples. While Azure CLI is included and noted to work in Bash, there are no explicit Linux/macOS shell examples (e.g., bash, zsh, or other Linux-native scripting), nor is there guidance for Linux-specific environments. The PowerShell examples are Windows-centric, and the CLI examples use variable assignment syntax that is not portable to Linux shells. There is no mention of Linux-specific tools, nor troubleshooting for Linux/macOS users.
Recommendations
  • Add explicit bash/zsh examples for Azure CLI commands, using Linux-native variable assignment and syntax.
  • Clarify that Azure CLI commands work cross-platform and provide examples for Linux/macOS terminals.
  • Note differences in environment setup, authentication, and file paths for Linux/macOS users where relevant.
  • Reduce the prominence of PowerShell by presenting CLI examples first, or equally.
  • Include troubleshooting tips for Linux/macOS users (e.g., permissions, environment variables).
GitHub Create Pull Request
Azure Resource Manager Evaluate a cloud workload for relocation ...azure-resource-manager/management/relocate-evaluate.md
Medium 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 a Windows bias primarily by referencing Windows-centric tools and examples, such as PowerShell for moving Azure Public IP configurations, without mentioning Linux/macOS equivalents. The only explicit example for exporting public IP configuration links to a PowerShell-based process, and there are no CLI/bash alternatives or cross-platform guidance. Additionally, Azure portal and tool instructions do not clarify cross-platform compatibility, and Windows-oriented terminology is used by default.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux/macOS.
  • Explicitly mention that Azure portal and most Azure tools are accessible from any OS, and clarify any OS-specific limitations.
  • Where PowerShell is referenced, add parallel instructions for Bash/CLI users.
  • Review all tool recommendations to ensure Linux/macOS users are not excluded or disadvantaged.
  • Add notes or links to documentation for Linux/macOS users where workflows differ.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a property ...es/azure-resource-manager/templates/copy-properties.md
Medium 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 Powershell Heavy
Summary
The documentation page exhibits Windows bias in several ways: the only example template linked is for Windows VMs, and the deployment guidance in 'Next steps' references Azure PowerShell, with no mention of Linux/macOS alternatives like Azure CLI or Bash. There are no explicit Linux/macOS examples or instructions, and Windows tools/patterns are mentioned before their cross-platform equivalents.
Recommendations
  • Include example templates for Linux VMs alongside Windows VM examples.
  • In 'Next steps', provide links to deployment instructions using Azure CLI and Bash, not just PowerShell.
  • When referencing supported tools/versions (e.g., for zero count), clarify that Azure CLI is cross-platform and provide parity in instructions.
  • Ensure that examples and sample links cover both Windows and Linux scenarios equally.
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-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 moderate Windows bias. Windows-specific tools, terminology, and examples (such as Azure PowerShell, Windows Update instructions, and screenshots of MARS agent registration) are presented without equivalent Linux/macOS examples. Windows instructions are often listed first, and Linux guidance is referenced generically (e.g., 'refer to distributor guidance') rather than providing concrete steps or commands. There are no explicit Linux/macOS CLI or agent configuration examples, and screenshots are Windows-centric.
Recommendations
  • Provide explicit Linux/macOS examples for backup agent configuration, certificate updates, and VM preparation steps.
  • Include Azure CLI and Bash script samples alongside PowerShell examples for bulk VM protection and resource management.
  • Add screenshots or walkthroughs for Linux-based agent registration and backup configuration.
  • Ensure instructions for certificate management and system preparation are detailed for Linux distributions, not just referenced.
  • Present Windows and Linux/macOS instructions in parallel sections, or clarify OS-specific steps where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a moderate Windows bias. Several command examples use Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without providing equivalent Azure CLI or bash examples, especially in critical steps like retrieving images and configuring AKS integration. The initial example for retrieving images uses PowerShell only, and PowerShell equivalents are mentioned before CLI in some places. While Azure CLI is used for deployment and import examples, Linux/macOS users may encounter friction due to missing bash/CLI alternatives for some steps.
Recommendations
  • Provide Azure CLI or bash equivalents for all PowerShell commands, especially for retrieving repository images and configuring AKS integration.
  • When listing commands, present Azure CLI/bash examples first or side-by-side with PowerShell to avoid Windows-first perception.
  • Explicitly mention cross-platform compatibility for all scripts and commands.
  • Add notes or links for Linux/macOS users where PowerShell is referenced, clarifying how to perform the same actions using CLI/bash.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid custom topics to another region ...ment/relocation/relocation-event-grid-custom-topics.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all steps, with screenshots and instructions tailored to a graphical interface. There are no CLI, PowerShell, or shell command examples provided, nor any mention of cross-platform tools like Azure CLI or ARM templates via command line. This creates a subtle Windows bias, as the portal experience is most commonly associated with Windows users, and Linux/macOS users often prefer or require command-line instructions for automation and accessibility.
Recommendations
  • Add equivalent instructions using Azure CLI (az commands) for exporting, editing, and deploying ARM templates.
  • Include PowerShell examples if relevant, but ensure Azure CLI is presented first or alongside PowerShell.
  • Provide guidance for performing these steps on Linux/macOS, such as using VS Code or command-line editors to modify JSON files.
  • Clarify that all steps can be performed on any OS via the portal, but highlight automation options for non-Windows users.
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-12 00:00
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 and examples, without mentioning or providing alternatives using cross-platform command-line tools like Azure CLI, PowerShell, or ARM templates via terminal. This approach implicitly favors Windows users, as the Azure Portal experience and screenshots are more closely aligned with Windows workflows. There are no Linux/macOS-specific instructions or examples, nor any mention of using CLI tools that are available on all platforms.
Recommendations
  • Add equivalent instructions for performing each step using Azure CLI commands, which are cross-platform and work on Linux/macOS/Windows.
  • Include examples of exporting, modifying, and deploying Resource Manager templates using CLI (az group export, az deployment group create, etc.).
  • Explicitly mention that all steps can be performed using CLI or PowerShell, and provide links to relevant documentation.
  • Add screenshots or terminal output examples for Linux/macOS users where appropriate.
  • Consider reordering sections to present CLI/automation options before or alongside portal-based instructions.
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-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 moderate Windows bias. Windows-specific paths (e.g., %HOME%\site) are referenced, and PowerShell is highlighted in the 'Next steps' section for app cloning. While Azure CLI is mentioned as an alternative for configuring service endpoints, examples and links for PowerShell are given equal or greater prominence. There are no explicit Linux/macOS shell examples, and Windows-centric terminology (such as Kudu and FTP credentials) is used without Linux equivalents or guidance.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash, Azure CLI) alongside or before PowerShell examples.
  • Reference Linux file paths and environment variables where appropriate, or clarify cross-platform differences.
  • Ensure that links to Azure CLI documentation are given equal prominence to PowerShell links.
  • Add guidance for Linux users regarding Kudu, FTP credentials, and other tooling that may differ from Windows.
  • Avoid using Windows-centric terminology exclusively; clarify when instructions apply to all platforms.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid domains to another region ...management/relocation/relocation-event-grid-domains.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions, with screenshots and step-by-step guidance. There are no examples or instructions for using cross-platform command-line tools such as Azure CLI, PowerShell, or REST API. This creates a bias toward users who prefer or require GUI-based workflows, which are more common on Windows, and omits parity for Linux/macOS users who often rely on CLI tools.
Recommendations
  • Add equivalent instructions for performing each step using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are given equal prominence.
  • Provide REST API example calls for advanced users and automation scenarios.
  • Clearly indicate that all steps can be performed on any OS using CLI tools, not just via the portal.
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-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. While it provides instructions for both the Azure portal and Azure PowerShell, it omits explicit examples for Linux/macOS users, such as Azure CLI commands or shell scripts. PowerShell is featured as the only command-line example, and Windows-centric tools (portal, PowerShell) are mentioned before any cross-platform alternatives. There are no instructions or examples for Linux-native workflows, and the guidance for obtaining region codes is PowerShell-specific.
Recommendations
  • Add Azure CLI examples alongside PowerShell, especially for tasks like obtaining region codes and deploying templates.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide equivalent command-line steps.
  • Reorder sections so that cross-platform tools (CLI) are presented before or alongside Windows-specific tools.
  • Include notes or tabs for Linux/macOS users, clarifying any platform-specific differences.
  • Where screenshots are used, consider including CLI output or Linux desktop screenshots for parity.
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-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 provides detailed instructions for Azure Firewall relocation using the Azure Portal and PowerShell, but omits equivalent CLI (az), Bash, or Linux/macOS shell examples. PowerShell is featured as the only command-line method, and links to migration guides also reference PowerShell. No cross-platform CLI alternatives are mentioned, and PowerShell is presented before any Linux-compatible options.
Recommendations
  • Add Azure CLI (az) examples for all steps currently shown with PowerShell, including template export, modification, and deployment.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS, but provide Bash/CLI syntax for parity.
  • Link to migration guides that include CLI and Bash instructions, not just PowerShell.
  • Reorder examples so that cross-platform methods (Azure CLI) are presented before or alongside PowerShell.
  • Clarify tool requirements for Linux/macOS users (e.g., installation of Azure CLI, PowerShell Core).
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Storage Account to another region ...er/management/relocation/relocation-storage-account.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed PowerShell examples for all automation steps, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The PowerShell method is presented alongside the Azure Portal, but no Azure CLI or Bash scripting alternatives are given. References to obtaining region codes and deploying templates are exclusively PowerShell-centric, creating friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all steps currently shown only in PowerShell, including exporting, modifying, and deploying Resource Manager templates.
  • Include Bash script snippets for common operations where appropriate.
  • Mention cross-platform tools and clarify that AzCopy and Azure CLI are available on Linux/macOS.
  • Present CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state platform compatibility for each tool and command.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, but omits equivalent examples for Linux/macOS users, such as Azure CLI or Bash scripts. PowerShell is featured as the only command-line option, and Windows-specific tools like Notepad are referenced for editing files. This creates friction for users on Linux or macOS, who may not have access to PowerShell or Notepad.
Recommendations
  • Add step-by-step instructions using Azure CLI for all command-line operations, including exporting, editing, and deploying ARM templates.
  • Replace references to Notepad with cross-platform editors (e.g., 'edit with your preferred text editor').
  • Where PowerShell is shown, provide Azure CLI equivalents side-by-side or in a separate tab.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant, or clarify platform requirements.
  • Ensure all resource management tasks (create, delete, verify) have CLI examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for exporting and deploying Azure Key Vault templates, but does not include equivalent Azure CLI or Bash examples. PowerShell is typically associated with Windows, and its usage is shown before any mention of cross-platform tools. The absence of Linux/macOS-specific instructions or CLI examples creates friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all steps currently shown only in PowerShell, including exporting and deploying templates.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure that CLI/Bash examples are presented alongside or before PowerShell examples to avoid Windows-first bias.
  • Include notes on how to perform template modifications and deployments from Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 7 of 20 Next →