Lab Services

127
Total Pages
83
Linux-Friendly Pages
44
Pages with Bias
34.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

272 issues found
Showing 76-100 of 272 flagged pages
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/hackathon-labs.md ...docs/blob/main/articles/lab-services/hackathon-labs.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 shows mild Windows bias. Windows-specific guidance (such as installing and disabling Windows updates, configuring OneDrive, and autoshutdown for Windows VMs) is provided in detail, while equivalent Linux instructions or alternatives are either missing or referenced only briefly. Windows tools and features (Windows updates, OneDrive) are mentioned without Linux equivalents, and Windows-specific settings (autoshutdown) are described without noting Linux applicability. Linux guidance is limited to enabling RDP/SSH, with no further detail on Linux-specific configuration, backup options, or update management.
Recommendations
  • Provide Linux-specific examples and instructions for VM preparation, such as how to update Linux VMs and manage package updates to avoid interruptions.
  • Include Linux alternatives for backup solutions (e.g., configuring Nextcloud, Dropbox, or other cloud storage clients on Linux VMs).
  • Clarify whether autoshutdown features apply to Linux VMs and provide instructions if available.
  • Offer parity in guidance for configuring remote desktop on Linux, including recommended RDP server packages and desktop environments.
  • Ensure that all OS-specific instructions are presented in parallel, with equal detail for Windows and Linux environments.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/connect-virtual-machine-mac-remote-desktop.md ...services/connect-virtual-machine-mac-remote-desktop.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 demonstrates Windows bias by exclusively recommending the 'Windows App' for RDP connections from Mac, without mentioning alternative RDP clients commonly used on Mac or Linux (e.g., Microsoft Remote Desktop, FreeRDP, or open-source options). The instructions focus on Windows-centric tooling and do not provide parity for Linux users or mention Linux-native patterns for remote desktop access. Although SSH is briefly mentioned for Linux VMs, no Linux-specific RDP client guidance is provided.
Recommendations
  • Include alternative RDP clients for Mac and Linux, such as Microsoft Remote Desktop (macOS), FreeRDP, or Remmina.
  • Provide step-by-step instructions for connecting to Azure Lab Services VMs using these alternative clients.
  • Mention open-source and cross-platform options alongside Windows App, giving users choice and improving parity.
  • Clarify when to use SSH versus RDP for Linux VMs, and provide examples for both connection types.
  • Add a section specifically for Linux users, detailing how to connect from a Linux desktop environment.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-bring-custom-linux-image-vhd.md ...es/lab-services/how-to-bring-custom-linux-image-vhd.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 demonstrates a Windows bias by focusing exclusively on Windows-based tooling (Hyper-V Manager, PowerShell) for preparing and converting Linux images, with no step-by-step guidance for equivalent Linux workflows (e.g., using KVM, qemu-img, or Linux-native VHD creation). The only detailed example is for Windows Hyper-V, and Linux host methods are only briefly mentioned without actionable instructions. Upload instructions reference Windows-centric tools and documentation, and PowerShell is suggested for disk operations.
