Lab Services

254
Total Pages
226
Linux-Friendly Pages
28
Pages with Bias
11.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

55 issues found
Showing 26-50 of 55 flagged pages
Lab Services Tutorial: Create a lab in Teams or Canvas ...ticles/lab-services/tutorial-setup-lab-teams-canvas.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending 'Windows Server 2022 Datacenter' as the virtual machine image in the lab creation example, without mentioning or providing Linux-based alternatives. No Linux VM images are suggested, and no Linux-specific instructions or parity notes are present. This may lead users to assume Windows is the only or preferred option, creating friction for those seeking Linux environments.
Recommendations
  • Include Linux-based VM images (e.g., Ubuntu, CentOS) as options in the lab creation example table.
  • Add notes or examples showing how to select and configure a Linux VM image.
  • Clarify that both Windows and Linux VM images are supported, and link to documentation listing available images.
  • Provide troubleshooting tips relevant to Linux VM usage if applicable.
GitHub Create Pull Request
Lab Services Create a lab for classroom training .../blob/main/articles/lab-services/tutorial-setup-lab.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 lab creation steps, and by only describing remote desktop (RDP) connection workflows, which are most commonly associated with Windows environments. There are no examples or instructions for selecting Linux VM images, connecting via SSH (the standard for Linux), or installing Linux-specific software. This may create friction for users intending to use Linux-based labs or those unfamiliar with Windows-centric workflows.
Recommendations
  • Include instructions and screenshots for creating labs with Linux VM images (e.g., Ubuntu, CentOS).
  • Provide examples for connecting to Linux VMs using SSH, including how to retrieve SSH connection details.
  • Mention Linux/macOS-compatible software installation steps and tools.
  • Present Windows and Linux options side-by-side in tables or as alternative steps, rather than only referencing Windows.
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and link to relevant documentation for each.
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (such as idle disconnect) are described in detail, with references to Windows OS definitions and screenshots. Linux support is mentioned only as an exception or limitation, with no equivalent technical explanation or examples. The 'Next steps' section promotes PowerShell (a Windows-centric tool) for lab account management, without mentioning Linux CLI or cross-platform alternatives.
Recommendations
  • Provide Linux-specific examples and screenshots where features differ or are supported.
  • Include Azure CLI or Bash examples for lab account management alongside PowerShell.
  • Clarify feature parity and limitations for Linux VMs, and link to relevant Linux documentation.
  • List Linux tools and workflows in 'Next steps', such as az CLI commands, to balance PowerShell references.
  • When describing features available only on Windows, suggest Linux alternatives or workarounds if possible.
GitHub Create Pull Request
Lab Services Configure automatic shutdown for a lab ...cles/lab-services/how-to-enable-shutdown-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for automatic shutdown, but provides more detailed guidance and links for Windows (e.g., a guide to controlling Windows shutdown behavior) while lacking equivalent Linux-specific troubleshooting or configuration examples. Linux support is discussed, but only in terms of distribution compatibility, not with practical examples or guidance.
Recommendations
  • Add a Linux-specific troubleshooting or configuration guide similar to the 'Guide to controlling Windows shutdown behavior' for Linux distributions.
  • Include examples or screenshots showing auto-shutdown configuration and expected behavior for popular Linux distributions.
  • Provide links to Linux documentation for remote session management and shutdown behavior.
  • Clarify any Linux-specific caveats or steps in the main workflow, not just in the support matrix.
