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 1626-1650 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/managed-applications/approve-just-in-time-access.md
...er/managed-applications/approve-just-in-time-access.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes using the Azure Portal (a web-based GUI) for configuring and approving just-in-time access, without providing any command-line examples. There are no references to PowerShell or Windows-specific tools, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission can disadvantage Linux users or those who prefer automation and scripting.
Recommendations
- Add equivalent instructions for performing JIT access configuration and approval using the Azure CLI, including example commands.
- Explicitly mention that the steps can be performed from any OS via the portal, but provide parity by including CLI/Bash examples for Linux and cross-platform users.
- If PowerShell examples are ever added, ensure that Bash/Azure CLI examples are provided alongside them.
- Clarify any OS dependencies or lack thereof for the described procedures.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/custom-providers/tutorial-resource-onboarding.md
...nager/custom-providers/tutorial-resource-onboarding.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes deployment and resource management through the Azure portal UI, which is most commonly used on Windows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts) for deploying the ARM template or managing resources. There is no mention of Linux or cross-platform tooling, and all screenshots and instructions are tailored to the Azure portal experience, which may be less accessible or less preferred for Linux users or those working in headless/server environments.
Recommendations
- Add Azure CLI examples for deploying the ARM template and managing custom resource providers and associations. The Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- If PowerShell examples are added, also provide Bash equivalents to ensure parity for Linux users.
- Include a section on how to deploy the template and manage resources using command-line tools, not just the Azure portal.
- Mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
- Consider including sample scripts or one-liners for common tasks (e.g., az deployment group create ...) to help users automate deployments from Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/howto-use-managed-identity.md
...//articles/azure-signalr/howto-use-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Azure Portal (GUI) instructions and omitting any command-line examples, such as Azure CLI or PowerShell. There are no Linux-specific or cross-platform command-line instructions, which may disadvantage users who prefer or require CLI-based workflows, especially on Linux or macOS. The absence of CLI examples and reliance on portal screenshots implicitly prioritizes Windows/GUI usage patterns.
Recommendations
- Add Azure CLI examples for all management tasks (e.g., adding system-assigned/user-assigned identities, configuring upstream settings, setting Key Vault access policies) alongside portal instructions.
- Explicitly mention that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
- Where PowerShell is relevant, provide equivalent Bash/Azure CLI commands.
- Include at least one end-to-end example using only CLI tools to demonstrate parity for Linux and macOS users.
- Clarify in prerequisites or introduction that all features are accessible from any OS using the CLI, not just via the Azure Portal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/control-plane-and-data-plane.md
...rce-manager/management/control-plane-and-data-plane.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Remote Desktop Protocol (RDP) as the example for interacting with a virtual machine via the data plane, without mentioning SSH or other cross-platform access methods. No Linux-specific or cross-platform examples are provided for data plane operations, and the only concrete example (RDP) is Windows-centric.
Recommendations
- When describing data plane operations for virtual machines, include SSH as an example alongside RDP to represent Linux and cross-platform scenarios.
- Provide examples or references for both Windows and Linux tools or protocols when discussing resource access (e.g., mention both RDP and SSH for VM access).
- Review other examples to ensure Linux and cross-platform tools are represented equally, especially in sections discussing interaction with resources.
- Consider adding a table or section that lists common data plane operations and their typical tools/protocols for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/lock-resources.md
...es/azure-resource-manager/management/lock-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI examples in the 'Configure locks' section. The PowerShell section is more detailed and comes before the Azure CLI, which is cross-platform and preferred by many Linux users. There are no explicit Linux-only examples or references to Linux-specific tools, but the ordering and emphasis may give the impression of a Windows/PowerShell bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Ensure parity in detail and coverage between Azure CLI and PowerShell sections.
- Explicitly mention that both Azure CLI and PowerShell are supported on Windows, macOS, and Linux, and provide installation links for each.
- Consider adding Bash shell script examples where appropriate, especially for automation scenarios.
- If referencing Visual Studio (a Windows-first tool), also mention cross-platform alternatives (e.g., VS Code) where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md
...ement/move-limitations/app-service-move-limitations.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure Portal (a web-based GUI) for all operational steps, with no mention of command-line alternatives such as Azure CLI, PowerShell, or scripting. There are no Linux-specific instructions or examples, nor are cross-platform tools highlighted. The guidance assumes the use of graphical tools, which are more commonly associated with Windows workflows, and omits parity for Linux or terminal-based users.
Recommendations
- Add step-by-step instructions using Azure CLI for all major operations (e.g., finding the original resource group, moving resources, handling certificates).
- Include PowerShell examples, but ensure Azure CLI examples are presented first or alongside, as Azure CLI is cross-platform.
- Explicitly mention that all operations can be performed via the command line on Linux, macOS, and Windows, and provide relevant command samples.
- Reference documentation for scripting and automation, which is common in Linux environments.
- Where screenshots are used, consider including terminal output or code blocks to illustrate non-GUI workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/manage-resource-groups-python.md
...ce-manager/management/manage-resource-groups-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but presents the Windows instructions first. It also references Windows-specific tools and editors (e.g., Visual Studio) in the context of restarting after environment variable changes, without mentioning Linux or macOS equivalents. No PowerShell-specific commands are present, and Linux/macOS examples are included, but Windows is prioritized in ordering and tool references.
Recommendations
- Rotate or randomize the order of platform-specific tabs (Windows, Linux, macOS) to avoid always presenting Windows first.
- When referencing the need to restart editors or terminals, include examples for popular Linux (e.g., VS Code, GNOME Terminal) and macOS editors/terminals, not just Visual Studio.
- Where possible, use cross-platform language (e.g., 'your editor or IDE') instead of naming only Windows-centric tools.
- Ensure that all platform-specific instructions are equally detailed and visible, and avoid implying Windows is the default or primary environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/samples-cli.md
...e-docs/blob/main//articles/devtest-labs/samples-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits a Windows-first bias by focusing on the creation of Windows VMs in its primary example and by labeling Bash scripts as 'powershell' in code blocks. There are no explicit Linux VM creation examples, and the code block language metadata may confuse Linux users. Although the scripts themselves are Bash and use Azure CLI (which is cross-platform), the documentation's language and structure prioritize Windows terminology and patterns.
Recommendations
- Provide explicit examples for creating both Windows and Linux VMs, or clarify that the scripts are suitable for both.
- Correct the code block language tags from 'powershell' to 'bash' or 'azurecli' to accurately reflect the script type and improve clarity for Linux users.
- Include notes or sections that address Linux users directly, ensuring parity in instructions and terminology.
- If possible, add a table or section comparing any OS-specific considerations (e.g., authentication methods, image references) for both Windows and Linux VMs in DevTest Labs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocate-evaluate.md
...azure-resource-manager/management/relocate-evaluate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing only Windows-centric tools and documentation (such as PowerShell) when discussing tasks like moving public IP configurations. There are no Linux or cross-platform command-line examples or references, and the documentation does not mention Linux-specific considerations or tools for discovery, automation, or migration.
Recommendations
- Provide Linux and cross-platform command-line examples (e.g., Azure CLI, Bash) alongside or before PowerShell examples, especially in sections like moving public IP configurations.
- Mention cross-platform automation and scripting options (such as Azure CLI, Terraform, or Ansible) in the automation and discovery sections.
- Include references to Linux-specific considerations for workload discovery and migration, such as handling Linux-based VMs, file systems, or application dependencies.
- Ensure that all tool recommendations and documentation links include both Windows and Linux usage instructions where applicable.
- Review and update language to avoid assuming a Windows environment by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/tutorial-create-custom-lab.md
...n//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 exclusively providing instructions and examples for creating a Windows Server 2019 Datacenter VM, without mentioning or illustrating how to create a Linux-based VM. There are no Linux-specific options, screenshots, or guidance, and the only OS base explicitly referenced is Windows.
Recommendations
- Include parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
- Mention the availability of Linux images in the 'Choose a base' step and provide guidance on selecting and configuring a Linux VM.
- Highlight any differences in user account creation, authentication, or artifact installation for Linux VMs.
- Ensure that any automation templates or scripts referenced are OS-agnostic or provide both Windows and Linux variants.
- Add a note or section addressing common Linux-specific considerations (e.g., SSH key setup, default usernames, package management).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-cosmos-db.md
...-manager/management/relocation/relocation-cosmos-db.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently lists Windows-centric tools (Azure portal, Azure PowerShell) before cross-platform options like Azure CLI, and references PowerShell in parallel with the portal and CLI throughout. There are no explicit Linux-only examples or mentions of Linux-native tools, and the ordering and phrasing may imply a preference for Windows/PowerShell environments.
Recommendations
- Alternate the order of tool mentions (e.g., sometimes list Azure CLI before PowerShell) to avoid implying a default preference.
- Provide explicit Linux/macOS usage notes or examples where relevant, especially for command-line operations.
- Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
- Consider including bash shell or script examples alongside PowerShell where command-line usage is demonstrated.
- Where possible, avoid grouping Azure portal and PowerShell together before CLI, or rotate the order to show parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-event-hub-cluster.md
.../management/relocation/relocation-event-hub-cluster.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure Portal (web UI) for all steps and does not provide any command-line examples. There are no references to PowerShell or Windows-specific tools, but the lack of CLI (az), Bash, or Linux-native instructions means Linux users are not given parity in automation or scripting approaches. The workflow implicitly assumes a GUI-first (and thus often Windows-first) environment.
Recommendations
- Add equivalent instructions using the Azure CLI (az) for exporting and deploying Resource Manager templates, including command-line examples for both Windows and Linux environments.
- Include Bash shell examples for Linux users, especially for tasks like unzipping files and deploying templates.
- Mention that all steps can be performed via CLI and provide links to relevant Azure CLI documentation.
- Ensure screenshots and UI references are supplemented with command-line alternatives to support automation and cross-platform usage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-event-grid-system-topics.md
...ment/relocation/relocation-event-grid-system-topics.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and examples, without mentioning or providing alternatives for command-line tools. There are no examples using Azure CLI, Bash, or PowerShell. However, the workflow and screenshots implicitly assume a Windows-centric environment (e.g., references to .zip files, file explorer, and editors), and the lack of CLI examples can disadvantage Linux users who often prefer or require command-line instructions. The absence of Azure CLI or Bash examples constitutes a 'missing_linux_example' bias, and the ordering of instructions (portal-first, no CLI) reflects a 'windows_first' bias.
Recommendations
- Add parallel instructions using Azure CLI for all major steps (exporting templates, modifying JSON, deploying resources, deleting resource groups).
- Include Bash shell examples for Linux users, especially for file extraction and editing.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide cross-platform guidance where relevant.
- Where file operations are described (e.g., unzipping, editing JSON), provide command-line alternatives (e.g., unzip, nano/vim) alongside GUI instructions.
- If PowerShell is relevant, provide equivalent Bash/Azure CLI commands to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-hdinsight.md
...-manager/management/relocation/relocation-hdinsight.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently listing Azure PowerShell as a primary method for exporting and deploying templates, often before or alongside Azure CLI. References to 'Azure Cloud Shell' are present, but there is no explicit mention of Linux shell or Bash-specific instructions. While Azure CLI is included, the ordering and emphasis on PowerShell and VS Code (which is more popular on Windows) suggest a Windows-first perspective. There are no Linux-specific examples or explicit parity for Linux-native tools or workflows.
Recommendations
- Explicitly include Bash or Linux shell examples where relevant, especially for template deployment and export.
- When listing deployment/export options, alternate the order or group Azure CLI and PowerShell together to avoid implying a preference.
- Add a note clarifying that Azure CLI and Cloud Shell are fully cross-platform and can be used from Linux, macOS, or Windows.
- Where VS Code is mentioned, also mention other editors or clarify that VS Code is available on Linux and macOS.
- If possible, provide sample commands for both PowerShell and Bash/Unix shells to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-virtual-machine-scale-sets.md
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing the Azure portal and PowerShell as primary tools, without providing explicit Linux CLI or cross-platform command-line examples. The instructions focus on GUI-based steps, which are more familiar to Windows users, and mention PowerShell as an option for deployment, but do not provide equivalent Bash or Linux-native command-line instructions.
Recommendations
- Include explicit Azure CLI (cross-platform) command examples for each major operation, such as exporting templates, deploying resources, and managing VMSS.
- Provide Linux shell (Bash) script examples alongside or before PowerShell examples to ensure parity.
- Clarify that all steps can be performed using Azure CLI on Linux, macOS, or Windows, and link to relevant CLI documentation.
- Where screenshots or instructions reference the Azure portal, consider adding equivalent command-line steps for users who prefer or require non-GUI workflows.
- Avoid assuming the use of Windows tools or patterns; explicitly mention cross-platform alternatives where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/resource-manager-personal-data.md
...e-manager/management/resource-manager-personal-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently lists Windows PowerShell cmdlets before cross-platform Azure CLI commands in every example. This ordering subtly prioritizes Windows tooling and patterns, which may signal a Windows-centric approach. However, Azure CLI commands (which are cross-platform) are present for all operations, and no examples are missing for Linux users.
Recommendations
- Alternate the order of examples so that Azure CLI commands are listed before or alongside PowerShell cmdlets, especially since Azure CLI is cross-platform.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, to reinforce cross-platform support.
- Consider grouping PowerShell and Azure CLI examples together under clear subheadings (e.g., 'Using Azure CLI', 'Using PowerShell') to avoid implicit prioritization.
- Add a brief note at the start of the examples section clarifying that both PowerShell and Azure CLI are supported, and that users can choose the tool that matches their platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/tag-resources.md
...les/azure-resource-manager/management/tag-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell and REST API as supported interfaces for tag operations before mentioning Azure CLI or Linux-friendly tools. In the 'Required access' section, PowerShell is specifically called out as a supported interface, while CLI is not mentioned until the 'Next steps' section. Additionally, the ordering in 'Next steps' lists Azure PowerShell before Python, ARM templates, and Bicep, which may suggest a Windows-centric perspective.
Recommendations
- Explicitly mention Azure CLI alongside Azure PowerShell and REST API in all sections where command-line interfaces are discussed, especially in 'Required access'.
- In the 'Required access' section, clarify that all tag operations are supported through Azure CLI as well as PowerShell and REST API.
- In 'Next steps', consider listing Azure CLI before PowerShell or in parallel, to avoid implying a preference for Windows tooling.
- Wherever examples or tool references are given, ensure parity by providing both Azure CLI (Linux/macOS/Windows) and PowerShell (Windows/macOS/Linux) options.
- Review the documentation for any implicit assumptions about the user's platform and adjust language to be platform-neutral.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/tag-support.md
...icles/azure-resource-manager/management/tag-support.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely a reference table listing Azure resource types and their tag support, which is generally neutral. However, in the few places where tooling or commands are mentioned, Windows/PowerShell tools are referenced first or exclusively (e.g., 'Set-AzVm -Generalized' before 'az vm generalize'). There are no Linux-specific examples or mentions of Linux tools, and the only CLI example is given after the PowerShell one.
Recommendations
- When referencing commands or tools, always provide both PowerShell (Windows) and Azure CLI (cross-platform) examples, and consider listing the Azure CLI first as it is platform-agnostic.
- If mentioning a Windows-specific tool or pattern, ensure the equivalent Linux/cross-platform method is also described.
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS.
- Review any future additions to ensure parity between Windows and Linux tooling and examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/resource-providers-and-types.md
...rce-manager/management/resource-providers-and-types.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. It references 'Windows Azure Service Management API' in an important note, which is a Windows-centric tool. Additionally, the PowerShell section (a Windows-native tool, though now cross-platform) is presented before the Azure CLI section, which is more platform-agnostic and commonly used on Linux. There are no explicit Linux-only examples or references, and no mention of Linux-specific tools or shell environments. However, the CLI and Python examples are cross-platform, and no examples are strictly Windows-only.
Recommendations
- Remove or clarify references to 'Windows Azure Service Management API' to avoid implying a Windows-only management experience.
- Present Azure CLI examples before PowerShell examples, as CLI is more widely used across platforms, especially on Linux.
- Explicitly mention that Azure CLI and Python examples work on Linux, macOS, and Windows.
- Consider adding a short note or section for Linux/macOS users, confirming parity and highlighting any differences if they exist.
- If referencing PowerShell, clarify that PowerShell Core is cross-platform, and provide installation links for Linux/macOS users.
Azure Docs
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 page focuses on using Azure DevTest Labs in Azure Pipelines but implicitly assumes a Windows/.NET environment by only referencing .NET Core, SQL Database, and ASP.NET Core templates. There are no examples, screenshots, or guidance for Linux-based environments, alternative stacks, or cross-platform considerations. All examples and tasks are tailored to Windows-centric workflows, with no mention of Linux tools, shell scripts, or deployment scenarios.
Recommendations
- Include parallel examples for Linux-based stacks, such as deploying a Node.js or Python app on Linux App Service.
- Show how to use Bash or shell scripts in pipeline tasks alongside or instead of PowerShell/Windows examples.
- Reference Linux VM creation and configuration in DevTest Labs, and provide sample Resource Manager templates for Linux environments.
- Ensure screenshots and walkthroughs include both Windows and Linux scenarios, or clarify that the instructions are applicable to both.
- Mention cross-platform compatibility and provide guidance for users working in non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-history-deletions.md
...urce-manager/templates/deployment-history-deletions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for all relevant operations, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). There are no Linux-specific shell examples (e.g., bash), but the Azure CLI examples use bash syntax, which is suitable for Linux/macOS. No exclusive Windows tools or patterns are used, but the ordering and prominence of PowerShell may suggest a Windows-first bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform.
- Explicitly mention that Azure CLI examples are suitable for Linux/macOS/Windows, and PowerShell examples are primarily for Windows (or PowerShell Core on Linux).
- Where possible, provide bash-specific examples or clarify that the CLI examples are intended for bash/zsh shells.
- Add a note at the start of the examples section explaining which platforms each tool supports, to help users choose the best fit for their environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md
...urce-manager/templates/deployment-tutorial-pipeline.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to 'Git Bash' or 'Git Shell' for command-line operations, which are primarily Windows-centric tools. There are no explicit Linux or macOS terminal instructions or screenshots, and no mention of using a standard Linux shell or terminal. All command-line examples are generic bash commands, but the environment setup and tool references assume a Windows user. There is no guidance for Linux or macOS users regarding prerequisites, environment setup, or alternative tools.
Recommendations
- Explicitly mention that the bash commands work in Linux and macOS terminals, not just Git Bash/Shell on Windows.
- In the prerequisites, add a note for Linux/macOS users to use their native terminal and provide installation instructions for Git on those platforms.
- Where 'Git Bash' or 'Git Shell' is mentioned, rephrase to 'a terminal (such as Git Bash on Windows, or Terminal on Linux/macOS)'.
- Include screenshots or notes that reflect cross-platform usage, or at least clarify that the instructions are platform-agnostic.
- If any step is different on Linux/macOS (such as file path conventions), provide those details.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deploy-what-if.md
...les/azure-resource-manager/templates/deploy-what-if.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell (which is Windows-centric) is consistently presented first in all sections, and all sample outputs are shown in PowerShell syntax. There are no Linux-specific shell examples (e.g., Bash), and the output formatting and explanations are tailored to PowerShell users. While Azure CLI is cross-platform, the documentation does not explicitly address Linux environments or provide Linux-specific guidance, which may disadvantage Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
- Include explicit Bash/Linux shell examples and outputs where relevant, especially for scripting and environment setup.
- Provide sample outputs in both PowerShell and CLI (JSON/text) formats to reflect the experience on different platforms.
- Add notes or sections highlighting any platform-specific considerations (e.g., color output, file paths, environment variables) for Linux/macOS users.
- Ensure installation instructions for Azure CLI and PowerShell clearly indicate cross-platform support and provide Linux/macOS-specific commands where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-tutorial-local-template.md
...anager/templates/deployment-tutorial-local-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Azure PowerShell and Azure CLI, and explicitly states that CLI examples are written for Bash (Linux/macOS). However, there is a subtle Windows bias in the ordering and tool recommendations: Windows tools and installation instructions are listed before Linux/macOS equivalents, and Visual Studio Code (a Microsoft product) is recommended as the editor, with no mention of Linux-preferred alternatives. The 'Get tools' section lists PowerShell (primarily a Windows tool) first, and the Azure CLI installation link for Windows precedes those for Linux and macOS.
Recommendations
- Alternate the order of tool and installation instructions (e.g., list Azure CLI before PowerShell, or rotate the order of OS-specific installation links).
- Explicitly mention that PowerShell is available cross-platform, or clarify that Bash examples are suitable for Linux/macOS users.
- Recommend additional editors commonly used on Linux (such as Vim, Emacs, or nano) alongside Visual Studio Code.
- Ensure that all sections provide equal visibility to Linux/macOS instructions and tools, not just as secondary options.
- Consider including a short note at the top stating that all instructions are cross-platform unless otherwise noted.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-add-parameters.md
...-manager/templates/template-tutorial-add-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying ARM templates, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in every example. There are no Linux-specific shell examples (e.g., Bash), and the clean-up instructions reference only the Azure Portal, not command-line options. The prerequisites mention both Azure PowerShell and CLI, but PowerShell is always presented first, which may subtly prioritize Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to better support Linux/macOS users.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS), and consider providing Bash-specific command examples where appropriate.
- Include command-line instructions for resource clean-up using both Azure CLI and PowerShell, not just Azure Portal steps.
- Where possible, clarify that Visual Studio Code and the Azure Resource Manager Tools extension are cross-platform.
- Add a note or section highlighting that all tasks can be performed on Linux/macOS as well as Windows.