Devtest Labs

97
Total Pages
43
Linux-Friendly Pages
54
Pages with Bias
55.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (76)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deliver-proof-concept.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows client OS access and licensing (Windows 10/8.1, MSDN, Enterprise Dev/Test subscription) in the Azure subscription section, with no mention of Linux equivalents or licensing. The examples and prerequisites focus on Windows tools and Microsoft-centric collaboration platforms (Visual Studio, Teams, SharePoint) without referencing Linux or open-source alternatives. There are no explicit Linux or cross-platform examples for VM usage, remote access, or DevTest Labs scenarios.
Recommendations:
  • Include information about using Linux-based VMs in DevTest Labs, including licensing and Marketplace image options.
  • Provide examples or references for connecting to Linux VMs (e.g., SSH instructions, Linux remote desktop options) alongside RDP/Windows examples.
  • Mention open-source or cross-platform collaboration tools (e.g., GitHub, GitLab, Slack, Mattermost) in addition to Microsoft Teams, SharePoint, and Azure Repos.
  • Clarify that DevTest Labs supports both Windows and Linux environments, and provide links to relevant Linux documentation.
  • Balance the order of presentation so that Linux options are mentioned alongside or before Windows options where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/connect-environment-lab-virtual-network.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page provides an ARM template example that exclusively references Windows Server images and OS versions, with no mention of Linux options or examples. The parameters and variables are all tailored to Windows (e.g., 'MicrosoftWindowsServer', 'WindowsServer', and specific Windows Server versions), and there is no guidance or parity for deploying Linux-based environments.
Recommendations:
  • Include Linux image options in the ARM template, such as Ubuntu, CentOS, or other popular distributions.
  • Add a parallel example or section demonstrating how to connect a Linux VM to the lab's VNet, including relevant parameters and variables.
  • Mention both Windows and Linux scenarios in the introductory and instructional text to ensure cross-platform applicability.
  • Provide guidance or links for customizing the template for Linux environments, including admin username conventions and SSH key authentication.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-get-started.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exhibits several signs of Windows bias. PowerShell is the only scripting example mentioned for automation (e.g., deleting all VMs), and adding users is described via the Azure portal or PowerShell, with no mention of Bash, CLI, or Linux-native automation. Creation and deployment examples (Bicep, ARM, Terraform) are linked with filenames referencing Windows VMs, and there are no explicit Linux VM creation examples. Artifact/tool examples (e.g., Visual Studio, Fiddler) are Windows-centric, and Windows terminology (Active Directory domain join) is highlighted without Linux equivalents. Linux scenarios, tools, and automation methods are not given equal prominence or examples.
Recommendations:
  • Include Linux-focused examples for VM creation, such as ARM/Bicep/Terraform templates specifically for Linux VMs.
  • Provide automation examples using Azure CLI and Bash scripts, not just PowerShell.
  • Mention and link to Linux-native tools and artifacts (e.g., VS Code, Git, common Linux packages) alongside Windows tools.
  • Ensure artifact and environment customization examples include Linux scenarios (e.g., joining to LDAP, installing Linux software).
  • Balance references to Windows and Linux in both text and linked resources, and avoid Windows-first naming in example filenames.
  • Explicitly mention that all features are available for both Windows and Linux, and provide parallel instructions where differences exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides instructions for creating Generation 2 VMs in Azure DevTest Labs exclusively through the Azure portal UI, with no mention of OS-specific tools, commands, or examples. However, it omits any discussion or examples of connecting to or managing Linux-based VMs, such as SSH access, Linux username conventions, or Linux-specific post-deployment steps. The documentation is neutral in terms of not explicitly favoring Windows, but it lacks Linux parity in connection and usage guidance.
Recommendations:
  • Include explicit examples for connecting to both Windows (using RDP) and Linux (using SSH) VMs after deployment.
  • Mention Linux username conventions and any differences in credential requirements.
  • Provide guidance or links for post-deployment configuration steps for Linux VMs, such as installing packages or configuring SSH keys.
  • Add screenshots or instructions that show Linux VM options and settings where they differ from Windows.
  • Clarify that the process applies equally to both Windows and Linux images, and highlight any OS-specific considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-vm.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation demonstrates a Windows-first bias by using a Windows 11 Pro image as the default example for VM creation, without mentioning or illustrating Linux-based images. Additionally, the only explicit script-based workflow for copying VMs into a lab uses a PowerShell script, with no Linux or cross-platform alternative provided. There are no Linux-specific instructions, screenshots, or examples, and the documentation does not mention SSH or Linux authentication methods, focusing instead on password and Key Vault secrets typical for Windows environments.
Recommendations:
  • Include Linux-based VM creation examples alongside or before Windows examples, such as using Ubuntu or other popular Linux distributions.
  • Provide equivalent Linux command-line instructions (e.g., Bash scripts or Azure CLI examples) for tasks currently shown only with PowerShell, such as copying VMs into a lab.
  • Mention Linux authentication options (e.g., SSH keys) in the basic settings section, and update screenshots to reflect both Windows and Linux VM creation flows.
  • Clarify that both Windows and Linux images are supported and highlight any differences in configuration steps.
  • Ensure that artifact examples and repository links include Linux-relevant artifacts and not just Windows-centric tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-store-secrets-in-key-vault.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page refers to 'passwords for your Windows VMs' and 'public SSH keys for your Linux VMs', but all subsequent examples and screenshots are generic and do not provide platform-specific guidance. However, the initial mention of Windows passwords before Linux SSH keys suggests a subtle 'windows_first' bias. There are no Linux-specific examples or screenshots, and no mention of Linux command-line tools or workflows, indicating a lack of Linux parity.
Recommendations:
  • Provide explicit Linux-focused examples, such as how to use secrets for Linux VM provisioning (e.g., using secrets for SSH keys or environment variables).
  • Include screenshots or command-line instructions relevant to Linux users, such as using the Azure CLI or bash scripts.
  • Ensure that Linux use cases (e.g., storing and retrieving SSH keys) are described with equal prominence and detail as Windows password scenarios.
  • Where possible, alternate the order of Windows and Linux references, or present them together, to avoid implicit prioritization.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-redeploy-vm.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page focuses on redeploying VMs in Azure DevTest Labs with a clear emphasis on Windows-based VMs, mentioning remote desktop connection and troubleshooting for Windows VMs. There are no references to Linux VMs, SSH connectivity, or Linux-specific troubleshooting, and all examples and terminology are Windows-centric.
Recommendations:
  • Include references to Linux-based VMs and scenarios where redeployment may help (e.g., SSH connection issues).
  • Mention both RDP (for Windows) and SSH (for Linux) as common remote access methods that may require redeployment troubleshooting.
  • Add examples or notes for Linux users, such as what to do if SSH access fails and how redeployment affects Linux VMs.
  • Ensure that language is inclusive of both Windows and Linux VM users throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/configure-lab-remote-desktop-gateway.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows bias. All code examples and automation scripts are provided in PowerShell, with no Linux shell or cross-platform alternatives. The setup process relies on Windows-specific tools (such as Internet Information Server (IIS), PowerShell scripts, and .msi installers), and references to Windows Remote Desktop Services are predominant. There are no instructions or examples for configuring or accessing the gateway from Linux or macOS clients, nor are there alternatives for Linux-based gateway hosts. The only mention of cross-platform access is a brief reference to Azure Bastion, but the main flow is Windows-centric.
