Extended Zones

32
Total Pages
25
Linux-Friendly Pages
7
Pages with Bias
21.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

19 issues found
Showing 1-19 of 19 flagged pages
Extended Zones Quickstart: Deploy a virtual machine in an Extended Zone - Azure portal .../blob/main/articles/extended-zones/deploy-vm-portal.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 exclusively guiding users to deploy a Windows Server VM, opening RDP ports, and connecting via RDP, which are Windows-centric patterns. There are no Linux VM options, SSH instructions, or Linux/macOS connection examples. The only OS image suggested is Windows Server, and the connection method is RDP, which is not applicable to Linux VMs.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows VM example.
  • Provide SSH connection steps for Linux/macOS users, including how to generate SSH keys and connect via SSH.
  • Mention Linux VM images in the 'Image' selection step and clarify differences in connection methods.
  • Add screenshots and portal steps relevant to Linux VM deployment and SSH access.
  • Clarify that RDP is only for Windows VMs and provide parity for Linux VM scenarios.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: Managed SQL Instance ...es/extended-zones/arc-enabled-workloads-managed-sql.md
Medium 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 notable Windows bias by providing only PowerShell scripts and examples for deploying Arc-enabled Managed SQL Instance in an Extended Zone. There are no Bash or Linux shell equivalents, and all command-line instructions are shown in PowerShell syntax, which is native to Windows. This can create friction for Linux/macOS users, who typically use Bash or other shells and may not be familiar with PowerShell scripting.
Recommendations
  • Provide equivalent Bash shell scripts and examples alongside PowerShell, especially for steps involving Azure CLI and resource creation.
  • Explicitly state that Azure CLI commands can be run in Bash, and show syntax differences if any.
  • Add notes or sections highlighting cross-platform usage, including how Linux/macOS users can adapt the instructions.
  • Avoid using PowerShell-specific constructs (e.g., `$ENV:`, `[string]`, `Write-Output`) in generic Azure CLI workflows, or provide alternatives.
  • Where possible, use Azure CLI commands in plain shell syntax, which is portable across platforms.
GitHub Create Pull Request
Extended Zones Create an Arc-enabled AKS cluster in an Extended Zone ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
Medium 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 exclusively uses PowerShell syntax for all command-line examples, including the main deployment script and resource cleanup. There are no Bash or Linux/macOS shell examples, and the scripting patterns (e.g., function definition, parameter passing) are tailored for PowerShell, which is native to Windows. This creates friction for Linux/macOS users, who typically use Bash or other shells and may not be familiar with PowerShell scripting.
Recommendations
  • Provide equivalent Bash shell examples for all command-line instructions, especially for the main cluster creation workflow.
  • Include notes clarifying that Azure CLI commands work cross-platform, and show usage in both Windows (PowerShell) and Linux/macOS (Bash).
  • Avoid using PowerShell-specific scripting constructs (e.g., function definitions, parameter blocks) unless also providing a Bash alternative.
  • Explicitly mention platform compatibility and link to Azure CLI installation guides for Linux/macOS.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium 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 exclusively provides a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The instructions and code are written in PowerShell syntax, which is native to Windows and less common on Linux/macOS. There is no mention of how to perform the same steps using Bash, nor are Linux-specific considerations addressed. The clean-up command is also shown in PowerShell, even though az CLI is cross-platform.
Recommendations
  • Provide a Bash shell script example for Linux/macOS users, covering the same deployment steps.
  • Explicitly state that az CLI commands can be run on Linux/macOS and show examples in Bash syntax.
  • Add notes or sections highlighting any OS-specific differences or requirements.
  • Ensure that client tool recommendations include Linux/macOS alternatives where relevant.
