Azure Large Instances

9
Total Pages
6
Linux-Friendly Pages
3
Pages with Bias
33.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

12 issues found
Showing 1-12 of 12 flagged pages
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for onboarding and configuration tasks, with no equivalent Linux CLI (e.g., Bash/Azure CLI) examples. Windows tools and patterns (PowerShell cmdlets) are mentioned and used throughout the setup instructions, while Linux alternatives are absent or referenced only generically. The only explicit Linux mention is in the context of setting up a Red Hat Satellite server, but no Linux-based onboarding or configuration instructions are provided.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash examples for all PowerShell cmdlet instructions, especially for onboarding, resource management, and ExpressRoute configuration.
  • Explicitly mention Linux-compatible tools and workflows where relevant, such as using Azure CLI on Linux/macOS for resource provisioning and management.
  • Structure example sections to present both Windows (PowerShell) and Linux (CLI/Bash) approaches side-by-side, or clearly indicate which instructions apply to which platform.
  • Include references to Linux documentation and troubleshooting resources for Azure Large Instances.
  • Clarify prerequisites for both Windows and Linux users, including installation steps for Azure CLI and authentication methods.
GitHub Create Pull Request
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.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 Windows bias by providing only PowerShell/Azure CLI examples for onboarding and ExpressRoute Fast Path setup, with no equivalent Linux shell or cross-platform CLI instructions. The use of PowerShell cmdlets is assumed throughout, and Windows-centric tools and patterns are referenced first and exclusively in the example sections. There is no mention of Linux-specific commands or guidance for users who may be operating from a Linux or macOS environment.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell cmdlets, ensuring Linux and macOS users can follow the onboarding steps without needing Windows or PowerShell.
  • Explicitly mention cross-platform tooling (e.g., Azure CLI) and provide links to installation and usage guides for Linux/macOS.
  • Add a section clarifying which steps are OS-agnostic and which require platform-specific commands, with clear guidance for both Windows and Linux users.
  • Ensure that references to enabling features (like Accelerated Networking) include both Windows and Linux VM instructions, not just links.
  • Review all example code blocks and ensure parity between Windows and Linux environments, including environment setup, authentication, and resource management.
GitHub Create Pull Request
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by providing only PowerShell-based examples for onboarding and configuration tasks, with no equivalent Linux CLI or Bash examples. Windows tools and patterns (PowerShell cmdlets, variable declaration syntax) are used exclusively and are presented first and only, while Linux alternatives (such as Azure CLI or Bash scripting) are missing. Although there is a mention of accelerated networking for both Windows and Linux VMs, the actual setup instructions and examples are Windows-centric.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all onboarding and configuration steps currently shown only in PowerShell.
  • Explicitly mention Linux-compatible tools and workflows alongside Windows ones, especially for tasks like resource management and network configuration.
  • Reorganize example sections to present both Windows and Linux approaches in parallel, or alternate which is presented first.
  • Include links to Linux-specific documentation where relevant, such as setting up ExpressRoute or managing Azure resources from Linux environments.
  • Clarify any platform-specific requirements or limitations for Azure Large Instances onboarding, ensuring Linux users are equally supported.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md ...icles/azure-large-instances/onboarding-requirements.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, primarily through exclusive use of PowerShell/Azure CLI examples for onboarding and ExpressRoute Fast Path setup. No Linux shell (bash) equivalents are provided, and Windows-centric tooling (PowerShell cmdlets) is assumed for all configuration steps. References to Linux are limited to a brief mention of Red Hat Satellite server installation, without parity in example commands or tooling.
Recommendations
  • Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for ExpressRoute and resource management tasks.
  • Explicitly mention Linux-compatible tools and workflows for onboarding steps, such as using Azure CLI in bash or shell scripts.
  • Balance references to Windows and Linux environments throughout the documentation, ensuring that Linux users have clear, actionable steps.
  • Where possible, link to Linux-specific documentation or guides for Azure onboarding and networking configuration.
  • Add a section or callout for Linux administrators, summarizing key differences and providing tailored instructions.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through exclusive use of PowerShell/Azure CLI examples for onboarding and ExpressRoute Fast Path setup, with no equivalent Linux shell (bash/az CLI) commands provided. Windows-centric tools and patterns (PowerShell cmdlets) are presented as the default, and Linux alternatives are not mentioned or demonstrated, despite references to Linux VMs elsewhere in the document.