Recommendations:
  • Provide equivalent Bash/CLI examples for certificate creation, file encoding, and deployment steps, so Linux and macOS users can follow along.
  • Include instructions for connecting to the remote desktop gateway from Linux and macOS clients (e.g., using FreeRDP, Remmina, or rdesktop).
  • Document whether Linux-based gateway hosts are supported, and if so, provide setup instructions using open-source RDP gateway solutions.
  • Mention and, if possible, provide automation scripts in cross-platform languages (e.g., Python, Bash) in addition to PowerShell.
  • Clarify any Windows-only requirements early in the documentation, and suggest Azure Bastion or other cross-platform alternatives more prominently for non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deliver-proof-concept.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows client operating systems and Windows-specific tools (e.g., Visual Studio, MSDN, Windows 10/8.1) in the Azure DevTest Labs proof of concept process. There is a notable absence of Linux-specific examples, tools, or guidance, and Windows is mentioned first and more frequently in subscription and OS discussions. No Linux scenarios or equivalent subscription/OS guidance are provided.
Recommendations:
  • Include explicit examples and guidance for deploying and managing Linux VMs in Azure DevTest Labs, such as referencing popular Linux distributions and their use cases.
  • Mention Linux-compatible subscription options and clarify how Linux users can leverage DevTest Labs, including any cost or licensing differences.
  • Provide parity in tooling recommendations, such as mentioning GitHub, GitLab, or other cross-platform collaboration tools alongside Azure Repos and Visual Studio.
  • When discussing remote access, include Linux-specific methods (e.g., SSH from Linux/macOS terminals) and highlight any differences in setup.
  • Balance references to Windows and Linux throughout the documentation, ensuring that Linux is not omitted or always mentioned second.
  • Add Linux-focused proof-of-concept plan examples or case studies to illustrate cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-concepts.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific resources and tools before or instead of Linux equivalents. For example, the only direct link for more information about Azure VMs is to the 'Windows virtual machines in Azure' page, with no mention or link to Linux VMs. Additionally, in the artifacts section, only Windows-centric tools (like Visual Studio and Fiddler) are mentioned as examples, with no Linux alternatives provided. There are no PowerShell-specific examples, but the overall framing and examples prioritize Windows environments.
Recommendations:
  • Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
  • Provide Linux-specific examples alongside Windows ones, especially when discussing artifacts or tools (e.g., mention installing Git, Apache, or VS Code as Linux artifact examples).
  • When listing tools or software in examples, ensure parity by including both Windows and Linux options.
  • Review all example links and ensure they are not Windows-exclusive unless the context is specifically about Windows.
  • Consider adding a section or callout that explicitly addresses support for both Windows and Linux environments in DevTest Labs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-alerts.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to create activity log alerts using the Azure Portal GUI, with no mention of command-line or scripting alternatives. There are no examples using PowerShell, Azure CLI, or any platform-specific tools. However, the lack of Azure CLI (cross-platform) or Linux-specific instructions means Linux users do not see parity with Windows users who may be more accustomed to GUI or PowerShell workflows.
Recommendations:
  • Add step-by-step instructions for creating activity log alerts using the Azure CLI, which is cross-platform and widely used on Linux.
  • Include example scripts for automating alert creation, highlighting both PowerShell (for Windows) and Bash (for Linux/macOS) usage.
  • Explicitly mention that the Azure Portal is accessible from any OS, but provide parity by showing how to accomplish the same tasks from the command line.
  • Link to documentation on using Azure CLI and ARM templates for alert rule creation, to support automation and Linux-first workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-dev-ops.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a subtle Windows bias by referencing PowerShell scripts and Azure CLI as the primary means of automation, without mentioning or providing examples for Linux shell scripting or tools. The phrase 'executing PowerShell scripts, or using Azure CLI' places PowerShell first, reinforcing a Windows-centric approach. There are no explicit Linux shell (bash) examples or mentions of Linux-native tools, and the documentation does not clarify cross-platform compatibility or provide parity for Linux users.
Recommendations:
  • Explicitly mention and provide examples for both PowerShell and bash scripting when discussing automation and scripting tasks.
  • Clarify that Azure CLI and REST APIs are cross-platform and can be used from Linux, macOS, and Windows.
  • Include Linux-specific guidance or examples (e.g., bash scripts, Linux build agents) alongside Windows examples.
  • Avoid listing Windows tools (PowerShell) before cross-platform or Linux tools unless there is a technical reason.
  • Add a section or note on how Linux users can integrate with DevTest Labs in CI/CD pipelines, including any prerequisites or differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-auto-shutdown.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing 'Windows Plan' as the default in Logic Apps creation, mentioning Office 365 Outlook as the email integration example, and not providing any Linux-specific or cross-platform command-line or scripting alternatives. There are no examples or guidance for Linux users, and the documentation assumes use of Windows-centric tools and workflows.
Recommendations:
  • When describing Logic Apps creation, clarify that the 'Windows Plan' is not required for all scenarios and mention Linux hosting options if available.
  • Provide alternative examples for integrating with non-Microsoft email clients (e.g., Gmail, generic SMTP) and clarify that Office 365 Outlook is just one option.
  • Include command-line or scripting examples (such as using Azure CLI or Bash scripts) for configuring autoshutdown, in addition to portal-based instructions.
  • Explicitly state that the instructions are platform-agnostic where possible, or provide parallel steps for Linux/macOS users if there are differences.
  • Review screenshots and terminology to ensure they do not assume a Windows environment unless absolutely necessary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation is heavily biased towards Windows users. It explicitly states that AzCopy is a Windows-only utility, provides only Windows Command Prompt and PowerShell instructions, references Windows file paths, and omits any mention of Linux or cross-platform alternatives. There are no Linux or macOS examples or instructions, and the automation section continues to assume a Windows environment.
Recommendations:
  • Update the documentation to clarify that modern versions of AzCopy (v10 and later) are cross-platform and provide download links for Windows, Linux, and macOS.
  • Include Linux and macOS installation instructions and example commands (e.g., using bash or sh).
  • Avoid referencing only Windows-specific paths (like ProgramFiles(x86)); instead, provide generic or OS-specific installation paths.
  • Add PowerShell and bash (or shell) command examples side-by-side where relevant.
  • Remove or update the note stating AzCopy is Windows-only, as this is inaccurate for current versions.
  • Mention and link to cross-platform automation options (such as Azure CLI or REST API) where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-governance-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by highlighting Windows-specific benefits (such as special Dev/Test rates for Windows VMs and exclusive access to Windows 8.1/10 images), referencing Windows-centric tools (Visual Studio, Active Directory, Group Policy Objects), and omitting Linux-specific examples or equivalent tooling. There are no Linux or cross-platform command-line examples, nor are Linux-specific considerations or benefits discussed.
Recommendations:
  • Include examples and benefits for Linux-based virtual machines, such as mentioning special rates or available images for Linux distributions in DevTest Labs.
  • Reference Linux identity and configuration management tools (e.g., Azure AD for Linux, Linux group policies, or configuration management with Ansible/Chef/Puppet) alongside Windows tools like Active Directory and Group Policy.
  • Provide parity in documentation by including Linux-focused scenarios, such as using SSH keys for access, Linux VM lifecycle management, and cost optimization for Linux workloads.
  • Add cross-platform command-line examples (e.g., Azure CLI, Bash scripts) in addition to or instead of Windows/PowerShell-centric instructions.
  • Mention Linux-specific security and compliance practices where relevant, such as SELinux/AppArmor, and how they can be integrated with DevTest Labs governance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page, while describing a cross-platform tool (Azure Storage Explorer), demonstrates Windows bias by referencing PowerShell as the primary CLI method for obtaining the storage account name, including screenshots and links specifically for PowerShell. There is no mention of Linux-native CLI alternatives (such as Azure CLI or Bash), and the only command-line workflow described is via PowerShell, which is most commonly associated with Windows. Additionally, the 'Upload a VHD using PowerShell' link is highlighted before any mention of other methods, reinforcing a Windows-centric workflow.
