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 176-200 of 1281 flagged pages
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-11 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 shown for interacting with Azure resources, and references to remote desktop and remote PowerShell traffic for Windows VMs are given before mentioning SSH for Linux VMs. The migration guidance and next steps link to PowerShell-based deployment instructions, with Azure CLI only mentioned as an alternative in a list, not in examples. There are no explicit Linux or cross-platform command-line examples, and Windows terminology/tools are prioritized throughout.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all command-line instructions, especially in code blocks.
  • Explicitly mention Linux and macOS compatibility in relevant sections, including remote management and deployment.
  • Ensure references to SSH and Linux VM management are given equal prominence to Windows/PowerShell examples.
  • Link to both PowerShell and Azure CLI deployment guides in 'Next steps', and clarify platform support.
  • Include screenshots or diagrams that are platform-neutral or show both Windows and Linux scenarios.
  • Review terminology to avoid Windows-centric phrasing (e.g., 'remote desktop and remote PowerShell traffic for Windows-based virtual machines and Secure Shell (SSH) traffic for Linux-based virtual machines' could be reworded to present both options equally).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently provides both Azure CLI and PowerShell examples for all operations, but PowerShell is a Windows-centric tool and is featured as a primary example alongside CLI. There is no mention of Linux-specific shells (e.g., Bash), nor are there any Linux-native command patterns or troubleshooting notes. The login instructions reference Connect-AzAccount (PowerShell) before az login (CLI), and the ms.custom metadata highlights Azure PowerShell tracking. No Linux-specific tools or usage notes are present.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, showing Linux terminal conventions.
  • Include notes on using Azure CLI in Linux environments, such as installation and authentication differences.
  • Clarify that Azure CLI is cross-platform and highlight its parity with PowerShell.
  • Avoid presenting PowerShell as an equal default to CLI; consider making CLI the primary example, with PowerShell as an alternative.
  • Add troubleshooting tips or environment setup instructions for Linux users where relevant.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but there is a notable bias toward Windows/PowerShell usage. PowerShell is given equal or sometimes more detailed coverage than Bash/Linux equivalents, and in some cases, PowerShell syntax is shown without clarifying that it is Windows-specific. There are no explicit Bash or Linux shell examples, and the CLI examples do not demonstrate Linux-specific patterns or considerations. The PowerShell section is detailed and assumes familiarity, while Linux/Bash users are left to infer usage from generic CLI commands. Additionally, the documentation refers to 'Azure PowerShell console' as an option for running CLI commands, which may confuse Linux users.
Recommendations
  • Explicitly provide Bash/Linux shell examples for all Azure CLI commands, including variable assignment and command chaining.
  • Clarify in each code block whether the example is for Windows (PowerShell) or Linux/macOS (Bash), especially where syntax differs.
  • Avoid presenting PowerShell examples before or with more detail than Bash/Linux equivalents; strive for parity in depth and clarity.
  • Add notes or sections for Linux/macOS users, highlighting any differences in environment setup, authentication, or command usage.
  • Where possible, include screenshots or terminal output from both Windows and Linux environments to illustrate cross-platform usage.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI and REST API, but there is no mention of Linux-specific shell usage (e.g., bash), nor are there any references to Linux tools or scripting patterns. The term 'PowerShell' is used without clarifying cross-platform support, and links to PowerShell documentation may imply a Windows-centric approach. Additionally, the Azure portal is referenced, which is platform-agnostic but often associated with Windows environments. No explicit Linux examples or shell-specific notes are present.
Recommendations
  • Explicitly state that Azure CLI and PowerShell are cross-platform, and clarify usage on Linux/macOS.
  • Add bash/zsh examples for Azure CLI commands, showing usage in Linux environments (e.g., environment variable syntax, quoting).
  • Include notes or links to installing and using Azure CLI and PowerShell on Linux/macOS.
  • Avoid implying that PowerShell is Windows-only; mention PowerShell Core and its availability on Linux.
  • Where possible, provide troubleshooting steps or examples relevant to Linux users (e.g., credential refresh, environment setup).