Recommendations
  • Provide parallel, step-by-step instructions for preparing and converting a Linux image using Linux-native tools (e.g., KVM, qemu-img, libvirt).
  • Include Linux command-line examples for resizing/converting disks (e.g., using qemu-img) alongside PowerShell/Hyper-V examples.
  • Reference and link to Linux-specific documentation for uploading VHDs (e.g., using Azure CLI or AzCopy from Linux).
  • Present both Windows and Linux workflows with equal prominence, or clearly indicate when a step is Windows-specific and offer Linux alternatives.
  • Avoid referencing only Windows documentation (such as PowerShell modules) when cross-platform alternatives exist.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-configure-firewall-settings.md ...les/lab-services/how-to-configure-firewall-settings.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 page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing the Az.LabServices PowerShell module. There are no equivalent examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform tools. Windows-centric tools and patterns are mentioned first and exclusively, leaving Linux users without guidance.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Provide Bash script examples for retrieving the public IP address of a lab.
  • Mention and link to documentation for Az.LabServices usage on Linux (if available) or clarify platform requirements.
  • Ensure that instructions and examples are presented for both Windows and Linux users, ideally side-by-side.
  • Avoid referencing only Windows tools and modules; include cross-platform alternatives where possible.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-bicep.md .../main/articles/lab-services/how-to-create-lab-bicep.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 provides deployment instructions using Azure CLI and Azure PowerShell, with PowerShell examples given equal prominence to CLI. However, there is a lack of explicit Linux-specific guidance or examples, such as shell scripting or Linux environment considerations. PowerShell, a Windows-centric tool, is featured throughout, and there is no mention of Linux tools or patterns (e.g., Bash, SSH, Linux file paths). The documentation assumes parity between CLI and PowerShell but does not address Linux user workflows or highlight any Linux-specific nuances.
Recommendations
  • Add explicit Linux shell (Bash) examples for deployment steps, including file path conventions and environment setup.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users (e.g., installation, authentication).
  • Include notes or sections on running Bicep and ARM deployments from Linux environments, addressing common issues (e.g., file permissions, case sensitivity).
  • Mention Linux tools (such as curl, jq) where relevant, especially for REST API or template manipulation.
  • Balance PowerShell and CLI examples by sometimes leading with CLI, which is more universal, and avoid implying PowerShell is the default.
  • Add troubleshooting tips for Linux users if there are known platform-specific issues.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-plan-bicep.md .../articles/lab-services/how-to-create-lab-plan-bicep.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 provides deployment and management instructions using Azure CLI and Azure PowerShell, but does not offer any Linux-specific shell examples (such as Bash), nor does it mention Linux tools or patterns. PowerShell is presented as an equal alternative to CLI, but CLI examples are generic and not tailored for Linux users. There is no discussion of platform-specific considerations, and PowerShell (a Windows-centric tool) is featured prominently throughout. The documentation does not address Linux shell usage, nor does it clarify cross-platform differences in commands or environment setup.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for CLI commands.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., file paths, environment variables).
  • Mention installation and usage of Azure CLI on Linux systems, including prerequisites and troubleshooting tips.
  • Reduce emphasis on PowerShell, or clarify its cross-platform availability, and provide guidance for Linux users who may not have PowerShell installed.
  • Include a section or note about platform differences, ensuring Linux users are aware of any steps that differ from Windows.
  • Where file paths or command syntax differ between Windows and Linux, provide both variants.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-python.md ...main/articles/lab-services/how-to-create-lab-python.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 referencing Windows-specific VM images (e.g., 'microsoftwindowsdesktop.windows-11.win11-21h2-pro') without mentioning or providing examples for Linux images. The connection profile in the code sample enables RDP (a Windows protocol) and disables SSH (commonly used for Linux), further reinforcing a Windows-centric approach. Additionally, the 'Next steps' section highlights Azure PowerShell and Az.LabServices cmdlets, which are more commonly associated with Windows environments, without mentioning equivalent CLI or Linux-friendly tools.
Recommendations
  • Include examples using Linux VM images (e.g., Ubuntu, CentOS) in addition to Windows images.
  • Demonstrate connection profiles that enable SSH access (webSshAccess/clientSshAccess) for Linux VMs.
  • In the 'Next steps' section, add references to Azure CLI and relevant Linux command-line tools for managing labs.
  • Where possible, provide parallel code snippets or configuration options for both Windows and Linux scenarios.
  • Clarify in the documentation that both Windows and Linux labs are supported, and guide users on how to select and configure each.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-enable-nested-virtualization-template-vm-using-script.md ...-enable-nested-virtualization-template-vm-using-script.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All setup instructions for enabling nested virtualization are exclusively for Windows environments, specifically Windows 11 and Windows Server, using PowerShell scripts and Windows GUI tools. Hyper-V is the only supported virtualization platform, and Linux is only mentioned as a guest OS inside nested VMs, not as a host or for configuration. There are no instructions or examples for enabling nested virtualization on Linux-based template VMs, nor for using Linux-native virtualization technologies (e.g., KVM, QEMU). Troubleshooting and connectivity examples also rely on Windows tools and PowerShell cmdlets.