Recommendations:
  • Provide equivalent instructions and screenshots for obtaining the storage account name using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include a section or callout for Linux/macOS users, outlining how to perform the same steps without PowerShell.
  • When referencing command-line workflows, present both PowerShell and Azure CLI (or Bash) options, or default to Azure CLI for parity.
  • Avoid highlighting Windows-specific tools or workflows (like PowerShell) before cross-platform alternatives, or present them in parallel.
  • Explicitly state that all steps can be performed on Windows, Linux, or macOS, and provide any OS-specific notes as needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows Server VM examples, providing only Windows-based quickstart templates, and focusing heavily on Azure PowerShell for automation tasks. There is a lack of Linux-specific examples or guidance, and PowerShell is consistently mentioned as the primary automation tool, with no mention of Bash or Linux-native scripting. The documentation also references Windows tools and workflows before or instead of their Linux equivalents.
Recommendations:
  • Include Linux VM examples alongside Windows Server VM examples in quickstart and template sections.
  • Provide automation examples using Bash scripts and Azure CLI, not just PowerShell.
  • Reference Linux tools and workflows (e.g., Bash, shell scripting) where appropriate, and ensure parity in instructions.
  • Add links to Linux-specific documentation or quickstarts for deploying and managing labs with ARM templates.
  • Ensure that both Windows and Linux scenarios are covered equally in screenshots, walkthroughs, and sample templates.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-delete-lab-vm.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides only a PowerShell script for automating VM deletion, with no equivalent example for Linux users (e.g., Bash, Azure CLI). The automation section assumes use of PowerShell and Windows tooling, and does not mention or prioritize cross-platform or Linux-native options. All automation guidance is Windows-centric.
Recommendations:
  • Provide equivalent automation examples using Azure CLI (az) in Bash or shell scripts for Linux/macOS users.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if the example requires Windows-only PowerShell.
  • Add guidance or links for Linux/macOS users on how to perform the same tasks, ensuring parity in automation instructions.
  • Consider presenting Azure CLI or REST API examples before or alongside PowerShell to avoid Windows-first bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-troubleshoot-apply-artifacts.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation exhibits a strong Windows bias. Troubleshooting steps and examples are primarily or exclusively provided for Windows VMs, including detailed PowerShell commands, Windows file paths, and the use of Windows tools like File Explorer and Command Prompt. Linux troubleshooting is only referenced via external links, with no in-place examples or step-by-step guidance. The structure and flow of the document assume Windows as the default environment, with Linux support treated as an afterthought.
Recommendations:
  • Provide equivalent Linux troubleshooting steps and examples alongside Windows instructions, not just as external links.
  • Include Azure CLI and/or Bash examples in addition to PowerShell for cross-platform parity.
  • Show Linux file paths and log locations directly in the documentation, mirroring the detail given for Windows.
  • When referencing tools (e.g., File Explorer, Command Prompt), also mention Linux equivalents (e.g., terminal, file managers).
  • Ensure artifact script troubleshooting covers both Windows (batch/PowerShell) and Linux (shell scripts) scenarios.
  • Where possible, present Windows and Linux instructions in parallel sections or side-by-side for clarity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-shared-ip.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows-first bias by presenting Windows (RDP) connection instructions before Linux (SSH) instructions, and by providing a detailed, tool-specific workflow for Windows users (downloading a pre-configured RDP file) while offering only a generic SSH connection description for Linux users. There are no command-line examples or screenshots for Linux users, and the documentation references Windows tools (RDP) explicitly, with no mention of Linux equivalents or tools.
Recommendations:
  • Provide Linux/SSH connection instructions with explicit command-line examples (e.g., ssh user@host -p port) and screenshots where appropriate.
  • Present Windows and Linux instructions in parallel or in a neutral order, rather than always listing Windows first.
  • Mention common Linux SSH clients (e.g., OpenSSH, PuTTY) and provide guidance for their use, similar to the RDP instructions for Windows.
  • Ensure parity in detail and clarity between Windows and Linux connection steps, including downloadable configuration files or scripts if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is presented as the first and primary automation method, with detailed scripting examples. In the Azure CLI section, both Bash (Linux) and Windows command syntaxes are shown, but Windows batch syntax is given equal or more prominence than is typical for cross-platform parity. The use of Windows-specific tools and patterns (PowerShell, batch variables, REM comments) is evident, and Linux/Bash examples are not consistently prioritized or explained in greater detail.
