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 401-425 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/create-private-link-access-commands.md ...ager/management/create-private-link-access-commands.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for key operations, but PowerShell (a Windows-centric tool) is given equal prominence and dedicated tabs. There is no mention of Linux-specific tools or shell patterns (e.g., Bash scripting), and PowerShell is referenced before REST in some sections. The guidance for logging in references Connect-AzAccount (PowerShell) and az login (CLI), but does not mention Linux authentication nuances or alternatives. The 'Add private endpoint' section links to PowerShell before CLI and does not mention Linux-specific workflows.
Recommendations
  • Add explicit Bash shell examples alongside Azure CLI, demonstrating usage in typical Linux environments.
  • Clarify that Azure CLI is cross-platform and provide sample commands in Bash syntax (with environment variable usage, piping, etc.).
  • Include notes or examples for Linux authentication (e.g., using service principals, environment variables) where appropriate.
  • Ensure that CLI examples are presented before PowerShell, or provide a Linux-first workflow where relevant.
  • Reference Linux-native tools or scripting patterns where possible, and avoid implying PowerShell is the default for all users.
  • In sections linking to further documentation, ensure Linux and CLI resources are listed before or alongside PowerShell/Windows resources.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md ...aged-applications/deploy-service-catalog-quickstart.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell examples are consistently presented before Azure CLI, and instructions for opening terminals reference PowerShell and Visual Studio Code, which are more commonly associated with Windows environments. The documentation also discusses PowerShell-specific syntax (e.g., backtick for line continuation and escaping quotes) in detail, while the Bash/Linux equivalents are covered less thoroughly. There is no mention of Linux-specific editors or terminal environments, and the overall flow assumes familiarity with Windows tools and patterns.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Explicitly mention Linux and macOS environments when discussing prerequisites and terminal usage (e.g., suggest using GNOME Terminal, Konsole, or Terminal.app alongside Visual Studio Code).
  • Provide equal detail for Bash/Linux syntax (e.g., line continuation, escaping) as is given for PowerShell.
  • Include notes or tips for users on Linux/macOS regarding installation and usage of Azure CLI and PowerShell.
  • Reference cross-platform editors (e.g., VS Code, Vim, Nano) and clarify that both Azure CLI and PowerShell are available on all major operating systems.
  • Ensure screenshots and instructions for the Azure portal do not assume a Windows look-and-feel.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/tutorial-create-managed-app-with-custom-provider.md ...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 detailed PowerShell scripts for packaging and uploading the application artifacts to Azure Storage, while omitting equivalent Linux/macOS shell (bash) examples. Windows tools and patterns (e.g., PowerShell cmdlets like New-AzStorageAccount, Set-AzStorageBlobContent) are presented first and exclusively, with no mention of cross-platform alternatives. The Azure CLI examples are present for deployment steps, but not for the artifact packaging/upload process, which is a critical part of the workflow. There are no bash or Linux-native instructions for users on non-Windows platforms.
Recommendations
  • Add bash/Azure CLI examples for packaging and uploading the application zip to Azure Storage, using az storage commands.
  • Present cross-platform instructions side-by-side or in tabs, ensuring Linux/macOS users have clear, tested guidance.
  • Explicitly mention that PowerShell scripts are Windows-specific and provide alternatives for Linux/macOS environments.
  • Avoid presenting Windows/PowerShell tooling first or exclusively; strive for parity in example coverage.
  • Review all code snippets and workflows for platform assumptions, and ensure Linux users can follow the tutorial without needing Windows tools.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/azure-services-resource-providers.md ...anager/management/azure-services-resource-providers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the 'Find resource provider' section, the PowerShell example is given immediately after the Azure CLI example, with no mention of Linux shell equivalents (such as Bash or scripting with shell tools). The PowerShell example is presented as a primary method, and the registration section references the 'Windows Azure Service Management API' without mentioning Linux or cross-platform alternatives. There is also a resource provider specifically for 'WindowsIoT' and 'Microsoft.WindowsDefenderATP', but no equivalent Linux-specific resource providers or examples. No Linux shell or scripting examples are provided, and Windows terminology (e.g., 'Windows Azure') is used in guidance.
