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 26-50 of 52 flagged pages
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
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 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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
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 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.
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 →
Detected Bias Types
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.
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 →
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, which is native to Windows. There are no Bash or Linux/macOS shell equivalents, and the use of PowerShell functions for automation may be unfamiliar or unusable for Linux/macOS users. The Azure CLI commands themselves are cross-platform, but their presentation and scripting context are Windows-centric.
Recommendations
- Provide equivalent Bash shell examples for all PowerShell scripts and command snippets.
- Include notes clarifying that Azure CLI is cross-platform and can be used on Linux/macOS terminals.
- Offer downloadable sample scripts for both PowerShell (.ps1) and Bash (.sh) to accommodate all users.
- Reorder examples or alternate between Windows and Linux/macOS first to avoid implicit prioritization.
Extended Zones
Deploy Arc-enabled workloads in an Extended Zone: ContainerApps
...extended-zones/arc-enabled-workloads-container-apps.md
Medium Priority
View Details →
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 equivalent Bash or Linux shell examples. This creates friction for Linux/macOS users, who must translate the script themselves. The use of PowerShell-specific syntax and patterns (e.g., parameter blocks, Write-Debug, Start-Sleep) further reinforces a Windows-centric approach.
Recommendations
- Provide a Bash (or cross-platform shell) script example alongside the PowerShell script, using standard shell syntax and tools.
- Explicitly mention that the steps can be performed on Linux/macOS and provide guidance for adapting the automation.
- Highlight any platform-specific requirements or differences, such as az CLI installation steps for Linux/macOS.
- Avoid using PowerShell-only constructs (e.g., parameter blocks, Write-Debug) in generic automation, or offer alternatives.
Extended Zones
Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL
...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only PowerShell-based automation for deploying Arc-enabled PostgreSQL in Extended Zones, with no equivalent Bash or Linux shell examples. All scripting and resource cleanup instructions use PowerShell syntax, which is native to Windows and not standard on Linux/macOS. This creates friction for non-Windows users, who must adapt or rewrite scripts to use Bash or other shells.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell examples, especially for deployment and cleanup steps.
- Clearly indicate cross-platform compatibility for all CLI commands and scripts.
- Add notes or sections for Linux/macOS users, including installation and usage tips for required tools.
- Consider using platform-agnostic scripting (e.g., pure Azure CLI commands in Bash) as the primary example, with PowerShell as an alternative.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for all major steps and references Windows-centric tools (PowerShell, Fiddler, Postman) for REST API calls. Azure CLI is only briefly mentioned for the final replication step, and there are no Bash, Linux shell, or REST API curl examples. The ordering and depth of PowerShell instructions suggest a Windows-first approach, with Linux/macOS users left to infer or adapt steps.
Recommendations
- Add Bash/curl examples for REST API PATCH operations, showing how to assign managed identities using standard Linux tools.
- Expand Azure CLI coverage to all steps, not just the final replication, including managed identity creation and role assignment.
- Explicitly mention cross-platform compatibility for all scripts and clarify which commands work on Linux/macOS.
- Reorder examples so that Azure CLI (cross-platform) instructions appear before PowerShell, or present both side-by-side.
- Reference Linux/macOS tools (e.g., curl, jq) alongside Windows tools like PowerShell and Fiddler.
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 →
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 (Windows Remote Desktop Protocol) as the only connection method, and omitting any mention of Linux VM images or SSH connectivity. All examples and screenshots are tailored to Windows, with no guidance for deploying or accessing Linux VMs.
Recommendations
- Include instructions for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
- Provide SSH connection steps for Linux VMs, including how to configure public inbound ports for SSH (port 22).
- Add screenshots and portal field values relevant to Linux VM creation and access.
- Mention security best practices for SSH, similar to the RDP caution.
- Clarify that users can choose either Windows or Linux images and provide parity in documentation for both.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides only a Windows VM deployment example, with no mention or example of deploying a Linux VM. This creates a bias towards Windows, as Linux users do not see their use case represented, and may be unsure how to specify a Linux image in the Azure CLI context.
Recommendations
- Add a Linux VM deployment example (e.g., using Ubuntu or CentOS) alongside the Windows example.
- Explicitly mention that both Windows and Linux images are supported, and provide guidance on how to find available Linux images.
- Consider alternating or balancing the order of examples so that Linux is not always secondary.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides PowerShell scripts and command examples, which are native to Windows and not directly usable on Linux/macOS. There are no Bash or shell script equivalents, nor any mention of how to adapt the instructions for non-Windows environments. This creates friction for Linux/macOS users, who are likely to use Bash or other shells and may not have PowerShell installed.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for Azure CLI commands which are cross-platform.
- Explicitly state platform compatibility for scripts and commands, and offer installation guidance for PowerShell on Linux/macOS if needed.
- Reorder examples so that cross-platform Azure CLI commands are shown first, followed by optional PowerShell or Bash scripts.
- Include notes or sections highlighting any platform-specific considerations or differences.
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 →
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, only enabling RDP (a Windows protocol) for remote access, and omitting any mention of Linux VM images or SSH connectivity. All examples and screenshots are tailored to Windows, with no guidance for Linux/macOS users.
Recommendations
- Include instructions for deploying a Linux VM image (e.g., Ubuntu, CentOS) alongside the Windows example.
- Provide steps for enabling SSH access (port 22) and connecting via SSH from Linux/macOS terminals.
- Add screenshots and example values for Linux VM creation and connection.
- Mention cross-platform tools (e.g., Azure CLI, SSH clients) and clarify that the Azure portal supports both Windows and Linux VM deployments.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only a Windows Server VM deployment example and does not mention or show how to deploy a Linux VM. There is no reference to Linux images or any Linux-specific considerations, which may lead Linux users to feel unsupported or uncertain about how to adapt the instructions.
Recommendations
- Include an example command for deploying a popular Linux VM image (e.g., Ubuntu, CentOS) in an Extended Zone.
- Add a note clarifying that the process is identical for Linux VMs, and provide a link to the list of available Linux images.
- Consider alternating or pairing Windows and Linux examples to demonstrate parity.
- Explicitly mention that both Windows and Linux VMs are supported in Extended Zones, if applicable.
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 →
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 in PowerShell syntax, including a full PowerShell function for cluster creation and resource management. No Bash or Linux/macOS shell examples are given, despite the Azure CLI being cross-platform. This may create friction for Linux and macOS users who are unfamiliar with PowerShell or prefer Bash.
Recommendations
- Provide equivalent Bash shell examples for all Azure CLI commands and scripts.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, Zsh, or other shells.
- Avoid wrapping Azure CLI commands in PowerShell-specific functions unless necessary; use plain CLI commands for broader compatibility.
- Explicitly mention platform compatibility and provide guidance for Linux/macOS users where appropriate.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell-based scripts and examples for deploying Arc-enabled Managed SQL Instances. There are no Bash or Linux shell equivalents, and all command-line instructions are shown in PowerShell syntax, 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 scripts for all PowerShell examples, especially for the main deployment workflow.
- Explicitly mention cross-platform compatibility for Azure CLI commands and clarify which steps are OS-agnostic.
- Add notes or sections highlighting any OS-specific considerations, such as environment variable handling.
- Show both PowerShell and Bash command snippets side by side where possible.
- Avoid using PowerShell-specific constructs (e.g., `$ENV:`, `Write-Output`, `catch {}`) in generic CLI instructions, or provide alternatives.
Extended Zones
Deploy Arc-enabled workloads in an Extended Zone: ContainerApps
...extended-zones/arc-enabled-workloads-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only a PowerShell script for deploying Arc-enabled ContainerApps, with no Bash, Linux shell, or cross-platform alternatives. All automation and scripting guidance is Windows-centric, and the cleanup example also uses PowerShell syntax. This creates friction for Linux/macOS users, who must translate or adapt the instructions themselves.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell examples, especially for deployment steps.
- Explicitly mention that Azure CLI commands work cross-platform and show examples in Bash where possible.
- Add notes or sections clarifying how Linux/macOS users can perform the same steps, including any OS-specific considerations.
- Use generic Azure CLI commands in documentation, avoiding OS-specific scripting unless necessary.
- If PowerShell is required, explain why and offer alternatives or conversion guidance.
Extended Zones
Deploy Arc-enabled workloads in an Extended Zone: PostgreSQL
...es/extended-zones/arc-enabled-workloads-postgre-sql.md
Medium Priority
View Details →
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 equivalent Bash or Linux/macOS shell instructions, and the workflow assumes use of Windows-centric tooling and scripting patterns. This creates friction for Linux and macOS users, who must adapt or rewrite the procedures for their environments.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for the main deployment workflow.
- 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 environment setup and script adaptation tips.
- List both Windows and Linux client tools in prerequisites, and link to installation instructions for each platform.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Most command-line examples are provided in PowerShell, with no Bash or Linux shell equivalents for critical steps such as creating managed identities, assigning roles, and making REST API calls. While Azure CLI is briefly mentioned for the final image replication step, the majority of scripting guidance is Windows-centric. Tools like Postman and Fiddler are referenced for REST calls, but Linux-native alternatives (e.g., curl) are not mentioned. This bias may create friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
- Provide Bash/Azure CLI examples for all steps, especially for creating managed identities and assigning roles.
- Include Linux/macOS-friendly instructions for REST API calls (e.g., using curl or httpie).
- Mention Linux-native tools alongside Postman/Fiddler for REST API operations.
- Ensure parity in example ordering: present Azure CLI/Bash examples before or alongside PowerShell.
- Add notes clarifying that all steps can be performed on Linux/macOS, and link to relevant cross-platform documentation.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only a Windows Server VM deployment example, with no mention of Linux images or Linux-specific deployment patterns. This may lead users to assume Windows is the preferred or only supported OS for Extended Zone VM deployments.
Recommendations
- Add an example deploying a popular Linux VM image (e.g., UbuntuLTS) alongside the Windows example.
- Explicitly mention that both Windows and Linux images are supported in Extended Zones.
- Where possible, alternate the order of examples or provide both Windows and Linux options in code blocks.
- Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations if they exist.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a Windows Server 2022 deployment example, without mentioning or showing how to deploy a Linux VM. There are no Linux image references or examples, and the only OS-specific example is Windows. This may lead Linux users to feel unsupported or unclear about how to use the Azure CLI for Linux VM deployment in Extended Zones.
Recommendations
- Add a Linux VM deployment example alongside the Windows example, such as using the UbuntuLTS image.
- Explicitly mention that both Windows and Linux images are supported and provide guidance on selecting Linux images.
- Ensure that documentation covers common Linux scenarios and tools where relevant, not just Windows-centric workflows.
- Consider alternating or balancing examples between Windows and Linux to avoid implicit prioritization.
Extended Zones
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/extended-zones/deploy-vm-cli.md
...ocs/blob/main/articles/extended-zones/deploy-vm-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only a Windows Server deployment example and does not mention or demonstrate how to deploy a Linux VM in an Extended Zone. The example uses the Windows Server 2022 Datacenter image exclusively, with no reference to Linux images or Linux-specific considerations. There is no evidence of Powershell-specific commands or Windows-only tools, but the example is Windows-centric.
Recommendations
- Include a parallel example for deploying a popular Linux VM image (e.g., UbuntuLTS) in an Extended Zone.
- Add notes or guidance for selecting Linux images and any Linux-specific configuration steps if applicable.
- Ensure that examples and instructions are balanced between Windows and Linux to reflect common cross-platform usage.
- Explicitly mention that the process is identical for Linux images unless there are differences, and provide links to Linux VM documentation if relevant.