Extended Zones

13
Total Pages
7
Linux-Friendly Pages
6
Pages with Bias
46.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (10)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-container-apps.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page provides only a PowerShell script for deploying Arc-enabled ContainerApps in an Extended Zone, with no equivalent Bash or Linux shell example. The script uses Windows/PowerShell-specific syntax (e.g., backticks for line continuation, Start-Sleep, Write-Debug, Write-Error, and Windows-style paths), and the instructions assume the user is running PowerShell. There is no mention of Linux or cross-platform alternatives, and no guidance for users on macOS or Linux.
Recommendations:
  • Provide a Bash (Linux/macOS) equivalent script for all deployment steps, using POSIX-compliant shell syntax.
  • Explicitly state that the provided script is for PowerShell/Windows, and offer a parallel section for Linux/macOS users.
  • Avoid Windows-specific path syntax (e.g., .\DemoApp) or provide both Windows and Unix-style path examples.
  • Use cross-platform Azure CLI commands in the main documentation body, and only supplement with OS-specific scripting where necessary.
  • Add a note in the prerequisites about supported operating systems and shell environments.
  • Where possible, use code blocks that are OS-agnostic, or provide tabs/switchers for PowerShell and Bash.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-arc-enabled-aks-cluster.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 strong Windows bias by providing all command-line and scripting examples in PowerShell syntax, including the main automation function and even simple Azure CLI invocations. There are no Bash or Linux shell equivalents, and the scripting patterns (e.g., function definition, parameter handling) are tailored to PowerShell users. This may disadvantage Linux or macOS users, who are likely to use Bash or other Unix shells.
Recommendations:
  • Provide all Azure CLI examples in both PowerShell and Bash syntax, especially for multi-step scripts and automation functions.
  • Include a Bash script or step-by-step Bash command sequence for creating and connecting the AKS cluster, using standard Bash idioms (e.g., environment variables, shell functions).
  • When showing Azure CLI commands, use the generic CLI syntax (which is cross-platform) and avoid wrapping them in PowerShell-specific constructs unless necessary.
  • Explicitly mention that the steps are cross-platform and clarify any OS-specific prerequisites or differences.
  • For resource cleanup, show both PowerShell and Bash command examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-vm-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively demonstrates deploying a Windows Server VM, with instructions and screenshots focused on RDP (Remote Desktop Protocol) for Windows-based access. There are no examples or guidance for deploying a Linux VM, nor are SSH or Linux-specific access methods mentioned. The use of RDP and Windows Server as the default image and connection method demonstrates a Windows-first and Windows-tools bias, with Linux scenarios entirely omitted.
Recommendations:
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu or CentOS) in the Azure Extended Zone, including selection of a Linux image in the 'Image' step.
  • Include guidance and screenshots for configuring SSH access (port 22) for Linux VMs, alongside or instead of RDP.
  • In the 'Connect to virtual machine' section, provide steps for connecting via SSH from Linux, macOS, and Windows clients (e.g., using ssh command-line tools or PuTTY).
  • Where possible, present both Windows and Linux options side-by-side, or clarify that the instructions are specific to Windows and link to Linux equivalents.
  • Update caution and security notes to reference best practices for both RDP and SSH access.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-postgre-sql.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 provides only a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The script uses PowerShell-specific syntax and patterns, which may not be directly usable on Linux or macOS systems. The absence of a Linux/Bash example and the exclusive use of PowerShell suggest a Windows-first approach, potentially making it less accessible for Linux users.
Recommendations:
  • Provide a Bash (Linux/macOS) equivalent script for all deployment steps, using standard shell syntax and environment variable handling.
  • Explicitly mention that the steps can be performed on both Windows (PowerShell) and Linux/macOS (Bash), and clarify any platform-specific differences.
  • Ensure that all az CLI commands are shown in a cross-platform way, avoiding PowerShell-specific constructs (e.g., $ENV:, backticks for line continuation, parameter passing).
  • Add a section or callout for Linux/macOS users, highlighting any required tools or differences in environment setup.
  • Consider making Bash the default example or presenting both PowerShell and Bash examples side by side for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-arc-enabled-aks-cluster.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 strong Windows bias by providing all command-line examples and automation scripts exclusively in PowerShell syntax. There are no Bash or Linux shell equivalents, and the scripting patterns (e.g., function definitions, parameter handling) are tailored for Windows/PowerShell users. This may hinder accessibility for Linux or macOS administrators, who are more likely to use Bash or other Unix shells.
