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 101-125 of 272 flagged pages
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
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias. Examples and explanations for features such as automatic disconnect on idle are provided only for Windows virtual machines, with explicit notes that certain settings are Windows-only. The documentation references the Windows OS definition of idle, but does not provide equivalent Linux details or links. The 'Next steps' section highlights PowerShell as the primary scripting tool for managing lab accounts, with no mention of CLI or Bash alternatives. Linux support is mentioned only as a caveat or limitation, and Linux-specific instructions or examples are missing.
Recommendations
- Provide Linux-specific examples and instructions where features are supported (e.g., how idle detection or shutdown works on Linux VMs).
- Include parity in tooling recommendations, such as Azure CLI or Bash scripts, alongside PowerShell for managing lab accounts.
- Where features are Windows-only, offer clear explanations or workarounds for Linux users, and link to relevant Linux documentation.
- List Linux and Windows support side-by-side in feature tables or callouts, rather than mentioning Linux only as a limitation.
- Ensure screenshots and examples include both Windows and Linux scenarios where applicable.
Create Pull Request
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 page demonstrates a Windows bias by presenting Windows validation steps and tools (such as NVIDIA Control Panel and Task Manager) in detail, while Linux instructions are referenced only via external links without in-page examples or screenshots. Windows instructions and tools are described first and more thoroughly, with Linux relegated to brief mentions or links.
Recommendations
- Provide in-page, step-by-step Linux examples for driver installation and validation, including relevant commands (e.g., nvidia-smi, lspci) and screenshots.
- Present Windows and Linux instructions in parallel sections, giving equal prominence and detail to both platforms.
- Avoid describing Windows tools (e.g., Control Panel, Task Manager) exclusively; include Linux equivalents (e.g., nvidia-settings, htop, or system monitoring commands).
- When referencing external links for Linux, summarize the key steps or commands directly in the documentation for parity with Windows instructions.
- Ensure that all screenshots and UI walkthroughs are balanced between Windows and Linux where applicable.
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 bias towards Windows by exclusively referencing Windows VM images in the code example, omitting Linux alternatives. Additionally, the 'Next steps' section only mentions Azure PowerShell and Az.LabServices cmdlets, which are traditionally Windows-centric tools, without referencing cross-platform or Linux-native tools. There are no Linux VM image examples or mentions of Linux-specific access methods (e.g., SSH), and the RDP (Windows) access is enabled by default in the sample.
Recommendations
- Include examples that use Linux VM images (e.g., Ubuntu, CentOS) in addition to or instead of only Windows images.
- Demonstrate both RDP (for Windows) and SSH (for Linux) connection profiles in the sample code.
- In the 'Next steps' section, add references to cross-platform tools such as Azure CLI and Bash scripting, and provide links to relevant documentation.
- Explicitly mention that the Python SDK and code samples are cross-platform and can be run on Linux, macOS, and Windows.
- If possible, provide guidance or examples for setting up labs with Linux VMs and managing them using Linux-native tools.
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 and resource management, but PowerShell is consistently presented as a primary or parallel option. There is an implicit Windows bias through the frequent mention and use of PowerShell, which is traditionally a Windows-centric tool, and through references to 'adminUsername' and 'adminPassword' patterns that are more common in Windows environments. There are no explicit Linux-specific instructions, notes, or examples, and the documentation does not address Linux shell environments or tools beyond the generic Azure CLI.
Recommendations
- Add explicit Linux shell (bash) examples or notes, especially for steps involving file paths or command syntax that may differ between Windows and Linux.
- Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific guidance (e.g., file permissions, path separators).
- When referencing PowerShell, note its availability on Linux, or provide bash equivalents for common tasks.
- Include Linux-specific troubleshooting tips or caveats, if any, for deploying Bicep or ARM templates.
- Avoid using only Windows-centric terminology (e.g., 'adminUsername', 'adminPassword') or clarify that these apply to both Windows and Linux VMs.
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 image, connecting via Remote Desktop). There is no mention of Linux-based lab options, nor are there instructions or examples for connecting to Linux VMs (e.g., via SSH). Windows tools and workflows (RDP) are assumed throughout, with no Linux equivalents provided.
Recommendations
- Include parallel instructions for creating a Linux-based lab VM, such as selecting an Ubuntu or other Linux image during lab creation.
- Provide examples and screenshots for connecting to Linux VMs, including SSH connection steps for Windows, macOS, and Linux clients.
- Mention and explain Linux-compatible remote access tools (e.g., SSH, xrdp, or web-based terminals) alongside RDP.
- Clarify in the introduction that Azure Lab Services supports both Windows and Linux labs, and provide links to Linux-specific documentation if available.
- Ensure troubleshooting and cleanup sections address Linux-specific scenarios as well.
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 (System Restore), and disk drive letters (C:, D:) without providing Linux equivalents or examples. Troubleshooting steps and data storage recommendations are oriented toward Windows environments, and Linux-specific guidance is absent.
Recommendations
- Add parallel Linux examples for troubleshooting steps, such as referencing Linux file paths (e.g., /var/log, /etc), and commands for checking disk space or resetting passwords.
- When mentioning Windows System Restore, provide Linux alternatives (e.g., using Timeshift, rsnapshot, or manual restoration from backups).
- Clarify disk references by explaining Linux equivalents (e.g., /dev/sda1 for OS disk, /mnt for temporary storage) instead of only using Windows drive letters.
- Include guidance for storing user data outside the VM using cross-platform solutions (e.g., Azure Files, NFS, or cloud storage options compatible with Linux).
- Ensure that all troubleshooting scenarios and resolutions address both Windows and Linux lab VMs equally, with step-by-step instructions for each.
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-centric tuning guides, and providing troubleshooting steps and error messages primarily for RDP (a Windows protocol). There is a lack of Linux/SSH-specific troubleshooting examples, and Windows tools and patterns are mentioned before or instead of their Linux equivalents. Powershell and Windows Server documentation are referenced, but there are no corresponding Linux command-line or SSH troubleshooting steps.
Recommendations
- Include Linux/SSH-specific troubleshooting steps and examples alongside RDP/Windows instructions.
- Mention cross-platform tools (e.g., ping, traceroute, nmap) that are available on both Windows and Linux for network diagnostics.
- Provide example error messages and resolutions for SSH (Linux) connections, not just RDP (Windows).
- Reference Linux documentation (e.g., adjusting SSH client/server settings, checking firewall rules with ufw/iptables, using journalctl or syslog for logs).
- When mentioning tools like PsPing, suggest equivalent Linux tools (e.g., hping, nping, or standard ping).
- Balance the order of presentation so that Linux and Windows troubleshooting steps are given equal prominence.
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 towards 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 tools for creating or importing images. The process is described exclusively for Windows images, with no guidance for users coming from Linux or other non-Windows environments.
Recommendations
- Add a parallel section or notes for importing Linux images, including prerequisites and preparation steps specific to Linux distributions.
- Provide examples using Linux-native tools (e.g., qemu-img for disk conversion, KVM/VirtualBox for VM management) alongside Hyper-V and PowerShell.
- Mention and link to Azure documentation for uploading and preparing Linux VMs/images.
- Clarify in the introduction whether the process is Windows-only or provide cross-platform guidance where possible.
- Include command-line examples for Linux (bash, az CLI) in addition to or instead of PowerShell.
- If Azure Lab Services only supports Windows images, state this explicitly and provide alternatives or workarounds for Linux users.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell script as the only example for querying lab quotas, without mentioning or providing equivalent instructions for Linux or cross-platform users (such as Azure CLI or Bash scripts). There are no Linux-specific tools, commands, or examples, and the only script reference is explicitly for PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI or Bash script examples alongside PowerShell scripts for querying quotas and other automation tasks.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for Linux/macOS users.
- Where scripts or tools are referenced, include both Windows and Linux usage patterns, or note cross-platform compatibility.
- Audit other troubleshooting steps for implicit Windows assumptions and ensure parity in instructions for Linux users.
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 demonstrates a Windows bias primarily in the 'Endpoint management' section, where only Windows-specific tools (e.g., SysPrep, PsGetSid) and scenarios are discussed. There is no mention of equivalent Linux endpoint management practices, nor are Linux-specific tools or considerations provided. Additionally, the only concrete VM image example given is for the 'Data Science VM for Linux', but operational guidance and tooling references are Windows-centric.
Recommendations
- Add Linux endpoint management guidance, including discussion of how machine identity and security identifiers are managed on Linux VMs in Azure Lab Services.
- Provide Linux-specific tools or commands (e.g., how to check machine IDs or handle image generalization/specialization on Linux, such as using cloud-init or waagent).
- Balance examples by including both Windows and Linux scenarios when discussing VM images, endpoint management, and content filtering.
- When referencing tools like SysPrep and PsGetSid, also mention their Linux equivalents or note if the concept is not applicable on Linux.
- Explicitly state any differences or limitations for Linux VMs in Azure Lab Services, especially where the documentation currently focuses on Windows.
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 page exhibits some Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (e.g., SysPrep, PsGetSid) and scenarios (machine SIDs, Microsoft Configuration Manager) are discussed. There are no equivalent Linux management tools or scenarios mentioned, nor are there Linux-specific examples for endpoint management or VM preparation. Additionally, in the VM sizing tables, GPU VM sizes for visualization are marked as '(Windows only)' without offering Linux alternatives or guidance.
Recommendations
- Include Linux-specific endpoint management considerations, such as how to prepare and manage Linux lab VMs, and mention tools or processes relevant to Linux (e.g., cloud-init, waagent, or Linux imaging best practices).
- When discussing Windows-only features (such as machine SIDs, SysPrep, or Microsoft Configuration Manager), explicitly state that these are Windows-specific and provide parallel information or clarify the situation for Linux VMs.
- In the VM sizing tables, clarify which GPU VM sizes support Linux for visualization workloads, or provide guidance for Linux users seeking similar functionality.
- Where possible, provide balanced examples or notes for both Windows and Linux administrators, especially in sections about image preparation, endpoint management, and content filtering.
- Review the documentation for other subtle Windows-first patterns, such as mentioning Windows tools or workflows before Linux equivalents, and adjust the order or add Linux parity where appropriate.
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-centric bias by prioritizing Windows-based solutions (Azure Virtual Desktop, Windows 365 Cloud PC, Microsoft Dev Box) and mentioning Windows scenarios and tools before Linux equivalents. While Azure DevTest Labs and some partner solutions are noted to support Linux, there are no Linux-specific examples, use cases, or guidance. The majority of detailed feature descriptions, migration notes, and recommendations focus on Windows environments, with Linux support only briefly acknowledged.
Recommendations
- Provide explicit Linux-focused transition scenarios and examples, such as migrating Linux-based labs or using Linux images in Azure DevTest Labs and partner solutions.
- Include Linux-specific guidance for image management, VM provisioning, and student/admin access, mirroring the detail given to Windows scenarios.
- Highlight Linux compatibility and features earlier and with equal prominence to Windows, especially in solution overviews and feature lists.
- Add links to Linux documentation, tutorials, and best practices for each recommended Microsoft and partner solution.
- Ensure that migration tooling and guidance address Linux-based labs and images, not just Windows/Hyper-V scenarios.
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 oriented toward Windows and Hyper-V, with all instructions, tools, and examples focused exclusively on Windows environments. There are no Linux-based setup instructions or examples, and all management guidance refers to Windows tools (Hyper-V Manager, PowerShell). Linux is only mentioned as a possible guest OS, not as a host or in configuration steps.
Recommendations
- Provide parallel instructions for enabling and managing nested virtualization on Linux-based Azure Lab VMs, if supported.
- Include examples using Linux-native virtualization technologies (e.g., KVM, QEMU) if Azure Lab Services supports them.
- Offer Linux command-line equivalents for PowerShell/Hyper-V Manager steps, or explicitly state if such functionality is not available.
- Clarify early in the documentation that nested virtualization is only supported on Windows-based lab VMs, and provide a rationale or roadmap for Linux support if possible.
- Add troubleshooting and best practices sections specifically for Linux-based guest VMs, not just links to general Hyper-V/Linux compatibility articles.
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
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by consistently listing Windows instructions before those for other platforms, especially in tables and SSH instructions. The SSH section is heavily focused on Windows users, detailing multiple Windows SSH client options (built-in client, PuTTY, OpenSSH) before mentioning general SSH usage. There is minimal mention of Linux or Mac terminal usage for SSH, and no explicit Linux or Mac SSH command-line examples are provided. The documentation also references Windows-specific tools and patterns (e.g., PuTTY, Windows Terminal) without equivalent Linux or Mac guidance.
Recommendations
- Provide parallel SSH instructions for Linux and Mac users, including example commands for their native terminals.
- Reorder tables and instructions to avoid always listing Windows first; consider alphabetical or rotating order.
- Mention and link to SSH usage on Linux and Mac, not just Windows (e.g., 'On Linux or Mac, open your terminal and run the SSH command').
- Include example screenshots or terminal snippets for Linux and Mac where appropriate.
- Reference Linux and Mac SSH client documentation or guides, not just Windows tools like PuTTY.
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 demonstrates a Windows bias by exclusively recommending the Microsoft Remote Desktop app (a Microsoft/Windows-centric tool), prioritizing RDP (a protocol most associated with Windows), and providing no Chromebook-native or open-source Linux/UNIX RDP client examples. While it mentions connecting to Linux VMs via RDP, it does not provide SSH instructions or alternatives for Linux VMs, nor does it discuss open-source or non-Microsoft RDP clients in detail.
Recommendations
- Include examples of connecting to Linux VMs using SSH from a Chromebook, as SSH is the default and more secure method for Linux remote access.
- List and provide instructions for open-source or cross-platform RDP clients available on Chrome OS (e.g., Remmina, FreeRDP, or Chrome Remote Desktop), including their installation and usage.
- Clarify that while Microsoft Remote Desktop is recommended for Windows VMs, Linux VMs may be better accessed via SSH, and provide step-by-step SSH connection instructions.
- Balance the mention of Microsoft tools by giving equal prominence to non-Microsoft alternatives, especially for Linux VM scenarios.
- Add a troubleshooting section for common Linux/SSH connection issues on Chromebook.
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 shows a moderate Windows bias. Windows-specific guidance (such as installing/stopping Windows updates and configuring OneDrive) is provided in detail, while Linux-specific instructions are less prominent or missing. Windows tools and patterns (e.g., OneDrive, Windows Updates, RDP) are mentioned explicitly, and Windows scenarios are often described before or in more detail than Linux equivalents. Linux examples, especially for backup solutions and update management, are missing.
Recommendations
- Provide Linux-specific examples and guidance alongside Windows instructions, especially for common administrative tasks such as system updates and backup solutions.
- When mentioning Windows tools (e.g., OneDrive), also mention Linux-friendly alternatives (e.g., Google Drive, Dropbox, or generic SFTP/rsync solutions) and provide configuration links or steps.
- Ensure parity in remote access instructions: if RDP is discussed for Windows, provide equal detail for SSH and RDP on Linux, including links to relevant documentation.
- Avoid assuming Windows as the default by presenting both Windows and Linux options together (e.g., 'For Windows, do X; for Linux, do Y').
- Include examples or links for configuring automatic updates and security patches on Linux VMs, similar to the Windows update guidance.
- When discussing client software for connecting to VMs, mention popular Linux and Mac clients (e.g., Remmina, KRDC, Terminal SSH) alongside Windows clients.
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 focusing almost exclusively on Windows-based tooling (Hyper-V Manager, PowerShell) for preparing and converting Linux images. Linux-native hypervisors and tools (such as KVM, qemu-img, or Linux CLI workflows) are only briefly mentioned or referenced as external resources, with no step-by-step guidance provided. All detailed instructions and screenshots assume a Windows host environment, and Linux alternatives are not presented in parallel.
Recommendations
- Provide a parallel set of instructions for preparing and converting Linux images using Linux-native tools (e.g., KVM, qemu-img, virt-manager) for users working on Linux hosts.
- Include Linux command-line examples for image conversion, resizing, and upload steps (e.g., using qemu-img, Azure CLI, or AzCopy on Linux).
- Present both Windows and Linux methods side-by-side or clearly indicate which steps are for which OS, rather than assuming a Windows environment.
- Reference Linux documentation and tools with equal prominence and detail as Windows tools.
- 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-create-lab-plan-bicep.md
.../articles/lab-services/how-to-create-lab-plan-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides deployment and management instructions using both Azure CLI and Azure PowerShell, but PowerShell is consistently presented as a primary or equal option, and there is no mention of Linux-specific shell environments or workflows. The use of PowerShell and references to PowerShell modules (e.g., Az.LabServices) reflect a Windows-centric approach. There are no explicit Linux shell (bash) examples or notes about running commands on Linux, and the documentation does not address Linux users' needs or highlight cross-platform parity.
Recommendations
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and clarify that PowerShell is optional.
- Add bash-specific instructions or notes for Linux/macOS users, especially for file paths and environment setup.
- When listing options (e.g., Azure CLI, PowerShell, Portal), present CLI (which is cross-platform) before PowerShell to avoid Windows-first bias.
- Include troubleshooting or setup notes for Linux users, such as installing Azure CLI or using bash.
- Where PowerShell modules are referenced, provide equivalent CLI commands and clarify that PowerShell is not required.
- Consider adding a 'Platform considerations' or 'Cross-platform usage' section to explicitly address Linux/macOS workflows.
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 all deployment and management steps, but PowerShell is consistently presented alongside or immediately after CLI, and is referenced as a primary tool. There are no explicit Linux shell (bash) examples or mentions of Linux-specific considerations. The use of PowerShell (a Windows-centric tool, though now cross-platform) and the absence of bash or Linux-native command examples indicate a subtle Windows bias.
Recommendations
- Explicitly mention that Azure CLI commands can be run in bash on Linux/macOS, and provide bash-specific instructions or notes where appropriate.
- Include example commands in bash syntax (e.g., with export for environment variables, or using \ for line continuations) to demonstrate parity for Linux users.
- Clarify that PowerShell is available cross-platform, but also provide guidance for users who may not have or wish to use PowerShell.
- Where the Azure Portal is referenced, note that it is OS-agnostic, but for scripting and automation, highlight Linux-native options.
- Add troubleshooting notes or links for common Linux issues (e.g., file permissions, path separators) when working with Bicep/ARM deployments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/includes/lab-services-non-microsoft-account.md
...ervices/includes/lab-services-non-microsoft-account.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Microsoft accounts and Microsoft services (Office, Skype, OneDrive, Windows) as primary examples. It does not mention Linux or cross-platform alternatives, nor does it provide guidance for users who may not use Microsoft-centric tools or accounts.
Recommendations
- Acknowledge users on Linux or other non-Windows platforms and clarify that Microsoft account creation is required regardless of OS.
- Provide explicit instructions or links for creating a Microsoft account from any operating system, not just via Microsoft-centric services.
- Include examples or notes for users who may not have interacted with Microsoft products before, ensuring the documentation is inclusive of all platforms.
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 page demonstrates a Windows-first bias by referencing Windows tools (e.g., Visual Studio), mentioning RDP before SSH, and omitting explicit Linux-focused examples or tools. There are no step-by-step instructions or screenshots for Linux users, nor are Linux-specific software or workflows highlighted. The documentation assumes familiarity with Windows environments and tools, which may disadvantage Linux users.
Recommendations
- Provide parallel Linux examples and instructions, such as installing common Linux development tools (e.g., gcc, Python, VS Code) alongside Visual Studio.
- Mention SSH before or alongside RDP when describing connection methods, and clarify which OS types each applies to.
- Include screenshots and step-by-step instructions for connecting to Linux template VMs, not just Windows.
- Reference Linux-specific troubleshooting tips and known issues, where applicable.
- List both Windows and Linux software options when suggesting what to install on template VMs.
- Ensure that all users, regardless of OS, can follow the documentation without needing to infer Linux steps from Windows-centric instructions.
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 exclusively provides PowerShell examples using the Az.LabServices module, which is primarily a Windows tool. There are no equivalent examples or instructions for Linux or cross-platform users (e.g., using Azure CLI, Bash, or REST API). The documentation references only PowerShell cmdlets and does not mention or link to Linux-friendly alternatives, indicating a strong Windows and PowerShell bias.
Recommendations
- Add equivalent examples using Azure CLI (az lab services ...) for Linux/macOS users.
- Provide Bash shell script examples for retrieving the public IP address.
- Mention and link to REST API documentation for users who may want to automate tasks in a cross-platform way.
- Clearly indicate which instructions are Windows-specific and provide parity for Linux/macOS.
- Include a section or note on how to install and use the Az.LabServices PowerShell module on Linux/macOS (via PowerShell Core), if applicable.
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 references both Windows and Linux support for automatic shutdown, but it exhibits subtle Windows bias. The warning section specifically links to a Windows shutdown behavior guide without providing a Linux equivalent or guidance. There are no concrete Linux configuration examples or troubleshooting steps, while a direct link to Windows-specific shutdown behavior is present. The documentation mentions Linux support but does not provide actionable Linux-focused instructions or references.
Recommendations
- Provide a comparable guide or reference for controlling Linux shutdown behavior, especially for common distributions.
- Include explicit Linux configuration or troubleshooting examples, not just statements of support.
- When mentioning both Windows and Linux, ensure parity by linking to both Windows and Linux resources or guides.
- Avoid referencing only Windows tools or guides in warnings or troubleshooting sections; always offer Linux equivalents.
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 bias towards Windows by exclusively referencing Windows VM images in code examples, omitting any Linux alternatives. The only VM image shown is 'microsoftwindowsdesktop.windows-11.win11-21h2-pro', and connection profiles are set up for RDP (a Windows protocol) with SSH access disabled. Additionally, the 'Next steps' section highlights Azure PowerShell and Az.LabServices cmdlets, which are traditionally Windows-centric tools, without mentioning cross-platform or Linux-native alternatives.
Recommendations
- Include examples that use Linux VM images (e.g., Ubuntu, CentOS) alongside or before Windows images in code samples.
- Demonstrate enabling SSH access (webSshAccess/clientSshAccess) in the connection profile, not just RDP.
- In the 'Next steps' section, add links to Azure CLI documentation and Linux-friendly management tools.
- Explicitly mention that the Python SDK and instructions are cross-platform, and provide any Linux-specific setup notes if needed.
- If possible, show how to set up labs for both Windows and Linux environments to illustrate parity.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias. It provides detailed explanations and references for Windows-specific features (such as idle detection and disconnect behavior), while Linux support is only briefly mentioned and lacks equivalent detail or examples. The only command-line tool referenced is a PowerShell module, with no mention of Linux CLI or cross-platform alternatives. Linux-specific limitations are noted, but not explored or mitigated with guidance.
Recommendations
- Provide equivalent Linux examples and explanations where Windows-specific behaviors are described, especially for idle detection and shutdown settings.
- Include references to cross-platform or Linux-native management tools (such as Azure CLI or Bash scripts), not just PowerShell.
- Clarify any feature gaps for Linux and, where possible, offer workarounds or alternative approaches.
- Ensure that Linux and Windows are treated with parity in both order and depth of coverage throughout the documentation.