GitHub Create Pull Request
Lab Services Troubleshoot a lab VM .../articles/lab-services/how-to-reset-and-redeploy-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows drive letters (C: and D:) when describing disk locations, listing PowerShell as the only CLI example for automation, and omitting Linux-specific examples or equivalent Linux tooling. There is no mention of Linux shell commands, nor are Linux disk mount points referenced. The REST API is platform-neutral, but the CLI automation guidance is Windows-centric.
Recommendations
  • Add Linux-specific examples for disk locations (e.g., /mnt/osdisk, /mnt/tempdisk) alongside Windows drive letters.
  • Include CLI automation examples using Azure CLI (az labservices ...) or Bash scripts, not just PowerShell.
  • Clarify that the REST API and .NET SDK are cross-platform and provide sample usage for Linux/macOS environments.
  • Reorder references so that platform-neutral or Linux examples are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Lab Services How to bring a Linux custom image from an Azure virtual machine. ...b-services/how-to-bring-custom-linux-image-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page, while focused on Linux custom images, presents Windows-centric links and examples first when discussing VM creation. The links for creating a VM via portal, PowerShell, CLI, and ARM template all point to Windows-specific documentation, despite the Linux focus. No Linux-specific examples or links are provided for these steps.
Recommendations
  • Update VM creation links to point to Linux-specific documentation (e.g., /azure/virtual-machines/linux/quick-create-portal, /azure/virtual-machines/linux/quick-create-powershell, etc.).
  • Provide Linux-specific command examples alongside or before Windows examples.
  • Ensure that any tool or process mentioned (such as PowerShell) is accompanied by equivalent Linux instructions (e.g., Bash, Azure CLI).
  • Review all referenced documentation to ensure Linux parity and clarity for Linux users.
GitHub Create Pull Request
Lab Services Administrator guide using lab accounts | Microsoft Docs ...ob/main/articles/lab-services/administrator-guide-1.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform and avoids explicit OS-specific instructions, but there is a notable Windows bias in the 'Endpoint management' section, which references Windows-specific concepts (machine SIDs, SysPrep, PsGetSid) and endpoint management tools (Microsoft Configuration Manager) without mentioning Linux/macOS equivalents or considerations. Windows tools and patterns are mentioned exclusively in this context, and no Linux/macOS endpoint management guidance is provided.
Recommendations
  • Add guidance for endpoint management on Linux/macOS VMs, including discussion of relevant tools and practices (e.g., cloud-init, Ansible, Puppet, Chef, etc.).
  • Clarify whether machine SID issues are relevant only for Windows, and provide information about analogous identity management concerns for Linux/macOS VMs (e.g., hostname, SSH keys, user/group IDs).
  • Include examples or references for managing Linux/macOS VMs in lab environments, especially where endpoint management or image generalization is required.
  • When mentioning Windows tools (SysPrep, PsGetSid), also mention Linux/macOS image preparation tools and practices.
GitHub Create Pull Request
Lab Services Connect to a lab VM from Chromebook ...s/connect-virtual-machine-chromebook-remote-desktop.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on using the Microsoft Remote Desktop app to connect to Azure Lab Services VMs from a Chromebook, with all instructions and screenshots centered on this Windows-origin tool. While it briefly mentions SSH as an option for Linux VMs and references Chrome Remote Desktop as an alternative, it does not provide any examples, instructions, or parity for connecting to Linux VMs via SSH or using non-Microsoft RDP clients. The documentation implicitly prioritizes Microsoft tools and workflows, leaving Linux/macOS users with less guidance and fewer options.
Recommendations
  • Add step-by-step instructions for connecting to Linux VMs via SSH from a Chromebook, including recommended SSH clients or Chrome OS terminal usage.
  • Provide examples and screenshots for using alternative RDP clients (e.g., Chrome Remote Desktop, Remmina, FreeRDP) on Chromebook, especially for Linux VMs.
  • Clarify the differences in connection workflows between Windows and Linux VMs, and offer guidance for both scenarios.
  • Include troubleshooting tips for Linux VM connections, such as firewall or xrdp configuration issues.
  • Balance recommendations so that Microsoft Remote Desktop is not presented as the only viable option.