Recommendations
  • Add explicit statements about Linux support or limitations for nested virtualization in Azure Lab Services.
  • If Linux-based template VMs are supported, provide equivalent instructions for enabling nested virtualization using Linux tools (e.g., KVM, QEMU, libvirt).
  • Include Linux command-line examples for networking and connectivity configuration, such as using iptables, firewalld, or netplan.
  • Present setup instructions for both Windows and Linux hosts in parallel tabs or sections, rather than only Windows.
  • Clarify whether Hyper-V is the only supported virtualization platform, and if so, explain why alternatives are not available.
  • Offer troubleshooting steps for common Linux guest VM issues, not just Hyper-V/Windows-specific problems.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-classroom-labs.md .../articles/lab-services/how-to-manage-classroom-labs.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 page demonstrates a Windows bias by referencing PowerShell (Az.LabServices module) as the only CLI automation tool for managing labs, without mentioning Linux-friendly alternatives (such as Azure CLI or REST API). Windows and Linux VM images are mentioned, but Windows patterns (like remote desktop) are described first, and Linux-specific instructions are relegated to notes or linked articles. No Linux shell or cross-platform CLI examples are provided, and the only automation example is PowerShell, which is traditionally Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for managing labs, alongside PowerShell.
  • Explicitly mention cross-platform management options, such as Azure CLI, and provide sample commands for Linux/macOS users.
  • When discussing remote access, present SSH (Linux) and RDP (Windows) options together, rather than focusing on Windows patterns first.
  • Include troubleshooting and automation guidance for Linux users, not just PowerShell.
  • Ensure that all steps and screenshots are applicable to both Windows and Linux users, or clearly indicate platform-specific differences.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/quick-create-connect-lab.md ...main/articles/lab-services/quick-create-connect-lab.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 exclusively describes creating and connecting to a Windows-based lab VM, with all examples and screenshots focused on Windows 11 Pro and Remote Desktop (RDP) as the connection method. There is no mention of Linux VM images, Linux connection methods (e.g., SSH), or parity for Linux users. The documentation implicitly prioritizes Windows by default and omits Linux alternatives.
Recommendations
  • Include examples for creating labs with Linux-based VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Provide instructions and screenshots for connecting to Linux VMs using SSH, including guidance for both Windows and Linux clients.
  • Mention Linux VM image options in the 'Virtual machine image' selection step and clarify how to enable them.
  • Add troubleshooting and cleanup instructions specific to Linux VMs where relevant.
  • Ensure that introductory and summary sections acknowledge support for both Windows and Linux labs.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/setup-guide.md ...re-docs/blob/main/articles/lab-services/setup-guide.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 shows a moderate Windows bias. Windows-specific tools and patterns (such as OneDrive, Microsoft Office, and RDP client recommendations) are mentioned before or in more detail than Linux equivalents. Automatic shutdown is described as a Windows feature, and instructions for setting up a Windows template VM are called out, while Linux setup is not similarly highlighted. Linux connection methods (SSH, RDP) are mentioned, but without detailed guidance or parity in examples. There is a lack of Linux-specific setup instructions and cost-control features.
