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 76-100 of 412 flagged pages
Azure Vmware
Deploy Zerto disaster recovery on Azure VMware Solution
...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation displays a moderate Windows bias, particularly in its description of the Zerto Cloud Appliance (ZCA), which is exclusively available as a Windows VM for Azure IaaS VM recovery. Windows services and integration patterns are described in detail, while Linux equivalents are not mentioned or provided for this scenario. Although the core Zerto management and replication appliances are Linux-based, the documentation does not offer Linux-based examples or alternatives for Azure VM recovery, nor does it provide parity in tooling or deployment instructions for Linux users in the Azure context.
Recommendations
- Provide Linux-based alternatives or clarify if none exist for Azure IaaS VM recovery, and explain the rationale.
- Include Linux deployment and configuration examples for Zerto components where possible, especially for Azure scenarios.
- Ensure that any tooling or service described (such as ZCA) is accompanied by information about Linux support or lack thereof, and suggest workarounds for Linux-centric environments.
- Present both Windows and Linux options in parallel when discussing Zerto deployment, management, and troubleshooting, especially in Azure contexts.
- Explicitly state platform limitations early in the documentation to help users understand the scope and avoid confusion.
Create Pull Request
Azure Vmware
Architecture - Integrate an Azure VMware Solution deployment in a hub and spoke architecture
...in/articles/azure-vmware/architecture-hub-and-spoke.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows-based jump boxes (Windows 10 or Windows Server) for accessing Azure VMware Solution environments, with no mention of Linux alternatives. The guidance for domain controllers and DNS resolution also assumes Active Directory (Windows-centric) as the default, and does not provide parity for Linux-based identity or DNS solutions. No Linux VM examples or tools are mentioned for management or connectivity.
Recommendations
- Include examples and recommendations for deploying Linux-based jump boxes (e.g., Ubuntu, CentOS) alongside Windows options for accessing Azure VMware Solution environments.
- Mention Linux-compatible remote access tools (e.g., SSH, xrdp) and provide guidance for securing Linux jump boxes.
- Provide parity in identity and DNS recommendations by referencing Linux-based DNS servers (e.g., BIND) and identity solutions (e.g., FreeIPA, Samba AD DC) where appropriate.
- Ensure that architectural diagrams and workflow descriptions do not assume Windows-only components, and clarify that both Windows and Linux VMs can be used in hub and spoke architectures.
Azure Vmware
Enable guest management and install extensions on Arc-enabled VMs
...n/articles/azure-vmware/arc-enable-guest-management.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by referencing VMware Tools (primarily associated with Windows VM management), providing no Linux-specific instructions or examples, and omitting any mention of Linux command-line tools or patterns. All steps are described in terms of GUI navigation and Azure CLI usage, with no attention given to Linux-specific extension installation or troubleshooting. The prerequisites and enablement steps do not distinguish between Windows and Linux VMs, nor do they provide parity for Linux users.
Recommendations
- Add explicit instructions and examples for enabling guest management and installing extensions on Linux VMs, including common Linux distributions.
- Include Linux-specific prerequisites (e.g., required packages, service dependencies, or SELinux/AppArmor considerations).
- Reference Linux equivalents to VMware Tools, such as open-vm-tools, and clarify any differences in process or requirements.
- Provide CLI examples using Bash or shell scripts for Linux environments, alongside Azure CLI usage.
- Highlight any differences in extension support or troubleshooting steps for Linux VMs.
Azure Vmware
Azure VMware Solution known issues
...les/azure-vmware/azure-vmware-solution-known-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as PowerShell cmdlets (e.g., Set-vSANCompressDedupe, Set-Tools-Repo) as the primary or sole remediation method for several issues. There are no Linux shell, Bash, or cross-platform CLI examples provided, nor are Linux equivalents or alternatives mentioned. Additionally, the documentation refers to 'VMware Tools for Windows' specifically in one issue, and remediation steps consistently use Windows/PowerShell terminology without Linux parity.
Recommendations
- Provide Linux shell (Bash) or cross-platform CLI examples alongside PowerShell cmdlets for all remediation steps.
- Reference VMware Tools for Linux and macOS where applicable, not just Windows.
- When mentioning commands (e.g., Set-vSANCompressDedupe, Set-Tools-Repo), clarify if they are available via REST API, Bash scripts, or other cross-platform interfaces.
- Add guidance for Linux administrators, such as using VMware's Linux CLI tools or REST APIs for remediation.
- Ensure that documentation does not assume the administrator is using Windows or PowerShell by default.
Azure Vmware
Deploy Bitnami virtual appliances
...articles/azure-vmware/bitnami-appliances-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by instructing users to connect to the VM via RDP and linking only to Windows VM connection instructions. There is no mention of Linux-based connection methods (such as SSH or Linux RDP clients), nor are Linux tools or workflows referenced when accessing the VM or vCenter. Windows terminology and tools are presented first and exclusively in the context of VM access.
Recommendations
- Include instructions and links for connecting to the VM from Linux and macOS clients, such as using SSH or Remmina.
- Provide parity in examples for VM access, referencing both Windows and Linux tools (e.g., 'connect-logon' for Windows, SSH for Linux/macOS).
- Avoid assuming the administrator is using Windows; use neutral language and offer cross-platform guidance.
- Add a note or section on accessing vCenter and appliances from non-Windows environments.
- Where RDP is mentioned, clarify that Linux and macOS users can use compatible RDP clients or SSH, and provide relevant documentation links.
Azure Vmware
Back up Azure VMware Solution VMs with Azure Backup Server
...mware/backup-azure-vmware-solution-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, screenshots, and tooling are centered around Azure Backup Server, which is a Windows-only product. Steps for certificate import, registry edits, and file recovery are exclusively described using Windows tools and interfaces (e.g., Certificate Import Wizard, Windows Registry Editor, right-click context menus). There are no Linux equivalents, nor any mention of how to perform these tasks on a Linux system. Even individual file recovery is only supported for Windows VMs.
Recommendations
- Explicitly state that Azure Backup Server is Windows-only and clarify Linux support limitations at the start of the document.
- Provide alternative instructions or links for Linux-based backup solutions, such as Azure Backup integration with Linux VMs or third-party tools.
- Include notes or sections describing how Linux VMs can be backed up and restored, and clarify limitations (e.g., individual file recovery not supported for Linux VMs).
- If possible, offer PowerShell and CLI examples for Windows, and Bash/command-line equivalents for Linux where relevant.
- Add a comparison table showing feature parity and gaps between Windows and Linux VM backup and recovery scenarios.
Azure Vmware
Use Azure VMware Solution with Azure Elastic SAN
...n/articles/azure-vmware/configure-azure-elastic-san.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure portal as primary tools for resource creation and management, with Azure CLI mentioned only as an alternative. There are no Linux-specific examples, CLI commands, or references to Linux-native tools or workflows. All procedural steps and screenshots are based on the Azure portal UI, which is typically accessed from Windows environments, and there is no mention of Linux shell scripting, automation, or integration patterns.
Recommendations
- Provide explicit Linux/Unix shell examples for resource creation and management using Azure CLI.
- Include guidance for using bash scripts to automate SAN and datastore operations.
- Add screenshots or walkthroughs for Azure CLI usage on Linux systems.
- Clarify that all steps can be performed from Linux environments and note any platform-specific caveats.
- Reference Linux-native tools (e.g., curl, jq) for interacting with Azure REST APIs where relevant.
- Ensure parity in example ordering: present CLI and PowerShell examples side-by-side, or alternate which comes first.
Azure Vmware
Configure DNS forwarder for Azure VMware Solution
...es/azure-vmware/configure-dns-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerCLI (PowerShell) examples for verifying DNS resolution, but does not offer equivalent Linux or cross-platform CLI examples (e.g., curl, dig, nslookup from bash). Windows-centric tooling and patterns (PowerShell, PowerCLI) are presented exclusively and before any mention of Linux alternatives, with no guidance for users on Linux or macOS platforms.
Recommendations
- Add Linux/macOS CLI examples for DNS verification, such as using dig or nslookup from a bash shell.
- Include cross-platform API usage examples (e.g., using curl or Python requests to interact with NSX-T Policy API).
- Explicitly mention that PowerCLI is Windows-centric and provide parity instructions for Linux users.
- Ensure screenshots and instructions reference both Windows and Linux environments where applicable.
- Consider reordering sections so that platform-neutral or Linux examples are presented alongside or before Windows-specific ones.
Azure Vmware
Set an external identity source for vCenter Server
...cles/azure-vmware/configure-identity-source-vcenter.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Active Directory as the external identity source for vCenter Server. All examples, prerequisites, and procedures reference Windows-specific tools (MMC, domain controller, NetBIOS, Windows Server AD), and there are no examples or guidance for integrating with Linux-based LDAP servers or using Linux tools. The documentation assumes the reader is using Windows environments and omits parity for Linux LDAP solutions.
Recommendations
- Add examples and step-by-step instructions for integrating Linux-based LDAP servers (such as OpenLDAP) as external identity sources for vCenter Server.
- Include Linux command-line tools and procedures (e.g., using openssl, ldapsearch, or certtool) for certificate export, validation, and management.
- Provide guidance on configuring DNS resolution for Linux LDAP servers within Azure VMware Solution.
- Clarify which steps are specific to Windows Server AD and which are applicable to generic LDAP servers.
- Add troubleshooting and validation steps for Linux LDAP integrations, including how to verify connectivity and authentication from Linux systems.
- Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux alternatives where applicable.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using PowerShell cmdlets and Azure portal workflows for configuration, with no mention of Linux CLI or automation alternatives. The examples and instructions are tailored to Windows-centric tools, and while Linux prerequisites are briefly mentioned, there are no Linux-specific configuration steps or examples provided.
Recommendations
- Provide equivalent Linux CLI commands or scripts (e.g., using SSH, VMware CLI tools, or REST APIs) for each configuration task.
- Include examples of automating vSAN configuration from Linux environments, such as using Python, Bash, or Ansible.
- Clarify whether the cmdlets can be run from Linux via PowerShell Core, and provide instructions if so.
- Add Linux-focused troubleshooting and operational guidance, especially for TRIM/UNMAP and space reclamation.
- Ensure parity in documentation by presenting both Windows and Linux methods side-by-side, or at least referencing Linux alternatives.
Azure Vmware
Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud
...s/azure-vmware/deploy-arc-for-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash) examples for running the onboarding scripts, but the Windows example is presented first and includes specific instructions about PowerShell execution policy. Additionally, file paths in the JSON examples use Windows-style paths (e.g., C:\Users\...), and proxy certificate configuration references Windows file locations. There is a general tendency to mention Windows patterns and tools before Linux equivalents, and some details (like execution policy) are specific to Windows environments.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Use OS-agnostic file path examples in configuration samples, or provide both Windows and Linux path formats.
- Include Linux-specific notes where Windows-specific instructions are given (e.g., mention script signing and permissions for Linux as well as execution policy for Windows).
- Ensure proxy and certificate configuration examples include Linux file path conventions (e.g., /home/user/sampleUser.sslProxy.crt) alongside Windows examples.
- Review all examples and instructions to ensure Linux users are equally supported and not required to adapt Windows-centric patterns.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell/cmdlet-based examples for all storage policy operations, referencing 'Run command' and cmdlets throughout. There are no Linux shell, Bash, or cross-platform CLI examples, nor are Linux-native tools or patterns mentioned. The workflow and screenshots are tailored to Windows/PowerShell users, with no guidance for Linux administrators.
Recommendations
- Add equivalent Linux/Bash/CLI examples for each operation, using tools such as VMware's ovftool, govc, or REST API calls via curl.
- Explicitly mention cross-platform alternatives to PowerShell cmdlets, and clarify which steps can be performed from Linux/macOS environments.
- Include screenshots or walkthroughs for Linux terminal usage where applicable.
- Document REST API endpoints for storage policy management, with sample requests and responses.
- Provide a comparison table of Windows and Linux methods for common storage policy tasks.
- Review terminology to ensure it is not Windows-centric (e.g., avoid assuming 'cmdlet' is the only interface).
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and patterns, such as PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), and Azure portal workflows that are typically Windows-oriented. There are no Linux shell/CLI examples, nor is there mention of Linux-specific tooling or procedures for configuring vSAN ESA features. Additionally, the documentation references Windows Server Failover Clusters as a supported feature, but does not mention Linux clustering equivalents.
Recommendations
- Include equivalent Linux CLI commands or procedures for configuring vSAN ESA features, such as using VMware's Linux command-line tools (e.g., esxcli, govc, or REST APIs).
- Provide examples using Linux shell syntax alongside PowerShell examples, ensuring parity for Linux administrators.
- Mention Linux-supported clustering solutions (e.g., Pacemaker, Corosync) where relevant, not just Windows Server Failover Clusters.
- Clarify whether the documented procedures are platform-agnostic or provide platform-specific instructions for both Windows and Linux environments.
- Add notes on how Linux users can access or automate these configurations, such as via SSH, REST API, or other cross-platform tools.
Azure Vmware
Deploy disaster recovery using JetStream DR
...ure-vmware/deploy-disaster-recovery-using-jetstream.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Azure VMware Solution environments and consistently uses Windows-centric tools and patterns. All operational examples for installing, configuring, enabling, disabling, and uninstalling JetStream DR rely on Azure portal 'Run command' features and PowerShell-style cmdlets (e.g., Invoke-PreflightJetDRInstall, Install-JetDRWithStaticIP), with no mention of Linux CLI, shell scripts, or cross-platform alternatives. There are no Linux-specific instructions or examples, and the workflow assumes the use of Windows/Azure tooling. The documentation does not provide parity for Linux administrators or environments outside of Azure/Windows.
Recommendations
- Add Linux CLI or shell script equivalents for all PowerShell/cmdlet-based operations, where possible.
- Include examples using Linux-based tools (e.g., SSH, curl, scp) for deploying and managing JetStream DR appliances.
- Document manual installation and configuration steps that can be performed outside of the Azure portal and Windows environments.
- Clarify which steps are platform-agnostic and which require Windows/Azure-specific tooling.
- Provide guidance for Linux-only environments or hybrid scenarios, including troubleshooting and support for Linux administrators.
Azure Vmware
Deploy VMware Cloud Director Availability in Azure VMware Solution
...e-cloud-director-availability-in-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure portal Run commands (a Windows-centric management pattern) for installation and management of VMware Cloud Director Availability. There are no examples or instructions for Linux-based deployment, CLI usage, or automation outside the Azure portal. Windows tools and patterns (such as Run commands and PowerShell-style command names) are mentioned exclusively, with no Linux equivalents or parity.
Recommendations
- Add instructions for deploying and managing VMware Cloud Director Availability using Linux-based tools (e.g., SSH, Bash scripts, or REST API calls).
- Provide CLI examples for both Windows (PowerShell) and Linux (Bash) environments.
- Mention and document alternative automation methods, such as Ansible or Terraform, for cross-platform deployment.
- Clarify whether Run commands can be invoked from Linux environments or provide guidance for Linux administrators.
- Ensure screenshots and walkthroughs include both Windows and Linux management scenarios.
Azure Vmware
Deploy Traffic Manager to balance Azure VMware Solution workloads
...ure-vmware/deploy-traffic-manager-balance-workloads.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft IIS Servers as backend pool members and using Windows-centric tooling (IIS, vSphere client, NSX Manager) for configuration and verification. There are no examples or mentions of Linux-based web servers (such as Apache or Nginx) or Linux-native management tools. All examples and screenshots focus on Windows environments and tools, with no Linux parity or alternatives provided.
Recommendations
- Include examples of configuring Linux-based web servers (e.g., Apache, Nginx) as backend pool members alongside IIS.
- Provide instructions and screenshots for verifying backend pool configuration using Linux tools (e.g., SSH, curl, netcat) and Linux VMs.
- Mention Linux equivalents for management and verification steps, such as using command-line tools or open-source alternatives to vSphere client.
- Ensure that references to backend pool members and endpoints are not exclusively Windows-centric, and clarify that both Windows and Linux VMs are supported.
- Add troubleshooting and verification steps that can be performed from Linux hosts, not just via browser or Windows-based tools.
Azure Vmware
vCenter Server access and identity description
...vmware/includes/vcenter-access-identity-description.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server Active Directory for user and group management, without mentioning or providing examples for Linux-based identity solutions (such as OpenLDAP). Windows tools and patterns are mentioned as the default or only approach, and there are no Linux or cross-platform alternatives or examples provided.
Recommendations
- Include references to Linux-based identity sources, such as OpenLDAP, and explain how they can be integrated (if supported) with vCenter Server in Azure VMware Solution.
- Provide examples or documentation links for configuring identity sources from both Windows and Linux environments.
- Clarify whether only Windows Server Active Directory is supported, or if other LDAP-compatible solutions can be used, and document any limitations.
- If Linux-based integration is not supported, explicitly state this to avoid ambiguity for non-Windows administrators.
Azure Vmware
Install Cloud Backup for Virtual Machines
.../azure-vmware/install-cloud-backup-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure portal 'Run command' operations and VMware vSphere client workflows, which are typically accessed from Windows environments. There are no Linux CLI, shell, or automation examples, nor any mention of Linux-native tools or patterns for installation, backup, or management. All command references use Windows/PowerShell-style cmdlets and naming conventions, and the workflow assumes use of graphical interfaces common on Windows platforms.
Recommendations
- Provide equivalent Linux CLI instructions for installing, upgrading, and uninstalling the Cloud Backup for Virtual Machines plug-in, such as using Azure CLI, REST API, or SSH.
- Include examples of how to interact with the VMware vSphere client and SnapCenter plug-in from Linux systems, such as using open-source tools or command-line utilities.
- Mention Linux-compatible automation options (e.g., Ansible, Bash scripts) for backup and restore operations.
- Clarify that the procedures can be performed from non-Windows environments, and specify any platform requirements or limitations.
- Add screenshots or walkthroughs for Linux desktop environments where applicable.
Azure Vmware
Azure Hybrid Benefit for Windows Server, SQL Server, or Linux subscriptions
...ain/articles/azure-vmware/sql-server-hybrid-benefit.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page, while mentioning Linux in the title and description, focuses almost exclusively on Windows Server and SQL Server scenarios, licensing, and migration. All examples, recommendations, and next steps are centered around Microsoft SQL Server and Windows Server technologies, with no practical guidance or examples for Linux subscriptions or workloads. Windows tools and patterns (e.g., Windows Server Failover Cluster) are referenced, but there is no mention of Linux equivalents or migration paths.
Recommendations
- Include concrete examples and guidance for applying Azure Hybrid Benefit to Linux subscriptions, such as supported Linux distributions and licensing models.
- Add migration scenarios and next steps for Linux workloads, similar to those provided for SQL Server and Windows Server.
- Reference Linux clustering or high-availability solutions (e.g., Pacemaker, Corosync) alongside Windows Server Failover Cluster.
- Ensure parity in documentation by providing step-by-step instructions for Linux environments, not just Windows/SQL Server.
- Highlight any Azure VMware Solution features or limitations specific to Linux workloads.
Azure Vmware
Remove Arc-enabled Azure VMware Solution vSphere resources from Azure
...led-azure-vmware-solution-vsphere-resources-from-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation presents uninstall instructions for Windows before Linux, using Windows-specific tools (Control Panel, Programs and Features) and folder paths. The Linux instructions are less detailed and grouped together, while Windows gets a dedicated section. No PowerShell commands are shown, but the overall flow and example order favor Windows environments.
Recommendations
- Present Linux and Windows uninstall instructions in parallel, or alternate which comes first.
- Provide more detailed Linux instructions, including common troubleshooting steps and verification commands.
- Include CLI-based uninstall methods for Windows (e.g., using PowerShell or command prompt), not just GUI steps.
- Reference Linux-specific management tools or patterns where appropriate.
- Ensure parity in detail and clarity between Windows and Linux sections.
Azure Vmware
Send VMware syslogs to log management server using Azure Logic Apps
.../blob/main/articles/azure-vmware/logs-via-logic-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing the default Windows hosting plan (Workflow Standard WS1) and focusing exclusively on Azure portal GUI steps, which are most familiar to Windows users. There are no Linux-specific examples, CLI instructions (such as Azure CLI, Bash, or PowerShell Core on Linux), or mentions of Linux-based log management servers or integration patterns. All certificate and configuration steps assume a Windows-centric workflow, such as exporting .cer files and using GUI navigation, without alternatives for Linux environments.
Recommendations
- Add equivalent instructions for deploying and managing Logic Apps using Azure CLI or ARM templates, which are platform-agnostic and commonly used on Linux.
- Include examples of integrating with Linux-based log management servers (such as rsyslog, syslog-ng, ELK stack) and provide sample URIs or configuration details.
- Provide certificate management steps for Linux environments (e.g., using openssl to export certificates, storing them in PEM format, and uploading via CLI).
- Mention and demonstrate how to retrieve Event Hub connection strings and other secrets using CLI tools on Linux.
- Clarify that the workflow is platform-agnostic and explicitly state support for both Windows and Linux log management endpoints.
- Add troubleshooting steps or notes relevant to Linux-based deployments, such as firewall rules, SELinux/AppArmor considerations, and integration with Linux syslog daemons.
Azure Vmware
Migrate Microsoft SQL Server Always On Availability Group to Azure VMware Solution
...are/migrate-sql-server-always-on-availability-group.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows-based SQL Server deployments, specifically referencing Windows Server Failover Clustering and tools like SQL Server Management Studio (SSMS). There are no examples or guidance for Linux-based SQL Server deployments or clustering solutions, and all instructions assume a Windows environment. Linux equivalents, such as SQL Server on Linux with Pacemaker, are not mentioned at all.
Recommendations
- Include a section or note addressing SQL Server Always On Availability Groups on Linux (with Pacemaker), outlining any differences in migration steps or prerequisites.
- Provide Linux-specific examples or call out where steps differ for SQL Server on Linux, including cluster management and failover procedures.
- Reference Linux tools (such as sqlcmd, Azure CLI, or Linux-based management utilities) alongside Windows tools like SSMS.
- Clarify in the prerequisites and throughout the guide whether the instructions are Windows-only, and provide links or guidance for Linux users where appropriate.
- Update the 'Next steps' and reference sections to include documentation for SQL Server on Linux and Linux-based clustering solutions.
Azure Vmware
Migrate SQL Server Failover cluster to Azure VMware Solution
...es/azure-vmware/migrate-sql-server-failover-cluster.md
High Priority
View Details →
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, screenshots, and tool references (e.g., Failover Cluster Manager, SQL Server Management Studio) being Windows-specific. There is no mention of Linux-based SQL Server clusters, nor are any Linux tools, commands, or migration scenarios discussed. The documentation assumes a Windows environment throughout.
Recommendations
- Add a section or parallel examples for migrating SQL Server clusters running on Linux (e.g., using Pacemaker or Linux clustering tools).
- Include Linux-specific prerequisites, such as commands to check cluster status, stop/start services, and manage storage.
- Provide screenshots or CLI examples for Linux-based management tools (e.g., crm, pcs, systemctl) where appropriate.
- Reference documentation for SQL Server on Linux and Linux clustering technologies.
- Clarify in the introduction that the procedure is specific to Windows clusters, and provide links or guidance for Linux-based scenarios if full parity is not possible.
Azure Vmware
Migrate Microsoft SQL Server Standalone to Azure VMware Solution
.../azure-vmware/migrate-sql-server-standalone-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All examples and validated scenarios use Windows Server and Microsoft SQL Server, with no mention of Linux-based SQL Server deployments or migration procedures. Tools and best practices referenced are exclusively for Windows environments (e.g., SQL Server Management Studio, Windows Server Failover Clustering). There are no instructions or validation for SQL Server on Linux, nor are Linux tools or patterns discussed.
Recommendations
- Add examples and validated scenarios for migrating SQL Server running on Linux (e.g., Ubuntu, Red Hat) to Azure VMware Solution.
- Include Linux-specific prerequisites, such as backup and restore procedures for SQL Server on Linux, and relevant commands (e.g., using sqlcmd, systemctl, or Linux-native backup tools).
- Reference Linux documentation and best practices for SQL Server deployments, including links to official Microsoft SQL Server on Linux docs.
- Provide parity in troubleshooting and verification steps, such as connecting to SQL Server using Linux tools (sqlcmd, Azure Data Studio) and verifying connectivity from Linux-based applications.
- Mention any differences or considerations when migrating Linux-based SQL Server VMs, such as OS-specific drivers, integration services, or network configuration nuances.
Azure Vmware
Enable first-party application service principal for Azure VMware Solution Generation 2 Private Clouds
.../azure-vmware/native-first-party-principle-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides step-by-step instructions for enabling the service principal using the Microsoft Entra ID portal (GUI), Azure PowerShell, and Azure CLI. The PowerShell example is given in detail and is listed before the Azure CLI example. PowerShell is a Windows-centric tool, and its prominence suggests a bias toward Windows environments. There are no explicit Linux shell or bash examples, and the CLI example is listed last, after PowerShell. The documentation does not mention Linux-specific tools or patterns.
Recommendations
- List Azure CLI instructions before PowerShell, as Azure CLI is cross-platform and commonly used on Linux.
- Provide explicit bash/shell examples and clarify that Azure CLI works on Linux, macOS, and Windows.
- Add notes or links for Linux users, such as installation instructions for Azure CLI on Linux.
- Avoid presenting PowerShell as the default or primary automation method; offer parity with Linux-native tools.
- Consider including troubleshooting steps or validation commands using Linux shell environments.