GitHub Create Pull Request
Lab Services Use Azure Lab Services for hackathon ...docs/blob/main/articles/lab-services/hackathon-labs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific guidance (such as installing/stopping Windows updates and configuring OneDrive) is given dedicated sections, while Linux instructions are less detailed and mostly limited to enabling RDP/SSH. Windows features (like autoshutdown after RDP disconnect) are mentioned without Linux equivalents. Backup instructions focus on OneDrive (a Windows-centric tool) with no mention of Linux alternatives. Examples and instructions for Linux are less comprehensive, and Windows is often referenced first.
Recommendations
  • Provide equivalent, detailed Linux guidance for VM preparation, such as update management, GUI/RDP setup, and backup solutions (e.g., Nextcloud, Dropbox, or generic cloud storage).
  • Mention Linux/macOS tools and workflows alongside Windows (e.g., alternatives to OneDrive, update management commands, autoshutdown options).
  • Ensure examples and instructions are presented for both Windows and Linux, ideally side-by-side or in parallel sections.
  • Clarify which features or settings are OS-specific, and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Lab Services Lab Services administrator guide ...blob/main/articles/lab-services/administrator-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays mild Windows bias, primarily in sections discussing endpoint management and GPU VM sizing. Windows-specific tools (SysPrep, PsGetSid) and endpoint management scenarios are described in detail, while Linux equivalents or considerations are not mentioned. GPU VM sizes for visualization are marked as '(Windows only)' without clarifying Linux alternatives or limitations. No PowerShell-heavy examples or explicit Windows-first ordering in general instructions, but some critical management scenarios are Windows-centric.
Recommendations
  • Add equivalent Linux endpoint management guidance, such as how to handle machine identity and image generalization for Linux VMs.
  • Clarify GPU VM visualization support for Linux: note whether Linux is unsupported, or provide instructions for Linux remote visualization scenarios.
  • Mention Linux tools or commands where Windows tools (SysPrep, PsGetSid) are referenced, e.g., suggest 'cloud-init' or 'waagent' for Linux image generalization.
  • Where Windows-only features are listed, explicitly state Linux limitations or alternatives.
  • Include Linux/macOS-specific examples or notes in relevant sections, especially for image management and endpoint management.
GitHub Create Pull Request
Lab Services Connect to Azure Lab Services VMs from Mac ...services/connect-virtual-machine-mac-remote-desktop.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page instructs Mac users to install and use the 'Windows App' (Microsoft's RDP client) to connect to Azure Lab Services VMs, focusing exclusively on this Windows-branded tool. It does not mention alternative RDP clients available for macOS (such as Microsoft Remote Desktop for Mac or open-source options), nor does it provide parity for connecting to Linux VMs beyond a brief mention of SSH and a link to a separate X2Go guide. The emphasis on 'Windows App' and lack of alternative client suggestions creates a Windows-centric experience, even for Mac users.
Recommendations
  • Mention and provide instructions for alternative RDP clients available on macOS, such as Microsoft Remote Desktop for Mac, FreeRDP, or Royal TSX.
  • Clarify whether 'Windows App' is required or if other RDP clients can be used, and provide guidance for those.
  • Include a brief comparison or recommendation for connecting to Linux VMs, referencing both SSH and graphical options like X2Go, within the main article rather than only in 'Related content'.
  • Ensure screenshots and instructions reflect the actual user experience on macOS, not just the use of Windows-branded tools.
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The primary workflow for preparing a Linux image relies on Windows-specific tooling (Hyper-V Manager, PowerShell), with step-by-step instructions and screenshots for these tools. Linux-native hypervisors (e.g., KVM, qemu) are only briefly mentioned and not documented with equivalent detail or examples. Upload instructions reference Windows-centric guides and PowerShell modules, with no Linux CLI or tool alternatives provided. This creates friction for users on Linux or macOS who wish to import images from their own environments.
Recommendations
  • Provide parallel instructions for preparing and converting images using Linux-native hypervisors (e.g., KVM, qemu-img), including command examples.
  • Include Linux CLI commands for uploading VHDs to Azure (e.g., az CLI, AzCopy on Linux).
  • Reference Linux documentation and guides with the same prominence as Windows guides.
  • Add screenshots and step-by-step instructions for Linux workflows.
  • Clarify which steps are platform-agnostic and which require platform-specific tools.
GitHub Create Pull Request
Lab Services Firewall settings for Azure Lab Services ...les/lab-services/how-to-configure-firewall-settings.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell examples and references the Az.LabServices PowerShell module for determining the public IP address of Azure Lab Services VMs. There are no equivalent examples or instructions for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform tools). The focus on PowerShell and Windows-centric tools creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent instructions and code examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for retrieving the public IP address.
  • Clearly indicate that PowerShell Core is available on Linux/macOS, and provide installation guidance if PowerShell is required.
  • Present examples for both Windows and Linux/macOS users, ideally side-by-side.
  • Reference documentation for Azure CLI commands relevant to Lab Services.
