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 301-325 of 334 flagged pages
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-store-secrets-in-key-vault.md
...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-redeploy-vm.md
.../main/articles/devtest-labs/devtest-lab-redeploy-vm.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/samples-cli.md
...re-docs/blob/main/articles/devtest-labs/samples-cli.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-auto-shutdown.md
...ain/articles/devtest-labs/devtest-lab-auto-shutdown.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/encrypt-disks-customer-managed-keys.md
...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority
View Details →
Detected Bias Types
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).
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deploy-nested-template-environments.md
...es/devtest-labs/deploy-nested-template-environments.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/connect-environment-lab-virtual-network.md
...evtest-labs/connect-environment-lab-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-use-custom-lab.md
.../main/articles/devtest-labs/tutorial-use-custom-lab.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-redeploy-vm.md
.../main/articles/devtest-labs/devtest-lab-redeploy-vm.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-create-custom-lab.md
...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-devtest-labs-build-release-pipelines.md
...vtest-labs/use-devtest-labs-build-release-pipelines.md
Medium Priority
View Details →
Detected Bias Types
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).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references managing tags using PowerShell before mentioning Azure CLI, and does not provide explicit Linux/macOS examples or clarify parity between platforms. The mention of PowerShell may imply a Windows-first approach, though Azure CLI is cross-platform.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands for both PowerShell and Azure CLI.
- Ensure that instructions and screenshots do not assume a Windows environment.
- Add a note clarifying that all tag management operations can be performed equally on Linux/macOS using Azure CLI.
- Consider listing Azure CLI before PowerShell to avoid Windows-first perception.
Devtest Labs
Access, claim, and connect to lab VMs
.../main/articles/devtest-labs/tutorial-use-custom-lab.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents connection options for Windows and Linux VMs, but lists Windows (RDP) instructions before Linux (SSH/Azure CLI) instructions. Both platforms are covered, but Windows is mentioned first in the connection section, which may subtly prioritize Windows users.
Recommendations
- Present connection instructions for Windows and Linux VMs in parallel or alphabetical order, rather than listing Windows first.
- Explicitly state parity of features and connection methods for both Windows and Linux VMs.
- Consider providing combined or side-by-side examples for connecting to both Windows and Linux VMs, ensuring equal visibility.
Devtest Labs
Connect to your Linux virtual machines
...articles/devtest-labs/connect-linux-virtual-machine.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation mentions Putty—a Windows-centric SSH client—as an example tool for connecting to Linux VMs, without mentioning popular Linux/macOS alternatives. However, the main connection example uses the cross-platform 'ssh' command, and no Windows/Powershell-specific instructions or ordering are present.
Recommendations
- List cross-platform SSH clients (e.g., OpenSSH, Terminal, MobaXterm, etc.) alongside Putty.
- Explicitly mention that Linux and macOS users can use their built-in terminal and ssh command.
- Provide links or brief instructions for using SSH on Linux/macOS, not just Putty.
- Avoid implying Putty is the default or only option.
Devtest Labs
Create a custom image from a lab VM
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows (sysprep) and Linux (deprovision) generalization steps together, but lists Windows first and links to Windows documentation before Linux. No command-line examples are provided, and the process is described as being performed in the Azure portal, which is cross-platform. There are no Windows-only tools or PowerShell-heavy examples, but the ordering subtly favors Windows.
Recommendations
- Present Windows and Linux generalization steps in parallel, or alternate which is listed first.
- Explicitly mention that the Azure portal is OS-agnostic and works on any platform.
- Provide links to both Windows and Linux generalization documentation side-by-side.
- Include brief command-line examples for both Windows (sysprep) and Linux (waagent deprovision) for users who may want to generalize outside the portal.
Devtest Labs
Create custom images for lab VMs from VHD files
...n/articles/devtest-labs/devtest-lab-create-template.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias. PowerShell is mentioned as an alternative method for creating custom images and for uploading VHD files, but Linux equivalents (such as Bash, Azure CLI, or shell scripts) are not referenced. The examples and instructions for uploading VHD files include PowerShell and Microsoft Azure Storage Explorer (a Windows-focused GUI tool), with no explicit mention of Linux-native tools or workflows. The OS selection step does mention both Windows and Linux, but Windows-specific tooling and terminology (sysprep, PowerShell) appear first or exclusively.
Recommendations
- Add explicit instructions or links for uploading VHD files using Azure CLI or Bash scripts on Linux/macOS.
- Provide parity by referencing Linux-native tools (e.g., azcopy usage on Linux, Azure CLI commands) alongside PowerShell.
- When listing upload methods, alternate or balance the order so Linux tools are not always last.
- Include examples or screenshots from Linux/macOS environments where relevant.
Devtest Labs
Create and manage virtual machines in Azure DevTest Labs with Azure CLI
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Examples
Summary
The documentation page demonstrates mild Windows bias: Windows VM creation is shown first, Windows images are highlighted, and Windows-specific tools (Remote Desktop, PowerShell) are mentioned before Linux equivalents. However, Linux VM creation and SSH connection are also covered, and Linux artifact examples are provided.
Recommendations
- Alternate the order of Windows and Linux examples, or present both side-by-side.
- Provide explicit Linux/macOS instructions for all steps, not just VM creation and SSH.
- Include more Linux/macOS artifact examples in output samples.
- Clarify tool usage parity (e.g., mention that Bash and PowerShell are both supported in Cloud Shell).
- Ensure that links to Linux/macOS connection guides are as prominent as Windows guides.
Devtest Labs
Troubleshoot VM deployment failures
...es/devtest-labs/troubleshoot-vm-deployment-failures.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing PowerShell as the scripting tool for ARM template deployments and mentioning it as the example method. No Linux/macOS CLI or scripting alternatives (such as Azure CLI or Bash) are provided. However, most troubleshooting steps are Azure Portal-based and platform-agnostic.
Recommendations
- Provide equivalent Azure CLI (az) or Bash examples alongside or instead of PowerShell for ARM template deployments.
- Explicitly mention that troubleshooting steps can be performed from any OS using the Azure Portal.
- Where scripting is referenced, offer cross-platform guidance or links to both PowerShell and Azure CLI documentation.
Devtest Labs
Use commands to start and stop lab VMs
...t-labs/use-command-line-start-stop-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure PowerShell and Azure CLI approaches for starting and stopping DevTest Labs VMs. However, PowerShell (a Windows-centric tool) is featured first in all sections, with detailed scripting examples. The Azure CLI section provides both Bash (Linux/macOS) and Windows command syntax, but Windows syntax is shown alongside Bash, and 'REM' (Windows batch comment) appears before Bash comments. There is a subtle prioritization of Windows tools and patterns, and PowerShell is treated as a primary automation method.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present CLI first to balance platform representation.
- In CLI examples, present Bash syntax before Windows batch syntax, and use Bash comments (#) rather than Windows REM.
- Add explicit notes clarifying parity between Windows and Linux/macOS workflows.
- Consider including macOS-specific notes or troubleshooting tips if relevant.
- Ensure that introductory and prerequisite sections mention Bash/CLI environments before or equally with PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows virtual machines first and exclusively in the main VM overview section, and by listing Windows-centric tools (e.g., Visual Studio, Fiddler) as artifact examples without mentioning Linux alternatives. There are no explicit Linux or macOS VM examples, nor are Linux-specific tools or patterns discussed.
Recommendations
- Include references and links to both Windows and Linux VM documentation in the 'Virtual machines' section.
- Provide examples of Linux-based artifacts and tools (e.g., Git, Apache, Node.js) alongside Windows ones.
- Mention Linux VM base images and their use cases in the 'Base images' section.
- Ensure parity in examples and links for both Windows and Linux environments throughout the documentation.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page primarily describes tag management using the Azure portal UI, which is platform-agnostic. However, in the section referencing programmatic tag management, 'PowerShell' is mentioned before 'Azure CLI', and no explicit Linux/macOS examples or tooling are provided. The mention of PowerShell (a Windows-centric tool) first, without equal emphasis on cross-platform alternatives, introduces a mild Windows bias.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide direct links or examples for both PowerShell and Azure CLI.
- Include sample commands for both PowerShell and Azure CLI for managing tags, ensuring parity for Linux/macOS users.
- Clarify that the Azure portal is accessible from any OS/browser, and highlight cross-platform options for automation.
- Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless contextually justified.
Devtest Labs
Create a custom image from a lab VM
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows-specific tooling (Sysprep) before Linux equivalents (deprovision), and refers to Sysprep as the primary example when discussing generalization. Windows terminology and links are presented first, which may subtly reinforce a Windows-centric workflow.
Recommendations
- Present Linux and Windows generalization options with equal prominence, possibly alternating which is mentioned first.
- Provide direct links to both Sysprep (Windows) and deprovision (Linux) documentation side-by-side.
- Clarify that both Windows and Linux VMs are supported equally in the custom image creation process.
- Include screenshots or examples for both Windows and Linux VMs if there are any differences in the UI or workflow.
Devtest Labs
Create custom images for lab VMs from VHD files
...n/articles/devtest-labs/devtest-lab-create-template.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. PowerShell is mentioned as an alternative method for creating custom images, and uploading VHD files via PowerShell is listed as a primary option. Windows tools (sysprep) are referenced before their Linux equivalents (deprovision), and the OS selection UI lists Windows before Linux. However, Linux is supported and referenced, and AzCopy (cross-platform) is included as an upload method.
Recommendations
- Provide explicit Bash/CLI examples for Linux users alongside PowerShell instructions.
- Ensure Linux tools (e.g., waagent deprovision) are described with equal detail as Windows sysprep.
- Alternate the order of Windows and Linux references in UI instructions to avoid Windows-first bias.
- Add screenshots or walkthroughs using Linux environments where relevant.
- Clarify that AzCopy and Storage Explorer are cross-platform and provide usage notes for Linux/macOS.
Devtest Labs
Create and manage virtual machines in Azure DevTest Labs with Azure CLI
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows-based VM creation is shown first, with explicit mention of Windows images and admin-password authentication before Linux/SSH examples. Artifact examples include both Linux and Windows, but the sample output for listing artifacts only shows a Windows artifact. The section on listing artifacts gives PowerShell syntax first, then Bash. References to Remote Desktop (Windows) and SSH (Linux/macOS) are present, but the ordering and examples tend to favor Windows.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their ordering to avoid implicit prioritization.
- Include sample output for both Linux and Windows artifacts when listing artifacts.
- When showing authentication options, mention SSH (Linux/macOS) and password (Windows) together, clarifying platform relevance.
- Ensure that Bash and PowerShell examples are given equal prominence, possibly in tabbed or parallel format.
- Explicitly state cross-platform compatibility in introductory sections.