Recommendations:
  • Present Azure CLI (Bash/Linux) examples before PowerShell or at least with equal prominence, as Azure CLI is cross-platform and more common in Linux environments.
  • In the Azure CLI section, provide Bash (Linux) syntax first, and clearly mark Windows batch syntax as an alternative for Windows users.
  • Avoid using Windows batch-specific comments (e.g., REM) in CLI examples unless also providing the Bash equivalent (e.g., # for comments).
  • Include more context or tips for Linux users, such as how to run scripts in typical Linux shells or integrate with Linux automation tools.
  • Consider adding a table or section summarizing the differences in command syntax between platforms to help users quickly find the relevant information.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/extend-devtest-labs-azure-functions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a strong Windows bias by exclusively using Visual Studio for building and deploying the sample, referencing only C# and PowerShell implementations, and providing instructions and screenshots solely for Windows tools and workflows. There are no Linux or cross-platform alternatives mentioned for development, deployment, or testing. The sample scenario also focuses on applying Windows Update artifacts, with no mention of Linux VM management or equivalent artifacts.
Recommendations:
  • Provide equivalent instructions for developing, building, and deploying the sample using cross-platform tools such as VS Code, Azure CLI, or the Azure Functions Core Tools.
  • Include Linux-based examples, such as managing Linux VMs in DevTest Labs or applying Linux-specific artifacts.
  • Offer sample code in additional languages (e.g., Python, JavaScript) that are commonly used in cross-platform environments.
  • Add screenshots and step-by-step instructions for Linux/macOS environments, not just Windows/Visual Studio.
  • Reference automation and scripting options that work natively on Linux (e.g., Bash scripts, Azure CLI) alongside or before PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/test-app-azure.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily oriented toward Windows environments. It assumes the use of Visual Studio (primarily a Windows tool), requires a Windows-based DevTest Labs VM, and only provides instructions and screenshots for Windows workflows (e.g., File Explorer, RDP). There are no examples or guidance for Linux-based VMs, nor for using cross-platform tools or workflows.
Recommendations:
  • Include instructions and examples for publishing and accessing apps from Linux-based DevTest Labs VMs.
  • Provide alternative workflows using cross-platform tools (e.g., VS Code, command-line publishing with dotnet CLI).
  • Add guidance for mounting Azure file shares on Linux (using SMB or NFS) and accessing files via Linux file managers or terminal.
  • Balance screenshots and step-by-step instructions to cover both Windows and Linux scenarios.
  • Explicitly mention support for Linux-based VMs in the prerequisites and throughout the documentation, or clarify if only Windows is supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary scripting tool for deploying VMs with ARM templates, without mentioning or providing equivalent examples for Linux users (e.g., Azure CLI, Bash). No Linux-specific tools, commands, or patterns are discussed, and the only automation example is PowerShell-centric. This may disadvantage users working from Linux or cross-platform environments.
Recommendations:
  • Add equivalent Azure CLI (az) and/or Bash examples alongside PowerShell instructions for deploying VMs with ARM templates.
  • Explicitly mention that ARM template deployments can be performed from Linux, macOS, and Windows, and provide links to cross-platform tooling.
  • Where PowerShell is referenced, clarify that it is one of several supported automation options, and provide parity in troubleshooting steps for Linux-based workflows.
  • Consider including a section or callout for Linux/macOS users, highlighting any differences or additional considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/automate-add-lab-user.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples and cmdlet references, mentioning PowerShell tools and patterns before Azure CLI equivalents, and omitting explicit Linux/bash examples. The CLI section is less detailed, and there are no bash or cross-platform shell examples, which may disadvantage Linux or macOS users.
Recommendations:
  • Provide parallel bash/Azure CLI examples for all PowerShell commands, especially for tasks like obtaining ObjectId and deploying templates.
  • List Azure CLI instructions before or alongside PowerShell instructions to avoid a 'Windows-first' impression.
  • Include references to cross-platform tools (e.g., Azure CLI, REST API, or bash scripting) wherever PowerShell cmdlets are mentioned.
  • Clarify that Azure CLI and ARM templates are fully supported on Linux/macOS and provide explicit instructions for those platforms.
  • Expand the Azure CLI section to match the detail and guidance given in the PowerShell section, including parameter explanations and example outputs.
  • Where GUID generation is needed, show how to generate GUIDs using Linux tools (e.g., uuidgen) in addition to PowerShell's New-Guid.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/samples-cli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page, while describing Azure CLI scripts (which are cross-platform), shows evidence of Windows bias. The scripts are referenced as Bash scripts, but the code blocks are incorrectly labeled as 'powershell', which may confuse Linux users. Additionally, the first and only explicit VM creation example is for a Windows VM, with no mention of creating a Linux VM or providing a Linux-specific example.
Recommendations:
  • Correct the code block language tags from 'powershell' to 'bash' or 'azurecli' to accurately reflect the script content and avoid confusion for Linux users.
  • Include explicit examples for creating Linux VMs in addition to Windows VMs, or clarify that the scripts can be adapted for both.
  • Ensure that references to operating systems are balanced, and provide parity in documentation for both Windows and Linux scenarios.
  • If possible, add notes or links to documentation on how to adapt the scripts for Linux VM creation, including differences in authentication and image selection.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-auto-shutdown.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by referencing 'Windows Plan' as the default for Logic Apps and focusing on Office 365 Outlook integration for notifications, with no mention of Linux or cross-platform alternatives. There are no CLI, PowerShell, or Bash examples, but the only platform-specific reference is to Windows plans and Microsoft-centric tools, with no Linux or open-source equivalents discussed.
Recommendations:
  • Clarify whether the 'Windows Plan' is required for Logic Apps or if Linux-based plans are available and supported. If so, provide guidance for both.
  • Include examples or notes for integrating with non-Microsoft email clients (e.g., Gmail, SendGrid) for notifications, to support users on Linux or non-Windows platforms.
  • If possible, provide Azure CLI or REST API instructions for configuring autoshutdown, as these are cross-platform and can be used from Linux, macOS, or Windows.
  • Review screenshots and instructions to ensure they are not Windows-specific, or add notes/screenshots for Linux users where the experience may differ.
  • Explicitly state that the Azure portal and Logic Apps are accessible from any OS/browser, to reassure Linux and macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation mentions the Windows generalization tool (Sysprep) before the Linux equivalent (deprovision), and the parenthetical note '(Run sysprep)' for Windows appears before '(Run deprovision)' for Linux. However, both platforms are mentioned and linked, and no platform-specific commands or tools are otherwise favored.
Recommendations:
  • Present Windows and Linux options in parallel or alternate the order to avoid always listing Windows first.
  • Provide explicit step-by-step instructions or links for both Sysprep (Windows) and waagent deprovision (Linux), ensuring equal detail.
  • Include screenshots or examples for both Windows and Linux generalization processes if applicable.
  • Use neutral phrasing such as 'for Windows (Sysprep) or Linux (deprovision)' or 'for Linux (deprovision) or Windows (Sysprep)' to balance representation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/encrypt-disks-customer-managed-keys.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively describes how to configure disk encryption using the Azure Portal UI, with terminology and navigation patterns that are most familiar to Windows users. There are no examples or instructions for performing these tasks using command-line tools such as Azure CLI, PowerShell, or Bash scripts, nor is there any mention of Linux-specific workflows or considerations. This may disadvantage Linux users or those who prefer automation and cross-platform scripting.
Recommendations:
  • Add step-by-step instructions for configuring disk encryption using Azure CLI, which is cross-platform and widely used by both Windows and Linux users.
  • Include PowerShell examples for users who prefer scripting, but ensure parity by providing equivalent Bash/Azure CLI commands.
  • Mention and link to relevant documentation for automating these tasks on Linux systems, such as using ARM templates or REST APIs.
  • Clarify that the Azure Portal UI is platform-agnostic, but explicitly state that all steps can be performed from any OS with a supported browser.
  • Provide troubleshooting or validation steps that can be performed from both Windows and Linux VMs (e.g., using OS-native commands to check disk encryption status).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-repository.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed instructions and scripts exclusively using Azure PowerShell, with no equivalent Bash or Linux-native scripting examples. The deployment sections and automation guidance are PowerShell-centric, and there is no mention of Linux command-line tools or cross-platform scripting approaches. While the Azure CLI is briefly mentioned as an alternative for ARM template deployment, no CLI or Bash examples are actually provided, and all code samples and step-by-step automation are in PowerShell.
Recommendations:
  • Provide equivalent Azure CLI (az) and Bash script examples for adding artifact repositories, including full scripts and parameter explanations.
  • Include Linux/macOS-specific instructions for running scripts and managing authentication, such as using environment variables for tokens.
  • When listing deployment options (e.g., ARM template deployment), present Azure CLI and Bash examples before or alongside PowerShell examples, not after.
  • Clarify that all automation steps can be performed on Linux/macOS as well as Windows, and provide any necessary prerequisites or differences.
  • Add a section or tab for Linux users, mirroring the structure used for PowerShell, to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deploy-nested-template-environments.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation references Azure PowerShell before Azure CLI when describing deployment commands, and it mentions the Visual Studio Azure Resource Group project template as a related tool, which is primarily a Windows-centric development environment. There are no explicit Linux or cross-platform examples or tool recommendations, and the documentation does not mention Linux-specific workflows or editors.
Recommendations:
  • List Azure CLI before Azure PowerShell when describing deployment commands, as Azure CLI is cross-platform.
  • Include explicit Linux/macOS command-line examples for deploying templates, such as bash scripts or CLI usage.
  • Mention cross-platform editors and tools (e.g., VS Code, Git) alongside or instead of Visual Studio.
  • Add a section or note highlighting that all steps can be performed from Linux/macOS environments using Azure CLI and other cross-platform tools.
  • Provide links to documentation or tutorials that use Linux/macOS environments for ARM template deployment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 examples for Linux users (e.g., Azure CLI, Bash). The prerequisites and automation sections focus exclusively on PowerShell, and the portal instructions do not clarify cross-platform considerations. There is no mention of Linux-native tooling or scripting approaches, and the only command-line automation path described is via PowerShell, which is traditionally associated with Windows environments.
Recommendations:
  • Add equivalent Azure CLI and/or Bash examples for adding artifacts to VMs, ensuring Linux users have clear, native instructions.
  • In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported automation tools, with links to installation and usage guides for each.
  • Where scripting is discussed, provide both PowerShell and Bash/CLI scripts side-by-side or in tabs, so users on any platform can follow along.
  • Clarify in the introduction and relevant sections that both Windows and Linux VMs and users are supported, and provide examples that reflect this parity.
  • If certain features are only available via PowerShell, explicitly state this and provide workarounds or alternatives for Linux users where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/automate-add-lab-user.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing extensive PowerShell examples and cmdlet references, mentioning PowerShell tools and patterns first and in greater detail, and omitting explicit Linux/bash shell examples. While Azure CLI is mentioned, the CLI example is brief and lacks parity with the PowerShell guidance. There is no discussion of Linux-native tools or scripting environments, and the workflow assumes familiarity with Windows/PowerShell conventions.
Recommendations:
  • Provide equivalent bash/Azure CLI examples for all PowerShell commands, including how to retrieve object IDs and deploy ARM templates from Linux/macOS environments.
  • List Azure CLI and bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Reference cross-platform tools (e.g., uuidgen for GUID generation) and explain how to perform prerequisite steps (like generating GUIDs or retrieving object IDs) in Linux/macOS shells.
  • Clarify that both PowerShell and CLI commands can be run on any OS, and provide guidance for installing and using Azure CLI and PowerShell Core on Linux/macOS.
  • Add notes or sections specifically addressing Linux/macOS users, including any differences in command syntax or environment setup.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/configure-lab-remote-desktop-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a strong Windows bias. All examples and scripts are provided in PowerShell, with no mention of Linux or cross-platform alternatives. The tooling and patterns referenced (e.g., IIS, RDGatewayFedAuth.msi, System Center VMM, RDP file workflow) are Windows-centric. There is no guidance for Linux-based remote desktop solutions or how to connect from Linux clients. The documentation assumes the use of Windows infrastructure and tools throughout.
Recommendations:
  • Provide equivalent instructions and scripts for Linux environments, such as using OpenSSL for certificate creation and Bash/Azure CLI for automation.
  • Include examples of connecting to lab VMs using open-source RDP clients available on Linux (e.g., xfreerdp, Remmina), and clarify token authentication compatibility.
  • Mention and, where possible, support Linux-based gateway solutions (such as xrdp or guacd) or clarify if only Windows gateways are supported.
  • When listing tools or scripts, present cross-platform or Linux options alongside Windows/PowerShell examples, not just after them.
  • Explicitly state any limitations or lack of support for Linux clients or servers, so users can plan accordingly.
  • Reference Azure Bastion as a cross-platform alternative more prominently, and provide a comparison table for remote access options across OSes.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/connect-environment-lab-virtual-network.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page provides only Windows-based examples for connecting an environment to a lab's VNet in Azure DevTest Labs. The sample ARM template exclusively references Windows Server images and does not mention or provide examples for Linux-based environments. There are no Linux OS options, publishers, or offers in the template, and no guidance is given for Linux users.
Recommendations:
  • Add Linux OS options (such as Ubuntu, CentOS, or other popular distributions) to the ARM template parameters and variables.
  • Include a Linux-based example in the documentation, showing how to deploy a Linux VM connected to the lab VNet.
  • Mention both Windows and Linux use cases in the scenario description to ensure parity.
  • Provide guidance or links for Linux-specific configuration or troubleshooting steps where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-environment-service-fabric-cluster.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation displays a Windows bias in several ways: Windows is the default OS for cluster VMs, certificate creation instructions are provided only for PowerShell (with a .ps1 script), and there are no equivalent Linux/bash examples or references to Linux tooling for certificate management. The documentation mentions that clusters can be created on Linux or Windows, but all concrete steps and scripts are Windows-centric.
Recommendations:
  • Provide Linux/bash equivalents for certificate creation, such as using OpenSSL, alongside the PowerShell example.
  • Explicitly mention that the .ps1 script is for Windows and offer a Linux alternative or link to Linux instructions.
  • When describing the OS selection, avoid making Windows the default or at least give equal prominence to Linux.
  • Include screenshots or CLI steps that demonstrate the process on a Linux system where applicable.
  • Reference Linux tools (e.g., bash, OpenSSL) in parallel with Windows tools (e.g., PowerShell, .ps1 scripts).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deliver-proof-concept.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by emphasizing Windows client operating systems, Windows-specific licensing (MSDN, Visual Studio subscriptions), and RDP as a primary remote access method. There is no mention of Linux-specific scenarios, tools, or licensing, and no examples are provided for Linux VM setup or access, despite Azure DevTest Labs supporting both Windows and Linux environments.
Recommendations:
  • Include explicit references to Linux VM support in DevTest Labs, both in prerequisites and example scenarios.
  • Provide guidance on using Linux images, including licensing and marketplace options.
  • Mention SSH as a primary remote access method for Linux VMs, and provide parity in remote access instructions (e.g., 'connect via RDP (for Windows) or SSH (for Linux)').
  • List Linux development/test scenarios alongside Windows scenarios in all relevant sections.
  • Reference open source tools and workflows (e.g., GitHub, GitLab, Jira, Slack) in addition to Microsoft tools for collaboration.
  • Add example proof-of-concept plans that include Linux-based teams or mixed OS environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-devtest-user.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively providing automation examples using Azure PowerShell, referencing only PowerShell and not Azure CLI or Bash. Prerequisites and instructions focus on PowerShell, and there are no examples or guidance for Linux/macOS users or for using cross-platform tools like Azure CLI. Microsoft account documentation links also point to Windows Server resources, further reinforcing the Windows-centric approach.
Recommendations:
  • Add equivalent Azure CLI examples for adding users to lab roles, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script snippets or instructions for Linux/macOS users where appropriate.
  • Reference Microsoft account documentation that is not Windows Server-specific, or provide alternative guidance for non-Windows environments.
  • In the prerequisites and tool installation sections, mention both Azure PowerShell and Azure CLI, and provide links and instructions for each.
  • Ensure that the order of presentation does not always place Windows/PowerShell first; consider alternating or presenting cross-platform methods before Windows-specific ones.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation demonstrates a Windows bias by using a Windows 11 Pro image as the example for VM creation, without mentioning or providing a Linux-based example. In the 'Copy existing Azure VMs into a lab' section, only a PowerShell script is referenced, with no mention of a Linux/CLI/bash alternative. The documentation also lists PowerShell before Azure CLI in the introductory paragraph, and does not provide parity in examples or tooling for Linux users.
Recommendations:
  • Include a parallel example using a popular Linux image (e.g., Ubuntu) when demonstrating VM creation, and note any Linux-specific settings or differences.
  • In the 'Copy existing Azure VMs into a lab' section, provide an equivalent Azure CLI or bash script example for Linux users, or at least reference one if available.
  • When listing automation options (PowerShell, CLI, ARM template), alternate or balance the order, or explicitly state that both Windows and Linux users are supported equally.
  • Where screenshots or instructions are OS-specific, clarify applicability or provide Linux alternatives.
  • Ensure artifact examples or references include both Windows and Linux use cases.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-attach-detach-data-disk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation focuses exclusively on using the Azure portal UI to attach and detach data disks, without providing any OS-specific (Windows or Linux) command-line examples. However, it omits any mention of post-attachment steps required inside the VM, such as mounting and formatting disks, which differ between Windows and Linux. This omission can disadvantage Linux users, as the process for making a new disk usable is not covered for either OS, but is especially critical for Linux where manual mounting is common.
Recommendations:
  • Add a section describing post-attachment steps for both Windows and Linux VMs, such as initializing, partitioning, and mounting the disk (for Linux, using fdisk/lsblk/mkfs/mount; for Windows, using Disk Management or PowerShell).
  • Provide example commands for both Linux (bash) and Windows (PowerShell) to guide users through making the new disk available inside the VM.
  • Explicitly mention that after attaching a disk in the Azure portal, further steps are required inside the VM, and link to relevant documentation for both OSes.
  • Ensure parity in instructions and examples for both Windows and Linux users throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-artifact-author.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples for artifact installation commands, referencing Windows-specific tools (such as Chocolatey), and using a sample artifact that is explicitly for Windows. There are no equivalent Linux shell script examples, nor is there a Linux-focused artifact sample or command. The guidance and screenshots are centered around Windows patterns, with Linux support mentioned only as an option in parameter values.
Recommendations:
  • Add parallel Linux examples throughout the documentation, such as showing a bash shell script artifact and corresponding 'commandToExecute' using 'bash' or 'sh'.
  • Include a sample artifactfile.json and script for a Linux VM (e.g., installing a package with apt or yum).
  • When referencing repositories or samples, provide both Windows and Linux artifact examples, or at least mention where Linux examples can be found.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., do not always show Windows first).
  • Mention Linux-specific tools or patterns (such as apt, yum, bash scripting) alongside Windows tools like PowerShell and Chocolatey.
  • Ensure screenshots and folder structures are not Windows-centric, or provide Linux equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-use-custom-lab.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation presents Windows connection methods (RDP) before Linux methods (SSH/CLI) and refers to Windows-specific tools (RDP) by name, while Linux connection options are mentioned second and less prominently. There are no explicit command-line examples for either OS, but the ordering and naming favor Windows.