GitHub Create Pull Request
Extended Zones Quickstart: Deploy a virtual machine in an Extended Zone - Azure portal .../blob/main/articles/extended-zones/deploy-vm-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image, enabling RDP (a Windows protocol) for remote access, and providing connection instructions only for RDP. There are no Linux VM images or SSH connection instructions, and the example workflow is tailored to Windows users. Linux/macOS users are left without guidance for deploying or connecting to Linux VMs.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Provide SSH connection steps for Linux/macOS users, including guidance on configuring SSH keys and connecting via terminal.
  • Mention Linux images as options in the 'Image' selection step.
  • Add a note or section clarifying that both Windows and Linux VMs are supported, and link to relevant Linux quickstarts.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.md
Medium 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 provides only PowerShell-based automation for deploying Arc-enabled ContainerApps, with no equivalent Bash, shell, or Linux/macOS instructions. All example scripts and resource cleanup commands are presented in PowerShell syntax, which is native to Windows and not pre-installed or commonly used on Linux/macOS. This creates friction for non-Windows users, who must translate the steps or install PowerShell Core.
Recommendations
  • Provide equivalent Bash/shell scripts for all automation steps, especially for Azure CLI commands and resource management.
  • Clearly indicate which commands are cross-platform (e.g., Azure CLI) and which are PowerShell-specific.
  • Add a section or note for Linux/macOS users, including prerequisites (e.g., PowerShell Core installation if needed) or alternative instructions.
  • Ensure resource cleanup examples are shown in both PowerShell and Bash.
  • Consider presenting Azure CLI commands in Bash syntax first, as Azure CLI is cross-platform.
GitHub Create Pull Request
Extended Zones Deploy a virtual machine in an Extended Zone using Azure CLI ...ocs/blob/main/articles/extended-zones/deploy-vm-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides a VM deployment example using a Windows Server image only, without mentioning or providing a Linux image alternative. This creates a subtle bias toward Windows, as Linux users may need to infer how to adapt the example for their needs.
Recommendations
  • Include an example using a popular Linux image (e.g., UbuntuLTS) alongside the Windows example.
  • Explicitly mention that any supported OS image can be used and link to a list of available images.
  • Clarify that the Azure CLI commands are OS-agnostic and provide guidance for Linux/macOS users if there are any platform-specific considerations.
GitHub Create Pull Request
Extended Zones Tutorial: Replicate 3rd Party (3P) Images into an Azure Extended Zone with Azure Compute Gallery ...cles/extended-zones/replicate-azure-compute-gallery.md
Medium 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 notable Windows bias: PowerShell is the only scripting example provided for most steps (creating managed identity, assigning roles, REST API calls), with no Bash or Linux shell equivalents. The PowerShell tab is present for every code section, while Linux/macOS users are only offered Azure CLI for the final replication step. Additionally, PowerShell examples are shown before CLI, and Windows tools (PowerShell, Fiddler) are mentioned for REST calls, with no mention of Linux alternatives (e.g., curl). This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native shell tools.
Recommendations
  • Provide Bash/Azure CLI equivalents for all PowerShell scripts, especially for managed identity creation and role assignment.
  • Include Linux/macOS-friendly REST API call examples using curl or httpie.
  • Mention cross-platform tools (e.g., curl, Postman) alongside Windows tools for API calls.
  • Present CLI/Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly state that all steps can be performed on Linux/macOS and link to relevant cross-platform documentation.
GitHub Create Pull Request
Extended Zones Create an Arc-enabled AKS cluster in an Extended Zone ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 by providing all command-line examples and automation scripts in PowerShell syntax, including a PowerShell function for cluster creation. There are no Bash or Linux shell equivalents, and the setup and cleanup commands are also shown in PowerShell. This may create friction for Linux/macOS users who are more familiar with Bash or other shells.
Recommendations
  • Provide equivalent Bash shell examples for all command-line instructions and scripts.
  • Clearly indicate that Azure CLI commands can be run on any platform and show cross-platform usage.
  • Offer downloadable script samples for both PowerShell and Bash.
  • Add notes or sections highlighting differences or considerations for Linux/macOS users.
