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 201-225 of 412 flagged pages
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by emphasizing Windows-specific security features (such as BitLocker and credential protection), mentioning Windows operating systems and tools before Linux, and omitting Linux-specific examples or guidance for using vTPM. While Linux is listed as a supported guest OS, there are no Linux-focused instructions or references to Linux security tooling or workflows.
Recommendations
- Include Linux-specific examples for configuring and using vTPM, such as enabling disk encryption with LUKS or using Linux attestation tools.
- Mention Linux security features (e.g., Secure Boot with shim/grub, TPM-backed disk encryption, measured boot) alongside Windows features like BitLocker.
- Provide parity in documentation by showing how vTPM benefits both Windows and Linux VMs, including references to Linux documentation or community best practices.
- Avoid language that implies Windows is the primary or only use case (e.g., 'prevents malware from running on windows system'), and instead use OS-neutral phrasing or explicitly mention both Windows and Linux.
Create Pull Request
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-vsan-esa.md
.../blob/main/articles/azure-vmware/configure-vsan-esa.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), using Windows-centric terminology (e.g., Run command, Packages), and mentioning Windows Server Failover Clusters as a supported feature. There are no Linux or cross-platform command-line examples, nor are Linux tools or workflows mentioned. The documentation assumes the user is operating from a Windows environment, with no guidance for Linux or macOS users.
Recommendations
- Provide equivalent command-line examples for Linux (e.g., using VMware's CLI tools such as govc, or REST API calls via curl).
- Mention and document how to perform the same operations from non-Windows environments, including macOS and Linux.
- Clarify if the 'Run command' feature is accessible via cross-platform tools or only through the Azure Portal/PowerShell.
- Include references to Linux-supported features or guest OS requirements, not just Windows (e.g., mention Linux guest support for TRIM/UNMAP).
- Balance the mention of Windows Server Failover Clusters with information about clustering support for Linux-based workloads.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell cmdlets for all configuration tasks, referencing Windows VM hardware requirements before Linux, and omitting any Linux-native command-line or tool examples. The workflow assumes use of the Azure portal and Windows-centric tools, with no mention of Linux shell equivalents or cross-platform automation options.
Recommendations
- Provide equivalent Linux shell (bash/CLI) commands or scripts for each configuration task, where possible.
- Mention and document cross-platform tools (such as VMware's govc CLI or REST APIs) that can be used from Linux environments.
- When listing VM prerequisites, alternate or parallelize the order of Windows and Linux requirements to avoid always listing Windows first.
- Clarify whether the cmdlets and portal workflows are accessible from Linux or require Windows, and provide alternatives if needed.
- Include examples or links for automating these tasks from Linux-based CI/CD pipelines or management hosts.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash) examples for running the installation scripts, but the Windows example is presented first and includes more detailed instructions (such as bypassing execution policy). Additionally, Windows-style paths (e.g., C:\Users\sampleUser.sslProxy.crt) are used in JSON examples for proxy configuration, and there is a general tendency to mention Windows Server and SQL Server as primary use cases. There are no missing Linux examples, but the documentation subtly prioritizes Windows patterns and tools.
Recommendations
- Alternate the order of Windows and Linux examples or present them side-by-side to avoid implicit prioritization.
- Use platform-agnostic file path examples in JSON snippets (e.g., /home/sampleUser/sslProxy.crt for Linux, or use placeholders).
- Explicitly state that both Windows and Linux management VMs are equally supported, and provide parity in troubleshooting and configuration details.
- Where possible, avoid Windows-specific terminology or provide equivalent Linux instructions (e.g., mention chmod and bash for Linux alongside Set-ExecutionPolicy for Windows).
- Highlight Linux-based use cases (e.g., Linux VMs, Linux management hosts) in the benefits and deployment considerations sections.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows/Azure-centric bias. All operational examples and automation steps are presented using Azure Run Command and PowerShell/cmdlet syntax, with no mention of Linux CLI, shell scripts, or cross-platform alternatives. The documentation assumes use of the Azure portal and Windows-style automation, omitting any Linux-native or cross-platform command-line instructions. There are no examples or guidance for users who may wish to automate or interact with JetStream DR from Linux environments.
Recommendations
- Provide equivalent Linux shell (bash) or cross-platform CLI examples for all installation, configuration, and management steps, especially for JetStream DR deployment and management.
- Document how to perform JetStream DR operations using REST APIs, if available, or via the vSphere CLI, to support automation from Linux or non-Windows environments.
- Clarify whether the Azure Run Command and cmdlets can be invoked from Linux systems (e.g., via Azure CLI or REST), and provide explicit instructions for doing so.
- Include references or links to JetStream DR documentation that covers Linux-based deployment and management, if available.
- Add a section addressing cross-platform automation and scripting, highlighting any differences or requirements for Linux users.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-traffic-manager-balance-workloads.md
...ure-vmware/deploy-traffic-manager-balance-workloads.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft IIS Servers as backend VMs, omitting any mention of Linux-based alternatives (such as Apache or Nginx). All backend pool examples and screenshots focus on IIS and Windows-centric tools. There are no Linux-specific instructions, examples, or validation steps, and the only server OS referenced is Windows. This may give the impression that only Windows workloads are supported or recommended.
Recommendations
- Include examples using Linux-based web servers (e.g., Apache, Nginx) as backend pool members alongside IIS.
- Explicitly state that both Windows and Linux VMs are supported as backend pool members in Azure VMware Solution.
- Provide screenshots or command-line examples (e.g., using curl or wget) for verifying endpoints from Linux hosts, not just browser-based validation.
- Mention Linux administration tools or validation steps (such as using SSH to connect to Linux VMs) where appropriate.
- Balance references to Windows and Linux in both prerequisites and step-by-step instructions to ensure parity and inclusivity.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows-centric workflows and tools, specifically the Azure portal and VMware vSphere client interfaces, with no mention of Linux command-line alternatives or parity. All operational steps (installation, upgrade, uninstall, password reset) are described using GUI-based or Windows-style 'Run command' workflows, and there are no CLI or automation examples for Linux users. The documentation assumes the use of Windows-based management tools and does not address Linux-based administration or scripting.
Recommendations
- Provide equivalent Linux CLI examples for installation, upgrade, and uninstallation (e.g., using Azure CLI, PowerShell Core on Linux, or REST API calls).
- Document how to perform these operations via automation or scripting for Linux administrators.
- Clarify whether the 'Run command' functionality is accessible via cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
- Include notes or sections for Linux users, outlining any prerequisites or differences in workflow.
- Ensure parity in screenshots and instructions for both Windows and Linux environments where applicable.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server and Microsoft SQL Server Always On Availability Groups, which are only supported on Windows. All examples, prerequisites, and operational steps assume Windows Server Failover Clustering, with no mention of Linux-based SQL Server deployments or cross-platform considerations. Only Windows tools (SQL Server Management Studio, Windows Server Failover Cluster) are referenced, and all guidance is Windows-centric.
Recommendations
- Explicitly state that SQL Server Always On Availability Groups are only supported on Windows, and clarify if Linux-based SQL Server deployments are out of scope for this guide.
- If Linux-based SQL Server high availability scenarios (such as Pacemaker clusters) are supported for migration to Azure VMware Solution, provide a parallel section or a separate guide for those scenarios.
- Where possible, mention the existence of SQL Server on Linux and its clustering options, even if only to clarify their support status.
- Include references or links to documentation for Linux-based SQL Server deployments and migration strategies, if applicable.
- If the migration process is fundamentally different for Linux, provide clear guidance or a pointer to relevant resources.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows Server Failover Clustering and SQL Server on Windows, with all examples, screenshots, and instructions referencing Windows Server tools (e.g., Failover Cluster Manager, SQL Server Management Studio). There is no mention of Linux-based SQL Server clusters, Linux failover clustering solutions (e.g., Pacemaker), or migration steps for non-Windows environments. The prerequisites, migration steps, and troubleshooting are all tailored exclusively to Windows Server environments.
Recommendations
- Add a section or parallel guide for migrating SQL Server clusters running on Linux (e.g., using Pacemaker/Corosync or Linux-based Always On Availability Groups).
- Include Linux-specific prerequisites, such as reviewing and recording Linux network/storage configuration, and backing up using Linux-native tools.
- Provide migration steps and screenshots for Linux-based clusters, including relevant commands and tools (e.g., systemctl, pcs, SQL Server on Linux management tools).
- Reference Linux documentation for SQL Server clustering and failover, and link to official Microsoft and VMware resources for Linux environments.
- Clarify in the introduction that the current guide is Windows-specific, and direct Linux users to appropriate resources if a Linux parity guide is not yet available.
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 →
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, with no mention of Linux-based SQL Server deployments or migration scenarios. All examples, prerequisites, and validation steps assume a Windows Server environment, and only Windows tools (e.g., SQL Server Management Studio) are referenced. There is no guidance for users running SQL Server on Linux or for Linux-based VM migrations.
Recommendations
- Include explicit mention of SQL Server on Linux as a supported scenario, if applicable.
- Provide parallel migration steps and prerequisites for SQL Server instances running on Linux (e.g., Ubuntu, Red Hat).
- Add examples and screenshots using Linux-based management tools (such as sqlcmd or Azure Data Studio) alongside Windows tools like SQL Server Management Studio.
- Reference Linux documentation and best practices for SQL Server deployments and migrations.
- Clarify any limitations or differences in the migration process for Linux-based SQL Server VMs.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, which is more cross-platform. There are no explicit Linux/macOS-specific instructions or clarifications, and the PowerShell example assumes a Windows environment. The CLI example is present but not emphasized or explained in a Linux context.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and works natively on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $) to reinforce this.
- If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/shell examples where possible.
- Add a note or section for Linux/macOS users, including any prerequisites or differences in experience (e.g., installation of Azure CLI, authentication methods).
- Ensure that all tooling references (e.g., 'copy the value from the ID column') are not Windows-centric and clarify how to perform these steps in different environments.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references PowerShell cmdlets and Windows-centric tooling (e.g., 'Run Command' panel, cmdlet naming conventions), with no mention of Linux/Unix equivalents or CLI alternatives. All examples and instructions are tailored to a Windows/PowerShell environment, and there is no guidance for users who may prefer or require Linux-based management or automation.
Recommendations
- Provide equivalent command-line examples using Bash or other Linux shells, if available.
- Clarify whether the Run Commands can be invoked via Azure CLI, REST API, or other cross-platform tools, and provide usage examples.
- Explicitly state if PowerShell is required, or if there are alternative methods for Linux users.
- Include references to Linux-compatible tools or scripts for managing VMware HCX in Azure VMware Solution.
- Ensure that documentation sections and examples are balanced, presenting both Windows and Linux approaches where possible.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias. All backend VM configuration examples use Windows Server 2016 with IIS, and only PowerShell commands are provided for web server setup. There are no Linux-based examples or references to Linux tools (such as Apache or Nginx), and no Bash or shell commands are shown. The documentation implicitly assumes a Windows environment for web hosting, omitting Linux alternatives entirely.
Recommendations
- Add parallel Linux-based examples for backend web server setup, such as using Ubuntu VMs with Apache or Nginx.
- Provide equivalent Bash/shell commands for installing and configuring web servers on Linux VMs.
- Explicitly mention that both Windows and Linux VMs are supported as backend pools, and illustrate this with screenshots or configuration steps.
- Where PowerShell is used, offer Linux command-line alternatives side-by-side.
- Update diagrams and screenshots to include Linux VM icons or references where appropriate.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by presenting Windows uninstall instructions before Linux, using Windows-specific tools (Control Panel, Programs and Features), and referencing Windows terminology and navigation patterns. While Linux instructions are present and reasonably detailed, the ordering and emphasis suggest a Windows-first approach.
Recommendations
- Present Linux and Windows instructions in parallel or in a consistent order (e.g., alphabetical or by usage share), rather than always listing Windows first.
- Where possible, provide command-line alternatives for Windows (e.g., using PowerShell or command prompt to uninstall the agent), similar to the Linux approach, to ensure parity for automation and headless environments.
- Avoid Windows-centric navigation language (such as Control Panel) as the default; instead, clarify that these are Windows-specific steps and provide equivalent Linux navigation or command-line steps.
- Add a summary table or section at the start of uninstall instructions that clearly distinguishes between Windows and Linux, helping users quickly find the relevant section.
- Ensure that all examples and tool references are balanced between Windows and Linux, and that neither is given undue prominence unless justified by user base data.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and credential requirements are specific to Windows guest OS, with explicit statements that Linux guest OS restores are not supported (except for a manual workaround). There are no Linux-specific instructions, examples, or parity in tooling or process. Windows tools, patterns, and account types are referenced exclusively.
Recommendations
- Clearly indicate in the introduction and prerequisites that Linux guest OS support is limited or unavailable, and provide a roadmap or ETA for Linux support if possible.
- If manual restore from Linux VMs is possible (by attaching VMDKs), provide a dedicated section with step-by-step instructions for Linux users, including example commands for mounting VMDKs and copying files using Linux tools.
- Where possible, generalize instructions and terminology to be OS-agnostic, or provide parallel sections for Windows and Linux.
- Include examples of restoring files using Linux guest OS (even if only manually), with appropriate commands (e.g., using mount, guestmount, or similar tools).
- List any limitations or differences in restore capabilities between Windows and Linux guests in a comparison table.
- Avoid exclusive use of Windows-specific credential and account requirements in general documentation; instead, clearly scope such requirements to Windows-only sections.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias throughout. All VM creation, disk attachment, and installation instructions are provided exclusively for Windows environments. There are no Linux-based examples or guidance for deploying or managing Azure Backup Server on Linux. Windows-specific tools (such as PowerShell, Windows Update, and ReFS) are referenced without Linux alternatives, and the documentation assumes the use of Windows Server as the host OS for Azure Backup Server.
Recommendations
- If Azure Backup Server supports Linux as a host, provide equivalent Linux-based instructions for VM creation, disk attachment, and installation.
- Include Linux command-line examples (e.g., using Azure CLI or Bash) alongside or before Windows/PowerShell examples.
- Mention Linux-compatible file systems and storage configuration steps if supported.
- Clarify early in the documentation if Azure Backup Server is Windows-only; if so, briefly explain why and suggest alternatives for Linux users.
- Where PowerShell or Windows-specific tools are referenced, provide Azure CLI or cross-platform alternatives where possible.
- Add a section or callout for Linux administrators, outlining any limitations or alternative approaches.
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 →
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. All detailed examples, migration paths, and next steps are centered on Microsoft SQL Server and Windows Server technologies, with no concrete examples or guidance for Linux subscriptions or workloads. Windows tools and patterns (e.g., Windows Server Failover Cluster, SQL Server) are highlighted, and Linux equivalents are not mentioned or linked.
Recommendations
- Include specific examples and migration guides for Linux workloads, such as migrating Linux VMs or databases (e.g., MySQL, PostgreSQL) to Azure VMware Solution.
- Provide parity in 'Next steps' by adding links to Linux-focused documentation (e.g., configuring HA for Linux, enabling Azure Hybrid Benefit for Linux subscriptions).
- Mention and explain Linux licensing/subscription options and how Azure Hybrid Benefit applies to them, with concrete scenarios.
- Balance the coverage by describing both Windows and Linux use cases, tools, and patterns equally throughout the document.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, without mentioning or providing examples for Linux shells or tools. There are no Linux/Unix command-line examples, nor is there any discussion of how to perform similar tasks from a Linux environment. The terminology and workflow are centered around Windows-native tools and patterns.
Recommendations
- Include examples of running Run Command operations using Linux shells (e.g., Bash) or cross-platform tools (e.g., Azure CLI, REST API).
- Clarify whether Run Command supports only PowerShell or if Linux/Unix scripting is also possible; if so, provide parity in examples.
- Mention and document any Linux-compatible tools or workflows for managing Run Command, such as using the Azure CLI from a Linux terminal.
- If PowerShell is required, note the availability of PowerShell Core on Linux and provide guidance for Linux users.
- Ensure screenshots and UI references are not exclusively Windows-centric, or supplement them with Linux/CLI equivalents where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/tutorial-access-private-cloud.md
...articles/azure-vmware/tutorial-access-private-cloud.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes creating and using a Windows VM as the jump box for accessing the Azure VMware Solution private cloud. All instructions, screenshots, and references are Windows-specific, with no mention of Linux alternatives or how to perform the same tasks on a Linux VM. The guidance for connecting to the VM and accessing vCenter/NSX Manager is tailored to Windows environments, and there are no Linux tools or patterns discussed.
Recommendations
- Provide parallel instructions for creating a Linux VM as a jump box, including recommended distributions (e.g., Ubuntu, CentOS) and any necessary configuration steps.
- Include guidance and screenshots for connecting to the Linux VM (e.g., using SSH) and accessing vCenter Server and NSX Manager from a Linux environment (using Firefox/Chrome or CLI tools).
- Mention Linux as an option in checklists and overviews, not just Windows.
- Link to both Windows and Linux VM connection documentation in the 'connect to a virtual machine' step.
- Discuss any differences or prerequisites for accessing vCenter/NSX Manager from Linux, such as browser compatibility or required packages.
Azure Vmware
Set an external identity source for vCenter Server
...cles/azure-vmware/configure-identity-source-vcenter.md
Medium 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, screenshots, and instructions reference Windows-specific tools (MMC, Windows domain controllers, NetBIOS, etc.), and there are no examples or guidance for integrating with Linux-based LDAP servers or using Linux-native tools. The documentation assumes the reader is using Windows infrastructure and does not mention alternatives or provide parity for Linux/macOS users.
Recommendations
- Add explicit instructions and examples for integrating with Linux-based LDAP servers (such as OpenLDAP), including relevant configuration steps and command-line tools.
- Provide screenshots or CLI examples for certificate management on Linux (e.g., using openssl, certtool, or keytool).
- Clarify which steps are generic LDAP/LDAPS and which are Windows-specific, and offer alternative procedures for non-Windows environments.
- Mention and document how to obtain and export certificates from Linux LDAP servers.
- Include troubleshooting steps and Run command usage for Linux-based identity sources, if supported.
- Avoid using Windows terminology (NetBIOS, MMC) exclusively; explain equivalents or note when they are not applicable.
Azure Vmware
Architecture - API Management
...n/articles/azure-vmware/architecture-api-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references management via the Azure portal and PowerShell, with no mention of Linux-native tools (such as Azure CLI or Bash scripting). Windows-centric automation (PowerShell) is highlighted as a primary mechanism for DevOps, and examples or guidance for Linux/macOS users are absent. The order of presentation also places Windows tools before any alternatives.
Recommendations
- Add explicit references and examples for Azure CLI usage alongside PowerShell, especially for automation tasks.
- Include Bash or shell scripting examples for Linux/macOS users.
- Mention cross-platform management options (e.g., REST API, Terraform) where relevant.
- Ensure that tool recommendations do not prioritize Windows-specific solutions unless necessary.
Azure Vmware
Architecture - Integrate an Azure VMware Solution deployment in a hub and spoke architecture
...in/articles/azure-vmware/architecture-hub-and-spoke.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Jump box and Azure Bastion' section, where only Windows 10 or Windows Server are mentioned as supported operating systems for the jump box VM. There are no references to Linux-based jump boxes, nor examples or guidance for Linux users. The rest of the documentation is OS-agnostic, focusing on Azure networking and VMware integration, but the lack of Linux parity in jump box recommendations is notable.
Recommendations
- Explicitly mention that the jump box VM can be Linux-based (e.g., Ubuntu, CentOS) and provide guidance or examples for deploying and accessing a Linux jump box.
- Include instructions for SSH access to Linux jump boxes via Azure Bastion, alongside RDP for Windows.
- Clarify that both Windows and Linux VMs are supported for jump box scenarios, unless there are technical limitations.
- Add screenshots or walkthroughs for Linux jump box setup and access.
Azure Vmware
Azure VMware Solution known issues
...les/azure-vmware/azure-vmware-solution-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several workarounds reference PowerShell cmdlets (e.g., Set-vSANCompressDedupe) and Azure VMware Solution Run commands that are typically executed via Windows/PowerShell environments. There are no Linux/macOS command equivalents or examples provided, nor is there guidance for performing these actions from non-Windows platforms. The documentation also references 'VMware Tools for Windows' specifically in one issue, without mentioning Linux/macOS variants.
Recommendations
- Provide Linux/macOS equivalents for PowerShell cmdlets and Run commands, such as REST API calls, CLI commands, or scripts.
- Clarify whether Run commands can be executed from Linux/macOS environments, and provide instructions or examples if possible.
- When referencing 'VMware Tools for Windows', also mention Linux/macOS versions and their remediation steps if applicable.
- Ensure that any command-line instructions are cross-platform or explicitly note platform requirements.
- Add a note or section on how Linux/macOS users can interact with Azure VMware Solution for common administrative tasks.
Azure Vmware
Integrate Microsoft Defender for Cloud with Azure VMware Solution
...in/articles/azure-vmware/azure-security-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the security analytics rule example, which exclusively references Windows server sign-in failures and provides a query tailored to Windows SecurityEvent logs. There are no equivalent examples or queries for Linux VMs, nor is there guidance for Linux-specific security event collection or analytics. The overall workflow and screenshots are platform-neutral, but the only concrete example is Windows-centric.
Recommendations
- Add equivalent examples for Linux VMs, such as analytics rules for failed SSH logins or Linux audit events.
- Include sample queries for Linux security events (e.g., using Syslog or Auditd data) alongside Windows examples.
- Clarify in the instructions how to collect and analyze security events from Linux VMs within Microsoft Sentinel and Defender for Cloud.
- Explicitly mention Linux support and provide links to relevant documentation for Linux security monitoring.
Azure Vmware
Configure DNS forwarder for Azure VMware Solution
...es/azure-vmware/configure-dns-azure-vmware-solution.md
Medium 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/macOS CLI examples (e.g., using curl, dig, or nslookup from a shell). The only command-line verification is via PowerCLI, which is Windows-centric and assumes the user is on a Windows system or has PowerShell/PowerCLI installed. No Linux tools or workflows are mentioned, and Windows/PowerShell tooling is presented first and exclusively.
Recommendations
- Add equivalent verification steps using Linux/macOS command-line tools (e.g., dig, nslookup) to query the DNS Forwarder Service.
- Clarify whether PowerCLI can be used cross-platform, or provide instructions for installing and using PowerCLI on Linux/macOS.
- Present Linux/macOS examples alongside or before Windows/PowerShell examples to ensure parity.
- Mention any platform requirements or limitations for the verification steps.