Recommendations:
  • Present Linux and Windows connection options in parallel or in a neutral order (e.g., 'For Windows VMs, use RDP; for Linux VMs, use SSH or Azure CLI').
  • Provide explicit examples or links for both Windows and Linux connection methods with equal prominence.
  • Avoid listing Windows tools or patterns before Linux equivalents unless there is a technical reason.
  • Consider including screenshots or instructions for both OS types side by side where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-concepts.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by referencing Windows virtual machines and tools before or instead of Linux equivalents. The only direct link to VM documentation is for Windows VMs, and examples of artifacts mention Windows-specific tools like Visual Studio and Fiddler, with no mention of Linux tools or distributions. There are no Linux-specific examples, links, or references, and the documentation does not clarify that Linux VMs and artifacts are equally supported.
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., Git, Apache, NGINX, or other common Linux software).
  • Explicitly state that DevTest Labs supports both Windows and Linux VMs, and provide parity in examples and explanations.
  • When listing base images or custom images, mention both Windows and Linux options.
  • Ensure that any step-by-step guides or referenced templates include Linux scenarios alongside Windows ones.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-environment-from-arm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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-native examples. While the Azure CLI is briefly mentioned, all step-by-step automation is shown using PowerShell, and the script is written in a Windows-centric style. There are no Linux/Bash shell examples or references to cross-platform scripting approaches.