Recommendations
  • Add Linux/Bash shell examples alongside PowerShell, especially for common tasks like listing resources.
  • Clarify that Azure CLI is cross-platform and works on both Windows and Linux, and provide explicit Linux usage notes if needed.
  • Avoid using Windows-specific terminology (e.g., 'Windows Azure Service Management API') without mentioning cross-platform or Linux alternatives.
  • If referencing Windows-specific resource providers (e.g., WindowsIoT), consider mentioning Linux equivalents or clarify platform support.
  • Ensure that examples and guidance are balanced between Windows and Linux, or explicitly state platform applicability.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/deployment-models.md ...azure-resource-manager/management/deployment-models.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only PowerShell command examples (no Azure CLI, Bash, or Linux-native examples), referencing Windows-based remote management (RDP and PowerShell) before mentioning Linux (SSH), and linking to deployment instructions that focus on PowerShell. Linux equivalents and cross-platform tools are either omitted or mentioned after Windows options.
Recommendations
  • Provide Azure CLI and Bash examples alongside or before PowerShell commands for all resource management operations.
  • Ensure that remote management instructions and endpoint descriptions mention SSH (for Linux) equally and not as an afterthought.
  • Include links to both PowerShell and CLI deployment guides in the 'Next steps' section.
  • When referencing documentation or templates, ensure parity in examples and guidance for both Windows and Linux virtual machines.
  • Review diagrams and architecture references to ensure they are not Windows-centric (e.g., avoid only referencing 'Run a Windows VM on Azure').
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-private-link-access-commands.md ...ager/management/manage-private-link-access-commands.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides command examples for Azure CLI, PowerShell, and REST API. PowerShell is a Windows-centric tool, and its examples are given equal prominence as Azure CLI, which is cross-platform. There is a slight Windows bias due to the inclusion of PowerShell examples and instructions (e.g., Connect-AzAccount), which are most commonly used on Windows. There are no Linux-specific shell examples (e.g., Bash), nor are Linux authentication patterns (such as using environment variables or managed identities) discussed. The documentation does not mention Linux-specific tools or patterns and does not clarify that Azure CLI is fully cross-platform, potentially leading to the perception that Windows tools are primary.
Recommendations
  • Add explicit Bash shell examples alongside Azure CLI commands to demonstrate Linux usage.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Mention Linux authentication alternatives (such as using environment variables, managed identities, or Azure CLI login methods) where relevant.
  • Consider reducing the prominence of PowerShell examples or providing them as secondary to CLI/Bash examples.
  • Add notes or sections for Linux users, including troubleshooting tips or environment setup instructions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-data-boundary.md ...re-resource-manager/management/manage-data-boundary.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, REST API, and Azure portal. However, PowerShell is featured prominently and referenced in links (e.g., 'Assign Azure roles' links to PowerShell docs), and PowerShell examples are given equal or greater prominence than CLI. There is a lack of explicit Linux shell (bash) examples, and no mention of Linux-specific tooling or patterns. REST API and Azure CLI are cross-platform, but PowerShell is a Windows-centric tool, and its inclusion without Linux shell equivalents suggests a Windows bias. Additionally, the documentation references PowerShell before CLI in some places and links to PowerShell documentation for further reading.
Recommendations
  • Add explicit bash/shell examples for Linux users, especially for role assignment and data boundary configuration.
  • Ensure Azure CLI is presented before PowerShell in example tabs and documentation links, as CLI is more cross-platform.
  • Include notes clarifying that Azure CLI commands work natively on Linux/macOS, while PowerShell may require installation and configuration.
  • Provide links to Azure CLI documentation in addition to or before PowerShell documentation.
  • Consider mentioning Linux-native tools or patterns where appropriate, and avoid assuming PowerShell is the default scripting environment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/microsoft-resources-move-regions.md ...manager/management/microsoft-resources-move-regions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates bias toward Windows environments by exclusively using Windows-style paths (e.g., c:\export), omitting Linux/macOS path examples, and referencing deployment steps that assume Windows tooling. Both Azure PowerShell and Azure CLI examples use Windows file paths, and there is no mention of Linux shell equivalents or cross-platform considerations. The export and deployment instructions do not address Linux-specific nuances, such as file system differences or alternative shell usage.