GitHub Create Pull Request
Lab Services Create a lab plan using Bicep or ARM .../articles/lab-services/how-to-create-lab-plan-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management tasks, but PowerShell is given equal or greater prominence throughout. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there notes about platform-specific differences. The ARM template deployment section defaults to the Azure portal, which is platform-agnostic, but the alternative methods link specifically to PowerShell documentation first. There is no mention of Linux-specific considerations or troubleshooting.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside PowerShell, especially for tasks like file saving and command execution.
  • Clarify that Azure CLI works cross-platform and highlight any OS-specific nuances.
  • When referencing alternative deployment methods, link to both PowerShell and CLI documentation equally, or provide a combined link.
  • Add notes or sections addressing Linux/macOS users, including any prerequisites or differences in experience.
  • Ensure example commands do not assume Windows file paths or conventions.
GitHub Create Pull Request
Lab Services Create a lab using Bicep .../main/articles/lab-services/how-to-create-lab-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and references to PowerShell (a Windows-centric tool) are frequent. The ARM template deployment section references PowerShell before CLI and REST API, and links to PowerShell-specific documentation. There are no explicit Linux/macOS examples or notes about cross-platform usage, and PowerShell is mentioned as a primary tool throughout.
Recommendations
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and recommend it for non-Windows users.
  • Provide examples or notes for Bash shell usage where relevant.
  • List Azure CLI examples before PowerShell to reduce Windows-first perception.
  • Add guidance for installing and using Azure CLI and PowerShell on Linux/macOS.
  • Clarify that PowerShell Core is available cross-platform, if recommending PowerShell.
  • Link to cross-platform deployment documentation, not just PowerShell-specific guides.
GitHub Create Pull Request
Lab Services Create a lab using Python ...main/articles/lab-services/how-to-create-lab-python.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing Windows VM images exclusively in code examples, mentioning RDP (Remote Desktop Protocol) access as the default connection method, and listing Azure PowerShell and Az.LabServices cmdlets as next steps without equivalent Linux/macOS CLI alternatives. There are no examples or mentions of Linux VM images, SSH access, or cross-platform command-line tools in the main workflow.
Recommendations
  • Include examples using Linux VM images (e.g., Ubuntu, CentOS) in the Python code samples.
  • Demonstrate how to configure SSH access (webSshAccess/clientSshAccess) for Linux VMs.
  • In the 'Next steps' section, provide links to Azure CLI documentation and examples for managing labs, which are cross-platform.
  • Clarify that the Python SDK and authentication methods are cross-platform, and provide any platform-specific notes if needed.
  • Present both Windows and Linux options for VM creation and management, ideally side-by-side.