GitHub Create Pull Request
Azure Resource Manager Move Microsoft.Resources resources to new region ...manager/management/microsoft-resources-move-regions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses Windows-style file paths (e.g., c:\export), and all examples for Azure CLI and PowerShell use Windows conventions. There are no Linux/macOS-specific examples, and the documentation does not mention Linux equivalents for file paths or shell usage. The export and deployment instructions assume a Windows environment, which may confuse or hinder Linux users.
Recommendations
  • Provide Linux/macOS examples alongside Windows ones, especially for file paths (e.g., use /home/user/export or ./export).
  • Mention that Azure CLI and PowerShell are cross-platform and show how commands can be run in Bash or other shells.
  • Use environment-agnostic placeholders for file paths (e.g., <output-folder>) and clarify with examples for both Windows and Linux.
  • Include notes about differences in shell syntax (backticks vs. backslashes, quoting, etc.) where relevant.
  • Ensure links to deployment instructions include both PowerShell and Azure CLI guides for all platforms.
GitHub Create Pull Request
Azure Resource Manager Move guidance for classic deployment model resources ...ent/move-limitations/classic-model-move-limitations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as a primary tool for moving resources and lists it before Azure CLI and REST API. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tooling or command-line patterns. The guidance assumes familiarity with Windows-centric tools and does not provide parity for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell examples.
  • Mention Linux and macOS compatibility for Azure CLI and REST API operations.
  • Ensure that instructions do not assume the use of PowerShell or Windows-only tools.
  • Add a section or note highlighting cross-platform support and usage patterns.
  • List Azure CLI before or alongside PowerShell to avoid Windows-first impression.
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-11 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 referencing Windows-centric tools and patterns, such as PowerShell and Azure portal features, without mentioning equivalent Linux or cross-platform alternatives. Examples and guidance are provided for Windows environments (e.g., moving Azure Public IP configuration via PowerShell), but there are no Linux CLI or automation examples. The documentation assumes users are operating in a Windows-centric context and does not offer parity for Linux users.
Recommendations
  • Include Linux CLI (az CLI) examples alongside or before PowerShell examples for operations such as moving Azure Public IP configurations.
  • Mention cross-platform tools and automation options (e.g., Terraform, Ansible) for resource discovery and migration.
  • Provide guidance for Linux users on how to access and use Azure visualization and management tools from non-Windows environments.
  • Ensure documentation references both Windows and Linux approaches when discussing scripting, automation, and resource management.
  • Add explicit notes or sections for Linux users to clarify any differences in process or tooling.
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-11 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 demonstrates a Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Kudu (which is more familiar to Windows users), and providing links and examples that prioritize or exclusively mention Azure PowerShell and Windows-centric tools. Linux equivalents (such as Bash, Linux file paths, or Linux deployment patterns) are not mentioned, and there are no Linux-specific examples or references to Linux tooling (e.g., Azure CLI, Bash scripts) in the main flow. The 'Next steps' section specifically highlights PowerShell for app cloning, with no mention of CLI or cross-platform alternatives.
Recommendations
  • Add Linux-specific examples and references, such as Bash scripts and Azure CLI commands, alongside or before PowerShell examples.
  • Use platform-neutral terminology for file paths (e.g., $HOME/site for Linux, %HOME%\site for Windows) and clarify differences where relevant.
  • Include links to documentation for both Azure PowerShell and Azure CLI for all operations, especially in 'Next steps' and procedural sections.
  • Mention Linux deployment patterns (e.g., zip deploy via Bash, use of Linux containers) and tools where relevant.
  • Ensure that all instructions and tips are applicable to both Windows and Linux environments, or clearly indicate platform-specific steps.
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-11 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 areas: Windows-specific instructions and tools (such as Azure PowerShell and MARS agent) are mentioned or exemplified first or exclusively, with Linux alternatives only briefly referenced or omitted. Certificate update instructions are detailed for Windows but vague for Linux. On-premises backup focuses on Microsoft-centric tooling, and scripting examples use Azure PowerShell without CLI or Linux shell equivalents.
Recommendations
  • Provide explicit Linux examples alongside Windows instructions, especially for certificate management and VM preparation.
  • Include Azure CLI and Bash script examples wherever Azure PowerShell is used.
  • Clarify Linux-specific steps for agent installation, backup configuration, and troubleshooting.
  • Mention Linux-native backup agents/tools where applicable for on-premises workloads.
  • Ensure screenshots and walkthroughs are available for both Windows and Linux environments.
  • Structure instructions so that Windows and Linux guidance are presented in parallel, not with Windows first.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently lists Windows-centric tools (Azure PowerShell, Azure portal) before cross-platform or Linux-friendly options (Azure CLI). In several places, PowerShell is mentioned alongside the portal and CLI, but always in a prominent or first position, suggesting a Windows-first approach. There are no explicit Linux-only examples or references to Linux-specific workflows, and the documentation does not provide parity in example commands or screenshots for Linux environments.
Recommendations
  • Alternate the order of tool mentions so that Azure CLI is listed before or alongside Azure PowerShell and the Azure portal.
  • Provide explicit example commands for both Azure CLI and Azure PowerShell in all relevant sections.
  • Include screenshots or references to Linux terminal environments where appropriate.
  • Add a note clarifying that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific guidance if available.
  • Where possible, highlight cross-platform tools (like Azure CLI) as the primary method, with PowerShell as an alternative.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Automation to another region ...manager/management/relocation/relocation-automation.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by providing only PowerShell-based examples and instructions for exporting and importing runbooks, referencing Azure PowerShell modules, and omitting equivalent Linux/CLI examples. Windows-centric tools and workflows are mentioned exclusively or before any cross-platform alternatives, making it less accessible for Linux users.
Recommendations
  • Add Azure CLI examples for exporting and importing runbooks, alongside PowerShell instructions.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) equally or before Windows-specific tools.
  • Include explicit instructions for Linux users, such as command-line steps for template export/import.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and provide alternatives where possible.
  • Ensure diagrams and workflow descriptions do not implicitly assume a Windows environment.
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-11 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 demonstrates Windows bias in several ways: PowerShell commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) are presented without Bash or Linux equivalents, and Windows/PowerShell tools are referenced before or instead of cross-platform alternatives. Some command examples use Azure CLI (cross-platform), but PowerShell commands are often mentioned first or exclusively, and there is no explicit mention or example for Linux shell users where parity is possible.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for registry and AKS operations.
  • When listing commands, present Azure CLI (cross-platform) examples first, followed by PowerShell alternatives.
  • Explicitly mention that Azure CLI commands work on Windows, macOS, and Linux, and provide sample scripts for both Bash and PowerShell where scripting is involved.
  • Avoid referencing Windows-specific tools or patterns (such as .zip extraction instructions) without also providing Linux/macOS alternatives.
  • Ensure that all automation and scripting steps have parity for Linux users, including file handling and environment setup.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid custom topics to another region ...ment/relocation/relocation-event-grid-custom-topics.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively uses the Azure portal (a graphical tool most commonly accessed via Windows) for all instructions and screenshots. There are no examples or guidance for using cross-platform command-line tools such as Azure CLI, PowerShell (cross-platform), or REST APIs. The workflow assumes GUI usage, which is more typical for Windows users, and does not mention or prioritize Linux-friendly alternatives.
