Extended Zones

16
Total Pages
8
Linux-Friendly Pages
8
Pages with Bias
50.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

52 issues found
Showing 1-25 of 52 flagged pages
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.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 provides only PowerShell-based deployment scripts and examples, which are native to Windows environments. There are no Bash, shell, or Linux-native instructions, nor is there mention of how to perform these steps on Linux or macOS. The use of PowerShell as the sole scripting language and lack of cross-platform guidance creates a Windows-centric bias.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Explicitly state that the Azure CLI commands can be run on any platform and clarify which steps are PowerShell-specific.
  • Add notes or sections highlighting cross-platform compatibility and any differences in command syntax or prerequisites for Linux/macOS.
  • Consider using platform-neutral scripting (e.g., Bash with Azure CLI) for core deployment steps, reserving PowerShell for Windows-specific scenarios.
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
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 exclusively uses PowerShell syntax for all command-line examples, including the main deployment script and resource cleanup. There are no Bash or Linux shell equivalents provided, and the scripting patterns (e.g., function declaration, parameter passing) are tailored for Windows/PowerShell users. This creates a bias toward Windows environments and may hinder Linux or macOS users who typically use Bash.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, especially for the main cluster creation workflow.
  • Use cross-platform Azure CLI commands outside of platform-specific scripting constructs (e.g., avoid PowerShell function wrappers).
  • Explicitly mention that the Azure CLI commands can be run on Linux/macOS and provide usage notes for those platforms.
  • Add a section or callout for Linux/macOS users, highlighting any differences in command syntax or environment setup.
  • Ensure resource cleanup examples include Bash syntax (e.g., az group delete --name my-aks-cluster in Bash).
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.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 Windows bias by providing only PowerShell-based deployment scripts and examples, with no equivalent Bash or Linux shell instructions. The workflow assumes the use of PowerShell, which is native to Windows, and does not mention or prioritize Linux-compatible tooling or patterns. This may hinder Linux users or those working in cross-platform environments.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell instructions, especially for deployment and resource cleanup.
  • Explicitly mention that the Azure CLI and kubectl are cross-platform, and clarify how Linux/macOS users can adapt the steps.
  • Add notes or sections highlighting Linux-specific considerations, such as environment variable handling and script execution.
  • Ensure that client tool recommendations include Linux-friendly options and installation instructions.
  • Review the order and prominence of examples to avoid implying Windows/PowerShell as the default or preferred platform.
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
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively using Windows Server as the VM image, enabling RDP (a Windows remote access protocol) as the default connectivity method, and omitting any mention of Linux VM images or SSH connectivity. All examples and screenshots are tailored to Windows deployment and access patterns, with no Linux alternatives provided.
Recommendations
  • Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu, CentOS) in an Extended Zone.
  • Add steps for configuring SSH access (port 22) for Linux VMs, alongside or instead of RDP.
  • Present both Windows and Linux VM creation options in the 'Image' selection step, and clarify differences in administrator account setup (password vs. SSH key).
  • Provide guidance on connecting to Linux VMs using SSH clients (e.g., PuTTY, OpenSSH) in the 'Connect to virtual machine' section.
  • Ensure that security cautions and best practices address both RDP and SSH 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
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 exclusively providing PowerShell scripts for deployment and management tasks, with no equivalent Bash or Linux shell examples. The instructions and code samples assume a Windows environment, which may hinder Linux users from following the guide effectively. No mention is made of Linux-specific tools or patterns, and PowerShell is used for all CLI invocations, despite Azure CLI and kubectl being cross-platform.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell code blocks, especially for deployment and resource management steps.
  • Explicitly mention that Azure CLI and kubectl commands can be run on Linux, macOS, and Windows, and show usage in a Linux shell context.
  • Avoid using PowerShell-specific syntax (e.g., `$variable`, `Write-Output`, `catch {}`) in CLI-focused documentation, or provide alternatives.
  • Add a section or notes for Linux users, including any environment-specific considerations (e.g., authentication, environment variables).
  • Ensure that client tool recommendations (e.g., Azure Data Studio) clarify cross-platform availability and usage.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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 examples for all major steps, listing PowerShell before Azure CLI, and referencing Windows-centric tools (e.g., PowerShell, Fiddler, Postman) for REST API calls. There are no Bash or Linux shell script examples, and Linux-native tools (e.g., curl, jq) are not mentioned. The Azure CLI is only used in one step, and even there, PowerShell is given equal or greater prominence.
