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 201-225 of 272 flagged pages
Lab Services Create and manage lab plans .../main/articles/lab-services/how-to-manage-lab-plans.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing lab plans through the Azure portal web interface, which is 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-native tools or workflows. This can be considered a 'windows_first' bias, as the portal experience is often associated with Windows users, and there is a 'missing_linux_example' bias due to the absence of Linux/CLI instructions.
Recommendations
  • Add instructions for managing lab plans using Azure CLI, which is cross-platform and works natively on Linux and macOS.
  • Include examples for common tasks (create, view, delete lab plans) using Bash scripts or Azure CLI commands.
  • Mention that the Azure portal is accessible from any modern browser on Linux, macOS, or Windows, to clarify platform neutrality.
  • If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented with equal prominence.
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 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referring to the OS disk as 'usually the C: drive on Windows' and the temporary disk as 'usually the D: drive on Windows', without mentioning Linux equivalents (such as /dev/sda1 or /mnt). No Linux-specific terminology or examples are provided, and all references to disk locations are Windows-centric. Additionally, command-line examples for redeploying or reimaging VMs mention PowerShell, but do not mention Linux CLI tools or Azure CLI usage.
Recommendations
  • Include Linux-specific terminology when referring to disk locations (e.g., '/dev/sda1' for OS disk, '/mnt' for temporary disk).
  • Provide examples for redeploying and reimaging VMs using Azure CLI, which is cross-platform and commonly used on Linux.
  • Mention that the instructions apply to both Windows and Linux VMs, and clarify any differences in disk naming or behavior.
  • Add screenshots or descriptions that show the experience for Linux VM users, if applicable.
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 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 lab creation, without mentioning or providing Linux-based alternatives. There are no examples, screenshots, or instructions for selecting or configuring Linux VM images, nor any references to Linux-specific access patterns (e.g., SSH, Linux credentials). This may lead users to believe that Windows is the default or only supported option, even though Azure Lab Services supports Linux images.
Recommendations
  • Include examples and screenshots that use Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Explicitly mention that both Windows and Linux images are supported, and provide guidance on choosing between them.
  • Show how to configure Linux-specific settings, such as SSH key authentication and default usernames.
  • Add troubleshooting tips relevant to Linux VMs (e.g., SSH connection issues, Linux user management).
  • Ensure parity in instructions for both Windows and Linux environments, so users on either platform feel equally supported.
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 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 (RDP), which is primarily associated with Windows environments. There are no examples or mentions of Linux VM images, nor instructions for connecting to or configuring Linux-based lab environments. All steps and screenshots assume a Windows-centric workflow.
Recommendations
  • Include examples that use Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples when describing lab creation.
  • Provide instructions and screenshots for connecting to Linux VMs (e.g., using SSH) in addition to RDP for Windows.
  • Mention software installation and configuration steps relevant to Linux environments (e.g., installing packages via apt/yum, setting up development tools).
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and link to documentation on supported OS images.
  • Ensure parity in troubleshooting and user invitation steps for Linux-based labs.
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 00:00
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 warnings for Windows (e.g., RDP session and a link to Windows shutdown behavior). There is a lack of Linux-specific configuration examples, troubleshooting, or references to Linux remote connection patterns (such as SSH). The warning section and troubleshooting links focus on Windows, with Linux only mentioned in passing.
Recommendations
  • Add Linux-specific examples for configuring and troubleshooting automatic shutdown, including common remote connection patterns (e.g., SSH, X11 forwarding).
  • Provide links to Linux shutdown behavior documentation, similar to the Windows guide.
  • Include troubleshooting steps or warnings specific to popular Linux distributions.
  • Ensure that Linux tools and patterns are mentioned with equal prominence to Windows tools (e.g., not just RDP, but also SSH).
  • Add screenshots or walkthroughs for Linux VM settings where relevant.
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-10 00:00
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 references for Windows (e.g., a specific link to controlling Windows shutdown behavior). There are no equivalent Linux-specific troubleshooting or configuration examples, and the warning section prioritizes Windows shutdown guidance over Linux. Linux support is described in general terms, with no concrete configuration steps or examples for Linux distributions.
Recommendations
  • Add Linux-specific troubleshooting and shutdown behavior guidance, similar to the Windows shutdown guide.
  • Provide concrete configuration examples for popular Linux distributions (e.g., Ubuntu, CentOS) showing how to enable/verify auto-shutdown.
  • Include links to Linux documentation or resources for managing shutdown events and remote session disconnects.
  • Ensure that Linux tools and patterns are mentioned alongside Windows equivalents, not just in general terms.
  • Add screenshots or step-by-step instructions for configuring auto-shutdown on Linux VMs.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a slight Windows bias by referencing Windows-specific tools (Azure PowerShell module and Az.LabServices cmdlets) in the 'Next steps' section, without mentioning equivalent Linux tools (such as Azure CLI). The documentation does not provide PowerShell-heavy examples, but it does mention Windows tooling before Linux alternatives and omits explicit Linux command-line guidance.
