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 251-272 of 272 flagged pages
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-lab-users.md
.../main/articles/lab-services/how-to-manage-lab-users.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias by exclusively referencing Microsoft-centric tools and ecosystems (e.g., Microsoft Excel for CSV editing, Microsoft Entra, Teams, and Office 365) and by mentioning Microsoft tools before any alternatives. There are no explicit Linux or cross-platform command-line examples, and the workflow assumes use of Microsoft products. However, there are no PowerShell-specific instructions or CLI commands, and the process is largely web-based, which mitigates some potential bias.
Recommendations
- When mentioning CSV file creation, suggest cross-platform tools such as LibreOffice Calc, Google Sheets, or command-line utilities (e.g., awk, sed) alongside Microsoft Excel.
- Clarify that any text editor (including Linux-based editors like nano, vim, or gedit) can be used to create or edit CSV files.
- If possible, provide CLI or script-based examples for user management that work on both Windows and Linux (e.g., using Azure CLI or REST API).
- Explicitly state that the Azure Lab Services website and its features are accessible from any modern browser on any OS.
- Include references or links to documentation for Linux/macOS users where relevant, especially for tasks like CSV manipulation or email sending.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently refers to Windows-specific disk naming conventions (C: and D: drives) when describing OS and temporary disks, without mentioning Linux equivalents (such as / or /mnt). There are no Linux-specific examples or terminology, and no mention of Linux command-line tools or patterns. The only command-line automation examples provided are via PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling.
Recommendations
- Include Linux disk naming conventions (e.g., '/' for OS disk, '/mnt' or '/mnt/resource' for temporary disk) alongside Windows examples when discussing disk persistence.
- Provide Linux-specific or cross-platform examples for command-line automation, such as using Azure CLI or Bash scripts, in addition to PowerShell.
- Explicitly state that the instructions apply to both Windows and Linux VMs, and clarify any differences in behavior or terminology.
- Where screenshots or UI references use Windows-centric language, consider adding notes or alternative screenshots for Linux users if the experience differs.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup tasks. However, PowerShell examples are consistently presented alongside CLI, and references to PowerShell (a Windows-centric tool) are frequent. In the ARM template deployment section, the link to further deployment methods points first to PowerShell documentation. There are no Linux-specific shell examples (e.g., bash), nor is there explicit mention of Linux/macOS environments or considerations, though Azure CLI is cross-platform.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
- Add bash-specific examples or notes for Linux/macOS users where appropriate.
- When referencing deployment methods, avoid listing PowerShell first or exclusively; mention CLI and REST API equally.
- Clarify that PowerShell is primarily for Windows, and suggest alternatives for Linux/macOS users.
- Consider adding a section or note on platform compatibility for all tools mentioned.
Lab Services
Quickstart: Create lab plan resource
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page concludes with a 'Next step' link that specifically directs users to create a Windows-based lab, without mentioning Linux-based lab options or providing parity in guidance for non-Windows environments. The rest of the page is platform-neutral and focuses on Azure Portal usage.
Recommendations
- Add a parallel 'Next step' link for creating a Linux-based lab.
- Ensure that subsequent quickstarts and tutorials offer both Windows and Linux lab creation examples.
- Explicitly mention that Azure Lab Services supports both Windows and Linux environments, if applicable.
- Review linked content to verify Linux parity in examples and instructions.
Low Priority
View Details →
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 Bash or Azure CLI). The tip about scripting is Windows-centric, and PowerShell is mentioned before any cross-platform tools. However, most of the documentation is platform-neutral and focuses on Azure portal and service configuration.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for quota queries, or clarify that PowerShell Core is cross-platform.
- Explicitly mention that PowerShell scripts can be run on Linux/macOS using PowerShell Core, or link to cross-platform instructions.
- Include links or examples for Linux/macOS users where scripting or command-line tools are referenced.
- When mentioning scripts or tools, present cross-platform options together or note their compatibility.
Lab Services
Lab Services administrator guide
...blob/main/articles/lab-services/administrator-guide.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias in several areas. Windows-specific tools (SysPrep, PsGetSid, Microsoft Configuration Manager) are mentioned for endpoint management, and some VM sizes are labeled as '(Windows only)' for GPU visualization. There are no equivalent Linux/macOS endpoint management examples or tools discussed, and Windows is referenced first in several technical contexts. However, the guide does mention Linux images (Data Science VM for Linux) and does not prevent Linux users from completing core tasks.
Recommendations
- Add Linux/macOS endpoint management guidance, such as mentioning Linux configuration management tools (e.g., Ansible, Puppet, Chef) for VM preparation and SID/identity management.
- For GPU VM sizes, clarify Linux support and provide examples for Linux visualization workloads if available.
- When referencing tools like SysPrep and PsGetSid, mention Linux alternatives (e.g., cloud-init for image generalization, Linux commands for machine identity).
- Ensure examples and tool recommendations are presented for both Windows and Linux/macOS environments, or explicitly state platform limitations.
- Where '(Windows only)' is noted, provide context or alternatives for Linux users.
Lab Services
Create a lab plan using Python
...articles/lab-services/how-to-create-lab-plan-python.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform, focusing on Python and the Azure Python SDK, which work on Windows, Linux, and macOS. However, in the 'Next steps' section, it exclusively mentions Azure PowerShell and Az.LabServices cmdlets—Windows-centric tools—without referencing equivalent CLI or scripting options for Linux/macOS. Additionally, PowerShell is mentioned before any Linux-friendly alternatives, suggesting a subtle 'windows_first' bias.
Recommendations
- Add references to Azure CLI (az labservices) commands for managing lab plans and labs, which are cross-platform.
- Include links or examples for Bash scripting or Linux/macOS terminal usage where relevant.
- In the 'Next steps' section, mention both PowerShell and Azure CLI, presenting them as equal options for resource management.
- Clarify that the Python SDK examples work on all major platforms.
Lab Services
Manage labs in Azure Lab Services when using lab accounts| Microsoft Docs
.../articles/lab-services/how-to-manage-classroom-labs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents platform-neutral instructions focused on the Azure Lab Services web portal, which is accessible from any OS. However, there is a subtle Windows bias: the only command-line automation tool mentioned is the Az.LabServices PowerShell module, with no mention of Azure CLI or Bash alternatives. Additionally, password management defaults are described for 'Windows and Linux images except for Ubuntu,' implying Windows as the primary reference point.
Recommendations
- Mention and provide examples for managing labs using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Add Bash or shell script examples for common automation tasks, or clarify that the PowerShell module is available on Linux/macOS via PowerShell Core.
- Explicitly state platform parity for all management features, especially for command-line and scripting options.
- When describing password management defaults, present Linux/Ubuntu behavior first or equally with Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and are presented in parallel tabs throughout the page. There is a slight Windows-first bias in the mention of PowerShell, and the ARM template deployment section references PowerShell before CLI in the 'other deployment methods' link. However, Linux users can complete all tasks using Azure CLI, and no steps are Windows-exclusive.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- When referencing alternative deployment methods, list Azure CLI before PowerShell to avoid Windows-first perception.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is recommended for cross-platform use.
- Consider including Bash script examples for Linux users, where appropriate.
Lab Services
Create a lab plan using Python
...articles/lab-services/how-to-create-lab-plan-python.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform, focusing on Python and the Azure Python SDK, which work on Windows, Linux, and macOS. However, in the 'Next steps' section, it exclusively references Azure PowerShell and Az.LabServices cmdlets—Windows-centric tools—without mentioning Linux/macOS equivalents (such as Azure CLI). Additionally, PowerShell is mentioned before any cross-platform alternatives, suggesting a subtle 'windows_first' bias.
Recommendations
- Include references to Azure CLI commands for managing lab plans and resources, as Azure CLI is cross-platform.
- Add explicit notes or links for Linux/macOS users on how to perform equivalent tasks using Azure CLI or REST API.
- Reorder or balance the 'Next steps' section to mention cross-platform tools (Azure CLI) before or alongside PowerShell.
- Clarify that the Python SDK examples work on all major platforms.
Lab Services
Manage labs in Azure Lab Services when using lab accounts| Microsoft Docs
.../articles/lab-services/how-to-manage-classroom-labs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is mostly platform-neutral, focusing on the Azure Lab Services web portal, which is accessible from any OS. However, there is a subtle Windows bias: PowerShell (Az.LabServices) is mentioned as the only CLI automation option, with no reference to Linux/macOS alternatives (e.g., Azure CLI, Bash). Additionally, some credential management defaults are described in terms of Windows images first, with Linux (Ubuntu) as a special case.
Recommendations
- Mention and provide examples for managing labs using Azure CLI, which is cross-platform and works on Linux/macOS.
- Clarify that the Az.LabServices PowerShell module can be used on Linux/macOS via PowerShell Core, or suggest equivalent Bash/CLI workflows.
- When describing credential management, present Linux and Windows behaviors in parallel, rather than Windows-first.
- Add explicit notes or examples for Linux/macOS users where relevant, especially for remote desktop setup and VM access.
Lab Services
Quickstart: Create lab plan resource
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page concludes by directing users to a Windows-based lab quickstart as the next step, without mentioning Linux or macOS alternatives. No Linux/macOS-specific examples or parity are provided, and the only explicit next action is Windows-focused.
Recommendations
- Provide parallel quickstart links for Linux-based and macOS-based labs alongside the Windows-based lab.
- Explicitly mention that Azure Lab Services supports non-Windows environments, if applicable.
- Include examples or guidance for creating labs using Linux or macOS images.
- Ensure that next steps are inclusive of all major platforms, not just Windows.
Low Priority
View Details →
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 directly to a PowerShell resource, which may not be directly usable by Linux/macOS users. No explicit Linux/macOS examples or parity are provided in this troubleshooting context.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for quota queries, and link to cross-platform resources.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify platform compatibility for the script.
- When suggesting scripts or tools, offer both Windows and Linux/macOS options, or note any platform-specific requirements.
- Add troubleshooting tips or examples relevant to Linux/macOS environments where applicable.
Lab Services
Quickstart: Create lab plan resource
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by prominently featuring a link to 'Quickstart: Create a Windows-based lab' as the next step, without mentioning Linux-based lab creation or providing parity for Linux examples. There are no Linux-specific instructions, examples, or references, and the only operating system explicitly mentioned is Windows.
Recommendations
- Add equivalent quickstart links and instructions for creating Linux-based labs.
- Ensure that examples and next steps reference both Windows and Linux options, or provide a neutral choice.
- Include information about available VM images for both Windows and Linux in lab plans.
- Review included content (such as role assignment and resource cleanup) to ensure platform neutrality or Linux parity.
Lab Services
Quickstart: Create lab plan resource
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by directing users to a Windows-based lab quickstart as the next step, without mentioning or offering Linux-based lab alternatives. There are no examples, instructions, or references to Linux tools or workflows, and the only explicit next action is Windows-centric.
Recommendations
- Include links to both Windows-based and Linux-based lab quickstarts in the 'Next step' section.
- Provide examples or instructions for creating labs using Linux VM images, alongside Windows examples.
- Mention Linux-compatible tools and workflows where relevant, ensuring parity with Windows references.
- Ensure that any referenced tutorials or guides cover both Windows and Linux scenarios, or clearly indicate platform applicability.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/quick-create-resources.md
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by directing users to a Windows-based lab quickstart as the next step, without mentioning Linux-based lab options or providing parity in examples. There are no Linux-specific instructions, examples, or references, and the only explicit next action is focused on Windows.
Recommendations
- Include links to both Windows-based and Linux-based lab quickstarts in the 'Next step' section.
- Add examples or instructions for creating Linux-based labs alongside Windows-based labs.
- Ensure that references to operating systems are balanced and do not prioritize Windows unless contextually necessary.
- Review included files (e.g., 'Create a lab plan', 'Add Lab Creator role') to ensure they do not contain Windows-specific instructions or examples exclusively.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/quick-create-resources.md
...b/main/articles/lab-services/quick-create-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by exclusively referencing the creation of a Windows-based lab in the 'Next step' section, without mentioning Linux-based lab creation or providing parity in examples or guidance for Linux environments.
Recommendations
- Include links or examples for creating Linux-based labs alongside Windows-based labs in the 'Next step' section.
- Ensure that instructions and screenshots throughout the documentation reference both Windows and Linux options where applicable.
- Add a note or section clarifying support for Linux-based labs and provide guidance for users interested in non-Windows environments.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-bring-custom-linux-image-azure-vm.md
...b-services/how-to-bring-custom-linux-image-azure-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page, while focused on Linux custom images, presents Windows-centric links and ordering in the VM creation step. Specifically, links for creating VMs via the Azure portal, PowerShell, CLI, and ARM templates all point to Windows-specific documentation before mentioning Linux equivalents, which may confuse or deprioritize Linux users.
Recommendations
- Update the VM creation step to link to Linux-specific documentation (e.g., /azure/virtual-machines/linux/quick-create-portal) or provide both Windows and Linux links side by side.
- Ensure that examples and references throughout the document use Linux-centric tools and commands where appropriate, especially since the article is about Linux custom images.
- Review all linked resources to ensure Linux users are not redirected to Windows-specific instructions.
- Consider adding explicit Linux command-line examples (e.g., Azure CLI commands for Linux) where steps are described generically.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-configure-lab-accounts.md
...articles/lab-services/how-to-configure-lab-accounts.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation mentions differences in Linux support for automatic shutdown features but does not provide any Linux-specific examples, instructions, or screenshots. All instructions are generic or implicitly assume the Azure Portal UI, which may not reflect Linux-specific considerations or limitations.
Recommendations
- Add explicit Linux-specific instructions or notes where behavior differs, including screenshots if the UI is different for Linux VMs.
- Provide a table or section summarizing feature support across Windows and various Linux distributions.
- Include troubleshooting tips or links for Linux users, especially regarding supported distributions and known limitations.
- Clarify in each step if any actions or settings are unavailable or behave differently for Linux VMs.
- Reference Linux command-line tools or scripts if applicable, or explain why such options are not available.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-connect-lab-virtual-machine.md
...s/lab-services/tutorial-connect-lab-virtual-machine.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents connection instructions for Windows virtual machines (via RDP) before Linux virtual machines (via SSH or RDP), indicating a 'windows_first' bias. However, both operating systems are mentioned, and Linux connection methods are included. There are no exclusive use of Windows tools, missing Linux examples, or PowerShell-heavy instructions.
Recommendations
- Present connection instructions for Windows and Linux VMs in parallel or alternate the order in which they are described.
- Provide explicit examples or screenshots for both Windows (RDP) and Linux (SSH/RDP) connection processes to ensure parity.
- Avoid always listing Windows instructions first; consider starting with Linux or using a tabbed or side-by-side format.
- If possible, include command-line examples for both platforms (e.g., SSH command for Linux/macOS, RDP client usage for Windows).
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/tutorial-connect-lab-virtual-machine.md
...s/lab-services/tutorial-connect-lab-virtual-machine.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents connection instructions for Windows virtual machines (using RDP) before Linux virtual machines (using SSH or RDP). While both platforms are mentioned, the ordering and phrasing prioritize Windows, which may subtly reinforce a Windows-centric perspective.
Recommendations
- Present Linux and Windows connection instructions in parallel or alternate the order in which they are described to avoid always listing Windows first.
- Provide explicit command-line examples for both SSH (Linux) and RDP (Windows) connections, ensuring parity in detail and clarity.
- Where possible, use neutral language such as 'For Linux or Windows virtual machines...' instead of always leading with Windows.
- Consider including screenshots or step-by-step instructions for both SSH (Linux) and RDP (Windows) workflows to ensure equal visibility.
Lab Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-configure-lab-accounts.md
...articles/lab-services/how-to-configure-lab-accounts.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation primarily describes the auto-shutdown feature in general terms and highlights some limitations for Linux labs, but does not provide any Linux-specific configuration examples or guidance. The only mention of Linux is in the context of feature limitations, with no equivalent positive or step-by-step Linux instructions.
Recommendations
- Include explicit Linux examples or screenshots where applicable, especially if the configuration steps or UI differ for Linux-based labs.
- Provide a table or section summarizing feature support and limitations for both Windows and Linux, including supported distributions and versions.
- Offer troubleshooting tips or alternative approaches for Linux users, particularly for unsupported distributions like Data Science Virtual Machine - Ubuntu.
- Ensure that any limitations for Linux are balanced with actionable guidance, not just caveats.