Recommendations
  • Include Linux/macOS path examples (e.g., /home/user/export) alongside Windows paths in all CLI and PowerShell commands.
  • Explicitly mention that Azure CLI and PowerShell are cross-platform, and provide shell-specific instructions or notes where behavior differs.
  • Add examples using Bash or other Linux shells, especially for file manipulation and command syntax.
  • Reference documentation for deploying templates using Linux/macOS, including links to relevant guides.
  • Avoid assuming the use of Windows tools or environments; clarify steps that are platform-agnostic or provide alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resources-rest.md ...e-resource-manager/management/manage-resources-rest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell examples are given equal prominence and detail as CLI, despite PowerShell being primarily a Windows tool. References to Visual Studio Code and PowerShell for template deployment further reinforce Windows-centric tooling. There are no explicit Linux shell (bash) or macOS-specific examples, and Windows tools/patterns (PowerShell, Visual Studio Code) are mentioned before or more frequently than Linux equivalents.
Recommendations
  • Add explicit bash examples for authentication and REST calls, showing usage on Linux/macOS.
  • Include references to cross-platform editors (e.g., VS Code, vim, nano) and clarify VS Code is available on Linux/macOS.
  • Provide guidance for Linux users on installing and using Azure CLI, and highlight that PowerShell Core is cross-platform if recommending it.
  • Ensure that CLI/bash examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention alternative Linux tools for HTTP requests (e.g., wget, httpie) in addition to curl.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocate-evaluate.md ...azure-resource-manager/management/relocate-evaluate.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-centric tools and patterns, such as PowerShell in the context of moving Azure Public IP configurations, and by omitting Linux-specific examples or alternatives. All command-line or automation references are either generic or implicitly Windows-focused, with no mention of Linux shell commands, Azure CLI, or cross-platform scripting. The visualization and automation tooling guidance is centered on Azure Portal and Windows-oriented tools, without highlighting Linux-compatible approaches.
Recommendations
  • Provide Linux-specific examples alongside PowerShell, such as Azure CLI or Bash scripts, especially for tasks like exporting and deploying public IP configurations.
  • Explicitly mention cross-platform tools and scripting options (e.g., Azure CLI, Bash, Python) when discussing automation and resource management.
  • Include references to Linux-native tools or patterns for discovery and documentation, such as using SSH, scp, or Linux-based monitoring solutions.
  • Ensure that any step-by-step instructions or code snippets are available for both Windows and Linux environments.
  • Clarify that Azure Portal and most Azure services are accessible from any OS, and highlight any OS-specific limitations or considerations.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-automation.md ...manager/management/relocation/relocation-automation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively referencing Azure PowerShell for exporting and importing runbooks, and by providing step-by-step instructions that assume use of the Azure portal (which is more commonly used on Windows). There are no examples or guidance for using Linux-native tools (such as Azure CLI or bash scripts), nor is there mention of cross-platform alternatives for key operations. The documentation also lists PowerShell before other deployment methods and omits Linux-specific considerations.
Recommendations
  • Add Azure CLI examples for exporting and importing runbooks, alongside PowerShell examples.
  • Include bash script samples for template deployment and resource management.
  • Explicitly mention that the Azure portal and Resource Manager templates are cross-platform, and provide links to Linux-compatible tooling.
  • Reorder instructions to present cross-platform methods (e.g., Azure CLI) before or alongside PowerShell.
  • Add a section discussing Linux-specific considerations for Automation relocation, such as authentication and file handling differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-backup.md ...rce-manager/management/relocation/relocation-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific instructions and tools (such as Azure PowerShell and MARS agent) are mentioned or exemplified, while Linux equivalents are either referenced generically or omitted. Windows update instructions are explicit, but Linux guidance is vague ('refer to distributor guidance'). PowerShell scripting is shown for bulk VM protection, but no Bash or Linux CLI examples are provided. The on-premises backup section focuses on Microsoft tools (MARS agent), which are Windows-centric, with no mention of Linux backup agents or procedures.
