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 (5)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/find-your-subscription-id.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/find-your-subscription-id.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/quality-checks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.