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 126-150 of 272 flagged pages
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-setup-lab-gpu.md
...lob/main/articles/lab-services/how-to-setup-lab-gpu.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows instructions and references before Linux equivalents, omitting detailed Linux walkthroughs in several sections, and focusing on Windows-specific tools (such as Control Panel and Task Manager) for validation. Linux instructions are often relegated to brief notes or links, lacking parity in detail and visual aids.
Recommendations
- Provide step-by-step Linux instructions alongside Windows instructions for manual driver installation, including explicit commands and screenshots where applicable.
- Include Linux-specific validation steps (e.g., using nvidia-smi, lshw, or other CLI tools) with examples and screenshots, not just links.
- Mention Linux support and limitations in VM size tables and usage scenarios, not only as parenthetical notes.
- Balance the order of presentation: present Windows and Linux instructions in parallel or alternate order, rather than always listing Windows first.
- Add Linux equivalents for Windows tools (e.g., show how to check GPU usage with nvidia-smi or glxinfo instead of only Task Manager/NVIDIA Control Panel).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell (Az.LabServices PowerShell module) as the only CLI automation tool, mentioning it in the main workflow and in the 'Next steps' without Linux CLI or cross-platform alternatives. Windows and Linux are both mentioned for VM images, but Windows patterns (e.g., remote desktop, password management) are described first or in more detail, and there are no explicit Linux shell or CLI examples. The documentation lacks parity in presenting Linux-native management tools or workflows, and does not provide Linux command-line automation options.
Recommendations
- Include Azure CLI and/or Azure REST API examples for managing labs, which are cross-platform and work on Linux, macOS, and Windows.
- When referencing PowerShell modules, also mention equivalent Azure CLI commands or scripts.
- Provide explicit Linux shell (bash) examples for common management tasks, such as creating, listing, or deleting labs.
- Ensure that Linux-specific workflows (e.g., SSH access, password management) are described with the same level of detail as Windows workflows.
- Add references to Linux-friendly tools and automation patterns alongside Windows/PowerShell tools, not just as an afterthought or in separate articles.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-reset-and-redeploy-vm.md
.../articles/lab-services/how-to-reset-and-redeploy-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific drive letters (C: and D:) when discussing OS and temporary disks, without mentioning Linux equivalents. Additionally, it lists PowerShell as a command-line automation tool for redeploying and reimaging VMs, but does not mention or provide examples for Linux command-line tools (such as Azure CLI or Bash). There are no Linux-specific instructions or examples, and Windows terminology appears first and exclusively.
Recommendations
- When referencing OS and temporary disks, include Linux equivalents (e.g., /dev/sda1 for OS disk, /mnt for temporary disk) alongside Windows drive letters.
- Provide Linux command-line examples using Azure CLI (az lab services ...) for redeploying and reimaging VMs, not just PowerShell.
- Explicitly mention that the instructions apply to both Windows and Linux VMs, and clarify any differences in behavior or terminology.
- Where screenshots or UI elements reference Windows-specific concepts, add notes or images for Linux users if the experience differs.
- Review all technical references and ensure Linux parity in both terminology and tooling.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-setup-lab-gpu-1.md
...b/main/articles/lab-services/how-to-setup-lab-gpu-1.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific validation steps and tools (such as NVIDIA Control Panel and Task Manager) before Linux equivalents, providing detailed instructions and screenshots for Windows but only linking out for Linux. Linux instructions are often referenced via links rather than being included inline, and there are no Linux-specific screenshots or command examples.
Recommendations
- Provide Linux validation steps inline, including example commands (e.g., using nvidia-smi) and expected outputs, rather than only linking to external documentation.
- Include screenshots or terminal outputs for Linux GPU validation, similar to the Windows Task Manager and Control Panel screenshots.
- Present Windows and Linux instructions in parallel or in clearly separated sections, ensuring neither is consistently prioritized over the other.
- Mention Linux tools (such as nvidia-smi, lshw, or glxinfo) for GPU validation and management, and provide step-by-step usage instructions.
- Ensure that all manual installation and validation steps are equally detailed for both Windows and Linux, including troubleshooting tips.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All setup instructions for enabling nested virtualization focus exclusively on Windows 11 and Windows Server, using PowerShell scripts and Windows GUI tools. Hyper-V is the only virtualization platform discussed, with no mention of Linux-based alternatives (such as KVM or VirtualBox), nor are there any instructions for enabling nested virtualization on Linux template VMs. Even troubleshooting and connectivity examples assume a Windows host, and Linux is only mentioned as a guest OS inside Hyper-V VMs.
Recommendations
- Add explicit instructions for enabling nested virtualization on Linux-based template VMs, including supported distributions and required configuration steps (e.g., enabling KVM, configuring libvirt, etc.).
- Provide parity in examples by including Linux command-line instructions (e.g., using SSH, virsh, or other Linux-native tools) alongside PowerShell and Windows GUI steps.
- Mention and document support (or lack thereof) for Linux virtualization technologies (KVM, QEMU, VirtualBox) in Azure Lab Services, and clarify any limitations.
- Include troubleshooting steps and connectivity examples for Linux hosts and guests, not just Windows/Hyper-V scenarios.
- Clearly state at the beginning if only Windows-based nested virtualization is supported, and provide guidance or alternatives for Linux users if so.
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 →
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 instructions focused on Windows (e.g., selecting 'Windows 11 Pro' as the VM image, connecting via Remote Desktop). There is no mention of Linux-based labs, Linux VM images, or alternative connection methods such as SSH, nor are any Linux tools or workflows referenced.
Recommendations
- Include parallel instructions and screenshots for creating a Linux-based lab VM (e.g., selecting Ubuntu or another Linux image).
- Provide examples of connecting to Linux VMs using SSH, including how to download SSH keys or connection details.
- Mention Linux-compatible remote desktop solutions if relevant, or clarify differences in connection methods between Windows and Linux labs.
- Update the description and steps to indicate that both Windows and Linux labs are supported, or clarify if this quickstart is intentionally Windows-specific.
- Add troubleshooting and cleanup guidance relevant to Linux-based labs.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows, such as recommending the Microsoft Remote Desktop client for VM access and providing detailed instructions for setting up Windows template VMs (including OneDrive and Office). Linux alternatives are mentioned but lack equivalent detail or step-by-step guidance. There are no Linux-specific examples or instructions for configuring Linux template VMs, and Windows features (like automatic shutdown on disconnect) are described in more detail.
Recommendations
- Provide parallel, detailed instructions for setting up Linux template VMs, including common tasks such as installing RDP and GUI packages, configuring SSH, and integrating with external storage solutions (e.g., mounting cloud drives).
- When discussing VM access, recommend and link to popular Linux RDP/SSH clients (e.g., Remmina, KRDC, or command-line SSH) alongside the Microsoft Remote Desktop client.
- Ensure that cost control features (such as automatic shutdown) are clearly explained for both Windows and Linux VMs, including any differences in configuration or behavior.
- Include Linux-specific examples and screenshots where appropriate, and avoid assuming Windows as the default operating system.
- Mention open-source or cross-platform alternatives for tools like OneDrive and Office, or provide guidance for integrating similar solutions in Linux environments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/troubleshoot-access-lab-vm.md
...in/articles/lab-services/troubleshoot-access-lab-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by predominantly referencing Windows-specific paths (e.g., C:\WindowsAzure), tools (e.g., Windows System Restore, OneDrive), and drive letters (C: and D:). Troubleshooting steps and data storage recommendations are centered around Windows, with little to no mention of Linux equivalents or guidance for Linux-based lab VMs. Linux troubleshooting tools, file paths, and storage solutions are absent.
Recommendations
- Include parallel Linux examples and instructions wherever Windows-specific steps are provided (e.g., mention relevant Linux file paths, commands, and troubleshooting tools).
- When referencing Windows System Restore, add a section or note about equivalent Linux recovery options (such as using Timeshift, rsnapshot, or manual restoration from backups).
- When discussing disk drives (C:, D:), clarify how these map to Linux (e.g., /, /mnt, /tmp) and explain what happens to data on Linux partitions during redeploy/reimage.
- Provide Linux-friendly data storage recommendations (such as using Azure Files, NFS, or other cross-platform cloud storage solutions) in addition to OneDrive.
- Ensure that all troubleshooting steps and examples are presented for both Windows and Linux lab VMs, or clearly indicate when a step is OS-specific.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., PsPing), linking to Windows Remote Desktop client settings, and providing troubleshooting steps and screenshots that are Windows-centric. There are no Linux-specific examples or equivalent Linux troubleshooting tools mentioned, and Windows terminology and tools are presented first or exclusively in several sections.
Recommendations
- Include Linux-specific troubleshooting steps and examples alongside Windows instructions, such as using 'ssh' for connectivity checks or 'ping', 'nmap', and 'traceroute' for network diagnostics.
- Mention cross-platform or Linux-native tools (e.g., 'iperf', 'netcat', 'ss', 'tcpdump') as alternatives to Windows tools like PsPing.
- Provide equivalent guidance for adjusting remote desktop or SSH client settings on Linux (e.g., using Remmina, KRDC, or command-line SSH options).
- Add screenshots or error messages from Linux RDP/SSH clients to balance the Windows-centric visuals.
- Reference Azure CLI and Bash examples in addition to or instead of PowerShell where possible, especially when filtering logs or interacting with Azure resources.
- Ensure that troubleshooting steps are not written with implicit Windows assumptions (e.g., referencing only Windows firewall settings or user management).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows 11 as the example VM image, using Windows PowerShell commands exclusively for enabling ICMP, and omitting equivalent Linux instructions. The workflow for enabling ICMP and connecting to VMs is described solely in the context of Windows, with no parallel guidance for Linux users.
Recommendations
- Include Linux as an example VM image in the lab creation steps, or at least mention it equally alongside Windows.
- Provide equivalent Linux instructions for enabling ICMP (e.g., using ufw or iptables commands to allow ICMP/ping).
- Add Linux-specific connection instructions (e.g., using SSH instead of RDP, and how to open a terminal).
- Where PowerShell or Windows-specific tools are referenced, offer side-by-side Linux alternatives.
- Ensure screenshots and command examples represent both Windows and Linux environments where applicable.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows tools (Hyper-V Manager, PowerShell cmdlets), and there is no mention of Linux-based workflows or alternatives. The process is described exclusively for Windows images, and Linux users are not provided with equivalent guidance or tooling references.
Recommendations
- Add a parallel section or notes for importing Linux images from physical labs, including common Linux imaging tools (e.g., dd, qemu-img) and preparation steps.
- Provide examples using cross-platform tools or mention Linux equivalents where PowerShell or Hyper-V are referenced.
- Clarify in the introduction that the guide is Windows-specific, or expand the scope to cover Linux scenarios.
- Reference Azure documentation for preparing and uploading Linux images, and link to relevant guides.
- Where possible, use Azure CLI or REST API examples, which are cross-platform, instead of only PowerShell.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-setup-lab-gpu-1.md
...b/main/articles/lab-services/how-to-setup-lab-gpu-1.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias: Windows instructions and tools (such as Control Panel, Task Manager, and NVIDIA Control Panel) are described in detail with screenshots, while Linux instructions are referenced via links without in-page examples or screenshots. Windows validation steps are explicit, but Linux validation is only linked. There is also a lack of parity in tool mention and step-by-step guidance for Linux users.
Recommendations
- Provide in-page, step-by-step Linux instructions for driver installation and validation, not just external links.
- Include screenshots of Linux tools (e.g., nvidia-smi output, relevant desktop environment GPU settings) analogous to the Windows screenshots.
- Mention Linux tools (such as nvidia-smi, lshw, or system monitoring utilities) for GPU validation, similar to Task Manager and NVIDIA Control Panel for Windows.
- Present Windows and Linux instructions in parallel sections, or at least alternate which OS is presented first in each section.
- Explicitly state when steps are identical or different between Windows and Linux, to help users understand OS-specific nuances.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-setup-lab-gpu.md
...lob/main/articles/lab-services/how-to-setup-lab-gpu.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows instructions and references before Linux equivalents, omitting Linux-specific examples in several sections, and focusing on Windows tools (such as Control Panel and Task Manager) for validation steps. Linux instructions are often relegated to notes or links, rather than being presented as first-class, step-by-step guidance.
Recommendations
- Provide parallel, step-by-step Linux instructions alongside Windows instructions in all relevant sections, not just as notes or external links.
- Include Linux-specific validation steps, such as using nvidia-smi or lshw, with screenshots where appropriate, similar to the Windows Task Manager and Control Panel examples.
- Explicitly mention Linux support in all tables and descriptions, clarifying which VM sizes and drivers are supported on Linux.
- Where Windows-only features or limitations exist (e.g., certain visualization GPU sizes), clearly state this early and provide Linux alternatives or workarounds if available.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or alternate which OS is presented first in each section.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes the creation and connection to a Windows-based lab VM, with all examples and instructions centered around Windows (e.g., selecting 'Windows 11 Pro' as the VM image, connecting via Remote Desktop). There is no mention of Linux-based lab options, nor are any Linux-specific tools, images, or connection methods (such as SSH) discussed. The documentation assumes the use of Windows tools and workflows throughout.
Recommendations
- Include parallel instructions for creating a Linux-based lab VM, such as selecting an Ubuntu or other Linux image from the Marketplace.
- Provide examples for connecting to Linux VMs, including SSH connection steps for Windows, macOS, and Linux clients.
- Mention and demonstrate the availability of Linux images and their configuration options within Azure Lab Services.
- Clarify in the introduction that both Windows and Linux labs are supported, and provide links or sections for each.
- Ensure troubleshooting and cleanup sections also address Linux-specific scenarios.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/retirement-guide.md
...cs/blob/main/articles/lab-services/retirement-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias, especially in the ordering and emphasis of solutions. Windows-based services (Azure Virtual Desktop, Windows 365 Cloud PC, Microsoft Dev Box) are described in detail and listed before Linux-supporting options. There is a strong focus on Windows desktop experiences, Windows-specific management tools (Intune, Entra ID), and Windows VM scenarios. While Azure DevTest Labs and some partner solutions mention Linux support, there are no Linux-specific examples, workflows, or feature highlights. Linux use cases are only referenced in passing, and there are no explicit instructions or guidance for Linux-based labs.
Recommendations
- Explicitly mention Linux support and scenarios in the main Microsoft solution sections, not just in partner solution summaries.
- Provide Linux-specific examples and workflows, such as setting up a Linux-based lab or using Linux images in Azure DevTest Labs.
- Balance the order of presentation: introduce cross-platform or Linux-supporting solutions before or alongside Windows-centric ones.
- Highlight Linux management and access tools (e.g., SSH, Azure CLI) where relevant, not just Windows tools like Intune or Entra ID.
- Include a comparison table or matrix showing Windows and Linux feature parity across all recommended solutions.
- Add links to Linux-focused documentation or guides for transitioning Linux-based labs.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows (such as RDP and OneDrive), mentioning Windows scenarios and features before Linux equivalents, and lacking detailed Linux-specific setup or examples. Linux is mentioned as an option, but without the same level of guidance or tool integration as Windows.
Recommendations
- Provide parallel, detailed instructions for Linux VM setup, including recommended SSH clients and RDP/GUI installation steps.
- Include examples and guidance for configuring Linux VMs with external storage solutions (e.g., mounting NFS, using Dropbox or other cross-platform tools) alongside OneDrive.
- Offer cost-control and auto-shutdown instructions specific to Linux VMs, clarifying any differences in behavior or setup.
- Ensure that all references to client tools (such as Remote Desktop clients) include Linux-compatible options and are not Windows-centric.
- Where Windows-specific features (like OneDrive or Office setup) are highlighted, provide equivalent Linux alternatives or note their absence.
- Add Linux-focused troubleshooting and best practices sections to match the depth provided for Windows.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/troubleshoot-access-lab-vm.md
...in/articles/lab-services/troubleshoot-access-lab-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., C:\WindowsAzure), tools (e.g., Windows System Restore), and disk drive letters (C: and D:) without providing equivalent Linux examples or guidance. Troubleshooting steps and data storage recommendations are also Windows-centric, with no mention of Linux alternatives or tools.
Recommendations
- Include Linux-specific troubleshooting steps and examples, such as referencing common Linux file paths and commands.
- When mentioning Windows System Restore, provide equivalent Linux recovery or rollback options (e.g., using Timeshift, snapshots, or manual recovery steps).
- Clarify disk references for Linux VMs (e.g., /, /mnt, /tmp) alongside Windows drive letters.
- When discussing storing user data, mention cross-platform solutions (e.g., OneDrive, but also Dropbox, Google Drive, or native Linux options like NFS or rsync).
- Ensure all instructions and examples are presented for both Windows and Linux environments, or clearly indicate when a step is OS-specific.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., PsPing), providing links and troubleshooting steps that focus on Windows environments (such as adjusting client experience settings for RDP via Windows Server documentation), and omitting equivalent Linux troubleshooting examples or commands. Powershell and Windows-centric Azure portal tabs are mentioned, while Linux/SSH troubleshooting is only referenced generically and not exemplified. Linux-specific tools, commands, or user experiences are not addressed, leading to a lack of parity for Linux users.
Recommendations
- Include Linux-specific troubleshooting steps and examples alongside Windows ones, such as using 'ping', 'traceroute', or 'ssh' for connectivity testing.
- When referencing tools like PsPing, also mention cross-platform or Linux-native alternatives (e.g., 'iperf', 'nmap', 'netcat').
- Provide links to both Windows and Linux documentation for adjusting RDP/SSH client settings.
- Ensure that troubleshooting steps for SSH connectivity (common for Linux VMs) are as detailed as those for RDP.
- When referencing Azure portal features or logs, include CLI and Bash examples, not just Powershell.
- Add screenshots or error messages relevant to Linux SSH clients (e.g., OpenSSH errors) in addition to Windows RDP dialogs.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references a PowerShell script as the only example for querying lab quotas, without providing equivalent Bash, Azure CLI, or Linux-native alternatives. This suggests a bias toward Windows tooling and scripting, and does not offer parity for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for querying lab quotas, alongside the PowerShell example.
- When referencing scripts or automation, include cross-platform options and note compatibility.
- Explicitly mention that Azure CLI is available on all platforms and provide examples using it for common administrative tasks.
- Review the documentation for other areas where only Windows-centric tools or scripts are referenced, and add Linux/macOS alternatives where possible.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, particularly in the sections on enabling ICMP (using PowerShell) and creating labs (defaulting to Windows 11 Pro images). There are no equivalent Linux commands or walkthroughs, and Windows tools and patterns are mentioned first or exclusively.
Recommendations
- Provide parallel Linux instructions for enabling ICMP (e.g., using ufw or firewalld commands to allow ICMP on Ubuntu/CentOS).
- Include examples of creating labs with Linux VM images, and note any differences in setup or configuration.
- When discussing remote access, mention SSH (for Linux) and RDP (for Windows) equally, and provide connection instructions for both.
- Add screenshots or command-line examples for Linux environments where relevant.
- Explicitly state that the tutorial applies to both Windows and Linux VMs, and highlight any OS-specific steps.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and tooling references are specific to Windows (Hyper-V, PowerShell, Windows Firewall, SysPrep, etc.), with no mention of Linux-based workflows or alternatives. The process assumes the source image is Windows and the tooling is Windows-centric, with no guidance for users working from Linux environments or with Linux images.
Recommendations
- Include parallel instructions for importing Linux images, including preparation steps (e.g., using qemu-img for disk conversion, cloud-init for initialization, and Linux-specific configuration).
- Provide examples using Linux-native tools (e.g., KVM/virt-manager for VM creation, shell commands for disk management, and Azure CLI for uploads).
- Mention and link to documentation for preparing and uploading Linux VMs to Azure, ensuring users know both Windows and Linux are supported.
- Avoid assuming the reader is using Windows by default; structure the documentation to present both Windows and Linux paths where applicable.
- If the service only supports Windows images, state this explicitly at the beginning to avoid confusion.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows and Hyper-V, with all instructions, examples, and tooling focused exclusively on Windows environments. There are no Linux-based setup instructions, examples, or equivalent tooling mentioned. PowerShell and Hyper-V are assumed as the only options, and Linux is only referenced as a guest OS, not as a host or for management tasks.
Recommendations
- Provide equivalent instructions for enabling and managing nested virtualization using Linux-based hosts (if supported in Azure Lab Services), or clearly state if not supported.
- Include Linux command-line examples (e.g., using KVM/QEMU or libvirt) where possible, or explain why only Hyper-V is supported.
- Mention Linux-native tools and patterns for managing nested VMs, or provide guidance for Linux users.
- If only Windows/Hyper-V is supported, make this limitation explicit at the beginning of the documentation and suggest alternatives for Linux users.
- Add parity in recommendations and troubleshooting sections for Linux environments, or clarify support boundaries.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (e.g., SysPrep, PsGetSid) and scenarios are discussed. There are no equivalent Linux tools or considerations mentioned for endpoint management, nor are Linux-specific examples provided elsewhere. While the document does reference a 'Data Science VM for Linux' in passing, the operational guidance and tooling focus almost exclusively on Windows environments.
Recommendations
- Include Linux-specific endpoint management considerations, such as handling machine IDs (e.g., /etc/machine-id) and tools for verifying uniqueness.
- Provide examples or references for managing Linux VMs in lab environments, including common Linux configuration management or imaging tools (e.g., cloud-init, Ansible, or Linux image generalization).
- When mentioning Windows tools like SysPrep and PsGetSid, also mention Linux equivalents or note if the issue (e.g., SID uniqueness) is not applicable or handled differently on Linux.
- Ensure that examples and operational guidance are balanced between Windows and Linux, especially in sections discussing VM preparation, management, and troubleshooting.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (such as SysPrep and PsGetSid) are mentioned for managing machine SIDs. Additionally, GPU VM sizes for visualization are labeled as '(Windows only)' without Linux alternatives or guidance. There are no Linux-specific endpoint management or content filtering examples, and Windows tools/patterns are referenced exclusively in relevant contexts.
Recommendations
- Include Linux-specific examples and tools for endpoint management (e.g., how to ensure unique machine IDs/SIDs on Linux VMs, such as using cloud-init or other Linux imaging best practices).
- For GPU VM sizes, clarify Linux support or provide Linux-compatible alternatives for visualization workloads, or explicitly state if such options are unavailable.
- In sections discussing tools like SysPrep and PsGetSid, add parallel Linux guidance (e.g., using 'machine-id', 'hostnamectl', or other relevant Linux utilities).
- In content filtering, mention popular Linux-compatible filtering solutions or note any differences in approach for Linux VMs.
- Review all examples and tool recommendations to ensure Linux and Windows parity, or clearly indicate platform-specific limitations.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/connect-virtual-machine-chromebook-remote-desktop.md
...s/connect-virtual-machine-chromebook-remote-desktop.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Microsoft Remote Desktop app (a Microsoft/Windows-centric tool) for connecting to lab VMs from a Chromebook. It provides detailed steps and screenshots for this tool, with only a brief mention of alternative RDP clients (like Chrome Remote Desktop) in a note, and no instructions or examples for using them. The process for connecting to Linux VMs is only mentioned in passing, with no Linux-specific RDP client guidance or parity in examples.
Recommendations
- Provide step-by-step instructions for using alternative, platform-neutral or open-source RDP clients (such as Chrome Remote Desktop, Remmina, or FreeRDP) on Chromebook.
- Include screenshots and examples for connecting to both Windows and Linux VMs, highlighting any differences in the process.
- Mention and link to documentation for configuring and using SSH for Linux VMs, as SSH is often the preferred method for Linux remote access.
- Rephrase recommendations to not exclusively promote Microsoft Remote Desktop, but to present it as one of several supported options.
- Ensure that Linux VM connection workflows are given equal prominence and detail as Windows VM workflows.