Recommendations
  • Provide explicit Linux examples alongside Windows instructions, such as Bash scripts or Azure CLI commands for bulk VM protection.
  • Include detailed steps for updating certificates and CRLs on common Linux distributions (e.g., Ubuntu, CentOS) rather than generic 'refer to distributor guidance'.
  • Mention and link to Linux-compatible backup agents or procedures for on-premises resources, such as Azure Backup Server for Linux or third-party solutions.
  • When listing prerequisites or configuration steps, ensure parity in detail and clarity for both Windows and Linux environments.
  • Where screenshots or UI instructions are given, clarify any differences for Linux users or provide alternative visuals if applicable.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-functions.md ...-manager/management/relocation/relocation-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Azure PowerShell and CLI together (with PowerShell listed first), and omitting explicit Linux shell or Bash examples. While Linux containers and explicit file share mounting are briefly mentioned, there are no concrete Linux-specific instructions, examples, or parity in tooling references. The documentation assumes familiarity with Windows conventions and tools, and does not provide equivalent Linux command-line or file system guidance.
Recommendations
  • Provide Linux/Bash examples alongside PowerShell and CLI instructions, or explicitly mention cross-platform command options.
  • Reference Linux file system paths (e.g., $HOME/site) and clarify differences in local storage handling between Windows and Linux hosting.
  • Include guidance for Linux users on mounting file shares and managing persisted storage, with links to relevant Linux documentation.
  • Ensure that deployment instructions and tooling references (CLI, templates, scripts) are presented in a platform-neutral order or with equal prominence.
  • Add explicit notes or sections for Linux-specific scenarios, such as running in Linux containers, using Bash scripts, and handling authentication or deployment differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-container-registry.md ...management/relocation/relocation-container-registry.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by frequently providing PowerShell examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Linux/bash alternatives, especially in the 'Prepare' and 'Import registry content' sections. Windows/PowerShell commands are often mentioned before or instead of cross-platform Azure CLI or bash scripts. There is a lack of explicit Linux or bash examples for several key operations, and Windows-centric tools are referenced without clear parity for Linux users.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI or bash command, and present them side-by-side or with clear platform labels.
  • Where scripting is required (e.g., importing images), include both bash and PowerShell script samples.
  • Avoid using Windows/PowerShell-specific cmdlets as the primary or sole example; prioritize cross-platform Azure CLI commands.
  • Explicitly mention platform applicability for each command or script, and ensure Linux users are not required to translate PowerShell syntax themselves.
  • Review all tool references (e.g., Azure Resource Mover, Export Template) to ensure instructions are clear for both Windows and Linux environments, including file handling and automation steps.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-firewall.md ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing only Azure PowerShell examples for command-line operations, with no mention or examples of Azure CLI (cross-platform) or Bash scripting. The use of PowerShell-specific commands and references to 'scripts' in the exported template further reinforce the Windows-centric approach. There is no guidance for Linux or macOS users, nor are alternative tools or workflows presented. The structure also presents PowerShell examples before any mention of cross-platform alternatives, which are absent.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including template export, modification, and deployment.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide Bash script samples where appropriate.
  • Clarify that the exported templates and scripts can be used with both PowerShell and Azure CLI, and provide instructions for both.
  • Reorder examples to present cross-platform (Azure CLI) options before or alongside PowerShell, to avoid Windows-first perception.
  • Include a section or note on how Linux/macOS users can perform the same tasks, including installation and usage of Azure CLI.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-key-vault.md ...-manager/management/relocation/relocation-key-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 detailed PowerShell examples for all key steps (exporting, modifying, and deploying templates) without equivalent Azure CLI or Bash examples. The PowerShell instructions are given equal or greater prominence than the Azure Portal, and there is no mention of Linux-specific workflows or cross-platform command-line alternatives. The absence of Azure CLI or Bash examples makes it harder for Linux users to follow the guidance.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line steps (export, modify, deploy templates).
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Provide Bash script snippets for common operations, especially for data migration tasks (e.g., exporting/importing secrets and certificates).
  • Ensure that references to obtaining region codes include Azure CLI commands (e.g., `az account list-locations`).
  • Where PowerShell is mentioned, clarify that it is available on Linux and macOS, but recommend Azure CLI for native Linux workflows.
  • Add a section or tab for 'Azure CLI' in all places where 'PowerShell' and 'Portal' are presented as options.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-hdinsight.md ...-manager/management/relocation/relocation-hdinsight.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell as a primary method for exporting and deploying templates, often before or alongside Azure CLI, but without explicit Linux shell (bash) examples. There is no mention of Linux-specific tools or command-line patterns (e.g., Bash, SSH, SCP), and the guidance for deployment and export is focused on Azure Portal, PowerShell, and CLI, which can be used on Linux but are often associated with Windows workflows. No Linux-specific instructions or examples are provided, and Windows-centric terminology (e.g., 'Azure PowerShell', 'Cloud Shell') appears frequently.