Recommendations
  • Provide equivalent, detailed instructions for setting up Linux template VMs, including configuring common Linux tools and storage options.
  • Mention Linux-first or cross-platform alternatives for saving work (e.g., Nextcloud, generic SFTP, or other cloud storage options) alongside OneDrive.
  • Clarify whether automatic shutdown on disconnect is available for Linux VMs and provide setup instructions if possible.
  • Include Linux-specific examples and recommendations for connecting to VMs (e.g., SSH clients, Linux RDP clients, and GUI setup steps).
  • Ensure that references to Windows tools and features are balanced with Linux equivalents, and avoid presenting Windows options first unless justified by usage data.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/troubleshoot-lab-creation.md ...ain/articles/lab-services/troubleshoot-lab-creation.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 displays a moderate Windows bias, primarily through the exclusive mention of a PowerShell script for quota querying, without providing equivalent Linux/bash examples. The scripting example is presented as the only automation option, implicitly prioritizing Windows tooling. No Linux-specific tools or cross-platform alternatives are referenced, and the PowerShell example is highlighted in a tip box, giving it prominence.
Recommendations
  • Provide equivalent bash or Azure CLI script examples for quota querying and other automation tasks.
  • Explicitly mention that PowerShell scripts can be run on Linux and macOS, or offer platform-agnostic alternatives.
  • When referencing scripts or tools, present both Windows and Linux options side-by-side, or link to cross-platform documentation.
  • Add notes or sections for Linux users, clarifying how to perform troubleshooting steps using Linux-native tools.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/troubleshoot-connect-lab-vm.md ...n/articles/lab-services/troubleshoot-connect-lab-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (PsPing), linking to Windows performance tuning guides, and providing troubleshooting steps and examples that are primarily relevant to Windows environments (e.g., RDP, Windows client experience settings, PowerShell references). There is a lack of Linux-specific troubleshooting guidance, examples, or tool recommendations, and Windows terminology and tools are mentioned first or exclusively in several sections.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as SSH connectivity troubleshooting, and reference common Linux tools (e.g., ping, traceroute, nmap) for network diagnostics.
  • Provide parity in tool recommendations by mentioning cross-platform or Linux alternatives to PsPing, such as 'iperf', 'mtr', or 'netcat'.
  • Add links to Linux documentation for performance tuning and remote access (e.g., SSH server configuration, firewall settings).
  • When discussing client experience settings or remote access, include both Windows (RDP) and Linux (SSH, xrdp, VNC) scenarios.
  • Ensure that PowerShell references are accompanied by equivalent Bash or shell command examples for Linux users.
  • Review all troubleshooting steps to ensure they are applicable to both Windows and Linux lab VMs, or clearly indicate when a step is OS-specific.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/upload-custom-image-shared-image-gallery.md ...b-services/upload-custom-image-shared-image-gallery.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 is heavily focused on Windows environments and tooling. All examples and instructions assume the use of Windows, Hyper-V, and PowerShell, with no mention of Linux equivalents or cross-platform alternatives. Windows-specific tools and patterns (Hyper-V Manager, PowerShell cmdlets, Windows registry, Windows Firewall, etc.) are referenced exclusively and before any possible Linux options. There are no examples or guidance for importing images from Linux-based labs or using Linux virtualization tools.
