Devtest Labs
188
Total Pages
144
Linux-Friendly Pages
44
Pages with Bias
23.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
113 issues found
Showing 1-25 of 113 flagged pages
Devtest Labs
How to delete and export personal data
...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 Azure CLI, Bash, or cross-platform alternatives. All instructions and code samples are tailored to PowerShell, which is primarily associated with Windows environments, and Windows-centric Azure modules are used exclusively. There is no guidance for Linux or macOS users, nor are equivalent steps or tools referenced.
Recommendations
- Add Azure CLI examples for exporting personal data, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
- Include Bash script samples or references to REST API methods for users who prefer non-PowerShell workflows.
- Reorder or parallelize examples so that Linux/macOS-friendly methods are presented alongside or before Windows/PowerShell methods.
- Clarify platform compatibility for each method, helping users choose the best approach for their OS.
Create Pull Request
Devtest Labs
Secure Labs by Using Remote Desktop Gateways
...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All examples and tooling references are Windows-centric: PowerShell scripts are used for certificate creation and lab configuration, Windows-only tools like Internet Information Services (IIS) and RDGatewayFedAuth.msi are mentioned exclusively, and the workflow assumes RDP as the remote access protocol. There are no Linux/macOS equivalents or examples for certificate management, gateway setup, or remote access, and Windows terminology and tools are presented first and exclusively.
Recommendations
- Provide Linux/macOS equivalents for certificate creation and management (e.g., using OpenSSL commands).
- Include examples of configuring the gateway using Bash scripts or Azure CLI on Linux/macOS.
- Mention and provide guidance for cross-platform RDP clients (such as FreeRDP, Remmina, or Microsoft Remote Desktop for macOS) and note any token authentication limitations.
- Offer alternatives to IIS for request routing, such as NGINX or Apache, with configuration examples.
- Clarify which steps/tools are Windows-only and suggest Linux/macOS alternatives where possible.
- Reorder examples so that cross-platform or Linux/macOS options are presented alongside or before Windows-specific instructions.
Devtest Labs
Upload a VHD file to Azure DevTest Labs by using AzCopy
...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with AzCopy described as a Windows-only utility and all instructions, examples, and screenshots referencing Windows tools and PowerShell. There are no Linux or macOS equivalents, nor any mention of alternative workflows for non-Windows users. This creates significant friction for users on other platforms.
Recommendations
- Update the documentation to reference AzCopy v10+, which is cross-platform (Windows, Linux, macOS).
- Provide installation instructions for AzCopy on Linux and macOS.
- Include command-line examples for Linux/macOS (e.g., Bash) alongside Windows examples.
- Replace or supplement PowerShell-specific instructions with Azure CLI or REST API alternatives.
- Clarify which AzCopy version is being referenced and recommend the latest version for all platforms.
Devtest Labs
Quickstart: Create a lab with REST API
...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell scripts and Windows-centric tooling (Az Module, PowerShell cmdlets) for all steps, including authentication, REST API invocation, and resource cleanup. No examples or guidance are provided for Linux/macOS users, such as using Bash, curl, or Azure CLI. This creates friction for non-Windows users and may prevent them from easily following the quickstart.
Recommendations
- Provide equivalent examples using Bash and curl for Linux/macOS users.
- Include Azure CLI commands for authentication and REST API invocation, which are cross-platform.
- Add a note at the beginning clarifying that PowerShell examples are Windows-focused and link to Linux/macOS alternatives.
- Ensure variable and file path usage is platform-agnostic or provide platform-specific notes.
Devtest Labs
Upload a VHD file to Azure DevTest Labs by using AzCopy
...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows, with AzCopy described as a Windows-only utility and all instructions, examples, and screenshots referencing Windows tools and PowerShell. There are no Linux or macOS equivalents or instructions, and critical steps (such as uploading the VHD) cannot be completed by non-Windows users based on this documentation.
Recommendations
- Update the documentation to reference AzCopy v10+, which is cross-platform and supports Windows, Linux, and macOS.
- Provide installation instructions and usage examples for AzCopy on Linux and macOS.
- Include CLI examples using Bash or other common shells in addition to Windows Command Prompt.
- Clarify which AzCopy version is required and recommend the cross-platform version for broader compatibility.
- Add notes or sections for Linux/macOS users, including troubleshooting and path conventions.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines before Linux equivalents, omitting explicit mentions or examples of Linux VM usage, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples without Linux alternatives. There are no PowerShell-heavy examples, but the overall focus is on Windows environments and tooling.
Recommendations
- Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
- Provide examples of artifacts and tools relevant to Linux environments (e.g., install Apache, Git, or other Linux utilities).
- Ensure artifact and template repository examples include Linux-focused templates and artifacts.
- Mention Linux base images and their configuration alongside Windows base images.
- Balance the order of presentation so that Windows and Linux options are discussed equally and in parallel.
Devtest Labs
Integrate Azure DevTest Labs with DevOps CI/CD Pipelines
...blob/main/articles/devtest-labs/devtest-lab-dev-ops.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 scripts and Azure CLI as primary integration methods, without mentioning Linux shell scripting or providing Linux-specific examples. Windows-centric tools and patterns are mentioned first or exclusively, and there is a lack of explicit Linux or cross-platform examples for CI/CD integration with DevTest Labs.
Recommendations
- Include Linux shell scripting (e.g., Bash) examples alongside PowerShell for managing DevTest Labs resources.
- Mention Linux-based CI/CD agents and workflows explicitly, and provide parity in instructions for both Windows and Linux environments.
- Highlight cross-platform compatibility of Azure CLI and REST APIs, and provide sample commands for both Windows and Linux terminals.
- Add references to Linux tools and patterns (such as cron jobs, systemd services, or Ansible) where relevant.
- Ensure that examples and guidance do not assume a Windows-first approach, and balance the order and prominence of Windows and Linux content.
Devtest Labs
Delete a lab virtual machine or a lab
...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and examples for deleting lab VMs and labs in Azure DevTest Labs, but automation is only demonstrated using PowerShell, a Windows-centric tool. There are no equivalent examples for Linux users (e.g., Bash, Azure CLI), and the scripting section exclusively references PowerShell cmdlets and patterns. This creates a bias toward Windows users and may hinder Linux users from automating these tasks.
Recommendations
- Add equivalent automation examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Provide Bash script samples for deleting all VMs in a lab, alongside the PowerShell example.
- Explicitly mention that the Azure portal steps are OS-agnostic, but clarify that scripting can be done from any platform using Azure CLI.
- Include links to Azure CLI documentation for resource deletion tasks.
- Ensure that future documentation covers both Windows and Linux automation options in parallel.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a clear Windows bias. PowerShell is heavily featured throughout, with multiple examples and references to PowerShell-specific cmdlets for key tasks (e.g., obtaining ObjectId, deploying templates, generating GUIDs). Windows tools and patterns (PowerShell, New-Guid) are mentioned exclusively or before their cross-platform equivalents. The Azure CLI section is present but less detailed and lacks parity in example depth. There are no explicit Linux shell/bash examples, nor references to Linux-native tools or workflows.
Recommendations
- Add bash/Linux shell examples for tasks such as generating GUIDs, obtaining ObjectId, and deploying ARM templates using Azure CLI.
- Expand the Azure CLI section to match the detail and coverage of the PowerShell section, including step-by-step instructions and parameter explanations.
- Reference cross-platform tools and workflows (e.g., uuidgen for GUID generation, az ad user for ObjectId retrieval) alongside or before Windows-specific tools.
- Ensure that all examples and instructions are clearly marked as cross-platform where applicable, and explicitly mention Linux/Mac compatibility.
- Consider adding a table or section comparing PowerShell and CLI commands for each major step, to help users choose their preferred environment.
Devtest Labs
Create a Service Fabric cluster environment
...test-labs/create-environment-service-fabric-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: the default operating system for cluster VMs is Windows; certificate creation instructions exclusively use a PowerShell script (Create-ClusterCertificate.ps1) and require launching PowerShell and Notepad, both Windows-centric tools; there are no Linux-specific instructions or examples for certificate creation or cluster management; and Windows terminology and workflows are presented first or exclusively.
Recommendations
- Provide Linux-specific instructions for certificate creation, such as using OpenSSL commands, and include example scripts.
- Mention and demonstrate how to perform cluster management tasks (start/stop, etc.) from Linux environments, including CLI commands.
- When describing OS selection, present Windows and Linux options equally, and avoid defaulting to Windows.
- Replace or supplement PowerShell/Notepad steps with cross-platform alternatives (e.g., Bash, nano, vi, or VS Code).
- Add screenshots and examples from Linux environments to balance visual representation.
Devtest Labs
Add and configure lab users with role-based access control (RBAC)
.../articles/devtest-labs/devtest-lab-add-devtest-user.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for automation, referencing Microsoft accounts and Entra ID (with links to Windows Server docs), and omitting any Linux-specific CLI (az CLI) or Bash examples. The prerequisites and instructions focus on PowerShell and do not mention Linux tools or workflows, making it less accessible for Linux users.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Include instructions for running automation scripts in Bash or other Linux shells, not just PowerShell.
- Reference Linux account management and authentication documentation where relevant, not only Microsoft account and Windows Server docs.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide steps for both environments.
- Ensure screenshots and UI references are not Windows-specific, or supplement with examples from Linux environments where applicable.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by using a Windows 11 Pro image as the example in the main workflow, mentioning PowerShell scripts for VM copying without Linux alternatives, and omitting explicit Linux VM creation or connection examples. Linux-specific instructions, images, or CLI commands are not provided, and Windows terminology is used by default.
Recommendations
- Provide parallel examples using a popular Linux image (e.g., Ubuntu) alongside the Windows 11 Pro example, including screenshots and step-by-step instructions.
- Include Linux-specific connection instructions (e.g., SSH commands) and mention differences in credential setup for Linux VMs.
- When referencing scripts for copying VMs, offer both PowerShell and Bash/CLI alternatives, or clarify cross-platform options.
- Ensure artifact examples include Linux-relevant tools and software, not just those commonly used on Windows.
- Review terminology and screenshots to ensure Linux VMs are equally represented in visuals and instructions.
Devtest Labs
Create custom artifacts for VMs
...n/articles/devtest-labs/devtest-lab-artifact-author.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 providing only PowerShell-based examples and referencing Windows-specific tools (e.g., Chocolatey, powershell.exe) without offering equivalent Linux shell script or tool examples. All code snippets and walkthroughs focus on Windows artifacts, and there is no demonstration of how to create or use artifacts for Linux VMs. The structure and examples prioritize Windows scenarios, leaving Linux users without guidance or parity.
Recommendations
- Add parallel Linux examples using shell scripts (e.g., Bash) in artifact definitions, showing how to use 'commandToExecute' for Linux VMs.
- Include Linux-specific tools (e.g., apt, yum) in sample artifacts, similar to how Chocolatey is used for Windows.
- Provide a downloadable sample artifact for Linux, such as one that installs a package or runs a shell script.
- Ensure that documentation sections and examples alternate or equally represent both Windows and Linux scenarios.
- Explicitly mention differences and best practices for Linux artifact development, including script file extensions (.sh), permissions, and common patterns.
Devtest Labs
Grant user permissions to specific lab policies
...st-lab-grant-user-permissions-to-specific-lab-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, which is primarily a Windows-centric tool. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The installation instructions and all code samples assume the use of Azure PowerShell, and there is no mention of how to perform these tasks on Linux or macOS systems. This creates a strong Windows bias and may hinder users working in non-Windows environments.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
- Include Bash shell scripts or command-line instructions for Linux users.
- Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide installation instructions for those platforms.
- Reorder or balance examples so that Linux and cross-platform tools are presented alongside or before Windows-specific tools.
- Provide guidance on how to perform role assignments and policy management using the Azure Portal (web interface), which is platform-agnostic.
Devtest Labs
Create a custom image from a lab VM
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (Sysprep) before Linux equivalents (deprovision), and by providing more detail and direct links for Windows processes. There are no concrete Linux command examples or screenshots, and the generalization step is described primarily in Windows terms.
Recommendations
- Present Linux and Windows generalization options with equal prominence, possibly alternating the order or grouping them together.
- Include explicit Linux command examples (e.g., waagent -deprovision) and step-by-step instructions for Linux VMs.
- Add screenshots or illustrations showing the process for both Windows and Linux VMs.
- Provide direct links to both Windows and Linux documentation for generalization procedures.
- Clarify any differences in the image creation workflow for Linux VMs, if applicable.
Devtest Labs
Create environments from ARM templates
...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed automation instructions and scripts exclusively for Azure PowerShell, with no equivalent Bash or Linux shell example. PowerShell is presented first and in greater detail than Azure CLI, and the automation section is heavily focused on Windows tooling. There are no Linux-specific instructions or examples, and the only mention of Azure CLI is brief and lacks a worked example.
Recommendations
- Add a full Azure CLI (bash) example for automating environment creation, including a sample script and usage instructions.
- Present Azure CLI and PowerShell options side-by-side, or alternate which is presented first, to avoid Windows-first ordering.
- Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
- Include notes or links to relevant Linux tools or patterns (e.g., using curl, jq, or bash scripting for automation).
- Review screenshots and UI instructions for OS-neutral language and imagery.
Devtest Labs
Create custom images for lab VMs from VHD files
...n/articles/devtest-labs/devtest-lab-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page shows moderate Windows bias. PowerShell is mentioned as an alternative method for creating custom images and for uploading VHD files, with no equivalent Bash or Linux CLI examples referenced. Windows tools (sysprep) are described before Linux equivalents (deprovision), and the upload instructions reference Microsoft-centric tools (AzCopy, Storage Explorer, PowerShell) without mentioning Linux-native options. The flow and examples tend to prioritize Windows terminology and tooling.
Recommendations
- Include Bash/Azure CLI examples alongside PowerShell for creating custom images and uploading VHD files.
- Mention Linux-native tools (e.g., dd, qemu-img, SCP, rsync) for VHD creation and upload, where relevant.
- Ensure Linux instructions (e.g., waagent --deprovision) are described with equal detail and prominence as Windows (sysprep).
- Add explicit guidance for Linux users, such as command-line steps for uploading VHDs from Linux environments.
- Balance the order of Windows and Linux instructions, alternating or grouping them to avoid Windows-first presentation.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: Windows-specific tools (PowerShell, Visual Studio, Fiddler) are mentioned exclusively or before Linux equivalents; automation examples and scripts reference PowerShell without mentioning Bash or CLI alternatives; links to quickstarts and templates are labeled as 'create-lab-windows-vm-*', with no explicit Linux VM examples; artifact examples and VM customization focus on Windows-centric scenarios; and Active Directory domain-join is highlighted without mention of Linux identity solutions.
Recommendations
- Include Linux-specific examples and quickstarts, such as 'create-lab-linux-vm-bicep.md', 'create-lab-linux-vm-template.md', and 'create-lab-linux-vm-terraform.md'.
- Provide Bash/Azure CLI script examples alongside PowerShell for automation tasks, such as adding users or deleting VMs.
- Mention Linux tools and applications (e.g., Git, VS Code, Apache) as artifact examples, not just Windows tools.
- Describe how to join Linux VMs to identity solutions (e.g., Azure AD, LDAP) if applicable.
- Ensure ARM template and image builder documentation explicitly covers both Windows and Linux scenarios.
- Balance references to Windows and Linux in all lists and examples, and avoid defaulting to Windows-first naming or ordering.
Devtest Labs
Move DevTest Labs to another region
...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-centric instructions and examples, referencing Windows-specific tools (such as AzCopy and PowerShell cmdlets), and linking to Windows-focused articles (e.g., swapping OS disks using PowerShell). Linux alternatives (such as Bash, CLI, or Linux-native tools) are either missing or mentioned after Windows, and there are no explicit Linux command examples for key steps like disk migration or VM management.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for disk migration and VM management.
- Include instructions and examples for using AzCopy on Linux/macOS, clarifying cross-platform usage.
- Reference Linux-focused documentation (e.g., swapping OS disks on Linux VMs) alongside Windows articles.
- Explicitly state that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
- Where screenshots or UI references are given, clarify if the experience differs on non-Windows platforms or in browser-based tools like Azure Cloud Shell.
Devtest Labs
Quickstart: Create a lab with REST API
...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for all command-line examples, assumes the presence of the PowerShell Az Module, and does not provide equivalent instructions for Linux or macOS users (e.g., Bash, curl, Azure CLI). Windows tooling and patterns are mentioned throughout, with no cross-platform alternatives or parity.
Recommendations
- Add equivalent examples using Bash and curl for REST API calls, suitable for Linux/macOS users.
- Include Azure CLI examples for authentication and resource management, as it is cross-platform.
- Update the prerequisites section to mention both PowerShell and Bash/Azure CLI options.
- Clearly indicate which steps are platform-specific and provide alternatives for each major OS.
- Avoid assuming file path conventions (e.g., 'path\body.json') that are Windows-specific; use cross-platform notation or clarify.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits Windows bias by consistently referencing Windows VMs as the default in examples, labeling code samples as 'powershell' even though the scripts are bash/CLI, and omitting explicit Linux VM creation or management examples. There is no mention of Linux-specific VM images, authentication methods, or usage patterns, and the terminology and sample focus suggest a Windows-centric approach.
Recommendations
- Include examples for creating and managing Linux VMs, specifying Linux marketplace images and SSH authentication.
- Correct code sample language labels to 'bash' or 'azurecli' where appropriate, instead of 'powershell'.
- Provide parity in documentation by mentioning both Windows and Linux options in descriptions and tables.
- Add notes or sections highlighting differences or considerations when working with Linux VMs in Azure DevTest Labs.
- Ensure that script samples and instructions are platform-neutral or provide alternatives for both Windows and Linux users.
Devtest Labs
Upload a VHD file to Azure DevTest Labs by using AzCopy
...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. AzCopy is described as a Windows-only tool, and all usage instructions reference Windows environments (Command Prompt, Windows file paths). The process for obtaining the storage account URI is tied to PowerShell and Windows screenshots. There are no Linux or cross-platform examples, nor any mention of Linux-compatible alternatives or usage patterns.
Recommendations
- Clarify whether AzCopy v10+ is cross-platform (since newer versions support Linux/macOS) and update the note accordingly.
- Provide Linux and macOS installation instructions for AzCopy, if supported.
- Include example commands for Linux/macOS shells (e.g., bash), with appropriate file paths and syntax.
- Add screenshots or instructions that do not reference PowerShell or Windows-only UI elements.
- Mention alternative tools or approaches for non-Windows users if AzCopy is truly Windows-only.
- Ensure parity in automation examples, showing how to script uploads on Linux/macOS.
Devtest Labs
Create and manage virtual machines in Azure DevTest Labs with Azure CLI
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. The first VM creation example uses a Windows image, and Windows terminology (e.g., 'Remote Desktop') is mentioned before Linux equivalents. Artifact examples include both Linux and Windows, but the sample output for listing artifacts only shows a Windows artifact. The Cloud Shell section gives PowerShell instructions before Bash, and highlights Windows-specific shell syntax issues. Linux examples are present but generally appear after Windows ones.
Recommendations
- Provide Linux VM creation examples before or alongside Windows examples, or alternate their order.
- Include sample outputs for both Linux and Windows artifacts when listing artifacts.
- Present Bash and PowerShell instructions in parallel, or alternate which is shown first.
- Explicitly mention Linux tools (e.g., SSH) before or alongside Windows tools (e.g., Remote Desktop) when discussing connection options.
- Ensure parity in artifact examples, showing both Linux and Windows use cases.
- Consider a section highlighting cross-platform considerations and differences.
Devtest Labs
Specify resource group for Azure VMs in DevTest Labs
...b/main/articles/devtest-labs/resource-group-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for scripting the resource group assignment, but does not offer equivalent examples for Bash, Linux shell, or cross-platform scripting. The command invocation uses Windows-style notation and file extensions (.ps1), and the scripting section is titled 'Use PowerShell' without mentioning alternatives. There is no mention of Linux-specific tools or CLI patterns, nor are Linux/Bash examples provided alongside the PowerShell example.
Recommendations
- Add a Bash or shell script example using the Azure CLI for Linux/macOS users.
- Include instructions for running the script on Linux/macOS, such as using .sh files and appropriate command syntax.
- Clarify that the Azure CLI commands used in the PowerShell script are cross-platform, and provide examples for both Windows and Linux environments.
- Consider renaming the 'Use PowerShell' section to 'Use scripting' or 'Use PowerShell or Bash', and provide parity in examples.
- Explicitly mention that the steps are applicable to both Windows and Linux users where relevant.
Devtest Labs
Define VM start order with Azure Automation
...devtest-labs/start-machines-use-automation-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for scripting and automation examples, with no mention of Bash, Python, or other cross-platform alternatives. All instructions and code samples are tailored to PowerShell and Azure Automation, which is most commonly used on Windows. There is no guidance for Linux users or those preferring non-Windows tools, and Windows-centric terminology and patterns are used throughout.
Recommendations
- Provide equivalent examples using Bash or Python scripts that can be run on Linux-based systems.
- Include instructions for using Azure CLI or REST API, which are cross-platform, to achieve the same VM start order functionality.
- Add a section explicitly addressing Linux users, outlining how to set up and run automation from a Linux environment.
- Mention and link to Azure Automation support for non-PowerShell runbooks (e.g., Python), and provide sample code.
- Ensure that references to tools and patterns do not assume a Windows environment by default, and present Linux options alongside Windows options.