Recommendations:
  • Provide equivalent automation instructions and sample scripts using Azure CLI with Bash, suitable for Linux and macOS users.
  • Include explicit Bash/Linux command-line examples for deploying ARM templates and managing DevTest Labs environments.
  • Ensure that references to automation tools (PowerShell, CLI) are presented in parallel, with neither platform prioritized over the other.
  • Add notes or sections clarifying cross-platform compatibility and any OS-specific considerations.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is web-based and platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation page shows a moderate Windows bias. PowerShell is mentioned as an alternative method for creating custom images, and uploading VHDs via PowerShell is listed as a primary option. Windows-specific tools (PowerShell, sysprep) are referenced directly, while Linux equivalents (deprovision) are mentioned but with less prominence. The ordering of upload methods and examples tends to favor Microsoft/Windows tools, and there are no explicit Linux CLI or cross-platform examples (e.g., Bash, Azure CLI).
Recommendations:
  • Add explicit examples and links for using Azure CLI (az) and Bash scripts to upload VHDs and create custom images, ensuring parity with PowerShell instructions.
  • List Linux and cross-platform upload methods (e.g., AzCopy, Azure CLI) before or alongside Windows/PowerShell options to avoid implicit prioritization.
  • Provide more detailed guidance for Linux users, such as step-by-step instructions for preparing and uploading VHDs from Linux environments.
  • Where Windows-specific tools (like sysprep) are mentioned, ensure the Linux equivalent (deprovision) is described with equal detail and visibility.
  • Consider including screenshots or terminal output from Linux environments to balance the visual representation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-delete-lab-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides only a PowerShell script for automating VM deletion, with no equivalent Bash, Azure CLI, or Linux-friendly example. The automation section is Windows/PowerShell-centric, and there is no mention of cross-platform tools or alternatives for Linux/macOS users.
Recommendations:
  • Add an Azure CLI (az) example for deleting all VMs in a lab, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include Bash script examples or instructions for Linux users where automation is discussed.
  • Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows systems.
  • Ensure that any automation or scripting guidance is presented with parity for both Windows and Linux users, ideally showing both PowerShell and CLI/Bash alternatives side by side.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-dev-ops.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page references executing PowerShell scripts and REST APIs as ways to interact with Azure DevTest Labs in CI/CD pipelines, but does not mention or provide examples for Linux shell scripting or other Linux-native tools. The mention of PowerShell comes before Azure CLI, and there are no explicit Linux or cross-platform examples, which may give the impression of a Windows-centric workflow.
Recommendations:
  • Explicitly mention Bash/shell scripting as an option alongside PowerShell for automation tasks.
  • Provide examples using both PowerShell and Bash/Azure CLI to demonstrate cross-platform compatibility.
  • List Azure CLI before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Include references to Linux-based build agents and workflows in the context of DevTest Labs integration.
  • Ensure that all scripting and automation guidance is presented in a platform-neutral way, or with parallel examples for Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page describes how to create Generation 2 VMs in Azure DevTest Labs using the Azure portal, but does not provide any OS-specific examples or instructions. There is no explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, the documentation omits any discussion or examples related to Linux-specific considerations, such as SSH access, Linux username conventions, or Linux image selection, which are relevant for cross-platform parity.
Recommendations:
  • Add explicit notes or examples for creating both Windows and Linux Generation 2 VMs, including any differences in image selection or configuration.
  • Clarify how to set up authentication for Linux VMs (e.g., SSH keys vs. passwords) in the 'User name' and 'Password' sections.
  • Include screenshots or descriptions that show both Windows and Linux images in the image selection step.
  • Mention any Linux-specific Generation 2 VM limitations or requirements, if applicable.
  • Provide guidance on connecting to Linux VMs (e.g., using SSH) in addition to the generic 'Connect' instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exclusively uses PowerShell and Azure PowerShell cmdlets for all examples and instructions, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. All command-line examples are in PowerShell, and there is an explicit requirement to install Azure PowerShell. No Linux or macOS-specific guidance or parity is provided.
Recommendations:
  • Provide equivalent examples using Azure CLI, which is cross-platform and works on Windows, Linux, and macOS.
  • Include Bash script examples alongside PowerShell, or at least mention that the steps can be performed using Azure CLI on Linux/macOS.
  • Add a section or note clarifying that these tasks can also be accomplished on non-Windows platforms, and link to relevant Azure CLI documentation.
  • Rephrase instructions to avoid assuming the user is on Windows (e.g., avoid 'PS C:\>' prompts or reference to Windows file paths).
  • List both PowerShell and CLI approaches, or provide a table comparing the commands for both environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-redeploy-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page focuses on troubleshooting remote desktop connection issues, specifically referencing Windows-based VMs and RDP. There is no mention of Linux VMs, SSH, or Linux-specific troubleshooting scenarios, which may lead users to believe the redeploy feature is only relevant for Windows VMs.
