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 51-75 of 334 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for scripting and automation, with no equivalent CLI or Bash examples for Linux users. The prerequisites and instructions focus on PowerShell and do not mention or provide guidance for using Azure CLI or Bash, which are more common on Linux. The documentation also refers to running 'Windows PowerShell scripts or Bash commands' in artifacts, but only PowerShell is covered in detail for artifact application.
Recommendations
- Add equivalent Azure CLI examples for adding artifacts to VMs, including full command-line scripts.
- Include Bash script examples for Linux users where automation is discussed.
- Mention and link to Azure CLI installation and usage in the prerequisites section alongside PowerShell.
- Ensure that instructions and screenshots are platform-neutral or provide both Windows and Linux variants.
- Explicitly state that both Windows and Linux VMs are supported and clarify any platform-specific differences in artifact handling.
Create Pull Request
Devtest Labs
Distributed collaborative development of Azure DevTest Labs resources
...ces-distributive-collaborative-development-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a mild Windows bias by referencing Azure PowerShell and PowerShell scripts as primary tools for managing and customizing resources. There is no mention of Linux shell equivalents (e.g., Bash), and examples or references to Linux-based tooling are absent. The documentation also refers to DSC scripts, which are Windows-centric, without mentioning alternatives for Linux configuration management.
Recommendations
- Include examples using Bash or Azure CLI alongside PowerShell for resource management tasks.
- Mention Linux-compatible configuration management tools (e.g., cloud-init, Ansible) when discussing scripts and automation.
- Clarify that Resource Manager templates and artifact scripts can be authored and executed on both Windows and Linux platforms.
- Add explicit references or links to Linux-focused documentation where relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references managing tags using PowerShell or Azure CLI, but mentions PowerShell first and does not provide any explicit Linux or Bash examples. There are no screenshots or instructions specific to Linux environments, and the only tool mentioned by name is PowerShell, which is traditionally associated with Windows. This suggests a subtle Windows bias, as Linux users may expect Bash or shell examples or at least equal mention of Linux-native tools.
Recommendations
- Explicitly mention and provide examples for managing tags using Azure CLI in Bash or Linux environments.
- When referencing command-line tools, list Azure CLI before or alongside PowerShell to avoid Windows-first bias.
- Include screenshots or instructions that are relevant for Linux users, such as using Azure CLI in a terminal.
- Add a section or note clarifying that all tag management operations can be performed equally on Linux, macOS, and Windows, with links to platform-specific guides if available.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing extensive PowerShell examples and references, mentioning Windows-centric tools (PowerShell cmdlets) for key tasks (such as GUID generation and querying Azure AD), and presenting PowerShell instructions before Azure CLI equivalents. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the use of PowerShell is assumed for automation and deployment steps. The CLI section is shorter and lacks parity in detail compared to PowerShell. Linux users are not provided with bash or shell-native alternatives for tasks like GUID generation or querying Azure AD object IDs.
Recommendations
- Add bash/Azure CLI examples for all key steps, such as querying Azure AD user/group/service principal object IDs and generating GUIDs.
- Present Azure CLI and bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Reference cross-platform tools for GUID generation (e.g., 'uuidgen' in bash) and querying Azure AD (e.g., 'az ad user show').
- Ensure all automation steps (template deployment, role assignment) have equivalent CLI/bash instructions.
- Explicitly mention that PowerShell examples are for Windows and provide Linux/macOS alternatives.
- Balance the detail and explanation between PowerShell and CLI/bash sections.
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 is heavily oriented toward Windows environments, with exclusive use of Windows RDP, PowerShell scripts, and Windows-specific tools (IIS, RDGatewayFedAuth.msi, System Center VMM). There are no examples or guidance for Linux-based remote desktop solutions, nor are Linux command-line equivalents or cross-platform alternatives mentioned. Windows terminology and tooling are presented first and exclusively throughout the page.
Recommendations
- Include examples for connecting to lab VMs from Linux clients, such as using xfreerdp, Remmina, or rdesktop.
- Provide Linux shell (bash) equivalents for certificate management and deployment steps, alongside PowerShell commands.
- Mention and document cross-platform remote desktop gateway solutions or clarify if the solution is Windows-only.
- Add guidance for Linux administrators on configuring and automating lab settings, possibly using Azure CLI or ARM templates from Linux.
- Explicitly state Windows-only requirements where applicable, and suggest alternatives or workarounds for Linux environments.
- Reference Linux-compatible remote desktop protocols (such as XRDP) and tools where possible.
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
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. The default operating system for cluster creation is set to Windows, and the only example provided for certificate creation uses a PowerShell script (Create-ClusterCertificate.ps1), with explicit instructions to use PowerShell and Notepad—both Windows-specific tools. There are no equivalent Linux instructions or examples for certificate creation or cluster management, and Windows is mentioned before Linux in the OS selection step. This may make it more difficult for Linux users to follow the documentation or feel supported.
Recommendations
- Provide Linux-specific instructions and examples for certificate creation, such as using OpenSSL commands and Linux text editors.
- Include screenshots and steps that demonstrate the process on Linux environments, not just Windows.
- Mention Linux as an equal option to Windows when selecting the operating system, rather than listing Windows as the default.
- Offer cross-platform scripts (e.g., Bash, Python) for certificate generation and other cluster management tasks.
- Review all tooling references and ensure Linux alternatives are documented and easy to find.
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 providing only Azure PowerShell examples for scripting, referencing Microsoft accounts (with links to Windows Server docs), and omitting any Linux-specific CLI (e.g., Azure CLI/bash) instructions. The PowerShell workflow is described in detail, while no equivalent Linux shell or cross-platform CLI example is given. The prerequisites and instructions prioritize PowerShell and Microsoft account patterns, which are more familiar to Windows users.
Recommendations
- Add Azure CLI (az) examples for adding lab users, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include instructions for using Bash or other shell environments in Azure Cloud Shell, not just PowerShell.
- Reference Microsoft accounts in a more platform-neutral way, or clarify that Azure AD/Entra ID users can be managed from any OS.
- Ensure screenshots and step-by-step instructions are not Windows-centric (e.g., avoid only showing Windows UI elements if possible).
- Explicitly mention that all procedures can be performed from Linux/macOS environments using Azure CLI or portal.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by presenting a Windows 11 Pro image as the example for VM creation, mentioning PowerShell scripts as the primary method for copying VMs into a lab, and omitting explicit Linux VM creation examples or Linux-specific instructions. Windows tools and patterns (such as PowerShell) are referenced before or instead of Linux equivalents, and there is no demonstration of creating or connecting to Linux VMs.
Recommendations
- Include explicit examples for creating Linux VMs, such as selecting Ubuntu or other Linux images in the walkthrough.
- Provide Linux-specific instructions for VM access (e.g., SSH connection details) alongside Windows (RDP) instructions.
- Mention and link to Bash/Azure CLI scripts for copying VMs into a lab, not just PowerShell.
- Ensure screenshots and step-by-step guides alternate or include both Windows and Linux scenarios.
- Clarify that DevTest Labs supports both Windows and Linux VMs, and highlight any differences in configuration or artifact usage.
Devtest Labs
Configure autoshutdown for lab virtual machines
...ain/articles/devtest-labs/devtest-lab-auto-shutdown.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing 'Windows Plan' and defaulting to Windows-based App Service Plans when creating Logic Apps, and by exclusively providing examples and instructions for the Azure portal and Office 365 Outlook integration, which are more commonly used in Windows environments. There are no examples or mentions of Linux-specific tools, email clients, or alternative approaches, nor is there guidance for command-line or automation via bash, Azure CLI, or other Linux-friendly methods.
Recommendations
- Provide examples for configuring autoshutdown using Azure CLI and/or PowerShell, and ensure both Windows and Linux command-line instructions are included.
- Mention Linux-compatible email clients (such as Thunderbird, Evolution, or webmail) and provide guidance for integrating with them, or with generic SMTP services.
- Clarify that the App Service Plan for Logic Apps can be Linux-based and provide steps for selecting a Linux plan.
- Include screenshots or instructions for Linux users where UI or tool differences exist.
- Add a section on automation using REST API calls with curl or similar Linux tools.
- Ensure parity in documentation by listing both Windows and Linux options for all major steps, especially where platform-specific terminology or defaults are used.
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 primarily through the use of PowerShell for automation examples, with detailed scripts and instructions provided only for Azure PowerShell. While the Azure CLI is briefly mentioned as an alternative, no CLI example or script is given, and the PowerShell workflow is presented first and in detail. There are no Linux-specific instructions, nor are cross-platform considerations (such as bash scripting or Linux tooling) addressed.
Recommendations
- Provide a complete Azure CLI example for automating environment creation, including a sample script and usage instructions.
- Present CLI and PowerShell examples side-by-side or alternate which is shown first to avoid 'windows_first' bias.
- Explicitly mention cross-platform compatibility and note which tools work on Linux, macOS, and Windows.
- Include references to bash or shell scripting for Linux users where appropriate.
- Add a note about prerequisites for Linux users (e.g., installing Azure CLI) and clarify that all steps can be performed on non-Windows platforms.
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 Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell as a method for creating custom images and uploading VHD files, and by listing Windows-specific tools (sysprep) before Linux equivalents (deprovision). PowerShell is mentioned multiple times as a primary automation option, while Linux command-line alternatives (such as Bash scripts or Azure CLI) are not referenced. The upload instructions mention AzCopy and Storage Explorer, which are cross-platform, but PowerShell is highlighted as a distinct method. The OS selection instructions mention Windows and sysprep before Linux and deprovision.
Recommendations
- Add explicit examples and links for using Azure CLI and Bash scripts for both uploading VHD files and creating custom images.
- Ensure Linux instructions (e.g., deprovision) are given equal prominence and detail as Windows instructions (e.g., sysprep).
- When listing upload methods, alternate the order or group Windows and Linux options together to avoid Windows-first ordering.
- Provide sample commands for Linux environments (e.g., using Azure CLI on Ubuntu) alongside PowerShell examples.
- Clarify which tools are cross-platform and recommend them for both Windows and Linux users.
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 examples or mentioning Linux scripting patterns (such as Bash or shell scripts). The step-by-step artifact creation walkthrough exclusively uses Windows artifacts and scripts, and the sample commands and folder structures are all Windows-centric. Although the documentation mentions that both Windows and Linux are supported, practical guidance and examples for Linux are missing.
Recommendations
- Add parallel Linux examples using Bash or shell scripts, including sample artifact definition files and install commands.
- Show how to use Linux package managers (e.g., apt, yum) in artifact scripts, similar to the Chocolatey example for Windows.
- Provide a walkthrough for creating a Linux artifact, including downloading and customizing a Linux-based artifact from the public repository.
- Ensure screenshots and folder structures include Linux artifacts and scripts (e.g., .sh files) alongside Windows examples.
- Explicitly mention Linux scripting patterns and tools when describing artifact creation and usage.
- Balance the order of presentation so that Windows and Linux are treated equally, rather than Windows examples appearing first or exclusively.
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 page provides detailed instructions for deleting lab VMs and labs in Azure DevTest Labs, with automation examples exclusively using PowerShell scripts. No Linux shell (Bash, CLI) or cross-platform automation examples are provided, and PowerShell is presented as the sole scripting method for bulk VM deletion. The page implicitly favors Windows users by omitting Linux-native tools and examples.
Recommendations
- Add equivalent Azure CLI (az) examples for automating VM and lab deletion, which are cross-platform and commonly used on Linux and macOS.
- Explicitly mention that PowerShell is available on Linux and macOS, but also provide Bash or shell script alternatives for users who prefer native Linux tooling.
- Include guidance or links to documentation for using REST API or SDKs (Python, Node.js) to perform these operations, ensuring broader platform coverage.
- Reorder or parallelize automation sections to present both PowerShell and Linux-friendly options side by side, rather than PowerShell-only.
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 subtle Windows bias. It mentions running PowerShell scripts and Azure CLI as integration options, but lists PowerShell before Azure CLI, implying a preference for Windows tooling. There are no explicit examples or references to Linux shell scripting, Linux-based build agents, or cross-platform considerations. The lack of Linux-specific examples or parity in scripting and tool mentions suggests a bias toward Windows environments.
Recommendations
- Explicitly mention Bash or Linux shell scripting alongside PowerShell when discussing automation options.
- Provide examples of integrating DevTest Labs with CI/CD pipelines using Linux-based build agents and scripts.
- Clarify that Azure CLI and REST API calls can be performed from any platform, including Linux and macOS.
- Add references to Linux tools and workflows where appropriate, ensuring equal visibility and guidance for non-Windows users.
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 demonstrates a strong Windows bias by exclusively using PowerShell for all examples and instructions. There are no references to Linux-native tools, Azure CLI, Bash, or cross-platform scripting. The installation instructions and all code samples assume the use of Azure PowerShell, which is most commonly used on Windows and is less familiar to Linux users. No equivalent Linux or Azure CLI examples are provided, and Windows-centric patterns (such as 'PS C:\>' prompts) are used throughout.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include Bash script samples for common tasks, such as role assignment and user lookup.
- Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, or link to cross-platform installation guides.
- Provide guidance on how to perform these tasks using the Azure Portal (web UI), which is platform agnostic.
- Reorder sections or add notes to clarify that these operations can be performed on any OS, not just Windows.
Devtest Labs
Troubleshoot Artifacts on Lab Virtual Machines
...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.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 in several ways: troubleshooting examples and commands are provided exclusively for Windows (e.g., PowerShell commands, Windows file paths, and use of File Explorer), with Linux equivalents either missing or relegated to external links. Windows-specific tools and patterns (such as Command Prompt, File Explorer, and Windows log locations) are described in detail, while Linux troubleshooting steps are not directly included. The structure and flow of the document present Windows guidance first and most prominently.
Recommendations
- Add equivalent Linux troubleshooting steps and examples directly in the documentation, not just as external links.
- Provide Azure CLI or Bash command examples alongside PowerShell commands for checking VM artifact status.
- Include Linux file paths and log locations for CSE and VM Agent troubleshooting, with screenshots or terminal output.
- Describe how to run and debug artifact installation scripts on Linux VMs, including common issues and solutions.
- Ensure parity in guidance for both Windows and Linux users throughout the document, presenting both platforms equally.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure DevTest Labs scenarios demonstrates a Windows bias in several ways. Windows-specific tools (e.g., PowerShell, Visual Studio, Fiddler) and examples are mentioned exclusively or before Linux equivalents. Automation and scripting references focus on PowerShell, with no mention of Bash or Linux shell alternatives. VM creation examples and quickstarts are labeled as 'create-lab-windows-vm', and there are no explicit Linux VM creation examples or references to Linux-specific tools or patterns. Artifact examples and customization options are Windows-centric, and Active Directory domain join is mentioned without reference to Linux identity solutions.
Recommendations
- Add Linux-focused examples for VM creation, including quickstarts and templates for common Linux distributions.
- Include Bash or Azure CLI scripting examples alongside PowerShell for automation tasks.
- Mention and provide examples of Linux tools and developer environments (e.g., VS Code, Git, Python, Node.js) in artifact and customization sections.
- Clarify that DevTest Labs supports both Windows and Linux environments, and provide parity in documentation for configuration, policy management, and automation.
- Reference Linux identity management options (e.g., LDAP, Kerberos) alongside Active Directory domain join artifacts.
- Ensure that links and diagrams do not exclusively reference Windows scenarios or tools.
Devtest Labs
Deploy Azure DevTest Labs (Enterprise Reference Architecture)
...les/devtest-labs/devtest-lab-reference-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: remote desktop gateway (a Windows-centric solution) is mentioned as the primary method for remote access, with no mention of Linux alternatives (such as SSH or Linux jump hosts). PowerShell is listed first among automation tools, and there are no Linux-specific examples or references to Linux-native tools for VM management or connectivity. The documentation assumes RDP as the default remote access protocol, which is primarily used for Windows VMs.
Recommendations
- Include examples and guidance for Linux VM management, such as SSH access and Linux-based jump hosts.
- Mention Linux-native automation tools (e.g., Bash scripts, Ansible) alongside PowerShell and Azure CLI.
- Provide parity in remote access solutions, such as describing how to set up SSH gateways or bastion hosts for Linux VMs.
- When discussing automation, alternate or balance examples between PowerShell and Bash/Azure CLI.
- Explicitly state that DevTest Labs supports both Windows and Linux VMs, and link to documentation for Linux-specific scenarios.
Devtest Labs
Upload a VHD file to lab storage by using Storage Explorer
...-labs/devtest-lab-upload-vhd-using-storage-explorer.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 CLI method for obtaining the storage account name, with screenshots and instructions focused on PowerShell usage. There are no equivalent examples or instructions for Linux users (e.g., using Bash, Azure CLI, or other Linux-native tools) to obtain the storage account name. The workflow implicitly assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in the initial steps.
Recommendations
- Add instructions and screenshots for obtaining the storage account name using Azure CLI (az commands) on Linux/macOS.
- Include references to Bash or other Linux-native shell environments alongside PowerShell, especially when describing command-line operations.
- Ensure that all steps involving command-line interaction have both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) examples.
- Clarify that Storage Explorer is cross-platform, and provide platform-specific guidance where workflows differ.
Devtest Labs
Create and deploy labs with Azure Resource Manager (ARM) templates
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server VM deployment in quickstart examples, heavily referencing PowerShell for automation and scripting, and omitting explicit Linux VM deployment examples or Linux-specific automation workflows. The use of Windows-centric tools and instructions (such as PowerShell) is prevalent, while Linux alternatives (such as Bash scripting or Linux VM templates) are not mentioned or provided.
Recommendations
- Include explicit examples for deploying Linux VMs using ARM templates, both in quickstart and automation sections.
- Provide automation instructions using Bash and Azure CLI, with sample scripts for Linux environments.
- Reference Linux VM base images and templates alongside Windows Server examples in all relevant sections.
- Add links to Linux-focused documentation and GitHub samples, ensuring parity with Windows/PowerShell resources.
- Balance the mention of PowerShell and CLI, and clarify cross-platform usage where possible.
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 page demonstrates some Windows bias: the first VM creation example is for a Windows image, and Windows-based images are described before Linux equivalents. Windows tools and patterns (e.g., Remote Desktop, PowerShell-specific syntax) are mentioned before or alongside Linux options, sometimes with more detail. PowerShell usage is explicitly called out, with special notes about escaping characters, while Bash is mentioned second. Artifact examples include both Linux and Windows, but sample output highlights a Windows artifact.
Recommendations
- Provide Linux-based VM creation examples before or alongside Windows examples to balance visibility.
- Ensure Linux connection methods (SSH) are described with equal prominence and detail as Windows (RDP).
- Include Bash examples and notes before or alongside PowerShell, not after.
- Show sample outputs for both Linux and Windows artifacts, or use neutral examples.
- Review ordering of examples and explanations to avoid consistently prioritizing Windows tools or patterns.
Devtest Labs
Extend Azure DevTest Labs with Azure Functions
...es/devtest-labs/extend-devtest-labs-azure-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Visual Studio is presented as the primary development environment, with no mention of cross-platform alternatives. PowerShell is referenced for service principal creation, and the sample scenario focuses on applying Windows Update artifacts to VMs. There are no examples or guidance for Linux VM management, nor are Linux development tools or workflows (such as VS Code, CLI, or Linux shell scripting) discussed.
Recommendations
- Include equivalent Linux examples for VM management, such as applying updates to Linux VMs (e.g., using apt or yum artifacts).
- Provide instructions for building and deploying the sample using cross-platform tools like VS Code, Azure CLI, or GitHub Actions.
- Add references and examples for Linux shell scripting or Bash when discussing service principal creation and automation.
- Highlight parity in artifact application by showing how to apply both Windows and Linux update artifacts.
- Clarify that Azure Functions development and deployment can be performed on Linux and macOS, not just Windows.
- Offer sample code and walkthroughs for PowerShell and Bash, or other Linux-friendly scripting languages.
Devtest Labs
Import virtual machines from another lab
...vtest-labs/import-virtual-machines-from-another-lab.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 detailed instructions and examples for PowerShell (a Windows-centric tool) and referencing a PowerShell script as the primary method for importing VMs. There are no equivalent examples or scripts for Linux shells (e.g., Bash), nor is there mention of cross-platform alternatives. The PowerShell method is presented before the REST API, reinforcing the Windows-first approach.
Recommendations
- Provide equivalent Bash or Azure CLI examples/scripts for Linux and macOS users.
- Explicitly mention that PowerShell Core is cross-platform if relevant, and clarify compatibility.
- Reorder sections or add a note to indicate that both Windows and Linux users can use the REST API equally.
- Reference Linux tools or workflows where appropriate, such as curl for REST API calls or Azure CLI commands.
- Add a table or section comparing available import methods for different platforms.
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 page demonstrates a Windows bias through the exclusive use of PowerShell commands and references to Windows-centric tools (e.g., AzCopy with PowerShell, OS disk swap article for Windows VMs). Windows VM configuration examples are presented before Linux equivalents, and Linux-specific instructions are minimal or absent. There are no CLI/bash examples, and Linux workflows are not described in detail.
Recommendations
- Provide equivalent CLI/bash commands for all PowerShell examples, especially for disk operations and AzCopy usage.
- Include explicit instructions for Linux users, such as how to swap OS disks on Linux VMs and reference the appropriate documentation.
- Present Linux VM configuration examples alongside or before Windows examples to ensure parity.
- Mention cross-platform tools and clarify when steps are OS-agnostic or require OS-specific handling.
- Add notes or sections highlighting differences or additional steps for Linux environments where applicable.
Devtest Labs
Azure DevTest Labs usage across multiple labs and subscriptions
...abs/report-usage-across-multiple-labs-subscriptions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell-based solutions and examples, mentioning Windows-centric tools (PowerShell Az.Resource module, Power BI, SQL Server) before or instead of Linux alternatives. There are no explicit Linux CLI or Bash examples, and Linux-friendly tools and workflows are not discussed or are mentioned only generically.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for exporting resource usage.
- Explicitly mention cross-platform compatibility of Azure Functions and Azure Automation, and provide Python or Bash sample code.
- Include Linux-friendly visualization tools (e.g., Grafana) alongside Power BI.
- Highlight storage solutions that are platform-agnostic or Linux-preferred, such as PostgreSQL or open-source databases.
- Add notes or sections clarifying how Linux users can perform each step without relying on PowerShell or Windows-only tools.