Recommendations
  • Add references to cross-platform tools such as Azure CLI in the 'Next steps' section, alongside Azure PowerShell.
  • Include examples or links for managing lab plans using Azure CLI, which works on both Linux and Windows.
  • Clarify that the Python SDK examples are platform-agnostic and can be run on Linux, macOS, or Windows.
  • Where possible, provide parity in tool recommendations, mentioning both PowerShell and CLI options for resource management.
GitHub Create Pull Request
Lab Services Create and manage lab plans .../main/articles/lab-services/how-to-manage-lab-plans.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing lab plans via the Azure portal, which is a GUI-based workflow most commonly used on Windows systems. There are no CLI, PowerShell, or Bash examples, nor any mention of Linux-native tools or workflows. This approach implicitly favors Windows users and omits guidance for Linux users who may prefer command-line or automation-friendly methods.
Recommendations
  • Add Azure CLI examples for creating, viewing, and deleting lab plans, ensuring commands work on both Windows and Linux.
  • Include PowerShell examples for parity, but present CLI and Bash options before or alongside PowerShell to avoid Windows-first bias.
  • Mention cross-platform management options (e.g., Azure CLI, REST API) and link to relevant documentation.
  • Clarify that the Azure portal is accessible from any OS, but provide explicit instructions for command-line workflows to support Linux users.
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-10 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 referring to OS and temporary disks using Windows drive letters (C: and D:) exclusively, with no mention of Linux equivalents (such as / or /mnt). There are no Linux-specific examples or references, and all tooling references (PowerShell, .NET SDK, REST API) are platform-neutral or Windows-centric, with PowerShell mentioned but no Linux CLI or shell alternatives provided.
Recommendations
  • Explicitly mention Linux disk paths (e.g., '/' for OS disk, '/mnt' or '/tmp' for temporary disk) alongside Windows drive letters.
  • Provide Linux-specific examples or notes where relevant, such as using Azure CLI or Bash scripts for redeploy/reimage operations.
  • Clarify that the instructions apply to both Windows and Linux VMs, and highlight any differences in behavior or terminology.
  • Include screenshots or references to Linux VM environments where appropriate.
  • List cross-platform tools (e.g., Azure CLI) before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Lab Services Transition from Azure Lab Services to Azure DevTest Labs ...icles/lab-services/transition-devtest-labs-guidance.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is generally neutral in its description of Azure DevTest Labs features, and it explicitly mentions Linux VM support as a differentiator. However, the transition steps and FAQs lack concrete Linux-specific examples or guidance, and most instructions (such as VM creation, image management, and access) are presented generically or with an implicit Windows-first approach. The only Linux-specific mention is a single note about SSH access, which is relegated to an 'Important' callout at the end of the transition steps, rather than integrated into the main workflow or examples.
Recommendations
  • Provide explicit step-by-step examples for both Windows and Linux VM creation, configuration, and access, including screenshots or command-line instructions where appropriate.
  • Include Linux-specific tooling and access patterns (e.g., SSH, cloud-init, Linux Marketplace images) alongside Windows equivalents in all relevant sections.
  • Mention Linux VM management tasks (such as package installation, remote desktop alternatives, and troubleshooting) in the transition steps and FAQs.
  • Ensure that Linux access instructions (such as SSH setup, firewall rules, and key management) are integrated into the main workflow, not just as a side note.
  • Highlight any differences or considerations for Linux users (e.g., image compatibility, automation, cost tracking) in the FAQ and scenario guidance sections.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates 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 VM images, nor are there instructions or screenshots showing how to select or configure a Linux-based lab environment. The documentation does not provide parity for Linux users or educators who may wish to create labs with Linux VMs.