Recommendations
  • Add explicit bash and Linux shell examples for exporting and deploying ARM/Bicep templates.
  • Include instructions for using Azure CLI in native Linux environments, highlighting differences from Windows usage if any.
  • Mention and provide examples for Linux-native tools (e.g., SSH, SCP, rsync) where relevant, especially for tasks like data migration and cluster access.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first impression.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
  • Review terminology to avoid implying that PowerShell is the default or preferred method, and balance references to Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-storage-account.md ...er/management/relocation/relocation-storage-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only PowerShell examples for command-line operations, with no equivalent examples for Linux or macOS users (e.g., Bash, Azure CLI). The PowerShell instructions are presented as the sole scripting option, and there is no mention of Linux-native tools or shell environments. This may hinder accessibility and usability 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 instructions for common tasks, especially for AzCopy usage and scripting.
  • Explicitly state cross-platform compatibility for AzCopy and provide sample commands for Linux/macOS terminals.
  • Where PowerShell commands are given, provide tabs or sections for equivalent Linux/macOS workflows.
  • Mention that the Azure portal and AzCopy are cross-platform, and clarify any platform-specific requirements or differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-network-nsg.md ...anagement/relocation/relocation-virtual-network-nsg.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, but omits equivalent guidance for Linux users. All command-line examples use PowerShell cmdlets, which are native to Windows and require extra setup on Linux. There are no Bash, Azure CLI, or cross-platform scripting examples, and file editing is demonstrated using Notepad, a Windows tool. The structure presents PowerShell as the only command-line option, implicitly prioritizing Windows workflows.
Recommendations
  • Add Azure CLI examples for all steps (export, edit, deploy, verify, delete NSGs and resource groups), as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell commands for file manipulation and editing, or reference editors available on Linux (e.g., nano, vim) instead of Notepad.
  • Explicitly mention that PowerShell is available on Linux, but provide installation instructions or alternatives for users who prefer Bash/Azure CLI.
  • Present command-line options in a more platform-neutral way, e.g., by using tabs for 'Azure CLI', 'PowerShell', and 'Portal', and avoid implying PowerShell is the default or only choice.
  • Review and update prerequisites and tool references to ensure Linux users are not excluded or required to use Windows-native tools.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-providers-and-types.md ...rce-manager/management/resource-providers-and-types.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. The Azure portal (a GUI tool most commonly used on Windows) is presented first and in greatest detail, with multiple screenshots. Azure PowerShell (primarily a Windows-centric tool, though now cross-platform) is covered before Azure CLI, and with more extensive command examples and output. There is explicit mention of 'Windows Azure Service Management API' in the registration notes. No Linux-specific tools, shell scripts, or platform parity notes are provided. The CLI section (which is cross-platform and preferred on Linux) is present, but comes after PowerShell and is less detailed. No Bash or Linux-native workflow examples are given.
Recommendations
  • Add explicit Bash shell examples for common tasks (using az CLI) to demonstrate Linux parity.
  • Mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Reorder sections so that Azure CLI appears before Azure PowerShell, or present both together to avoid platform prioritization.
  • Include notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell Core on Linux.
  • Reduce reliance on Azure portal screenshots, or supplement with CLI/script equivalents for headless/server environments.
  • Clarify that all operations can be performed from Linux, macOS, and Windows, and highlight any platform-specific caveats.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-network.md ...er/management/relocation/relocation-virtual-network.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, with extensive PowerShell examples and cmdlets. There are no CLI (az), Bash, or Linux-native command examples, nor are cross-platform scripting options mentioned. The PowerShell tab is present and detailed, but there is no equivalent for Azure CLI or Bash, which are commonly used on Linux and macOS. The use of 'notepad' as the editor in PowerShell instructions further reinforces a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell steps, including exporting, editing, and deploying ARM templates.
  • Provide Bash shell scripting examples for Linux/macOS users.
  • Replace or supplement 'notepad' references with cross-platform editors (e.g., 'code', 'vim', 'nano').
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and suitable editors.
  • Ensure parity in troubleshooting and resource management instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/add-template-to-azure-pipelines.md ...e-manager/templates/add-template-to-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 clear Windows bias by focusing exclusively on PowerShell scripts and Windows-based tools/tasks (e.g., AzurePowerShell, AzureFileCopy), with examples and YAML pipelines using 'windows-latest' VM images. There are no Linux shell script equivalents, nor are cross-platform alternatives (such as Bash or AzCopy CLI usage on Linux) mentioned or demonstrated. Windows tools and patterns are presented first and exclusively, with no parity for Linux users.