Recommendations
  • Add step-by-step instructions for relocating Event Grid custom topics using Azure CLI, which is available on Linux, macOS, and Windows.
  • Include examples using Azure PowerShell, noting its cross-platform capabilities.
  • Provide REST API sample calls for exporting, modifying, and redeploying resources.
  • Clearly indicate that the Azure portal is accessible from any OS, but offer parity for users who prefer command-line or automation workflows.
  • Add a section comparing portal, CLI, and API approaches, with links to relevant documentation for each.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line operations, with no mention of Azure CLI, Bash, or Linux-native tooling. All scripting and automation instructions are given in PowerShell, and references to migration steps also point to PowerShell-based guides. There is no parity for Linux users, as no Bash or cross-platform CLI examples are provided. The structure and order of examples also place PowerShell before any alternative, reinforcing the bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, ensuring parity for Linux and macOS users.
  • Include Bash script samples for template export, modification, and deployment steps.
  • Reference cross-platform tools and documentation (e.g., Azure CLI, REST API) in addition to PowerShell.
  • Reorder examples or provide tabs for both PowerShell and Azure CLI/Bash, ensuring neither platform is prioritized.
  • Update migration guides to include instructions for both Windows and Linux environments.
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-11 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 Azure portal and PowerShell instructions, referencing PowerShell-specific commands (Get-AzLocation), and omitting explicit Linux or cross-platform CLI examples for key steps such as region code discovery and template deployment. The Azure CLI is mentioned only in passing as a manual configuration option, with no step-by-step instructions or examples provided. There are no bash, Linux shell, or cross-platform CLI walkthroughs for the main workflow.
Recommendations
  • Add explicit Azure CLI examples for all steps currently shown only for PowerShell, including region code discovery and template deployment.
  • Include Linux/bash command snippets where relevant, especially for users working outside Windows environments.
  • Ensure that CLI instructions are presented alongside or before PowerShell instructions to avoid Windows-first ordering.
  • Clarify that all steps can be performed on Linux, macOS, and Windows, and provide platform-agnostic guidance where possible.
  • Reference cross-platform tools and patterns (e.g., az CLI, REST API) equally or before Windows-specific tools.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Azure PowerShell alongside Azure CLI as deployment options, and omitting explicit Linux or Bash examples. Windows terminology and tools are mentioned first or exclusively, while Linux equivalents or considerations are only briefly referenced or not detailed.
Recommendations
  • Provide explicit Linux/Bash examples alongside Windows/PowerShell examples, especially for deployment and scripting tasks.
  • Mention Linux file system paths (e.g., $HOME/site) in addition to Windows paths when discussing persisted local storage.
  • Clarify cross-platform differences in deployment tooling, such as Azure CLI usage on Linux/macOS and PowerShell on Windows.
  • Include guidance for Linux container scenarios, such as Docker Compose or Kubernetes, where relevant.
  • Ensure that instructions and terminology are platform-neutral or give equal prominence to both Windows and Linux approaches.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure HDInsight clusters to another region ...-manager/management/relocation/relocation-hdinsight.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell methods and examples alongside or before Azure CLI, and by referencing deployment from VS Code (a common Windows IDE) and Azure Cloud Shell without explicit mention of Linux-native workflows or tools. There are no Linux-specific command-line examples (e.g., Bash scripts), and no mention of Linux package managers or shell environments. The documentation does not provide parity for users who may prefer or require Linux-native approaches.
Recommendations
  • Add explicit Bash and Linux shell command examples for template export and deployment steps.
  • Include references to Linux-native tools and environments, such as using Bash in Azure Cloud Shell or local Linux terminals.
  • Ensure Azure CLI examples are given equal prominence and order as PowerShell examples, or consider listing CLI first as it is cross-platform.
  • Mention Linux package managers or scripting approaches where relevant (e.g., using curl, jq, etc. for automation).
  • Clarify that all steps can be performed from Linux, macOS, or Windows, and provide guidance for each platform where differences exist.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Key Vault to another region ...-manager/management/relocation/relocation-key-vault.md