Recommendations
  • Include examples that use popular Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples in the lab creation steps.
  • Add a table or section listing both Windows and Linux VM image options, with guidance on when to use each.
  • Provide screenshots and walkthroughs for creating labs with Linux VM images, including any differences in credential setup (e.g., SSH keys for Linux).
  • Mention Linux-specific configuration options, such as enabling SSH access and setting up initial user accounts.
  • Ensure troubleshooting and next steps sections reference Linux VM scenarios where relevant.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 in the main example, with no mention of Linux images or Linux-specific configuration steps. All instructions and screenshots assume a Windows environment, and remote desktop (RDP) is referenced as the sole connection method, which is most commonly used for Windows VMs. There are no examples or guidance for creating labs with Linux images, nor any mention of SSH or Linux-specific tools.
Recommendations
  • Include examples and screenshots for creating labs using popular Linux images (e.g., Ubuntu, CentOS) in addition to Windows.
  • Provide instructions for connecting to Linux VMs using SSH, alongside RDP for Windows.
  • Mention Linux-compatible software installation and configuration steps in the 'Customize the lab template' section.
  • Clarify that Azure Lab Services supports both Windows and Linux VM images, and provide guidance for choosing between them based on training needs.
  • Ensure parity in troubleshooting and user invitation steps for Linux-based labs.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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 lab creation, with no mention or example of Linux-based VM images. The instructions and screenshots focus on Windows environments, and there are no Linux-specific steps, recommendations, or parity in examples. This may lead users to assume that Windows is the default or preferred platform for Azure Lab Services labs, despite Linux images being available in Azure.
Recommendations
  • Include Linux-based VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples when describing lab creation.
  • Explicitly mention that both Windows and Linux images are supported, and provide guidance on selecting and configuring Linux images.
  • Add screenshots and walkthroughs for creating labs with Linux VM images to ensure parity.
  • Highlight any differences in credential setup, access methods (e.g., SSH for Linux), and troubleshooting for Linux labs.
  • Ensure that documentation language does not imply Windows is the default or only supported platform.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/transition-devtest-labs-guidance.md ...icles/lab-services/transition-devtest-labs-guidance.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes Azure DevTest Labs transition steps and features in a platform-neutral way, but it exhibits subtle Windows bias. Most examples and instructions are generic or Azure portal-based, but explicit Linux guidance is only provided in a single 'Important' note at the end, and there are no step-by-step Linux-specific examples (e.g., SSH connection, Linux VM setup, or Linux tooling). Windows patterns (Azure portal, Bastion, RBAC) are described first or exclusively, while Linux access is mentioned as an exception rather than integrated throughout.
Recommendations
  • Provide parallel, step-by-step examples for connecting to both Windows and Linux VMs (e.g., RDP for Windows, SSH for Linux) in the main transition steps, not just in a side note.
  • Include references to Linux-specific tools and workflows (such as using cloud-init, Linux image customization, or command-line Azure CLI examples for Linux VM management).
  • Mention Linux access methods (SSH, SCP, SFTP) alongside Windows methods (RDP, Bastion) wherever VM access is discussed.
  • Add troubleshooting tips and best practices for Linux VM users (e.g., SSH key management, firewall configuration, package installation).
  • Ensure that any referenced features (such as Shared Image Gallery, cost management, dashboard creation) include Linux-centric use cases and examples.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows 11 Pro as the example VM image and only referencing remote desktop (RDP) for VM access, which is primarily a Windows protocol. There are no examples or mentions of Linux VM images, Linux-specific configuration steps, or alternative connection methods such as SSH. All customization and software installation instructions implicitly assume a Windows environment.
