Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 501-525 of 2185 flagged pages
Azure Docs
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 deployment in examples, providing only Windows-based quickstart templates, and focusing heavily on Azure PowerShell for automation and scripting. There are no explicit Linux VM examples or Linux-specific instructions, and PowerShell is emphasized over cross-platform alternatives. The GitHub resources referenced also highlight PowerShell scripts, with no mention of Bash or Linux shell scripts.
Recommendations
- Include Linux VM deployment examples alongside Windows examples, especially in quickstart and template walkthroughs.
- Provide automation instructions and links for both Azure CLI (cross-platform) and Azure PowerShell, ensuring parity in depth and detail.
- Reference and link to Bash or shell script samples in the GitHub repository, or add such scripts if they do not exist.
- Avoid using Windows-specific terminology or tools as the default; present cross-platform options first or in parallel.
- Add screenshots and walkthroughs that demonstrate Linux VM creation and management in DevTest Labs.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/understand-path-lengths.md
...articles/azure-netapp-files/understand-path-lengths.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting SMB/Windows path length limitations and workarounds in greater detail and before NFS/Linux equivalents. Windows-specific tools (e.g., registry edits, Group Policy, drive mapping) are described extensively, including screenshots, while Linux/NFS sections are briefer, lack visual aids, and do not provide equivalent troubleshooting or configuration guidance. Linux/NFS examples are limited to basic shell commands, with no discussion of advanced configuration or error handling comparable to the Windows coverage.
Recommendations
- Provide Linux/NFS troubleshooting steps and configuration examples analogous to the Windows registry and Group Policy instructions (e.g., how to check or adjust NFS client limits, or handle path length errors).
- Include screenshots or terminal output for Linux/NFS error messages and configuration steps, similar to the Windows dialog and Group Policy images.
- Present NFS/Linux information before or alongside SMB/Windows information to avoid the impression of Windows-first bias.
- Expand on Linux/NFS-specific limitations, workarounds, and best practices, such as mounting strategies, relevant kernel parameters, or client configuration files.
- Offer parity in example depth: if Windows path mapping and error dialogs are shown, provide equivalent Linux/NFS examples (e.g., mounting deep directories, handling long paths in scripts, or using alternative mount options).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric tools. All instructions and examples are tailored to Windows development environments, with no mention of Linux-compatible alternatives (such as .NET Core/.NET 6+, cross-platform editors, or Linux package management). There are no Linux-specific instructions or examples, and the workflow is described exclusively in terms of Windows tools and patterns.
Recommendations
- Provide alternative instructions for creating the console application using cross-platform tools such as the .NET CLI (e.g., 'dotnet new console') and editors like VS Code.
- Mention and demonstrate the use of .NET Core/.NET 6+ instead of .NET Framework, as these are cross-platform and supported on Linux.
- Include Linux-specific package installation steps (e.g., using 'dotnet add package Microsoft.Azure.Relay' instead of Visual Studio's NuGet UI).
- Clarify that the sample code works on Linux and macOS as well, and provide any necessary steps or caveats for those platforms.
- Avoid assuming the presence of Visual Studio or Windows-only workflows; present Windows and Linux options side-by-side where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md
...id-connections-http-requests-dotnet-get-started-client.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and the .NET Framework (not .NET Core or .NET 5/6/7+), which are primarily used on Windows. There are no instructions or examples for Linux users, such as using cross-platform .NET SDKs, command-line tools, or alternative editors. The steps for adding NuGet packages and creating projects are described only in the context of Visual Studio's GUI, with no mention of CLI alternatives that work on Linux or macOS.
Recommendations
- Add instructions for creating the console application using the cross-platform .NET CLI (e.g., 'dotnet new console').
- Include steps for adding NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
- Clarify that the code works with .NET Core/.NET 5+ and is cross-platform, or provide a separate section for Linux/macOS users.
- Mention alternative editors (such as VS Code) and provide guidance for users on Linux/macOS.
- Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented together, ensuring parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/private-link-service.md
...lob/main//articles/azure-relay/private-link-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based configuration, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/Bash or Azure CLI examples. The validation steps specifically mention using a Windows VM and do not address Linux alternatives. There is no mention of Linux tools or cross-platform command-line instructions.
Recommendations
- Add equivalent Azure CLI (az) examples for creating and managing private endpoints, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include instructions for creating and validating the setup using a Linux virtual machine, with appropriate screenshots and command-line examples.
- When providing command-line validation steps (e.g., nslookup), clarify that these commands work on both Windows and Linux, and show example outputs from both environments.
- Avoid referencing only Windows-specific resources or tools (such as Azure PowerShell or Windows VM creation guides) without mentioning or linking to Linux equivalents.
- Consider reordering examples or providing parallel instructions for both Windows and Linux users to ensure parity and inclusivity.
Azure Docs
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
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step troubleshooting instructions and examples specifically for Windows VMs, including PowerShell commands, File Explorer navigation, and references to Windows-specific paths and tools. Linux troubleshooting is only referenced via a link, with no in-page guidance or examples. Windows tools and patterns (e.g., File Explorer, Command Prompt, C:\ paths) are mentioned exclusively, and PowerShell is the only CLI example provided.
Recommendations
- Provide parallel Linux examples and instructions alongside Windows steps, including explicit Linux file paths and log locations.
- Include Azure CLI or Bash command examples in addition to PowerShell, especially for checking VM artifact status.
- Describe how to access and interpret Custom Script Extension logs on Linux VMs directly in the document, rather than linking out.
- Reference Linux tools (e.g., SSH, less, cat, tail) and shell navigation where appropriate.
- Ensure that troubleshooting steps are presented for both Windows and Linux VMs in each relevant section, not just as a footnote or external link.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-authentication-and-authorization.md
.../azure-relay/relay-authentication-and-authorization.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page focuses on .NET and WCF (Windows Communication Foundation) SDKs and samples, which are traditionally Windows-centric technologies. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Azure CLI), and the only code samples referenced are for .NET, Java, and JavaScript, with WCF being Windows-specific. There is no mention of Linux tools or patterns for authentication, nor are there instructions for generating SAS tokens or managing access from a Linux environment. The documentation implicitly assumes a Windows/.NET development environment.
Recommendations
- Add explicit Linux and cross-platform examples for generating SAS tokens, such as using Bash scripts, curl, or OpenSSL.
- Include Azure CLI commands for managing Azure Relay authentication and authorization, which work across platforms.
- Provide sample code or instructions for authenticating from Linux environments, including Python or Node.js examples.
- Clarify which features or SDKs are cross-platform and which are Windows-only (e.g., WCF).
- Reference Linux-friendly tools and workflows alongside Windows/.NET examples to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md
...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation assumes the use of Visual Studio (a Windows-centric IDE) and does not mention or provide examples for Linux development environments or tools. There are no instructions for running or building the .NET applications on Linux, nor is there mention of cross-platform .NET Core/SDK usage or alternative editors. The focus on Visual Studio and omission of Linux-specific guidance demonstrates a Windows-first and Windows-tools bias, with missing Linux examples.
Recommendations
- Add instructions for developing and running the .NET applications using cross-platform tools such as the .NET CLI (dotnet new, dotnet run) and editors like VS Code.
- Explicitly mention that the sample code works on Linux, macOS, and Windows if using .NET Core or .NET 5+.
- Provide example commands for installing the .NET SDK on Linux and running the applications from the terminal.
- Include screenshots or terminal output from Linux environments, or clarify that the tutorial is cross-platform.
- Avoid assuming Visual Studio as the only development environment; mention alternatives like VS Code, JetBrains Rider, or command-line workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/ip-firewall-virtual-networks.md
...//articles/azure-relay/ip-firewall-virtual-networks.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing deployment instructions that link specifically to PowerShell (a Windows-centric tool) for deploying ARM templates, without mentioning or providing equivalent instructions for Linux or cross-platform tools like Azure CLI. There are no Linux-specific or cross-platform command examples, and the only automation/deployment path referenced is PowerShell.
Recommendations
- Add explicit instructions and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux.
- Wherever PowerShell is referenced, also provide equivalent Bash/Azure CLI commands and links.
- Review all links and ensure that Linux and cross-platform deployment options are mentioned alongside Windows/PowerShell options.
- Consider adding a section or note clarifying that all steps can be performed on Linux, macOS, and Windows, and provide links to relevant documentation for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments. All instructions and examples assume the use of Visual Studio (Windows-only for .NET Framework), and there is no mention of Linux or cross-platform development tools. The tutorial steps, screenshots, and project templates are all specific to Windows and Visual Studio, with no guidance for Linux users or those using cross-platform .NET Core/SDK tools.
Recommendations
- Provide equivalent instructions for Linux users, including how to set up the development environment using .NET Core/SDK CLI tools (dotnet CLI) instead of Visual Studio.
- Include examples and steps for creating, building, and running the projects using cross-platform tools (e.g., VS Code, JetBrains Rider, or the dotnet CLI).
- Clarify which parts of the tutorial require Windows-specific technologies (such as WCF with .NET Framework) and suggest alternatives or workarounds for Linux users.
- Add notes or sections that explicitly address Linux/macOS users, including any limitations or required adaptations.
- Where possible, use .NET 6+ and cross-platform project types (such as ASP.NET Core) to maximize compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/understand-volume-languages.md
...cles/azure-netapp-files/understand-volume-languages.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools, settings, and workflows (such as PowerShell, Notepad, Notepad++, Windows Explorer, Windows Terminal, and region settings) are frequently mentioned, often before or instead of their Linux equivalents. Many screenshots and examples focus on Windows environments, and encoding conversion is primarily shown with PowerShell before mentioning Linux commands. Some Linux tools (iconv, file) are included, but often after Windows-centric explanations. There are also sections where only Windows-specific troubleshooting or configuration is described, with less detail for Linux or macOS clients.
Recommendations
- Ensure Linux and macOS examples are presented alongside Windows examples, not just after or as an afterthought.
- When describing encoding conversion or file viewing, provide Linux/macOS command-line examples (e.g., iconv, file, cat, locale) before or alongside PowerShell/Notepad workflows.
- Include screenshots from Linux terminals (e.g., GNOME Terminal, Konsole) and macOS Terminal, not just Windows tools.
- When referencing configuration steps (such as changing encoding or fonts), provide equivalent instructions for Linux and macOS environments.
- Mention Linux and macOS client behaviors and troubleshooting steps with the same level of detail as Windows.
- Avoid assuming Windows as the default client; use neutral phrasing or rotate the order of OS examples.
- Highlight cross-platform tools (e.g., VS Code, nano, vim) for encoding inspection and conversion.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-what-is-it.md
...cs/blob/main//articles/azure-relay/relay-what-is-it.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through the prominent mention and prioritization of WCF Relay, which is tightly coupled to Windows and the .NET Framework. WCF (Windows Communication Foundation) is a Windows-specific technology, and all WCF Relay examples and quick starts are inherently Windows-centric. While the Hybrid Connections feature is described as cross-platform and examples are provided for .NET, Node.js, and Java, the WCF Relay section lacks any Linux or cross-platform guidance. Additionally, the documentation does not provide parity in Linux-native tooling or examples for WCF Relay scenarios, and the Windows-specific WCF Relay is always mentioned before the more cross-platform Hybrid Connections in several sections.
Recommendations
- Clearly indicate that WCF Relay is Windows/.NET Framework-specific and not supported on Linux, and recommend Hybrid Connections for cross-platform scenarios.
- Where possible, provide equivalent Linux or cross-platform examples for all scenarios, or explicitly state when a feature is Windows-only.
- Reorganize sections so that cross-platform features (Hybrid Connections) are introduced and emphasized before Windows-specific ones (WCF Relay).
- Add explicit Linux quick starts or guidance for setting up and using Azure Relay from Linux environments, especially for Hybrid Connections.
- Avoid using Windows-specific terminology (such as WCF) without context or alternatives for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/bicep-config-modules.md
...s/azure-resource-manager/bicep/bicep-config-modules.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure CLI as the primary credential sources, listing Azure PowerShell before other options, and not providing any Linux- or bash-specific examples or guidance. There is no mention of Linux shell usage, nor are there examples or notes about cross-platform differences in authentication or tooling.
Recommendations
- Explicitly mention that Azure CLI and Bicep are cross-platform and can be used on Linux, macOS, and Windows.
- Provide bash or shell command examples alongside any PowerShell or Windows-centric instructions.
- When listing credential sources, avoid always listing Azure PowerShell before Azure CLI, or clarify that both are supported equally across platforms.
- Include a section or note about using Bicep and configuring credentials on Linux and macOS, highlighting any differences or additional steps.
- If referencing Visual Studio, also mention Visual Studio Code, which is cross-platform.
- Ensure that all tool references and instructions are inclusive of non-Windows environments.
Azure Docs
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 demonstrates a strong Windows bias: it explicitly states AzCopy is 'Windows-only' (which is outdated, as newer AzCopy versions are cross-platform), provides only Windows Command Prompt and PowerShell instructions, references Windows installation paths, and omits any Linux or macOS usage examples. There is no mention of Linux equivalents or cross-platform usage, and automation is described only in a Windows context.
Recommendations
- Update the note about AzCopy: clarify that AzCopy v10+ is cross-platform and available for Windows, Linux, and macOS.
- Provide Linux and macOS installation instructions and example commands (e.g., using bash shell).
- Include cross-platform AzCopy usage examples, showing both Windows (cmd/PowerShell) and Linux/macOS (bash) command syntax.
- Avoid referencing only Windows-specific paths (like ProgramFiles(x86)); mention typical Linux/macOS install locations.
- When referencing automation, include examples for Linux shell scripting as well as PowerShell.
- Ensure screenshots and portal instructions do not assume PowerShell as the only automation method.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/service-bus-relay-rest-tutorial.md
...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows development environments. It assumes the use of Visual Studio (a Windows-centric IDE), relies on WCF (which is not cross-platform), and provides instructions and examples exclusively for Windows. There are no Linux or cross-platform alternatives, nor any mention of how to perform the same tasks on Linux or with non-Windows tools. The workflow, project setup, and testing instructions are all tailored to Windows users.
Recommendations
- Provide equivalent instructions for Linux users, such as using VS Code, JetBrains Rider, or command-line .NET tools (dotnet CLI) for project creation and management.
- Clarify that WCF is not supported on .NET Core/.NET 5+ on Linux, and suggest alternative cross-platform approaches (e.g., ASP.NET Core with Azure Relay Hybrid Connections, or using REST APIs directly).
- Include examples and configuration steps for cross-platform development, such as using the dotnet CLI to create and run projects.
- Avoid assuming Visual Studio or Windows-specific workflows; where necessary, provide parallel instructions for Linux/macOS.
- Explicitly state platform limitations and provide links to cross-platform Azure Relay samples or documentation.
- If the scenario is inherently Windows-only (due to WCF), call this out clearly at the top and suggest alternatives for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md
...ource-manager/bicep/bicep-functions-parameters-file.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 exclusively providing PowerShell commands and .NET-specific methods for setting environment variables, without mentioning or providing equivalent Linux/macOS shell commands (such as export or set in Bash). All examples and references for environment variable manipulation are Windows-centric, and there is no guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Linux/macOS shell examples (e.g., export testEnvironmentVariable="Hello World!") for setting environment variables at process, user, and machine levels where applicable.
- Mention that the PowerShell/.NET methods are specific to Windows and provide Bash or other shell alternatives for cross-platform parity.
- Reorder or parallelize the examples so that both Windows and Linux/macOS commands are presented together, rather than Windows first or exclusively.
- Include a brief note or table summarizing environment variable handling differences across platforms, with links to relevant documentation for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/service-bus-relay-tutorial.md
...in//articles/azure-relay/service-bus-relay-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All instructions, examples, and tooling references assume a Windows platform. There are no mentions of Linux or cross-platform alternatives, and all code samples and project setup steps are tailored to Windows users. The use of Visual Studio, .NET Framework (not .NET Core/.NET 5+), and Windows-specific project types further reinforce this bias.
Recommendations
- Provide equivalent instructions for Linux and macOS users, including using cross-platform .NET (such as .NET 6/7/8) and editors like VS Code or JetBrains Rider.
- Include command-line instructions (e.g., using dotnet CLI) for project creation, package management, and building/running applications.
- Clarify which steps are Windows-specific and offer alternatives for other platforms (e.g., running as a .NET Core console app, using cross-platform configuration files).
- Mention and demonstrate how to use Azure WCF Relay with .NET Core/.NET 5+ (which is cross-platform) and highlight any limitations or differences.
- Add troubleshooting notes for Linux users, especially around WCF support and any required dependencies.
- Consider referencing or linking to official Microsoft documentation on running WCF clients/services on non-Windows platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/create-resource-group.md
.../azure-resource-manager/bicep/create-resource-group.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell is always presented after Azure CLI, and there is no explicit mention of Linux or Bash scripting. The PowerShell examples use Windows-specific syntax (backticks for line continuation), and there are no Linux/Bash-specific notes or troubleshooting tips. There is also no mention of running Azure CLI commands in Bash or Linux environments, nor are there any screenshots or references to Linux shells.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI commands, including line continuations with backslashes and any relevant environment notes.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Cloud Shell, or Windows Command Prompt, with examples for each where syntax differs.
- Include troubleshooting notes or tips for common Linux/Bash issues (such as file path differences or permission issues).
- Consider providing a table or section summarizing command usage across Windows (PowerShell, CMD) and Linux (Bash) environments.
- Avoid using only PowerShell-specific syntax (like backticks) without also showing the Bash equivalent.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deployment-script-vnet-private-endpoint.md
...nager/bicep/deployment-script-vnet-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates the use of Azure PowerShell for deployment scripts (kind: 'AzurePowerShell', azPowerShellVersion, scriptContent: 'Write-Host ...'), with no mention or example of Bash or Linux scripting. The script content and deploymentScript kind are both Windows/PowerShell-centric, and there is no guidance for users who may prefer or require Linux-based (Bash) deployment scripts.
Recommendations
- Provide an equivalent example using 'AzureCLI' (Bash) as the deployment script kind, including sample Bash script content.
- Explicitly mention that both PowerShell and Bash (AzureCLI) are supported for deployment scripts, and link to documentation for both.
- Show both PowerShell and Bash scriptContent examples side-by-side, or allow the user to select their preferred scripting language.
- Clarify any differences in prerequisites or behavior between PowerShell and Bash deployment scripts in this scenario.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/image-factory-set-retention-policy-cleanup.md
...est-labs/image-factory-set-retention-policy-cleanup.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 by exclusively referencing Azure PowerShell tasks and scripts for automation, without mentioning or providing examples for Linux users or cross-platform alternatives such as Azure CLI, Bash, or Python scripts. All screenshots and instructions are centered on PowerShell, and there is no guidance for users who may be working from non-Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for each PowerShell task, ensuring Linux and macOS users can follow along.
- Mention cross-platform automation options (e.g., Azure CLI, REST API, Python SDK) alongside PowerShell, and clarify when a step is Windows-specific.
- Include screenshots or code snippets from non-Windows environments (e.g., Bash task in Azure DevOps).
- Rephrase instructions to be tool-agnostic where possible, or offer parallel instructions for both PowerShell and CLI.
- Explicitly state any limitations or prerequisites if a step can only be performed on Windows, and suggest workarounds for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-what-if.md
...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and instructions are consistently presented before Azure CLI equivalents, and the output samples are shown in PowerShell syntax. The text output and programmatic evaluation sections use PowerShell as the primary example, with CLI examples following. There is a focus on PowerShell cmdlets and Windows-centric tools, with no mention of Linux-specific considerations or shell environments. However, Azure CLI examples are present throughout, and both PowerShell and CLI are covered in most sections.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples to avoid always presenting Windows/PowerShell first.
- Provide explicit Linux/macOS shell examples where relevant (e.g., bash, zsh), especially for scripting and environment setup.
- Include notes about cross-platform compatibility for both PowerShell (e.g., PowerShell Core on Linux/macOS) and Azure CLI.
- Ensure that output samples are shown in both PowerShell and CLI formats, or use CLI as the default where possible for cross-platform parity.
- Clarify that all commands work on Windows, Linux, and macOS, and mention any platform-specific caveats if they exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deployment-script-bicep.md
...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently, with full deployment and management examples using Azure PowerShell, and PowerShell command-line snippets are provided for deployment and REST API usage. While Azure CLI (which is cross-platform) is also covered, there are no explicit Linux shell (bash) deployment examples, and the PowerShell approach is often presented alongside or before CLI alternatives. The documentation assumes familiarity with PowerShell tools and patterns, and does not provide parity for Linux-native workflows (e.g., bash scripts for deployment, Linux package/tool installation, or Linux-specific troubleshooting).
Recommendations
- Add explicit bash/Linux shell examples for deploying Bicep files, including resource group creation and deployment, to complement the PowerShell examples.
- When showing both Azure CLI and PowerShell, alternate the order or clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Provide instructions for setting up a Linux-based development environment, including common tools (e.g., jq, bash) and package installation commands.
- Include troubleshooting steps and script management examples using bash and Azure CLI, not just PowerShell.
- Avoid using PowerShell-specific syntax (such as $variable or Write-Host) in general guidance unless also providing a Linux shell equivalent.
- Clarify in the introduction that both Windows and Linux environments are supported, and highlight any differences or limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md
...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and PowerShell environments. PowerShell is used as the default scripting and deployment tool throughout, with all deployment and upload examples provided only in PowerShell. Even in sections about Azure CLI and Docker, PowerShell scripts are used for resource creation and file upload, and Windows-style path conventions are shown first or exclusively. There is a lack of equivalent Bash or cross-platform CLI examples for common tasks, such as uploading files or deploying resources, which may hinder Linux or macOS users.
Recommendations
- Provide Bash/Azure CLI equivalents for all PowerShell scripts, especially for uploading files and deploying Bicep templates.
- When demonstrating Docker volume mounts, include Linux/macOS examples (e.g., using /home/user/docker:/data) alongside Windows drive letter examples.
- Avoid assuming PowerShell as the default shell; clarify when steps are cross-platform or provide alternatives.
- Explicitly mention and demonstrate how to perform each step on Linux/macOS, not just Windows.
- List both PowerShell and Bash/CLI commands side-by-side where possible, and avoid Windows-first ordering.
- Clarify any platform-specific requirements or differences in the prerequisites and setup sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deployment-script-develop.md
...re-resource-manager/bicep/deployment-script-develop.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides parallel examples for both Azure CLI (Bash) and Azure PowerShell, but there are several signs of Windows bias. PowerShell is given equal or sometimes more detailed treatment, and Windows-specific tools and APIs (such as CommandLineToArgvW and Connect-AzAccount) are referenced without Linux equivalents. The documentation assumes familiarity with PowerShell patterns and Windows-centric APIs, and sometimes mentions Windows/PowerShell tools before or more prominently than their Linux/Bash counterparts.
Recommendations
- Where Windows-specific APIs or tools are referenced (e.g., CommandLineToArgvW, Connect-AzAccount), provide Linux or cross-platform equivalents or clarify that these are implementation details not relevant to script authors.
- Ensure that CLI/Bash examples are always presented first or in parallel with PowerShell examples, especially in introductory or summary sections.
- Where PowerShell-specific troubleshooting or scripting patterns are discussed (e.g., $ErrorActionPreference, Start-Sleep), provide Bash/Linux equivalents (e.g., set -e, sleep) and explain their usage.
- Clarify that both Bash and PowerShell scripts run in Linux-based containers by default, and highlight any cross-platform considerations.
- Avoid referencing Windows-only concepts or APIs unless strictly necessary, and always provide context for users on non-Windows platforms.
- Consider adding a section explicitly addressing cross-platform scripting best practices and differences between Bash and PowerShell in the Azure deployment script context.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/installation-troubleshoot.md
...re-resource-manager/bicep/installation-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing command-line instructions and environment variable paths that are specific to Windows (e.g., 'where bicep', '%USERPROFILE%\.Azure\bin'), without mentioning or providing equivalents for Linux or macOS users. There are no Linux/macOS-specific commands (such as 'which bicep' or path examples like '$HOME/.azure/bin'), and the troubleshooting steps assume a Windows environment.
Recommendations
- Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' for Linux/macOS alongside 'where bicep' for Windows).
- Provide environment variable path examples for Linux/macOS (e.g., '$HOME/.azure/bin') in addition to Windows paths.
- Clarify steps that are platform-specific and offer parallel instructions for each supported OS.
- Explicitly mention that the instructions apply to Windows, and provide separate sections or notes for Linux/macOS users where applicable.