Recommendations:
  • Include examples or scenarios for Linux VMs, such as troubleshooting SSH connectivity issues.
  • Clarify that the redeploy feature applies to both Windows and Linux VMs, if applicable.
  • Mention Linux-specific remote access methods (e.g., SSH) alongside RDP.
  • Add a note or section addressing common Linux VM redeployment use cases.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-get-started.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates several types of Windows bias. PowerShell is the only scripting example mentioned for automation (e.g., adding users, deleting VMs), with no reference to Bash, CLI, or Linux scripting alternatives. In the 'Lab creation' section, all code sample links reference Windows VMs (e.g., Bicep, ARM, Terraform templates for Windows), with no mention of Linux VM creation. Tools and artifacts examples are Windows-centric (e.g., Visual Studio, Fiddler), and Windows-specific patterns (Active Directory domain join) are referenced without Linux equivalents. Linux is only mentioned in passing, with no concrete examples or parity in instructions.
Recommendations:
  • Provide parallel examples for Linux VM creation using Bicep, ARM templates, and Terraform, and link to those alongside Windows examples.
  • Include automation instructions and scripts using Azure CLI and Bash, not just PowerShell.
  • Mention and provide examples of Linux tools and artifacts (e.g., installing common Linux development tools, editors, or agents).
  • When referencing domain join or other Windows-specific features, also mention Linux equivalents (e.g., joining to LDAP or using SSH keys).
  • Ensure that all user-facing instructions and quickstarts are available for both Windows and Linux scenarios, and present them with equal prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-hibernate-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exhibits a Windows bias by using Windows 11 Pro as the default example for VM creation, referencing 'Windows VM' in screenshots and instructions, and omitting any explicit mention or example of Linux-based VMs. There are no Linux-specific instructions, screenshots, or clarifications about hibernation support or differences for Linux VMs. The documentation also uses patterns and language (such as 'Connect' options) that are typically associated with Windows environments.
Recommendations:
  • Include explicit examples and screenshots for creating and managing Linux VMs with hibernation enabled.
  • Clarify whether hibernation is supported for Linux distributions, and if so, list supported versions and any caveats.
  • When referencing VM images, provide both Windows and Linux options (e.g., 'The following instructions use Windows 11 Pro or Ubuntu 22.04 LTS').
  • Avoid referring to 'Windows VM' in a way that implies exclusivity; use neutral terms or mention both Windows and Linux where appropriate.
  • If there are differences in the hibernation process or prerequisites for Linux VMs, document them clearly.
  • Ensure screenshots and instructions are balanced between Windows and Linux scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-shared-ip.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by presenting the Windows RDP connection method before the Linux SSH method, and by providing a detailed, step-by-step instruction for Windows users (including a pre-configured RDP file download), while Linux users are only given a brief description without a concrete SSH command example. There is also a lack of parity in actionable examples for Linux users.
Recommendations:
  • Present Windows and Linux instructions in parallel, or alternate which is presented first.
  • Provide explicit SSH command-line examples for Linux users (e.g., ssh username@contoso.westus3.cloudapp.azure.com -p 65013).
  • Include screenshots or step-by-step instructions for Linux SSH connections, similar to the RDP instructions for Windows.
  • Avoid assuming the user is on Windows; mention cross-platform tools where possible.
  • Clarify that SSH can be used from Windows, macOS, or Linux, and provide guidance for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-reference-architecture.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric tools and patterns, such as the Remote Desktop Gateway (RDP) and referencing Windows Server documentation. There are no examples or mentions of Linux-based remote access (e.g., SSH), nor are Linux administration tools or patterns discussed. Automation examples mention PowerShell first, and there is no parity in examples or guidance for Linux environments.
Recommendations:
  • Include Linux-based remote access options (e.g., SSH bastion hosts, Linux jump boxes) alongside or before Windows RDP solutions.
  • Reference Linux documentation and tools (such as OpenSSH, Linux firewall configuration) when discussing connectivity and security.
  • Provide automation examples using Bash scripts and Azure CLI, not just PowerShell.
  • Explicitly mention that DevTest Labs supports both Windows and Linux VMs, and provide Linux-specific considerations where relevant.
  • Balance references to Windows and Linux tools and patterns throughout the documentation to ensure cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-troubleshoot-apply-artifacts.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing detailed, step-by-step troubleshooting instructions and examples exclusively for Windows virtual machines, including PowerShell commands, Windows file paths, and screenshots of Windows tools (File Explorer, Command Prompt). Linux troubleshooting is only referenced via external links, with no in-page examples or equivalent walkthroughs. Windows tools and patterns are mentioned first and in detail, while Linux users are directed elsewhere.
Recommendations:
  • Provide parallel Linux examples for all troubleshooting steps, including equivalent Bash/CLI commands and Linux file paths.
  • Include screenshots or terminal output from Linux environments where Windows screenshots are shown.
  • Add in-page instructions for locating and inspecting Custom Script Extension logs on Linux VMs, not just a link.
  • Show how to check the Azure VM Agent status and logs on Linux, with sample log snippets.
  • Demonstrate how to run artifact installation scripts on Linux (e.g., using bash or sh), including how to handle script parameters and errors.
  • Ensure that references to tools (e.g., File Explorer, Command Prompt) are paired with their Linux equivalents (e.g., file managers, terminal).
  • When mentioning PowerShell or Windows-specific commands, immediately follow with the Linux/CLI equivalent, not just a reference link.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias. It explicitly states that AzCopy is a Windows-only utility, provides only Windows Command Prompt and PowerShell instructions and screenshots, and omits any Linux or cross-platform alternatives or examples. The instructions assume a Windows environment throughout, with no mention of how Linux or macOS users could perform the same tasks.
Recommendations:
  • Update the documentation to reflect that modern versions of AzCopy (v10 and above) are cross-platform and available for Windows, Linux, and macOS.
  • Provide Linux and macOS installation instructions and example commands (e.g., using bash shell).
  • Include screenshots or terminal examples from Linux environments where appropriate.
  • Avoid language that implies exclusivity to Windows unless it is truly the case; clarify version-specific limitations if any.
  • If PowerShell is referenced, also provide equivalent bash or shell commands for Linux/macOS users.
  • Link to cross-platform AzCopy documentation and downloads.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page, while stating that Azure Storage Explorer is cross-platform, demonstrates a Windows bias in several ways. It directs users to obtain the storage account name by following a workflow that explicitly references PowerShell and the 'Upload a VHD using PowerShell' link, with screenshots and instructions focused on the Windows Azure portal experience. There are no Linux- or macOS-specific examples, nor are alternative CLI-based workflows (such as using Azure CLI or azcopy) mentioned. The related content section also prioritizes PowerShell-based guidance.
Recommendations:
  • Provide explicit instructions or examples for Linux and macOS users, including screenshots where appropriate.
  • Include alternative workflows using Azure CLI or azcopy for users who may not use PowerShell or the Azure portal.
  • Avoid referencing PowerShell as the primary or only method for obtaining required information (such as the storage account name); instead, describe a platform-neutral method or provide parallel instructions for different OSes.
  • Balance related content links by including Linux/macOS/CLI-based documentation alongside PowerShell resources.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows Server VM examples, providing detailed PowerShell automation instructions, and referencing Windows-centric tools and workflows. There is a lack of Linux-specific examples or guidance, and Linux VM deployment is not mentioned alongside Windows. PowerShell is emphasized for automation, with no mention of Bash or Linux shell scripting alternatives.