GitHub Create Pull Request
Lab Services Accelerated lab setup guide for Azure Lab Services ...re-docs/blob/main/articles/lab-services/setup-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features and tools (such as automatic shutdown after RDP disconnect and OneDrive setup) are mentioned explicitly, while Linux equivalents are either omitted or referenced only briefly. Windows connection methods (RDP) are described in more detail and presented first, with Linux options (SSH, RDP) mentioned later and without setup guidance. There are references to Windows-specific instructions and tools, but Linux/macOS users are not provided with equivalent step-by-step examples or recommendations.
Recommendations
  • Provide parallel Linux/macOS examples and instructions for all major setup steps, especially for VM connection, shutdown automation, and external storage integration.
  • Include details on configuring RDP and GUI environments for Linux VMs, or link to relevant guides.
  • Mention Linux-friendly storage solutions (e.g., Nextcloud, SFTP, NFS) alongside OneDrive.
  • Clarify cost-control features for Linux VMs, including how to automate shutdown after SSH disconnect.
  • Ensure that all OS-specific instructions are grouped together or presented in parallel, rather than Windows-first.
GitHub Create Pull Request
Lab Services Troubleshoot connectivity issues with Azure Lab Services ...n/articles/lab-services/troubleshoot-connect-lab-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits moderate Windows bias. Troubleshooting steps and examples frequently reference Windows tools (PsPing), Windows-specific settings (Remote Desktop client experience), and PowerShell (for activity log filtering). Linux/macOS equivalents (e.g., SSH troubleshooting, Linux network tools) are not mentioned, and Windows terminology and links are presented first or exclusively in several sections.
Recommendations
  • Include Linux/macOS troubleshooting steps and examples alongside Windows ones, such as using SSH for connectivity checks and Linux network tools (e.g., ping, traceroute, nmap).
  • Mention cross-platform alternatives to Windows-only utilities like PsPing (e.g., use 'ping', 'iperf', or 'nc' on Linux/macOS).
  • Provide guidance for adjusting RDP/SSH client settings on Linux/macOS (e.g., Remmina, rdesktop, or native SSH clients).
  • When referencing PowerShell or Windows-specific Azure portal features, also describe how to perform equivalent actions using Azure CLI or Bash.
  • Ensure that troubleshooting steps and terminology are presented in a platform-neutral way, or at least alternate between Windows and Linux/macOS examples.
GitHub Create Pull Request
Lab Services Tutorial: Create a lab in Teams or Canvas ...ticles/lab-services/tutorial-setup-lab-teams-canvas.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending 'Windows Server 2022 Datacenter' as the virtual machine image in the lab creation example, without mentioning or providing examples for Linux-based images. There are no Linux/macOS-specific instructions, nor are alternative OS images suggested or shown in screenshots. The documentation does not discuss Linux VM options or provide parity in examples for non-Windows users.
Recommendations
  • Include Linux-based VM images (e.g., Ubuntu, CentOS) as options in the lab creation example and screenshots.
  • Provide step-by-step instructions and screenshots for creating labs with Linux VM images.
  • Mention that both Windows and Linux images are supported, and link to documentation about selecting and configuring Linux VMs.
  • Clarify any differences in credential setup or remote access methods (e.g., SSH for Linux, RDP for Windows).
  • Ensure troubleshooting and next steps sections address Linux-specific scenarios.
GitHub Create Pull Request
Lab Services Use advanced networking in Azure Lab Services | Microsoft Docs ...rvices/tutorial-create-lab-with-advanced-networking.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows is the default and only example for VM image selection, with explicit instructions for enabling ICMP using Windows PowerShell cmdlets. There are no equivalent Linux/macOS instructions for firewall configuration or VM image selection, and Windows terminology (RDP, PowerShell) is used first and exclusively in critical steps.
Recommendations
  • Include explicit Linux VM image selection steps and mention Linux images as equally valid options.
  • Provide Linux/macOS firewall configuration instructions (e.g., using ufw or firewalld) for enabling ICMP.
  • Offer SSH connection instructions and examples for Linux/macOS users, not just RDP for Windows.
  • Present both Windows and Linux examples side by side, or clearly indicate when steps differ by OS.
  • Avoid assuming Windows as the default; use neutral language and highlight cross-platform support.