Recommendations
  • Provide equivalent examples using Bash scripts and the Azure CLI for ARM template deployment.
  • Demonstrate pipelines using 'ubuntu-latest' or other Linux VM images, especially for file copy and deployment tasks.
  • Mention and show usage of AzCopy CLI in a cross-platform context, including Linux and macOS.
  • Add notes or sections highlighting cross-platform compatibility and differences, guiding users on how to adapt instructions for Linux environments.
  • Ensure all PowerShell script references have corresponding Azure CLI or Bash alternatives where possible.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-properties.md ...es/azure-resource-manager/templates/copy-properties.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific examples and tools before Linux equivalents. The only example template linked is for a Windows VM deployment, and deployment instructions prioritize Azure PowerShell without mentioning Azure CLI or Linux shell usage. There are no Linux-specific examples or guidance, and PowerShell is mentioned before CLI in version requirements.
Recommendations
  • Include example templates for Linux VM deployments alongside Windows examples.
  • Provide deployment instructions using Azure CLI and bash/zsh shell commands, not just PowerShell.
  • Mention Azure CLI before or alongside PowerShell when discussing supported versions and deployment methods.
  • Ensure parity in quickstart links and tutorials for both Windows and Linux scenarios.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources.md ...les/azure-resource-manager/management/tag-resources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Azure PowerShell and REST API as the primary supported interfaces for tag operations, with PowerShell mentioned before CLI and other cross-platform tools. The Tag Contributor role is described as supporting all tag operations through Azure PowerShell and REST API, but does not mention Azure CLI or other Linux-friendly tools in the same context. Examples and instructions for updating tags on certain resources (e.g., IP Groups) do reference Azure CLI, but overall, PowerShell is given prominence. There are no explicit Linux shell or Bash examples, and the documentation does not clarify parity between Windows and Linux tooling for tag management.
Recommendations
  • Explicitly mention Azure CLI alongside PowerShell wherever tag operations are discussed, especially in sections about permissions and supported interfaces.
  • Provide Bash or Linux shell examples for tag management tasks, ensuring parity with PowerShell examples.
  • Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux users.
  • Where REST API is referenced, provide sample curl commands or Linux-friendly usage patterns.
  • Review the order of tool mentions to avoid always listing Windows tools (PowerShell) first; alternate or group by platform-neutral tools.
  • Add a section or note on Linux/macOS compatibility for all tag management operations.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tls-support.md ...icles/azure-resource-manager/management/tls-support.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, referencing Windows versions and .NET Framework/Visual Studio exclusively, and providing guidance and troubleshooting steps focused on PowerShell and WinHTTP. There are no Linux-specific instructions, examples, or tool recommendations, and Linux environments are not mentioned in migration or troubleshooting steps.
Recommendations
  • Add explicit guidance for Linux environments, including how to verify and configure TLS 1.2 support on popular distributions (e.g., Ubuntu, CentOS).
  • Include examples using Linux command-line tools (e.g., OpenSSL, curl) to check TLS versions and troubleshoot connections.
  • Mention Linux equivalents for Windows tools such as Fiddler (e.g., Wireshark, tcpdump) and provide links or usage instructions.
  • Discuss updating libraries and frameworks commonly used on Linux (e.g., OpenSSL, Python, Java) and how to ensure they use TLS 1.2.
  • Balance references to .NET Framework and Visual Studio with information about cross-platform frameworks and editors (e.g., .NET Core, VS Code, JetBrains Rider).
  • Add troubleshooting steps for Linux-based clients and servers, including configuration files and environment variables relevant to TLS settings.
GitHub Create Pull Request
← Previous Page 17 of 52 Next →