Recommendations
  • Provide examples using Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Include instructions for connecting to Linux VMs, such as using SSH, in addition to RDP for Windows.
  • Mention Linux-compatible software installation and configuration steps.
  • Clarify that Azure Lab Services supports both Windows and Linux VMs, and link to relevant documentation for Linux users.
  • Ensure screenshots and field values alternate between Windows and Linux scenarios, or provide parallel walkthroughs.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools (Azure PowerShell module, Az.LabServices cmdlets) in the 'Next steps' section, without mentioning equivalent Linux or cross-platform CLI alternatives. The connection profile in the lab plan example prioritizes RDP (a Windows protocol) and disables SSH (commonly used on Linux), which may suggest a Windows-centric approach to remote access.
Recommendations
  • Include references to Azure CLI commands and documentation, which are cross-platform and widely used on Linux and macOS.
  • Mention Linux-friendly remote access protocols (such as enabling SSH in the lab plan example) alongside or before RDP.
  • Provide examples or links for managing lab plans using Bash or other Linux-native tools.
  • Clarify that the Python SDK and code samples are cross-platform and can be run on Linux, macOS, and Windows.
  • Balance the 'Next steps' section by listing both PowerShell and CLI options for further management.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing lab plans via the Azure portal, which is a web-based GUI. There are no examples or references to command-line tools, scripts, or automation methods, such as Azure CLI, PowerShell, or Bash. While the portal is cross-platform in theory, the documentation's screenshots and instructions implicitly favor Windows users, as the Azure portal is most commonly accessed from Windows environments. There is no mention of Linux-specific workflows or parity in automation, nor are there examples using Linux-friendly tools.
Recommendations
  • Add examples for managing lab plans using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples if relevant, but ensure Azure CLI or REST API examples are presented first or alongside.
  • Mention that the Azure portal can be accessed from any OS/browser, and clarify that all instructions are OS-agnostic.
  • Provide links to automation guides for both Windows and Linux users.
  • Add a section on scripting lab plan management for advanced users, with sample commands for both Bash (Azure CLI) and PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is intended for Linux custom images, but in the 'Prepare a custom image on an Azure VM' section, links and instructions for creating an Azure VM reference Windows resources first (portal, PowerShell, CLI, ARM template), and all example links point to Windows-specific documentation. There are no direct links or examples for creating a Linux VM, nor are Linux-specific tools or commands (other than a brief mention of '-deprovision+user') provided for the initial VM creation step.
Recommendations
  • Update the VM creation step to reference Linux-specific documentation and examples, such as linking to '/azure/virtual-machines/linux/quick-create-portal', '/azure/virtual-machines/linux/quick-create-cli', and '/azure/virtual-machines/linux/quick-create-template'.
  • Provide explicit Linux VM creation examples using Azure CLI, portal, and ARM templates.
  • Ensure that Linux-specific tools and commands are mentioned where relevant, and avoid referencing Windows documentation or tools unless necessary for cross-platform parity.
  • Review all steps to ensure Linux workflows are described in detail and with parity to any Windows instructions.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-enable-shutdown-disconnect.md ...cles/lab-services/how-to-enable-shutdown-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 specific guide for controlling Windows shutdown behavior) while Linux coverage is limited to listing supported distributions. There are no Linux-specific configuration examples, troubleshooting steps, or equivalent guides for Linux shutdown behavior.
Recommendations
  • Add a Linux-specific guide or troubleshooting section similar to the Windows shutdown behavior guide.
  • Provide configuration examples or screenshots for Linux VMs, including common distributions.
  • Include links to relevant Linux documentation for managing shutdown and remote session disconnects.
  • Ensure parity in troubleshooting advice for both Windows and Linux users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by referring to OS and temporary disks using Windows drive letters (C: and D:) and does not mention Linux equivalents (such as / or /mnt). There are no Linux-specific examples or references to Linux tools or patterns. All command-line automation examples reference PowerShell, with no mention of Bash, CLI, or Linux-native approaches.