GitHub Create Pull Request
Extended Zones Deploy a virtual machine in an Extended Zone using Azure CLI ...ocs/blob/main/articles/extended-zones/deploy-vm-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates deploying a Windows Server VM, with no mention or example of Linux VM images. This creates a Windows-first impression and omits guidance for Linux users who may wish to deploy a Linux-based VM in an Extended Zone.
Recommendations
  • Add an example for deploying a Linux VM (e.g., using --image UbuntuLTS or another popular Linux image).
  • Briefly mention that the --image parameter supports both Windows and Linux images, and link to the list of available images.
  • Consider alternating or showing both Windows and Linux examples to ensure parity.
GitHub Create Pull Request
Extended Zones Tutorial: Replicate 3rd Party (3P) Images into an Azure Extended Zone with Azure Compute Gallery ...cles/extended-zones/replicate-azure-compute-gallery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code samples primarily for the Azure Portal and PowerShell, with PowerShell examples given for all automation steps. There are no Bash or Linux shell examples for tasks like creating managed identities, assigning roles, or making REST API calls. The only Linux-friendly example is a single Azure CLI command for image replication, but all other scripting is Windows/PowerShell-centric.
Recommendations
  • Add Bash/Azure CLI examples for all steps currently shown only in PowerShell (e.g., creating managed identities, assigning roles, making REST API PATCH calls).
  • Explicitly mention cross-platform tools (curl, jq, etc.) for REST API calls, not just Postman/Fiddler/PowerShell.
  • Ensure Linux/macOS users can follow the tutorial end-to-end without needing PowerShell.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: Managed SQL Instance ...es/extended-zones/arc-enabled-workloads-managed-sql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based examples and scripts for deploying Arc-enabled Managed SQL Instance, with no equivalent Bash or Linux shell instructions. All code snippets use PowerShell syntax, and there is no mention of Linux/macOS-specific guidance or parity. This creates friction for users on non-Windows platforms, especially since Azure CLI and Kubernetes tools are cross-platform.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for the main deployment workflow.
  • Explicitly state that the steps can be performed on Linux/macOS and clarify any platform-specific requirements.
  • Use Azure CLI commands in a platform-neutral way, avoiding PowerShell-specific syntax (e.g., environment variable handling, command substitution).
  • Add notes or sections for Linux/macOS users, including troubleshooting tips and tool installation instructions.
  • Ensure that all referenced tools (Azure CLI, kubectl, arcdata) are described as cross-platform, and link to installation guides for Linux/macOS.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based automation for deploying Arc-enabled ContainerApps in Extended Zones, with no Bash, shell, or Linux-native scripting examples. All step-by-step instructions and code samples use PowerShell syntax and conventions, which are not natively supported on most Linux/macOS systems. There is no mention of Linux/macOS alternatives, nor any guidance for adapting the process for those platforms.
Recommendations
  • Provide equivalent Bash/shell script examples for all PowerShell code blocks.
  • Explicitly note cross-platform compatibility for Azure CLI commands and clarify which steps require adaptation for Linux/macOS.
  • Add a section or callout for Linux/macOS users with instructions or links to platform-specific guidance.
  • Ensure resource cleanup examples include Bash syntax as well as PowerShell.
  • Consider using Azure CLI commands directly in documentation, as they are cross-platform, and minimize reliance on PowerShell-specific constructs.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based examples and scripts for deploying Arc-enabled PostgreSQL in Extended Zones. There are no Bash, shell, or Linux-native script equivalents, and the instructions assume a Windows/PowerShell environment throughout. This creates friction for Linux/macOS users, who must adapt the examples themselves.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell scripts.
  • Explicitly mention cross-platform compatibility for Azure CLI commands and clarify which steps are OS-agnostic.
  • Add notes or sections for Linux/macOS users, including any required environment setup or differences.
  • Consider reordering examples so that OS-neutral CLI commands are shown first, followed by platform-specific scripts.