Recommendations:
  • Provide equivalent Bash shell scripts for all PowerShell examples, especially for the main cluster creation workflow.
  • When showing command-line examples (such as az CLI usage), present both PowerShell and Bash syntax side-by-side or clearly indicate differences.
  • Avoid using PowerShell-specific constructs (like function definitions and parameter blocks) as the only automation example; instead, offer cross-platform alternatives.
  • Explicitly mention that the Azure CLI is cross-platform and can be used from Bash, PowerShell, or CMD, and link to relevant installation or usage guides for Linux/macOS.
  • Add a note or section for Linux/macOS users, clarifying any differences or additional steps required.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-container-apps.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 provides only a PowerShell script for deploying Arc-enabled ContainerApps in an Extended Zone, with no equivalent Bash or Linux shell example. All automation and scripting guidance is presented in PowerShell syntax, which is native to Windows and less commonly used on Linux. There is no mention of Linux or cross-platform alternatives, and the script assumes a Windows environment (e.g., use of .ps1 files, PowerShell-specific constructs).
Recommendations:
  • Provide a Bash (or cross-platform shell) script example alongside the PowerShell script to ensure Linux users can follow the same workflow.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI and Bash, and provide any necessary adjustments (e.g., syntax differences, file paths).
  • If PowerShell is required, clarify that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS.
  • Review all script snippets and ensure that any Windows-specific commands or patterns have Linux equivalents or are written in a cross-platform manner.
  • Consider restructuring the documentation to present both Windows and Linux approaches in parallel, or at least note the parity and differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-managed-sql.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 PowerShell scripts and command examples, with no equivalent Bash or Linux shell instructions. All automation and CLI usage is shown in PowerShell syntax, which is native to Windows, and there is no mention of how to perform these steps on Linux or macOS environments. This may hinder accessibility for users on non-Windows platforms.
Recommendations:
  • Provide equivalent Bash shell scripts and command-line examples for Linux/macOS users alongside the PowerShell examples.
  • Explicitly mention cross-platform compatibility for all CLI commands, clarifying that Azure CLI and kubectl are available on Linux/macOS.
  • Where possible, use platform-agnostic scripting (e.g., Bash or plain Azure CLI commands) in mainline documentation, or offer both PowerShell and Bash versions.
  • Add a note or section addressing any platform-specific differences or prerequisites for Linux/macOS users.
  • Ensure that tool installation and usage instructions are not Windows-centric and reference Linux/macOS installation guides where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-postgre-sql.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 provides only a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The script uses PowerShell-specific syntax and patterns, which are native to Windows environments. There is no mention of how to perform the same steps on Linux or macOS, and the only code samples and automation guidance are Windows-centric.
Recommendations:
  • Provide a Bash (or POSIX shell) script example that performs the same deployment steps, using az CLI and standard Linux shell conventions.
  • Explicitly mention that the steps can be performed from Linux/macOS as well as Windows, and clarify any OS-specific requirements.
  • Where possible, use cross-platform scripting (e.g., az CLI commands in Bash) in the main flow, and move PowerShell-specific automation to a separate section or appendix.
  • Ensure that all prerequisite tools and instructions are described in a cross-platform manner, including installation steps for Linux/macOS.
  • Add notes or callouts for any steps that are different or require adaptation on Linux/macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-aks-cluster.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI or PowerShell). While this avoids explicit Windows-only tooling, it implicitly favors Windows users by omitting Linux-friendly CLI workflows, which are common in Linux environments and automation. There is also no mention of how to perform these tasks via command line, which is often preferred by Linux users.
Recommendations:
  • Add Azure CLI examples for all major steps (e.g., creating the resource group, deploying the AKS cluster, cleaning up resources).
  • If PowerShell examples are added, ensure Azure CLI (cross-platform) examples are provided first or alongside.
  • Explicitly mention that the Azure CLI can be used on Windows, Linux, and macOS, and provide installation links.
  • Include a section or links for automating these tasks via scripts for both Linux and Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-vm-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively demonstrates deploying a Windows Server VM, with instructions and screenshots focused on RDP connectivity (a Windows-centric tool). There are no examples or options provided for deploying a Linux VM, nor are SSH or Linux-related connectivity methods mentioned. This creates a clear Windows-first bias and omits Linux user scenarios.
Recommendations:
  • Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu or CentOS) alongside the Windows example.
  • Provide guidance for configuring SSH access (port 22) for Linux VMs, including how to use SSH keys and connect from Linux/macOS/Windows clients.
  • Mention both RDP (for Windows) and SSH (for Linux) in the 'Connect to virtual machine' section, with steps for each.
  • In the 'Image' selection step, show how to choose both Windows and Linux images.
  • Add a note or table summarizing differences in connection methods and initial setup between Windows and Linux VMs.