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 26-50 of 272 flagged pages
Lab Services
Use Azure Lab Services for hackathon
...docs/blob/main/articles/lab-services/hackathon-labs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. Windows-specific guidance (such as installing and stopping Windows updates, configuring OneDrive, and autoshutdown for Windows VMs) is provided in detail, while equivalent Linux instructions are either missing or referenced only briefly. Windows tools and features (Windows updates, OneDrive, RDP) are mentioned explicitly, but Linux alternatives (such as Linux backup solutions or Linux-specific remote desktop options) are not discussed or are given less prominence. Examples and instructions often prioritize Windows scenarios over Linux, and some Linux-specific steps (like enabling remote desktop) are referenced but not explained in detail.
Recommendations
- Provide equivalent Linux guidance for steps currently focused on Windows, such as backup solutions (e.g., using rsync, Nextcloud, or other Linux-friendly cloud storage options).
- Include detailed instructions for configuring Linux updates and managing update interruptions, similar to the Windows update section.
- Offer parity in remote desktop setup instructions, including alternatives to RDP for Linux (such as VNC, xrdp, or NoMachine), and clarify differences in setup and user experience.
- Mention Linux-specific tools and patterns where Windows tools are referenced (e.g., alternatives to OneDrive for Linux users).
- Ensure that examples and instructions are provided for both Windows and Linux VMs, and avoid prioritizing Windows scenarios unless justified by usage statistics.
- Where features are OS-specific (like autoshutdown for Windows), clarify whether Linux equivalents exist or provide workarounds.
Create Pull Request
Lab Services
How to bring a Linux custom image from an Azure virtual machine.
...b-services/how-to-bring-custom-linux-image-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
Although the documentation is focused on bringing a Linux custom image from an Azure VM, the initial instructions for creating an Azure VM link to Windows-specific guides first (portal, PowerShell, CLI, ARM template), all of which use Windows documentation URLs. There are no explicit Linux CLI or portal examples, and the guidance for VM creation is Windows-centric. Linux-specific instructions are only referenced later for generalizing the image, and there are no Linux command-line examples or Linux portal walkthroughs provided.
Recommendations
- Update the VM creation step to link to Linux-specific guides (e.g., /azure/virtual-machines/linux/quick-create-portal, /azure/virtual-machines/linux/quick-create-cli, /azure/virtual-machines/linux/quick-create-powershell).
- Provide explicit Linux command-line examples for VM creation using Azure CLI and PowerShell.
- Ensure that Linux tools and patterns are mentioned before or alongside Windows equivalents when the context is Linux-focused.
- Add screenshots or step-by-step instructions for creating Linux VMs in the Azure portal.
- Review all links and references to ensure they point to Linux documentation when the article is about Linux images.
Lab Services
Manage labs in Azure Lab Services when using lab accounts| Microsoft Docs
.../articles/lab-services/how-to-manage-classroom-labs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias: PowerShell (Az.LabServices) is mentioned as the only CLI automation tool, with no reference to Linux-native alternatives (e.g., Azure CLI, Bash scripts). Windows-centric patterns (such as password management) are described first, and Linux-specific instructions are only given as exceptions or notes. There are no Linux shell or Azure CLI examples for managing labs, and Windows tools are referenced without Linux parity.
Recommendations
- Add examples for managing labs using Azure CLI and Bash scripts, suitable for Linux users.
- Mention Linux-native automation options alongside PowerShell, such as az labservices commands if available.
- Ensure that instructions for connecting to Linux VMs (SSH, graphical desktop) are as detailed and prominent as those for Windows.
- Present Windows and Linux patterns in parallel, rather than describing Windows defaults first and Linux as exceptions.
- Include troubleshooting and management steps relevant to Linux users, such as SSH key management and Linux authentication flows.
Lab Services
Connect to a lab VM from Chromebook
...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 demonstrates bias toward Windows by recommending the Microsoft Remote Desktop app as the primary (and only detailed) RDP client for Chromebook users. The instructions and screenshots exclusively feature Microsoft's tool, with only a brief mention of alternatives like Chrome Remote Desktop, which is discouraged and not documented. The process for connecting to Linux VMs is mentioned, but no Linux-specific RDP client or configuration guidance is provided, nor is there parity in example depth for Linux VMs.
Recommendations
- Provide step-by-step instructions for connecting to Linux VMs using open-source or third-party RDP clients available on Chrome OS, such as Remmina, KRDC, or Chrome Remote Desktop.
- Include screenshots and examples for connecting to both Windows and Linux VMs, ensuring equal coverage.
- Document any additional configuration steps required for Linux VMs, such as enabling xrdp or similar services, and link to relevant guides.
- Clarify the differences in connection workflows between Windows and Linux VMs, and avoid language that implies Microsoft tools are the only or preferred option.
- Add a comparison table of RDP clients for Chrome OS, listing features, compatibility, and setup requirements for both Windows and Linux VM scenarios.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments. The only VM image referenced in the Python example is a Windows 11 image, with no mention of Linux alternatives. Connection profiles are configured for RDP (Windows remote desktop) rather than SSH (Linux remote access). In the 'Next steps' section, only Azure PowerShell and Az.LabServices cmdlets (Windows-centric tools) are mentioned, with no reference to Bash, CLI, or Linux-native tooling. There are no examples or guidance for creating Linux-based labs or using Linux tools.
Recommendations
- Provide examples using Linux VM images (e.g., Ubuntu, CentOS) in addition to Windows.
- Show how to configure SSH access in the connection profile for Linux labs.
- Include references and links to Azure CLI and Bash scripting for lab management.
- Mention Linux-compatible authentication and management approaches in prerequisites and next steps.
- Ensure parity in documentation by offering both Windows and Linux scenarios for lab creation, management, and cleanup.
Lab Services
Lab Services administrator guide
...blob/main/articles/lab-services/administrator-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and scenarios (such as SysPrep, SIDs, PsGetSid, and endpoint management with Microsoft Configuration Manager) are discussed in detail, while Linux equivalents or considerations are not mentioned. GPU VM sizes for visualization are marked as '(Windows only)' without Linux alternatives or guidance. The only explicit OS example is the Data Science VM for Linux, but operational and management examples focus on Windows. There are no PowerShell-heavy examples, but Windows-centric patterns and tools are referenced before or instead of Linux options.
Recommendations
- Include Linux-specific endpoint management guidance and tools (e.g., mention Ansible, Puppet, or Linux imaging/generalization processes).
- Clarify how SIDs and machine identity concerns apply (or do not apply) to Linux VMs, and provide Linux-specific instructions for image generalization.
- For GPU VM sizes, specify Linux support and provide examples or guidance for Linux-based visualization workloads.
- Where Windows-only tools (e.g., SysPrep, PsGetSid, Configuration Manager) are mentioned, add Linux equivalents or note differences in management requirements.
- Add examples of lab creation, management, and customization for Linux VMs, including content filtering and user account management.
Lab Services
Administrator guide using lab accounts | Microsoft Docs
...ob/main/articles/lab-services/administrator-guide-1.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Endpoint management' section, where Windows-specific tools (SysPrep, PsGetSid) and Windows VM behaviors (machine SIDs) are discussed exclusively. There are no equivalent Linux examples or mentions of Linux endpoint management tools or patterns. The only explicit Linux reference is in the context of VM images (Data Science VM for Linux), but operational and management examples are Windows-centric. Windows tools are mentioned before any Linux alternatives, and Linux scenarios for endpoint management are missing.
Recommendations
- Add examples and guidance for managing Linux VMs in endpoint management, such as handling host identity, SSH keys, or Linux-specific configuration tools.
- Mention Linux equivalents to SysPrep (e.g., cloud-init, waagent) and discuss how Linux VMs are generalized and provisioned in Azure Lab Services.
- Include references to Linux endpoint management solutions (e.g., Ansible, Puppet, Chef) and how they interact with Lab Services.
- Provide parity in troubleshooting and verification tools for Linux (e.g., commands to check machine identity, hostname, or other relevant identifiers).
- Review other sections for implicit Windows-first assumptions and ensure Linux scenarios are described with equal detail.
Lab Services
Nested virtualization in Azure Lab Services
...-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 page exhibits a strong Windows bias. It exclusively discusses nested virtualization in the context of Hyper-V, which is only available on Windows-based lab VMs. All configuration steps, tooling, and examples reference Windows technologies (Hyper-V, PowerShell, VHDX). There are no Linux-specific instructions, examples, or parity for Linux-based virtualization tools (such as KVM or VirtualBox). Linux is only mentioned as a possible guest OS, not as a host or in any configuration context.
Recommendations
- Add guidance and examples for nested virtualization using Linux-based hosts (e.g., KVM, QEMU) if supported by Azure Lab Services.
- Include Linux command-line equivalents for configuration steps, such as creating and managing nested VMs.
- Mention Linux virtualization tools and patterns (e.g., libvirt, virt-manager) where appropriate.
- Clarify whether nested virtualization is fundamentally limited to Windows/Hyper-V in Azure Lab Services, and if so, explain the technical reasons.
- Provide more detailed instructions for running Linux guest VMs, including integration services, performance tuning, and troubleshooting.
- If Linux hosts are not supported, make this limitation explicit early in the documentation.
Lab Services
Connect to Azure Lab Services VMs from Mac
...services/connect-virtual-machine-mac-remote-desktop.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows a Windows bias by exclusively recommending the 'Windows App' (a Microsoft tool) for RDP connections from Mac, without mentioning alternative RDP clients commonly used on Mac or Linux. The instructions focus on connecting to Windows VMs, with Linux VM connection options (SSH, RDP) mentioned only in passing and without detailed guidance. There are no examples or recommendations for using open-source or cross-platform RDP clients, and Linux tools/patterns are absent from the main workflow.
Recommendations
- Include instructions for using popular cross-platform RDP clients on Mac, such as Microsoft Remote Desktop, FreeRDP, or Royal TSX.
- Provide parity by showing how to connect to both Windows and Linux VMs, including SSH and RDP workflows for Linux VMs.
- Mention open-source alternatives to 'Windows App' and explain their installation and usage.
- Reorder content to present cross-platform solutions first, or in parallel, rather than focusing on Microsoft-branded tools.
- Add troubleshooting tips relevant to Linux VMs and non-Windows RDP clients.
Lab Services
Use Azure Lab Services for hackathon
...docs/blob/main/articles/lab-services/hackathon-labs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate 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 are either missing or referenced only briefly. Windows tools and features (Windows updates, OneDrive) are discussed with links to dedicated guides, but Linux alternatives (e.g., backup solutions, update management) are not mentioned. Examples and instructions tend to focus on Windows first, with Linux guidance limited to enabling remote desktop and SSH.
Recommendations
- Provide equivalent Linux guidance for VM preparation, such as instructions for updating Linux systems and managing updates to avoid interruptions.
- Include Linux alternatives for backup solutions (e.g., integration with Dropbox, Google Drive, or other cloud storage options).
- Clarify autoshutdown behavior for Linux VMs and provide configuration instructions if available.
- Ensure examples and instructions are presented for both Windows and Linux, ideally side-by-side, to improve parity.
- Mention Linux-specific tools or patterns where relevant, such as package managers, desktop environments, and remote access clients.
Lab Services
Import a Linux image from a physical lab
...es/lab-services/how-to-bring-custom-linux-image-vhd.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by primarily describing the process of importing a Linux image using Windows-based tools such as Hyper-V Manager and PowerShell. The instructions and screenshots focus on Windows workflows, with only brief mentions of Linux alternatives (e.g., KVM, qemu) and no step-by-step guidance for Linux users. Upload instructions reference Windows-specific documentation and tools before mentioning cross-platform options. Linux-native hypervisors and workflows are not covered in detail.
Recommendations
- Add a parallel section detailing how to create and prepare a Linux image using Linux-native hypervisors (e.g., KVM, VirtualBox) and tools.
- Provide step-by-step instructions for converting and resizing disks using Linux command-line utilities (e.g., qemu-img, dd).
- Include Linux-specific examples for uploading VHDs to Azure, such as using AzCopy or Azure CLI from a Linux terminal.
- Reference Linux documentation and workflows before or alongside Windows equivalents, ensuring parity in guidance.
- Add screenshots and command examples for Linux environments to match the detail provided for Windows/Hyper-V.
- Clarify which steps are platform-agnostic and which are specific to Windows or Linux, helping users choose the appropriate workflow.
Lab Services
Firewall settings for Azure Lab Services
...les/lab-services/how-to-configure-firewall-settings.md
High Priority
View Details →
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 determining the public IP address of Azure Lab Services VMs. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform tools. The documentation assumes a Windows environment and does not mention or prioritize Linux alternatives.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
- Provide Bash script snippets for retrieving the public IP address, demonstrating how Linux users can accomplish the same task.
- Reference both PowerShell and Azure CLI documentation, and clarify which tools are available on which platforms.
- Reorder examples or provide parallel instructions so that Linux and Windows users are equally supported.
- Explicitly mention that PowerShell Core is available on Linux and macOS, if recommending PowerShell, and provide installation guidance.
Lab Services
How to bring a Linux custom image from an Azure virtual machine.
...b-services/how-to-bring-custom-linux-image-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
Although the documentation is focused on bringing a Linux custom image from an Azure VM, the instructions for creating the VM reference Windows-specific documentation and tools first (Azure portal, PowerShell, CLI, ARM template), and all example links point to Windows VM creation guides. There are no direct links or examples for creating Linux VMs, and no Linux-specific command-line examples are provided, despite the Linux context.
Recommendations
- Update the VM creation step to reference Linux-specific documentation and examples, such as links to Azure portal, CLI, and ARM template guides for Linux VMs.
- Provide Linux-specific command-line examples (e.g., Azure CLI commands for Linux VM creation).
- Ensure that Linux tools and patterns are mentioned before or alongside Windows equivalents in all instructions.
- Review all linked resources to ensure Linux parity and add Linux-focused alternatives where missing.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias. PowerShell is presented as a primary deployment method alongside Azure CLI, with explicit PowerShell examples and references to PowerShell-specific modules (e.g., Az.LabServices). The ARM template deployment section links to a PowerShell-focused guide before mentioning other methods. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there examples tailored to Linux users, despite Azure CLI being cross-platform. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of environment setup or command-line usage.
Recommendations
- Explicitly mention that Azure CLI commands work in Bash and other Linux shells, and provide example commands using Bash syntax where appropriate.
- Include instructions or notes for Linux/macOS users regarding environment setup (e.g., installing Azure CLI on Linux, using Bash or zsh).
- Balance PowerShell and CLI examples by clarifying that CLI is cross-platform and not Windows-specific.
- Avoid linking to PowerShell deployment guides before mentioning cross-platform alternatives; instead, present deployment options in a neutral order.
- If referencing modules (e.g., Az.LabServices), note their platform compatibility and provide alternatives or installation instructions for Linux users.
Lab Services
Create a lab plan using Bicep or ARM
.../articles/lab-services/how-to-create-lab-plan-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While both Azure CLI and Azure PowerShell examples are provided for deployment, resource review, and cleanup, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes referenced first. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The instructions assume familiarity with PowerShell and do not address Linux users' common workflows (e.g., bash scripting, use of native Linux tools).
Recommendations
- Add explicit bash shell examples for all CLI commands, showing usage in a Linux terminal.
- Clarify that Azure CLI commands work cross-platform and can be run in bash, zsh, etc., not just in Windows Command Prompt or PowerShell.
- When listing deployment options, avoid listing PowerShell before CLI, or alternate the order to avoid implicit prioritization.
- Include notes or links for Linux users on installing and using Azure CLI and Bicep on Linux systems.
- Where PowerShell modules are referenced, provide equivalent bash/CLI instructions for Linux users.
- Consider adding a section or callout for Linux-specific considerations, such as environment setup or troubleshooting.
Lab Services
Manage lab accounts in Azure Lab Services | Microsoft Docs
...in/articles/lab-services/how-to-manage-lab-accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific features and examples. The automatic disconnect on idle is only available for Windows VMs, with detailed explanation and links to Windows OS documentation, while Linux support is mentioned only for shutdown on disconnect, with caveats and no equivalent idle disconnect feature. The 'Next steps' section highlights PowerShell (a Windows-centric tool) for lab account management, with no mention of Linux CLI or cross-platform alternatives. No Linux-specific examples or screenshots are provided.
Recommendations
- Provide equivalent Linux examples and screenshots where possible, especially for management tasks.
- Include cross-platform CLI tools (e.g., Azure CLI, Bash scripts) alongside PowerShell in the 'Next steps' and throughout the documentation.
- Clarify feature parity and limitations for Linux VMs, and link to relevant Linux documentation or troubleshooting guides.
- Where features are Windows-only, suggest alternative approaches for Linux users or note roadmap for Linux parity.
- Reorder sections or examples to present Windows and Linux options together, rather than Windows-first.
Lab Services
Enable nested virtualization
...-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 page exhibits a strong Windows bias. All setup instructions for enabling nested virtualization focus exclusively on Windows environments, specifically Windows 11 and Windows Server, using PowerShell scripts and Windows GUI tools. There are no instructions or examples for enabling nested virtualization on Linux-based template VMs, nor is there mention of Linux virtualization technologies (e.g., KVM, QEMU). Even troubleshooting and connectivity examples assume Hyper-V and Windows tools, with only brief references to Linux as a nested guest OS, not as a host.
Recommendations
- Add instructions for enabling nested virtualization on Linux template VMs (e.g., using KVM/QEMU).
- Provide parity examples for Linux hosts, including command-line steps and relevant tools.
- Mention Linux virtualization technologies and their support status in Azure Lab Services.
- Include troubleshooting steps and connectivity examples for Linux-based hosts and guests.
- Clarify whether nested virtualization is supported for Linux template VMs and, if not, state this explicitly.
Lab Services
Manage labs in Azure Lab Services when using lab accounts| Microsoft Docs
.../articles/lab-services/how-to-manage-classroom-labs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell (Az.LabServices PowerShell module) as the only command-line automation tool for managing labs, without mentioning equivalent Linux/CLI options. Windows patterns (such as remote desktop and password management) are described first or in more detail, while Linux-specific instructions are relegated to notes or linked articles. There are no direct examples or guidance for Linux CLI management, and Windows-centric tools are mentioned without Linux parity.
Recommendations
- Include Azure CLI and/or REST API examples for managing labs, alongside PowerShell, to provide cross-platform parity.
- Mention Linux-compatible automation tools (e.g., Bash scripts, Azure CLI) wherever PowerShell is referenced.
- Ensure that instructions for connecting to Linux VMs (SSH, graphical desktop) are as detailed and prominent as those for Windows RDP.
- Add explicit Linux command-line examples for common tasks (creating, deleting labs, managing VMs) in the main documentation, not just in linked articles.
- Clarify which features or steps differ for Linux and Windows, and provide side-by-side guidance where possible.
Lab Services
Quickstart: Create and connect to a lab
...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 page demonstrates a clear Windows bias: it exclusively describes creating a Windows-based lab, only provides instructions for connecting via Remote Desktop (RDP, a Windows-centric protocol), and does not mention Linux VM images or alternative connection methods (e.g., SSH for Linux). All screenshots and examples reference Windows tools and workflows, with no Linux equivalents or parity.
Recommendations
- Include instructions and examples for creating labs using Linux VM images from the Azure Marketplace.
- Provide connection steps for Linux VMs, such as using SSH, and mention relevant tools (e.g., PuTTY, OpenSSH, terminal commands) alongside RDP.
- Add screenshots and walkthroughs for Linux-based lab creation and connection to ensure parity.
- Explicitly mention that Azure Lab Services supports both Windows and Linux VMs, and clarify the differences in setup and connection.
- Reorder or balance examples so that Linux options are presented alongside Windows, not exclusively or secondarily.
Lab Services
Accelerated lab setup guide for Azure Lab Services
...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 page demonstrates a Windows bias by frequently mentioning Windows-specific tools and patterns (such as RDP and OneDrive) before their Linux equivalents, providing more detail for Windows scenarios, and lacking equivalent Linux examples or instructions (e.g., for automatic shutdown, OneDrive setup, and template VM preparation). Linux options are mentioned but not elaborated upon, and Linux-specific guidance is minimal.
Recommendations
- Provide step-by-step Linux examples alongside Windows instructions, especially for tasks like template VM setup, automatic shutdown, and connecting to VMs.
- Include Linux-specific tools and patterns (e.g., SSH, SFTP, Linux desktop environments, Linux file sync options) with equal prominence and detail.
- Offer guidance for configuring external repositories and file sync solutions on Linux VMs, not just OneDrive.
- Clarify how cost controls and shutdown features work for Linux VMs, including any differences or required configurations.
- Ensure that all major features and workflows are documented for both Windows and Linux environments, with parity in depth and clarity.
Lab Services
Troubleshoot connectivity issues with Azure Lab Services
...n/articles/lab-services/troubleshoot-connect-lab-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools (PsPing), referencing Windows settings and guides first, and omitting Linux-specific troubleshooting steps and examples. Powershell and Windows-centric links are provided, while Linux alternatives (e.g., SSH troubleshooting, Linux network tools) are not mentioned or are only referenced generically. This may hinder Linux users from effectively troubleshooting connectivity issues in Azure Lab Services.
Recommendations
- Include Linux-specific troubleshooting examples alongside Windows ones, such as using 'ping', 'nmap', or 'ss' for network diagnostics.
- Provide SSH connection troubleshooting steps for Linux users, including common error messages and resolutions.
- Reference Linux firewall configuration (e.g., ufw, firewalld) and how to allow RDP/SSH connections.
- Add links to Linux documentation for adjusting remote desktop client settings and network troubleshooting.
- Mention Linux command-line tools and patterns (e.g., journalctl, systemctl) where relevant.
- Ensure parity in guidance for both Windows and Linux users throughout the documentation.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing a PowerShell script as the only example for querying lab quotas, without mentioning or providing equivalent Linux/bash/CLI alternatives. No Linux-specific tools or examples are given, and the scripting example is presented as the sole method, implying Windows-first support.
Recommendations
- Provide equivalent bash/CLI scripts for quota queries and other automation tasks, alongside PowerShell examples.
- Explicitly mention cross-platform compatibility for all scripts and tools, clarifying whether they work on Linux/macOS as well as Windows.
- Include references to Azure CLI commands where possible, as these are cross-platform and widely used on Linux.
- Add notes or sections highlighting Linux usage patterns and troubleshooting steps, ensuring parity with Windows guidance.
Lab Services
Use advanced networking in Azure Lab Services | Microsoft Docs
...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 page demonstrates a Windows bias in several ways. The tutorial explicitly instructs users to select Windows 11 Pro as the VM image, and all subsequent configuration steps (such as enabling ICMP) use Windows-specific tools (PowerShell cmdlets). There are no Linux examples or instructions for equivalent tasks (e.g., enabling ICMP via firewall-cmd or ufw), and the only mention of Linux is a brief note suggesting SSH port should be allowed in NSG rules. The workflow and screenshots are tailored to Windows environments, and Linux users are left to infer or research their own steps.
Recommendations
- Provide parallel instructions and screenshots for creating labs with Linux VM images (e.g., Ubuntu, CentOS).
- Include Linux-specific steps for enabling ICMP (e.g., using firewall-cmd, ufw, or iptables) on template VMs.
- Show SSH connection examples for Linux VMs, including how to connect from Linux/macOS clients.
- Clarify that the tutorial is applicable to both Windows and Linux, and offer guidance for choosing VM images based on user needs.
- Where PowerShell is used, offer equivalent bash or shell commands for Linux.
- Add troubleshooting tips for common Linux networking/firewall issues in Azure Lab Services.
Lab Services
Import a Windows image from a physical lab
...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 focused on Windows environments, exclusively referencing Windows tools (Hyper-V Manager, PowerShell), Windows-specific configuration steps, and Windows disk formats. There are no examples or guidance for Linux-based workflows, nor are Linux tools or patterns mentioned. Windows terminology and instructions are presented first and exclusively throughout.
Recommendations
- Add equivalent instructions for importing Linux images, including preparation steps for common Linux distributions.
- Include examples using Linux virtualization tools (e.g., KVM, VirtualBox, qemu-img) for creating and converting disk images.
- Provide Linux command-line alternatives to PowerShell for disk conversion and upload (e.g., using Azure CLI, AzCopy on Linux).
- Clarify which steps are Windows-specific and offer parallel Linux-specific documentation or links.
- Mention Linux disk formats (e.g., VHD, VMDK, QCOW2) and how to convert them for Azure compatibility.
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 is heavily focused on creating and connecting to Windows-based lab VMs, with all examples and screenshots using Windows 11 Pro as the VM image. The connection method described is exclusively Remote Desktop (RDP), which is a Windows-centric protocol. There are no examples, instructions, or mentions of creating Linux-based labs, nor are alternative connection methods (such as SSH for Linux) discussed. Windows tools and workflows are presented as the default and only option.
Recommendations
- Include examples and instructions for creating Linux-based lab VMs, such as Ubuntu or CentOS, alongside Windows examples.
- Provide guidance on connecting to Linux VMs using SSH, including how to download SSH keys or connection details from the portal.
- Add screenshots and walkthroughs for Linux VM creation and connection steps to ensure visual parity.
- Mention Linux-specific configuration options (e.g., setting up SSH users, installing software via package managers) where relevant.
- Clarify that Azure Lab Services supports both Windows and Linux labs, and link to documentation for both.