GitHub Create Pull Request
Extended Zones Create an Arc-enabled AKS cluster in an Extended Zone ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
Medium 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 provides all command-line examples and scripts in PowerShell syntax, including a complex function for cluster creation. No Bash or Linux/macOS shell equivalents are given, and PowerShell is used for Azure CLI invocation throughout. This creates friction for Linux/macOS users, who typically use Bash and may not be familiar with PowerShell scripting.
Recommendations
  • Provide Bash shell equivalents for all PowerShell scripts and command examples.
  • Explicitly note that Azure CLI commands work cross-platform and show usage in Bash (e.g., with environment variables, parameter passing).
  • Avoid wrapping Azure CLI commands in PowerShell functions unless a Bash alternative is also provided.
  • Clarify any platform-specific requirements or differences in the prerequisites section.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.md
Medium 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 provides only PowerShell-based automation for deploying Arc-enabled ContainerApps in Extended Zones, with no Bash or Linux shell equivalents. All scripting and resource management examples are given in PowerShell syntax, which is native to Windows and less common on Linux/macOS. This creates friction for users on non-Windows platforms, as they must translate the workflow to Bash or use PowerShell Core, which is not standard on most Linux distributions.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, using standard Linux tools and Azure CLI.
  • Explicitly mention cross-platform compatibility and note if PowerShell Core is required for Linux/macOS users.
  • Reorder examples so that Bash and PowerShell are presented side-by-side, or Bash is shown first to emphasize parity.
  • Add notes or links to resources for installing PowerShell Core on Linux/macOS, if PowerShell scripting is unavoidable.
  • Ensure all az CLI commands are shown in a way that works in Bash (e.g., avoid backticks, use \ for line continuation).
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium 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 provides only PowerShell-based examples and scripts for deploying Arc-enabled PostgreSQL in Extended Zones. There are no Bash, shell, or Linux-native script examples, and the instructions assume the use of PowerShell, which is primarily a Windows tool. This creates friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Provide equivalent Bash/shell script examples for all PowerShell scripts.
  • Explicitly mention that az CLI commands are cross-platform and can be run in Bash, Zsh, etc.
  • Add notes or sections for Linux/macOS users, clarifying any differences in environment variables or command syntax.
  • Ensure cleanup and other operational commands are shown in both PowerShell and Bash formats.
GitHub Create Pull Request
Extended Zones Deploy a virtual machine in an Extended Zone using Azure CLI ...ocs/blob/main/articles/extended-zones/deploy-vm-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides only a Windows VM deployment example, with no mention of Linux VM images or examples. The quickstart uses Azure CLI, which is cross-platform, but the exclusive use of a Windows image and lack of Linux parity in examples creates a subtle Windows bias.
Recommendations
  • Include a Linux VM deployment example alongside the Windows example, such as using Ubuntu or CentOS images.
  • Explicitly mention that Azure CLI supports deploying both Windows and Linux VMs.
  • Provide guidance or links to documentation for common Linux VM images and their parameters.
  • Alternate or parallelize examples to show both Windows and Linux scenarios.
GitHub Create Pull Request
Extended Zones Quickstart: Deploy a virtual machine in an Extended Zone - Azure portal .../blob/main/articles/extended-zones/deploy-vm-portal.md
Medium Priority View Details →
Scanned: 2026-01-10 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 a Windows bias by exclusively using Windows Server as the example VM image, instructing users to open RDP ports (which are primarily used for Windows remote desktop access), and providing connection instructions only for RDP. There are no examples or instructions for deploying or connecting to Linux VMs (e.g., using SSH), nor are Linux images mentioned as options.
Recommendations
  • Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu) alongside the Windows example.
  • Add steps for configuring SSH access (port 22) for Linux VMs, including how to generate and use SSH keys.
  • Provide connection instructions for Linux/macOS users, such as using SSH from a terminal.
  • Mention Linux images as selectable options in the VM creation process.
  • Clarify that the portal supports both Windows and Linux VM deployments.
GitHub Create Pull Request