Recommendations
  • Add equivalent instructions for importing Linux images, including preparation steps for common Linux distributions.
  • Include examples using Linux virtualization tools such as KVM, VirtualBox, or VMware, and detail how to create and convert disk images (e.g., using qemu-img).
  • Provide PowerShell alternatives for Linux, such as Bash scripts or CLI commands.
  • Mention cross-platform tools and workflows (e.g., AzCopy, Azure CLI) with examples for both Windows and Linux.
  • Clarify in the introduction that the guide is Windows-specific, or provide links to Linux-focused documentation if available.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-plan-bicep.md .../articles/lab-services/how-to-create-lab-plan-bicep.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment and management instructions using both Azure CLI and Azure PowerShell, but PowerShell is given equal or sometimes more prominence than CLI, and there are no explicit Linux shell/bash examples or references. The use of PowerShell-specific cmdlets and terminology may be less familiar to Linux users. There is no mention of Linux-specific tools, shell environments, or command-line patterns, and the documentation does not clarify that Azure CLI commands are cross-platform or show them in a Linux context.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and show example commands in a bash shell context (e.g., using $ instead of az> or PS> prompts).
  • Add Linux shell-specific notes or examples, such as using bash variables or scripting patterns.
  • Clarify that PowerShell is primarily a Windows tool, and provide guidance for Linux users who may not have PowerShell installed.
  • Where PowerShell is mentioned, ensure that CLI (bash) examples are given equal or greater prominence, and consider listing CLI examples first.
  • Include a section or note on installing and using Azure CLI on Linux, and link to relevant documentation.
  • Avoid using Windows-centric terminology (such as 'local computer' without specifying OS) or clarify when instructions are OS-agnostic.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-create-lab-with-advanced-networking.md ...rvices/tutorial-create-lab-with-advanced-networking.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias, particularly in the sections on enabling ICMP and connecting to lab VMs. Only Windows 11 is used as the example VM image, and instructions for enabling ICMP are provided exclusively for Windows via PowerShell. There are no equivalent Linux examples or commands for enabling ICMP or connecting to Linux VMs (e.g., via SSH). The documentation also references RDP before SSH and does not provide Linux command-line examples for tasks like firewall configuration or connectivity testing.
Recommendations
  • Provide parallel Linux examples throughout, especially for enabling ICMP (e.g., using ufw or firewalld commands).
  • When showing how to connect to VMs, include both RDP (for Windows) and SSH (for Linux) instructions, with equal prominence.
  • When suggesting VM images, mention both Windows and popular Linux distributions (e.g., Ubuntu, CentOS) and show how to select them.
  • In sections that use PowerShell, add equivalent bash or shell commands for Linux users.
  • Ensure screenshots and walkthroughs are balanced between Windows and Linux scenarios, or clarify when steps are OS-specific.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/administrator-guide-1.md ...ob/main/articles/lab-services/administrator-guide-1.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is generally platform-neutral but contains subtle Windows bias in certain sections. Specifically, endpoint management guidance and tooling (e.g., Sysinternals PsGetSid) are Windows-specific, and the discussion of endpoint management focuses on Windows VM scenarios. There are no equivalent Linux tools or management patterns mentioned, and no Linux-specific examples are provided for endpoint management or content filtering. The only explicit Linux mention is in the context of a Data Science VM image, but operational guidance and tooling are Windows-centric.
Recommendations
  • For endpoint management, include information about Linux VM management, such as handling machine IDs (e.g., /etc/machine-id) and tools for verifying uniqueness on Linux.
  • Mention Linux-compatible endpoint management solutions (e.g., Ansible, Puppet, Chef, Azure Automation for Linux) alongside Windows tools.
  • When referencing tools like PsGetSid, provide Linux equivalents (e.g., commands to check machine IDs or hostnames).
  • In the content filtering section, suggest Linux-compatible filtering software and note any differences in managing admin/non-admin accounts on Linux VMs.
  • Review all operational examples and ensure both Windows and Linux scenarios are covered where applicable, especially in sections discussing VM preparation, management, and security.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/administrator-guide.md ...blob/main/articles/lab-services/administrator-guide.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (such as SysPrep and PsGetSid) and scenarios are discussed. The GPU VM size tables also repeatedly specify '(Windows only)' for certain visualization scenarios, but do not clarify Linux support or provide Linux equivalents. There are no PowerShell-heavy examples or command-line instructions, but Linux tools, patterns, or management scenarios are not mentioned or are missing where relevant.