GitHub Create Pull Request
Lab Services Create a lab for classroom training .../blob/main/articles/lab-services/tutorial-setup-lab.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows 11 Pro as the VM image in the main example, and by only describing connection via Remote Desktop (RDP), which is most commonly associated with Windows environments. There are no examples or mentions of Linux VM images, nor instructions for connecting to Linux-based VMs (e.g., via SSH). All customization and connection steps assume a Windows VM and workflow.
Recommendations
  • Include Linux VM image options (e.g., Ubuntu, CentOS) in the 'Create a lab' section alongside Windows.
  • Provide parallel instructions for connecting to Linux VMs (e.g., using SSH) in the 'Customize the lab template' section.
  • Add examples of installing software relevant to Linux environments (e.g., Python, gcc) in the customization steps.
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and link to documentation for both.
  • Ensure screenshots and field descriptions do not exclusively reference Windows unless the tutorial is specifically Windows-focused.
GitHub Create Pull Request
Lab Services Quickstart: Create lab plan resource ...b/main/articles/lab-services/quick-create-resources.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a minor Windows bias by featuring a 'Quickstart: Create a Windows-based lab' as the next step, without mentioning Linux-based lab creation or providing parity for non-Windows environments. No command-line or tool-specific examples are present, so the bias is limited to the ordering and focus of follow-up content.
Recommendations
  • Add a parallel quickstart or link for creating a Linux-based lab.
  • Mention that Azure Lab Services supports both Windows and Linux labs in the introduction and next steps.
  • Ensure future examples and tutorials provide both Windows and Linux options where applicable.
GitHub Create Pull Request
Lab Services Create a lab using Bicep .../main/articles/lab-services/how-to-create-lab-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup, but PowerShell is given equal prominence and is referenced frequently, which may suggest a slight Windows bias. However, Azure CLI is cross-platform and shown first in most cases. There are no exclusive Windows tools or patterns, and Linux/macOS users can follow all steps using Azure CLI. No Linux-specific examples (e.g., bash scripts) are provided, but the CLI commands are sufficient for Linux parity.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and Windows.
  • Add example bash scripts or shell usage for Linux users where appropriate.
  • Clarify that PowerShell examples are for users who prefer PowerShell, and that CLI is recommended for cross-platform usage.
  • Consider providing Linux/macOS screenshots or notes where UI steps are shown.
  • Add a note about installing Azure CLI on Linux/macOS.
GitHub Create Pull Request
Lab Services Create a lab plan using Python ...articles/lab-services/how-to-create-lab-plan-python.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure PowerShell and Az.LabServices cmdlets as next steps, which are Windows-centric tools. These are mentioned without equivalent Linux/macOS alternatives, and are presented before any cross-platform CLI options. The Python code samples themselves are cross-platform, but the 'Next steps' section introduces Windows bias.
Recommendations
  • Include Azure CLI equivalents for lab management tasks alongside PowerShell references.
  • Explicitly state that the Python code samples work on Linux/macOS as well as Windows.
  • Add links to documentation for managing Azure Lab Services using Azure CLI or REST API, which are cross-platform.
  • Reorder or balance the 'Next steps' section to present cross-platform tools before or alongside Windows-specific ones.
GitHub Create Pull Request
Lab Services Troubleshoot lab creation ...ain/articles/lab-services/troubleshoot-lab-creation.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias by referencing a PowerShell script as the only example for querying lab quotas, without mentioning Linux/macOS alternatives (such as Azure CLI or Bash). The tip about running a script to query quotas links specifically to a PowerShell solution, which is typically associated with Windows environments. No Linux/macOS-specific tools or examples are provided, and the PowerShell example appears before any mention of cross-platform options.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for querying lab quotas, and link to them alongside the PowerShell script.
  • Explicitly state that PowerShell Core is cross-platform if recommending PowerShell, and clarify usage on Linux/macOS.
  • Ensure troubleshooting steps reference tools and commands available on all major platforms (Windows, Linux, macOS).
  • Add a note or section on how Linux/macOS users can perform the same tasks using their preferred tools.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →