Devtest Labs
99
Total Pages
40
Linux-Friendly Pages
59
Pages with Bias
59.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
334 issues found
Showing 176-200 of 334 flagged pages
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/automate-add-lab-user.md
...ob/main/articles/devtest-labs/automate-add-lab-user.md
High Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/configure-lab-remote-desktop-gateway.md
...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-environment-service-fabric-cluster.md
...test-labs/create-environment-service-fabric-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation 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).
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deliver-proof-concept.md
...ob/main/articles/devtest-labs/deliver-proof-concept.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-devtest-user.md
.../articles/devtest-labs/devtest-lab-add-devtest-user.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-vm.md
.../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-artifact-author.md
...n/articles/devtest-labs/devtest-lab-artifact-author.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-concepts.md
...lob/main/articles/devtest-labs/devtest-lab-concepts.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-environment-from-arm.md
...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed automation instructions and scripts exclusively for Azure PowerShell, with no equivalent Bash or Linux-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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-template.md
...n/articles/devtest-labs/devtest-lab-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-delete-lab-vm.md
...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
...blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md
...st-lab-grant-user-permissions-to-specific-lab-policies.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-get-started.md
...icles/devtest-labs/devtest-lab-guidance-get-started.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-hibernate-vm.md
...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-shared-ip.md
...ob/main/articles/devtest-labs/devtest-lab-shared-ip.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-reference-architecture.md
...les/devtest-labs/devtest-lab-reference-architecture.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md
...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/extend-devtest-labs-azure-functions.md
...es/devtest-labs/extend-devtest-labs-azure-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/how-to-move-labs.md
...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/image-factory-create.md
...lob/main/articles/devtest-labs/image-factory-create.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/start-machines-use-automation-runbooks.md
...devtest-labs/start-machines-use-automation-runbooks.md
High Priority
View Details →
Detected Bias Types
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.