Azure Vmware

153
Total Pages
96
Linux-Friendly Pages
57
Pages with Bias
37.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

412 issues found
Showing 151-175 of 412 flagged pages
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-vsan.md ...docs/blob/main/articles/azure-vmware/configure-vsan.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 cmdlet-based instructions for configuring VMware vSAN features, with no equivalent Linux CLI or automation examples. Windows prerequisites are mentioned before Linux, and the workflow assumes use of the Azure portal and PowerShell commands, which are more familiar to Windows administrators. There is no guidance for Linux users on how to perform these tasks using native Linux tools or automation frameworks.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using VMware's CLI tools or REST APIs) for each configuration task.
  • Include instructions for automating these tasks from Linux environments, such as using Bash scripts or Ansible modules.
  • List Linux prerequisites alongside Windows, and avoid mentioning Windows first unless there is a technical reason.
  • Clarify whether the cmdlets can be run from Linux via PowerShell Core, or offer alternative methods for Linux-only environments.
  • Add links to VMware documentation that specifically addresses Linux workflows for vSAN management.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/includes/vcenter-access-identity-description.md ...vmware/includes/vcenter-access-identity-description.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently references Windows Server Active Directory as the primary or sole identity source for assigning the CloudAdmin role in vCenter Server. There are no examples or mentions of Linux-based identity sources (such as OpenLDAP), nor is there guidance for integrating with non-Windows environments. Windows terminology and tools are introduced before any alternatives, and Linux parity is not addressed.
Recommendations
  • Add examples and instructions for integrating Linux-based identity sources (e.g., OpenLDAP) with vCenter Server.
  • Mention and document how non-Windows environments can assign roles and manage access, including any limitations or requirements.
  • Provide parity in documentation by listing both Windows and Linux options for identity management, ideally with step-by-step guidance for each.
  • Clarify whether the CloudAdmin role can be assigned to users/groups from non-Windows directories and, if so, how to configure this.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/migrate-sql-server-always-on-availability-group.md ...are/migrate-sql-server-always-on-availability-group.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 is heavily focused on Windows Server and Microsoft SQL Server Always On Availability Groups, with all examples, configuration steps, and references centered around Windows-based tools and patterns (e.g., Windows Server Failover Cluster, SQL Server Management Studio). There are no Linux equivalents or cross-platform alternatives mentioned, and all guidance assumes a Windows environment for both the database and clustering technologies.
Recommendations
  • Explicitly state that the guidance applies only to Windows-based SQL Server deployments, or clarify platform limitations.
  • If Linux-based SQL Server Always On Availability Groups are supported in Azure VMware Solution, add equivalent migration steps, prerequisites, and tooling for Linux environments (e.g., Pacemaker clusters, Linux SQL Server tools).
  • Include references to Linux documentation and best practices for SQL Server clustering and migration.
  • Provide a comparison table or section outlining differences and considerations for Windows vs. Linux SQL Server deployments in Azure VMware Solution.
  • Mention alternative management tools (e.g., Azure Data Studio, sqlcmd) that are cross-platform, in addition to SSMS.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-arc-for-azure-vmware-solution.md ...s/azure-vmware/deploy-arc-for-azure-vmware-solution.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. While both Windows and Linux deployment examples are provided for running the onboarding script, the Windows/PowerShell example is presented first and in more detail, including explicit instructions about execution policy. Windows file paths (e.g., C:\Users\sampleUser.sslProxy.crt) are used in JSON examples, and references to Windows tools (PowerShell, Set-ExecutionPolicy) are more prominent. There is little mention of Linux-specific considerations, and Linux instructions are less detailed. Some configuration examples (such as certificateFilePath) use only Windows-style paths, and there are no explicit Linux path examples.
Recommendations
  • Present Windows and Linux instructions with equal prominence, alternating which comes first or presenting them side-by-side.
  • Include Linux-style file paths (e.g., /home/sampleUser/sslProxy.crt) in configuration examples, or show both Windows and Linux variants.
  • Provide Linux-specific details where relevant, such as common shell environments, permission requirements, or troubleshooting tips.
  • Avoid assuming PowerShell as the default scripting environment; clarify when Bash or other shells are supported.
  • Ensure that all steps and examples are equally detailed for both platforms, including prerequisites and troubleshooting.
  • Explicitly state that both Windows and Linux management VMs are supported at the start of the onboarding section.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-zerto-disaster-recovery.md ...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. The Zerto Cloud Appliance (ZCA) is described as a Windows-only VM, and its components (ZVM and VRA) are noted as Windows services. There are no Linux equivalents or alternatives mentioned for ZCA, nor are any Linux-based deployment or operational examples provided for scenarios involving Azure IaaS VMs. Windows tools and patterns are referenced before Linux ones in the context of cloud recovery, and practical instructions/examples for Linux users are missing.
Recommendations
  • Add explicit Linux-based deployment instructions or examples for Zerto components where possible, especially for cloud recovery scenarios.
  • Clarify whether any Zerto components (such as ZCA) have Linux alternatives or if future support is planned.
  • Provide parity in operational guidance, such as log collection, troubleshooting, and upgrades, for both Windows and Linux environments.
  • Include references to Linux tools or commands where relevant, and ensure that prerequisites and installation steps are not Windows-centric.
  • If Windows-only components are required, explain the rationale and offer guidance for Linux users on integration or interoperability.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/install-cloud-backup-virtual-machines.md .../azure-vmware/install-cloud-backup-virtual-machines.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 a Windows bias by exclusively referencing Windows-centric tools and workflows, such as the Azure portal 'Run command' interface and PowerShell-like command naming conventions (e.g., Install-NetAppCBSA, Invoke-UpgradeNetAppCBSAppliance). There are no Linux CLI, shell, or automation examples, nor any mention of Linux-native tools or procedures for installation, upgrade, or backup. The documentation assumes users interact primarily through graphical interfaces or Windows-style commands, with no parity for Linux administrators.
Recommendations
  • Provide equivalent Linux CLI instructions (e.g., Azure CLI, Bash scripts) for installing, upgrading, and uninstalling the Cloud Backup for Virtual Machines plug-in.
  • Include examples of how to automate these tasks using Linux tools (such as shell scripts or Ansible) and document any required permissions or dependencies.
  • Clarify whether the 'Run command' interface is accessible or usable from Linux environments, and if so, provide step-by-step guidance.
  • Mention Linux-specific considerations for VM backup, MySQL database backup, and vSphere client access, including any differences in authentication or file paths.
  • Ensure that all command-line examples are provided for both Windows (PowerShell) and Linux (Bash/CLI) users, with clear labeling.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/migrate-sql-server-standalone-cluster.md .../azure-vmware/migrate-sql-server-standalone-cluster.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 is heavily focused on Windows environments, specifically Windows Server and Microsoft SQL Server. All tested configurations, prerequisites, and migration steps assume Windows as the operating system, with no mention of Linux-based SQL Server deployments or tools. Examples and validation steps reference Windows-only tools (e.g., SQL Server Management Studio), and all best practices and references are for Windows Server. There is no guidance for Linux SQL Server instances or parity in migration procedures.
Recommendations
  • Include tested configurations and migration steps for SQL Server running on Linux (e.g., Ubuntu, Red Hat).
  • Provide Linux-specific prerequisites, such as backup procedures, network configuration, and VM preparation steps.
  • Add examples using Linux tools (e.g., sqlcmd, Azure Data Studio) for post-migration validation.
  • Reference Linux SQL Server documentation and best practices alongside Windows resources.
  • Clarify whether VMware HCX migration steps differ for Linux-based SQL Server VMs and provide guidance if so.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/integrate-azure-native-services.md ...ticles/azure-vmware/integrate-azure-native-services.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric monitoring features (such as registry and file monitoring), mentioning Windows services before Linux daemons, and omitting concrete Linux-specific examples or commands except for a brief sudoers configuration. There is a lack of parity in practical Linux guidance, with no Linux extension installation walkthrough or troubleshooting tips, while Windows patterns and terminology are more prevalent.
Recommendations
  • Add explicit Linux extension installation steps, including screenshots or terminal commands for common distributions.
  • Provide Linux-specific monitoring examples, such as collecting syslog, journald, or daemon status, and clarify how Log Analytics agent interacts with Linux systems.
  • List Linux daemons and configuration files monitored, similar to the Windows registry and files mentioned.
  • Balance the order of mention between Windows and Linux features, ensuring Linux is not always secondary.
  • Include troubleshooting steps and prerequisites for Linux environments, such as SELinux/AppArmor considerations, package dependencies, and network requirements.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md ...led-azure-vmware-solution-vsphere-resources-from-azure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation presents Windows uninstall instructions before Linux, and uses Windows-specific tools (Control Panel, Programs and Features) for agent removal. The Linux instructions are provided, but Windows steps are listed first and in greater detail, with graphical interface steps. No PowerShell commands are given, but the overall pattern prioritizes Windows workflows and tools.