Recommendations
  • In the 'Endpoint management' section, add information about Linux endpoint management tools and considerations (e.g., how to ensure unique host identifiers for Linux VMs, or mention tools like cloud-init).
  • Where Windows-only GPU VM sizes are listed, clarify Linux support for GPU visualization workloads, or explicitly state if Linux is not supported for those VM sizes.
  • If mentioning Windows tools (e.g., SysPrep, PsGetSid), provide Linux equivalents or note how similar tasks are handled on Linux (e.g., using 'hostnamectl', 'machine-id', or other Linux imaging best practices).
  • Add examples or notes for Linux-based labs where relevant, especially in sections discussing VM image preparation, endpoint management, and content filtering.
  • Review for other sections where Windows-specific terminology or tools are used, and ensure Linux parity or at least mention of Linux alternatives.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/concept-nested-virtualization-template-vm.md ...-services/concept-nested-virtualization-template-vm.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows and Hyper-V. It assumes the use of Windows-based lab VMs, exclusively describes enabling and managing nested virtualization with Hyper-V, and provides only PowerShell/Windows tool examples. Linux is only mentioned as a possible guest OS, with no instructions or parity for Linux-based host VMs or alternative virtualization technologies. There are no Linux command-line examples, and all configuration steps and recommendations are Windows/Hyper-V-centric.
Recommendations
  • Clarify early that nested virtualization is only supported on Windows-based lab VMs, but provide guidance or links for Linux users where possible.
  • Add examples or notes for Linux-based virtualization solutions (e.g., KVM, QEMU) if/when supported, or explicitly state their lack of support.
  • Where PowerShell or Hyper-V tools are used, provide Linux equivalents or explain the absence of such features on Linux.
  • Include Linux command-line examples for any steps that could be performed on Linux, or clearly state that such steps are not applicable.
  • In the 'Best practices for running Linux on Hyper-V' section, summarize key points directly in the doc instead of only linking out, and provide troubleshooting tips specific to Linux guest VMs.
  • If Linux-based host VMs are not supported, make this limitation prominent at the top of the documentation.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-bring-custom-linux-image-vhd.md ...es/lab-services/how-to-bring-custom-linux-image-vhd.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing primarily on Windows-based tooling and workflows (Hyper-V Manager, PowerShell) for preparing and converting Linux images. Linux-native hypervisors and tools (such as KVM, qemu-img, or Linux CLI workflows) are only briefly mentioned or referenced as alternatives, without step-by-step guidance. The primary example assumes a Windows host and does not provide equivalent Linux-based instructions.
Recommendations
  • Add a parallel section detailing how to prepare, convert, and upload a Linux image using Linux-native tools (e.g., KVM, qemu-img, libvirt, and Linux CLI).
  • Provide step-by-step instructions for creating and converting VHDs on Linux, including commands for qemu-img and guidance for managing disk formats and sizes.
  • Include examples of uploading VHDs to Azure from a Linux environment, using tools like AzCopy for Linux, Azure CLI, or REST APIs.
  • Ensure that Linux-based workflows are presented with equal prominence and detail as Windows-based workflows, ideally in side-by-side or clearly separated sections.
  • Reference Linux documentation and tools first or equally, rather than defaulting to Windows/Hyper-V as the primary workflow.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-configure-firewall-settings.md ...les/lab-services/how-to-configure-firewall-settings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively provides PowerShell examples and references only the Az.LabServices PowerShell module for retrieving the public IP address of Azure Lab Services labs. There are no examples or instructions for performing the same task using Azure CLI, Bash, or other cross-platform tools. The documentation assumes the user is on Windows or has access to PowerShell, and does not mention or prioritize Linux or macOS workflows.
Recommendations
  • Add equivalent examples using Azure CLI (az lab services) commands, which are cross-platform and work on Linux, macOS, and Windows.
  • Include Bash shell script examples for retrieving the public IP address, especially using Azure CLI.
  • Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation guidance for non-Windows systems.
  • Reorganize the documentation to present cross-platform (CLI/Bash) solutions before or alongside PowerShell examples.
  • Reference relevant Azure CLI documentation and modules, not just PowerShell cmdlets.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-enable-shutdown-disconnect.md ...cles/lab-services/how-to-enable-shutdown-disconnect.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. While it states that both Windows and Linux VMs are supported, the only deep-dive example or troubleshooting link is for Windows shutdown behavior. There are no Linux-specific configuration or troubleshooting examples, and the warning section references only a Windows guide. Linux support is mentioned, but without actionable Linux-focused guidance or parity in examples.