Recommendations:
  • Include Linux VM deployment examples alongside Windows Server VM examples in the ARM quickstart section.
  • Provide equivalent Bash or Azure CLI scripts for automation tasks currently demonstrated only with PowerShell.
  • Reference Linux-compatible tools and workflows, such as Bash scripting, when discussing automation.
  • Ensure that instructions and screenshots are not Windows-specific, or provide Linux equivalents where appropriate.
  • Explicitly mention that ARM templates can be used to deploy both Windows and Linux VMs, and provide links to relevant Linux template samples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-vmcli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation page demonstrates a mild Windows bias by presenting the Windows VM creation example before the Linux example, and by referencing Windows-specific images and artifacts first. While both Windows and Linux scenarios are covered, Windows is consistently mentioned or exemplified before Linux, and Windows tools (such as Remote Desktop) are referenced alongside SSH, sometimes with more prominence.
Recommendations:
  • Alternate the order of examples so that Linux-based VM creation is shown before or alongside Windows-based examples.
  • Ensure parity in artifact examples by including both Windows and Linux artifacts in sample outputs and JSON snippets.
  • When referencing connection methods, present SSH (Linux) and RDP (Windows) in parallel, giving neither undue prominence.
  • Where possible, use neutral or cross-platform examples (e.g., generic images, admin credentials) unless a specific OS is being demonstrated.
  • Explicitly mention that all commands and procedures apply equally to both Windows and Linux VMs, and provide links to both Linux and Windows connection guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/extend-devtest-labs-azure-functions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows bias. All step-by-step instructions and screenshots are based on Visual Studio, a Windows-centric IDE, with no mention of cross-platform alternatives (e.g., VS Code, CLI-based deployment). The only code samples referenced are C# and PowerShell, both of which are traditionally Windows-first technologies. The walkthrough for creating a service principal lists Azure CLI, PowerShell, and Portal, but the rest of the guide assumes Visual Studio usage. There are no Linux/macOS-specific instructions, nor are there examples for deploying or developing the sample from non-Windows environments. The 'ApplyWindowsUpdateArtifact' function and artifact are Windows-specific, and there is no mention of Linux VM management or update artifacts.
Recommendations:
  • Provide equivalent instructions for developing, building, and deploying the sample using cross-platform tools such as Visual Studio Code, Azure CLI, and/or GitHub Actions.
  • Include Linux/macOS-specific steps for cloning, building, and deploying the Azure Functions sample.
  • Offer examples of managing Linux VMs in DevTest Labs, including applying Linux update artifacts, alongside the Windows Update example.
  • Reference and provide links to Linux-compatible tools and workflows, such as using the Azure CLI or VS Code for function development and deployment.
  • Add code samples or walkthroughs for Python or JavaScript Azure Functions, which are popular and cross-platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/how-to-move-labs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing PowerShell-based examples for disk migration and referencing Windows-specific tools and patterns (e.g., PowerShell, Windows VM with RDP) before Linux equivalents. The only command-line example for moving disks uses PowerShell, and while there is a brief mention of Linux VMs (with SSH port 22), there are no Linux shell (bash/CLI) examples for key steps such as using AzCopy or managing disks. The guidance for swapping OS disks links to a Windows/PowerShell article, with no Linux/CLI equivalent. The overall workflow assumes familiarity with Windows tools and environments, with Linux parity lacking in practical, step-by-step guidance.
Recommendations:
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for disk migration and AzCopy usage.
  • Include explicit Linux VM management steps and examples (e.g., swapping OS disks using Azure CLI or Bash).
  • When showing code snippets for VM network configuration, present Linux and Windows examples side by side, not with Windows first.
  • Reference both Windows and Linux documentation for advanced tasks (e.g., swapping OS disks) to ensure parity.
  • Review all instructions to ensure that Linux users are equally supported and not required to translate PowerShell or Windows-centric steps themselves.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-create.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a strong Windows bias by exclusively referencing Azure PowerShell scripts and PowerShell-based automation, without mentioning or providing examples for Linux shell scripts or cross-platform alternatives. The tools and patterns described (e.g., PowerShell, VSTS/DevOps extensions) are primarily Windows-centric, and there is no discussion of Linux-native scripting or automation options. No Linux or Bash examples are provided, and the documentation assumes the reader is using Windows tooling.
Recommendations:
  • Include equivalent Bash or Azure CLI script examples for Linux users alongside PowerShell scripts.
  • Explicitly mention cross-platform compatibility of the solution, and clarify which parts are Windows-specific.
  • Reference and link to Linux-friendly tools or extensions where available.
  • Rephrase sections to avoid assuming PowerShell is the only or primary automation method.
  • Add a section or note describing how Linux users can implement or adapt the image factory process.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/start-machines-use-automation-runbooks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exclusively uses PowerShell scripts and Azure Automation runbooks, which are Windows-centric tools. There are no examples or instructions for Linux users, such as Bash, Azure CLI, or Python runbooks. The workflow and tooling described are tailored for Windows environments, with no mention of Linux alternatives or parity.
Recommendations:
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux users.
  • Include instructions for creating and running Python runbooks in Azure Automation, which are cross-platform.
  • Mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.), and link to relevant Linux-friendly documentation.
  • Where possible, use cross-platform Azure modules (e.g., Az instead of AzureRM) and clarify their compatibility.
  • Add a section or note explicitly addressing Linux/macOS users and how they can achieve the same VM startup order using their preferred tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-save-distribute-custom-images.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-set-retention-policy-cleanup.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-set-up-devops-lab.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/import-virtual-machines-from-another-lab.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/network-isolation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/personal-data-delete-export.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/report-usage-across-multiple-labs-subscriptions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/resource-group-control.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/test-app-azure.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-create-custom-lab.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing only a Windows Server 2019 Datacenter example when adding a VM to the lab, without mentioning or illustrating how to create a Linux-based VM. There are no Linux-specific instructions, screenshots, or references to Linux images, tools, or patterns. The documentation implicitly assumes Windows as the default, which may mislead or disadvantage users seeking to deploy Linux environments.
Recommendations:
  • Include parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) in the 'Add a VM to the lab' section.
  • Explicitly mention that both Windows and Linux images are supported, and provide guidance on selecting a Linux base image.
  • Add notes or tips about Linux-specific configuration options (e.g., SSH key authentication, default usernames, artifact installation differences).
  • Where possible, use neutral language and examples that apply to both Windows and Linux, or provide side-by-side examples.
  • Reference documentation or quickstarts for deploying Linux VMs in DevTest Labs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-devtest-labs-build-release-pipelines.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation focuses exclusively on .NET Core and ASP.NET Core examples, which are traditionally associated with Windows environments, and does not provide any Linux-specific examples or mention Linux-based tools or patterns. There are no references to Linux shell scripts, Bash, or Linux VM configurations, nor are there any screenshots or instructions that address Linux users. The documentation implicitly assumes a Windows-centric workflow by defaulting to technologies and templates commonly used in Windows environments.
Recommendations:
  • Include parallel examples for Linux-based web apps (e.g., Node.js, Python, or Java on Linux App Service) alongside .NET Core examples.
  • Demonstrate how to configure and deploy to Linux VMs or Linux-based environments in DevTest Labs.
  • Add sample pipeline YAML or task configurations that use Bash scripts or Linux shell commands.
  • Explicitly mention that DevTest Labs and Azure Pipelines support both Windows and Linux environments, and provide links or references to Linux-specific documentation.
  • Show screenshots or UI flows that include Linux options (e.g., selecting Ubuntu or other Linux images in DevTest Labs).