Recommendations
  • Provide equivalent Linux shell (bash) and Azure CLI command examples for all PowerShell cmdlet instructions.
  • Clearly indicate cross-platform compatibility for each step, specifying which commands/tools work on Windows, Linux, or both.
  • Where PowerShell is used, offer az CLI alternatives, which are natively supported on Linux and macOS.
  • Add explicit instructions for Linux users, including environment setup and prerequisites.
  • Review all referenced links and ensure they include Linux-specific guidance where relevant.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 Azure PowerShell (Windows-centric) command examples for onboarding and configuring Azure Large Instances, without offering equivalent Azure CLI or Linux shell examples. The instructions for enabling ExpressRoute Fast Path and related tasks are exclusively shown using PowerShell cmdlets, and there is no mention or example of how to perform these tasks using Linux-native tools or cross-platform CLI. Additionally, the guidance to install PowerShell modules is presented before any mention of Linux compatibility, and there is no explicit parity for Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all configuration steps, especially for ExpressRoute and networking setup.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant cross-platform documentation.
  • Where PowerShell is required, clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions for those platforms.
  • Add Linux shell (bash) script examples for variable declaration and command execution, ensuring Linux users can follow the onboarding process without switching to Windows tools.
  • Review all sections for implicit Windows-first language or assumptions, and ensure Linux and cross-platform scenarios are treated with equal prominence.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing onboarding and configuration examples using Azure PowerShell cmdlets and Windows-style variable declarations. There are no equivalent CLI (az), Bash, or Linux-native examples for onboarding, managing ExpressRoute, or enabling features. The only mention of Linux is in the context of installing a Red Hat Satellite server, but no Linux command-line or automation examples are provided. The documentation assumes familiarity with PowerShell and Windows-centric tooling, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash examples for all PowerShell commands and workflows, especially for ExpressRoute and network configuration.
  • When introducing command-line examples, present both Windows/PowerShell and Linux/Bash/CLI options, or clearly indicate which platforms each example applies to.
  • Explicitly mention Linux-compatible tools and patterns (such as Bash scripting, cloud-init, or Ansible) where appropriate.
  • Ensure that references to enabling features (like Accelerated Networking) include links and steps for both Windows and Linux VMs.
  • Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in examples.
GitHub Create Pull Request
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias, especially in the ExpressRoute Fast Path setup section. All command-line examples use Azure PowerShell cmdlets with Windows-style variable declarations and login flows, with no Azure CLI (cross-platform) or Bash examples provided. The instructions and code snippets assume a PowerShell environment, which is native to Windows but less common on Linux/macOS. References to enabling accelerated networking do mention Linux, but the actual setup steps and examples are Windows-centric.
Recommendations
  • Provide equivalent Azure CLI/Bash examples for all PowerShell cmdlets, especially for ExpressRoute and networking setup.
  • Explicitly mention that PowerShell Core is available cross-platform, or clarify if Windows PowerShell is required.
  • Reorder examples so that cross-platform (Azure CLI/Bash) instructions are presented first or alongside PowerShell.
  • Add notes or links for Linux/macOS users on how to install and use Azure CLI and PowerShell Core.
  • Ensure that any referenced documentation (e.g., accelerated networking) includes Linux-specific instructions or links.
GitHub Create Pull Request
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.md
Medium Priority View Details →
Scanned: 2026-01-13 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, especially in the ExpressRoute Fast Path setup section. All command-line examples use Azure PowerShell cmdlets, with no Azure CLI, Bash, or Linux-native instructions. The variable declarations and connection setup are shown only in PowerShell syntax, which is most familiar to Windows users. There is no mention of Linux/macOS alternatives or parity, and the guidance assumes familiarity with Windows tools and workflows. While some references mention Linux (e.g., Red Hat Satellite server), the critical onboarding and configuration steps are Windows-centric.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell cmdlets, especially for ExpressRoute and gateway setup.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and link to relevant cross-platform documentation.
  • Reorder examples so that cross-platform (CLI) instructions are presented before or alongside PowerShell examples.
  • Add notes clarifying tool compatibility and prerequisites for non-Windows environments.
  • Include troubleshooting tips for Linux/macOS users where workflows may differ.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/find-your-subscription-id.md ...les/azure-large-instances/find-your-subscription-id.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides instructions solely for the Azure web portal, without mentioning command-line alternatives. There are no examples for Linux users (e.g., using Azure CLI), nor are PowerShell or Windows-specific tools mentioned, but the absence of CLI guidance can disadvantage Linux users who may prefer or require non-GUI methods.
Recommendations
  • Add instructions for finding the subscription ID using the Azure CLI, which is cross-platform and commonly used on Linux.
  • If mentioning PowerShell, ensure Azure CLI examples are given equal prominence and appear before or alongside any Windows-specific tools.
  • Clarify that the Azure portal is accessible from any OS, but provide alternative methods for users who prefer or require command-line access.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/find-your-subscription-id.md ...les/azure-large-instances/find-your-subscription-id.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation only describes how to find the subscription ID via the Azure portal, which is a graphical interface accessible from any OS, but does not mention command-line alternatives. There are no examples for Linux users (e.g., using Azure CLI), nor are there any PowerShell or Windows-specific tools, but the lack of CLI instructions may disadvantage Linux users who prefer or require terminal-based workflows.
Recommendations
  • Add instructions for finding the subscription ID using Azure CLI, which is cross-platform and commonly used on Linux.
  • If mentioning PowerShell, ensure equivalent Azure CLI examples are provided and presented with equal prominence.
  • Explicitly state that the portal method works on all operating systems, but also provide terminal-based alternatives for users who may not use a GUI.
  • Consider including a table or section comparing methods (Portal, Azure CLI, PowerShell) to ensure parity and user choice.
GitHub Create Pull Request
Azure Large Instances https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/quality-checks.md .../main/articles/azure-large-instances/quality-checks.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or instructions, but it also omits any mention of Linux or cross-platform considerations. There are no explicit Windows or PowerShell examples, but the lack of Linux-specific guidance or parity checks could be seen as a subtle bias by omission.
Recommendations
  • Add explicit instructions or examples for both Windows and Linux environments when discussing OS-level checks.
  • Mention common tools for both platforms (e.g., PowerShell for Windows, Bash/SSH for Linux) when suggesting how to perform connectivity or health checks.
  • Include sample commands or scripts for verifying server health, LUN accuracy, and configuration checks on both Windows and Linux.
  • Clarify that the guidance applies to both Windows and Linux Azure Large Instances, or specify any differences in procedures.
GitHub Create Pull Request