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 226-250 of 272 flagged pages
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab-teams-canvas.md
...ticles/lab-services/tutorial-setup-lab-teams-canvas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a Windows Server 2022 Datacenter image as the example for the virtual machine setup, with no mention of Linux-based images or examples. There are no Linux-specific instructions, screenshots, or references to Linux tools or patterns. The documentation implicitly assumes Windows as the default operating system for lab VMs, which may discourage or confuse users interested in Linux environments.
Recommendations
- Include Linux-based VM images (e.g., Ubuntu, CentOS) in the example lab creation steps and screenshots.
- Add a table or section listing both Windows and Linux VM image options, with brief descriptions of their use cases.
- Provide example lab creation steps using a Linux image, including details on SSH access, default credentials, and any Linux-specific configuration.
- Mention Linux tools and access patterns (e.g., SSH clients, terminal usage) alongside Windows equivalents.
- Ensure troubleshooting and next steps sections address Linux VM scenarios, such as connecting via SSH from various platforms.
Create Pull Request
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab.md
.../blob/main/articles/lab-services/tutorial-setup-lab.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows 11 Pro as the virtual machine image and only describing remote desktop (RDP) connection workflows, which are primarily associated with Windows environments. There are no examples or instructions for creating labs with Linux VM images, nor any mention of connecting to Linux VMs (e.g., via SSH). All customization and connection steps assume a Windows-based workflow.
Recommendations
- Include examples for creating labs with Linux VM images (e.g., Ubuntu, CentOS) alongside Windows options.
- Describe connection methods for Linux VMs, such as SSH, and provide step-by-step instructions for those workflows.
- Mention software installation examples relevant to Linux (e.g., installing VS Code via apt or yum).
- Ensure screenshots and field descriptions show both Windows and Linux VM options where applicable.
- Add troubleshooting tips specific to Linux VM scenarios.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-plan-python.md
...articles/lab-services/how-to-create-lab-plan-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally cross-platform, focusing on Python and the Azure Python SDK, which are available on both Windows and Linux. However, in the 'Next steps' section, it highlights Azure PowerShell and Az.LabServices cmdlets as further learning resources, both of which are traditionally associated with Windows environments. There is no mention of Linux-native tools (such as Azure CLI) or explicit Linux shell examples, which may give the impression of a Windows-first or Windows-tools bias.
Recommendations
- In the 'Next steps' section, add references to Azure CLI and its equivalent commands for managing Lab Services, ensuring Linux users see parity in tooling.
- Where PowerShell is mentioned, clarify that Azure CLI is also fully supported and provide links to relevant CLI documentation.
- Consider including a brief note in the prerequisites or introduction that the Python SDK and examples work identically on Linux, macOS, and Windows.
- If possible, provide example commands or scripts using bash or Azure CLI alongside PowerShell references.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/approaches-for-custom-image-creation.md
...s/lab-services/approaches-for-custom-image-creation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows tools and workflows (such as Hyper-V and Microsoft Configuration Manager) as the default or only options for creating and managing custom images, with Linux alternatives mentioned but not equally detailed. In several places, Windows is mentioned before Linux, and the tooling focus is on Microsoft/Windows-specific solutions.
Recommendations
- When listing steps or options, alternate the order in which Windows and Linux are mentioned, or present them together (e.g., 'Windows or Linux') to avoid implicit prioritization.
- Include Linux-native tools and workflows (such as KVM, qemu-img, or virt-manager) alongside Windows tools like Hyper-V for creating VHDs, and provide links to relevant Linux documentation.
- Where Microsoft Configuration Manager is mentioned, suggest open-source or Linux-native alternatives for image creation and management (e.g., Packer, Clonezilla, or Ansible).
- Ensure that all example workflows and tool recommendations are equally detailed for both Windows and Linux, including step-by-step guides and troubleshooting tips.
- Add explicit notes or sections for Linux users where Windows-specific instructions or tools are referenced.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/concept-lab-accounts-versus-lab-plans.md
.../lab-services/concept-lab-accounts-versus-lab-plans.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by highlighting the Az PowerShell module as the primary SDK integration and mentioning Windows and Linux auto-shutdown settings with Windows listed first. There are no Linux-specific command-line examples, and the only SDK/tooling example given is PowerShell, which is more commonly associated with Windows environments.
Recommendations
- Include CLI examples using Azure CLI (az), which is cross-platform and widely used on Linux.
- When listing OS support (e.g., auto-shutdown), alternate or balance the order (e.g., 'Linux and Windows operating systems') or mention both equally.
- Highlight or provide examples for Linux administrators, such as using bash scripts or Linux-native tools to interact with Azure Lab Services.
- Mention or link to documentation for managing Azure Lab Services from Linux environments, ensuring parity with Windows tooling.
- If referencing SDKs, provide example usage in both PowerShell and bash (Azure CLI), and clarify that all features are accessible from both environments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-configure-lab-accounts.md
...articles/lab-services/how-to-configure-lab-accounts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation primarily describes the auto-shutdown feature in a general way but includes a prominent note that Linux support is limited and varies by distribution. There are no Linux-specific instructions, screenshots, or examples, and the limitations for Linux are only mentioned in a side note. The main flow assumes parity but does not provide Linux-focused guidance or alternatives.
Recommendations
- Provide explicit Linux-specific instructions or examples, including any UI differences or additional configuration steps required for supported distributions.
- Include screenshots or illustrations showing the experience for Linux-based labs, if different.
- List supported and unsupported Linux distributions more clearly, possibly in a table.
- Mention Linux limitations earlier in the workflow, not just in a note, to set expectations.
- Offer troubleshooting or workaround guidance for Linux users, especially for unsupported images like Data Science Virtual Machine - Ubuntu.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-lab-plans.md
.../main/articles/lab-services/how-to-manage-lab-plans.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes how to create, view, and delete lab plans using the Azure portal, which is a graphical interface most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), nor are there references to Linux tools or workflows. This may implicitly favor Windows users and workflows, and does not provide parity for Linux users who may prefer or require command-line instructions.
Recommendations
- Add equivalent instructions for managing lab plans using the Azure CLI, which is cross-platform and widely used on Linux.
- Provide examples for common tasks (create, view, delete lab plans) using both Azure CLI and PowerShell, and present them in parallel.
- Explicitly mention that the Azure portal can be accessed from any modern browser on Windows, Linux, or macOS to clarify platform neutrality.
- Include screenshots or terminal output from Linux environments where relevant.
- Consider adding a section on automating lab plan management using scripts, with examples in Bash and PowerShell.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-reset-and-redeploy-vm.md
.../articles/lab-services/how-to-reset-and-redeploy-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to Windows-specific drive letters (C: and D:) when describing OS and temporary disks, without mentioning Linux equivalents (such as / or /mnt). No Linux-specific examples or terminology are provided, and the documentation does not clarify how these instructions or disk mappings apply to Linux VMs. This may cause confusion for users working with Linux-based lab VMs.
Recommendations
- Include references to Linux disk conventions (e.g., root filesystem '/', '/mnt', or '/tmp') alongside Windows drive letters when discussing OS and temporary disks.
- Explicitly state that the instructions apply to both Windows and Linux VMs, or provide separate notes/examples for each platform where behavior differs.
- Add Linux command-line or tool references where PowerShell is mentioned, or clarify if PowerShell is required/supported on Linux VMs.
- Review screenshots and UI text to ensure they are not Windows-centric, or provide Linux-relevant visuals if the experience differs.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-set-virtual-machine-passwords.md
...s/lab-services/how-to-set-virtual-machine-passwords.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes password setting/resetting in a way that assumes Windows VMs as the default, with screenshots and UI text referencing Windows terminology. There is only a brief mention of Ubuntu, and no detailed Linux-specific instructions or examples are provided.
Recommendations
- Include explicit instructions and screenshots for setting and resetting passwords on Linux-based VMs (e.g., Ubuntu), highlighting any differences in workflow or UI.
- Clarify any limitations or differences for Linux VMs (such as the inability to use the same password for all VMs) with more detail and guidance.
- Ensure that terminology and screenshots are balanced between Windows and Linux, or provide parallel sections/examples for each platform.
- Add troubleshooting tips or notes specific to Linux VM password management where applicable.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/concept-lab-accounts-versus-lab-plans.md
.../lab-services/concept-lab-accounts-versus-lab-plans.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page shows mild Windows bias, primarily in the SDKs section, where the Az PowerShell module is mentioned first and in more detail than other SDKs. There is also a general tendency to mention Windows before Linux (e.g., in the auto-shutdown section), and no explicit Linux command-line or tool examples are provided. However, the page does mention Linux support and the Python SDK, and does not include exclusive Windows-only tools or examples.
Recommendations
- When listing SDKs and automation tools, mention cross-platform options (such as Azure CLI and Python SDK) before or alongside PowerShell.
- Provide explicit Linux/Unix command-line examples (e.g., using Azure CLI) where automation or scripting is discussed.
- In feature descriptions (such as auto-shutdown), mention Linux and Windows together or alternate their order to avoid 'Windows first' bias.
- Include references to Linux-specific documentation or supported distributions where relevant.
- Ensure parity in example scripts and workflows for both Windows and Linux users.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/approaches-for-custom-image-creation.md
...s/lab-services/approaches-for-custom-image-creation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux by explicitly mentioning both platforms and providing links to detailed guides for each. However, there is a subtle Windows bias in the order of presentation (Windows is consistently mentioned before Linux) and in the exclusive mention of Windows Hyper-V as the tool for creating VHDs, without reference to common Linux alternatives (e.g., KVM, qemu-img).
Recommendations
- Alternate the order of Windows and Linux mentions throughout the documentation to avoid the perception of prioritizing Windows.
- When describing the creation of VHDs, mention popular Linux-based virtualization tools (such as KVM, qemu-img, or VirtualBox) alongside Windows Hyper-V.
- Provide links or references to official documentation for creating and exporting VHDs from Linux environments.
- Ensure that any tool-specific instructions are paired with Linux equivalents or note cross-platform alternatives where possible.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-plan-python.md
...articles/lab-services/how-to-create-lab-plan-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally cross-platform in its Python code examples, but it exhibits subtle Windows bias by mentioning Azure PowerShell and Az.LabServices cmdlets as next steps, without referencing equivalent CLI or Linux-native tools. Additionally, the default connection profile in the example enables RDP (a Windows protocol) and disables SSH (a Linux/Unix protocol), which may suggest a Windows-centric usage pattern.
Recommendations
- In the 'Next steps' section, include references to Azure CLI and relevant az labservices commands, not just PowerShell modules.
- When discussing connection profiles, provide balanced examples that enable both SSH and RDP, or explain how to configure for Linux (SSH) and Windows (RDP) environments.
- Explicitly state that the Python SDK and examples work on all platforms (Windows, Linux, macOS), and provide any platform-specific notes if needed.
- If mentioning PowerShell, also mention Bash or shell scripting alternatives for Linux users.
- Consider adding a short section or note about using the Azure Cloud Shell, which is cross-platform and accessible from any OS.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-lab-users.md
.../main/articles/lab-services/how-to-manage-lab-users.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Microsoft-centric tools and ecosystems (e.g., Microsoft Excel for CSV editing, Microsoft Entra, Teams, and Office 365) and by describing workflows and account types primarily in the context of Microsoft services. While the instructions are largely web-based and platform-agnostic, the only specific tool mentioned for CSV editing is Microsoft Excel, and Microsoft account workflows are described before alternatives. There are no explicit Linux or open-source tool examples, nor are Linux-specific workflows or tools mentioned.
Recommendations
- When mentioning CSV file creation or editing, suggest cross-platform or open-source alternatives such as LibreOffice Calc, Google Sheets, or command-line tools (e.g., 'You can use Microsoft Excel, LibreOffice Calc, Google Sheets, or a text editor of your choice...').
- When describing account types and workflows, clarify that non-Microsoft users (including those on Linux or macOS) can participate fully, and provide guidance for users who may not use Microsoft accounts or tools.
- Where possible, include examples or notes for users on non-Windows platforms, such as how to generate or edit CSV files using Linux command-line utilities (e.g., 'cat', 'awk', 'sed') or open-source spreadsheet applications.
- Avoid implying that Microsoft tools are required by default; instead, present them as one of several options.
- If screenshots or instructions reference platform-specific UI or behaviors, consider including notes or alternatives for users on other operating systems.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-set-virtual-machine-passwords.md
...s/lab-services/how-to-set-virtual-machine-passwords.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes password setting/resetting processes in a way that assumes Windows as the default or primary OS. It references features (such as 'Use same password for all virtual machines') that are not supported on Ubuntu, but does not provide equivalent Linux/Ubuntu-specific instructions or examples. There are no Linux command-line or GUI examples, and the screenshots and dialog descriptions appear Windows-centric.
Recommendations
- Include explicit instructions and screenshots for setting and resetting passwords on Linux/Ubuntu VMs, highlighting any differences in workflow.
- Provide Linux/Ubuntu-specific notes or sections, especially where features differ (e.g., explain how password management works for Ubuntu VMs if the 'same password' feature is not supported).
- Avoid presenting Windows workflows or features as the default; instead, structure documentation to address both Windows and Linux users equally, or clearly indicate when instructions are OS-specific.
- Add command-line examples for both Windows (PowerShell) and Linux (bash/ssh) 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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias, particularly in the sections discussing disk data loss during reimage and redeploy operations. The OS and temporary disks are described with Windows-centric drive letters (C: and D:) without mentioning Linux equivalents (such as / or /mnt). There are no explicit Linux examples or references to Linux-specific behaviors, and the only disk references are to Windows conventions. No PowerShell commands or Windows-only tools are shown, but the documentation implicitly assumes a Windows context in its explanations.
Recommendations
- When describing disk data loss, mention both Windows and Linux conventions (e.g., 'C: drive on Windows or / on Linux').
- Clarify that the instructions apply to both Windows and Linux VMs where applicable, and note any differences.
- If possible, include screenshots or examples that show Linux VM scenarios, or explicitly state that the process is the same for Linux.
- Add a note or table mapping Windows disk letters to Linux mount points for clarity.
- Review other sections for implicit Windows assumptions and ensure Linux parity in terminology and examples.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab-teams-canvas.md
...ticles/lab-services/tutorial-setup-lab-teams-canvas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server 2022 Datacenter as the example virtual machine image when creating a lab. There are no examples or mentions of Linux-based images or instructions for Linux users. The documentation does not provide parity in showcasing Linux options or workflows, which may lead users to believe that only Windows environments are supported or recommended.
Recommendations
- Include Linux-based virtual machine images (e.g., Ubuntu, CentOS) as example options alongside Windows in the lab creation steps.
- Provide a brief note or table listing both Windows and Linux image options available in Azure Lab Services, with links to further documentation.
- Add example scenarios or screenshots that demonstrate creating and connecting to a Linux VM, including any differences in credential setup (e.g., SSH keys vs. passwords).
- Clarify in the prerequisites or relevant sections that both Windows and Linux environments are supported, and link to guidance for each.
- Ensure troubleshooting and next steps sections mention Linux-specific considerations where relevant.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-access-lab-virtual-machine-teams-canvas.md
...es/tutorial-access-lab-virtual-machine-teams-canvas.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation mentions connecting to lab VMs using RDP (typically Windows) or SSH (typically Linux), but does not provide any concrete examples or instructions for either method. There are no command-line examples for connecting from Windows (e.g., using PowerShell or Remote Desktop Connection) or from Linux/macOS (e.g., using ssh in the terminal). However, the order of mentioning RDP before SSH subtly prioritizes Windows usage patterns, and the lack of explicit Linux/macOS instructions or screenshots constitutes a missing Linux example bias.
Recommendations
- Provide step-by-step examples for connecting to the lab VM using SSH from Linux/macOS terminals, including sample ssh commands.
- Include instructions and screenshots for connecting via RDP from Windows, and also from Linux/macOS using open-source RDP clients (e.g., Remmina, rdesktop, FreeRDP).
- When describing connection methods, alternate the order (e.g., mention SSH before RDP in some places) or clarify that both are equally supported depending on the VM OS.
- Explicitly state which connection method is appropriate for which OS (e.g., 'Use RDP for Windows VMs, SSH for Linux VMs'), and provide parity in documentation for both scenarios.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab.md
.../blob/main/articles/lab-services/tutorial-setup-lab.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently presents Windows as the default or only option for lab virtual machines, specifically instructing users to select 'Windows 11 Pro' as the VM image. There are no examples, instructions, or mentions of using Linux-based images or connecting to Linux VMs. All connection instructions reference Remote Desktop (RDP), which is primarily a Windows protocol, with no mention of SSH or Linux-compatible tools. No Linux-specific setup, customization, or troubleshooting is included.
Recommendations
- Include Linux as an alternative in the 'Virtual machine image' selection step (e.g., Ubuntu, CentOS, etc.), and provide parallel instructions for setting up a Linux-based lab.
- Add examples and screenshots for connecting to Linux VMs, such as using SSH clients (e.g., PuTTY, OpenSSH) instead of only RDP.
- Mention Linux-specific customization steps, such as installing software via apt/yum and setting up user accounts.
- Ensure troubleshooting and access instructions cover both Windows and Linux VM scenarios.
- Wherever possible, present Windows and Linux options side-by-side, or clarify that the instructions apply to both, with notes on differences.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-set-virtual-machine-passwords.md
...s/lab-services/how-to-set-virtual-machine-passwords.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page predominantly describes password setting/resetting in a way that assumes Windows as the default, with screenshots and dialog text referencing Windows. There is only a brief mention of Ubuntu in a parenthetical note, and no Linux-specific instructions, screenshots, or examples are provided. The process for Linux VMs is not explained, and the UI appears Windows-centric.
Recommendations
- Include explicit instructions and screenshots for setting and resetting passwords on Linux-based VMs (e.g., Ubuntu), highlighting any differences in workflow or UI.
- Clarify any limitations or differences for Linux VMs beyond the single parenthetical note (e.g., how students set passwords, what dialog boxes look like, or if command-line tools are needed).
- Ensure that examples and images alternate between Windows and Linux, or provide parallel sections for each platform.
- Avoid language that assumes Windows as the default; instead, structure the documentation to address both Windows and Linux VMs equally.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab-teams-canvas.md
...ticles/lab-services/tutorial-setup-lab-teams-canvas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-based examples for virtual machine images (specifically 'Windows Server 2022 Datacenter') and does not mention or demonstrate Linux-based alternatives. There are no examples, screenshots, or instructions for creating or using Linux VMs, nor are Linux-specific considerations or options discussed. This presents a Windows-first bias and omits Linux parity in the tutorial workflow.
Recommendations
- Include Linux-based virtual machine image options (e.g., Ubuntu, CentOS) alongside Windows in the 'Create a new lab' section.
- Provide example walkthroughs and screenshots for creating a lab using a Linux VM image.
- Mention any Linux-specific configuration steps or differences, such as SSH key setup or default credentials.
- Ensure troubleshooting and next steps sections address both Windows and Linux VM scenarios.
- Clarify that both Windows and Linux VMs are supported by Azure Lab Services, and link to relevant documentation for each.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-setup-lab.md
.../blob/main/articles/lab-services/tutorial-setup-lab.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows 11 Pro as the virtual machine image in the example, and by only describing remote desktop (RDP) connections, which are primarily associated with Windows environments. There are no examples or instructions for creating labs with Linux VM images, nor are there any Linux-specific configuration or connection instructions. The documentation does not mention or show parity for Linux users or scenarios.
Recommendations
- Provide examples that use both Windows and Linux VM images when creating a lab, or explicitly mention that Linux images are supported.
- Include instructions or screenshots for connecting to Linux-based lab VMs, such as using SSH, in addition to RDP for Windows.
- When listing software installation examples, include popular Linux tools or editors (e.g., VS Code, vim, gcc) and show how to install them on Linux.
- Clarify in the prerequisites or relevant sections that both Windows and Linux environments are supported, and link to documentation for both.
- Ensure that any step or screenshot that is OS-specific is accompanied by a Linux equivalent, or at least a note about Linux usage.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/concept-lab-accounts-versus-lab-plans.md
.../lab-services/concept-lab-accounts-versus-lab-plans.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias, primarily by referencing the Az PowerShell module as the only command-line SDK example and listing it before mentioning .NET and Python SDKs. There are no explicit Linux CLI (e.g., Azure CLI) examples or references, and no mention of Linux-specific tools or workflows. While the page does mention improved auto-shutdown for both Windows and Linux, the SDK/tooling focus is Windows-centric.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples when discussing SDKs or automation.
- Explicitly mention Linux compatibility and provide Linux command-line usage patterns where relevant.
- Reference cross-platform tools (e.g., Azure CLI) in addition to Windows-centric tools (e.g., PowerShell).
- Ensure that any SDK or automation guidance is not presented as PowerShell-first; consider listing Python, .NET, and CLI options equally.
- Add links or notes about managing Azure Lab Services from Linux environments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/approaches-for-custom-image-creation.md
...s/lab-services/approaches-for-custom-image-creation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows tools and workflows before Linux equivalents, particularly in the section about creating VHDs, where Windows Hyper-V is mentioned as the default tool for both Windows and Linux images. There is a notable absence of Linux-native tooling (such as KVM, qemu-img, or VirtualBox) for creating VHDs, and the only example of on-premises image creation references Windows Hyper-V. While both Windows and Linux are acknowledged throughout, Windows-centric tools and patterns are prioritized or exclusively mentioned in some key steps.
Recommendations
- When describing how to create VHDs for custom images, include Linux-native tools such as KVM, qemu-img, or VirtualBox alongside Hyper-V, with links to relevant documentation.
- Where steps differ for Windows and Linux, provide parallel, side-by-side instructions or clearly separate sections for each OS.
- Avoid presenting Windows tools as the default or only option for cross-platform workflows; instead, introduce both Windows and Linux options together.
- Consider adding a summary table or matrix showing supported tools and workflows for both Windows and Linux environments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-bring-custom-linux-image-azure-vm.md
...b-services/how-to-bring-custom-linux-image-azure-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Linux custom images, presents Windows-centric links and examples first when describing how to create an Azure VM. Specifically, the instructions for creating a VM reference Windows portal, PowerShell, and CLI documentation before any Linux-specific equivalents, and do not provide direct Linux-focused examples or links. This may confuse or inconvenience Linux users and gives the impression of a Windows-first approach.
Recommendations
- Provide Linux-specific links and examples alongside or before Windows options when describing how to create an Azure VM (e.g., link to /azure/virtual-machines/linux/quick-create-portal and /azure/virtual-machines/linux/quick-create-cli).
- Ensure that all example commands, scripts, and references are either Linux-specific or presented in both Windows and Linux variants.
- Review the documentation for any other Windows-centric language or assumptions and revise to ensure Linux users are equally supported.
- Consider adding a dedicated section or callout for Linux users to clarify any differences in process or tooling.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-create-lab-plan-python.md
...articles/lab-services/how-to-create-lab-plan-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell and Az.LabServices cmdlets as next steps, without mentioning equivalent CLI or Linux-native tools. While the main content is cross-platform Python, the only administrative tooling highlighted is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include references to Azure CLI (az labservices) commands as alternatives to PowerShell cmdlets for managing lab plans and resources.
- Explicitly state that the Python code examples are cross-platform and can be run on Linux, macOS, and Windows.
- Provide links to documentation for both Azure CLI and PowerShell, ensuring Linux users are equally supported.
- If mentioning PowerShell, clarify that PowerShell Core is available cross-platform, or provide Bash/CLI equivalents where possible.