High Priority View Details →
Scanned: 2026-01-11 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 and PowerShell environments. All command-line examples are provided exclusively using Azure PowerShell, with no Azure CLI (cross-platform) or Bash/Linux shell examples. PowerShell instructions are given equal prominence to the Azure Portal, but Linux-native tooling and workflows are not mentioned. This may disadvantage users on Linux or macOS, who typically use Azure CLI or Bash scripts.
Recommendations
  • Add Azure CLI examples for all PowerShell command sequences, including exporting, modifying, and deploying templates.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide Bash script snippets where appropriate.
  • Ensure that cross-platform tools (Azure CLI, REST API) are referenced before or alongside PowerShell, not after.
  • Include notes or tabs for Linux/macOS workflows, such as using Bash, zsh, or other common shells.
  • Review all instructions to ensure parity between Windows and Linux environments, especially for automation and scripting tasks.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure NSG to another region ...anagement/relocation/relocation-virtual-network-nsg.md
High Priority View Details →
Scanned: 2026-01-11 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 provides detailed instructions for relocating an Azure NSG using either the Azure Portal or PowerShell. All command-line examples use PowerShell cmdlets, which are native to Windows environments. There are no examples using Azure CLI, Bash, or other Linux-native tools. The use of 'notepad' as the editor and the absence of Linux or cross-platform alternatives further reinforce the Windows-centric approach. The documentation does not mention or provide parity for Linux users, nor does it suggest equivalent workflows using Linux tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • When referencing file editing, suggest cross-platform editors (e.g., 'code', 'vim', 'nano', 'gedit') in addition to 'notepad'.
  • Include Bash shell commands for tasks such as file manipulation and resource deployment.
  • Explicitly state that the instructions apply to both Windows and Linux, and provide guidance for Linux users where workflows differ.
  • Consider reordering examples so that cross-platform (Azure CLI) instructions are presented before or alongside PowerShell to avoid implicit Windows-first bias.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Storage Account to another region ...er/management/relocation/relocation-storage-account.md
High Priority View Details →
Scanned: 2026-01-11 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 and PowerShell environments. All command-line examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI or Bash/Shell alternatives commonly used on Linux and macOS. The structure consistently presents PowerShell instructions before or instead of cross-platform options. There are no explicit Linux or macOS-specific instructions, nor are there examples using native Linux tools or shell scripting. This may hinder accessibility for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including template export, modification, deployment, and resource deletion.
  • Include Bash/Shell script snippets where appropriate, especially for AzCopy usage and automation.
  • Explicitly mention that AzCopy is cross-platform and provide installation and usage instructions for Linux/macOS.
  • Where PowerShell commands are shown, provide equivalent Azure CLI commands in a separate tab or section.
  • Review all instructions for platform-specific terminology and ensure parity in guidance for Linux and macOS users.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Network to another region ...er/management/relocation/relocation-virtual-network.md
High Priority View Details →
Scanned: 2026-01-11 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 Virtual Network using the Azure Portal and Azure PowerShell, but omits equivalent examples for Linux users, such as Azure CLI or Bash scripts. The PowerShell examples are extensive and reference Windows-specific tools (e.g., Notepad), while no Linux-native workflows or commands are mentioned. This creates a bias toward Windows users and administrators, making it less accessible for those on Linux or macOS.
Recommendations
  • Add step-by-step instructions using Azure CLI for all major operations (export, modify, deploy, clean up).
  • Replace or supplement references to Notepad with cross-platform editors (e.g., 'edit with your preferred text editor').
  • Ensure all PowerShell examples have equivalent Azure CLI or Bash script examples, presented in parallel tabs.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI and provide links to relevant documentation.
  • Review and update any references to Windows-specific tools or workflows to be platform-neutral.
GitHub Create Pull Request
Azure Resource Manager Use tags to organize your Azure resources and management hierarchy ...les/azure-resource-manager/management/tag-resources.md
High Priority View Details →
Scanned: 2026-01-11 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 by referencing Azure PowerShell and REST API as primary tools for tag operations, mentioning Azure PowerShell before Azure CLI in access descriptions, and omitting explicit Linux shell or Bash examples. The CLI (which is cross-platform) is only referenced in limitations and 'Next steps', while PowerShell is highlighted for tag operations. There are no direct Linux or Bash command examples, and Windows-centric tools/patterns (PowerShell) are prioritized in explanations.
Recommendations
  • Ensure Azure CLI (cross-platform) is mentioned alongside or before Azure PowerShell when describing tag operations and access.
  • Provide explicit Bash/Linux shell examples for common tag operations, especially in sections discussing access and limitations.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and link to platform-specific installation guides.
  • Avoid language that implies PowerShell is the default or preferred tool; present CLI and PowerShell as equal options.
  • Add a section or examples for managing tags using Bash scripts or Linux-native tools where appropriate.
