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 151-175 of 334 flagged pages
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/import-virtual-machines-from-another-lab.md
...vtest-labs/import-virtual-machines-from-another-lab.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell script examples for importing virtual machines, referencing a .ps1 script, and omitting any Linux shell or cross-platform CLI examples. PowerShell is a Windows-centric tool, and the lack of Bash, Azure CLI, or other Linux-friendly instructions makes the documentation less accessible to Linux users. The PowerShell method is presented before the REST API, reinforcing the Windows-first approach.
Recommendations
- Add equivalent examples using Bash scripts and/or Azure CLI commands for Linux users.
- Explicitly state cross-platform options and clarify PowerShell Core compatibility on Linux/macOS if applicable.
- Present REST API and CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Reference Linux tools and scripting patterns where appropriate, and provide links to relevant cross-platform resources.
Create Pull Request
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/quickstarts/create-lab-rest.md
...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell for all command-line examples, assumes the presence of the Az PowerShell module, and provides no equivalent instructions for Linux users (e.g., Bash, curl, or Azure CLI). Windows-specific tools and patterns are mentioned throughout, with no mention of Linux alternatives or cross-platform approaches. This creates a strong Windows bias and may hinder Linux users from following the quickstart.
Recommendations
- Add equivalent examples using Bash and curl for REST API calls.
- Include instructions for using Azure CLI (az) to authenticate and interact with the REST API.
- Mention cross-platform compatibility and provide guidance for both Windows and Linux users.
- Reorganize sections to present platform-neutral or Linux examples alongside or before Windows/PowerShell examples.
- Clarify prerequisites for Linux users, such as installing Azure CLI or using native tools.
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 is heavily oriented toward Windows environments, with exclusive use of Windows tools (PowerShell scripts, IIS, RDGatewayFedAuth.msi, System Center VMM), and no mention of Linux equivalents or cross-platform alternatives. All code and automation examples are in PowerShell, and the workflow assumes RDP and Windows-based gateway solutions. There are no instructions or examples for Linux-based remote desktop gateways, certificate management, or automation, and Linux users are not addressed.
Recommendations
- Provide Linux-based examples for certificate creation and management (e.g., using OpenSSL or Linux CLI tools).
- Include instructions or references for setting up a remote desktop gateway on Linux (such as xrdp, FreeRDP, or Guacamole) and how to integrate with Azure DevTest Labs.
- Offer automation scripts in Bash or Azure CLI (not just PowerShell) for key steps such as certificate handling and lab configuration.
- Mention and document cross-platform RDP clients and their compatibility with token authentication.
- Clarify which steps or tools are Windows-specific and provide Linux alternatives where possible.
- Consider a section or callout for Linux administrators, outlining any differences or additional requirements.
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 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.
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 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.
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-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.
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 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.
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 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.
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-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.
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 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.
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
High Priority
View Details →
Detected Bias Types
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.
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
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-governance-resources.md
...test-labs/devtest-lab-guidance-governance-resources.md
High Priority
View Details →
Detected Bias Types
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.
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
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.
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
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.
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 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.
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 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.
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
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md
...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority
View Details →
Detected Bias Types
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.
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
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/test-app-azure.md
...docs/blob/main/articles/devtest-labs/test-app-azure.md
High Priority
View Details →
Detected Bias Types
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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md
...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary 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.
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 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-repository.md
.../main/articles/devtest-labs/add-artifact-repository.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 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.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-vm.md
...ocs/blob/main/articles/devtest-labs/add-artifact-vm.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 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.