Devtest Labs
99
Total Pages
40
Linux-Friendly Pages
59
Pages with Bias
59.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
334 issues found
Showing 201-225 of 334 flagged pages
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-save-distribute-custom-images.md
...st-labs/image-factory-save-distribute-custom-images.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All scripting and automation examples use Azure PowerShell, with no mention of Bash, Azure CLI, or Linux scripting alternatives. The sample configuration references only Windows images (e.g., Win2012R2, Win2016), and there are no examples or guidance for Linux VM image creation or distribution. The documentation assumes familiarity with Windows-centric tools and workflows, omitting Linux equivalents.
Recommendations
- Provide parallel examples using Azure CLI and Bash scripts for saving and distributing images, alongside PowerShell.
- Include Linux VM image examples in the labs.json configuration and discuss any differences in generalizing Linux VMs (e.g., using waagent for deprovisioning).
- Mention and illustrate how to add Azure CLI tasks in Azure DevOps build definitions, not just Azure PowerShell.
- Balance the documentation by referencing both Windows and Linux workflows, tools, and image types throughout.
- Add a section or callout for Linux users, highlighting any special considerations or steps.
Create Pull Request
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-set-retention-policy-cleanup.md
...est-labs/image-factory-set-retention-policy-cleanup.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell tasks and scripts for all automation and cleanup steps, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All screenshots and instructions are PowerShell-centric, and there are no Linux or macOS examples or guidance. This creates a strong Windows bias and may alienate users who prefer or require Linux-based automation.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for all automation steps, alongside the PowerShell examples.
- Include screenshots and instructions for adding Bash or Azure CLI tasks in Azure DevOps build definitions.
- Explicitly mention that the process can be performed on Linux/macOS agents using cross-platform tools.
- Add a section comparing PowerShell and CLI approaches, helping users choose the best fit for their environment.
- Ensure terminology and instructions are inclusive of both Windows and Linux users (e.g., avoid assuming PowerShell is the only or default scripting environment).
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-set-up-devops-lab.md
...ticles/devtest-labs/image-factory-set-up-devops-lab.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on using Azure PowerShell scripts and Windows-centric tools and patterns (such as Windows Task Scheduler), with no mention or examples of Linux equivalents (e.g., Bash, Azure CLI, cron). All scripting and automation steps assume PowerShell usage, and there are no instructions or guidance for users on Linux or macOS platforms.
Recommendations
- Include parallel examples using Azure CLI and Bash scripts for Linux/macOS users.
- Mention and provide instructions for using Linux-native automation tools such as cron or systemd timers alongside Windows Task Scheduler.
- Clarify that the image factory scripts can be adapted for non-Windows environments, and provide guidance or references for doing so.
- Add notes or sections on how to run the image factory from Linux-based Azure DevOps agents or self-hosted runners.
- Ensure all screenshots and UI instructions are platform-neutral or provide alternatives for Linux/macOS users where applicable.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/import-virtual-machines-from-another-lab.md
...vtest-labs/import-virtual-machines-from-another-lab.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell instructions and scripts for importing VMs, with no equivalent examples or scripts for Linux users (e.g., Bash, Azure CLI). PowerShell is a Windows-centric tool, and its exclusive use may hinder Linux users. The REST API section is platform-neutral, but the only scripted example is for PowerShell, and there is no mention of Linux command-line tools or workflows.
Recommendations
- Add equivalent instructions and sample scripts using Azure CLI (az) for Linux/macOS users.
- Provide Bash shell examples for invoking the REST API (e.g., using curl or httpie).
- Mention that PowerShell Core is cross-platform, but clarify if the provided script works on Linux/macOS or only on Windows PowerShell.
- Include a table or section comparing Windows and Linux approaches to importing VMs.
- Ensure that any downloadable scripts are compatible with both Windows and Linux environments, or provide separate versions if necessary.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/network-isolation.md
...s/blob/main/articles/devtest-labs/network-isolation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing a PowerShell script as the only method for converting an existing lab to network isolation mode, without providing equivalent Bash, Azure CLI, or Linux-native instructions. While Azure CLI is briefly mentioned as an automation option, no concrete CLI or Linux shell examples are provided. The exclusive use of PowerShell and lack of Linux-specific guidance or parity in scripting options may disadvantage users on non-Windows platforms.
Recommendations
- Provide Azure CLI and/or Bash script equivalents for the PowerShell script (Convert-DtlLabToIsolatedNetwork.ps1) used to convert existing labs to network isolation.
- Include example commands for both PowerShell and Azure CLI (or Bash) wherever automation is discussed, ensuring parity for Linux and macOS users.
- Explicitly mention cross-platform tooling (e.g., Azure CLI, REST API) as first-class options alongside PowerShell.
- Add a section or callout for Linux/macOS users, clarifying how to perform all steps without requiring Windows or PowerShell.
- Review all automation and scripting references to ensure they are not Windows-centric and provide equal support for Linux environments.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/personal-data-delete-export.md
...n/articles/devtest-labs/personal-data-delete-export.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only Azure PowerShell examples for exporting personal data, with no mention of Linux-compatible tools or cross-platform alternatives such as Azure CLI, Bash, or REST API. The instructions and code samples are tailored exclusively to Windows/PowerShell users, implicitly prioritizing Windows tooling and omitting guidance for Linux or macOS environments.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash shell script examples for common operations, or reference how to perform the same actions in a Linux terminal.
- Mention REST API options for exporting data, with sample curl commands.
- Clearly state that the export functionality is not limited to PowerShell/Windows and provide links or references to official Azure CLI and REST API documentation.
- Reorganize the section to present cross-platform or Linux-friendly options before or alongside PowerShell examples, ensuring parity and inclusivity.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/report-usage-across-multiple-labs-subscriptions.md
...abs/report-usage-across-multiple-labs-subscriptions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing PowerShell and Windows-centric tools and workflows. PowerShell is the only command-line example provided, and there are no Linux shell (bash/CLI) examples or explicit mentions of Linux tools. Windows tools like Power BI and SQL Server are mentioned before cross-platform or Linux-native alternatives. The documentation does not address Linux users or provide parity in instructions or tooling.
Recommendations
- Provide equivalent bash/CLI examples for exporting resource usage, using Azure CLI or REST API with curl.
- Explicitly mention that Azure Functions and Automation can be implemented in Python or other cross-platform languages, and provide sample code or links.
- Include Linux-friendly storage and visualization options, such as PostgreSQL, Grafana, or open-source BI tools, alongside Power BI and SQL Server.
- Ensure that instructions and examples are platform-agnostic or provide both Windows and Linux workflows side by side.
- Clarify that PowerShell Core is cross-platform if recommending it, and provide installation guidance for Linux users.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/resource-group-control.md
...b/main/articles/devtest-labs/resource-group-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides a detailed PowerShell script example for specifying a resource group for Azure DevTest Labs VMs, but does not include equivalent examples for Linux shells (such as Bash). The scripting section is labeled 'Use PowerShell' and only demonstrates usage with PowerShell, which is primarily associated with Windows environments. There is no mention of Bash, Azure CLI in Bash, or cross-platform scripting approaches. The ordering also places the PowerShell example before the ARM template and API sections, reinforcing a Windows-first approach.
Recommendations
- Add an equivalent Azure CLI example using Bash syntax to demonstrate how Linux or cross-platform users can accomplish the same task.
- Include explicit mention that the Azure CLI commands can be run in any shell (Bash, zsh, etc.), not just PowerShell.
- Reorganize the scripting examples to present cross-platform (Bash/Azure CLI) and PowerShell examples side by side, or clarify that both are supported.
- Where possible, use neutral Azure CLI commands in documentation, as they are cross-platform and widely used.
- Add a note or section for Linux/macOS users to ensure parity and inclusivity.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/test-app-azure.md
...docs/blob/main/articles/devtest-labs/test-app-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows environments. It assumes the use of Visual Studio (a primarily Windows tool), requires a Windows-based DevTest Labs VM, and only provides instructions for connecting via RDP and using File Explorer to access the Azure file share. There are no examples or guidance for Linux-based VMs, nor are alternative tools or workflows (such as VS Code, SCP, or SMB mounting on Linux) mentioned.
Recommendations
- Include instructions for publishing and accessing apps from Linux-based DevTest Labs VMs, such as mounting Azure file shares using SMB on Linux.
- Provide alternative examples using cross-platform tools (e.g., Visual Studio Code, dotnet CLI) for publishing applications.
- Add guidance for connecting to Linux VMs (e.g., using SSH) and accessing the file share via the Linux file system.
- Mention and link to documentation for mounting Azure file shares on Linux and macOS.
- Clarify in the prerequisites and throughout the article that the instructions are Windows-specific, and provide parity for other platforms where possible.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md
...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary scripting tool for ARM template deployments, without mentioning Azure CLI or Bash alternatives. No Linux-specific examples or tools are provided, and the only automation example is Windows-centric. This may make Linux users feel unsupported or require them to translate instructions themselves.
Recommendations
- Include equivalent Azure CLI (az) or Bash examples alongside PowerShell for ARM template deployments.
- Mention both Windows and Linux automation tools when discussing deployment scripting.
- Explicitly state that instructions apply to both Windows and Linux environments, or provide OS-specific guidance where relevant.
- Add troubleshooting steps or references for common Linux shell environments.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md
...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation shows a moderate Windows bias: PowerShell (a Windows-centric tool) is presented first in all sections, and its usage is described in greater detail. In the Azure CLI section, both Bash (Linux) and Windows command syntaxes are provided, but Windows batch syntax is given equal prominence, and 'REM' (a Windows batch comment) is used in the CLI example. There are no Linux-specific tools or shell scripting examples beyond Bash variable assignment, and the PowerShell section is more detailed and prominent.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (which is more cross-platform) first.
- Provide more detailed Bash/Linux shell scripting examples, including error handling and output, to match the PowerShell example's depth.
- Use cross-platform comment syntax in CLI examples (e.g., '#' for Bash, 'REM' for Windows), and clearly separate Bash and Windows batch examples.
- Highlight that Azure CLI is fully cross-platform and can be used in Linux, macOS, and Windows environments.
- Consider adding Linux-native automation examples (e.g., using shell scripts or cron jobs) for starting/stopping VMs.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. The main VM creation walkthrough uses a Windows 11 Pro image as its example, with no mention of Linux images or their configuration differences. The only explicit scripting example for copying VMs uses a PowerShell script, with no Azure CLI or Linux shell alternatives provided. While the page references Azure CLI and ARM templates as alternative creation methods, it does not provide direct examples or links in the main flow, and Windows tools/patterns are mentioned first or exclusively in key sections.
Recommendations
- Include Linux VM creation examples alongside Windows, highlighting any differences in settings or options.
- Provide explicit Azure CLI and Bash script examples for tasks such as copying VMs, not just PowerShell.
- Alternate the order of examples so Linux is shown first in some sections, or present both OS options equally.
- Add notes or links about Linux-specific considerations (e.g., SSH keys, user setup) in relevant steps.
- Ensure artifact examples include popular Linux tools as well as Windows software.
Devtest Labs
Extend Azure DevTest Labs with Azure Functions
...es/devtest-labs/extend-devtest-labs-azure-functions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing instructions and screenshots for Visual Studio on Windows, referencing Windows-specific artifacts, and omitting Linux/macOS equivalents. The sample walkthrough assumes the use of Visual Studio (Windows-only), and there are no instructions for developing, building, or deploying the sample on Linux or macOS platforms. PowerShell is mentioned as a tool for creating service principals, but Linux alternatives (such as Bash scripts or VS Code) are not highlighted. The Windows Update artifact is featured prominently, with no mention of Linux update artifacts.
Recommendations
- Include instructions and screenshots for cross-platform tools such as Visual Studio Code and Azure CLI for building and deploying Azure Functions.
- Provide Linux/macOS equivalents for all steps, including sample code, build, and deployment workflows.
- Mention and link to Linux update artifacts or provide guidance for updating Linux VMs in DevTest Labs.
- Ensure that examples for creating service principals include Bash/Azure CLI commands and clarify platform compatibility.
- Add parity in sample code repositories (e.g., Python or Node.js samples) and reference them in the documentation.
Devtest Labs
Delete a lab virtual machine or a lab
...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell script as the sole example for automating the deletion of all VMs in a lab, without offering equivalent instructions or scripts for Linux/macOS users (e.g., Azure CLI, Bash). This creates a bias towards Windows users and PowerShell, making automation less accessible for those on other platforms.
Recommendations
- Add Azure CLI and/or Bash script examples for automating VM deletion, ensuring Linux/macOS users have clear guidance.
- Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI, and link to relevant documentation.
- Where scripting is discussed, present both Windows (PowerShell) and Linux/macOS (CLI/Bash) options side-by-side.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page mentions both Windows and Linux use cases in the introduction, but all examples and screenshots focus on generic UI steps without platform-specific guidance. However, passwords for Windows VMs are mentioned before SSH keys for Linux VMs, and there are no Linux/macOS-specific examples or CLI instructions (e.g., Bash, Azure CLI) for storing or retrieving secrets. There is a subtle Windows-first bias and a lack of Linux parity in practical examples.
Recommendations
- Add explicit Linux/macOS examples, such as storing SSH keys as secrets and using them in VM creation.
- Include Azure CLI or Bash command examples for secret management, not just UI screenshots.
- Ensure that references to secrets for Linux VMs (e.g., SSH keys) are given equal prominence and detailed steps.
- Provide platform-specific guidance or troubleshooting for Linux/macOS users where relevant.
Devtest Labs
How to delete and export personal data
...n/articles/devtest-labs/personal-data-delete-export.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides an Azure PowerShell example for exporting personal data, with no mention of Linux/macOS-compatible alternatives (such as Azure CLI, Bash, or REST API). The use of PowerShell and Windows-centric Azure modules creates friction for users on Linux or macOS, who may not have access to or prefer not to use PowerShell.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
- Mention REST API options for exporting data, if available, and provide sample requests.
- Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide guidance if so.
- Present cross-platform examples first, or at least alongside Windows/PowerShell examples, to avoid Windows-first bias.
Devtest Labs
Create environments from ARM templates
...evtest-labs/devtest-lab-create-environment-from-arm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the automation section. The only detailed automation example is a PowerShell script, with step-by-step instructions and code provided for Windows/PowerShell users. While the Azure CLI is mentioned as an alternative, no CLI example or walkthrough is given. This prioritizes Windows tools and patterns, and leaves Linux/macOS users without equivalent guidance for automating environment creation.
Recommendations
- Provide a full Azure CLI example for automating environment creation, including a sample command and parameter usage.
- Include guidance for running automation scripts on Linux/macOS, such as using Bash or shell scripts.
- Present both PowerShell and CLI examples side-by-side, or alternate which is shown first, to avoid implicit prioritization.
- Explicitly mention cross-platform compatibility and note any differences in workflow or prerequisites for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions and a full script for adding artifacts to Azure DevTest Labs VMs using Azure PowerShell, but does not offer equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell approach is presented as the only command-line option, and prerequisites and examples are Windows-centric, creating friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI or Bash examples for adding artifacts to VMs, including full command-line workflows.
- In prerequisites, mention Azure CLI and Bash as supported alternatives for Linux/macOS users.
- Present cross-platform options side-by-side or in tabs, rather than focusing solely on PowerShell.
- Explicitly state which methods are platform-agnostic and which are Windows-specific.
Devtest Labs
Add an Artifact Repository to Your Lab
.../main/articles/devtest-labs/add-artifact-repository.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides extensive instructions and examples for adding an artifact repository to Azure DevTest Labs, with a strong emphasis on Azure PowerShell and ARM templates. All command-line automation is shown using PowerShell, with no Bash, Linux shell, or macOS-specific examples. The deployment section explicitly instructs users to use Azure PowerShell, and the only script provided is a PowerShell script. While Azure CLI is mentioned as an alternative for ARM template deployment, no CLI or Linux-native examples are given. The ordering of examples and tooling references puts PowerShell and Windows-centric tools first, creating friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands and scripts, including resource group creation and ARM template deployment.
- Provide Bash or shell script examples for automating repository addition, or clarify cross-platform compatibility of the steps.
- Explicitly state which steps are platform-agnostic and which require Windows/PowerShell, and offer alternatives where possible.
- Reorder sections or provide tabs so Linux/macOS and CLI users see relevant examples without needing to adapt PowerShell code.
- Include notes or links to official Azure CLI documentation for each step currently shown in PowerShell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily featured throughout, with most examples and guidance using PowerShell cmdlets. Windows tools and patterns (e.g., New-Guid, Get-AzADUser) are mentioned exclusively or before any cross-platform alternatives. The Azure CLI section is present but less detailed, and there are no explicit Linux/macOS shell examples or guidance for generating GUIDs or querying Azure AD from non-Windows environments. This creates friction for Linux/macOS users, who may need to find their own equivalents or workarounds.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for key steps, such as generating GUIDs (e.g., using uuidgen) and querying Azure AD (e.g., using Azure CLI or Microsoft Graph API).
- Provide Azure CLI examples with equivalent detail and coverage as PowerShell, including parameter file deployment and role assignment.
- Mention cross-platform tools and patterns first, or at least alongside Windows/PowerShell options.
- Clarify which commands and tools are cross-platform and which are Windows-specific.
- Link to relevant Linux/macOS documentation for Azure CLI and scripting.
Devtest Labs
Nested ARM templates for lab environments
...es/devtest-labs/deploy-nested-template-environments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell and Visual Studio tooling before or instead of Linux/macOS alternatives. The deployment instructions reference Azure PowerShell (`New-AzResourceGroupDeployment`) first, with Azure CLI mentioned second. The related content highlights Visual Studio, a Windows-centric tool, without referencing cross-platform editors or deployment methods. There are no explicit Linux/macOS shell examples or guidance for users on those platforms.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
- Include Linux/macOS-specific instructions or examples (e.g., Bash shell usage, VS Code integration).
- Reference cross-platform editors like VS Code in related content, not just Visual Studio.
- Clarify that all deployment steps can be performed on Linux/macOS and provide any platform-specific notes if needed.
Devtest Labs
Create a Service Fabric cluster environment
...test-labs/create-environment-service-fabric-cluster.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows as the default OS for cluster VMs, providing only PowerShell instructions and scripts for certificate creation, and omitting equivalent Linux instructions or examples. The certificate creation process is described exclusively using a PowerShell script (.ps1), with no mention of Linux-compatible alternatives or commands. Windows is listed as the default OS, and Linux support is only briefly mentioned later, without guidance.
Recommendations
- Provide explicit instructions and examples for Linux users, including how to create the required cluster certificate using Linux tools (e.g., OpenSSL) and how to encode it in Base64.
- Mention Linux as an equal option when selecting the operating system, not just as a secondary note.
- Offer a bash script or step-by-step Linux/macOS command-line instructions for certificate generation and management.
- Clarify any differences in cluster setup or management between Windows and Linux, if applicable.
- Ensure screenshots and UI descriptions reflect both Windows and Linux scenarios where relevant.
Devtest Labs
Add and configure lab users with role-based access control (RBAC)
.../articles/devtest-labs/devtest-lab-add-devtest-user.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for adding lab users via the Azure portal and Azure PowerShell, but only PowerShell is offered as the CLI/script example. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. PowerShell is presented as the sole scripting option, which is more native to Windows environments and less common on Linux/macOS. The prerequisites and instructions reference PowerShell exclusively, and do not mention or provide parity for Linux users who may prefer Bash or Azure CLI.
Recommendations
- Add equivalent Azure CLI examples for adding lab users, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that Azure PowerShell can be run in Azure Cloud Shell (which is cross-platform), but also provide Bash/CLI alternatives.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- Reorder examples so that cross-platform methods (Azure portal, Azure CLI) are presented before or alongside PowerShell.
Devtest Labs
Create custom artifacts for VMs
...n/articles/devtest-labs/devtest-lab-artifact-author.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias. All code examples use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey). There are no Linux shell script examples, nor is there guidance for creating Linux-compatible artifacts. The workflow and screenshots focus exclusively on Windows artifacts, and Windows terminology/tools are presented first and exclusively.
Recommendations
- Add parallel Linux examples using shell scripts (e.g., Bash) and Linux package managers (e.g., apt, yum).
- Show how to structure artifact definition files for Linux VMs, including sample runCommand values for Linux.
- Include instructions and screenshots for creating and storing Linux artifacts.
- Mention Linux tools and patterns alongside Windows equivalents, not after or instead of them.
- Clarify any OS-specific differences in artifact creation and usage.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific resources and examples, such as linking to 'Windows virtual machines in Azure' and listing Windows tools (e.g., Visual Studio, Fiddler) as artifact examples. There are no explicit Linux/macOS examples, tools, or links, and Windows is mentioned before any cross-platform or Linux alternatives.
Recommendations
- Include references and links to Linux and macOS VM documentation, such as 'Linux virtual machines in Azure'.
- Provide artifact examples relevant to Linux/macOS environments (e.g., installation of Linux tools, configuration scripts).
- Ensure that examples and instructions are platform-neutral or include both Windows and Linux/macOS variants.
- List cross-platform tools and patterns before or alongside Windows-specific ones.
- Add explicit mention of support for Linux/macOS in relevant sections (e.g., base images, artifacts, environments).