Recommendations
  • Add Bash/Linux shell script examples for each step, especially for creating managed identities, assigning roles, and making REST API calls (using curl/jq).
  • List Azure CLI and Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Mention Linux-native tools (curl, wget, jq) for REST API calls, not just Windows tools like PowerShell, Fiddler, and Postman.
  • Ensure parity in detail and completeness between PowerShell and CLI/Bash examples.
  • Explicitly state cross-platform compatibility and provide troubleshooting notes for Linux users 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
High 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 demonstrates Windows bias by exclusively using Windows Server as the VM image, requiring RDP for connectivity, and omitting any mention of Linux VM images or SSH access. All examples and screenshots focus on Windows-centric workflows, with no guidance for deploying or connecting to Linux VMs.
Recommendations
  • Include examples for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Add instructions for enabling SSH access (port 22) and connecting to Linux VMs using SSH clients.
  • Present both Windows and Linux options for VM images and connection methods in tables or side-by-side sections.
  • Update screenshots and step-by-step instructions to reflect Linux VM deployment and connection workflows.
  • Mention security recommendations for SSH access similar to those given for RDP.
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
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 exclusively providing PowerShell-based examples and scripts for Azure CLI usage, including a custom PowerShell function for cluster creation. There are no Bash or Linux shell equivalents, and the setup and cleanup instructions also use PowerShell syntax. This may disadvantage users on Linux or macOS, who typically use Bash or other shells.
Recommendations
  • Provide equivalent Bash shell examples for all PowerShell scripts and commands, especially for the cluster creation workflow.
  • Explicitly mention that Azure CLI commands can be run in Bash, PowerShell, or other shells, and clarify any syntax differences.
  • Avoid wrapping Azure CLI commands in PowerShell-specific functions unless a Bash alternative is also provided.
  • Add notes or sections for Linux/macOS users, including environment-specific tips (e.g., SSH key generation, environment variables).
  • Ensure that cleanup instructions include Bash syntax (e.g., using \ for line continuation in Bash, not backtick).
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: ContainerApps ...extended-zones/arc-enabled-workloads-container-apps.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 exclusively provides a PowerShell script for deploying Arc-enabled ContainerApps, with no Bash or Linux shell equivalent. The instructions and code samples assume the user is operating in a Windows environment, which may disadvantage Linux or macOS users. There is no mention of Linux-specific tools or alternative command-line patterns, and PowerShell is presented as the default and only method.
Recommendations
  • Provide equivalent Bash scripts or command-line instructions for Linux/macOS users.
  • Explicitly state that the steps can be performed on both Windows and Linux, and clarify any platform-specific requirements.
  • Where possible, use cross-platform Azure CLI commands outside of PowerShell functions, or show both PowerShell and Bash usage.
  • Add a section or note highlighting how Linux users can adapt the instructions, including any differences in environment setup or command syntax.
GitHub Create Pull Request
Extended Zones Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL ...es/extended-zones/arc-enabled-workloads-postgre-sql.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 deployment scripts and examples, with no equivalent Bash or Linux shell instructions. The use of PowerShell as the sole scripting language assumes a Windows environment, and there is no mention of Linux-specific patterns, tools, or alternative workflows. This may hinder Linux users or those working in cross-platform environments from following the guide efficiently.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, especially for deployment and cleanup steps.
  • Explicitly mention that the steps can be performed on Linux/macOS and clarify any platform-specific requirements.
  • Add notes or sections highlighting differences or additional steps for Linux users (e.g., environment variable handling, script execution).
  • Ensure that client tool recommendations include Linux-compatible options and clarify installation steps for different operating systems.
  • Consider presenting both Windows and Linux examples side by side, or defaulting to cross-platform CLI commands where possible.
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
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 strong Windows bias by providing only PowerShell-based deployment scripts and examples, with no equivalent Bash or Linux shell instructions. All code samples use PowerShell syntax, and there is no mention of Linux-specific tooling or patterns, despite the cross-platform nature of Azure CLI and Kubernetes. This may hinder Linux users or those working in non-Windows environments from following the guide efficiently.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, especially for deployment and resource management steps.
  • Explicitly mention that Azure CLI and kubectl are cross-platform, and show usage examples in both Windows (PowerShell) and Linux (Bash) environments.
  • Include notes or sections on Linux prerequisites, such as package managers (apt, yum) for installing Azure CLI, kubectl, and other tools.
  • Ensure that all commands (e.g., az group delete, az sql mi-arc list) are shown in both PowerShell and Bash syntax where differences exist.
  • Review references to client tools and clarify cross-platform support, recommending alternatives if any tool is Windows-only.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples for all major steps, including managed identity creation, role assignment, and gallery operations, while omitting equivalent Linux/bash shell examples. Windows-centric tools (PowerShell, references to Fiddler) are mentioned before or instead of cross-platform or Linux-native alternatives. The only non-Windows command-line example is a single Azure CLI snippet for image replication, but all other scripting is PowerShell-focused. There are no bash, shell, or Linux-specific instructions for users who do not use Windows.
Recommendations
  • Add bash and Azure CLI examples for all steps currently covered only by PowerShell, such as managed identity creation, role assignment, and gallery assignment.
  • Mention cross-platform tools (e.g., curl, httpie) for REST API calls alongside or before Windows-specific tools like Fiddler and PowerShell.
  • Ensure that scripting instructions are presented in a platform-neutral order (e.g., Azure CLI/bash first, then PowerShell), or provide tabs for both environments.
  • Explicitly state that all steps can be performed from Linux/macOS environments and provide guidance for those platforms.
  • Review terminology and tool recommendations to avoid assuming a Windows environment (e.g., avoid referencing Windows-only tools unless alternatives are also provided).
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-vm-portal.md .../blob/main/articles/extended-zones/deploy-vm-portal.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 demonstrates Windows bias by exclusively providing instructions for deploying a Windows Server VM (specifically 'Windows Server 2022 Datacenter: Azure Edition'), enabling RDP (Remote Desktop Protocol) for access, and omitting any mention of Linux VM images or SSH connectivity. All connection instructions focus on RDP, a Windows-centric tool, with no guidance for Linux users or alternatives.
Recommendations
  • Include examples for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Provide instructions for configuring SSH access to Linux VMs, including opening port 22 and connecting via SSH clients.
  • Mention Linux images in the 'Image' selection step and clarify that users can choose either Windows or Linux OS.
  • Add screenshots and step-by-step guidance for Linux VM deployment and SSH connection.
  • Note differences in administrator account setup for Linux (username, SSH key) versus Windows (username, password).
  • Ensure connection instructions cover both RDP (for Windows) and SSH (for Linux), with security recommendations for each.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-arc-enabled-aks-cluster.md ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.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 exclusively providing PowerShell-based examples and scripts for Azure CLI usage. There are no Bash or Linux shell equivalents, and the scripting patterns (e.g., function definitions, parameter passing) are tailored to PowerShell, which is native to Windows. This may hinder Linux users, who typically use Bash or other shells, from following the instructions seamlessly.
Recommendations
  • Provide equivalent Bash shell examples for all PowerShell scripts, especially for Azure CLI commands, as Azure CLI is cross-platform.
  • Include notes or sections clarifying that the instructions are applicable to both Windows and Linux, and specify any platform-specific considerations.
  • Avoid using PowerShell-specific constructs (such as function definitions and parameter passing) in generic Azure CLI documentation, or offer parallel Bash alternatives.
  • Ensure that cleanup and setup commands are shown in both PowerShell and Bash syntax.
  • Consider listing Bash examples first or side-by-side with PowerShell to signal equal support for Linux users.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-container-apps.md ...extended-zones/arc-enabled-workloads-container-apps.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 provides only PowerShell-based examples and scripts for deploying Arc-enabled ContainerApps in Extended Zones. There are no equivalent Bash or Linux shell instructions, and the scripting approach assumes a Windows environment by default. This may disadvantage Linux or cross-platform users, as PowerShell is not the default shell on most Linux systems and some commands (e.g., Write-Debug, Start-Sleep, parameter passing) are PowerShell-specific.
Recommendations
  • Provide equivalent Bash shell scripts and examples for all deployment steps, using standard Linux tools and syntax.
  • Explicitly mention cross-platform compatibility for Azure CLI commands, and clarify which steps are OS-agnostic.
  • If PowerShell is required, note how to install and use PowerShell Core on Linux, or offer alternatives.
  • Reorder examples so that Bash/Linux instructions are presented first or alongside PowerShell, to avoid Windows-first bias.
  • Add notes or links to official Azure CLI documentation for Linux users, highlighting any differences in usage.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-postgre-sql.md ...es/extended-zones/arc-enabled-workloads-postgre-sql.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 only a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The use of PowerShell as the sole scripting language and the lack of explicit Linux/macOS instructions or examples indicate a Windows-first and PowerShell-heavy bias. This may hinder Linux users, who are common in Kubernetes and cloud-native environments.
Recommendations
  • Provide equivalent Bash shell scripts or step-by-step CLI commands for Linux/macOS users alongside the PowerShell example.
  • Explicitly mention that the process can be performed on Linux/macOS, and clarify any OS-specific prerequisites or differences.
  • Where possible, use cross-platform scripting (e.g., plain Azure CLI commands) instead of PowerShell functions for core deployment steps.
  • Include notes or links to resources for running Azure CLI and kubectl on Linux/macOS.
  • Ensure that all code snippets and automation examples are available in both PowerShell and Bash to support a wider range of users.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/replicate-azure-compute-gallery.md ...cles/extended-zones/replicate-azure-compute-gallery.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 examples for all major steps, listing PowerShell before Azure CLI, and referencing Windows-centric tools (e.g., PowerShell, Fiddler, Postman) for REST API calls. There are no Bash or Linux shell examples for creating managed identities, assigning roles, or making REST API calls. The Azure CLI is only used for the final replication step, and even there, the PowerShell example is more detailed. No Linux-specific guidance or parity is provided.
Recommendations
  • Add Bash/Linux shell examples for all steps currently covered by PowerShell, including managed identity creation, role assignment, and REST API PATCH calls (using curl or az rest).
  • List Azure CLI and Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Reference cross-platform tools for REST API calls, such as curl or httpie, in addition to or instead of Windows-centric tools like Fiddler and Postman.
  • Ensure all code snippets have equivalent Azure CLI or Bash versions, and clearly indicate platform-neutral approaches.
  • Add notes or sections specifically addressing Linux/macOS users, including troubleshooting and environment setup tips.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-managed-sql.md ...es/extended-zones/arc-enabled-workloads-managed-sql.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 exclusively providing PowerShell scripts for deployment and management tasks, without offering equivalent Bash or shell examples for Linux/macOS users. The use of PowerShell is assumed throughout, and there is no mention of Linux-specific patterns, tools, or alternative workflows. This may hinder accessibility and usability for administrators working in non-Windows environments.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell commands, especially for deployment and resource management steps.
  • Explicitly mention cross-platform compatibility of Azure CLI commands and clarify which steps are OS-agnostic.
  • Add notes or sections highlighting any OS-specific considerations, such as environment variable handling or script execution.
  • Ensure that Linux tools and workflows (e.g., bash, sh, zsh) are referenced alongside Windows/PowerShell options.
  • Consider reordering examples or providing tabs for Windows (PowerShell) and Linux/macOS (Bash) to improve parity and user experience.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-container-apps.md ...extended-zones/arc-enabled-workloads-container-apps.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 exclusively provides a PowerShell script for deploying Arc-enabled ContainerApps in an Extended Zone, with no equivalent Bash or Linux shell example. The use of PowerShell as the only scripting language and the absence of Linux-specific instructions or parity signals a Windows-first and PowerShell-heavy bias. This may hinder accessibility for Linux or macOS users, who are more likely to use Bash or other Unix shells.
Recommendations
  • Provide a Bash (or generic shell) equivalent script for all deployment steps, especially for users on Linux or macOS.
  • Explicitly mention cross-platform compatibility for the Azure CLI commands and clarify which steps are OS-agnostic.
  • Add notes or sections highlighting any differences or requirements for Linux users, such as environment setup or command syntax.
  • Consider listing both Windows and Linux examples side-by-side, or defaulting to Bash for CLI-based workflows unless PowerShell-specific features are required.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-postgre-sql.md ...es/extended-zones/arc-enabled-workloads-postgre-sql.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 exclusively provides a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, without offering equivalent Bash or Linux shell examples. All scripting and automation guidance is Windows-centric, implicitly prioritizing Windows environments and tools. No Linux-specific instructions or parity examples are present.
Recommendations
  • Provide a Bash (Linux shell) equivalent script for the entire deployment workflow, using standard Bash syntax and environment variable handling.
  • Explicitly mention that the process can be performed on Linux/macOS, and provide any OS-specific prerequisites or notes.
  • Where possible, use cross-platform scripting (e.g., Azure CLI commands in Bash) in the main documentation, or present both PowerShell and Bash examples side-by-side.
  • Clarify that Azure CLI and kubectl are cross-platform, and show their usage in a Linux context.
  • Avoid assuming PowerShell as the default scripting environment; instead, offer both Windows and Linux automation options.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-vm-portal.md .../blob/main/articles/extended-zones/deploy-vm-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions for deploying a Windows Server VM, using RDP for remote access, and omitting any mention of Linux images or SSH connectivity. All examples and screenshots focus on Windows-centric workflows, with no guidance for Linux users or alternative connection methods.
Recommendations
  • Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu, CentOS) in an Extended Zone.
  • Provide examples for configuring SSH access (port 22) alongside RDP, including guidance on generating SSH keys and connecting via SSH from Linux/macOS/Windows.
  • Mention Linux images as options in the 'Image' selection step, and clarify differences in administrator account setup for Linux VMs.
  • Add notes or sections highlighting platform-specific steps, ensuring parity for both Windows and Linux users.
  • Where RDP is discussed, also discuss SSH as a secure and common alternative for Linux VMs.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/replicate-azure-compute-gallery.md ...cles/extended-zones/replicate-azure-compute-gallery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 examples for all major steps, referencing Windows-centric tools (PowerShell, Fiddler), and omitting equivalent Linux/bash examples. The PowerShell tab is present for every code sample, while Linux/bash alternatives are missing except for a single Azure CLI snippet. Windows tools are mentioned for REST API calls, and the scripting guidance is primarily in PowerShell, which is native to Windows. There is no mention of Linux-specific workflows or tools, nor are bash or shell commands provided for key steps.
Recommendations
  • Add bash or shell script examples for all steps currently covered only by PowerShell, especially for creating managed identities, assigning roles, and making REST API calls.
  • Include instructions for using Linux-native tools (e.g., curl, jq) for REST API PATCH operations, alongside Postman and Fiddler.
  • Ensure Azure CLI examples are provided for every major operation, not just image replication.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
  • Reorder examples so that platform-neutral (Azure CLI) or Linux/bash examples are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-managed-sql.md ...es/extended-zones/arc-enabled-workloads-managed-sql.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 demonstrates a Windows bias by providing only PowerShell-based deployment scripts and examples, with no equivalent Bash or Linux shell instructions. All command-line examples use PowerShell syntax, and there is no mention of Linux-specific tools, shell environments, or alternative workflows for non-Windows users. This may hinder accessibility for administrators working primarily on Linux or macOS systems.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell scripts, especially for deployment and resource management steps.
  • Explicitly mention that the Azure CLI and kubectl commands are cross-platform, and show examples in both Windows (PowerShell) and Linux/macOS (Bash).
  • Add notes or sections highlighting any platform-specific considerations, such as environment variable handling or script execution differences.
  • Ensure that client tool recommendations include Linux-compatible options and clarify installation steps for Linux environments.
  • Consider reordering examples or providing parallel instructions so that Linux/Bash usage is not secondary to Windows/PowerShell.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-arc-enabled-aks-cluster.md ...zones/arc-enabled-workloads-arc-enabled-aks-cluster.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 demonstrates a Windows bias by exclusively providing PowerShell-based examples and scripts for Azure CLI operations, without offering equivalent Bash or shell examples for Linux/macOS users. The use of PowerShell functions and syntax (e.g., param blocks, Write-Output, backticks for line continuation) presumes a Windows environment and may be unfamiliar or incompatible with Linux-based workflows. No Linux-specific instructions, shell scripts, or alternative command-line examples are provided.
Recommendations
  • Provide Bash/sh examples alongside PowerShell scripts for all Azure CLI commands and workflows.
  • Use cross-platform syntax for Azure CLI commands, avoiding PowerShell-specific constructs (e.g., function definitions, param blocks, Write-Output).
  • Explicitly mention that Azure CLI is available on Linux/macOS and provide installation instructions for those platforms.
  • Include notes or sections highlighting any platform-specific considerations or differences.
  • Ensure resource cleanup examples are shown in both PowerShell and Bash formats.
GitHub Create Pull Request
Extended Zones https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/arc-enabled-workloads-container-apps.md ...extended-zones/arc-enabled-workloads-container-apps.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →