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 176-200 of 272 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is focused on bringing a Linux custom image from an Azure VM, but in the 'Prepare a custom image on an Azure VM' section, it lists Windows-centric links and tools (Azure portal, PowerShell, CLI, ARM template) with URLs pointing to Windows VM creation guides. Windows examples and links are presented first, and there is no direct link to Linux VM creation guides or Linux-specific tooling. This may create confusion or friction for Linux users, as they must manually find the Linux equivalents.
Recommendations
  • Provide direct links to Linux VM creation guides for the Azure portal, PowerShell, CLI, and ARM template.
  • List Linux options before or alongside Windows options when describing VM creation.
  • Include Linux-specific examples or commands where relevant.
  • Clarify that the steps apply to both Windows and Linux, and highlight any Linux-specific considerations.
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-14 00:00
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 PowerShell is a Windows-centric tool. There is no mention of Bash, Linux shell, or macOS-specific considerations. The ARM template deployment section prioritizes the Azure Portal (a graphical interface, often used on Windows) and links to PowerShell deployment documentation before CLI. There are no explicit Linux/macOS examples or notes about cross-platform usage, and PowerShell is referenced throughout without clarifying its cross-platform availability.
Recommendations
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide Bash shell examples where appropriate.
  • Clarify that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
  • In the ARM deployment section, link to CLI deployment documentation before PowerShell, or provide both links equally.
  • Add notes or sections highlighting any OS-specific considerations, such as file path formats or authentication differences.
  • Consider including screenshots or instructions for Linux/macOS users where UI or tool differences exist.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias. Windows-specific features (like automatic shutdown after RDP disconnect) are described in detail, while Linux equivalents are only briefly mentioned or omitted. Windows tools (OneDrive, Microsoft Office, Microsoft Remote Desktop client) are referenced with setup instructions, but Linux alternatives are not provided. Windows connection methods (RDP) are explained first and more thoroughly, with Linux (SSH/RDP) mentioned second and with less guidance. There are no Linux/macOS-specific setup examples or tool recommendations.