GitHub Create Pull Request
Azure Resource Manager Understand how Azure Resource Manager throttles requests ...ce-manager/management/request-limits-and-throttling.md
High Priority View Details →
Scanned: 2026-01-11 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 and references for retrieving throttling headers and debugging, with PowerShell shown before Azure CLI. While Azure CLI is cross-platform, there are no explicit Linux shell (bash/curl) examples, nor is there mention of Linux-specific patterns or tools. The PowerShell focus and ordering may suggest a Windows-centric bias, and the lack of Linux-native command examples could hinder parity for Linux users.
Recommendations
  • Add Linux shell (bash/curl) examples for retrieving headers from Azure Resource Manager REST API responses.
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform usage.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide troubleshooting tips for Linux environments.
  • Include sample scripts using common Linux tools (e.g., curl, jq) to parse throttling headers.
  • Balance the documentation by referencing both Windows and Linux approaches for common tasks, especially in code and command-line examples.
GitHub Create Pull Request
Azure Resource Manager Tag support for Azure resources ...icles/azure-resource-manager/management/tag-support.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is largely a reference table listing Azure resource types and their tag support, which is generally platform-neutral. However, in the few places where command-line tooling is mentioned, Windows-centric tools (PowerShell) are referenced first or exclusively, such as 'Set-AzVm -Generalized' before 'az vm generalize', and references to PATCH operations are explained in terms of Azure CLI commands without explicit Linux parity. There is also a lack of Linux-specific examples or explicit mention of Linux tooling, and Windows terminology (e.g., 'Winfields') appears in resource names.
Recommendations
  • When mentioning command-line tools, always provide both PowerShell (Windows) and Bash/Azure CLI (Linux/macOS) examples side-by-side.
  • Where Windows-specific terminology or tools are referenced, clarify Linux/macOS equivalents or note cross-platform compatibility.
  • Audit resource type names and documentation for unnecessary Windows-centric naming (e.g., 'Winfields') and provide context or alternatives if possible.
  • Add explicit notes or examples for Linux users where platform-specific behaviors may differ, especially in command syntax or resource management.
  • Ensure that documentation for PATCH operations and other resource updates includes instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Migrating to TLS 1.2 for Azure Resource Manager ...icles/azure-resource-manager/management/tls-support.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias by prioritizing Windows operating systems and tools in its guidance and examples. Windows versions are mentioned first and exclusively in the 'Quick tips' section, with no equivalent information for Linux or macOS. The recommended tools (Fiddler, PowerShell, WinHTTP) are Windows-centric, and all code/configuration examples reference .NET Framework and Visual Studio, which are primarily Windows technologies. There are no Linux-specific instructions, examples, or tool recommendations for checking or configuring TLS versions.
Recommendations
  • Add equivalent guidance for Linux and macOS systems, such as how to check and configure TLS versions on those platforms.
  • Include examples using common Linux tools (e.g., OpenSSL, curl, nmap) to verify TLS support.
  • Mention how to update TLS settings in popular Linux distributions and frameworks (e.g., Python, Java, Node.js on Linux).
  • Provide parity in quick tips, listing which Linux distributions and versions have TLS 1.2 enabled by default.
  • Recommend cross-platform tools (e.g., Wireshark, OpenSSL) alongside Windows-specific ones.
  • Add troubleshooting steps for TLS 1.2 compatibility on Linux and macOS clients.
GitHub Create Pull Request
← Previous Page 8 of 52 Next →