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 151-175 of 272 flagged pages
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/connect-virtual-machine.md
.../main/articles/lab-services/connect-virtual-machine.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by consistently listing Windows instructions and tools before Linux equivalents, especially in SSH connection steps. Windows-specific tools (e.g., PuTTY, Windows built-in SSH) are highlighted, while Linux and macOS SSH instructions are missing or underexplained. There is also a lack of parity in example commands and tool recommendations for non-Windows users.
Recommendations
- Provide explicit SSH connection instructions for Linux and macOS users, including example commands and terminal usage.
- List instructions for all platforms (Windows, Linux, macOS) in parallel tables or sections, rather than always leading with Windows.
- Mention native SSH clients on Linux and macOS, and provide guidance for their use.
- Balance tool recommendations by including popular Linux and macOS SSH clients (e.g., Terminal, GNOME Terminal, iTerm2) alongside Windows tools.
- Ensure that all examples and screenshots are platform-agnostic or include variants for each major OS.
Create Pull Request
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows-specific guidance (such as installing and stopping Windows updates, configuring OneDrive, and autoshutdown for RDP sessions) is provided in detail, while equivalent Linux instructions or alternatives are either missing or less emphasized. Windows tools and patterns (e.g., OneDrive, Windows Update) are mentioned without Linux counterparts, and Windows-specific features are sometimes described before or in more detail than Linux equivalents.
Recommendations
- Provide equivalent Linux guidance for all Windows-specific instructions, such as how to update Linux VMs, disable automatic updates, and configure backup solutions (e.g., using rsync, Nextcloud, or other cross-platform cloud storage).
- When mentioning tools like OneDrive, also mention Linux-compatible alternatives or clarify if/how OneDrive can be used on Linux VMs.
- For features like autoshutdown, clarify if similar functionality exists for Linux VMs and provide instructions or references.
- Ensure that examples and instructions are balanced between Windows and Linux, and avoid presenting Windows steps or tools first unless there is a technical reason.
- Explicitly mention and link to Linux-specific documentation or how-to guides wherever Windows-specific guides are referenced.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by primarily describing and illustrating the process using Windows-specific tools (Hyper-V Manager, PowerShell), and by assuming the user is operating from a Windows environment. Linux-native workflows and tooling (such as KVM, qemu-img, or Linux shell commands) are only briefly mentioned or referenced externally, with no step-by-step guidance provided for users on Linux hosts. The upload process also references Windows-centric tools and documentation, and PowerShell is suggested for disk operations without Linux equivalents.
Recommendations
- Provide a parallel, step-by-step workflow for preparing and converting a Linux image using Linux-native tools (e.g., KVM, qemu-img, virt-manager).
- Include Linux command-line examples for resizing and converting disk images, such as using qemu-img.
- When referencing upload tools, mention and provide examples for AzCopy and Azure CLI usage on Linux, not just from a Windows context.
- Ensure links to documentation for Linux-based image preparation are as prominent as those for Windows/Hyper-V.
- Avoid assuming the user is on Windows; clarify which steps are OS-specific and offer alternatives.
- Add screenshots or terminal output examples from Linux environments where appropriate.
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 →
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-based instructions and examples for retrieving the public IP address of Azure Lab Services labs. There are no equivalent command-line examples for Linux or macOS users (e.g., using Azure CLI or Bash). The references and links are all centered around PowerShell modules, reinforcing the Windows-centric approach and omitting cross-platform alternatives.
Recommendations
- Add equivalent instructions and code examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Include Bash shell script examples for retrieving the public IP address, demonstrating parity with the PowerShell example.
- Mention both PowerShell and Azure CLI options at the start of the 'Find public IP for a lab' section, rather than only referencing PowerShell.
- Provide links to Azure CLI documentation alongside PowerShell references.
- Explicitly state that the instructions apply to Windows and provide alternative steps for Linux/macOS users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, review, and cleanup tasks. However, PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI, and is referenced as a primary method for deployment and resource management. There is no explicit mention of Linux-specific shell environments (e.g., Bash), nor are there any examples or notes tailored for Linux users. The documentation assumes familiarity with PowerShell and Windows tools, and does not address potential differences or considerations for Linux users.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, macOS, Linux) and can be run in Bash or other Linux shells.
- Add Bash-specific notes or examples where relevant, especially for file paths and shell syntax.
- Clarify that PowerShell is optional and primarily relevant for Windows users; suggest Bash or other shells for Linux users.
- Include troubleshooting tips or environment setup instructions for Linux users (e.g., installing Azure CLI on Linux, using chmod for file permissions).
- Where PowerShell modules are referenced (e.g., Az.LabServices), note their availability and support on Linux PowerShell Core, or provide alternative CLI commands.
- Ensure that any screenshots or UI references do not assume a Windows environment.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and management tasks, but PowerShell is given equal or sometimes more prominence than CLI. PowerShell is a Windows-centric tool, and there is no mention of Linux-specific shell environments or examples (e.g., Bash). The documentation does not clarify cross-platform compatibility for PowerShell, and there are no Linux-specific notes or examples, which may lead Linux users to feel less supported.
Recommendations
- Explicitly state that both Azure CLI and Azure PowerShell are cross-platform, and clarify installation instructions for Linux and macOS users.
- Add Bash-specific examples or notes, especially for common deployment and file management tasks.
- When presenting multiple command-line options, consider listing Azure CLI (which is more universally cross-platform) before PowerShell.
- Include a section or callout for Linux/macOS users, mentioning any differences or prerequisites.
- Avoid assuming PowerShell is the default or primary shell; clarify that users can use their preferred shell environment.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based VM images (e.g., 'microsoftwindowsdesktop.windows-11.win11-21h2-pro') in the code sample, omitting any Linux alternatives. Additionally, the 'Next steps' section highlights Azure PowerShell and Az.LabServices cmdlets, which are traditionally more familiar to Windows users, without mentioning cross-platform or Linux-native tools. There are no Linux VM image examples or references to Linux command-line tools.
Recommendations
- Include examples that use Linux VM images (e.g., Ubuntu, CentOS) in the code samples, either as alternatives or alongside the Windows example.
- In the 'Next steps' section, add links to Azure CLI documentation and examples, which are cross-platform and widely used on Linux.
- Explicitly mention that the Python SDK and code samples work on both Windows and Linux, and provide any necessary Linux-specific setup instructions if applicable.
- Where PowerShell is referenced, also reference Bash or other Linux-native scripting environments to ensure parity.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by mentioning Windows-centric tools (e.g., Visual Studio, Azure Storage Explorer) as example software to install, and by listing Remote Desktop Protocol (RDP) before Secure Shell (SSH) when describing connection methods. There are no explicit Linux-specific examples or tools mentioned, and no Linux-focused workflow or screenshots are provided.
Recommendations
- Provide Linux-specific examples of software to install (e.g., GCC, Python, Gedit) alongside or instead of Windows examples.
- Alternate the order of connection methods (mention SSH before RDP when the template is Linux-based, or clarify which applies to which OS).
- Include screenshots or instructions that show connecting to a Linux VM, including SSH command-line examples.
- Mention Linux tools and workflows (e.g., package installation with apt/yum, configuring systemd services) in the update steps.
- Explicitly state that the process applies to both Windows and Linux VMs, and highlight any OS-specific considerations.
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 toward Windows environments, specifically Windows 11 and Windows Server, with all setup instructions and tooling (PowerShell, Hyper-V, Windows Settings) being Windows-specific. There are no instructions or examples for enabling nested virtualization with Linux-based template VMs, nor is there mention of Linux virtualization technologies (such as KVM or VirtualBox). Even when Linux is referenced (e.g., nested Ubuntu VMs), the host and configuration steps are always Windows-centric.
Recommendations
- Add explicit guidance on whether Linux-based template VMs are supported for nested virtualization in Azure Lab Services. If not supported, state this clearly at the beginning.
- If Linux hosts are supported, provide equivalent instructions for enabling nested virtualization on Linux template VMs, including examples using KVM or other common Linux virtualization tools.
- Include Linux command-line examples (e.g., using virsh, virt-manager, or qemu) alongside PowerShell/Windows examples.
- Mention Linux tools and patterns (e.g., SSH, systemd, libvirt) where relevant, and not only as guest OSes.
- If only Windows is supported as a host, clarify this limitation early and suggest alternatives or workarounds for Linux users.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While it states that both Windows and Linux VMs are supported, it references Windows-specific behaviors and resources more prominently. For example, the warning about shutdown behavior links only to a Windows-specific guide, and there are no Linux-specific troubleshooting or configuration examples. The documentation also mentions RDP sessions (primarily a Windows protocol) without referencing Linux equivalents, and does not provide Linux command-line or tool-based examples for configuring or troubleshooting auto-shutdown.
Recommendations
- Provide equivalent Linux-specific troubleshooting and configuration guidance, such as linking to a guide on controlling Linux shutdown behavior.
- Include examples or references for Linux remote connection protocols (e.g., SSH, VNC) alongside RDP.
- Ensure that any warnings or tips are balanced with both Windows and Linux contexts, not just Windows.
- Add Linux command-line examples or screenshots where appropriate, especially for common distributions.
- Reference Linux tools and patterns (e.g., systemd, shutdown commands) where relevant.
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 as a management tool without mentioning Linux CLI alternatives, mentioning Windows and Linux images but providing more detail and default behaviors for Windows, and referencing Windows-centric tools (Az.LabServices PowerShell module) without Linux equivalents. There are no CLI or scripting examples for Linux users, and the only explicit command-line management option is PowerShell.
Recommendations
- Include Azure CLI and/or Bash examples for managing labs, alongside or before PowerShell examples.
- Mention and link to cross-platform management tools (e.g., Azure CLI, REST API) wherever PowerShell is referenced.
- Provide parity in instructions and screenshots for both Windows and Linux VM scenarios, including connection methods and credential management.
- Clarify default behaviors for both Windows and Linux images equally, and ensure that Linux-specific workflows are as detailed as Windows ones.
- Add troubleshooting and management guidance for Linux users, not just Windows/PowerShell users.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-lab-accounts.md
...in/articles/lab-services/how-to-manage-lab-accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows-first bias. Most examples and explanations focus on Windows virtual machines, especially for idle detection and automatic disconnect features, which are described as Windows-only. Linux support is mentioned only as an exception or limitation, with no equivalent Linux-specific instructions or examples. The 'Next steps' section highlights PowerShell (a Windows-centric tool) for lab management, without mentioning cross-platform or Linux-native alternatives.
Recommendations
- Provide Linux-specific examples and instructions where features are supported (e.g., how idle detection or shutdown works on Linux VMs).
- Clarify feature parity and limitations for Linux VMs up front, and offer workarounds or alternatives if possible.
- Include CLI (az cli) or REST API examples for lab management, which are cross-platform, alongside or instead of PowerShell.
- Ensure that Linux tools and workflows are presented with equal prominence to Windows/PowerShell options.
- Add screenshots or terminal output relevant to Linux scenarios where applicable.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While the main instructions are platform-neutral and focus on the Azure Lab Services web portal, 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 examples or notes about Linux VMs, and the only references to file systems and data loss are Windows-centric. No Linux-specific instructions or terminology are provided.
Recommendations
- When referring to OS and temporary disks, include Linux equivalents (e.g., 'the OS disk (C: drive on Windows, / on Linux)' and 'the temporary disk (D: drive on Windows, /mnt on Linux)').
- Add notes or examples that clarify behavior for both Windows and Linux VMs, especially regarding disk persistence and data loss.
- Where screenshots or instructions reference Windows-specific concepts, provide parallel information for Linux users if applicable.
- Consider including a section or note that explicitly addresses differences in managing Windows vs. Linux lab VMs, if any exist.
- Ensure that links to further instructions (e.g., connecting to a VM) are clear about supporting both Windows and Linux environments.
Lab Services
Firewall settings for Azure Lab Services
...les/lab-services/how-to-configure-firewall-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell-based instructions and examples for determining the public IP address of Azure Lab Services labs. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI (such as Azure CLI or Bash) examples are provided. References to PowerShell modules and cmdlets are given without mention of cross-platform alternatives, creating friction for users on Linux or macOS.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation guidance if PowerShell is required.
- Where possible, provide Bash script examples or generic REST API calls for users who prefer shell scripting.
- Reorder examples so that cross-platform tools (e.g., Azure CLI) are presented first or alongside PowerShell.
Lab Services
Use advanced networking in Azure Lab Services | Microsoft Docs
...rvices/tutorial-create-lab-with-advanced-networking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows 11 Pro as the example VM image, providing only Windows PowerShell commands for enabling ICMP, and omitting equivalent instructions for Linux-based VMs. The workflow and screenshots are tailored to Windows environments, and Linux alternatives are mentioned only briefly (e.g., SSH port in NSG rules) without actionable guidance or examples.
Recommendations
- Include step-by-step instructions for enabling ICMP (ping) on Linux VMs, such as using ufw or iptables.
- Provide Linux shell command examples alongside PowerShell for firewall configuration.
- Show how to connect to Linux VMs (e.g., via SSH) and test communication using Linux tools.
- Offer screenshots and workflow details for Linux VM setup and management within Azure Lab Services.
- Explicitly mention how to select Linux images and any differences in credential setup.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a subtle Windows bias: the example lab image is a Windows 11 desktop, and in the 'Next steps' section, Azure PowerShell and Az.LabServices cmdlets (Windows-centric tools) are highlighted, with no mention of Linux/macOS equivalents or CLI alternatives. There are no explicit Linux examples or references to Linux VM images, and Windows tools are mentioned first and exclusively.
Recommendations
- Include examples using Linux VM images (e.g., Ubuntu) in the Python code samples.
- In the 'Next steps' section, mention Azure CLI and its Lab Services commands as a cross-platform alternative to PowerShell.
- Add notes or links for Linux/macOS users regarding authentication and environment setup.
- Ensure parity in documentation by providing both Windows and Linux-focused scenarios.
Lab Services
Configure automatic shutdown for a lab
...cles/lab-services/how-to-enable-shutdown-disconnect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page mentions both Windows and Linux support for automatic shutdown, but provides more detailed guidance and links for Windows (e.g., a dedicated guide for Windows shutdown behavior). Linux support is discussed in terms of distribution/version compatibility, but lacks equivalent troubleshooting or configuration detail. No Linux-specific examples or guides are provided, and the warning section references only Windows resources.
Recommendations
- Add a dedicated guide or troubleshooting section for Linux shutdown behavior, similar to the Windows guide.
- Provide Linux-specific examples or screenshots for configuring auto-shutdown.
- Include links to relevant Linux documentation or community resources for common distributions.
- Ensure warnings and troubleshooting tips cover both Windows and Linux scenarios equally.
Lab Services
Quickstart: Create and connect to a lab
...main/articles/lab-services/quick-create-connect-lab.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes creating and connecting to a Windows-based lab VM, with all instructions and screenshots focused on Windows 11 Pro and Remote Desktop (RDP) as the connection method. There is no mention of Linux-based VM options, nor are there instructions for connecting from non-Windows clients or using SSH, which is standard for Linux VMs. This creates a clear Windows-first bias and omits guidance for Linux users.
Recommendations
- Include instructions for creating a Linux-based lab VM (e.g., Ubuntu or CentOS) alongside the Windows example.
- Provide connection instructions for Linux VMs, such as using SSH, and mention how to connect from Linux/macOS clients.
- Add screenshots and field values relevant to Linux VM creation and connection.
- Clarify in the prerequisites or introduction that both Windows and Linux labs are supported, if applicable.
- If RDP is the only supported connection method, explicitly state this and provide guidance for Linux/macOS users on how to use RDP clients.
Lab Services
Manage lab accounts in Azure Lab Services | Microsoft Docs
...in/articles/lab-services/how-to-manage-lab-accounts.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific features (like idle disconnect) are described in detail, with explicit references to Windows OS behavior and links to Windows documentation. The PowerShell module is recommended for lab account management, with no mention of Linux/macOS CLI alternatives or examples. Linux support is mentioned only as a caveat or secondary note, and Linux-specific instructions or examples are missing.
Recommendations
- Provide equivalent CLI examples for Linux/macOS users, such as using Azure CLI or Bash scripts for lab account management.
- Explicitly document Linux/macOS workflows for managing lab accounts, including supported tools and commands.
- Include Linux-specific screenshots or UI notes where behavior differs.
- Clarify limitations and supported features for Linux VMs, and link to relevant Linux documentation.
- Avoid presenting Windows features or tools first; strive for parallel presentation of Windows and Linux options.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows drive letters (C: and D:) exclusively when discussing OS and temporary disks, and by listing PowerShell as the only CLI example for programmatic redeploy/reimage operations. There are no Linux/macOS shell or CLI examples, nor are Linux-specific disk conventions mentioned. The REST API is mentioned, which is cross-platform, but the lack of parity in CLI tooling and examples creates friction for non-Windows users.
Recommendations
- Include Linux/macOS shell (e.g., Bash, Azure CLI) examples for redeploy and reimage operations.
- Mention Linux disk conventions (e.g., /dev/sda1, /mnt) alongside Windows drive letters when discussing OS and temporary disks.
- Clarify that PowerShell examples are applicable on Linux/macOS (if true), or provide alternative commands.
- Ensure screenshots and UI references do not assume Windows conventions only.
Lab Services
Administrator guide using lab accounts | Microsoft Docs
...ob/main/articles/lab-services/administrator-guide-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias, primarily in the 'Endpoint management' section, where Windows-specific tools (SysPrep, PsGetSid) and Windows VM management patterns are discussed exclusively. While Linux is mentioned as a possible VM image, there are no equivalent Linux endpoint management examples, nor are Linux-specific tools or concerns addressed. Windows terminology and tools are introduced before any Linux alternatives, and no PowerShell-heavy bias is present, but the lack of Linux parity in endpoint management is notable.
Recommendations
- Add equivalent Linux endpoint management guidance, such as handling machine IDs or security identifiers (e.g., /etc/machine-id, hostnamectl, or cloud-init usage).
- Mention Linux-specific tools or patterns for VM generalization and identity management.
- Provide examples or references for managing Linux VMs in lab environments, especially where Windows tools are discussed.
- Ensure that any Windows-specific advice is paired with Linux/macOS equivalents or notes on differences.
Lab Services
Connect to a lab VM from Chromebook
...s/connect-virtual-machine-chromebook-remote-desktop.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page focuses exclusively on using the Microsoft Remote Desktop app for connecting to lab VMs from a Chromebook, with all instructions and screenshots centered around this Windows-centric tool. While it briefly mentions alternatives like Chrome Remote Desktop, these are discouraged and not documented. The process for connecting to Linux VMs is only covered via RDP, with no Linux-native client recommendations or examples. The documentation assumes the use of Microsoft tools and patterns, which may not be optimal or preferred for Linux VM users.
Recommendations
- Provide step-by-step instructions for connecting to Linux VMs using SSH, which is a native and preferred method for Linux systems.
- Include examples and screenshots for alternative RDP clients available on Chrome OS and Linux, such as Remmina or FreeRDP.
- Document the process for configuring and using Chrome Remote Desktop or other open-source remote desktop solutions, especially for Linux VMs.
- Clarify the limitations and requirements for using third-party clients, and provide guidance for lab administrators to support these options.
- Present Linux connection options (SSH, open-source RDP clients) before or alongside Microsoft Remote Desktop instructions to avoid Windows-first bias.
Lab Services
Connect to Azure Lab Services VMs from Mac
...services/connect-virtual-machine-mac-remote-desktop.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation instructs Mac users to install and use the 'Windows App' for RDP connections, positioning Microsoft's tool as the primary (and only) method. Alternative RDP clients commonly used on macOS (such as Microsoft Remote Desktop or open-source options) are not mentioned. The workflow and screenshots focus on Windows-centric patterns, and the only tool recommended is a Microsoft-branded app, which may not be the default or preferred choice for many Mac users.
Recommendations
- Mention and provide instructions for other popular RDP clients on macOS, such as Microsoft Remote Desktop (distinct from 'Windows App'), Royal TSX, or open-source alternatives like FreeRDP.
- Clarify the differences between 'Windows App' and 'Microsoft Remote Desktop' for Mac users, and help users choose the best fit for their needs.
- Include examples or steps for connecting using these alternative clients, ensuring parity for users who do not wish to use the Windows App.
- Add a brief section explaining RDP client options on macOS, including pros/cons and links to official download pages.
Lab Services
Import a Linux image from a physical lab
...es/lab-services/how-to-bring-custom-linux-image-vhd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by focusing almost exclusively on Windows tooling (Hyper-V Manager, PowerShell) for preparing and converting Linux images. Steps and screenshots are centered on Windows workflows, with only brief mentions of Linux alternatives (e.g., KVM, qemu) that lack detailed instructions or parity in guidance. Upload instructions reference Windows-centric tools and documentation, and Linux-based methods for image creation and conversion are not covered in detail.
Recommendations
- Add step-by-step instructions for preparing and converting Linux images using Linux-native tools such as KVM, qemu-img, and virt-manager.
- Provide Linux command-line examples for uploading VHDs (e.g., using AzCopy on Linux, Azure CLI).
- Include screenshots or terminal outputs from Linux environments to match those shown for Windows/Hyper-V.
- Reference and link to Linux-specific documentation for each major step, not just Windows-centric guides.
- Present Linux and Windows methods side-by-side, or clearly separate them, to avoid implying Windows is the default or preferred platform.
Lab Services
Use Azure Lab Services for hackathon
...docs/blob/main/articles/lab-services/hackathon-labs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows moderate Windows bias: Windows-specific guidance (such as installing/stopping Windows updates and configuring OneDrive) is given in detail, while Linux equivalents (e.g., backup options, update management) are not mentioned. Windows features (like autoshutdown after RDP disconnect) are described, but Linux-specific behaviors are not. Windows examples and tools (OneDrive, Windows updates) are presented before or instead of Linux alternatives.
Recommendations
- Provide equivalent Linux guidance for update management (e.g., using apt/yum for updates, disabling automatic updates).
- Include Linux backup options (such as using rsync, cloud storage, or mounting network shares) alongside OneDrive.
- Clarify autoshutdown behavior for Linux VMs and provide instructions if different from Windows.
- Ensure examples and instructions are balanced between Windows and Linux, or presented in parallel.
- Mention cross-platform tools for backup and remote access (e.g., Nextcloud, SFTP, VNC) where appropriate.