Recommendations
  • Provide explicit Linux/macOS setup instructions and examples alongside Windows ones, especially for template VM preparation and connection methods.
  • Include guidance for configuring Linux VMs for RDP (e.g., installing xrdp and a desktop environment), and mention SSH clients for Windows, macOS, and Linux.
  • List Linux/macOS alternatives to Windows tools (e.g., alternatives to OneDrive, Office, or mention how to set up Nextcloud or LibreOffice).
  • Ensure that cost control and shutdown features are explained for Linux VMs, including any differences in implementation.
  • Present connection methods and tool recommendations for all platforms equally, not 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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Troubleshooting steps and examples frequently reference Windows-specific tools (PsPing), settings (client experience), and links (Windows Server performance tuning). Powershell is mentioned for activity log filtering, but no equivalent Linux commands or tools are provided. There are references to SSH alongside RDP, but actionable examples and tool recommendations are Windows-centric, and Windows terminology appears first or exclusively in several sections.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps, e.g., recommend 'ping', 'nmap', or 'iperf' for connection speed measurement instead of only PsPing.
  • Include Linux/macOS instructions for checking and adjusting firewall/network settings.
  • Add examples for SSH connectivity troubleshooting, including relevant Linux commands (e.g., 'ssh -v', 'ss', 'netstat').
  • When referencing activity logs, provide Azure CLI or Bash examples alongside Powershell.
  • Ensure parity in troubleshooting links and guides for both Windows and Linux VM scenarios.
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-14 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 examples for Linux-based images. There are no instructions or screenshots showing the selection or use of Linux VM images, nor is there guidance for Linux-specific configuration or access patterns.
Recommendations
  • Include examples that use popular Linux VM images (e.g., Ubuntu, CentOS) in the lab creation steps.
  • Provide a table or list of supported VM images, highlighting both Windows and Linux options.
  • Add screenshots and walkthroughs for creating labs with Linux images, including any differences in credential setup (e.g., SSH keys vs. passwords).
  • Mention Linux-specific access methods (e.g., SSH from Linux/macOS terminals) where relevant.
  • Ensure troubleshooting steps cover issues unique to Linux VM images.
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-14 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 main example, and only describing connection via Remote Desktop Protocol (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 or using SSH, which is standard for Linux/macOS users.
Recommendations
  • Include Linux VM image options in the lab creation example, such as Ubuntu or CentOS.
  • Provide instructions for connecting to Linux VMs using SSH, including example commands for Windows, Linux, and macOS clients.
  • Mention software installation examples relevant to Linux environments (e.g., installing Python or VS Code on Ubuntu).
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and link to documentation on supported images.
  • Ensure screenshots and walkthroughs are not exclusively Windows-centric, or provide parallel Linux examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Disk references use Windows drive letters (C: and D:) exclusively, with no mention of Linux disk conventions. Command-line automation is only demonstrated with PowerShell, omitting Linux/macOS equivalents such as Bash or Azure CLI. No Linux-specific examples or terminology are provided, which may cause confusion or friction for non-Windows users.
Recommendations
  • Include Linux disk references (e.g., /dev/sda1, /mnt, etc.) alongside Windows drive letters when discussing OS and temporary disks.
  • Provide automation examples using Azure CLI and Bash scripts, in addition to PowerShell.
  • Clarify that the web portal and REST API are cross-platform, and explicitly mention Linux/macOS compatibility where relevant.
  • Add screenshots or instructions that show the experience on Linux/macOS systems if there are any differences.
  • Use neutral terminology (e.g., 'OS disk', 'temporary disk') before referencing platform-specific conventions.
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-13 00:00
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, which is primarily used on Windows. There are no Linux/macOS CLI or Azure CLI examples, nor any mention of how to perform the same tasks on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention platform requirements for PowerShell and provide installation guidance for non-Windows users if PowerShell is required.
  • Where possible, provide REST API or portal-based steps as alternatives.
  • Reorder examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside PowerShell examples.
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-13 00:00
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 Windows bias by prioritizing Windows-specific features and examples, such as automatic disconnect on idle (Windows-only), referencing Windows OS definitions, and suggesting PowerShell as the primary automation tool. Linux support is mentioned but with caveats and less detail, and no Linux-specific management examples or CLI alternatives are provided.
Recommendations
  • Provide equivalent Linux management examples, such as using Azure CLI or Bash scripts for lab account operations.
  • Include Linux/macOS screenshots or instructions where applicable, especially for automation and shutdown settings.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and provide usage examples.
  • List Linux support details earlier and more prominently, not just as caveats.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits some Windows bias, particularly in sections discussing endpoint management and GPU VM sizing. Windows-specific tools (SysPrep, PsGetSid, Microsoft Configuration Manager) are mentioned exclusively for endpoint management, with no Linux/macOS equivalents or guidance. GPU VM sizes for visualization are marked as '(Windows only)', but no Linux alternatives or instructions are provided. Overall, Linux and macOS users may find gaps in guidance for endpoint management and visualization workloads.
Recommendations
  • Provide Linux/macOS equivalents or alternatives for endpoint management, such as guidance on managing machine identity and security for Linux VMs.
  • Include examples or references for Linux/macOS endpoint management tools (e.g., cloud-init, Ansible, etc.) and how to generalize images for those platforms.
  • Clarify GPU VM sizing for Linux: indicate which visualization VM sizes are supported for Linux, and provide instructions or links for setting up remote visualization on Linux VMs.
  • Where Windows-only tools are mentioned, explicitly state the limitations for Linux/macOS and offer alternative approaches or workarounds.
  • Ensure that examples and instructions are provided for both Windows and Linux/macOS platforms where relevant, especially in critical workflow sections.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, especially in the 'Endpoint management' section, which discusses Windows-specific concepts like machine SIDs and recommends Windows tools (SysPrep, PsGetSid) without mentioning Linux equivalents or addressing Linux/macOS endpoint management scenarios. The only VM image example explicitly named is the 'Data Science VM for Linux', but overall, Windows patterns and tools are referenced first or exclusively in critical management contexts.
Recommendations
  • Add equivalent guidance for Linux/macOS endpoint management, including discussion of how identity and configuration management differs for non-Windows VMs.
  • Include examples of Linux/macOS tools for verifying machine identity or managing images, such as mentioning cloud-init, /etc/machine-id, or other relevant mechanisms.
  • When referencing Windows-specific tools (SysPrep, PsGetSid), also mention what Linux/macOS users should consider or use in similar scenarios.
  • Provide parity in examples and recommendations for VM images, endpoint management, and content filtering, ensuring Linux/macOS scenarios are covered.
  • Explicitly state when guidance is Windows-only and provide links or notes for Linux/macOS users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias by exclusively recommending the Microsoft Remote Desktop app (a Microsoft product), referencing Windows Server documentation, and prioritizing RDP (a protocol most commonly associated with Windows). While Linux VMs are mentioned, the guidance and examples focus on the Microsoft ecosystem, with alternative RDP clients for Chromebook only briefly noted and discouraged. There are no Linux-specific remote desktop client examples or instructions for connecting to Linux VMs using protocols more common in Linux environments (e.g., VNC, X2Go), nor is there parity in tool recommendations.
Recommendations
  • Include instructions for connecting to Linux VMs using Linux-friendly protocols (e.g., VNC, X2Go) and clients available on Chromebook.
  • Provide examples and screenshots for third-party RDP clients (such as Remmina, FreeRDP, or Chrome Remote Desktop) and clarify their setup for both Windows and Linux VMs.
  • Reference Linux documentation and tools alongside Microsoft/Windows resources, ensuring equal visibility.
  • Offer troubleshooting steps specific to Linux VM connections, including SSH and graphical desktop access.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page instructs Mac users to install and use the 'Windows App' for RDP connections, exclusively referencing Microsoft's tool and documentation. No alternative RDP clients (such as Microsoft Remote Desktop for Mac, FreeRDP, or open-source options) are mentioned. The workflow is centered on Windows tooling, and the only external link is to Microsoft's Windows App documentation. While the page does mention SSH and X2Go for Linux VMs elsewhere, the main RDP instructions are Windows-centric.
Recommendations
  • Include instructions for using alternative RDP clients available on macOS, such as Microsoft Remote Desktop, FreeRDP, or open-source options.
  • Provide a comparison or mention of multiple RDP clients, not just Windows App, to give users choice and flexibility.
  • Add troubleshooting or configuration notes relevant to non-Windows RDP clients.
  • Ensure parity in documentation by linking to guides for connecting to both Windows and Linux VMs using various clients.
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-13 00:00
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 provided in detail, while Linux equivalents (e.g., update management, backup solutions) are missing. Windows tools and features (RDP, OneDrive) are mentioned before or instead of Linux alternatives. Linux instructions are referenced but less detailed, and examples for Linux backup or update management are absent.
Recommendations
  • Provide equivalent Linux guidance for VM preparation, such as instructions for updating Linux systems and managing updates to prevent interruptions.
  • Include Linux-friendly backup solutions (e.g., instructions for configuring Dropbox, Google Drive, or mounting network shares) alongside OneDrive.
  • Ensure examples and instructions for connecting to VMs (RDP/SSH) are balanced, with Linux/macOS client recommendations and step-by-step guides.
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than Windows-first.
  • Reference Linux-specific documentation for common administrative tasks (firewall configuration, remote desktop setup, etc.) where appropriate.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page, while focused on bringing a Linux custom image from an Azure VM, presents Windows-centric links and examples first when describing how to create an Azure VM. The primary links for VM creation reference Windows-specific documentation (portal, PowerShell, CLI, ARM template) without providing direct Linux equivalents or examples. This may cause confusion or extra effort for Linux users seeking platform-relevant instructions.
Recommendations
  • Provide direct links to Linux-specific documentation for creating Azure VMs using the portal, PowerShell, CLI, and ARM templates.
  • Ensure that examples and references for Linux are presented before or alongside Windows examples, especially in Linux-focused articles.
  • Add explicit Linux command-line examples (e.g., Azure CLI commands for Linux VM creation) where relevant.
  • Clarify any differences in process or tooling for Linux users, including prerequisites and image preparation steps.
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-13 00:00
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 creating a Linux image relies on Windows-specific tools (Hyper-V Manager and PowerShell), with step-by-step instructions and screenshots for these. Linux-native hypervisors (like KVM) and workflows are mentioned only briefly and not documented in detail. Upload instructions reference Windows/Powershell guides, and Linux alternatives are not provided or are referenced indirectly. This creates friction for users on Linux or macOS who wish to perform the same tasks natively.
Recommendations
  • Add a parallel workflow for Linux users, detailing how to create and prepare a VHD using KVM or other common Linux hypervisors.
  • Include step-by-step instructions for converting and resizing disks using Linux tools (e.g., qemu-img, dd).
  • Provide upload instructions using Azure CLI or AzCopy from Linux/macOS, with explicit examples.
  • Ensure screenshots and examples are balanced between Windows and Linux environments.
  • Reference and link to Linux-specific documentation where possible, and clarify which steps are OS-agnostic.
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-13 00:00
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, resource review, and cleanup. However, PowerShell examples are consistently present and sometimes highlighted, while there are no explicit Linux/macOS shell examples (e.g., Bash). The ARM template deployment section prioritizes the Azure Portal (a GUI, often associated with Windows) and references PowerShell before CLI in the 'other deployment methods' link. There is no mention of Linux-specific considerations, nor are Bash or shell script examples provided, despite the cross-platform nature of Azure CLI.
Recommendations
  • Add explicit Bash/shell script examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and mention installation instructions for non-Windows platforms.
  • In sections referencing PowerShell, include equivalent Bash or shell commands where possible.
  • When listing deployment methods, avoid listing PowerShell before CLI or provide both in parallel.
  • Add notes or links for Linux/macOS users about prerequisites or environment setup.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The example lab creation uses a Windows 11 image exclusively, with no mention of Linux VM images or configuration. The 'connectionProfile' enables RDP (Remote Desktop Protocol, Windows-centric) and disables SSH (Linux/macOS-centric) access. The 'Next steps' section references Azure PowerShell and Az.LabServices cmdlets, both Windows-first tools, without mentioning Azure CLI or Bash alternatives. No Linux/macOS VM creation or management examples are provided.
Recommendations
  • Include examples for creating labs with Linux VM images (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Show how to configure SSH access in the 'connectionProfile' for Linux/macOS users.
  • Mention Azure CLI and Bash scripting as alternatives to PowerShell for cross-platform management.
  • In 'Next steps', add links to Azure CLI documentation and Linux/macOS-specific guidance.
  • When listing VM images, demonstrate how to enumerate and select both Windows and Linux options.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page generally acknowledges both Windows and Linux support for automatic shutdown in Azure Lab Services. However, there is a notable Windows bias: a warning references only RDP (Windows remote protocol) and links to a Windows-specific shutdown guide, with no equivalent Linux guidance or troubleshooting. There are no Linux-specific configuration examples, troubleshooting steps, or links to Linux shutdown behavior guides. Windows terminology and tools (RDP, Windows shutdown guide) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add a Linux-specific troubleshooting section or link to a guide explaining shutdown behavior for common Linux distributions.
  • Include examples or screenshots for configuring auto-shutdown on Linux-based VMs, especially if the UI or process differs.
  • Provide parity in warnings and guidance, e.g., mention SSH or Linux desktop session disconnects and their impact on auto-shutdown.
  • Reference Linux tools or commands (e.g., systemctl, shutdown) where relevant.
  • Ensure that any Windows-specific links have Linux equivalents or at least a note on Linux differences.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
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 described in detail, while Linux equivalents are either briefly mentioned or omitted. Windows connection methods (RDP) and tools (Microsoft Remote Desktop client) are discussed first and more thoroughly, with Linux alternatives (SSH, RDP) mentioned later and with less guidance. There are no Linux/macOS-specific setup examples or references to Linux tools for VM management, image customization, or cost control.
Recommendations
  • Provide Linux/macOS-specific examples for VM setup, image customization, and cost control.
  • Include detailed instructions for connecting to Linux VMs via SSH and configuring RDP/GUI environments.
  • Mention Linux-friendly storage solutions (e.g., mounting NFS shares, using Dropbox or other cross-platform tools) alongside OneDrive.
  • Ensure parity in automation features (e.g., auto-shutdown) for Linux VMs, or clarify any differences.
  • List Linux/macOS connection methods and tools before or alongside Windows options to avoid ordering bias.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (PsPing), Windows settings (client experience), and PowerShell for activity log filtering. There are no explicit Linux/macOS troubleshooting examples or tool recommendations, and Windows terminology appears first or exclusively in several sections.
Recommendations
  • Include Linux/macOS equivalents for troubleshooting tools (e.g., suggest 'ping', 'nmap', or 'iperf' instead of PsPing).
  • Provide SSH troubleshooting steps and examples alongside RDP, especially for Linux/macOS users.
  • Add instructions for checking connectivity and logs using Linux/macOS command-line tools.
  • When referencing PowerShell or Windows settings, also mention how to perform similar actions on Linux/macOS (e.g., Azure CLI, Bash scripts).
  • Ensure examples and tool recommendations are presented for both platforms, or in a platform-neutral way.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows 11 is the only VM image explicitly recommended for the tutorial, and all instructions for enabling ICMP (ping) on lab VMs use Windows PowerShell commands with no Linux equivalent. The process for connecting to VMs is described in terms of RDP, which is Windows-centric, and while SSH is mentioned as an alternative for Linux, no concrete Linux examples or commands are provided. The order of presentation and examples consistently favor Windows tools and workflows.
Recommendations
  • Provide explicit Linux examples for enabling ICMP (e.g., using ufw or iptables to allow ping).
  • Include instructions for connecting to Linux VMs via SSH, with sample commands and screenshots.
  • Mention Linux VM images as equally valid choices in the lab creation steps, and provide guidance for selecting and configuring them.
  • Where PowerShell commands are shown, offer equivalent bash or shell commands for Linux.
  • Ensure troubleshooting and next steps sections address common Linux/macOS scenarios.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows 11 Pro as the virtual machine image in the main example, and by only describing remote desktop (RDP) connection methods, which are most commonly associated with Windows environments. There are no examples or guidance for creating labs with Linux VM images, nor are there instructions for connecting to Linux VMs (e.g., via SSH), which may hinder Linux/macOS users or those wishing to use Linux-based labs.
Recommendations
  • Include examples for creating labs with Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Provide instructions for connecting to Linux VMs, such as using SSH, and mention cross-platform tools (e.g., VS Code Remote, Terminal, PuTTY, etc.).
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and link to documentation listing available images.
  • Present Windows and Linux options in parallel, rather than defaulting to Windows-first in examples and screenshots.
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-13 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 when creating a lab, without mentioning or providing examples for Linux-based images. No Linux or macOS-specific guidance, examples, or parity is offered in the lab creation steps, which may lead users to assume Windows is the only or preferred option.
Recommendations
  • Include Linux-based VM image options (e.g., Ubuntu, CentOS) in the 'Virtual machine image' selection step and provide examples.
  • Add notes or examples for connecting to Linux VMs (e.g., SSH instructions, default credentials).
  • Clarify that both Windows and Linux images are supported and link to documentation listing all available images.
  • Ensure screenshots and walkthroughs show both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Lab Services Create a lab plan using Python ...articles/lab-services/how-to-create-lab-plan-python.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (Azure PowerShell module and Az.LabServices cmdlets) in the 'Next steps' section, without mentioning equivalent Linux or cross-platform CLI options. The mention of PowerShell occurs before any reference to other tools, and there are no examples or guidance for Linux users or those preferring Azure CLI.
Recommendations
  • Add references and examples for Azure CLI commands for managing lab plans and labs, which are cross-platform and widely used on Linux.
  • Include a note or section highlighting Linux compatibility and any OS-specific considerations for the Python SDK usage.
  • Balance the 'Next steps' section by mentioning both PowerShell and Azure CLI, with links to relevant documentation for each.
  • Consider providing troubleshooting tips or environment setup instructions for Linux users, ensuring parity with Windows guidance.
GitHub Create Pull Request
← Previous Page 8 of 11 Next →