Recommendations
  • Present Linux and Windows uninstall instructions in parallel or start with Linux to avoid implicit prioritization.
  • Provide equivalent graphical and command-line instructions for Linux agent removal, such as using GNOME Software or KDE Discover for uninstalling packages.
  • Include more detailed Linux steps, such as verifying removal and cleaning up residual files, similar to the Windows folder deletion step.
  • Explicitly state that both Windows and Linux are supported and ensure parity in example depth and clarity.
  • If PowerShell or Windows tools are mentioned, provide Bash or Linux-native alternatives wherever possible.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/manage-arc-enabled-azure-vmware-solution.md ...ure-vmware/manage-arc-enabled-azure-vmware-solution.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows-based Management VM instructions before Linux equivalents, and by using command patterns (e.g., virtual environment activation) that are more familiar to Windows users. Linux instructions are present but less emphasized, and there is a lack of explicit Linux command examples for some steps. No Linux-specific troubleshooting or tool references are provided, and the overall flow assumes familiarity with Windows environments.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
  • Provide explicit Linux command examples for all steps, including troubleshooting and environment setup.
  • Reference Linux-native tools (e.g., bash, SSH, file permissions) where appropriate.
  • Include notes about differences in file paths, environment activation, and permissions between Windows and Linux.
  • Ensure parity in example coverage, so Linux users have clear, actionable guidance for each step.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/migrate-sql-server-failover-cluster.md ...es/azure-vmware/migrate-sql-server-failover-cluster.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 is heavily focused on Windows Server Failover Clustering and SQL Server on Windows, with all examples and procedures referencing Windows Server, Windows Failover Cluster Manager, and SQL Server Management Studio. There are no mentions of Linux-based SQL Server deployments, Linux clustering tools, or migration procedures for non-Windows environments. All tooling and screenshots are Windows-specific, and references to best practices and documentation are exclusively for Windows Server and Windows clustering.
Recommendations
  • Include guidance for migrating SQL Server Failover Cluster Instances running on Linux (e.g., using Pacemaker or other Linux clustering solutions).
  • Provide examples and screenshots for Linux-based SQL Server deployments, including relevant tools and commands (e.g., systemctl, pcs, SQL Server on Linux management tools).
  • Reference Linux documentation and best practices for SQL Server clustering and migration.
  • Clarify in prerequisites and migration steps whether the procedures are Windows-only or provide parallel steps for Linux environments.
  • Add notes or sections addressing differences and considerations for Linux-based clusters, including networking, storage, and failover mechanisms.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/sql-server-hybrid-benefit.md ...ain/articles/azure-vmware/sql-server-hybrid-benefit.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, while mentioning Linux subscriptions in the title and description, focuses almost exclusively on Windows Server and SQL Server scenarios. All examples, migration guides, and feature descriptions are centered on Microsoft SQL Server and Windows Server, with no Linux-specific examples, migration paths, or tooling mentioned. Windows tools and patterns (e.g., Windows Server Failover Cluster) are referenced, while Linux equivalents are absent.
Recommendations
  • Add concrete examples and guidance for using Azure Hybrid Benefit with Linux subscriptions, including supported distributions and scenarios.
  • Include migration guides for common Linux workloads (e.g., migrating Linux VMs, Linux-based databases) to Azure VMware Solution.
  • Reference Linux-native clustering and high availability solutions (e.g., Pacemaker, Corosync) alongside Windows Server Failover Cluster.
  • Ensure parity in documentation structure by providing Linux-focused 'Next steps' links and walkthroughs.
  • Clarify any differences in licensing, eligibility, and technical implementation for Linux users.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/use-hcx-run-commands.md ...lob/main/articles/azure-vmware/use-hcx-run-commands.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 Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes the use of VMware HCX Run Commands via PowerShell-style cmdlets and the Azure portal, with all command examples and terminology centered around Windows/PowerShell conventions. There is no mention of Linux equivalents, CLI alternatives, or cross-platform usage. The documentation assumes familiarity with Windows tools and patterns, and does not provide guidance for Linux users or administrators who may prefer bash, shell scripting, or other non-Windows interfaces.