Recommendations
  • Provide a Linux-specific guide or troubleshooting section analogous to the 'Guide to controlling Windows shutdown behavior', covering common Linux shutdown behaviors and how they interact with auto-shutdown.
  • Include concrete Linux command-line examples or screenshots for configuring and verifying auto-shutdown, similar to any Windows examples provided elsewhere.
  • Ensure that references to OS-specific behavior are balanced: if a Windows guide is linked, a Linux equivalent should also be offered.
  • Clarify any differences in user experience or required steps between Windows and Linux VMs, rather than focusing primarily on Windows scenarios.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-classroom-labs.md .../articles/lab-services/how-to-manage-classroom-labs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While it does mention Linux support and provides some Linux-specific notes (such as enabling remote desktop and SSH for Linux VMs), Windows is generally presented as the default or primary scenario. The only command-line management tool mentioned is the Az.LabServices PowerShell module, with no mention of equivalent CLI or scripting options for Linux users. Additionally, the documentation refers to password management behaviors with a Windows-centric default, and Windows terminology and tools are referenced before Linux equivalents.
Recommendations
  • Include Azure CLI examples for managing labs, alongside or instead of PowerShell, to ensure Linux parity.
  • Explicitly mention and link to cross-platform management tools (e.g., Azure CLI, REST API) wherever PowerShell is referenced.
  • When describing features or behaviors that differ between Windows and Linux (such as password management), present both platforms equally and clarify differences in parallel.
  • Add Linux-specific usage examples or screenshots where relevant, such as connecting to Linux VMs via SSH.
  • Avoid presenting Windows tools or workflows as the default; instead, structure documentation to address both Windows and Linux users equally.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-manage-template.md ...articles/lab-services/how-to-create-manage-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools (e.g., Visual Studio) as examples of software to install, mentioning Remote Desktop Protocol (RDP) before Secure Shell (SSH) when describing connection methods, and not providing any Linux-specific examples or guidance. There are no Linux tool examples or screenshots, and the workflow implicitly assumes familiarity with Windows environments.
Recommendations
  • Provide Linux-specific examples of software to install on the template VM (e.g., GCC, Python, or Gedit) alongside Windows examples.
  • When describing connection methods, mention SSH before or equally with RDP, and clarify which OS each method applies to.
  • Include screenshots or instructions that show connecting to Linux-based template VMs.
  • Add notes or sections that address common Linux configuration tasks in lab templates.
  • Ensure parity in troubleshooting and known issues for both Windows and Linux template VMs.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-vm-pool.md ...ob/main/articles/lab-services/how-to-manage-vm-pool.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. References to OS disks and temporary disks use Windows drive letters (C: and D:) exclusively, with no mention of Linux equivalents (such as / or /mnt). There are no Linux-specific examples or terminology, and the documentation assumes familiarity with Windows disk conventions. No Linux or cross-platform command-line examples are provided, and the only references to file systems or data locations are Windows-centric.
Recommendations
  • When referring to OS and temporary disks, include Linux equivalents (e.g., 'C: drive on Windows or / on Linux').
  • Add notes or examples for Linux users where disk paths or conventions differ.
  • Ensure that any screenshots or instructions that are OS-specific are paired with Linux alternatives, or clarify when steps are OS-agnostic.
  • Where possible, use neutral terminology (e.g., 'OS disk' and 'temporary disk') and provide both Windows and Linux context.
  • If there are command-line or scripting examples, provide both PowerShell (Windows) and Bash (Linux) versions.
GitHub Create Pull Request
← Previous Page 4 of 11 Next →