Recommendations
  • Include references to Linux disk paths (e.g., '/' for OS disk, '/mnt' or '/tmp' for temporary disk) alongside Windows drive letters.
  • Provide Linux/Bash command-line examples for redeploying and reimaging VMs, such as using Azure CLI.
  • Mention Linux-specific considerations for data persistence and VM troubleshooting.
  • Ensure screenshots and instructions are platform-neutral or include both Windows and Linux perspectives where relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a slight Windows bias by referencing Azure PowerShell and Az.LabServices cmdlets as next steps for admins, without mentioning Linux equivalents such as Azure CLI. The connection profile in the lab plan defaults to enabling RDP (a Windows protocol) and disables SSH (commonly used on Linux), suggesting a Windows-centric setup. No explicit Linux or cross-platform command-line tools are referenced.
Recommendations
  • Include Azure CLI examples alongside PowerShell references, highlighting cross-platform compatibility.
  • Mention SSH access and Linux-friendly connection profiles in lab plan examples, or provide guidance for enabling SSH.
  • Add notes or links for Linux users on how to perform equivalent tasks using Bash or other Linux-native tools.
  • Ensure next steps section references both PowerShell and CLI documentation, making it clear that both are supported.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
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 links for creating a VM via the Azure portal, PowerShell, Azure CLI, and ARM template all point to Windows documentation, with no Linux equivalents provided or referenced. This may confuse users seeking Linux-specific instructions and creates a perception of Windows preference.
Recommendations
  • Update the VM creation step to reference Linux-specific documentation for the Azure portal, PowerShell, Azure CLI, and ARM templates (e.g., /azure/virtual-machines/linux/quick-create-portal).
  • Ensure that examples and links for Linux are presented before or alongside Windows equivalents, especially in Linux-focused documentation.
  • Add explicit Linux command-line examples (e.g., Azure CLI commands for Linux VM creation) to improve clarity and parity.
  • Review all linked resources to confirm they are relevant to Linux workflows, and avoid defaulting to Windows documentation unless the topic is Windows-specific.
GitHub Create Pull Request
Lab Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-enable-shutdown-disconnect.md ...cles/lab-services/how-to-enable-shutdown-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 dedicated guide for controlling Windows shutdown behavior) while lacking equivalent Linux-specific troubleshooting or configuration examples. There are warnings and references that focus on Windows shutdown patterns, but no Linux-specific examples or guides for shutdown behavior or troubleshooting.
Recommendations
  • Add Linux-specific troubleshooting and configuration guidance for automatic shutdown, similar to the Windows shutdown behavior guide.
  • Provide explicit examples or screenshots for configuring auto-shutdown on Linux VMs, including common distributions.
  • Include links to Linux documentation for shutdown behavior and remote session management.
  • Ensure warnings and notes address Linux-specific scenarios and edge cases, not just Windows.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing lab plans via the Azure portal, which is a web-based GUI. There are no command-line examples provided, such as Azure CLI or PowerShell, but the workflow and screenshots reflect a Windows-centric user experience (e.g., portal screenshots, terminology). There is no mention of Linux tools, CLI commands, or cross-platform automation options, which may disadvantage Linux users or those preferring non-GUI workflows.
Recommendations
  • Add Azure CLI examples for creating, viewing, and deleting lab plans, as the CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented with equal prominence.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, and clarify that all steps are OS-agnostic.
  • Include links or references to automation guides for Linux users, such as scripting with Bash and Azure CLI.
  • Provide screenshots or instructions that are not visually or terminologically biased toward Windows (e.g., avoid Windows-specific UI elements or language).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by consistently referencing Windows-specific drive letters (C: and D:) when discussing OS and temporary disks, without mentioning Linux equivalents (such as / or /mnt). There are no Linux-specific examples, terminology, or screenshots, and the only command-line tooling referenced is PowerShell, with no mention of Bash, CLI, or Linux-native tools.
Recommendations
  • Include Linux terminology when describing disk locations (e.g., mention '/' for OS disk and '/mnt' or '/tmp' for temporary disk).
  • Provide Linux-specific examples or notes alongside Windows references, especially when discussing disk data retention.
  • Add references to Linux command-line tools or Azure CLI commands for redeploying and reimaging VMs, not just PowerShell.
  • Ensure screenshots and instructions are platform-neutral or include both Windows and Linux variants where applicable.
GitHub Create Pull Request
← Previous Page 9 of 11 Next →