Recommendations
  • Add equivalent Linux/bash command examples for each operation, if available.
  • Clarify whether the Run Commands can be executed via Azure CLI, REST API, or other cross-platform tools, and provide examples.
  • Include a section on prerequisites and platform compatibility, explicitly stating whether Linux users can perform these tasks and how.
  • Avoid using only PowerShell cmdlet syntax; provide generic command syntax or alternatives where possible.
  • Mention any limitations or differences when using these commands from Linux or macOS environments.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/restore-guest-files-folders.md ...n/articles/azure-vmware/restore-guest-files-folders.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 is heavily biased towards Windows environments. All instructions, examples, and credential requirements are specific to Windows guest OS, with explicit statements that Linux guest OS is not supported for file/folder restore. Windows tools and patterns (such as UNC paths, administrator account requirements, and NTFS/FAT file system notes) are mentioned exclusively, with no Linux equivalents or guidance. Linux users are only told to manually restore files after attaching a VMDK, with no further detail or parity in workflow.
Recommendations
  • Add explicit support or guidance for Linux guest OS restores, including step-by-step instructions for manual file recovery after VMDK attachment.
  • Provide Linux-specific examples for credential configuration, file system handling, and restore paths (e.g., mount points, permissions).
  • Clarify limitations and offer alternative workflows for Linux users, such as using Linux tools (mount, cp, rsync) to access and restore files from attached VMDKs.
  • If Linux guest OS restore is not supported, document a roadmap or workaround for Linux environments, and ensure parity in documentation structure and detail.
  • Include a comparison table of Windows and Linux restore capabilities, highlighting differences and available options for each platform.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/protect-azure-vmware-solution-with-application-gateway.md ...protect-azure-vmware-solution-with-application-gateway.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 clear Windows bias in its configuration examples. All backend VM setup instructions use Windows Server 2016 and IIS, with PowerShell commands provided exclusively for web server configuration. There are no examples or instructions for deploying Linux-based web servers (such as Apache or Nginx) or using Linux command-line tools. The use of Windows-specific tooling (PowerShell, IIS) is presented as the default and only option, with no mention of Linux alternatives.
Recommendations
  • Add parallel examples for Linux-based web servers (e.g., Ubuntu with Apache or Nginx) including setup and configuration commands.
  • Provide Bash shell commands for Linux VM configuration, such as installing Apache/Nginx and creating test pages.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend pools.
  • Include screenshots or walkthroughs using Linux VMs in VMware vSphere Client, not just Windows Server.
  • Avoid language that implies Windows is the default or only supported backend; present Windows and Linux options side-by-side.
  • Reference documentation for Linux web server setup in the 'Next Steps' or prerequisites section.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/set-up-backup-server-for-azure-vmware-solution.md ...ware/set-up-backup-server-for-azure-vmware-solution.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. It exclusively describes deploying Azure Backup Server on Windows Server, references only Windows VM creation and disk attachment guides, and provides Windows-specific instructions and tooling (e.g., PowerShell, ReFS, VSS, Windows Update). There are no Linux deployment examples, nor are Linux-specific patterns or requirements discussed beyond a brief mention of pre/post scripts for application-consistent backups. All step-by-step instructions, screenshots, and recommendations assume a Windows environment.
Recommendations
  • Add instructions and examples for deploying Azure Backup Server on supported Linux distributions, if possible.
  • Include Linux VM creation and disk attachment guides alongside Windows equivalents.
  • Provide Linux-specific backup consistency details, including supported file systems and backup tools.
  • Offer parity in troubleshooting and configuration steps for Linux environments (e.g., using Bash or shell commands, Linux storage management).
  • Clarify any limitations or requirements for Linux VMs, such as supported distributions, file systems, and integration points.
  • If Azure Backup Server is Windows-only, explicitly state this limitation early in the documentation and provide alternative solutions for Linux workloads.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/using-run-command.md ...s/blob/main/articles/azure-vmware/using-run-command.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, without mentioning or providing examples for Linux shells or cross-platform alternatives. There is no guidance for users who may prefer Bash, shell scripts, or other Linux-native tools, nor is there any mention of Linux-specific patterns or parity in command execution.
Recommendations
  • Include examples of Run Command usage with Linux shells (e.g., Bash) or clarify whether only PowerShell is supported.
  • Explicitly state platform limitations and provide guidance for Linux administrators if PowerShell is the only supported method.
  • Add documentation or links for Linux-based automation and scripting in Azure VMware Solution, if available.
  • If Run Command supports only PowerShell, consider adding a rationale and suggest workarounds for Linux users (such as using PowerShell Core on Linux).
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-first-party-principle-security.md .../azure-vmware/native-first-party-principle-security.md
High Priority View Details →
Scanned: 2025-08-29 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation prioritizes Windows-centric tools and workflows. Azure PowerShell is presented as the primary command-line automation example, with detailed steps and multiple commands, while Azure CLI (cross-platform) is only mentioned later and with less detail. There are no Linux-specific examples or references to Linux environments, and the PowerShell approach is described before the CLI, reinforcing a Windows-first perspective.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary prerequisites or installation links for non-Windows platforms.
  • If scripting is required, include bash script examples or note how to adapt the process for Linux shells.
  • Balance the order of presentation so that cross-platform tools (like Azure CLI) are not always listed after Windows-specific tools.
  • Add a note clarifying that all steps can be performed from Linux or macOS using the Azure CLI, and provide troubleshooting tips for those environments if needed.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-dns-azure-vmware-solution.md ...es/azure-vmware/configure-dns-azure-vmware-solution.md
High Priority View Details →
Scanned: 2025-08-29 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell/PowerCLI examples for verifying DNS resolution, with no equivalent Linux or cross-platform CLI examples. The use of PowerShell cmdlets is presented as the primary (and only) method for interacting with the NSX-T Policy API, and there are no references to Linux-native tools or instructions for users on non-Windows platforms.
Recommendations
  • Provide equivalent Linux-based examples for verifying DNS resolution, such as using curl, wget, or direct API calls with tools like curl or httpie.
  • Include examples using the NSX-T Policy API via REST calls, demonstrating how to perform the same operations from Linux/macOS or any platform.
  • Mention and document the use of native Linux tools (e.g., dig, nslookup) for DNS verification, especially since the raw answer in the PowerShell example references DiG output.
  • Ensure that any scripting or automation steps are shown in both PowerShell and Bash (or other common shells) to support cross-platform administrators.
  • Clarify in the documentation that PowerCLI is not required, and provide alternative methods for users who do not have access to Windows environments.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/architecture-api-management.md ...n/articles/azure-vmware/architecture-api-management.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell and the Azure portal as management tools, without referencing Linux-native tools or CLI alternatives. The examples and workflow descriptions prioritize Windows-centric tools and patterns, with no mention of Bash, Azure CLI, or Linux automation approaches. There are no Linux-specific examples or guidance, which may leave Linux users underserved.
Recommendations
  • Include Azure CLI (az) examples alongside or instead of PowerShell for management tasks, as Azure CLI is cross-platform and widely used on Linux.
  • Mention Bash scripting and Linux automation tools as alternatives to PowerShell for DevOps workflows.
  • Explicitly state that all management operations can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
  • Balance references to the Azure portal and PowerShell with equivalent instructions or links for Linux users.
  • Add a section or callout highlighting cross-platform support and best practices for Linux-based environments.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-vsan.md ...docs/blob/main/articles/azure-vmware/configure-vsan.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Azure portal and PowerShell/cmdlet-based workflows for all configuration steps, with no mention of Linux CLI or automation alternatives. Windows VM prerequisites are listed before Linux, and all operational examples are based on Windows-centric tools and patterns.
Recommendations
  • Provide equivalent Linux command-line (e.g., Azure CLI, Bash, or REST API) instructions for each configuration task, not just PowerShell/cmdlets.
  • Include automation examples using cross-platform tools (such as Terraform, Ansible, or REST API calls) where possible.
  • List Linux and Windows VM prerequisites together or alternate their order to avoid implicit prioritization.
  • Reference Linux administration tools or scripts for managing vSAN features, where applicable.
  • Explicitly state if certain operations are only possible via Windows tools, and suggest workarounds or alternatives for Linux users.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-virtual-trusted-platform-module.md ...re-vmware/configure-virtual-trusted-platform-module.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows security features (e.g., BitLocker), mentioning Windows OS versions before Linux in prerequisites, and describing VBS as protecting 'windows system' specifically. There are no Linux-specific configuration examples or mentions of Linux disk encryption tools or security features, despite Linux being listed as a supported guest OS.
Recommendations
  • Provide Linux-specific examples for vTPM usage, such as configuring disk encryption with LUKS or integrating with Linux security modules.
  • Mention Linux guest OS versions and features before or alongside Windows equivalents in prerequisites and feature descriptions.
  • Describe VBS benefits in a cross-platform manner, highlighting protections for both Windows and Linux systems.
  • Reference Linux security tools (e.g., dm-crypt, LUKS, SELinux) where BitLocker is mentioned for Windows.
  • Include screenshots or step-by-step instructions for configuring vTPM on Linux VMs, not just Windows.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/azure-vmware-solution-known-issues.md ...les/azure-vmware/azure-vmware-solution-known-issues.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a mild Windows bias. Where remediation steps involve VMware Tools, the instructions reference 'VMware Tools for Windows' and provide no mention of Linux or cross-platform equivalents. The use of the Azure VMware Solution Run command 'Set-Tools-Repo' is described without clarifying its applicability to non-Windows environments. No Linux-specific examples or guidance are provided, and Windows is mentioned explicitly before Linux in the context of vulnerabilities and updates.
Recommendations
  • For any mention of VMware Tools updates or vulnerabilities, specify whether the issue and remediation apply to both Windows and Linux guest operating systems. If remediation steps differ, provide instructions for both platforms.
  • When referencing commands like 'Set-Tools-Repo', clarify if they are applicable to Linux guests, and if not, provide equivalent steps or note any limitations.
  • Avoid using 'VMware Tools for Windows' as the default phrasing; instead, use 'VMware Tools' and then specify platform differences as needed.
  • Wherever possible, include Linux-specific examples or notes alongside Windows instructions to ensure parity.
  • Review all workaround instructions for implicit Windows assumptions and add Linux guidance where relevant.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-disaster-recovery-using-jetstream.md ...ure-vmware/deploy-disaster-recovery-using-jetstream.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows/Azure VMware Solution bias. All operational instructions for installing, configuring, and managing JetStream DR are centered around the Azure portal and its 'Run command' feature, which is a Windows/Azure-specific tool. Cmdlet-based workflows (e.g., Invoke-PreflightJetDRInstall) are used throughout, with no mention of equivalent Linux CLI, shell, or cross-platform alternatives. There are no Linux or non-Azure examples, and the documentation assumes the use of Azure-specific tools and patterns, omitting any guidance for users operating in Linux environments or outside Azure.
Recommendations
  • Provide equivalent Linux shell (bash) or cross-platform CLI instructions for installing, configuring, and managing JetStream DR, especially for on-premises deployments.
  • Include examples using standard VMware tools (e.g., vSphere CLI, ovftool) that are available on Linux, not just Azure portal or PowerShell cmdlets.
  • Document manual installation and configuration steps that do not rely on Azure 'Run command' or Windows-centric tools, for users who may not have access to these features.
  • Clearly indicate which steps are Azure-specific and provide alternative instructions for non-Azure or hybrid environments.
  • Add troubleshooting and operational guidance for Linux administrators, including how to monitor, manage, and automate JetStream DR from Linux systems.
GitHub Create Pull Request
Azure Vmware https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/backup-azure-vmware-solution-virtual-machines.md ...mware/backup-azure-vmware-solution-virtual-machines.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All examples and instructions assume the use of Windows tools (Registry Editor, Certificate Import Wizard, right-click context menus, Notepad, etc.), and there is no mention of Linux equivalents or alternative procedures for Linux-based Azure Backup Server installations. The registry modification and certificate import steps are Windows-specific, and individual file recovery is only supported for Windows VMs. No Linux command-line or GUI alternatives are provided, and the documentation does not acknowledge or guide users who may be running Azure Backup Server on Linux or managing Linux VMs.
Recommendations
  • Add instructions and examples for Linux environments, including certificate import steps using Linux tools (e.g., openssl, update-ca-certificates).
  • Clarify whether Azure Backup Server can be installed and used on Linux, and if not, explicitly state the Windows-only support.
  • Provide guidance for backing up and restoring Linux VMs, including any limitations or differences compared to Windows VMs.
  • Include alternative procedures for registry modifications or configuration changes for Linux, if applicable.
  • Ensure that individual file recovery instructions address Linux VMs, or clearly state the limitation and suggest alternative approaches for Linux workloads.
GitHub Create Pull Request
← Previous Page 7 of 17 Next →