Scan Details - Linux-first Docs for Azure

12938

Pages Scanned

2094

Pages Flagged

12938

Changed Pages

16.2%

% Pages Flagged

Scan Information

Started At: 2025-07-13 21:37:55

Finished At: 2025-07-14 15:52:47

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation prioritizes Windows remediation steps by providing a clear PowerShell example and direct guidance for Windows VMs, while Linux remediation is described in less detail, lacks direct script examples, and is presented as less supported (e.g., 'you don't have the option of using the Run command'). Windows tools and cmdlets are referenced directly, while Linux solutions are only linked or described in passing.

Recommendations:

Provide a direct Linux command-line example (e.g., Bash or Python) for remediating drift, similar to the PowerShell example for Windows.
Clarify and expand on the Linux remediation process, including step-by-step instructions and sample scripts.
Reference Linux-native tools and workflows explicitly, not just through external links.
Present Windows and Linux remediation sections with equal prominence and detail.
If certain features (like Run Command) are unavailable for Linux, suggest alternative Azure-native or open-source solutions, and explain any workarounds.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell commands for critical setup steps (such as creating Teams resource accounts and associating them with Communication Services), referencing Windows-centric tools (PowerShell, Set-CsOnlineApplicationInstance), and omitting equivalent Linux/bash/CLI instructions. The DevTunnel setup also uses PowerShell syntax without clarifying cross-platform support. No Linux or macOS alternatives are mentioned, and the workflow assumes familiarity with Windows tooling.

Recommendations:

Provide equivalent bash/CLI commands for all PowerShell examples, especially for Teams resource account creation and association steps.
Explicitly state whether the PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide alternatives using Azure CLI, Microsoft Graph API, or REST where possible.
For DevTunnel setup, clarify if the tool and commands are cross-platform, and if so, provide examples in both PowerShell and bash syntax.
Add a note in the prerequisites about platform compatibility for all required tools, and link to installation instructions for Linux/macOS users.
Where only Windows tooling is available, acknowledge this limitation and suggest workarounds or alternatives for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or instructions for running the same workflow on Linux or macOS, nor is there mention of cross-platform tools such as Azure CLI. The only automation walkthrough links and commands are for Azure PowerShell, reinforcing a Windows-centric approach.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, including pipeline deployment and execution.
Include Linux/macOS-friendly file path examples (e.g., ~/ADF) alongside Windows paths.
Explicitly mention that Azure CLI and PowerShell are both supported, and provide links to relevant CLI documentation.
Consider providing Bash script examples for automation, or at least note how the process would differ on non-Windows platforms.
Ensure that walkthroughs and tutorials referenced in the documentation include cross-platform coverage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by listing Microsoft Azure Recovery Services (MARS) agent for Azure Backup, which is Windows-only, as the first and only detailed backup solution for VM file/folder recovery, while Linux support is only mentioned in third-party solutions. There are no Linux-specific examples or instructions, and no mention of Linux-native tools or patterns. The documentation also references Windows tools (MARS agent) without Linux equivalents.

Recommendations:

Provide Linux-specific backup and recovery examples, including native Linux tools or Azure-supported Linux backup agents.
List Linux and Windows solutions in parallel, rather than Windows-first, and clarify OS support for each tool.
Include command-line examples for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) where relevant.
If Azure does not offer a first-party Linux backup agent, explicitly state this and recommend best-practice alternatives for Linux users.
Ensure parity in documentation depth for both Windows and Linux recovery workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All file copy examples use Windows-native tools (Robocopy, File Explorer), and the Data Box Disk Split Copy and Validation tools are only available for Windows. There are no Linux-specific examples or equivalent Linux tool recommendations for copying or validating data. Linux users are only briefly mentioned, with no guidance or parity in tooling or workflow.

Recommendations:

Provide equivalent Linux command-line examples for copying data, such as using cp, rsync, or smbclient.
Document how to mount Data Box Disks on Linux, including any required SMB/CIFS options.
Recommend and provide examples of Linux-compatible checksum/validation tools (e.g., sha256sum, md5sum) and describe how to use them for data integrity verification.
Clarify any limitations or differences for Linux users, and offer troubleshooting steps specific to Linux environments.
Where Windows-only tools are referenced, suggest open-source or cross-platform alternatives where possible.
Ensure that screenshots and walkthroughs include Linux desktop or CLI environments where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the certificate generation section by providing only Windows-specific instructions (e.g., opening Command Prompt via Win+R and using Powershell syntax), and does not provide equivalent Linux or macOS command-line examples or guidance. The sample code section assumes usage of Visual Studio and NuGet, which are Windows-centric development tools, without mentioning cross-platform alternatives.

Recommendations:

Provide explicit Linux and macOS instructions for generating certificates with step CLI, including terminal commands and file paths.
Replace or supplement 'open a Command Prompt window (Win+R...)' with cross-platform terminal instructions.
Show bash/zsh shell commands alongside Powershell, or use bash as the default for CLI examples.
Mention and provide instructions for using cross-platform editors (e.g., VS Code) and package managers (e.g., dotnet CLI for NuGet) in the sample code section.
Ensure all steps and tools referenced are available and documented for Linux/macOS users, or clearly link to equivalent guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation shows some Windows bias, primarily by referencing Windows before Linux in the prerequisites, using PowerShell-based includes for resource group creation, and not providing explicit Linux/macOS shell examples for Azure CLI or resource management steps. While the main code samples are cross-platform (Node.js/TypeScript), setup and resource management instructions lean towards Windows/PowerShell without ensuring parity for Linux users.

Recommendations:

Provide explicit Azure CLI examples alongside or instead of PowerShell for resource group creation and provider registration, as Azure CLI is cross-platform.
When referencing prerequisites, list operating systems in a neutral or alphabetical order (e.g., 'Windows, Linux, or macOS') and ensure all steps are validated on each platform.
If using includes that are PowerShell-specific, add parallel includes or inline instructions for Bash/shell environments.
Clarify that all terminal commands (npm, tsc, node) work identically on Linux/macOS, and add notes or troubleshooting tips for common platform-specific issues.
Consider adding a section or callout for Linux/macOS users if any step differs or requires adaptation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples often reference Windows tools and commands first or exclusively (e.g., Control Panel, admin command prompt, PowerShell, Notepad, Windows file paths), and remediation steps for Windows are more detailed than for Linux. In some cases, Linux guidance is present but less prominent or appears after Windows instructions. There are also sections where only Windows-specific tools or patterns are mentioned, and Linux equivalents are missing or less detailed.

Recommendations:

Ensure that for every Windows-specific troubleshooting step (e.g., using Control Panel, PowerShell, Notepad, Windows file paths), an equivalent Linux step is provided, with equal detail and prominence.
Where both Windows and Linux are supported, use parallel tabbed sections or side-by-side examples for commands and file locations.
Avoid using Windows-first language (e.g., 'Open Notepad as an admin' or referencing C:\ paths) without providing the Linux equivalent (e.g., 'Open your preferred text editor as root' and '/etc/hosts').
For sections that reference Windows tools (e.g., WMI, WinRM, Control Panel), include Linux equivalents (e.g., SSH, systemd, chrony/ntpd for time sync) and troubleshooting steps.
When providing code samples, ensure both PowerShell and Bash/SSH examples are present where applicable.
Review the order of presentation so that Linux and Windows are treated with parity, either by alternating order or using tabs, rather than always listing Windows first.
Expand Linux troubleshooting guidance to match the depth and clarity of Windows instructions, especially for common issues like connectivity, authentication, and service management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias in several areas: Windows tools and technologies (such as PowerShell and WMI) are mentioned as requirements, often without equivalent Linux details or alternatives. SQL Server discovery and web app discovery are supported only or primarily for Windows, with Linux support either missing or limited. Example scripts and configuration steps are provided only for Windows authentication scenarios, with no Linux-specific examples. Windows requirements and tools are often listed before Linux equivalents, and some features (like SQL Server discovery) are not supported for Linux at all.

Recommendations:

Provide equivalent Linux examples and instructions wherever Windows-specific tools or scripts are mentioned (e.g., sample scripts for Linux authentication and permissions).
When listing requirements or supported OSes, alternate the order or group Windows and Linux together to avoid always listing Windows first.
Expand support for Linux workloads where possible (e.g., SQL Server on Linux, web app discovery for Linux-based stacks). If not supported, clearly state the roadmap or alternatives.
Where Windows tools (PowerShell, WMI) are required, specify the Linux equivalents (e.g., Bash, SSH, relevant Linux management tools) and provide configuration guidance.
Ensure that all features and workflows are documented for both Windows and Linux, or clearly indicate any limitations or differences in parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell commands for deploying the ARM template, referencing Windows-style file paths (e.g., C:\MyTemplates\azuredeploy.json), and omitting any CLI or Bash/Linux-based deployment instructions. There are no examples or guidance for Linux or cross-platform users, and Windows tools and patterns are presented as the default.

Recommendations:

Add equivalent Azure CLI (az) command examples for deploying the ARM template, with Linux/macOS-friendly file paths (e.g., ~/MyTemplates/azuredeploy.json).
Explicitly mention that both PowerShell and Azure CLI can be used, and provide parallel instructions for each.
Avoid using Windows-specific file paths in examples; use generic or cross-platform paths, or provide both Windows and Linux/macOS variants.
Include a note or section for Linux/macOS users, highlighting any differences or considerations.
Ensure that portal-based instructions are clearly platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed examples and payloads for Windows Store applications (using XML and Windows-specific notification formats) before or instead of Linux/Android equivalents. Windows notification services (WNS, MPNS) and XML payloads are discussed in detail, while Linux/Android (FCM) are only mentioned in passing, with no concrete example payloads or registration templates shown. There are no Linux command-line or tooling examples, and the documentation assumes familiarity with Windows notification paradigms.

Recommendations:

Add explicit example payloads and registration templates for Android (FCM) and other non-Windows platforms, showing both JSON and XML formats as appropriate.
Ensure that examples are balanced: for every Windows-specific example, provide an equivalent for Linux/Android platforms.
Mention Linux/Android tools and notification patterns alongside Windows ones, not just in passing.
Consider reordering examples so that no single platform (such as Windows) is always presented first.
Include a section or appendix on cross-platform tooling and best practices for Linux/Android developers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Windows-centric code examples and patterns. All sample code is written in C# and uses Windows-specific APIs (such as PushNotificationChannelManager and ApplicationData), with no equivalent Linux, Android, or iOS code samples. The documentation discusses secondary tiles and headers specifically for Windows Store apps, and does not mention or demonstrate how to perform similar registration management from non-Windows platforms or with cross-platform tools. There are no Linux command-line, REST/cURL, or non-Windows SDK examples provided.

Recommendations:

Add code samples for Linux, Android, and iOS platforms, using their respective notification APIs and SDKs.
Provide REST API examples using cURL or HTTP libraries in languages common on Linux (e.g., Python, Node.js) to demonstrate cross-platform registration management.
Include equivalent instructions and code snippets for managing device registration from non-Windows backends (e.g., running on Linux servers).
Document any platform-specific differences or requirements for registration, and ensure that Windows-specific features (like secondary tiles) are clearly marked as such, with alternatives or notes for other platforms.
Reorganize sections so that platform-agnostic or cross-platform approaches are presented before or alongside Windows-specific guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using an ASP.NET (Windows-centric) backend for the server-side component, without mentioning or providing examples for Linux-friendly alternatives such as Node.js, Python (Flask/Django), or Java. The backend setup and all code samples assume a Windows development environment and toolchain. There are no instructions or references for setting up or deploying the backend on Linux, nor are there cross-platform command-line or deployment examples. The only backend technology mentioned is ASP.NET, which is traditionally associated with Windows, even though .NET Core is cross-platform.

Recommendations:

Provide alternative backend implementation examples using popular Linux-friendly stacks (e.g., Node.js/Express, Python/Flask, Java/Spring Boot) alongside the ASP.NET example.
Include instructions for deploying the backend on Linux-based environments (e.g., Ubuntu, Docker) and not just Azure App Service.
When referencing backend technologies, mention cross-platform options and clarify that .NET Core can run on Linux.
Add Linux/macOS command-line instructions where relevant (e.g., for project setup, deployment, or testing), not just Windows/PowerShell.
Explicitly state that the backend can be implemented and hosted on Linux, and provide links to relevant documentation for cross-platform development.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: it directs users to create and validate private endpoints using Windows-centric tools and workflows, such as referencing the creation of a Windows VM and providing only a PowerShell (Resolve-DnsName) command for DNS validation. There are no equivalent instructions or examples for Linux users (e.g., using dig or nslookup), and the validation steps are explicitly tied to Windows environments. The documentation also references Windows tools and patterns before any cross-platform or Linux alternatives.

Recommendations:

Provide parallel Linux examples for all validation and management steps, such as using dig or nslookup for DNS resolution.
When instructing users to create a VM for validation, offer both Windows and Linux VM creation links and instructions.
Avoid referencing only Windows-specific tools (e.g., PowerShell) in validation steps; include cross-platform alternatives.
Ensure screenshots and walkthroughs are not exclusively from Windows environments, or supplement them with Linux equivalents.
Explicitly state that all CLI steps are cross-platform and clarify any OS-specific requirements or differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exclusively provides an Azure PowerShell example (Remove-AzResourceGroup) for deleting a resource group, with no mention of equivalent commands or instructions for Linux users (e.g., Azure CLI or Bash). Only Windows-centric tools and patterns are referenced, and no Linux or cross-platform alternatives are presented.

Recommendations:

Add an Azure CLI example (e.g., az group delete --name myResourceGroup) alongside the PowerShell example.
Include Bash shell instructions for Linux/macOS users.
Present both Windows and Linux examples in parallel tabs or sections to ensure parity.
Avoid referencing only Windows tools; mention cross-platform tools like Azure CLI where possible.
Consider reordering or presenting examples in a way that does not prioritize Windows tools over Linux equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively uses PowerShell and Az PowerShell module examples, both in Azure Cloud Shell and for local use, without providing any Bash, Azure CLI, or Linux-native alternatives. All command-line instructions and tooling references are Windows-centric, with no mention of Linux or cross-platform approaches.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux and macOS.
Include Bash shell instructions for users who prefer or require a Linux-native environment.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select or switch between them.
Reference installation instructions for Azure CLI on Linux, in addition to PowerShell module installation.
Ensure that all steps (such as resource group creation) have both PowerShell and CLI/Bash code blocks, clearly labeled.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_heavy_examples

Summary:

The documentation demonstrates a clear Windows bias. Windows platforms (WNS, MPNS) and related credential objects are consistently mentioned first and in greater detail than their Linux or cross-platform counterparts. Many code examples focus on Windows-specific push notification services (WNS, MPNS), and Windows credential setup is shown as the primary example. There is no mention of Linux-specific tools, shell commands, or development patterns, and the documentation assumes familiarity with Windows notification concepts.

Recommendations:

Provide equal prominence to Android (FCM) and iOS (APNS) examples and credential setup, not just Windows.
Include Linux/macOS shell command equivalents (e.g., show how to build with Maven using bash/sh, not just 'cmd').
Reorder examples so that cross-platform or most widely-used platforms (Android/iOS) are presented before or alongside Windows.
Add explicit notes or sections for Linux/macOS users, including troubleshooting and environment setup.
Ensure that links and sample projects are not Windows-centric and include cross-platform sample apps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing Windows-specific path length limits, using a Windows-style filesystem example (drive letters, backslashes), and omitting any Linux or cross-platform filesystem examples or considerations. There are no Linux or POSIX path examples, and no mention of Linux path length limits or filesystem conventions.

Recommendations:

Include Linux/POSIX filesystem examples alongside Windows examples, using forward slashes and typical Linux directory structures.
Mention Linux path length limits and any relevant differences in file naming or path conventions.
Avoid using only Windows drive letters (e.g., G:\) in examples; provide parallel Linux examples (e.g., /mnt/conversion/...).
Clarify that the service is cross-platform (if applicable), and note any platform-specific considerations for both Windows and Linux users.
Where referencing documentation (such as path length limits), provide links or notes for both Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias primarily in the 'Automation and control: Alert on security configuration drifts' section, where only PowerShell and PowerShell Desired State Configuration (DSC) are mentioned for automation and configuration management. There are no references to Linux-native tools or cross-platform scripting alternatives, and no examples are provided for Linux users. Additionally, the mention of 'malicious PowerShell scripts' as a threat vector is not balanced with equivalent Linux scripting threats (e.g., Bash scripts).

Recommendations:

Include examples and references for Linux-native automation tools, such as Bash scripts, Ansible, or Chef, alongside PowerShell/DSC.
Mention and provide guidance for using Azure Automation with Linux VMs, including supported scripting languages and configuration management options.
Balance the discussion of scripting threats by mentioning Linux shell scripts and common Linux attack vectors in addition to PowerShell.
Where PowerShell is referenced, clarify cross-platform support (e.g., PowerShell Core on Linux) and provide Linux-specific usage notes or examples.
Ensure that all configuration and automation guidance is presented in a cross-platform manner, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only Azure PowerShell examples for verifying results, with no equivalent instructions for Linux-native tools, Azure CLI, or Bash scripting. This creates a bias toward Windows users and PowerShell environments, potentially making it harder for Linux or cross-platform users to follow the verification steps.

Recommendations:

Add equivalent verification instructions using Azure CLI (az storage-action-task show ...) and Bash shell commands.
Present both PowerShell and CLI/Bash examples side by side using tabs or clear sections.
Ensure that all steps that use PowerShell or Windows-specific tools have Linux-friendly alternatives.
Review other sections for implicit assumptions about the user's shell or environment, and clarify when instructions are cross-platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions for defining a migration job using the Azure Portal and PowerShell, with all CLI-based examples using PowerShell cmdlets. There are no examples or references for Linux-native tools, Bash, or Azure CLI, and PowerShell is presented as the only scripting/automation option. This creates a Windows-centric experience, potentially excluding Linux users or those who prefer cross-platform tools.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets shown, ensuring Linux and macOS users can follow along without needing PowerShell.
Explicitly mention that PowerShell examples are cross-platform if true, or clarify any Windows-specific requirements.
Include Bash script examples or guidance for Linux environments where appropriate.
Reference Linux-native tools or workflows (e.g., az CLI, shell scripting) alongside PowerShell, not just after or as an afterthought.
Ensure that any screenshots or UI instructions do not assume a Windows environment (e.g., file paths, UI conventions).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a significant Windows bias, particularly in the command-line and scripting sections. All automation and scripting examples are provided exclusively using PowerShell, a tool primarily associated with Windows environments (despite its cross-platform support, it is still less common on Linux). There are no CLI, Bash, or Linux-native command examples, nor is there mention of using the Azure CLI or REST API, which are more typical in Linux workflows. The prerequisite and walkthrough sections also reference patterns and tools familiar to Windows users (e.g., Outlook-style calendar, PowerShell, and Windows-centric terminology), with no Linux-first or cross-platform parity.

Recommendations:

Provide equivalent examples using Azure CLI (az), which is widely used on Linux and macOS, alongside PowerShell.
Include Bash shell scripting examples for schedule management, or at least show how to use curl or other Linux-native tools to interact with the relevant Azure REST APIs.
Explicitly mention that PowerShell Core is cross-platform, but clarify installation steps for Linux and macOS users.
Balance screenshots and terminology to reference both Windows and Linux environments (e.g., compare Outlook calendar to common Linux calendar tools, or use more neutral language).
Add a section or callout for Linux users, outlining any differences or additional steps required.
Reference documentation for managing Storage Mover agents from Linux systems, if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation method, with detailed instructions and examples. There are several references to Windows-specific tools (e.g., Windows PowerShell as a console example), and PowerShell is mentioned before Azure CLI in most sections. While Azure CLI examples are provided (which are cross-platform), the documentation sometimes defaults to Windows-centric language and patterns, such as suggesting Windows PowerShell as the default local CLI environment, and does not explicitly mention or show Linux/macOS terminal usage or shell conventions.

Recommendations:

Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts for Bash (e.g., $) as well as PowerShell (e.g., PS>), or use neutral prompts.
When referencing command-line environments, mention Bash or other Linux/macOS shells alongside Windows PowerShell.
Balance the ordering of PowerShell and Azure CLI sections, or alternate their order to avoid always listing PowerShell first.
Where possible, provide Bash-specific notes or examples, especially for multi-line commands or environment variable usage.
Avoid language that assumes the user is on Windows (e.g., 'open a command console application such as Windows PowerShell'); instead, use neutral phrasing like 'open a terminal or command prompt.'

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows (Visual Studio, PowerShell), providing explicit instructions and screenshots for Visual Studio (a Windows-centric IDE), and using PowerShell for resource cleanup without offering equivalent Linux/bash alternatives. While the .NET CLI is mentioned and bash is referenced in passing, Linux-specific guidance, troubleshooting, or examples are missing, especially for resource cleanup and IDE/editor usage.

Recommendations:

Provide explicit Linux/bash alternatives for all command-line instructions, especially for resource cleanup (e.g., show az CLI or bash commands alongside PowerShell).
Include screenshots and instructions for cross-platform editors like Visual Studio Code, not just Visual Studio 2022.
When referencing opening the project, include Linux-friendly editors (e.g., code . for VS Code, or instructions for JetBrains Rider).
In the prerequisites, clarify that .NET Core/.NET 6+ is cross-platform and provide installation links for Linux and macOS, not just .NET Framework (which is Windows-only).
For package management, mention that the dotnet CLI is available on Linux and macOS, and provide troubleshooting steps relevant to those platforms.
Where PowerShell is used (e.g., resource cleanup), provide an equivalent az CLI command (e.g., az group delete) and show both side-by-side.
Ensure that all instructions, especially those involving file paths, environment variables, or shell commands, are cross-platform or have platform-specific notes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows (such as Visual Studio and .sln files), providing Windows command examples before Linux ones, and focusing on Windows-centric project setup. Linux alternatives are sometimes mentioned but are less detailed or appear after Windows instructions. There is little guidance for Linux-native development environments or editors, and the project creation flow is tightly coupled to Visual Studio on Windows.

Recommendations:

Provide equal prominence to Linux development workflows, such as using CMake or Makefiles, and include instructions for setting up projects in popular Linux IDEs (e.g., CLion, Qt Creator, VS Code) or via command line.
When showing environment variable setup, present Linux and Windows instructions side-by-side or in tabs, rather than listing Windows first.
Offer code snippets and project setup instructions that are platform-agnostic or provide parallel instructions for both Windows and Linux.
Avoid assuming Visual Studio as the default IDE; mention cross-platform alternatives and provide guidance for both.
Include Linux-specific troubleshooting tips or notes where relevant, especially for dependency installation and environment configuration.
Ensure all screenshots and step-by-step guides have Linux equivalents or clarify when a step is Windows-only.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides both Windows and Linux command-line examples for static route manipulation, but the Fiddler-based failure simulation method is Windows-specific and lacks any Linux or cross-platform alternative. Additionally, Fiddler is introduced as a primary method without mentioning its Windows-only nature or suggesting Linux equivalents. In some instructions, Windows is mentioned first, and the overall flow assumes familiarity with Windows tools.

Recommendations:

For the Fiddler section, explicitly state that Fiddler is a Windows-only tool and provide equivalent instructions for Linux users, such as using mitmproxy or similar cross-platform tools.
When introducing tools or commands, present Linux and Windows options in parallel, rather than defaulting to Windows-first phrasing.
Add a section or callout for Linux/macOS users that describes how to simulate HTTP failures using open-source, cross-platform tools.
Where screenshots or UI steps are shown for Windows-only tools, provide comparable visuals or command-line steps for Linux alternatives.
Review the prerequisites and tool recommendations to ensure Linux users are not left without guidance for any step.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides PowerShell examples for all code scenarios, but does not provide equivalent Linux shell (bash/CLI) examples. The setup instructions for .NET reference 'command prompt' (a Windows term) and do not mention cross-platform shells. The PowerShell examples use Windows-specific tools and patterns, and are always presented first in each code tab group, indicating a 'Windows-first' ordering. There are no bash, Azure CLI, or Linux-native scripting examples, and no mention of Linux-specific tools or environments.

Recommendations:

Add equivalent Azure CLI (az storage blob query) or bash scripting examples alongside PowerShell for all scenarios.
In setup instructions, use cross-platform terminology such as 'terminal' instead of 'command prompt', and clarify that commands work on Windows, Linux, and macOS.
Alternate the order of code tabs or default to a more neutral SDK (such as Python or JavaScript) to avoid a Windows-first impression.
Explicitly mention that PowerShell examples can be run on PowerShell Core on Linux/macOS, or provide bash alternatives.
Review all references to Windows-specific tools and ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias by presenting PowerShell as a primary upgrade method, listing it before Azure CLI, and referencing PowerShell-specific modules and installation instructions. While Azure CLI is included (which is cross-platform), there are no explicit Linux/bash examples, nor is there mention of Linux-specific considerations or parity in tooling. The documentation assumes familiarity with PowerShell and Windows-centric patterns.

Recommendations:

Provide explicit bash/Linux shell examples alongside or before PowerShell examples, especially for Azure CLI commands.
Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, possibly linking to Linux-specific installation instructions.
Avoid listing PowerShell before Azure CLI unless there is a clear reason; consider alternating order or presenting CLI first for broader platform neutrality.
Mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and provide guidance for Linux/macOS users.
Add a section or note addressing Linux/macOS users, highlighting any differences or confirming parity in the upgrade process.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias. Scripted/programmatic transfer tools list 'Azure PowerShell' before 'Azure CLI', and the 'Next steps' section links to a PowerShell quickstart before the Azure CLI equivalent. There are no explicit Linux or Bash/Shell examples or references, and the focus on PowerShell may suggest a Windows-centric approach. No Linux-specific tools or workflows are mentioned.

Recommendations:

Ensure that Azure CLI and Bash/Shell examples are presented alongside or before PowerShell examples, especially in quickstarts and code snippets.
Explicitly mention Linux/macOS compatibility for tools like AzCopy and Azure CLI.
Include links to Linux/Bash quickstarts or tutorials where available.
Balance references to PowerShell and CLI in both the main text and 'Next steps' section.
Consider adding a table or section comparing tool usage across Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows, as the Azure Storage Emulator is only available for Windows. All setup, usage, and command-line instructions are Windows-specific, referencing Windows tools (SQL Server LocalDB, SSMS, Windows authentication, Windows taskbar, Command Prompt). The only code example for generating a SAS token uses Azure PowerShell, with no Linux or cross-platform CLI alternatives. While Azurite is mentioned as the cross-platform replacement, no practical Linux or Azurite usage examples are provided, and the documentation does not guide Linux/macOS users on equivalent workflows.

Recommendations:

Add a clear section or callout at the top directing Linux/macOS users to Azurite, with a link to detailed Azurite setup and usage documentation.
Provide parallel examples for Azurite, including installation (npm, Docker), starting the emulator, and connecting to it from code.
Include cross-platform command-line examples (e.g., Azure CLI, Bash) for generating SAS tokens and interacting with the emulator, not just PowerShell.
Mention and demonstrate how to use Azurite with popular Linux tools and shells.
Where Windows-specific tools are referenced (e.g., SSMS, LocalDB), suggest cross-platform alternatives or clarify their scope.
Ensure that all code and workflow examples have Linux/macOS equivalents or clear guidance for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows tools and scripts (e.g., PowerShell, iscsicli, mpclaim) are often mentioned first or exclusively, and some troubleshooting steps provide detailed instructions or scripts for Windows before Linux equivalents. In some sections, Linux examples are present but less detailed or referenced after Windows. There are also cases where only Windows session limits or tools are discussed, and Linux-specific details are less prominent.

Recommendations:

Ensure that for every Windows tool or script mentioned (e.g., iscsicli, mpclaim, PowerShell scripts), the equivalent Linux command or script (e.g., iscsiadm, multipath, bash/python scripts) is provided with equal detail and prominence.
Present Linux and Windows instructions in parallel or side-by-side, rather than listing Windows first by default.
Where session limits or configuration parameters are discussed for Windows, provide the corresponding Linux values and commands.
Expand Linux troubleshooting steps to match the depth and clarity of Windows steps, including direct command examples and links to scripts.
Review the order of examples and ensure Linux is not consistently presented after Windows, to avoid reinforcing a Windows-first perspective.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. It exclusively references Windows Server concepts (e.g., NTFS, Windows Server data deduplication, Event Viewer), uses Windows-specific terminology (e.g., reparse points, FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS), and provides operational examples only for Windows (such as the PowerShell cmdlet Invoke-StorageSyncFileRecall). There are no Linux equivalents, examples, or mentions of cross-platform support, and the documentation assumes the reader is operating in a Windows environment.

Recommendations:

Clarify early in the documentation whether Azure File Sync and cloud tiering are supported on Linux, and if not, state this explicitly.
If Linux support exists, provide equivalent examples for Linux environments, including command-line operations, file attribute handling, and monitoring/logging instructions.
Reference Linux file systems (e.g., ext4, XFS) and their handling of file metadata and access times, if applicable.
Include Linux-native tools or commands for checking file status, disk space, and event logs.
Avoid assuming NTFS or Windows-specific features (such as reparse points or Event Viewer) are universally available; provide cross-platform alternatives or note limitations.
If PowerShell cmdlets are mentioned, provide equivalent shell or scripting examples for Linux (e.g., Bash).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell instructions, referencing Windows PowerShell specifically, and suggesting opening a 'Windows PowerShell command window.' The Azure CLI section also suggests using 'Windows PowerShell' as a console, and does not mention Linux or macOS terminals. There are no explicit Linux/macOS shell examples or guidance, and no mention of Linux-native tools or environments. The documentation assumes a Windows-centric workflow and omits parity for Linux users.

Recommendations:

In the PowerShell section, clarify that Azure PowerShell can be used on Windows, Linux, and macOS, and provide instructions for all platforms.
In the Azure CLI section, recommend using Bash or other Linux/macOS terminals as alternatives to Windows PowerShell, and provide examples or screenshots from those environments.
Wherever 'Windows PowerShell' is mentioned, generalize to 'PowerShell' and note cross-platform compatibility.
Add explicit Linux/macOS instructions or notes for command-line steps, including any differences in command syntax or prerequisites.
Ensure that screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux/macOS where possible.
Mention Linux-native tools or scripting environments (e.g., Bash, zsh) as valid options for running Azure CLI commands.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the recovery process is performed exclusively on Windows Server or Azure VMs running Windows. All instructions reference Windows-specific tools (e.g., Robocopy), and there are no examples or guidance for performing the same tasks on Linux servers. The agent installation and registration steps are also linked specifically to Windows Server documentation, with no mention of Linux compatibility or alternatives.

Recommendations:

Explicitly state whether Azure File Sync is supported on Linux, and if not, clarify this early in the documentation.
If Linux is supported, provide equivalent instructions and examples for Linux environments, including alternative tools (e.g., rsync instead of Robocopy) and Linux-specific agent installation steps.
If only Windows is supported, add a clear note at the beginning of the article to inform users.
Where possible, use cross-platform terminology and provide parity in examples for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall), using Windows-style file paths (e.g., F:\sync1), and mentioning Windows tools (RoboCopy) as behavioral analogies. There are no Linux-specific instructions, examples, or tool references, and no mention of Linux support or parity for Azure File Sync server endpoints.

Recommendations:

Explicitly state platform support (Windows, Linux) for Azure File Sync server endpoints at the beginning of the documentation.
If Linux is supported, provide equivalent Linux command-line examples (e.g., bash scripts, relevant Linux tools) alongside PowerShell examples.
Replace or supplement Windows-specific path examples (e.g., F:\sync1) with Linux-style paths (e.g., /mnt/sync1) where appropriate.
If certain features or tools (like RoboCopy or PowerShell cmdlets) are only available on Windows, clearly note this and suggest Linux alternatives if possible.
Include troubleshooting and management instructions for Linux servers if they are supported, or clearly state if only Windows is supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All instructions, examples, and tooling references are exclusively for Windows Server, with no mention of Linux or cross-platform support. PowerShell is the only scripting interface shown, and all file paths, configuration steps, and screenshots are Windows-specific. There is no guidance for Linux servers, nor any indication that Azure File Sync can be used outside of Windows.

Recommendations:

Clearly state in the introduction whether Azure File Sync supports only Windows Server or if there is any Linux support. If Linux is not supported, make this explicit to set user expectations.
If Linux support exists or is planned, add equivalent Linux instructions, including command-line examples (e.g., Bash, Azure CLI), package installation steps, and configuration file locations.
Where PowerShell is used, provide Azure CLI or REST API equivalents for cross-platform automation.
If certain features (e.g., agent installation, server registration) are Windows-only, explicitly note this and provide alternative Azure file integration solutions for Linux users.
Avoid Windows-centric terminology and screenshots unless the feature is strictly Windows-only; otherwise, include Linux or generic alternatives.
For proxy configuration and network limits, describe how to achieve similar results on Linux systems, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently listing Windows-centric tools (Azure PowerShell) before cross-platform alternatives (Azure CLI), and by referencing PowerShell in key usage examples. There are no explicit Linux or Unix-specific examples or guidance, and Windows/SMB scenarios are implicitly prioritized (e.g., in the redundancy matrix and failover instructions). No Linux/NFS-specific failover or recovery workflows are described.

Recommendations:

Ensure that all command-line examples are provided for both Azure PowerShell and Azure CLI, with equal prominence and in parallel sections.
Explicitly mention and provide examples for Linux/NFS scenarios, including how to handle failover and remounting from Linux clients.
When referencing tools or commands, avoid listing Windows/PowerShell first by default; alternate or present both together.
Include a section or callout for Linux administrators, outlining any differences or considerations for disaster recovery and failover with NFS shares.
In the redundancy matrix and throughout the document, clarify the parity (or lack thereof) between SMB (Windows) and NFS (Linux) support for DR features.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page shows a mild Windows bias in the 'Next steps' section, where Windows-centric tools and workflows (PowerShell, Visual Studio) are listed before cross-platform or Linux-friendly options (Azure CLI, Visual Studio Code). There is a dedicated PowerShell quickstart, and Visual Studio (Windows-only) is mentioned before Visual Studio Code. No Linux-specific examples or tools are highlighted, and there is no mention of Linux shell or scripting environments.

Recommendations:

List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio) in the 'Next steps' section.
Explicitly mention Linux and macOS compatibility where applicable, especially for Azure CLI and Visual Studio Code.
Provide Linux shell (bash) examples or references alongside PowerShell examples.
Add a note clarifying which tools are cross-platform and which are Windows-only.
Consider including a Linux-specific quickstart or troubleshooting guide.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page exhibits subtle Windows bias, particularly in the 'Next steps' section, where Windows-centric tools (PowerShell, Visual Studio) are listed before or alongside cross-platform alternatives. There is a dedicated quickstart for Azure PowerShell and Visual Studio (both Windows-focused), while Linux-native or cross-platform command-line examples (like Bash or Linux shell) are not specifically highlighted. No explicit Linux examples or tools are mentioned, and the ordering of next steps may suggest a preference for Windows environments.

Recommendations:

Add explicit Linux/bash shell examples or quickstarts, especially for common tasks (e.g., using Azure CLI from Bash).
Ensure that cross-platform tools (Azure CLI, Visual Studio Code) are listed before or at least alongside Windows-specific tools in 'Next steps'.
Include notes or sections clarifying that all features and instructions apply equally to Linux and macOS environments where applicable.
Where PowerShell is mentioned, also provide equivalent Bash or shell commands for Linux users.
Consider adding a table or section comparing tool availability and usage across Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing Windows file paths (e.g., C:\Users\Downloads), and instructing users to use PowerShell for Azure CLI operations. There are no Linux/macOS equivalents or notes, and instructions such as 'right-click and copy the path' are Windows-specific. No mention is made of Linux or cross-platform considerations, despite Azure CLI being cross-platform.

Recommendations:

Provide command-line examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, especially for Azure CLI commands.
Use generic or platform-neutral file paths in examples (e.g., /home/user/Downloads/isrgrootx1.pem for Linux/macOS).
Add notes or sections explaining how to perform steps (such as copying file paths) on Linux/macOS.
Explicitly state that Azure CLI can be used on Windows, Linux, and macOS, and link to relevant installation guides for each platform.
Where screenshots or UI steps are shown, clarify if there are any platform-specific differences or confirm that the steps are the same across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the prerequisites, Windows (PowerShell) and Linux (wget) are both mentioned, but Windows/PowerShell is listed second. However, in the hosts file editing section, the Windows path is listed before the Linux path, and the instructions for testing endpoints reference Windows-specific tools and locations first. There is also an assumption of familiarity with Windows tools and patterns (such as 'Invoke-WebRequest' and the Windows hosts file path), and PowerShell is mentioned as the Windows method for HTTP requests, with no mention of curl, which is available on both platforms.

Recommendations:

When listing tools or commands, present cross-platform options side-by-side (e.g., 'Use wget or curl on Linux/macOS, or Invoke-WebRequest or curl on Windows').
Alternate the order in which Windows and Linux instructions are presented, or provide both together where possible.
In hosts file editing instructions, mention both Windows and Linux paths together, or start with Linux to balance representation.
Include curl as a cross-platform HTTP request tool, since it is available on both Windows and Linux.
Where possible, provide explicit Linux/macOS shell command examples alongside Windows/PowerShell examples.
Avoid assuming the user is more familiar with Windows tools or patterns.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, and does not explicitly mention Linux-native tools or provide Linux-specific examples. The ordering and tool selection suggest a Windows-first approach, with limited visibility for Linux users.

Recommendations:

Ensure that Linux-native tools (such as Bash scripts or Linux command-line examples) are included and highlighted equally.
Reorder the list or randomize the order to avoid always placing Windows tools first.
Add explicit Linux examples or links to Linux-specific documentation.
Clarify in the documentation that Azure CLI and Portal are cross-platform, and provide usage notes for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses variable assignment syntax ($token=...) that is specific to PowerShell or Windows Command Prompt, without providing equivalent examples for Bash or Linux shells. This may confuse Linux/macOS users, as the syntax is not portable. The documentation implicitly assumes a Windows environment, omitting Linux-specific guidance or examples.

Recommendations:

Provide both PowerShell/Windows and Bash/Linux command examples for variable assignment and usage.
Explicitly mention which shell the example is intended for, and offer alternatives for other platforms.
Add a note clarifying that the Azure CLI works cross-platform, and show how to adapt the commands for different environments.
Consider using syntax highlighting or code block labels (e.g., 'bash', 'powershell') to distinguish between examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by specifically referencing Windows operating systems (Windows 10, 8.1, 8, 7) and their compatibility with cipher suites, while omitting any mention of Linux or macOS client compatibility. There are no examples or notes for Linux users, and the only client-side guidance is Windows-specific. No Linux tools, distributions, or configuration patterns are mentioned.

Recommendations:

Add equivalent compatibility notes for common Linux distributions (e.g., Ubuntu, CentOS) and macOS, specifying which cipher suites are supported by default in OpenSSL or GnuTLS.
Include example commands or configuration snippets for verifying TLS/cipher support on Linux (e.g., using openssl s_client).
Mention how to update or configure cipher suites on Linux systems, or link to relevant documentation.
Ensure that client compatibility guidance is cross-platform, not Windows-only, and appears in a platform-neutral order or with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by repeatedly referencing Windows-specific audit controls, tools, and extensions (such as the Microsoft IaaSAntimalware extension and auditing the Windows Administrators group) without providing equivalent Linux examples or controls. In several sections, only Windows VMs or Windows web servers are mentioned for auditing or security checks, while Linux VMs are either omitted or only referenced in a limited context. Antivirus and endpoint protection recommendations are also Windows-centric, and there is a lack of parity in Linux-specific guidance for several controls.

Recommendations:

For every control or recommendation that references Windows VMs, provide equivalent guidance and Azure Policy mappings for Linux VMs (e.g., audit sudoers or root group membership for Linux).
When mentioning tools like Microsoft IaaSAntimalware extension (Windows-only), also mention and recommend supported Linux antimalware/endpoint protection solutions.
Where audit results or prerequisites are listed for Windows (e.g., Administrators group, Security Settings - Account Policies), include parallel examples for Linux (e.g., /etc/passwd, /etc/group, PAM configuration, SSH settings).
For web server security controls, include Linux-based web servers (Apache, Nginx) in audit recommendations and secure communication protocol checks.
Ensure that endpoint protection, vulnerability assessment, and backup recommendations explicitly cover both Windows and Linux environments, with clear instructions or links for each.
Review all sections for Windows-centric language and update to use inclusive phrasing (e.g., 'Windows or Linux VMs') where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Many control mappings and policy definitions specifically reference Windows virtual machines, Windows-specific settings (such as password policies and antimalware extensions), and Windows tools, often without providing equivalent Linux examples or parity. In several sections, Windows controls are listed before Linux ones, and some controls (e.g., password complexity, antimalware) are only described for Windows, with no mention of Linux equivalents or best practices. Linux is referenced in some areas (e.g., auditing accounts without passwords, Log Analytics agent deployment), but coverage is less comprehensive and often appears after Windows content.

Recommendations:

For every Windows-specific policy or example, provide an equivalent Linux policy or example where applicable (e.g., password complexity, antimalware/endpoint protection, auditing domain membership).
Ensure Linux controls and examples are presented with equal prominence and detail as Windows ones, rather than as secondary or afterthoughts.
Where a feature is not available for Linux, explicitly state this and, if possible, suggest alternative approaches or workarounds.
Expand documentation for Linux-specific security practices (e.g., password file permissions, PAM configuration, Linux antimalware solutions) to match the depth of Windows coverage.
Review the order of presentation to avoid consistently listing Windows controls before Linux ones; alternate or group by OS where appropriate.
Audit for missing Linux coverage in areas such as password policy enforcement, domain join auditing, and endpoint protection, and add relevant content.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments in the 'Business intelligence on HDInsight' section, where only Windows-based tools (Power Query, Microsoft Hive ODBC Driver, Excel integration) are mentioned or explicitly required. There are no Linux or cross-platform BI tool examples provided. Additionally, the development tools section lists Visual Studio and other Microsoft-centric tools before mentioning cross-platform options, and there is no mention of Linux alternatives or parity for BI integration.

Recommendations:

Include examples and guidance for connecting to HDInsight from BI tools available on Linux, such as Tableau, Qlik, or open-source alternatives (e.g., Apache Superset, DBeaver).
Provide instructions for using ODBC/JDBC drivers on Linux and macOS, not just Windows.
When listing development tools, give equal prominence to cross-platform IDEs (e.g., VS Code, IntelliJ, Eclipse) and clarify their OS compatibility.
Explicitly state when a feature or tool is Windows-only, and offer Linux/macOS alternatives where possible.
Add sample walkthroughs or links for BI/reporting integration from non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-related artifacts and parameters in both descriptions and examples. Windows VM administration and domain join are discussed in detail, while Linux equivalents are mentioned only in passing or as secondary considerations. There are no Linux-specific usage examples, and Windows terminology (e.g., 'Administrators group', 'domain join') is used exclusively where cross-platform alternatives could be provided.

Recommendations:

Provide Linux-specific examples and instructions alongside Windows ones, especially for tasks like VM administration and domain join.
Balance the artifact parameter table by including Linux-focused parameters and descriptions where applicable (e.g., mention Linux admin groups or domain join alternatives).
Avoid listing Windows artifacts and parameters before Linux ones unless there is a technical reason; consider alternating or grouping by OS.
Use neutral, cross-platform terminology where possible (e.g., 'administrator group' instead of 'Windows VM Administrators group').
Include guidance or links for managing Linux VMs (e.g., joining to a domain, configuring admin users) to achieve parity with the Windows instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists several development tools (IntelliJ, Eclipse, VS Code, Visual Studio) for configuring Apache Spark applications, but only the Visual Studio tool is Windows-specific and is mentioned alongside cross-platform tools. There is a lack of explicit Linux command-line or shell examples, and the documentation does not provide parity in showing Linux-native troubleshooting steps or tools. The ordering of tools and examples sometimes places Windows-centric options (Visual Studio) before or alongside cross-platform ones, without clarifying platform support.

Recommendations:

Clearly indicate which tools are cross-platform and which are Windows-only (e.g., Visual Studio).
Provide explicit Linux shell/command-line examples for common troubleshooting tasks, not just tool-based workflows.
When listing tools, group or order them by platform (cross-platform first, then Windows-only), or clearly label them.
Add more Linux-specific troubleshooting steps and highlight any differences in workflows between Windows and Linux environments.
Ensure that all examples and guides are available for both Windows and Linux users, or provide equivalent alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell explicitly as the primary scripting tool for deploying HDInsight clusters, both in the introduction and in the note about VM SKU identifiers. There are no Linux shell (bash) examples or explicit mentions of Linux-native tools or workflows. The guidance assumes familiarity with PowerShell, and Linux alternatives are not provided or mentioned.

Recommendations:

Include explicit bash/Azure CLI examples alongside PowerShell references for deploying HDInsight clusters.
Rephrase instructions to mention both PowerShell and bash equally (e.g., 'when creating deployment scripts using PowerShell or bash').
Add notes or examples for Linux users, such as how to obtain VM SKU identifiers using bash or Azure CLI.
Avoid assuming PowerShell as the default scripting environment; use neutral language or provide parity.
Where possible, provide links to both Windows and Linux scripting documentation for Azure.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of Microsoft Power BI Desktop, which is only available for Windows, and does not mention or provide alternatives for Linux users. All instructions and screenshots are specific to Power BI Desktop, with no discussion of cross-platform or Linux-compatible visualization tools. The prerequisites and workflow are Windows-centric, and there is no guidance for users on Linux or macOS.

Recommendations:

Explicitly state that Power BI Desktop is Windows-only and mention this limitation in the prerequisites.
Provide alternative instructions or recommendations for Linux users, such as using Power BI Service (web), Apache Zeppelin, Jupyter Notebooks, or other cross-platform BI tools.
Include links or references to Linux-compatible visualization tools that can connect to Hive/HDInsight, such as Apache Superset, Tableau (if available), or open-source alternatives.
Add a section comparing available visualization options for different operating systems, with step-by-step guides for at least one Linux-compatible tool.
Ensure that future documentation includes parity in examples and screenshots for both Windows and Linux environments where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. While some Linux-specific controls are mentioned (e.g., auditing Linux VM password files and accounts without passwords), Windows examples and controls are prioritized or exclusively detailed in several sections. For example, password management (A.9.4.3) lists only Windows VM policies, with no equivalent Linux password policy controls. Additionally, some controls reference Windows-specific tools or settings without Linux parity, and there is a general lack of Linux-focused examples or guidance in areas where both platforms are relevant.

Recommendations:

For each control that audits or enforces password policies on Windows VMs, provide equivalent controls, examples, or guidance for Linux VMs (e.g., minimum password length, complexity, password age, and reuse policies).
Where Windows-specific tools or settings are referenced (such as password complexity or audit policies), include Linux equivalents (e.g., PAM configuration, chage, passwd file permissions) and describe how to audit/enforce them via Azure Policy or other supported mechanisms.
Ensure that for every mention of Windows VM controls, there is a corresponding mention of Linux VM controls where applicable, or explicitly state if such controls are not available.
Add more Linux-focused examples and recommendations throughout the documentation, especially in sections that currently only mention Windows.
Review the ordering of examples and controls to avoid always listing Windows first; alternate or group by platform where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing on PowerShell tooling and examples, referencing the GuestConfiguration PowerShell module and providing a video tutorial based on PowerShell. There is no mention of Linux-native tooling, nor are there Linux-specific examples or workflows. The documentation assumes PowerShell as the primary authoring and validation environment, even though Linux support is mentioned.

Recommendations:

Include Linux-native command-line examples (e.g., Bash, shell scripts) for authoring and validating machine configuration packages.
Provide parity in tooling instructions, such as how to use the GuestConfiguration module or equivalent tools on Linux systems.
Add a Linux-focused video or walkthrough to complement the PowerShell-based video.
Clarify any differences or additional steps required for Linux users, especially where PowerShell is not the default shell.
Explicitly mention and link to Linux documentation or resources where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first bias by providing examples and references that are specific to Windows environments, such as the Azure Windows Baseline configuration and exclusive use of PowerShell for management tasks. There are no Linux-specific examples or equivalent command-line instructions, and the documentation does not mention Linux tools or patterns for managing machine configuration assignments.

Recommendations:

Include Linux-specific examples, such as associating a Linux baseline configuration or referencing Linux guest configuration packages.
Provide equivalent CLI (az CLI), Bash, or REST API examples for managing machine configuration assignments, not just PowerShell.
Mention and demonstrate how Linux VMs or Arc-enabled machines can be managed with guest configuration assignments.
Balance the order of examples and references so that Linux and Windows are treated equally, or clarify cross-platform applicability where relevant.
Reference Linux-relevant documentation or tools where appropriate, such as DSC for Linux or other configuration management solutions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides PowerShell (Az.Storage module) examples for publishing configuration packages to Azure Blob Storage, with no mention of Linux-native tools, Bash, or cross-platform CLI alternatives. All code snippets and workflow steps assume a Windows/PowerShell environment, and there are no references to Linux or macOS workflows.

Recommendations:

Add equivalent examples using Azure CLI (az storage ...) commands, which are cross-platform and work natively on Linux, macOS, and Windows.
Include Bash shell script examples for uploading files to Azure Blob Storage.
Mention and provide examples for using tools like azcopy, which is available on all major platforms.
Explicitly state that the process can be performed from Linux/macOS as well as Windows, and provide guidance for those environments.
Reorganize the documentation to present cross-platform or CLI-first solutions before PowerShell-specific instructions, or at least present them in parallel.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All code examples use PowerShell and reference Windows-specific cmdlets and paths. The 'Platform' parameter is always set to 'Windows' in examples, and file paths use Windows conventions (e.g., C:\Local\Path\To\Package). There are no Linux/Bash/CLI examples, and Linux-specific considerations are only mentioned in passing (e.g., minimum agent version). Windows tools and patterns are presented exclusively, with no parity for Linux users.

Recommendations:

Provide equivalent examples using Bash or Azure CLI for Linux users, especially for tasks like setting variables, uploading packages, and creating policies.
Include at least one example where the 'Platform' parameter is set to 'Linux', and use Linux file path conventions (e.g., /home/user/package.zip) in those examples.
Mention Linux prerequisites and environment setup steps alongside Windows/PowerShell instructions.
Reference Linux tools (e.g., az CLI, bash scripting) and show how to accomplish the same tasks without PowerShell.
Clarify which steps are OS-agnostic and which require OS-specific commands, ideally grouping examples by platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a PowerShell-only example for interacting with the REST API, with no equivalent example for Linux-native tools such as Bash, curl, or Azure CLI. The only script-based automation guidance is given in PowerShell, which is primarily a Windows tool, and there is no mention of Linux or cross-platform alternatives.

Recommendations:

Add equivalent examples using Bash with curl for REST API calls, which are native to Linux environments.
Provide Azure CLI (az) command examples where possible, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that the REST API can be called from any platform and provide generic HTTP request examples.
Ensure that scripting examples are not limited to PowerShell, and offer parity for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references PowerShell as a deployment method before mentioning the Azure CLI, and links to a PowerShell-specific quickstart. There are no explicit Linux or Bash examples, and the ordering of deployment options places Windows-centric tools first. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users.

Recommendations:

Provide Linux/Bash examples alongside or before PowerShell examples when describing deployment options.
Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
Reorder deployment options to avoid Windows-first bias, e.g., list Azure CLI before PowerShell or present them in parallel.
Include screenshots or instructions relevant to Linux environments where applicable.
Add a note clarifying that all deployment methods are available on both Windows and Linux, and link to platform-specific guidance if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Windows-specific instructions and examples. The execution command uses a Windows-style executable (mgCreate.exe) and PowerShell-style line continuations (`), with no mention of Linux or cross-platform equivalents. There are no Linux/macOS-specific instructions or examples for running the application, and the use of .exe implies a Windows environment. Additionally, the clean-up instructions reference deleting folders in a way that is more familiar to Windows users.

Recommendations:

Provide explicit instructions and examples for running the .NET Core application on Linux and macOS, including using 'dotnet mgCreate.dll' instead of 'mgCreate.exe'.
Use cross-platform command-line syntax, or provide both Windows (PowerShell/cmd) and Linux/macOS (bash) variants for commands, especially for application execution and directory navigation.
Avoid Windows-specific line continuation characters (e.g., backtick `) in command examples, or provide bash equivalents (e.g., backslash \) for Linux/macOS.
Clarify that .NET Core applications are cross-platform and can be run on Windows, Linux, and macOS, and provide any necessary prerequisites or troubleshooting tips for non-Windows environments.
Update clean-up instructions to include Linux/macOS commands for deleting project folders (e.g., 'rm -rf mgCreate').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways. Many policy definitions and compliance controls specifically reference Windows machines, Windows extensions, or Windows-specific tools (such as the Microsoft IaaSAntimalware extension), often without providing equivalent Linux examples or alternatives. In sections where both Windows and Linux are relevant (e.g., guest configuration, privileged access, antivirus), Windows is frequently mentioned first or exclusively, with Linux-specific policies either omitted or only included in select areas. This creates an impression that Windows is the primary or default platform for compliance, while Linux support is secondary or incomplete.

Recommendations:

For every Windows-specific policy or example, provide a Linux equivalent where possible, or explicitly state if one does not exist.
Ensure Linux guest configuration, extension deployment, and security controls are documented alongside Windows, not as an afterthought.
Add Linux-focused antivirus and hardening policy examples, or clarify the current limitations for Linux support.
Review the ordering of examples and policies to avoid always listing Windows first; consider alternating or grouping by OS.
Where Windows tools or extensions are referenced (e.g., IaaSAntimalware), mention Linux-compatible alternatives or note the lack thereof.
Include cross-platform guidance and highlight any differences in compliance implementation between Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Windows-specific tools (such as Windows Admin Center and Microsoft Antimalware for Azure) are highlighted with detailed configuration steps and dedicated sections, while Linux equivalents are either omitted or only briefly mentioned. In several sections, Windows is mentioned before Linux, and some features (like antimalware and Windows Admin Center) are described exclusively for Windows, with no Linux alternatives or guidance provided. Where Linux is mentioned (e.g., Change Tracking and Inventory, Azure Update Manager), the coverage is less detailed than for Windows.

Recommendations:

For every Windows-specific tool or feature (e.g., Windows Admin Center, Microsoft Antimalware), provide Linux equivalents or explicitly state if no equivalent exists.
Ensure that all example policies, configuration steps, and extension deployments are shown for both Windows and Linux VMs, with equal detail.
Avoid listing Windows before Linux by default; alternate the order or use neutral phrasing (e.g., 'Windows and Linux VMs').
Where a feature is Windows-only, clearly state this and, if possible, suggest best practices or alternatives for Linux users.
Expand sections such as antimalware and admin tools to discuss Linux security and management options (e.g., integration with third-party Linux antimalware, SSH-based management, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas. Windows-specific policies and controls (such as auditing Windows Administrators group membership, password policies, and deployment of Windows Guest Configuration extensions) are listed and described in detail, while equivalent Linux controls are either absent or less comprehensive. In several sections, Windows controls are presented first or exclusively, and there are more granular controls for Windows than for Linux. There are also policies that reference Windows-specific tools and patterns without Linux parity.

Recommendations:

Ensure that for every Windows-specific policy or example (e.g., auditing Administrators group, password complexity, Guest Configuration extension deployment), there is an equivalent Linux policy or example, or clearly state if a Linux equivalent is not available.
Present Linux and Windows controls in parallel, rather than listing Windows controls first or exclusively, to avoid the perception of prioritizing Windows.
Expand Linux coverage to include more granular controls, such as auditing Linux sudoers group membership, password complexity, and other common Linux security configurations.
Where Windows tools or extensions are mentioned (e.g., Windows Guest Configuration extension), ensure Linux equivalents are described with equal detail and prominence.
If certain controls are not available for Linux, explicitly acknowledge the gap and, if possible, provide guidance or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. The majority of policy definitions and examples are Windows-specific, referencing Windows tools, PowerShell Desired State Configuration (DSC), and Windows-centric modules. Linux is only mentioned in a few entries, and Linux-specific modules or equivalent tooling are not described in detail. The introductory text and table structure focus on PowerShell and Windows, with Linux policies being the exception rather than the norm.

Recommendations:

Add more Linux-specific policy definitions and examples to achieve parity with Windows coverage.
Include details and links for Linux equivalents of PowerShell DSC modules, or clarify how guest configuration is implemented on Linux.
Revise introductory text to mention both Windows and Linux approaches equally, rather than focusing on PowerShell and Windows first.
Where possible, provide side-by-side examples or tables for both Windows and Linux, ensuring Linux is not treated as an afterthought.
Document any differences in implementation or support between Windows and Linux guest configuration, so users are aware of platform-specific limitations or requirements.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by primarily using PowerShell-specific syntax and escape characters in command examples, mentioning PowerShell and Windows tools before Linux equivalents, and lacking explicit, fully worked Linux/Bash-native examples. While it acknowledges Bash shells like Git Bash, it does not provide clear, parallel Linux command examples or address common Linux environments (e.g., Ubuntu, macOS Terminal) directly.

Recommendations:

Provide explicit, side-by-side command examples for both PowerShell (Windows) and Bash (Linux/macOS), including correct syntax and escape characters for each.
Mention Linux and macOS terminal environments (e.g., Ubuntu, WSL, macOS Terminal) equally alongside Windows/PowerShell.
Clarify escape character differences with concrete Bash examples, not just notes about omitting backticks.
Include installation instructions or links for Bash shells on Linux and macOS, not just Git Bash (which is primarily for Windows).
Avoid assuming Visual Studio Code as the default terminal; mention alternatives common in Linux/macOS environments.
Use neutral language when referring to shells and tools, ensuring neither Windows nor PowerShell is presented as the default or primary environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell as the first utility for scaling clusters, providing explicit PowerShell cmdlet examples, and referencing Windows-style paths in some command snippets. While Azure CLI and SSH/bash commands are included, the prominence and ordering of PowerShell and Windows tools suggest a Windows-centric approach. There is also a lack of explicit Linux-specific guidance or parity in some sections, such as not providing Linux command-line equivalents for all PowerShell actions.

Recommendations:

List Azure CLI before PowerShell in the utilities table, as CLI is cross-platform and more commonly used on Linux.
Provide explicit Linux/bash command examples wherever PowerShell examples are given, ensuring parity.
Avoid using Windows-style paths (e.g., %HBASE_HOME%\bin) in command snippets; use Linux-style paths or provide both.
Clarify that all command-line examples (e.g., SSH, hadoop fs, hdfs dfsadmin) are intended for Linux environments, and provide any necessary Windows equivalents if relevant.
Add a section or note highlighting Linux usage patterns and tools, ensuring Linux users feel equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as primary management interfaces for scaling Kafka clusters, without mentioning Linux-native tools or CLI examples. There are no Linux shell or cross-platform CLI examples, and Windows-centric management patterns are presented first and exclusively.

Recommendations:

Include Azure CLI (az) examples for scaling and managing Kafka clusters, as it is cross-platform and widely used on Linux.
Mention Linux-native management tools or interfaces (such as SSH, Bash, or REST API usage) alongside or before Windows-specific tools like PowerShell.
Provide explicit Linux shell command examples for common tasks, ensuring parity with any PowerShell or portal instructions.
Clarify that all management operations can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
Review and update all procedural sections to ensure Linux users are not excluded or made secondary in the workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows and PowerShell bias. All code examples use PowerShell, including for Linux scenarios, and Windows-specific paths and outputs are shown by default. Windows configuration steps and tools are described first and in more detail, while Linux-specific guidance is minimal or deferred to external articles. There are no examples using native Linux tools or shell environments, and the packaging and inspection steps assume Windows conventions.

Recommendations:

Provide equivalent examples using native Linux shell commands (e.g., Bash) for compiling, renaming, and packaging configuration files.
Show Linux file paths and outputs alongside or instead of Windows paths (e.g., use /home/user/dsc/MyConfig instead of C:\dsc\MyConfig).
Include instructions for using Linux-native tools (e.g., mv, zip/unzip, du) for tasks like renaming files, creating archives, and checking file sizes.
Balance the order of presentation so that Linux and Windows steps/examples are given equal prominence, or alternate which platform is described first.
Clarify which steps are platform-agnostic and which are platform-specific, and provide clear, parallel guidance for both environments.
Consider including a section or appendix specifically for Linux users, summarizing the end-to-end workflow using Linux-native tools and conventions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for making REST API calls, recommending PowerShell as the tool of choice, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The guidance assumes familiarity with PowerShell cmdlets and Windows-centric tooling, with no mention of cross-platform alternatives or how to perform the same tasks on Linux or macOS.

Recommendations:

Add equivalent examples using curl or HTTPie for making REST API calls, which are available on Linux, macOS, and Windows.
Mention cross-platform tools (e.g., Azure CLI, REST clients like Postman, or ARMClient) alongside PowerShell, and provide sample usage.
Rephrase guidance to avoid recommending PowerShell as the default or only tool, instead offering a choice of tools for different platforms.
Include notes or sections specifically for Linux/macOS users, ensuring parity in authentication and REST invocation instructions.
Where PowerShell-specific cmdlets are referenced (e.g., ConvertFrom-Json), provide equivalent commands for bash/jq or other common Linux utilities.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but does not include any Linux- or macOS-specific shell examples (e.g., Bash). The PowerShell example is present, which is primarily associated with Windows environments, and there is no mention of Linux-native tools or shell usage. This may make Linux users feel less directly supported, especially since PowerShell is highlighted as a primary scripting interface.

Recommendations:

Add a Bash shell example for running the Azure CLI command, demonstrating usage in a typical Linux environment.
Explicitly mention that the Azure CLI example works cross-platform (Windows, Linux, macOS) and provide any OS-specific notes if needed.
If PowerShell is included, consider also including a Bash or zsh example to ensure parity for Linux/macOS users.
Clarify in the documentation that PowerShell Core is available cross-platform, if relevant, to reduce the perception of Windows-only bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation consistently provides examples using Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) featured equally alongside CLI. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tooling or workflows. The use of PowerShell as a primary example and the absence of Linux-native command-line patterns (e.g., bash, curl, jq) indicate a Windows bias.

Recommendations:

Add Linux shell (bash) examples for each scenario, using tools like curl for REST API calls and jq for JSON processing.
Clearly indicate cross-platform compatibility for Azure CLI and PowerShell, and provide notes on installation or usage differences on Linux/macOS.
Where PowerShell is shown, also provide equivalent bash or shell script snippets to ensure Linux users are equally supported.
Mention Linux-native tools and workflows (e.g., piping Azure CLI output to jq) when discussing result formatting and processing.
Consider the order of examples: alternate or lead with cross-platform (CLI/bash) examples before PowerShell to avoid Windows-first perception.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways. PowerShell examples are given in detail and before Azure CLI examples, with file paths and usage patterns that are Windows-specific (e.g., 'c:\policies\coolAccessTier.json'). There are no explicit Linux or macOS command-line examples, nor are there notes about cross-platform differences or alternative shells. The documentation assumes familiarity with Windows tools and conventions, potentially making it less accessible to Linux users.

Recommendations:

Provide Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
Include Linux/macOS file path examples (e.g., '/home/user/policies/coolAccessTier.json') wherever file paths are shown.
Add notes clarifying that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and highlight any OS-specific considerations.
Avoid using Windows-specific terminology (like 'right-click') without also mentioning keyboard or alternative methods for other platforms.
Explicitly mention that the Azure portal and REST API are OS-agnostic, and provide guidance for users on non-Windows systems.
Where possible, provide Bash shell equivalents for PowerShell commands, especially for scripting scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates bias towards Windows by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or REST API. There are no Linux or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and commonly used on Linux and macOS.
Mention REST API options for custom role creation to provide a platform-agnostic approach.
If PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent Bash or CLI commands.
Add explicit Linux/macOS instructions or notes to ensure parity and inclusivity for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is always presented alongside the CLI. There are no explicit Linux shell (e.g., Bash) or scripting examples, nor is there guidance for Linux-specific environments. The documentation does not clarify shell quoting/escaping differences, and PowerShell is given equal prominence to CLI, which may suggest a Windows bias.

Recommendations:

Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
Add notes or examples for common Linux shell quoting/escaping issues, especially when embedding Kusto queries.
If PowerShell examples are provided, consider also providing Bash or other Linux shell script equivalents for parity.
Clarify in introductory sections that Azure CLI is the recommended cross-platform tool, and PowerShell is optional for Windows users.
Where relevant, mention installation or usage differences for Linux users (e.g., package managers, environment variables).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples and environment variable usage in Windows syntax (e.g., 'set' for variables, Windows file paths like C:\Temp\input.txt), and by recommending Windows-specific approaches (such as using input files with Windows paths). There are no Linux/macOS equivalents for environment variables, file paths, or alternative tools, and the only file upload tool mentioned by name is AzCopy, which is Windows-centric.

Recommendations:

Provide parallel Linux/macOS examples for all command-line snippets, including environment variable setting (e.g., 'export clustername=CLUSTERNAME') and file paths (e.g., '/tmp/input.txt').
When referencing input files, show both Windows (C:\Temp\input.txt) and Linux (/tmp/input.txt) path formats.
Mention and provide examples for Linux-native tools for file upload (such as 'Azure CLI', 'hadoop fs', or 'scp'), not just AzCopy.
Avoid language that recommends a Windows-specific approach as the default; instead, offer platform-neutral guidance or dual instructions.
Explicitly state that the examples are shown for Windows and provide equivalent commands for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations and referencing Windows-centric tools first. There are no examples or instructions for performing the same tasks using Linux-native tools (such as Bash, Azure CLI, or SSH), which are commonly used in HDInsight clusters that often run on Linux VMs. The REST API section is platform-neutral, but the lack of Linux command-line parity is notable.

Recommendations:

Add equivalent examples using Azure CLI (az hdinsight ...) for listing and restarting nodes, as Azure CLI is cross-platform and widely used on Linux.
Include Bash or shell script examples for interacting with the REST API, such as using curl or httpie, to demonstrate how Linux users can perform the same operations.
Reorganize the documentation to present cross-platform or Linux-native options before or alongside PowerShell, rather than PowerShell first.
Explicitly mention that the PowerShell examples are for Windows users and provide clear alternatives for Linux/macOS users.
Consider referencing SSH-based troubleshooting or reboot commands for scenarios where the VM is still accessible via SSH.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available cross-platform) and the absence of explicit Linux/macOS shell or scripting examples (such as Bash) indicate a mild Windows bias. Additionally, PowerShell examples are always present and given equal prominence to CLI, and there are no Linux-specific notes or examples, such as using Bash scripting or mentioning shell environments. There are no references to Windows-only tools, but the documentation does not address Linux users directly or provide parity in scripting approaches.

Recommendations:

Add explicit Bash or shell script examples for Linux/macOS users, especially for common scenarios such as running az graph query and processing output.
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample shell usage (e.g., piping output to jq or grep).
If PowerShell is mentioned, note that PowerShell Core is cross-platform, or provide a Bash alternative where appropriate.
Consider including a 'Platform compatibility' note to reassure users that the instructions are not Windows-specific.
If scripting is discussed, show both PowerShell and Bash script blocks for parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and PowerShell examples, but the CLI example is written in a way that uses Windows/PowerShell variable syntax (e.g., $variable), and the PowerShell example is given in full. There are no explicit Linux/bash-native examples, and the CLI example is not shown in a cross-platform shell style (e.g., bash arrays or environment variables). This may confuse or disadvantage Linux users, as the CLI example is not directly copy-pastable into a bash shell.

Recommendations:

Provide a true bash/Linux example for the Azure CLI commands, using bash variable syntax (e.g., export SUBSCRIPTION_ID=..., arrays with parentheses, etc.).
Clarify which code blocks are for PowerShell and which are for bash, and ensure both are present where relevant.
Avoid using PowerShell array syntax (e.g., [String[]]$resources = @(...)) in CLI examples; instead, show how to pass multiple --service-resources arguments in bash.
Add a section or note specifically for Linux/macOS users, demonstrating the same workflow in a bash shell.
Ensure the order of examples does not always present Windows/PowerShell first; consider alternating or presenting both in parallel.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the section on triggering the Data Factory pipeline, where PowerShell is presented as the primary scripted method, with no equivalent Bash/Azure CLI example for Linux users. Power BI Desktop, a Windows-only tool, is the only visualization option described, and its use is assumed throughout. The documentation refers to Windows tools and patterns (PowerShell, Power BI Desktop) before or instead of cross-platform or Linux-native alternatives.

Recommendations:

Provide an Azure CLI or Bash example for triggering and monitoring the Data Factory pipeline, ensuring Linux users have a first-class scripted option.
Explicitly mention that Power BI Desktop is Windows-only and suggest alternatives for Linux users, such as Power BI web, Azure Data Studio, or open-source BI tools.
When presenting multiple options (e.g., scripting vs. portal), avoid listing Windows/PowerShell options first by default; consider parallel presentation or alternating order.
Include notes or links to documentation for connecting to HDInsight from Linux or macOS environments, especially for visualization and data access.
Audit for other sections where only Windows tools or workflows are described, and add Linux/macOS equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows/Active Directory-centric approach to enterprise security in Azure HDInsight. It emphasizes Microsoft Entra Domain Services (formerly Azure AD DS) and Active Directory-based authentication as the primary method for identity and access management. PowerShell is mentioned as a client tool for cluster access, but there is no mention of Linux-native authentication mechanisms (such as LDAP, Kerberos outside of AD context, or integration with non-AD identity providers), nor are there examples or references to Linux command-line tools or workflows. The documentation does not provide parity for Linux-first or cross-platform environments, and Windows-centric tools and patterns are presented as the default or only option.

Recommendations:

Include examples and guidance for integrating with non-Active Directory identity providers, such as generic LDAP or MIT Kerberos, to support Linux-centric enterprises.
Mention and provide examples for Linux-native client tools (e.g., SSH, curl, kinit, beeline, etc.) alongside or instead of PowerShell.
Clarify whether authentication and access control features are compatible with Linux-based identity systems or if there are workarounds.
Add explicit Linux command-line examples for common administrative and user tasks (e.g., connecting to clusters, submitting jobs, managing access).
Balance references to Windows tools with equivalent Linux tools in all sections, especially where PowerShell or Windows authentication is mentioned.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias, particularly in the feature registration section, where Azure PowerShell commands are presented first and in detail, while Azure CLI (more common on Linux) is only mentioned in passing. The use of PowerShell-specific code blocks and terminology (e.g., Register-AzProviderFeature, Get-AzProviderFeature) prioritizes Windows tooling. However, the main NFS conversion workflow and client-side examples are Linux-centric, using Linux commands (umount, mount, /etc/fstab) and terminology.

Recommendations:

Provide Azure CLI examples alongside (or before) Azure PowerShell examples for feature registration and status checking, with full command syntax and output samples.
Explicitly mention that both Windows and Linux clients are supported, and clarify any differences in steps for each platform.
Where possible, use platform-neutral language and tooling, or present both Windows and Linux options equally.
Ensure screenshots and UI references are not Windows-specific unless necessary.
Add a section or note for Windows NFS clients if they are supported, or clarify if the instructions are Linux-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric, providing only instructions and screenshots for Windows tools such as the ODBC Data Source Administrator and Excel on Windows. There are no Linux or cross-platform alternatives or instructions, and all steps assume a Windows environment.

Recommendations:

Add instructions for configuring ODBC data sources on Linux and macOS, including using unixODBC and relevant configuration files (e.g., odbc.ini).
Provide examples for connecting to Hive from Excel on macOS (if supported) or from alternative spreadsheet tools available on Linux.
Include command-line examples for setting up ODBC connections (e.g., using isql or similar tools) for non-Windows users.
Mention and link to any cross-platform ODBC drivers or tools, if available.
Clearly indicate platform-specific steps and provide parity where possible, or explicitly state if a feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. In sections discussing how to find the sAMAccountName, Windows AD tools are mentioned before Linux/SAMBA alternatives, and the only explicit tool reference is to 'standard Windows AD tools.' There is no mention of Linux GUI tools or command-line alternatives for directory browsing, and the Windows approach is described in more detail. Some troubleshooting steps (e.g., password changes) reference the Azure portal, which is platform-neutral, but there are no PowerShell-specific commands or examples. However, Linux commands (e.g., kinit, net ads search, export KRB5_TRACE) are present, but not always introduced with parity to Windows methods.

Recommendations:

When listing ways to find sAMAccountName, mention Linux/SAMBA command-line methods before or alongside Windows tools.
Provide explicit Linux GUI or CLI alternatives for browsing Active Directory (e.g., using 'ldbsearch', 'ldapsearch', or 'adcli').
If referencing Windows AD tools, also reference equivalent Linux tools with example commands.
Ensure that all troubleshooting steps that mention Windows-specific tools or portals also mention Linux-friendly methods where possible.
Consider adding a table or section summarizing both Windows and Linux approaches for common administrative tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates some Windows bias, particularly in the 'Escape characters' section, where PowerShell (a Windows-centric shell) is given a dedicated example and is mentioned before Bash. The Bash example is present, but the ordering and explicit mention of PowerShell and cmd (both Windows shells) before Bash suggests a Windows-first approach. There are no CLI (az), Linux shell, or cross-platform examples for running queries, and no mention of Linux-specific tools or workflows elsewhere in the document.

Recommendations:

Reorder shell-specific instructions to list Bash (Linux/macOS) before PowerShell and cmd, or present all at the same time in a neutral order.
Include examples using the Azure CLI (az) for running Resource Graph queries from Linux/macOS terminals.
Add explicit Linux/macOS usage notes or examples where relevant, especially in sections discussing shell-specific syntax or escaping.
Where PowerShell is mentioned, clarify that cross-platform PowerShell Core is available, or provide both Windows PowerShell and Linux/macOS PowerShell Core examples.
Audit other sections for implicit Windows assumptions and ensure parity in tooling and workflow guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing command-line examples that use Windows-specific syntax (e.g., 'set' for environment variables, caret '^' for line continuation, and Windows paths for jq). There are no explicit Linux/bash examples, and the instructions for using curl are tailored to Windows environments. PowerShell is also presented as a primary method, with no mention of bash or Linux shell equivalents. Tools and patterns (like jq path and environment variable setting) are shown only for Windows.

Recommendations:

Provide parallel Linux/bash examples for all curl commands, using 'export' for environment variables, backslash '\' for line continuation, and typical Linux jq paths (e.g., '/usr/bin/jq').
Clearly separate Windows and Linux command blocks, labeling them accordingly.
Avoid using Windows-specific syntax in generic sections, or provide both Windows and Linux alternatives.
Mention bash or Linux shell as an equivalent to PowerShell for users on non-Windows systems.
Include a note or table summarizing differences in command syntax and tool locations between Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily through exclusive use of Azure PowerShell commands (e.g., Get-AzProviderFeature) for feature registration checks, with no CLI (az) or Bash/Linux alternatives provided. There are no Linux shell or cross-platform command examples, and the only command-line tooling referenced is PowerShell, which is more familiar to Windows users. This may disadvantage Linux administrators or those who prefer cross-platform tools.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for feature registration checks (e.g., az feature list --namespace Microsoft.NetApp --query ...).
Explicitly note that PowerShell commands can be run on any OS with PowerShell Core, but also offer Bash or shell script alternatives where possible.
Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform, and consider mentioning any OS-specific considerations if relevant.
In sections discussing Terraform, mention that Terraform is cross-platform and can be used from Linux, macOS, or Windows.
Review all command snippets and ensure that for every PowerShell example, a CLI or Bash equivalent is provided to ensure Linux parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows-centric bias by exclusively referencing Microsoft Entra Domain Services (formerly Azure AD DS), Active Directory, and related tooling for authentication, authorization, and cluster management. There are no examples or guidance for integrating with Linux-native identity providers (such as LDAP, MIT Kerberos, or FreeIPA), nor are there instructions for managing HDInsight clusters in environments that do not use Microsoft identity solutions. The documentation assumes a Windows/Active Directory environment as the default, omitting Linux-first or open-source alternatives.

Recommendations:

Provide equivalent guidance for integrating HDInsight clusters with Linux-native identity providers (e.g., OpenLDAP, FreeIPA, MIT Kerberos), including configuration steps and security best practices.
Include examples and workflows for environments that do not use Microsoft Entra Domain Services or Active Directory, such as those using open-source directory services.
Explicitly mention any limitations or requirements for non-Windows environments, and offer workarounds or alternatives where possible.
Ensure that documentation sections referencing authentication, authorization, and cluster management do not assume Microsoft tooling as the only or primary option.
Add Linux command-line examples (e.g., using SSH, kinit, or open-source tools) alongside or in place of Windows/PowerShell-centric instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas. Data ingestion into Azure Storage is described as typically done via PowerShell, the Azure Storage SDK, or AzCopy, with no mention of Linux-native tools or CLI workflows. PowerShell and .NET SDKs are referenced before cross-platform or Linux-friendly options. There is a lack of explicit Linux or bash command examples, and the ordering of tool mentions often puts Windows-centric tools first. While some open-source Hadoop tools are mentioned, the overall guidance and examples favor Windows environments.

Recommendations:

Include Linux-native and cross-platform CLI examples (e.g., Azure CLI, Bash scripts, Hadoop CLI tools) alongside or before PowerShell examples.
Explicitly mention and provide examples for Linux-based ingestion tools, such as Azure CLI az storage commands, Hadoop fs commands, or Linux-compatible SDKs.
When listing ingestion or orchestration tools, avoid putting Windows-centric tools (PowerShell, .NET SDK) first unless there is a technical reason; alternate or randomize order, or group by platform.
Add sample commands or code snippets for Linux users, especially for common ingestion and orchestration tasks.
Clarify which tools are cross-platform and which are Windows-only, to help users on Linux identify their best options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias throughout. All setup and configuration steps are described using Windows-centric tools and workflows, such as Remote Desktop, Server Manager, Microsoft Management Console (MMC), and PowerShell scripts. There are no examples or guidance for performing equivalent tasks on Linux-based systems or using cross-platform tools. The documentation assumes the use of Windows VMs and does not mention or provide alternatives for Linux environments, even though HDInsight clusters themselves run on Linux by default.

Recommendations:

Provide equivalent instructions for Linux environments, including how to set up and manage users, groups, and certificates using Linux tools (e.g., OpenLDAP, command-line utilities).
Offer Bash/Azure CLI examples alongside PowerShell scripts for network and resource provisioning.
Clarify which steps are Windows-specific and which can be performed from any OS, and provide cross-platform alternatives where possible.
Include guidance for connecting to the domain controller and managing Entra ID from Linux or macOS clients, possibly using RDP alternatives or Azure portal exclusively.
Document how to generate and manage certificates for LDAPS using OpenSSL and Linux-based certificate stores.
Explicitly state any prerequisites or limitations if only Windows is supported for certain steps, and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. The focus is on Windows-native tools (PowerShell modules, Active Directory, Microsoft Entra Domain Services), and there are no instructions or guidance for users on Linux or macOS. The documentation assumes a Windows-centric environment and does not address Linux administration scenarios.

Recommendations:

Provide equivalent command-line examples using Azure CLI and/or Bash scripts, which are cross-platform and commonly used on Linux.
Mention and document how Linux administrators can perform required tasks, such as managing service principals and policies, using non-Windows tools.
Clarify whether any steps require Windows specifically, and if so, suggest workarounds or alternatives for Linux/macOS users.
Include references to Linux-compatible tools (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming the user is on Windows.
Add a section or notes for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation presents both Azure CLI and Azure PowerShell examples for all queries, but there is a notable bias toward Windows/PowerShell patterns. PowerShell examples are always present and sometimes explained in more detail (e.g., use of ConvertTo-Json and depth), and Windows-centric tools and patterns (PowerShell variables, cmdlets) are used throughout. In the multi-step public IP address example, the Azure CLI workflow uses Unix tools (awk, sed, tail), but there is no explicit mention of Linux shell environments or guidance for Linux users. The JSON output examples use Windows-centric values (e.g., WindowsServer images, osType: Windows), and there is no mention of Linux VMs or their properties.

Recommendations:

Add explicit Linux/Unix shell examples (e.g., bash, zsh) for workflows involving Azure CLI, especially for variable handling and file manipulation.
Include examples or notes for querying Linux virtual machines (e.g., using 'osType: Linux', 'publisher: Canonical', etc.) in JSON and queries.
Balance explanations between PowerShell and CLI, ensuring that CLI examples are as detailed and accessible as PowerShell ones.
When discussing output formatting (e.g., ConvertTo-Json in PowerShell), provide equivalent CLI/jq or other Linux-friendly alternatives.
Avoid Windows-centric sample data where possible, or provide parallel Linux examples (e.g., show both Windows and Linux VM JSON).
Clarify in notes or callouts when CLI examples assume a Unix-like shell, and provide Windows CMD or PowerShell equivalents if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively presents Windows-based tools and workflows (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no Linux or cross-platform alternatives mentioned, and all instructions and screenshots are Windows-specific. This creates a strong Windows bias and leaves out users who may be administering from Linux or other non-Windows environments.

Recommendations:

Include equivalent instructions for viewing and managing SMB share ACLs from Linux systems, such as using smbclient, smbcacls, or other Samba tools.
Explicitly state if certain operations (such as modifying share-level ACLs) are only possible from Windows, and provide any available workarounds or alternatives for non-Windows users.
Add a section or note addressing cross-platform management, clarifying limitations and suggesting best practices for Linux/macOS administrators.
Where possible, provide command-line examples (e.g., PowerShell and Bash/smbcacls) side by side to improve parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell for all scripting and automation examples, with no mention of alternatives such as Python or Bash. All runbook examples, module installations, and code snippets are PowerShell-based, and the workflow assumes familiarity with Windows-centric tools and patterns. There are no Linux-native scripting examples or references to cross-platform automation options, and the 'Next step' also points to a PowerShell-specific guide.

Recommendations:

Provide equivalent examples using Python runbooks (supported in Azure Automation) for creating and deleting HDInsight clusters.
Include Bash/CLI examples where possible, especially for users who may prefer Linux-native scripting.
Mention and link to Azure CLI and REST API documentation as alternative, cross-platform ways to automate HDInsight cluster management.
Balance the order of presentation so that PowerShell and Linux-friendly options are introduced together, or alternate which is presented first.
Clarify that PowerShell runbooks can be authored and executed from non-Windows platforms using PowerShell Core, and provide guidance for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows (such as SQL Server Integration Services, Excel, PowerShell, and Azure Logic Apps) for ETL orchestration and data loading. There is a lack of Linux/Unix command-line examples, and Linux-native tools or workflows are not mentioned or are referenced only after Windows equivalents. The documentation does not provide Linux-specific guidance or parity in examples.

Recommendations:

Include Linux/Unix command-line examples for orchestrating Hive ETL workflows (e.g., using Bash scripts, cron jobs, or Apache Oozie).
Mention and provide examples for Linux-native tools for data loading and orchestration, such as Apache NiFi, Airflow, or Sqoop CLI usage from Linux.
When listing tools (e.g., SSIS, Excel, PowerShell), also mention Linux alternatives (e.g., csvkit, pandas, shell scripting, or open-source ETL tools).
Avoid presenting Windows tools and workflows first or exclusively; provide parallel Linux options or structure sections by platform.
Demonstrate how to automate Hive queries using Linux-native scheduling (cron) or workflow tools (Oozie, Airflow), not just PowerShell or Logic Apps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is used for several automation examples, including ARM template deployment and enabling encryption at host, without providing equivalent Bash or Linux shell examples. Windows-centric tools and patterns (e.g., PowerShell cmdlets, references to Undo-AzKeyVaultKeyRemoval) are mentioned, sometimes before or instead of cross-platform or Linux-native alternatives. There are no explicit Linux shell (bash) command examples for key operations, and the documentation assumes familiarity with Windows tooling.

Recommendations:

For every PowerShell example, provide an equivalent Bash (Linux shell) example, especially for ARM template deployment and cluster creation.
When referencing recovery or management tools (e.g., Undo-AzKeyVaultKeyRemoval), also mention and provide examples for the Azure CLI or REST API equivalents.
Avoid assuming the use of Windows tools by default; clarify that both Windows and Linux users are supported and provide parity in instructions.
Where possible, use Azure CLI as the primary example, as it is cross-platform, and supplement with both PowerShell and Bash examples.
Explicitly mention that HDInsight clusters are Linux-based by default, and provide guidance for Linux users where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows users, requiring a Windows client and Visual Studio, and provides only C#/.NET and NuGet/PowerShell-based instructions. There are no equivalent Linux or cross-platform examples, and Linux users are referred elsewhere rather than given parity in this guide.

Recommendations:

Provide equivalent instructions and code samples for Linux users, such as using .NET Core/SDK on Linux and alternative editors (e.g., VS Code, JetBrains Rider, or command-line tools).
Include Linux-specific setup steps, such as installing the .NET SDK and running the sample from the terminal.
Replace or supplement PowerShell/NuGet Package Manager Console commands with cross-platform .NET CLI commands (e.g., 'dotnet add package').
Clarify which steps are Windows-specific and offer direct alternatives for Linux/macOS users within the same article, rather than referring them to other documentation.
Highlight cross-platform compatibility of the .NET SDK where applicable, and provide troubleshooting tips for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET, with all code samples in C#. Instructions reference Windows-centric tools (Visual Studio, NuGet Package Manager Console) and workflows. There are no examples or guidance for Linux or cross-platform development environments, nor are alternative tools or command-line approaches mentioned. The only mention of Linux is in the limitations section, which focuses on feature gaps rather than usage guidance.

Recommendations:

Provide equivalent instructions and code samples for Linux and macOS users, such as using .NET Core/SDK and VS Code or JetBrains Rider as alternatives to Visual Studio.
Include command-line examples for running Sqoop jobs using Bash or cross-platform .NET CLI, not just through Visual Studio and C#.
Mention and demonstrate how to install the required SDKs and dependencies on Linux (e.g., using apt, yum, or dotnet CLI).
Clarify which steps are platform-specific and offer alternatives for non-Windows users.
Consider including Python or Java examples, which are more common in cross-platform and Linux-based big data environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily in the management and configuration of LDAP POSIX attributes, where only Windows tools (Active Directory Users and Computers MMC snap-in) are described and illustrated. There are no equivalent instructions or examples for managing POSIX attributes using Linux tools or command-line utilities. Additionally, the step-by-step instructions for accessing the Attribute Editor are exclusively for Windows systems, and Windows terminology and tools are mentioned first or exclusively in several places. There are no PowerShell command examples, but the overall guidance assumes a Windows-centric administrative environment.

Recommendations:

Add equivalent instructions and examples for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or graphical LDAP editors like Apache Directory Studio).
Provide Linux-based workflows for common administrative tasks, such as editing user and group attributes, alongside the Windows MMC snap-in instructions.
When referencing tools or workflows, mention both Windows and Linux options, or present them in a neutral order (e.g., 'On Windows, use X; on Linux, use Y').
Include screenshots or command-line examples for Linux-based LDAP management where possible.
Clarify that administrative tasks can be performed from both Windows and Linux environments, and link to relevant Linux documentation or external resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/Visual Studio-centric workflow, with all project creation, building, uploading, and job submission steps described using Visual Studio and Azure tools that are primarily Windows-based. While there is a brief mention of SSH for Pig jobs, there are no Linux-native or cross-platform alternatives for building, uploading, or running jobs, and no command-line or non-Visual Studio workflows are provided. Linux is only referenced as the HDInsight cluster OS, not as a development or client environment.

Recommendations:

Provide equivalent instructions for creating, building, and packaging the C# UDFs using cross-platform tools such as the dotnet CLI and MonoDevelop, which are available on Linux and macOS.
Include examples of uploading .exe files to HDInsight storage using Azure CLI and/or azcopy, with command-line instructions suitable for Linux/macOS.
Demonstrate how to submit Hive queries and Pig jobs using Azure CLI, SSH, or other cross-platform methods, not just through Visual Studio.
Reorder or parallelize instructions so that Windows/Visual Studio and Linux/cross-platform workflows are presented equally, or at least mention Linux alternatives alongside Windows steps.
Explicitly state that all steps can be performed from Linux/macOS, and provide guidance for users who do not have access to Visual Studio or Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively providing installation instructions using the Visual Studio NuGet Package Manager Console (a Windows-centric tool), and all code examples are in C#/.NET, which is most commonly used on Windows. There are no instructions or examples for installing or using the SDK on Linux or macOS, nor any mention of cross-platform command-line alternatives. The documentation assumes the user is operating in a Windows/.NET environment, omitting Linux-native workflows or tools.

Recommendations:

Provide installation instructions using the dotnet CLI (e.g., 'dotnet add package Microsoft.Phoenix.Client'), which is cross-platform and works on Linux, macOS, and Windows.
Explicitly mention that the SDK and examples work on Linux and macOS if supported, and provide any prerequisites or differences for those platforms.
Include at least one example of running the SDK from a Linux shell or in a cross-platform .NET Core project.
If the SDK is Windows-only, clearly state this limitation early in the documentation.
Avoid referencing only Windows-specific tools (like Visual Studio NuGet Package Manager Console) as the primary installation method; present cross-platform alternatives first or alongside.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally aims for cross-platform coverage but exhibits some Windows bias. Windows-specific tools (Visual Studio, PowerShell, SSIS) are mentioned as primary options, sometimes before or more prominently than Linux equivalents. PowerShell is listed as a method for running Hive queries, but there is no equivalent Bash or Linux shell example. Integration with Windows-centric tools like SQL Server Integration Services is described in detail, while Linux-native scheduling or orchestration tools (other than Oozie) are not highlighted. In some cases, Windows is listed first or exclusively in client OS support.

Recommendations:

Add explicit Linux shell (Bash) and macOS command-line examples for running Hive queries, especially where PowerShell is mentioned.
Ensure parity in tool recommendations: for every Windows tool (e.g., Visual Studio, PowerShell), mention and provide equal detail for cross-platform or Linux-native alternatives (e.g., IntelliJ IDEA, VS Code, Bash scripts).
When listing client operating systems, avoid putting Windows first unless there is a technical reason; use alphabetical or neutral ordering.
Expand the scheduling section to include Linux-native options such as cron, Airflow, or other workflow tools commonly used in Linux environments.
Where possible, provide code snippets or walkthroughs that are platform-agnostic or include both Windows and Linux/macOS variants.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell commands for package installation, referencing Windows-specific tools and patterns (such as PowerShell client GUID and Windows-style prompts), and lacking equivalent Linux or cross-platform examples for setup and management. The only shell command example for HBase uses Windows batch syntax, and there are no Bash or Linux-native instructions for any step, despite HDInsight's strong Linux support.

Recommendations:

Provide equivalent Bash/Linux shell commands for installing .NET SDK packages (e.g., using dotnet CLI or NuGet on Linux).
Include Linux/macOS authentication and setup instructions, clarifying any differences in environment variables or authentication flows.
Replace or supplement Windows batch commands (e.g., HBase shell example) with Bash equivalents.
Clarify that the .NET SDK and all code samples are cross-platform, and explicitly mention how to run them on Linux/macOS.
Avoid referencing Windows-specific tools (such as PowerShell client GUID) without Linux alternatives or explanations.
Where possible, use platform-neutral language and examples, or provide side-by-side instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting all local development environment setup steps using Windows-specific commands (cmd, Notepad, DEL, MKDIR) and explicitly stating that the environment is Windows 10. There are no equivalent Linux (bash, nano/vim, rm, mkdir) instructions or examples, and Windows tools are referenced exclusively for editing and file management. While the Hadoop cluster interaction uses SSH and bash commands (which are cross-platform), the initial project creation and editing workflow is only documented for Windows users.

Recommendations:

Provide parallel Linux/macOS instructions for all environment setup steps, including directory creation, file deletion, and file editing (e.g., use 'mkdir', 'rm', 'nano' or 'vim').
Present both Windows and Linux/macOS command examples side by side or in tabs, so users on any platform can follow along easily.
Avoid referencing Windows tools (like Notepad) exclusively; mention cross-platform editors or provide alternatives (e.g., VS Code, nano, vim).
Clarify that the instructions are applicable to all platforms, and explicitly state any platform-specific differences.
Consider using platform-agnostic language and commands wherever possible, especially for Java/Maven-based workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits mild Windows bias. While most of the content is platform-neutral, the only automation example explicitly mentioned is PowerShell scripts, and Azure Automation is referenced (which is often used with PowerShell/Windows workflows). There are no examples or mentions of Linux-native scripting or tools (such as Bash, CLI, or ARM templates) for cluster lifecycle management. The order of mention also puts PowerShell before any Linux alternative, and no Linux-specific automation or scripting options are discussed.

Recommendations:

Include Linux-native automation examples, such as Bash scripts or Azure CLI commands, for provisioning and deleting clusters.
Mention ARM/Bicep templates as a cross-platform, declarative alternative for cluster lifecycle management.
When referencing automation, list both PowerShell and Bash/CLI options, or refer to 'scripting' in a platform-neutral way.
Provide links to documentation for both Windows and Linux automation approaches.
Avoid implying PowerShell is the only or primary automation method for HDInsight clusters.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates bias toward Windows environments by exclusively referencing Azure SQL Database (a Microsoft/Windows-centric technology) as the only supported external Ambari database, omitting any mention of Linux-native or open-source database alternatives (such as PostgreSQL or MySQL). All SQL examples use T-SQL syntax specific to Azure SQL/SQL Server, and there are no examples or guidance for Linux-based database management or tooling. The deployment instructions focus on Azure CLI (cross-platform), but the overall pattern and requirements are tightly coupled to Windows-centric tools and services.

Recommendations:

Add guidance and examples for using open-source, Linux-native databases (e.g., PostgreSQL, MySQL) as external Ambari DBs, if supported.
If only Azure SQL Database is supported, explicitly state this limitation and provide rationale.
Include Linux-native command-line examples for database setup and management (e.g., using psql or mysql CLI tools) if/when support is added.
Mention and provide parity for Linux-based firewall and networking configuration steps, not just Azure Portal/Windows-centric instructions.
Ensure that any SQL code samples are clearly marked as T-SQL/Azure SQL-specific, and provide alternatives if other databases are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is generally Linux-oriented (reflecting HDInsight's Linux focus), but there are notable instances of Windows bias. PowerShell and Windows tooling are referenced without equivalent Linux CLI/Azure CLI examples, and Windows is sometimes mentioned before Linux. For example, the deprecated 'EnableVmProtection' parameter is discussed only in the context of PowerShell, and VM DNS forwarder setup mentions both Linux and Windows, but PowerShell is the only automation example provided. There are no Azure CLI or Bash scripting equivalents for network or VM management tasks.

Recommendations:

For every PowerShell example (such as checking or configuring network settings), provide an equivalent Azure CLI or Bash example.
When mentioning VM setup for DNS forwarding, give step-by-step instructions for both Linux and Windows VMs, or link to relevant guides for each.
If referencing Windows tools or patterns (e.g., PowerShell, Windows VMs), ensure Linux alternatives are described with equal prominence and detail.
In sections where Windows and Linux are both possible (e.g., DNS forwarder VM), mention Linux first or present both options side-by-side.
For automation or scripting, include Bash or Azure CLI scripts alongside PowerShell scripts to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits Windows bias, particularly in the configuration examples for HDInsight Spark.NET settings. Paths and tool references (such as 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME) are given exclusively in Windows format (e.g., C:\Program Files\, D:\winutils), and there is no mention of Linux or macOS equivalents. Additionally, the documentation does not provide Linux-specific instructions or examples for these settings, nor does it clarify cross-platform differences.

Recommendations:

Provide Linux and macOS equivalents for all file paths and tool references (e.g., /usr/bin/7z, /usr/lib/jvm/java-8-openjdk-amd64, /home/user/spark).
Explicitly state when a setting is Windows-only, and offer alternative instructions or notes for Linux/macOS users.
Include examples or a table showing how to configure these settings on different operating systems.
Mention any platform-specific requirements or limitations for tools like winutils.exe, and suggest alternatives or workarounds for non-Windows environments.
Review all examples and ensure parity by including at least one Linux/macOS example wherever a Windows example is given.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a detailed PowerShell example for verifying additional storage accounts but does not offer equivalent Linux CLI or Bash-based examples. PowerShell is presented as the primary (and only) script-based verification method, with no mention of Linux command-line tools or scripts for this task. This creates a Windows-first and PowerShell-heavy bias, despite the cluster itself being Linux-based.

Recommendations:

Add equivalent Linux/Bash command-line examples for verifying storage accounts, such as using curl, jq, or other standard Linux tools to query the cluster REST API and parse results.
Present both PowerShell and Linux CLI examples side by side, or at least mention Linux alternatives before or alongside PowerShell.
Clarify that PowerShell is optional and provide guidance for users on Linux or macOS systems.
Ensure that all steps, especially those involving scripting or automation, have cross-platform parity to support the Linux-based nature of HDInsight clusters.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits a moderate Windows bias. The primary script referenced for adding Hive libraries is a PowerShell (.ps1) script, and the script location provided at the top is for a PowerShell script, with the Bash (Linux) script URI only appearing later in a table. The instructions and examples reference Azure PowerShell and .NET SDK before mentioning Linux-based provisioning, and Windows tools like Azure Storage Explorer are suggested for file uploads without mentioning Linux-native alternatives. The documentation does not provide Linux CLI examples for uploading files or managing storage, and the ordering of information often puts Windows/PowerShell options first.

Recommendations:

List both PowerShell and Bash script URIs together at the start, with clear guidance for Windows and Linux users.
Provide Linux-native CLI examples (e.g., using azcopy, Azure CLI, or blobfuse) for uploading files to Azure Storage, alongside Windows tools.
When mentioning provisioning methods, present Linux and cross-platform options (Azure CLI, Bash) before or alongside Windows-specific options like PowerShell and .NET SDK.
Explicitly state which script to use based on the OS/environment, and provide parity in instructions for both Windows and Linux users.
Include references to Linux-friendly tools for managing Azure Storage, such as Azure CLI or azcopy, not just Azure Storage Explorer.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing C#/.NET examples, referencing NuGet and PowerShell commands, and omitting any Linux or cross-platform CLI alternatives. All instructions and code samples are tailored to Windows development environments, with no mention of equivalent steps or tooling for Linux users.

Recommendations:

Include equivalent examples using cross-platform tools such as the Azure CLI (az), which runs on both Windows and Linux.
Provide instructions for installing required packages and dependencies on Linux (e.g., using dotnet CLI instead of NuGet/PowerShell).
Add code samples or guidance for developing .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI).
Mention and link to Linux-compatible authentication and resource management workflows.
Ensure that references to PowerShell are accompanied by Bash or shell script equivalents where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a mild Windows bias by referencing the PowerShell command 'New-SelfSignedCertificate' as the tool for creating self-signed certificates, without mentioning Linux or cross-platform alternatives. No Linux or macOS command-line examples or tools are provided for certificate creation, and the only tool-specific guidance is Windows-centric.

Recommendations:

Include equivalent Linux/macOS commands for generating self-signed certificates, such as using 'openssl'.
Explicitly mention that 'New-SelfSignedCertificate' is a Windows PowerShell command and provide cross-platform alternatives.
Add a note or section for non-Windows users, outlining steps to create and export certificates using common Linux/macOS tools.
Wherever possible, use platform-agnostic language and tools, or provide parallel instructions for each major OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias by focusing on Visual Studio and Windows-based development tools (e.g., .NET Portability Analyzer in Visual Studio 2015) without providing equivalent Linux-based workflows or examples. There are no instructions for performing portability analysis, building, or testing .NET applications using Linux-native tools or environments. The only explicit example of a file path uses a Windows-style path, and there is no mention of Linux file path conventions or Linux-based development environments.

Recommendations:

Provide examples of how to run the .NET Portability Analyzer or similar tools on Linux, such as using the command-line version or alternative open-source tools.
Include instructions for building .NET/Mono projects on Linux using tools like msbuild, dotnet CLI, or Mono's xbuild, rather than only referencing Visual Studio.
Show Linux file path conventions in code examples and highlight the need to update hardcoded Windows paths.
Offer guidance for developers who use Linux-based editors (e.g., VS Code) or command-line workflows.
Present Linux-native troubleshooting and logging techniques, not just references to Windows-based development and testing.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows environments by referencing Windows-style file paths (e.g., '\out\artifacts'), mentioning AzCopy (primarily a Windows tool) as the example for uploading files, and omitting explicit Linux/Mac instructions or examples. There are no terminal/command-line examples for Linux or Mac, nor are alternative tools (like scp, rsync, or Azure CLI) mentioned for non-Windows users. The steps and screenshots all assume a Windows environment, with no consideration for Linux or Mac users.

Recommendations:

Include Linux/Mac equivalents for file paths (e.g., '/out/artifacts') wherever Windows paths are shown.
When mentioning AzCopy, also mention cross-platform alternatives such as Azure CLI (az storage blob upload), scp, or rsync, and provide example commands for each.
Add notes or sections for Linux and Mac users, especially for steps involving file navigation, tool installation, and command-line operations.
Ensure screenshots and instructions are not Windows-specific, or provide parallel screenshots for Linux/Mac where the UI differs.
Explicitly state that IntelliJ IDEA and the Azure Toolkit are available cross-platform, and provide any OS-specific installation instructions if needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates some Windows bias by referencing and linking to Windows-centric tools (AzCopy, AdlCopy) for data movement, without mentioning or providing Linux-native alternatives. There are no explicit PowerShell or cmd.exe examples, but the data copy tooling and instructions assume the use of these Microsoft tools, which are most commonly used on Windows. Additionally, the documentation does not provide parity for Linux/Unix-native tools (such as rsync, scp, or hdfs dfs commands) for copying data, nor does it clarify cross-platform usage for AzCopy/AdlCopy. All command-line examples use SSH and standard HBase commands, which are cross-platform, but the omission of Linux-native data copy options and the exclusive mention of Windows tools constitutes a subtle bias.

Recommendations:

Include Linux-native data copy options (e.g., rsync, scp, hdfs dfs -cp) alongside AzCopy and AdlCopy, with example commands.
Clarify that AzCopy and AdlCopy are available for Linux and provide installation/use instructions for Linux environments.
When listing tools for copying data, avoid listing Windows-centric tools first or exclusively; present cross-platform options together.
Explicitly state that all SSH and HBase commands are cross-platform, and provide any OS-specific caveats if applicable.
Consider adding a table or section comparing available data movement tools for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows/PowerShell bias. All command-line instructions for creating Azure resources (resource group, storage account, blob container, file copy) are provided exclusively as PowerShell scripts, with no equivalent Bash, Azure CLI, or Linux-native instructions. The prerequisites and workflow assume the use of PowerShell, a tool primarily associated with Windows environments, and reference Windows-centric patterns (e.g., 'Write-Host', PowerShell modules). There are no Linux shell or Azure CLI alternatives, and the documentation does not mention how to perform these steps from a Linux or cross-platform environment. This could hinder accessibility for users working on Linux or macOS systems.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the steps can be performed from Linux, macOS, or Windows, and provide guidance for each platform.
Where PowerShell is referenced, add a parallel section or code block for Bash/Azure CLI users.
Clarify in the prerequisites that either PowerShell or Azure CLI can be used, and link to installation instructions for both.
Ensure that all portal navigation and screenshots are not Windows-specific and clarify that the Azure portal is web-based and OS-agnostic.
Consider including a table or toggle that lets users select their preferred environment (Windows/PowerShell or Linux/Bash/Azure CLI) for code samples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias. Windows-related FQDNs and services (e.g., WindowsUpdate, login.windows.net, login.microsoftonline.com) are listed before Linux equivalents. There is a lack of explicit Linux-focused examples or guidance, and no mention of Linux-specific tools or patterns. While Ubuntu update endpoints are included, the overall framing and examples prioritize Windows services and tools, with no parity in Linux-specific configuration or troubleshooting steps.

Recommendations:

Provide explicit Linux-focused examples, such as referencing Linux package update endpoints (e.g., security.ubuntu.com, mirrors for other distributions) alongside WindowsUpdate.
List Linux and Windows dependencies together, or alternate their order to avoid always placing Windows first.
Include troubleshooting or configuration steps relevant to Linux users, such as using SSH from Linux/macOS terminals, or configuring iptables/firewalld if relevant.
Mention Linux authentication endpoints or scenarios, if applicable, alongside Windows login endpoints.
Clarify that the guidance applies equally to both Windows and Linux-based HDInsight clusters, and call out any differences in requirements.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides comprehensive coverage of script actions for Azure HDInsight clusters, but it demonstrates a Windows bias by prioritizing Azure PowerShell and .NET SDK examples and instructions before Azure CLI and REST API equivalents. PowerShell cmdlets are featured prominently, often with more detailed examples, while Azure CLI instructions are less detailed or appear after PowerShell. There is also a focus on .NET SDK usage, which is more common in Windows-centric environments. Although the documentation is about Linux-based clusters and Bash scripts, the tooling and automation examples are skewed toward Windows/PowerShell users.

Recommendations:

Ensure that Azure CLI examples are provided with equal detail and prominence as PowerShell examples, especially for common tasks such as applying, promoting, and demoting script actions.
Present Azure CLI and PowerShell instructions side-by-side or in parallel sections, rather than listing PowerShell first.
Include REST API and ARM template examples with the same level of detail as PowerShell and .NET SDK.
Highlight cross-platform tools (such as Azure CLI) as the default or preferred method for automation, given the Linux context.
Add explicit notes or sections for Linux/macOS users, including any prerequisites or environment setup steps for non-Windows platforms.
Where .NET SDK is mentioned, also reference Python or Java SDKs if available, or clarify that .NET is cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows users: all file and directory commands use Windows Command Prompt syntax, file editing is done with Notepad, and troubleshooting uses PowerShell scripts. There are no equivalent Linux/macOS commands or editor suggestions, despite HDInsight clusters being Linux-based. Linux command-line patterns (e.g., mkdir, rm, nano/vi) are missing, and Windows tools are mentioned exclusively or first.

Recommendations:

Provide Linux/macOS equivalents for all command-line instructions (e.g., use mkdir, cd, rm -rf, nano/vi for file editing).
Include both Windows and Linux/macOS command blocks side by side or in tabs for each step.
Suggest cross-platform editors (e.g., VS Code, nano, vi) instead of only Notepad.
For troubleshooting, provide Linux command-line solutions (e.g., dos2unix, sed) for fixing line endings, not just PowerShell.
Clarify at the start that instructions are for Windows and provide a parallel set for Linux/macOS users.
Where possible, use platform-neutral language and tools, especially since HDInsight clusters are Linux-based.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates several forms of Windows bias. In the 'Check cluster connectivity' step, the only example for deploying a test VM uses a Windows 10 image, with RDP as the default access method, and requires a Windows license. The instructions for testing SSH access begin from a Windows command prompt, with no mention of Linux or cross-platform alternatives. In the cluster deployment section, the PowerShell example is mentioned before the Azure CLI example, and there are no explicit Linux shell or Bash examples. Throughout the page, tooling and workflows are described primarily in terms of the Azure portal and Windows-centric patterns, with no guidance for Linux users or those using non-Windows environments.

Recommendations:

Provide parallel Linux-based examples for deploying a test VM (e.g., Ubuntu or CentOS), including SSH access instructions from a Linux terminal.
When referencing command-line tools, present Azure CLI (cross-platform) examples before or alongside PowerShell, and include Bash syntax where appropriate.
In connectivity testing, show how to use SSH from both Windows (e.g., PowerShell or CMD) and Linux/macOS terminals.
When describing VM deployment, offer both Windows and Linux image options, and clarify that either can be used for testing connectivity.
Review all step-by-step instructions to ensure Linux users are not excluded or forced to adapt Windows-specific steps.
Where GUI instructions are given (e.g., Azure portal), consider adding CLI alternatives for automation and scripting, which are platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation frequently presents Windows instructions and examples before Linux equivalents, and in some cases, Linux instructions are less detailed or have additional restrictions. There are also sections where only Windows-specific tools or paths are referenced, and Linux users are sometimes redirected or given less guidance.

Recommendations:

Ensure that Linux instructions and examples are presented alongside Windows, or in parallel, rather than after or as an afterthought.
Provide equally detailed Linux examples for all languages and scenarios, including local development and configuration steps.
Avoid language such as 'select the Windows tab' as the default; instead, present both OS options equally.
Where features are not available on Linux (e.g., Python on Windows), clearly explain alternatives or workarounds for Linux users.
Review all code samples and ensure that Linux command-line and file path conventions are included where relevant.
Where possible, use cross-platform tools and instructions (such as Azure CLI) as the primary example, and only provide OS-specific guidance when necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias in several ways: Windows paths and deployment patterns are consistently mentioned before Linux equivalents, and Windows-specific folders (e.g., c:\home\data\SitePackages) are referenced throughout. There is a lack of Linux-specific command-line or shell examples, and no Linux-native tooling or deployment workflows are highlighted. The documentation assumes familiarity with Windows conventions and tools, with only minimal parity for Linux mentioned as afterthoughts.

Recommendations:

Present Linux and Windows instructions/examples side by side or in parallel sections, rather than always listing Windows first.
Include Linux-native command-line examples (e.g., bash, zip, scp, az CLI on Linux) for creating and deploying packages.
Reference Linux paths first or equally, and avoid assuming Windows as the default environment.
Highlight Linux-specific deployment considerations and tools (such as using Linux shells, permissions, or automation scripts).
Provide explicit Linux troubleshooting steps and examples, not just Windows-centric advice.
Where UI steps are described, mention any differences for Linux users (e.g., Azure CLI vs. Azure Portal).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. In most sections, examples are provided for Azure CLI, Azure PowerShell, and the Azure Portal, but there is a consistent presence of PowerShell (a Windows-centric tool) as a primary example. In OS update queries, Windows and general OS queries are presented before Linux-specific queries, and the Linux example appears later in the document. There are no Linux-native command-line examples (e.g., Bash scripts or Linux-specific tooling) outside of the Azure CLI, and terminology and patterns (such as PowerShell) are more familiar to Windows users. The documentation does not provide parity in Linux-native usage or highlight Linux-specific considerations except in one dedicated Linux section.

Recommendations:

Provide Linux-native command-line examples (e.g., Bash, shell scripts) alongside PowerShell, especially for scenarios where users may interact with Azure from Linux environments.
Ensure that Linux-specific queries and examples are given equal prominence and are not grouped only at the end or in a separate section.
Where PowerShell is used, clarify that it is cross-platform or provide explicit Linux installation/use instructions.
Highlight any differences in resource properties or behaviors between Windows and Linux VMs in the documentation.
Consider adding a table or section summarizing OS-specific queries for both Windows and Linux at the top of the page for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation displays a mild Windows bias: Windows/PowerShell examples and links are presented before Linux equivalents, and references to Windows-specific tools and documentation are more prominent. The prerequisites and important notes link only to Windows-specific IMDS documentation, and troubleshooting/learning links default to Windows tabs. While a Linux example is present, Linux documentation is less emphasized.

Recommendations:

Present Linux and Windows examples in parallel or in a neutral order, or default to a platform-agnostic example.
Ensure all documentation links (e.g., prerequisites, further reading) include both Windows and Linux versions or use platform-neutral links.
Add Linux-specific notes where relevant (e.g., proxy bypassing in curl).
Avoid referencing Windows tools or documentation exclusively; mention Linux equivalents with equal prominence.
Consider a 'Platform' selector at the top of the page to allow users to choose their OS context.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both PowerShell and Azure CLI examples for creating a service principal, but the PowerShell example is presented first and is described as being tested in Visual Studio Code, which is more commonly associated with Windows environments. There is no explicit mention of Linux or macOS compatibility, nor are there any bash-specific or Linux shell examples, which may leave Linux users uncertain about cross-platform support.

Recommendations:

Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh shell context for CLI examples.
Add a note or section confirming that all steps are cross-platform and highlight any differences (if any) for Linux/macOS users.
Consider presenting Azure CLI (which is cross-platform) examples before PowerShell, or at least in parallel, to avoid a Windows-first impression.
If Visual Studio Code is mentioned, clarify that it is available on all major platforms, or suggest alternatives for Linux users.
Include troubleshooting tips or links for Linux users who may encounter environment-specific issues.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing PowerShell scripts as the primary or only scripting example for deploying ARM templates, and by referencing PowerShell before or in more detail than cross-platform alternatives. There are no explicit Linux shell (bash) or scripting examples for ARM template deployment, and the PowerShell deployment script is presented without a CLI or bash equivalent. While Azure CLI is included for service creation, the overall pattern prioritizes Windows-native tooling and omits Linux-native command-line workflows.

Recommendations:

Add bash or shell script examples for ARM template deployment using Azure CLI (e.g., az deployment group create) to ensure Linux users have parity.
When presenting scripting examples, provide both PowerShell and bash/CLI alternatives side by side.
Avoid presenting PowerShell as the only automation option for deployment; always include cross-platform CLI commands.
Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide any OS-specific notes if needed.
Review the order of examples to avoid always listing Windows/PowerShell first; consider alternating or grouping by platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. It only references the creation of Windows server virtual machines, uses Windows-specific tools (IIS), and provides PowerShell examples. There are no mentions or examples for Linux VMs, Linux web servers (such as Apache or Nginx), or Linux command-line tools. The steps and examples are tailored exclusively to Windows users, leaving Linux users without guidance.

Recommendations:

Add parallel instructions and examples for creating and configuring Linux virtual machines.
Include steps for setting up popular Linux web servers (e.g., Apache, Nginx) alongside IIS.
Provide Linux CLI examples (using Bash/Azure CLI) for all configuration steps.
Ensure that portal, CLI, and PowerShell sections all include Linux-specific guidance where relevant.
Mention Linux as an option in the tutorial introduction and checklist, not just Windows.
Balance the order of presentation so that Linux and Windows are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing PowerShell instructions and prerequisites before CLI/Bash equivalents, and by recommending Git Bash (from Git for Windows) as the Bash shell for CLI users. PowerShell is presented as a primary automation method, and the CLI section assumes a Bash shell but specifically references a Windows-centric tool (Git Bash) rather than native Linux/macOS terminals. However, Linux CLI parity is generally maintained in the examples.

Recommendations:

In the CLI prerequisites, mention native Bash shells on Linux and macOS first, then mention Git Bash for Windows users as an alternative.
Reorder the sections so that CLI (cross-platform) instructions appear before PowerShell (Windows-centric) instructions, or clarify that both are equally supported.
In the prerequisites and instructions, avoid phrasing that implies PowerShell is the default or preferred automation tool.
Explicitly state that all CLI examples work natively on Linux and macOS terminals, and provide any necessary notes for Windows users.
Where possible, provide links or notes for installing Bash on all platforms, not just Git Bash for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by presenting PowerShell as the primary method for registering the resource application, mentioning it before the Azure CLI alternative. The use of PowerShell and the 'azurepowershell-interactive' code block further reinforces a preference for Windows tooling and workflows. While Azure CLI is mentioned, there is no explicit mention of Linux or cross-platform environments, and no Linux-specific guidance or examples are provided.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more inclusive of Linux/macOS users.
Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for running them in different environments.
If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or provide Bash shell equivalents where appropriate.
Add a section or note highlighting Linux/macOS compatibility and any prerequisites for running the commands on those platforms.
Review and update custom metadata (e.g., 'devx-tr2ck-azurepowershell') to ensure it does not reinforce a Windows-centric approach.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing all command-line and scripting examples in PowerShell, referencing .NET tooling (dotnet user-secrets, dotnet run) without mentioning cross-platform compatibility, and omitting equivalent Linux/bash examples. There is no mention of Linux-specific tools or alternative shell commands, and the workflow assumes familiarity with Windows-centric patterns.

Recommendations:

Provide equivalent bash/Linux shell script examples for all PowerShell commands, such as base64 encoding and string manipulation.
Clarify that .NET Core and related tools (dotnet CLI) are cross-platform, and provide explicit instructions for Linux/macOS users where paths or commands may differ.
Include notes or sections for Linux/macOS users, especially for steps involving local development, environment variable management, and running the sample app.
When referencing file paths or localhost URLs, mention any differences in how these are handled on non-Windows systems.
Where screenshots or UI instructions are given, clarify if there are any differences for users on other operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by exclusively describing the asymmetric name mapping process using Windows tools (Active Directory Users and Computers MMC) and workflows. There are no equivalent instructions or references for performing similar LDAP attribute modifications using Linux-native tools or command-line utilities, despite the hybrid environment context.

Recommendations:

Add parallel instructions for modifying LDAP attributes using Linux tools such as ldapmodify, ldapvi, or Apache Directory Studio.
Include examples of how to update the UID field for a user in LDAP from a Linux system, possibly with command-line snippets.
Present both Windows and Linux methods side-by-side or in separate sections to ensure parity and inclusivity for administrators on either platform.
Reference cross-platform LDAP management tools where appropriate, and clarify that the process is not limited to Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing a PowerShell snippet for base64-encoding a PFX file, without offering a Linux/Unix equivalent (such as an OpenSSL or base64 command-line example). The only tool-specific guidance is for Windows/PowerShell users, and no Linux or cross-platform alternatives are mentioned. This may hinder Linux users from following the instructions seamlessly.

Recommendations:

Add equivalent Linux/Unix shell commands for base64-encoding a PFX file, such as using 'base64' and 'openssl'.
Explicitly mention that the certificate conversion and encoding can be performed on any platform, and provide cross-platform examples.
Wherever PowerShell or Windows-specific tools are referenced, provide parallel instructions for Bash/Linux environments.
Review the documentation for other subtle Windows-first assumptions, ensuring parity in tool and workflow recommendations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for all Azure CLI and scripting examples, stating 'we're using PowerShell' without providing Bash or Linux shell equivalents. There are no Linux/macOS-specific instructions or examples, and variable assignment and command usage are tailored to PowerShell users. This may hinder accessibility for users on Linux or macOS platforms who use Bash or other shells.

Recommendations:

Provide parallel Bash/Linux shell examples for all Azure CLI commands and scripting steps, especially for variable assignment and command chaining.
Explicitly mention that Azure CLI works cross-platform and that users can use Bash, zsh, or other shells on Linux/macOS.
Where PowerShell-specific syntax is used (e.g., variable assignment with $Var = ...), show the Bash equivalent (e.g., VAR=...) side-by-side.
In the prerequisites or opening sections, clarify that the tutorial is cross-platform and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash) users.
For clean-up and other scripting sections, ensure Bash alternatives are present and tested.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell commands and instructions for configuring Azure Storage networking and permissions. There are no equivalent examples or guidance for Linux or cross-platform tools (such as Azure CLI, Bash, or REST API via curl). The use of PowerShell is presented as the default and only scripting method, and Windows-centric tools are referenced without mention of alternatives.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell examples, especially for installing modules and configuring storage account network rules.
Include Bash/curl examples for REST API interactions where applicable.
Explicitly mention that PowerShell commands can be run cross-platform (if true), or clarify platform requirements.
Present cross-platform or Linux-native instructions alongside or before Windows/PowerShell examples.
Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently lists PowerShell as a primary scripting option and often mentions it before Azure CLI or REST API, which can be used cross-platform. There are no explicit Linux/bash examples or references to Linux-specific tools or workflows. The document also highlights Power BI (a Windows-centric tool) for analytics, with no mention of Linux-friendly alternatives. While cURL and REST Client are mentioned, there is a general lack of parity in example scripts or guidance for Linux users.

Recommendations:

Ensure that all scripting examples are provided in both PowerShell and bash/Azure CLI formats, with equal prominence.
When listing scripting options, alternate the order or explicitly state that Azure CLI and REST API are cross-platform.
Include Linux-specific guidance or examples, such as using bash scripts, and clarify that cURL and REST Client are available on Linux.
For analytics, mention cross-platform tools (such as Jupyter Notebooks, Python/pandas, or open-source BI tools) alongside Power BI.
Review linked sample scripts to ensure they include bash/Linux equivalents and are not PowerShell-exclusive.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias: all command-line examples use PowerShell syntax and Windows-style paths, with no Linux/macOS shell equivalents. Directory and file paths are shown in Windows format (e.g., C:\msBuildDemo), and project file examples reference the Windows-specific Bicep CLI package by default. Instructions for creating and cleaning up directories, as well as running MSBuild, are provided only for Windows/PowerShell, with no bash or cross-platform alternatives. Linux and macOS are mentioned in package lists, but practical usage guidance is missing.

Recommendations:

Provide equivalent bash/zsh command-line examples for Linux/macOS, including directory creation, navigation, and cleanup (e.g., mkdir, cd, rm -rf).
Show both Windows (\) and Unix-style (/) path separators in file and directory paths, or use cross-platform variables.
In project file examples, demonstrate referencing the appropriate Azure.Bicep.CommandLine package for each OS, or show how to use environment variables for BicepPath in a cross-platform way.
Include explicit instructions for running MSBuild and dotnet CLI commands on Linux/macOS, noting any differences (such as using 'msbuild' instead of 'MSBuild.exe').
Add tabs or callouts for Linux/macOS alongside Windows in all step-by-step instructions.
Ensure that all prerequisite and setup steps (such as installing PowerShell or using a shell) are clearly cross-platform, or provide alternatives for each OS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page references tools and workflows that are primarily associated with Windows environments, such as PowerShell scripts (.ps1), Visual Studio Code extensions, and Azure Data Factory pipelines, without mentioning or providing equivalent Linux or cross-platform alternatives. There are no explicit Linux or bash examples, and the only script linked is a PowerShell script, suggesting a Windows-first approach.

Recommendations:

Provide Linux/bash shell script examples or equivalents alongside PowerShell scripts, especially for automation tasks (e.g., creating Synapse external tables).
Mention and link to cross-platform tools or clarify when tools (such as VS Code extensions) are available on Linux/macOS as well as Windows.
Include references to Linux-native workflows (e.g., using Azure CLI in bash, or running tools in Docker containers) where appropriate.
Explicitly state platform compatibility for each tool or script, and provide installation or usage instructions for Linux users.
Where Azure Data Factory or other Windows-centric tools are mentioned, suggest or document alternative approaches that are commonly used in Linux environments (e.g., Apache NiFi, custom Python scripts, etc.).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns (such as Azure SQL Server, Power BI, and Microsoft Teams) without mentioning Linux-compatible alternatives or cross-platform options. There are no command-line or code examples, but the exclusive mention of these Microsoft ecosystem tools and the absence of Linux or open-source equivalents suggest an implicit prioritization of Windows environments.

Recommendations:

Include references to cross-platform or Linux-friendly alternatives for data repositories (e.g., PostgreSQL, MySQL) and BI tools (e.g., Grafana, Kibana) alongside Azure SQL Server and Power BI.
Mention that Azure services (such as Azure Databricks, Azure Functions, and Azure Data Lake) are accessible from both Windows and Linux environments.
Provide examples or guidance for integrating with open-source or Linux-based care coordination tools in addition to Microsoft Teams.
Explicitly state the cross-platform compatibility of the solution components where applicable.
Where possible, add sample workflows or architectural notes for Linux-based deployments or hybrid environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation frequently mentions PowerShell and Azure CLI scripts for client application registration and access token retrieval, often listing PowerShell before Azure CLI. It references .NET SDK and C# as access tools, which are more commonly associated with Windows environments. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, nor are Linux-specific tools or workflows highlighted. The documentation lacks parity in presenting Linux-native approaches or examples, and Windows-centric tools are mentioned first or exclusively.

Recommendations:

Provide explicit Bash or Linux shell examples alongside or before PowerShell examples.
Mention Azure CLI as the primary cross-platform tool, and clarify that it works on Linux, macOS, and Windows.
Include examples using Linux-native tools (e.g., Bash scripts, curl) for authentication and API access.
Balance references to .NET/C# with Python or JavaScript examples, which are more cross-platform.
Clearly state that all features and workflows are supported on Linux and macOS, not just Windows.
Where screenshots are used, include examples from non-Windows environments when possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by describing Windows SMB inheritance controls first and in more detail, including a screenshot of the Windows interface, while Linux/NFS methods are only briefly mentioned without visual aids or command-line examples. Windows terminology and tools are foregrounded, and there are no Linux/NFS command examples or screenshots.

Recommendations:

Provide equivalent Linux/NFS examples, such as showing how to set inheritance with setfacl or chmod on NFSv4.1.
Include screenshots or command-line snippets for Linux/NFS permission management, not just Windows GUI.
Present Windows and Linux/NFS instructions in parallel, rather than describing Windows first and in more detail.
Expand on Linux/NFS permission inheritance, including practical steps and best practices.
Balance the use of terminology and visuals between Windows and Linux/NFS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell, referencing .NET SDK and dotnet user-secrets (which are more familiar to Windows users), and omitting equivalent Linux/bash commands or guidance. There are no explicit Linux or cross-platform instructions for cloning repositories, running scripts, or setting environment variables, which may hinder Linux users.

Recommendations:

Provide all command-line examples in both PowerShell and bash (or at least indicate bash equivalents).
Explicitly mention that .NET SDK and dotnet user-secrets are cross-platform, and provide Linux/macOS installation and usage notes.
When referencing file paths, use platform-neutral or dual examples (e.g., forward and backslashes).
Add a section or callout for Linux/macOS users, highlighting any differences in setup or command usage.
Where scripts are shown (e.g., for base64 encoding), provide both PowerShell and bash (or Python) versions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively recommending Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no command-line or cross-platform instructions (such as using Azure CLI, IoT CLI, or Python scripts), and all tooling is presented in a way that assumes a Windows/GUI workflow. No Linux-specific or cross-platform examples or tools are referenced.

Recommendations:

Include instructions for using Azure CLI or Azure IoT CLI to create devices and send test messages, which work on both Windows and Linux.
Provide examples using cross-platform tools such as Python scripts (using the Azure IoT SDK) for device simulation.
Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux and macOS, or provide alternative workflows for users who prefer not to use a GUI.
Add a section or callout for Linux users, outlining the equivalent steps using terminal commands.
Ensure screenshots and step-by-step instructions are not solely focused on Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools (PsPing, TCPing, netstat, netsh) in troubleshooting steps, providing Windows command examples first or exclusively, and only briefly mentioning Linux equivalents (netstat -l, sudo iptables -L) as secondary notes. There are no Linux-specific troubleshooting tools or detailed Linux command examples, and the overall troubleshooting workflow assumes a Windows environment.

Recommendations:

Provide Linux-first or parallel Linux command examples alongside Windows commands for each troubleshooting step.
Include Linux-native tools (e.g., ss, nc/ncat, lsof, firewalld-cmd, ufw) for port and firewall checks, with example commands.
Offer example commands for both Windows and Linux for connectivity testing (e.g., using nc or curl for Linux instead of only PsPing/TCPing).
Explicitly state that the instructions apply to both Windows and Linux VMs, and structure sections so that Linux and Windows guidance are equally prominent.
Where third-party tools are suggested (PsPing, TCPing), recommend open-source or pre-installed Linux alternatives and provide installation instructions if needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. It provides only PowerShell commands for certificate management and testing, references Windows-specific certificate stores (Cert:\LocalMachine\Root), and explicitly states that private client certificates are only supported from custom code in Windows code apps. There are no Linux or cross-platform examples, and Linux scenarios are not addressed.

Recommendations:

Provide equivalent Linux/Bash examples for certificate creation (e.g., using openssl) and certificate management.
Clarify support for Linux-based App Service apps, including any limitations or alternative approaches.
Include instructions for accessing and managing certificates on Linux-based workers (e.g., using Kudu Bash console, Linux file paths).
Mention Linux tools (such as openssl) alongside PowerShell, and avoid presenting Windows tools first or exclusively.
Explicitly state platform limitations at the beginning of relevant sections, and offer guidance or workarounds for Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates some Windows bias, particularly in the .NET and Python sections. For .NET, Windows tools like Visual Studio and Azure PowerShell are listed before cross-platform or Linux-native options. In the Python section, most quickstart links default to 'windows' tabs, and Linux-specific instructions are not highlighted or are less visible. Azure PowerShell, a Windows-centric tool, is promoted alongside or before CLI options. Linux-specific tools and workflows are less emphasized or missing in some stacks (e.g., .NET).

Recommendations:

In .NET sections, list cross-platform tools (e.g., Visual Studio Code, CLI) before Windows-only tools (e.g., Visual Studio, Azure PowerShell).
Ensure that Linux and cross-platform CLI examples are present and prominent for all stacks, especially .NET and Python.
For Python, provide explicit Linux/macOS quickstart tabs and links, not just 'windows' defaults.
Where Azure PowerShell is mentioned, also mention Azure CLI as an equal or preferred cross-platform alternative.
Add or highlight Linux-native workflows and tools (e.g., Bash, Linux package managers) where appropriate.
Review all quickstart and tutorial links to ensure Linux parity and visibility, not just as an afterthought or in a secondary position.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in the 'Server level (Windows apps only)' section, where it provides detailed instructions for configuring authorization using IIS and web.config, which are exclusive to Windows. There is no equivalent example or guidance for Linux-based App Service apps. Additionally, the section is presented before any mention of Linux alternatives, and no Linux-native tools or configuration patterns are discussed.

Recommendations:

Add a parallel section for Linux-based App Service apps, providing equivalent guidance for configuring authorization (e.g., using middleware in common frameworks like Node.js, Python, or .NET Core).
Explicitly state that Linux apps require different approaches and link to relevant documentation or examples for Linux environments.
Where possible, present Windows and Linux options side-by-side to avoid the perception of Windows as the default or preferred platform.
Include sample code or configuration for popular Linux web servers (e.g., Nginx, Apache) or application-level authorization patterns.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias in several ways: (1) Windows-specific examples and tools (e.g., PowerShell, Windows registry paths) are provided first or exclusively in key sections, especially in the Bicep, ARM template, PowerShell, and removal instructions. (2) There is a lack of equivalent Linux-focused examples for core automation scenarios (e.g., Bicep/ARM templates and PowerShell/CLI commands are tailored to Windows VMs and extensions, with no Linux VM or extension examples). (3) PowerShell is heavily featured, with less emphasis on bash or Linux-native scripting. (4) Windows-specific requirements and tools (e.g., .NET Framework, Windows PowerShell 5.1) are highlighted, while Linux requirements are less detailed or are presented as secondary.

Recommendations:

Provide Linux-specific examples alongside Windows examples for Bicep, ARM templates, REST API, Azure CLI, and PowerShell sections. For instance, show how to deploy a Linux VM and install the HybridWorkerForLinux extension.
Ensure that Linux commands and requirements are given equal prominence and detail as Windows, including bash scripts and Linux-native automation tools.
When listing prerequisites, present Windows and Linux requirements in parallel, and avoid listing Windows first by default.
For PowerShell-heavy sections, provide equivalent bash or shell script examples for Linux users.
Clarify when a step or tool is Windows-only, and always provide the Linux alternative immediately after or in a side-by-side format.
In code samples and parameter tables, include Linux OS options and extension types (e.g., HybridWorkerForLinux) wherever Windows options are shown.
Expand the removal instructions for Linux to include cleanup of all related components, matching the detail provided for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is featured heavily in code examples, often before or alongside Azure CLI, and is the only scripting language shown for advanced scenarios (e.g., multi-source rules, Azure Front Door filtering). There are no Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and the PowerShell examples are not explicitly marked as cross-platform (i.e., using PowerShell Core). While the Azure CLI is included, the advanced and inline scripting guidance favors PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Provide bash (Linux shell) script examples for all scenarios where PowerShell is shown, especially for advanced use cases like multi-source rules and HTTP header filtering.
Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Where PowerShell is used, specify if the commands are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
In advanced scenarios, ensure that Azure CLI and bash examples are given equal prominence to PowerShell.
Consider including a note or table summarizing which management tools are available on which platforms.
Avoid presenting PowerShell examples before Azure CLI or bash unless there is a technical reason to do so.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions, but the PowerShell section is more detailed and assumes use of a local PowerShell terminal. There are references to Windows-specific issues (e.g., native modules lacking Windows binaries) and tools (PowerShell, Git Credential Manager dialog). There is no explicit mention or example of using Linux-specific shells or tools, and the troubleshooting section references Windows-specific errors without Linux equivalents.

Recommendations:

Add explicit Linux/macOS terminal examples alongside PowerShell, especially for steps like changing directories and running commands.
Clarify that Azure CLI commands can be run in Bash, Zsh, or other Unix shells, and provide sample commands in those contexts.
Include troubleshooting notes for common Linux/macOS issues (e.g., SSH key permissions, credential manager differences).
Avoid assuming the presence of the Git Credential Manager dialog, which is Windows-specific; mention alternatives for Linux/macOS.
Balance error message examples to include those commonly encountered on Linux/macOS.
Where PowerShell is mentioned, also mention Bash or other common Linux shells as alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides cross-platform deployment examples for most stacks, but the ASP.NET (classic) section exclusively uses a Windows runner and Windows-specific tools (NuGet, MSBuild) without offering Linux alternatives or parity. All other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use Ubuntu runners and standard, cross-platform tooling. The ASP.NET section is both Windows-first and Windows-only, lacking Linux-based workflow examples.

Recommendations:

Add a Linux-based (ubuntu-latest) workflow example for ASP.NET (classic), using Mono and cross-platform equivalents of NuGet and MSBuild where possible.
Explicitly state in the ASP.NET section why a Windows runner is required (if so), or provide guidance for Linux users.
Reorder or clearly label sections to avoid implying Windows is the default or only supported environment for .NET workloads.
Where Windows-specific tools are used, mention if cross-platform alternatives exist or provide links to relevant documentation.
Ensure parity in example depth and clarity between Windows and Linux workflows for all stacks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Azure-specific tools and patterns (such as Azure AD, RBAC, and SMB/NTLMSSP) are emphasized, and Windows-centric protocols (SMB) and tools (AzCopy) are mentioned before or more prominently than their Linux equivalents. While Linux/NFS examples are present, there is a lack of parity in command-line examples for Linux tools (e.g., rsync is only briefly mentioned in best practices, not in detailed steps or examples), and Windows/SMB mounting is described in more detail. There are no PowerShell-specific examples, but the overall focus is on Azure-native and Windows-friendly approaches.

Recommendations:

Provide Linux-native command-line examples (e.g., rsync, scp, or Linux AzCopy usage) alongside or before Windows/Azure tools.
When describing mounting procedures, offer both Linux and Windows client instructions (e.g., show how to mount Azure Files on Windows using PowerShell or 'net use', and on Linux using 'mount -t cifs').
Include explicit Linux authentication and access control guidance (e.g., using Linux PAM, Kerberos, or LDAP with Azure AD integration) to balance the focus on Azure AD/RBAC.
Mention open-source or cross-platform alternatives to Azure Data Factory and AzCopy, such as Apache NiFi, rclone, or native Linux scripting.
Ensure that Linux/NFS and Windows/SMB examples are given equal prominence and detail in all setup and deployment sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows and Visual Studio on Windows. All instructions, screenshots, and tooling references assume the user is on Windows, using Visual Studio, and deploying to Azure App Service (Windows). There are no examples or guidance for Linux users, alternative IDEs, or command-line workflows. PowerShell and Windows-specific tools (e.g., Package Manager Console, SQL Server Object Explorer) are used exclusively, with no mention of cross-platform or Linux alternatives.

Recommendations:

Provide parallel instructions for Linux users, including how to use VS Code or the .NET CLI for project management, publishing, and database migrations.
Include examples using Azure CLI and Bash for tasks such as database creation, managed identity configuration, and deployment.
Show how to deploy to Azure App Service (Linux) and highlight any differences or considerations.
Reference cross-platform tools (e.g., Azure Data Studio, sqlcmd for Linux/macOS) instead of or in addition to Windows-only tools like SQL Server Object Explorer.
Add notes or sections for Mac users, especially regarding prerequisites and environment setup.
Ensure screenshots and UI instructions are not exclusively tied to Visual Studio on Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows development environments, specifically Visual Studio on Windows. All instructions, UI references, and publishing steps assume the use of Visual Studio 2022, with no mention of cross-platform alternatives such as Visual Studio Code, Azure CLI, or command-line tools available on Linux/macOS. The publishing process explicitly targets 'Azure Function App (Windows)', and there are no examples or guidance for Linux users or those preferring non-Windows workflows.

Recommendations:

Provide alternative instructions for Linux/macOS users, such as using Visual Studio Code, Azure CLI, or the Azure Functions Core Tools.
Include command-line examples for project creation, dependency installation, and publishing that work on all platforms.
Mention and demonstrate how to use cross-platform editors (e.g., VS Code) and tools (e.g., dotnet CLI, func CLI) alongside or instead of Visual Studio.
Clarify that Azure Functions and API Management are cross-platform services, and show how to deploy to Linux-based Function Apps.
Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented equally, rather than Windows-first or Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally provides parity between Windows and Linux for most configuration tasks, using Azure CLI examples for both. However, there is a subtle Windows bias: Windows instructions and tools (such as IISNode, web.config, and PowerShell references) are often mentioned first or in more detail, and some troubleshooting and monitoring steps reference Windows-specific tools or patterns (e.g., web.config, PowerShell) without always providing equivalent Linux guidance. The Application Insights section references PowerShell for instrumentation but does not mention a Linux/CLI alternative. The troubleshooting section for Windows is more detailed than for Linux.

Recommendations:

Ensure that for every Windows-specific tool or configuration (e.g., web.config, IISNode, PowerShell), an equivalent Linux/container approach is described with equal detail and prominence.
When listing platform pivots, alternate the order or present Linux first in some sections to avoid the impression of Windows primacy.
In the Application Insights section, provide explicit CLI or Linux-native instructions for enabling instrumentation, not just PowerShell.
Expand Linux troubleshooting guidance to match the depth provided for Windows (e.g., what to do if the app doesn't start, common container issues, etc.).
Where possible, avoid referencing Windows-only tools (like web.config or IISNode) without clear Linux/container alternatives or explanations.
Audit for any remaining sections where Windows is the default or first-mentioned platform, and balance with Linux-first or cross-platform-neutral language.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and workflows centered around PowerShell cmdlets and scripting. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide parity or guidance for Linux users or those using non-Windows environments.

Recommendations:

Explicitly state that Azure Automation graphical runbooks are currently limited to PowerShell and clarify platform support (e.g., Windows-only or cross-platform PowerShell Core).
If Linux support is available (e.g., via PowerShell Core on Linux), provide examples and guidance for Linux users, including any differences in cmdlet availability or behavior.
Include a section comparing graphical runbooks with textual runbooks, highlighting scenarios where Bash, Python, or other languages (supported in Azure Automation) may be preferable, and link to relevant documentation.
Mention any limitations or considerations for Linux-based Automation workers, if applicable.
Where possible, provide cross-platform PowerShell examples (using PowerShell Core syntax) and clarify when examples are Windows-specific.
Add references or links to documentation for authoring and running runbooks in other languages (Bash, Python) for users who do not use PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed explanations and tooling references for Windows (such as IIS Application Initialization and .NET Core stdout logging), mentioning Windows-specific features and modules first, and only briefly mentioning Linux equivalents (e.g., WEBSITE_WARMUP_PATH) without comparable detail or examples. There are no Linux command-line or configuration examples, and Linux-specific patterns are not discussed in depth.

Recommendations:

Provide Linux-specific examples and configuration steps alongside Windows examples, especially for features like application initialization and logging.
Mention Linux and Windows options together, or alternate which platform is presented first in each section.
Include references to Linux-native tools and patterns (e.g., systemd, NGINX, Apache, or Linux startup scripts) where relevant.
Expand on the use of WEBSITE_WARMUP_PATH for Linux, including example configurations and best practices.
Offer parity in troubleshooting/logging guidance for Linux (e.g., stdout/stderr log collection, integration with Linux logging systems).
Ensure that all features and recommendations are clearly marked as Windows-only, Linux-only, or cross-platform, and provide alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively uses PowerShell for all examples and instructions, assumes the use of Azure PowerShell (a Windows-centric tool), and does not provide any equivalent Bash, CLI, or Linux-native examples. All command references and cleanup instructions are PowerShell-specific, with no mention of cross-platform alternatives or Linux workflows.

Recommendations:

Provide equivalent examples using Azure CLI (az) with Bash syntax, which is cross-platform and widely used on Linux and macOS.
Include a section or tabbed examples for both PowerShell and Bash/Azure CLI to ensure parity for Linux users.
Mention installation and usage instructions for Azure CLI alongside Azure PowerShell.
Reference Linux/macOS compatible tools and workflows where appropriate, not just Windows/PowerShell.
Ensure that cleanup and deployment steps are shown for both PowerShell and Bash environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally provides parity between Windows and Linux instructions via platform pivots. However, there are several areas where Windows-specific tools (e.g., KuduScript, directory paths, DLLs) are mentioned or explained in more detail, and Windows instructions or concepts are presented first. Some sections (such as custom deployment scripts and Composer automation) are much more detailed for Windows, with Linux equivalents either missing or less explicit.

Recommendations:

Ensure that all examples and instructions provided for Windows (such as custom deployment scripts, Composer automation, and enabling extensions) have equally detailed Linux equivalents.
Avoid presenting Windows instructions or tools first by default; alternate the order or clarify that both platforms are equally supported.
Where Windows-specific tools (like KuduScript) are mentioned, provide Linux-native alternatives or clarify their applicability to Linux environments.
For sections that discuss directory structures or file extensions (e.g., .dll vs .so, d:\ paths vs /home/site), explicitly note the Linux equivalents and provide parallel examples.
Expand the Linux 'Run Composer' and 'Run Bower, Gulp, or Grunt' sections to match the detail and step-by-step guidance given for Windows.
Review all troubleshooting and advanced configuration sections to ensure Linux users are not left with less actionable guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and first, while Linux support is described more generically and with fewer examples. Windows-specific tools and patterns are named explicitly, whereas Linux examples are minimal and lack parity in detail.

Recommendations:

Provide a more comprehensive list of supported file types for Linux, similar to the Windows section (e.g., include *.py*, *.pl*, *.php*, *.rb*, etc. if supported).
List Linux examples with the same level of detail as Windows, including explicit mentions of runtimes and file types.
Avoid listing Windows tools and patterns (cmd, PowerShell) before Linux equivalents; consider parallel structure or a neutral order.
Include example scenarios for Linux containers similar to those given for Windows containers (e.g., mention Java, .jar, .war, etc. if supported).
Clarify if runtimes for Linux file types are pre-installed, as is stated for Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a strong Windows bias by requiring the use of the WAImportExport tool, which is explicitly stated to be compatible only with 64-bit Windows operating systems. There are no Linux or cross-platform alternatives mentioned, nor are there any Linux-specific instructions or examples. The documentation also references BitLocker (a Windows-native encryption technology) as the only supported encryption method, further reinforcing the Windows-centric approach.

Recommendations:

Provide or reference a cross-platform (Linux/macOS) version of the WAImportExport tool, or offer equivalent functionality via a platform-agnostic tool or script.
Include Linux-specific instructions and examples for preparing drives, copying data, and handling encryption/decryption.
If BitLocker is required, document supported methods for unlocking BitLocker-encrypted drives on Linux (e.g., using dislocker or similar tools), and provide step-by-step guidance.
Clearly state any limitations for non-Windows users and suggest workarounds or alternatives where possible.
Consider supporting open, cross-platform encryption standards in addition to BitLocker to improve accessibility for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a Windows bias primarily in the 'Hybrid Connections' section, where the only supported relay agent (Hybrid Connection Manager) is specified as requiring 'Windows Server 2012 or newer.' There are no Linux equivalents or instructions for Linux-based environments. Additionally, the 'Gateway-required virtual network integration' feature is stated as 'limited to App Service Windows plans,' with no Linux alternative or parity discussed. Throughout the document, there are no platform-specific command-line examples, but when platform limitations are mentioned, Windows is prioritized or exclusively supported.

Recommendations:

Provide explicit information about Linux support or alternatives for Hybrid Connections (e.g., clarify if a Linux agent exists or is planned, or suggest alternative connectivity options for Linux-based apps).
For features limited to Windows (such as gateway-required VNet integration), clearly state the lack of Linux support and, if possible, provide workarounds or alternative approaches for Linux users.
Where platform-specific tools or agents are required, include parity tables or cross-platform guidance to help Linux users achieve similar functionality.
Consider adding Linux-focused examples or notes throughout the documentation to ensure equal clarity for both Windows and Linux deployment scenarios.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools (such as Visual Studio and PowerShell) and patterns, while not providing equivalent emphasis or examples for Linux users. For example, Visual Studio integration is mentioned for Application Insights, but no mention is made of Linux-friendly tools or editors. The page states that Azure activity logs can be queried using PowerShell, REST API, CLI, or portal, but PowerShell is listed before CLI, which is more cross-platform. There are no explicit Linux-specific examples or notes, and no mention of Linux-native tools or workflows.

Recommendations:

When mentioning development tool integration (e.g., Application Insights with Visual Studio), also mention popular Linux-friendly editors (such as VS Code) and their integration.
When listing command-line options (PowerShell, CLI, REST API), list Azure CLI before PowerShell, or mention both equally, to reflect cross-platform parity.
Provide explicit Linux examples or notes where relevant, such as how to access logs or monitor services from a Linux environment.
Reference Linux-native troubleshooting or monitoring tools (such as tail, grep, journalctl) where appropriate, especially in sections discussing log streaming or diagnostics.
Include links or references to Linux-specific documentation or guides for App Service monitoring.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits several signs of Windows bias. File paths and environment variables are presented in Windows format (e.g., %HOME%, D:\home\site\wwwroot), and instructions for file exclusion reference Windows-style paths. The use of Kudu DebugConsole and FTP is described with Windows-centric paths. There is no mention of Linux shell commands or Linux-specific tools for managing files, and PowerShell is referenced as an automation option alongside Azure CLI, but no Linux shell scripting examples are provided. While the content does acknowledge Linux apps in some tables, practical examples and instructions are consistently Windows-first or Windows-only.

Recommendations:

Provide Linux-equivalent file paths (e.g., /home/site/wwwroot) alongside Windows paths in all examples and instructions.
Include Linux shell (bash) commands for file operations, such as creating and uploading the _backup.filter file, in addition to or instead of Windows-centric instructions.
Mention and demonstrate the use of Linux-native tools (e.g., SCP, SFTP, curl) for file uploads and management.
When referencing environment variables, include both Windows (%HOME%) and Linux ($HOME) syntax.
Offer automation examples using bash scripts, not just PowerShell, to ensure parity for Linux users.
Clarify when instructions or features are OS-specific, and ensure that Linux users are not left to infer the correct procedure.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias by referencing Windows file paths (e.g., D:\home), using Windows terminology and tools (such as Kudu/SCM), and omitting Linux-specific examples or equivalents. The documentation describes behaviors and settings primarily in the context of Windows-based App Service environments, with only brief mentions of Linux or containerized scenarios, and does not provide Linux command-line examples or clarify differences for Linux users.

Recommendations:

Provide parallel Linux examples and file paths (e.g., /home/site) alongside Windows paths.
Explicitly describe how local cache works (or does not work) on Linux-based App Service plans, including any differences in behavior, paths, or configuration.
Include Linux command-line examples (e.g., using Bash) for checking folder sizes or environment variables, not just references to Windows tools or extensions.
Clarify the availability and configuration of local cache or its alternatives (such as App Cache) for Linux and containerized environments, with links to relevant documentation.
Where features are not supported on Linux, provide clear guidance and alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. Windows platforms and tools are mentioned first in lists (e.g., 'Windows code' before 'Linux code'), and deployment via Visual Studio (a primarily Windows tool) is highlighted with no equivalent Linux IDE example. File/script type support lists Windows executables and scripts before Bash and other cross-platform options. There are no explicit Linux-focused deployment or development examples, and the 'Develop WebJobs using Visual Studio' link reinforces a Windows-centric workflow.

Recommendations:

Alternate the order of platform mentions (e.g., list Linux and Windows options interchangeably or alphabetically).
Include Linux-focused deployment and development examples, such as using VS Code, the Azure CLI, or direct Bash scripting.
Highlight cross-platform tools (e.g., VS Code, GitHub Actions, Azure CLI) equally with Visual Studio.
Provide explicit Linux-based workflows or tutorials, such as deploying from a Linux environment or using Bash scripts.
Add links or references to Linux-friendly documentation or guides alongside Windows/Visual Studio resources.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no equivalent examples or guidance for Linux or cross-platform shells (such as Bash or Azure CLI). The tooling and workflow described are Windows-centric, and Linux users are not provided with alternative commands or approaches.

Recommendations:

Provide equivalent Bash or Azure CLI examples alongside PowerShell scripts to ensure Linux users can follow the documentation.
Explicitly mention cross-platform compatibility where possible, and clarify if any steps are Windows-specific.
Include references to Linux tools and workflows (e.g., using Bash, sh, or Azure CLI) in addition to PowerShell.
Structure the documentation so that Windows and Linux instructions are given equal prominence, or provide tabs/switchers for different platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes SMB over QUIC in the context of Windows Server 2022 Datacenter: Azure Edition, with no mention of Linux support, Linux VM images, or cross-platform configuration. All examples and steps assume a Windows environment, and the only referenced documentation is for Windows Server. There are no Linux equivalents, tools, or instructions provided.

Recommendations:

Explicitly state whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not supported, clarify this early in the documentation.
If Linux support exists or is planned, provide parallel instructions for enabling and managing SMB over QUIC on Linux-based Azure VMs.
Include references to Linux SMB/QUIC documentation or community resources, if available.
When mentioning prerequisites or supported images, list both Windows and Linux options (if applicable), or explain the Windows-only limitation.
Consider adding a comparison table or section outlining feature parity and differences between Windows and Linux environments for SMB over QUIC and Automanage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively uses PowerShell for all examples, commands, and explanations, implicitly assuming a Windows environment. There are no Bash, CLI, or Linux-native examples or references. The focus on PowerShell and the absence of Linux alternatives or cross-platform guidance demonstrates a clear Windows bias.

Recommendations:

Provide equivalent Azure CLI (az) or Bash script examples alongside PowerShell scripts to support Linux and macOS users.
Mention that PowerShell Core is cross-platform, or clarify if the instructions are specific to Windows PowerShell.
Include references or links to Linux/macOS setup guides for Azure CLI or PowerShell Core.
Reorder or supplement content so that both Windows and Linux approaches are presented equally, rather than prioritizing Windows tools.
Add a section or note on how to perform the same tasks using the Azure Portal or REST API for maximum cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias primarily through the exclusive use of Windows-style file paths (e.g., c:\data\import) in configuration examples, references to Windows-specific .NET APIs (such as WinHttpHandler and ServicePointManager), and the absence of explicit Linux or cross-platform command-line or file path examples. There are no mentions of Linux-specific tools, shell commands, or file system conventions, and all examples assume a Windows environment by default.

Recommendations:

Provide Linux and macOS equivalents for all file path examples (e.g., use /home/user/data/import alongside c:\data\import).
When referencing .NET APIs that have platform-specific behavior (like WinHttpHandler or ServicePointManager), clarify their cross-platform compatibility or provide alternatives for Linux environments.
Include notes or examples for setting environment variables and configuration files using Linux/macOS shell syntax (e.g., export VAR=value, or editing ~/.bashrc).
Explicitly state that the SDK and its configuration are cross-platform, and provide guidance for running and debugging WebJobs on Linux/macOS.
Where relevant, mention any differences in behavior or limitations when running on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by providing installation instructions using Visual Studio's Package Manager Console (PowerShell-based) and referencing Visual Studio UI paths. While the .NET Core CLI is cross-platform, the Package Manager Console and Visual Studio instructions are Windows-centric, and there are no explicit Linux or non-Windows environment examples or guidance. The documentation assumes the use of Visual Studio, which is primarily a Windows tool, and omits parity for Linux development environments (e.g., VS Code, JetBrains Rider, or plain CLI usage on Linux/Mac).

Recommendations:

Add explicit instructions for Linux and macOS users, such as using the .NET CLI for all package installations and project management tasks.
Avoid referencing Visual Studio-specific tools (like the Package Manager Console) as primary or only options; if included, present cross-platform CLI instructions first.
Mention and provide examples for popular cross-platform editors (e.g., VS Code) and how to perform equivalent tasks outside Visual Studio.
Clarify that all .NET CLI commands work identically on Linux, macOS, and Windows, and provide terminal/shell instructions for non-Windows users.
Where UI navigation is described (e.g., Visual Studio menus), offer alternative steps for CLI or other IDEs.
Include a note or section on developing and running the sample on Linux/macOS, highlighting any differences or prerequisites.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by frequently referencing Windows-specific tools (such as PowerShell, IIS diagnostics, and SysInternals Procdump), providing instructions and links that are Windows-centric (e.g., .NET Profiler for Windows), and omitting equivalent Linux-based troubleshooting steps or examples. The Kudu Console section highlights PowerShell and DOS commands, but does not mention Bash or Linux shell usage. There is a lack of parity in examples and guidance for Linux-based App Service environments.

Recommendations:

Include Linux-specific troubleshooting steps and examples, such as using Bash in the Kudu Console, and mention Linux-compatible diagnostic tools.
Provide links and instructions for enabling diagnostics and profiling on Linux-based App Service plans (e.g., Application Insights Profiler for Linux, or alternatives).
When referencing PowerShell or Windows tools, also provide equivalent Bash/CLI commands and Linux-native tools where possible.
Clarify when a feature or tool is Windows-only, and offer Linux alternatives or workarounds.
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or clearly indicate which applies to which environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by providing more detailed instructions, features, and examples for Windows-based App Service apps. Several logging features (web server logging, detailed error messages, failed request tracing) are described only for Windows, with no Linux equivalents or alternatives mentioned. Windows-specific tools and log formats (e.g., W3C, Log Parser, Web.config) are referenced, while Linux-native patterns or tools are absent. Linux instructions are less detailed and sometimes limited to basic file system logging, with no mention of advanced diagnostics or parity with Windows features.

Recommendations:

Provide equivalent Linux examples and instructions for all logging features, or clearly state if a feature is unavailable on Linux.
Describe Linux-native logging and diagnostic tools (e.g., journalctl, syslog, or container log collection patterns) where applicable.
Include parity tables or feature comparison charts to clarify which logging features are available on Windows vs. Linux.
Avoid referencing only Windows tools (like Log Parser or Web.config) without suggesting Linux alternatives.
Expand Linux sections to match the detail and troubleshooting guidance given for Windows, including advanced diagnostics and error tracing where possible.
If certain features are Windows-only, suggest best-practice workarounds or third-party tools for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. It provides a Windows-specific DNS cache clearing command (ipconfig /flushdns) without mentioning the Linux/macOS equivalent. In the FAQ, PowerShell is referenced for moving resources, but no CLI or Linux-native alternative is given. There are no Linux-specific tools, commands, or troubleshooting steps, and Windows patterns are mentioned first or exclusively in relevant sections.

Recommendations:

When providing command-line instructions (e.g., clearing DNS cache), include Linux/macOS equivalents such as 'sudo systemd-resolve --flush-caches' or 'sudo killall -HUP mDNSResponder' for macOS.
When referencing PowerShell cmdlets (e.g., Move-AzResource), also provide the Azure CLI equivalent (e.g., 'az resource move ...') and note cross-platform compatibility.
Where troubleshooting steps involve tools or commands, ensure parity by mentioning both Windows and Linux/macOS approaches.
Consider adding a section or callouts for Linux/macOS users where platform-specific steps may differ.
Review for any other Windows-centric language or assumptions and revise to be more platform-neutral.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias, primarily through the exclusive use of PowerShell cmdlets for operational instructions (such as restarting the Application Gateway), and by referencing Azure PowerShell before Azure CLI when discussing how to change the subnet of an existing Application Gateway. There are no Linux shell or Azure CLI command examples provided, and no mention of Linux-specific tools or workflows, which may disadvantage users on non-Windows platforms.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operational tasks, such as stopping and starting the Application Gateway.
When referencing tools for management (e.g., 'use Azure PowerShell or the Azure CLI'), list Azure CLI first or equally, and provide direct links to both sets of documentation.
Include example commands or scripts for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) environments to ensure platform parity.
Where possible, avoid assuming the use of PowerShell as the default, and clarify that all operations can be performed from any supported OS using the Azure CLI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows and Visual Studio workflows, with all examples and instructions assuming the use of Visual Studio on Windows. There are no examples or guidance for Linux-based development environments, cross-platform tools, or command-line alternatives. Windows-specific tools (e.g., Server Explorer, File Explorer, IIS/Log Parser) are referenced exclusively, and there is no mention of Linux equivalents or how to perform these tasks outside of Visual Studio or on non-Windows platforms.

Recommendations:

Add equivalent instructions and examples for Linux and macOS users, including how to perform remote debugging, log streaming, and file access using cross-platform tools such as VS Code, Azure CLI, and Kudu.
Include command-line examples (e.g., using Azure CLI, PowerShell Core, or Bash) for enabling diagnostics, downloading logs, and managing App Service configurations.
Reference and provide instructions for cross-platform editors (such as VS Code) and tools, not just Visual Studio on Windows.
Mention and link to Linux-friendly log analysis tools (e.g., grep, awk, jq, or open-source log viewers) as alternatives to Windows tools like Log Parser.
Clearly indicate which features are only available in Visual Studio on Windows and suggest alternatives or workarounds for users on other platforms.
Reorder sections or provide parallel instructions so that Linux/macOS approaches are not always secondary or omitted.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary automation interface, mentioning Azure Resource Manager and PowerShell together, and omitting any explicit mention of Linux tools, Bash, or cross-platform scripting examples. There are no Linux-specific authentication workflows, nor are there examples or guidance for Linux users. The documentation assumes a Windows-centric approach to automation, both in terminology and in the tools referenced.

Recommendations:

Include examples of authenticating and automating tasks using Bash, Azure CLI, or Python scripts, not just PowerShell.
Explicitly mention that Azure Automation supports both Windows and Linux Hybrid Runbook Workers, and provide parity in examples.
Add sections or notes describing how Linux users can authenticate and interact with Azure Automation, including any differences in setup or permissions.
Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and avoid presenting Windows tools or patterns first or exclusively.
Provide links to Linux-specific or cross-platform documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides step-by-step instructions and screenshots for exporting certificates using Windows Certificate Manager, a Windows-only tool. There are no examples or guidance for performing equivalent tasks on Linux or macOS. The only command-line reference is to PowerShell/certmgr, and the 'Next steps' section links to a PowerShell-specific guide. Linux tools and workflows are not mentioned or demonstrated.

Recommendations:

Add parallel instructions for exporting certificates using common Linux tools such as openssl, including command-line examples for exporting public keys and root certificates in Base-64 encoded X.509 (.CER) format.
Include screenshots or terminal output from Linux environments to illustrate the process.
Mention Linux and macOS as supported platforms explicitly, and provide guidance for users on those systems.
Balance references to Windows tools by listing Linux and cross-platform alternatives (e.g., openssl, certutil).
Update the 'Next steps' section to include links to Linux and cross-platform guides, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell command examples for certificate management, omitting equivalent Azure CLI (cross-platform) or Bash examples. The troubleshooting steps and automation guidance focus on PowerShell, which is traditionally associated with Windows environments. There is no mention of Linux or cross-platform workflows, and the use of PowerShell is presented as the default or only option for scripting and automation.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell for all certificate management and troubleshooting tasks.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
Where PowerShell is referenced, clarify that it is available cross-platform, but also offer Bash/CLI alternatives to ensure Linux users are not excluded.
Review all automation and scripting guidance to ensure parity between Windows and Linux tooling, and avoid presenting Windows tools as the default.
Include a section or note highlighting cross-platform support and linking to relevant Azure CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server as the backend VM OS, provides only PowerShell commands for configuration (with no Bash or Linux CLI alternatives), and instructs users to edit the Windows hosts file using Windows-specific paths and tools. There are no examples or instructions for Linux users, either for backend VM creation, web server installation, or local name resolution.

Recommendations:

Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
Include Azure CLI/Bash examples alongside PowerShell for tasks like installing web servers or managing resources.
Add a section on editing the /etc/hosts file for Linux/macOS users, including appropriate commands (e.g., using sudo nano /etc/hosts).
Mention cross-platform tools and commands where possible, or clearly indicate when steps are Windows-specific.
Balance screenshots and code snippets to show both Windows and Linux environments where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All command-line examples for certificate creation and backend server setup use Windows PowerShell and Windows Server. There are no Linux or cross-platform alternatives provided for creating self-signed certificates, exporting PFX files, or setting up backend servers. The documentation assumes the user is running Windows locally and uses Windows-specific tools and patterns throughout.

Recommendations:

Provide equivalent Linux and macOS instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
Include examples for deploying Linux-based backend servers (such as Ubuntu VMs) and installing a web server (e.g., Apache or Nginx) for testing.
When referencing command-line tools, offer both Windows (PowerShell) and Linux/macOS (Bash/OpenSSL) alternatives side by side.
Clarify in the prerequisites that the tutorial is currently Windows-centric, or update it to be explicitly cross-platform.
Consider using Azure CLI examples, which are cross-platform, for steps such as VM creation and extension installation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows tools (WAImportExport.exe), Windows-style paths (e.g., C:\Users\bob\Pictures), and does not provide any Linux or cross-platform examples. All command-line examples use Windows syntax, and there is no mention of Linux equivalents or usage on non-Windows systems.

Recommendations:

Provide equivalent Linux command-line examples, using Linux-style paths (e.g., /home/bob/Pictures) and syntax.
Clarify whether the Azure Import/Export Tool is available for Linux, and if not, mention any alternatives or workarounds for Linux users.
If the tool is Windows-only, explicitly state this limitation early in the documentation.
Include guidance for accessing and manipulating log and path map files on Linux systems, if supported.
Ensure that any file path or environment variable references are shown in both Windows and Linux formats where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based instructions for listing VM extensions in Azure Government, referencing Windows-centric tools and workflows, and omitting equivalent Linux/CLI examples. Additionally, the 'Next steps' section lists Windows extension deployment before Linux, reinforcing the Windows-first pattern.

Recommendations:

Include equivalent Azure CLI or Bash examples for listing VM extensions, ensuring Linux users have clear guidance.
Explicitly mention that PowerShell is cross-platform, or clarify if the instructions are Windows-only.
Provide links or references to Linux/CLI documentation alongside PowerShell instructions.
Alternate the order of 'Next steps' to avoid always listing Windows before Linux, or present both options equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only Windows-based SQL Server VM creation instructions (with the default image being 'SQL Server 2022 Developer on Windows Server 2022'), and by instructing users to connect using SQL Server Management Studio, a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM or for connecting from Linux clients using cross-platform tools.

Recommendations:

Include instructions for creating a SQL Server VM on Linux (e.g., Ubuntu) as an alternative to the Windows-based VM.
Provide examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI clients available on Linux and macOS.
Mention both Windows and Linux options when describing VM image selection, and clarify that the procedure works for both OS types.
Add screenshots or command-line examples for Linux users where appropriate, such as using the Azure CLI or SSH.
Ensure that any references to client tools (like SQL Server Management Studio) are accompanied by alternatives that work on Linux and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. It refers to the 'File Explorer dialog' and uses terminology and UI patterns most familiar to Windows users, without mentioning Linux equivalents (such as file managers like Nautilus, Dolphin, or generic 'file picker'). The only API development tool mentioned is Postman, which is cross-platform, but no command-line (e.g., curl) or Linux-native alternatives are suggested. There are no explicit PowerShell or Windows command-line examples, but the documentation assumes familiarity with Windows-centric tools and patterns.

Recommendations:

When referencing file dialogs, use neutral language such as 'file picker dialog' or mention both Windows (File Explorer) and Linux (file manager, e.g., Nautilus, Dolphin) equivalents.
Provide examples or mention alternative API tools such as curl or httpie, which are commonly used on Linux.
Explicitly state that the instructions apply to all platforms and, where relevant, provide Linux-specific notes (e.g., how to unzip files or open HTML files in common Linux browsers).
Avoid assuming the user is on Windows; use cross-platform terminology and examples throughout.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for HTTP debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly web debugging tools (like tcpdump, Wireshark, or mitmproxy) mentioned. Instructions and screenshots are tailored to Windows environments, and Windows tools are introduced before any alternatives.

Recommendations:

Provide equivalent Azure CLI (az network application-gateway ...) and/or Bash examples for checking Application Gateway settings, alongside or before PowerShell.
Mention and give examples for cross-platform or Linux-friendly web debugging tools such as mitmproxy, Wireshark, or tcpdump, not just Fiddler.
Include installation and usage instructions for these tools on Linux/macOS as well as Windows.
Avoid Windows-specific instructions like 'Run as administrator' unless also providing the equivalent for other platforms.
Where screenshots are used, consider including examples from Linux desktops or web-based tools to ensure parity.
Explicitly state that the troubleshooting steps can be performed on any OS, and provide guidance for users on non-Windows systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides detailed instructions and code samples for enabling diagnostic logs using the Azure Portal and PowerShell, both of which are Windows-centric tools. There are no equivalent CLI or Bash examples for Linux/macOS users, and PowerShell is presented as the only scripting option. This creates a bias toward Windows environments and leaves out Linux-native workflows.

Recommendations:

Add Azure CLI (az) examples for enabling diagnostic logging, as the Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell script examples alongside PowerShell, or at least reference how Linux users can accomplish the same tasks.
Explicitly mention that PowerShell Core is cross-platform if retaining PowerShell examples, but still provide native Bash/Azure CLI alternatives.
Ensure that documentation sections do not assume a Windows environment by default; present cross-platform options equally or list Linux-friendly methods first where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windowscode_links

Summary:

The documentation demonstrates a mild Windows bias, primarily by referencing Windows-specific concepts and links (such as 'windowscode' tabs and file type documentation), and by presenting .NET (historically Windows-centric) as the first and most detailed example. There is also a subtle preference for Windows terminology and documentation structure, even though the code and packaging examples themselves are cross-platform and use Bash scripts for execution.

Recommendations:

Provide explicit Linux and Windows instructions or clarify when steps are cross-platform, especially in the .NET section.
Avoid linking only to 'windowscode' tabs for supported file types and CRON expressions; provide Linux-specific or neutral links where possible.
Ensure parity in depth and clarity across all language pivots, not just .NET.
Explicitly mention when a step is platform-agnostic or, if not, provide both Windows and Linux alternatives (e.g., for packaging, running, or scripting).
Consider adding a section or note about differences in WebJobs behavior or deployment between Windows and Linux App Service plans, if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows environments by only providing a PowerShell command (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting any Linux-based examples or equivalent CLI commands. There are no instructions or examples for performing these tasks using Azure CLI, Bash, or Linux-native tools.

Recommendations:

Provide equivalent Azure CLI (az group delete) and/or Bash commands for resource cleanup alongside the PowerShell example.
Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify that the backend VMs could run either Windows or Linux.
Offer guidance or examples for users deploying and validating the setup from Linux/macOS environments, not just Windows.
Ensure that all code snippets and instructions are cross-platform where possible, or explicitly provide alternatives for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references the Windows-based 'WAImportExport.exe' tool, provides only Windows-style command-line examples (with Windows file paths and drive letters), and does not mention or provide instructions for Linux or cross-platform usage. There is no discussion of Linux equivalents, compatibility, or alternative tooling, and all examples and terminology are Windows-centric.

Recommendations:

Explicitly state whether the Azure Import/Export Tool is available for Linux or cross-platform environments. If not, clarify this limitation early in the documentation.
If a Linux version or alternative exists (such as a .NET Core or Python-based tool), provide equivalent Linux command-line examples, using Linux-style paths and conventions.
If only Windows is supported, suggest workarounds for Linux users (e.g., using a Windows VM, Docker container, or Azure Cloud Shell).
Avoid using 'Windows Azure' in tool/service names unless it is the official name; prefer 'Azure' for neutrality.
Add a section addressing platform compatibility and any known issues or requirements for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows and PowerShell by providing only PowerShell-based command-line examples for configuring Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The instructions and code samples assume the use of PowerShell, which is most commonly associated with Windows environments, and the 'Next steps' section links exclusively to a PowerShell guide. This may hinder Linux or macOS users who prefer or require CLI/Bash-based workflows.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and managing Application Gateway.
Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or Bash, and provide links to relevant documentation.
In the 'Next steps' section, include links to guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
Where possible, provide Bash script snippets or instructions for common Linux workflows (e.g., using environment variables, jq for JSON parsing, etc.).
Ensure that references to tools and commands are cross-platform or, if not, that alternatives are clearly documented.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Azure PowerShell scripts for migration, without mentioning or providing examples for Azure CLI or other cross-platform tools. There are no Linux-specific instructions or examples, and the guidance assumes use of PowerShell, which is traditionally associated with Windows environments. This creates a bias towards Windows users and may hinder Linux or cross-platform users.

Recommendations:

Provide equivalent Azure CLI commands and scripts for all migration steps, ensuring Linux and macOS users have clear, supported options.
Explicitly mention that Azure PowerShell is cross-platform, if relevant, and provide installation instructions for Linux/macOS if PowerShell must be used.
Include examples or references for Bash scripting or automation, not just PowerShell.
Add a section comparing migration approaches/tools for both Windows and Linux environments.
Ensure all tooling recommendations are platform-agnostic or offer parity between Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for all command-line operations, referencing PowerShell modules and cmdlets exclusively, and omitting equivalent instructions for Linux environments (such as Azure CLI or Bash). Windows-centric tools and patterns are mentioned first and often exclusively, with no parity for Linux-native workflows.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
Include Bash script examples where appropriate, especially for automation scenarios.
Mention both PowerShell and CLI options in prerequisites and throughout the documentation, not just PowerShell.
Clarify that PowerShell can be used cross-platform, but also highlight native Linux workflows.
Add a section or callouts for Linux/macOS users, ensuring they can follow the same procedures without relying on Windows tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance primarily via PowerShell, and omitting equivalent Linux or cross-platform command-line examples. The 'Next steps' section directs users to a PowerShell-based guide, and there is no mention of Azure CLI, Bash, or Linux certificate management tools. The documentation assumes familiarity with Windows-centric certificate formats and management patterns, with no guidance for Linux users.

Recommendations:

Include Azure CLI and/or Bash examples alongside or before PowerShell instructions for configuring Application Gateway and TLS.
Reference cross-platform certificate management tools (e.g., OpenSSL) for creating and managing certificates, and provide sample commands for exporting to PFX format on Linux.
Link to or provide guidance for Linux/macOS users on how to generate, convert, and upload certificates, including how to handle certificate chains.
Mention that PFX files can be created and managed on non-Windows systems, and provide relevant documentation links.
In the 'Next steps' section, add links to guides for configuring end-to-end TLS using Azure CLI, ARM templates, and the Azure Portal, not just PowerShell.
Where Windows APIs or tools are referenced, provide equivalent cross-platform alternatives or clarify that the process is not Windows-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell-based runbooks and Windows-centric tools (such as the Az PowerShell module and cmdlets like Start-AzAutomationRunbook). All examples are in PowerShell, and there is no mention of Linux-native scripting (e.g., Bash, Python) or cross-platform approaches. The documentation assumes the use of Windows/PowerShell patterns and does not provide parity for Linux users or those preferring non-PowerShell automation.

Recommendations:

Add equivalent examples using Python and Bash runbooks, which are supported in Azure Automation.
Include references to Linux-based scripting environments and clarify which features are available for non-PowerShell runbooks.
Mention and provide examples for starting and managing runbooks using the Azure CLI (az automation runbook ...), which is cross-platform.
Reorganize sections to mention cross-platform options (Python, Bash, Azure CLI) alongside or before Windows/PowerShell-specific tools.
Clarify any limitations or differences in behavior for non-PowerShell runbooks (e.g., parameter passing, job output retrieval).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page lists both Windows and Linux as supported operating systems, but there is a clear Windows bias. Windows Server versions are listed first, and the only anti-malware solution mentioned is Microsoft Antimalware, which is explicitly stated as Windows-only. There are no Linux-specific examples, tools, or guidance, and no mention of Linux equivalents for anti-malware or other management tools. The documentation does not provide Linux-specific considerations or best practices, despite being tagged as part of a Linux collection.

Recommendations:

List Linux operating systems before or alongside Windows to avoid the impression of Windows primacy.
For each Windows-specific tool or feature (e.g., Microsoft Antimalware), mention Linux equivalents (such as ClamAV, ESET, or other supported anti-malware solutions for Linux) or explicitly state if there is no Linux support.
Provide Linux-specific configuration examples, troubleshooting steps, or best practices where relevant.
Include notes on any differences in feature support or behavior between Windows and Linux, especially for services like Change Tracking, Update Management, and Machine Configuration.
Ensure that documentation sections and examples are balanced between Windows and Linux, especially in articles marked as relevant to Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates mild Windows bias, primarily in the 'For testing purposes only' section, where PowerShell scripts are mentioned alongside Bash, and in the linked tools for certificate generation, which often default to Windows-first approaches. While Azure CLI and Node.js tools are cross-platform, the explicit mention of PowerShell and the lack of explicit Linux command-line examples (e.g., OpenSSL for all certificate operations, Bash-only scripts) suggest a slight preference for Windows tooling and workflows.

Recommendations:

Ensure all script/tool references are clearly marked as cross-platform, or provide separate instructions for Windows (PowerShell) and Linux/macOS (Bash).
When listing tools or scripts, alternate the order (e.g., mention Bash before PowerShell in some places) or group them as 'Bash/PowerShell' rather than listing PowerShell first.
Expand examples using OpenSSL or other standard Linux tools for certificate/key generation, especially in sections where only PowerShell or Windows-centric tools are mentioned.
Explicitly state the platform compatibility of each tool or script, and provide download/use instructions for both Windows and Linux users.
Where screenshots or UI instructions are given, ensure they are not Windows-specific or provide Linux/macOS equivalents if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows/PowerShell bias. All code examples, tool references, and explanations are exclusively based on Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux-based automation, Bash, or Python runbooks (except for a brief note about Python output language support). Retrieval of runbook output is only shown using Windows PowerShell tools, and preference variables are discussed only in the context of PowerShell. No Linux-native or cross-platform CLI (such as Azure CLI) equivalents are provided.

Recommendations:

Add equivalent examples using Azure CLI (az) commands for retrieving runbook output and managing jobs, which work cross-platform.
Include Bash or Python runbook examples where applicable, especially in sections discussing output and message streams.
When referencing tools or commands, mention cross-platform options (e.g., Azure CLI, REST API) alongside or before Windows PowerShell.
Clarify which features or behaviors are specific to PowerShell-based runbooks versus those available in Python or other supported runbook types.
Provide links to documentation for managing Azure Automation from Linux/macOS environments.
If certain features are only available in PowerShell runbooks, explicitly state this and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows and PowerShell usage. All migration instructions, code samples, and tooling references are exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform scripting. The prerequisites, script download, and execution steps assume a PowerShell environment, and there are no Linux- or macOS-specific instructions or examples. This creates a significant barrier for users on non-Windows platforms or those who prefer CLI/Bash scripting.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for each PowerShell example, including authentication, resource queries, and migration steps.
Include explicit instructions for running the migration from Linux/macOS environments, such as using Azure Cloud Shell (Bash) or installing PowerShell Core cross-platform.
Mention and demonstrate how to use the Azure CLI to retrieve resource IDs, manage certificates, and perform other prerequisite steps.
Clarify whether the migration script can be run in Azure Cloud Shell (Bash) or if it requires PowerShell, and provide alternatives if possible.
Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
Ensure that any references to downloading and running scripts include Linux/macOS-compatible instructions (e.g., using wget/curl, handling .nupkg files without Windows tools).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux and Windows binaries for AzAcSnap, but there is a noticeable emphasis on Windows-specific features (e.g., Microsoft SQL Server on Windows) and terminology. Some features are described as available only for Windows (e.g., SQL Server 2022 on Windows), and there are no explicit Linux-specific examples or parity notes for features. Windows is often mentioned first or exclusively in feature announcements, and there is a lack of Linux-focused troubleshooting or configuration examples.

Recommendations:

Ensure that for every Windows-specific feature or example, a Linux equivalent is provided or the lack thereof is explicitly documented.
When listing supported platforms or features, alternate the order (e.g., Linux first in some sections) or use neutral phrasing.
Add Linux-specific configuration, troubleshooting, and usage examples where appropriate.
Clearly indicate feature parity or gaps between Windows and Linux, and provide timelines or workarounds for missing Linux features.
Include Linux tools, logs, and environment variable usage in examples and troubleshooting guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a significant Windows and PowerShell bias. All migration scripts and automation examples are provided exclusively in PowerShell, with no mention of Bash, Python, or cross-platform scripting alternatives. The instructions for Hybrid Runbook Worker installation and management link first (and sometimes only) to Windows-specific tabs or documentation. There are no Linux-specific or cross-platform code samples, and the required modules and runtime environments are all Windows/PowerShell-centric. This creates an impression that Linux users are secondary or unsupported, despite the initial claim of Linux VM applicability.

Recommendations:

Provide equivalent Bash or Python scripts for asset migration, or at least reference cross-platform alternatives if available.
Include explicit Linux examples and instructions, especially for Hybrid Runbook Worker deployment and management.
Ensure that documentation tabs and links are balanced, offering both Windows and Linux options side-by-side.
Mention and support cross-platform modules or tools (such as Azure CLI) where possible, not just PowerShell/Az modules.
Clarify any limitations or differences for Linux users up front, and provide guidance for achieving parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows and PowerShell-based workflows for compiling DSC configurations in Azure Automation. All code examples use PowerShell, and there is no mention or example of using Linux-based tools or workflows. Windows-specific modules, cmdlets, and file paths are referenced throughout, and Linux alternatives or cross-platform approaches are not discussed. The documentation assumes a Windows environment and does not address Linux users' needs.

Recommendations:

Add examples using cross-platform PowerShell Core (pwsh) and clarify compatibility with Linux/macOS.
Explicitly state whether DSC compilation and management is supported on Linux, and if not, provide guidance or alternatives for Linux users.
If Linux support is deprecated (as hinted by the retirement announcement), clearly highlight this at the top and provide migration paths or alternatives.
Provide equivalent command-line or scripting examples for Linux environments where possible, or explain limitations.
Avoid using only Windows file paths (e.g., C:\...) in examples; include Linux-style paths or note platform differences.
Mention and link to any Linux-native tools or approaches for configuration management if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and workflows for configuring Azure RBAC and managing role assignments in Azure Automation. There are no examples or instructions using cross-platform tools such as Azure CLI, and no mention of Linux-native workflows or shell environments. The exclusive use of PowerShell and lack of Linux/CLI parity may hinder users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, including role assignment, listing, and removal.
Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide sample bash shell commands.
Where scripts are shown, offer both PowerShell and bash/CLI alternatives side by side.
Review references to 'PowerShell' in headings and text, ensuring that cross-platform options are equally visible and not presented as secondary.
Add a section or note clarifying that Azure Automation and RBAC are fully manageable from any OS using CLI or REST API, not just Windows/PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation refers to 'Azure PowerShell' before mentioning the Azure CLI or REST API (which are only mentioned in passing in the introduction). There are no Linux-specific instructions or examples, and no mention of running commands in Bash or on Linux/macOS platforms.

Recommendations:

Add Azure CLI examples (az commands) alongside PowerShell for all automation and deletion tasks.
Include Bash shell examples where appropriate, especially for cross-platform users.
When listing options (e.g., Azure portal, PowerShell, CLI, REST API), present Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
Explicitly state that all command-line examples work on Windows, Linux, and macOS where applicable, and clarify any platform-specific limitations.
Provide links or references to documentation for using Azure Automation with Linux environments, if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All code examples use Windows PowerShell DSC syntax and resources (such as WindowsFeature), and there are no Linux configuration examples. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. Linux is only mentioned in passing, with no practical guidance or parity in examples.

Recommendations:

Provide parallel Linux examples, such as a sample DSC configuration using the nx or nxFile resource for Linux nodes.
Include links to both Windows and Linux VM creation guides in the prerequisites.
Reference both Windows and Linux DSC documentation in the overview and next steps.
Clarify which features and steps apply to Linux, and note any differences or limitations.
If Linux support is deprecated, make this explicit at the start and provide migration or alternative guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias: it assumes the use of PowerShell syntax throughout, references Windows-centric tools and patterns (such as MOF documents and the PowerShell Gallery), and does not provide Linux-native alternatives or examples. Although the configuration example targets a LAMP stack (Linux), the entire workflow is described using PowerShell DSC constructs, and the documentation explicitly notes that Azure Automation DSC for Linux has been retired, further marginalizing Linux users. There are no Bash or Linux-native configuration examples, and next steps reference Chocolatey, a Windows package manager.

Recommendations:

Provide parity for Linux users by including examples using native Linux configuration management tools (such as Ansible, Chef, or native Azure Policy Guest Configuration for Linux).
Offer Bash or shell script equivalents for steps currently described only in PowerShell.
Clarify the current support status for Linux and direct users to up-to-date, supported alternatives for Linux VM configuration.
When referencing tools like Chocolatey, also mention Linux package managers (e.g., apt, yum) or cross-platform solutions.
Reorganize the documentation to avoid assuming PowerShell as the default, and explicitly state when steps are Windows-only.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows and PowerShell bias. PowerShell DSC is the only configuration language discussed, and examples or references are almost exclusively Windows-centric. Windows operating systems are listed first and in detail, while Linux support is referenced generically and with less detail. Windows-specific tools and patterns (e.g., WinRM, WMF, PowerShell cmdlets, Chocolatey) are mentioned without Linux equivalents or examples. There are no Linux-specific walkthroughs or examples, and Linux support is often described as an afterthought.

Recommendations:

Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
List Linux operating systems and their requirements with the same level of detail as Windows.
Include references to Linux-native configuration tools or patterns where appropriate (e.g., systemd, shell scripts, or integration with Linux package managers).
Offer parity in documentation structure: for every Windows/PowerShell example or tool mentioned, provide the Linux equivalent or clearly state limitations.
Highlight any differences or limitations in Linux support up front, and keep Linux-specific retirement or deprecation notices clearly separated from general documentation.
Add a Linux-focused 'Next steps' or quickstart guide, similar to the Windows/PowerShell guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by providing more detailed and prominent guidance for Windows users, especially around TLS configuration and data backup. Windows-specific tools (PowerShell cmdlets) are referenced repeatedly, often without Linux or cross-platform equivalents. Linux guidance is present but less detailed and sometimes appears after Windows instructions. Several examples and instructions are Windows-centric, with Linux alternatives either missing or less emphasized.

Recommendations:

Provide Linux command-line (bash, shell) examples alongside or before Windows/PowerShell examples for all relevant operations (e.g., exporting runbooks, managing DSC nodes).
Reference cross-platform tools (such as Azure CLI or REST API) where possible, rather than only PowerShell cmdlets.
Ensure Linux-specific instructions are as detailed and actionable as Windows instructions (e.g., for TLS configuration, provide distro-specific guidance and verification steps).
Balance the order of presentation: alternate between Windows and Linux, or group by platform, rather than always listing Windows first.
Where Windows registry or PowerShell is referenced, provide equivalent Linux file or command references (e.g., for confirming TLS settings).
Explicitly mention if a feature or operation is not available or differs on Linux, to avoid ambiguity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation claims support for both Windows and Linux VMs, but throughout the page, there is a clear Windows-first bias. Windows-specific features (like Registry and Software tracking) are highlighted in the introduction, and the policy breakdown lists 'Configure ChangeTracking Extension for Windows virtual machines' before the Linux equivalent. There are no Linux-specific examples, screenshots, or mentions of Linux-specific tracked items (e.g., Linux packages or configuration files), and all screenshots and UI references are generic or Windows-centric. No Linux command-line or configuration examples are provided.

Recommendations:

Include explicit Linux examples, such as tracking Linux package changes or configuration files.
Balance the order of presentation: alternate or group Windows and Linux instructions equally, or start with Linux in some sections.
Add screenshots or UI references that show Linux-specific tracking (e.g., tracking /etc files or installed packages).
Mention Linux-specific tracked items and clarify parity or differences in feature support.
If command-line or scripting examples are provided, ensure both PowerShell (Windows) and Bash (Linux) examples are included.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation displays a moderate Windows bias. While the main certificate generation workflow uses cross-platform OpenSSL commands, several sections and examples prioritize or exclusively reference Windows tools, paths, or procedures. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. Instructions for editing the hosts file and importing certificates into IIS link to Windows-specific resources, and file paths in PowerShell examples use Windows conventions. Linux-specific instructions or parity are often missing or appear after Windows references.

Recommendations:

Provide Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Include Linux-specific instructions for editing the hosts file (e.g., /etc/hosts) and importing certificates into popular Linux web servers.
When referencing file paths, use cross-platform conventions or show both Windows and Linux examples.
When linking to web server documentation, include links for both Windows (IIS) and Linux (Apache, NGINX) equally and in parallel.
Explicitly mention Linux procedures for adding a root certificate to the trusted store (e.g., update-ca-certificates on Debian/Ubuntu).
Balance the order of presentation so that Linux and Windows tools/examples are given equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The section for creating a new connection specifically references 'Windows PowerShell' and provides only PowerShell examples. There is no guidance or example for users working from Linux or macOS environments. The documentation also refers to Windows-centric patterns and tools (e.g., PowerShell cmdlets, DSC configurations) before mentioning Python, and does not provide parity for Linux/CLI workflows.

Recommendations:

Add Azure CLI examples for creating and managing connections, suitable for Linux/macOS users.
Include Bash script examples where appropriate, especially for automation scenarios.
Clarify that PowerShell examples can be run cross-platform (if true), or provide equivalent instructions for non-Windows environments.
Mention and link to any Linux-compatible tools or modules for Azure Automation.
Rephrase headings and instructions to be OS-neutral (e.g., 'Create a new connection with the command line' instead of 'with Windows PowerShell').
Ensure that all workflows (creation, management, retrieval of connections) have both PowerShell and CLI/Bash examples.
Explicitly state platform support and any limitations for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows and PowerShell-centric bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in the most detail, with numerous examples and troubleshooting sections focused on Windows paths, environment variables, and cmdlets. Many examples and limitations reference Windows-specific file paths (e.g., C:\modules), environment variables, and tools, with little or no equivalent Linux guidance. Python runbooks are discussed, but Linux-specific instructions are minimal and often secondary to Windows explanations. Graphical runbooks and workflows are also tightly coupled to Windows PowerShell, and Linux support is explicitly limited or absent.

Recommendations:

Provide Linux-specific examples and troubleshooting guidance alongside or before Windows examples, especially for file paths, environment variables, and known issues.
When referencing environment variables or file paths, include both Windows and Linux formats (e.g., C:\modules and /opt/automation/modules).
Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and offer Linux workarounds where possible.
For PowerShell runbooks, explicitly document differences in behavior or support between Windows and Linux Hybrid Runbook Workers.
Expand Python runbook sections to include more Linux-specific details, such as package management, file system paths, and common issues.
Where graphical runbooks or workflows are Windows-only, suggest alternative approaches for Linux users or clearly state the lack of support.
Balance the order of presentation so that Linux and cross-platform scenarios are not always secondary to Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows and PowerShell bias. Most examples, scripts, and workflows are presented using PowerShell and Windows-specific tooling (e.g., WMF 5, PowerShell DSC cmdlets), with Linux instructions often appearing later, being less detailed, or requiring Windows tools to manage Linux nodes. Some Linux-specific steps are present, but they are less comprehensive, and Linux users are frequently directed to use Windows/PowerShell environments for configuration generation and management.

Recommendations:

Provide Linux-first and cross-platform examples alongside Windows/PowerShell examples, especially in sections on generating and applying DSC metaconfigurations.
Include native Linux command-line examples (e.g., Bash, Python) for all major workflows, such as onboarding, configuration, and status checking.
Document how to generate and apply DSC metaconfigurations entirely from a Linux environment, without requiring access to Windows or PowerShell.
List Linux and Windows instructions in parallel, or clearly separate them, rather than always presenting Windows/PowerShell first.
Expand Linux troubleshooting and operational guidance to match the depth provided for Windows.
Where PowerShell is required for Linux, clarify if PowerShell Core on Linux is supported, and provide examples accordingly.
Avoid assuming the user has access to a Windows machine for managing Linux nodes; provide alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension names are Windows-specific, with no equivalent guidance or visuals for Linux VMs. Linux is only mentioned in passing, and there are no examples or instructions for Linux users.

Recommendations:

Provide parallel step-by-step instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
Explicitly mention and show the selection of the Linux Hybrid Worker extension in the Azure portal, including its name and any differences in the installation process.
Update the prerequisites section to include both Windows and Linux VM requirements.
Ensure that all references to extension names and configuration steps are clear for both Windows and Linux scenarios.
Consider alternating the order of Windows and Linux instructions or presenting them side-by-side to avoid a Windows-first impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples for both Azure CLI and Azure PowerShell, but PowerShell examples are given equal prominence to CLI, and in some sections, PowerShell is mentioned before or alongside CLI. PowerShell is a Windows-centric tool, and its inclusion without explicit mention of Linux alternatives or parity may suggest a bias towards Windows users. There are no explicit Linux-specific instructions, nor are there examples using Bash or other common Linux shells. The documentation also references Azure portal (web-based) and REST API, which are cross-platform, but the command-line focus is split between CLI (cross-platform) and PowerShell (primarily Windows).

Recommendations:

Clearly indicate that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though available on Linux).
Add explicit Bash shell examples for Linux users where scripting is involved, especially for variable assignment and command chaining.
In tabbed examples, list Azure CLI before PowerShell to reflect its cross-platform nature and reduce perceived Windows-first bias.
Where PowerShell is referenced, note that PowerShell Core is available on Linux, and provide installation links or guidance.
Consider including a section or note on using these tools in Linux environments, including any prerequisites or differences.
If possible, provide sample scripts or automation guidance using Bash for Linux users, especially in sections involving role assignments or identity management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific concepts (such as registry keys and Windows services) are described in greater detail and with more examples than their Linux equivalents. Windows tools, paths, and terminology (e.g., c:\ paths, registry, Windows services) are often mentioned first or exclusively, and alerting examples focus heavily on Windows scenarios. While Linux is supported and mentioned, Linux-specific examples (e.g., for daemons, package tracking, or file paths) are less detailed or absent in some sections. The registry tracking section is entirely Windows-centric, and alerting queries are predominantly Windows-focused, with only one Linux daemon example. Powershell is used as the default CLI context, even for Linux commands.

Recommendations:

Provide equivalent Linux-focused examples alongside Windows examples in all sections, especially for alerting queries and configuration tracking.
Expand the documentation on Linux-specific features, such as daemon tracking, package inventory, and typical Linux configuration files (e.g., /etc/hosts, /etc/passwd).
When listing features or examples, alternate the order or present both Windows and Linux scenarios together to avoid 'windows_first' bias.
Include Linux command-line examples using bash or shell where appropriate, rather than only using PowerShell or Windows-centric CLI.
Add a section on tracking Linux configuration files and directories, with concrete examples (e.g., monitoring changes in /etc/ssh/sshd_config or /var/log).
In registry/key tracking sections, clarify that this is Windows-only and provide a parallel discussion of Linux equivalents (e.g., tracking changes in /etc or systemd unit files).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows and PowerShell environments. Troubleshooting steps, examples, and tooling (such as xDscDiagnostics, PowerShell cmdlets, and references to Windows event logs and WMI) are almost exclusively Windows-centric. Linux is only mentioned in a single scenario, with no equivalent troubleshooting depth, examples, or tooling guidance. Windows tools and patterns are introduced first and often exclusively, with Linux support treated as an afterthought or omitted.

Recommendations:

Provide Linux-specific troubleshooting steps and examples for each scenario where applicable, including log locations, commands, and error investigation techniques relevant to Linux nodes.
Include Linux equivalents for all PowerShell cmdlets and tools, such as how to collect and analyze DSC logs on Linux, and how to manage certificates or extensions.
Balance the order of presentation by mentioning Linux approaches alongside Windows, rather than only after or not at all.
Reference Linux-native tools (e.g., journalctl, systemd, log files in /var/log) and shell commands where appropriate.
Clarify where features or tools are Windows-only, and provide alternative guidance for Linux users.
Expand the Linux troubleshooting section to cover common issues, error messages, and resolutions in parity with the Windows content.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for scripting examples (e.g., setting public network access flags), and by referencing Windows tools and patterns (such as PowerShell Desired State Configuration) without providing equivalent Linux/Unix command-line or scripting examples. While the text mentions Linux support in some features, practical examples and configuration steps are only shown for Windows/PowerShell environments, leaving Linux users without direct guidance.

Recommendations:

Provide equivalent Azure CLI or Bash examples alongside PowerShell scripts, especially for key configuration steps such as setting the publicNetworkAccess property.
When referencing configuration management (e.g., DSC), include notes or links about Linux alternatives (such as Chef, Puppet, or native Linux DSC support) and how they interact with Azure Automation.
Explicitly show Linux command-line examples for agent installation, configuration, and DNS setup, not just mention that Linux is supported.
Ensure that screenshots and UI walkthroughs do not assume a Windows-centric environment (e.g., referencing Windows file paths or tools only).
Add a dedicated section or callouts for Linux users, summarizing any differences or additional steps required for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in several ways. The Windows section is presented first and in greater detail, with step-by-step instructions that rely heavily on Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts). The Windows workflow is tightly coupled to the Visual Studio GUI and Windows file management patterns, with no mention of equivalent Linux or cross-platform approaches for those steps. There is no guidance for performing the Windows scenario from a non-Windows environment, and the Linux section is entirely separate, with no cross-references or parity in application scenario (the Windows example is ASP.NET with custom fonts, while the Linux example is a generic Django/Flask app). There are also missing Linux equivalents for certain steps (e.g., installing custom fonts in a Linux container, using PowerShell scripts for configuration).

Recommendations:

Provide Linux or cross-platform equivalents for all steps shown in the Windows workflow, especially for application scenarios that require OS-level customization (e.g., installing fonts in a Linux container, not just Windows).
Avoid presenting Windows as the default or primary platform by giving equal prominence to both Windows and Linux pivots, or by starting with a neutral introduction.
Replace or supplement Windows-specific tooling (Visual Studio, Windows Explorer, PowerShell scripts) with cross-platform alternatives (VS Code, command-line instructions, Bash scripts) where possible.
For steps that require file installation or OS customization, show how to achieve the same result in a Linux container (e.g., using apt-get to install fonts, Bash scripts for automation).
Ensure that advanced scenarios (such as custom OS configuration, font installation, or other integrations) are demonstrated for both Windows and Linux, not just Windows.
Where PowerShell scripts are used, provide Bash equivalents for Linux users.
Explicitly mention any limitations or differences between Windows and Linux container support in App Service, and provide guidance for users migrating from either platform.
Consider using a consistent sample application or scenario across both pivots to better illustrate parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for all steps, including Azure resource management, Key Vault operations, and the runbook itself. There are no references to Bash, Azure CLI, or Linux-based scripting alternatives. All tooling and module references (e.g., Az PowerShell module) are Windows-centric, and the workflow assumes the use of PowerShell as the default and only supported scripting environment.

Recommendations:

Provide equivalent Azure CLI (az) and/or Bash script examples for all resource creation, permission assignment, and secret management steps.
Include a sample runbook written in Python (supported in Azure Automation) or Bash, demonstrating how to retrieve secrets and send emails using SendGrid.
Mention and link to Linux/macOS-compatible tools and installation instructions, not just PowerShell modules.
Rephrase instructions to be platform-neutral where possible, or explicitly note that the steps apply to both Windows and Linux environments.
Add a section or callout for users who prefer or require non-Windows environments, outlining their options for achieving the same automation goals.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows and PowerShell environments. All command-line examples use PowerShell cmdlets, and there are no equivalent instructions or examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The documentation assumes the use of PowerShell consoles and Windows-specific tools, and there is no mention of how to perform these tasks on Linux or macOS. The only supported runbook type for source control integration is PowerShell 5.1, which is Windows-only, further reinforcing the Windows-centric approach.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
Explicitly state the platform limitations (e.g., that PowerShell 5.1 is Windows-only) and provide guidance for users on other platforms.
Include Bash or shell script examples for common tasks, such as assigning roles or configuring source control.
Mention and document any Linux/macOS-compatible alternatives for tasks currently shown only with PowerShell.
Clarify whether source control integration is possible with Python or other cross-platform runbook types, and if not, explain the roadmap or alternatives.
Add troubleshooting and encoding guidance relevant to Linux/macOS editors and environments, not just those focused on Windows/PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation presents deployment instructions with PowerShell first, followed by Azure CLI. While Azure CLI is cross-platform, the explicit mention of PowerShell and the ordering may suggest a Windows-first approach. There are no explicit Linux/macOS-specific instructions or examples, and the verification and cleanup steps rely on the Azure portal, which is platform-agnostic but does not offer command-line parity for Linux users. The prerequisites mention Visual Studio Code and extensions, which are cross-platform, but do not highlight any Linux-specific tools or workflows.

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 commands work on Linux, macOS, and Windows.
Provide bash/zsh shell variable examples for Linux/macOS users (e.g., export templateFile=...).
Include instructions for verifying and cleaning up resources using Azure CLI commands, not just the Azure portal.
Add a note or section highlighting Linux/macOS compatibility and any platform-specific considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All troubleshooting steps, code examples, and references are provided exclusively for PowerShell, with no mention of Linux/Unix equivalents or cross-platform approaches. Windows-specific DLL errors and cmdlets are discussed without Linux context, and there are no Bash, CLI, or Python examples for Linux users.

Recommendations:

Provide equivalent troubleshooting steps and examples using Azure CLI (az) and Bash scripts for Linux users.
Mention cross-platform modules and tools where possible, and clarify which steps are Windows-specific.
Include notes or sections on how to perform common tasks (such as module import, authentication, and error resolution) in Linux environments.
Reference Linux-specific issues or error messages that may arise in Azure Automation, and how to resolve them.
Balance the order of presentation so that Linux and cross-platform solutions are given equal prominence to Windows/PowerShell solutions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on PowerShell modules and workflows, with nearly all examples, instructions, and internal tooling centered on Windows PowerShell and Windows-specific features. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no Linux shell or cross-platform scripting examples. Linux support is mentioned only to note limitations or lack of availability, and there are no Linux-native module management workflows or parity in examples.

Recommendations:

Provide equivalent Linux/bash examples for module management, such as using Azure CLI or bash scripts to import, update, or delete modules.
Clearly indicate which features are Windows-only and provide alternative workflows or guidance for Linux Hybrid Runbook Workers.
Include documentation and examples for managing Python modules and runbooks on Linux, not just a link to another page.
Highlight cross-platform capabilities and limitations in a dedicated section, making it clear what is supported on Linux vs. Windows.
When listing internal cmdlets or features, suggest Linux-compatible alternatives or workarounds where possible.
Balance the order of presentation so that Linux and cross-platform options are not always secondary or omitted.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows and PowerShell usage, with all command-line examples and tooling instructions centered around PowerShell cmdlets and Windows-specific patterns. Linux or cross-platform CLI alternatives are not mentioned, and there are no examples using Bash, Azure CLI, or other Linux-native tools. The Python examples are present but limited to the Azure Automation Python SDK, not general Linux workflows. The documentation assumes a Windows/PowerShell environment for automation tasks.

Recommendations:

Add equivalent examples using Azure CLI (az) commands for credential management, which are cross-platform and work natively on Linux.
Include Bash or shell script examples for retrieving and using credentials in runbooks, especially for Linux Hybrid Runbook Workers.
Mention and document how Linux users can interact with Azure Automation credentials, including any SDKs or REST API usage.
Avoid referring to 'Windows PowerShell' exclusively; use 'PowerShell' and clarify cross-platform compatibility where possible.
List Linux-compatible tools and workflows alongside PowerShell cmdlets, and avoid presenting Windows tools first or exclusively.
Clarify which features or modules are available on Linux-based Automation workers and provide parity guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides three main methods for creating an IoT Central application: Azure portal (GUI), Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform, the PowerShell section is Windows-centric and is given equal prominence to the CLI, despite PowerShell being less commonly used on Linux. There are no explicit Linux shell (bash) examples, and the documentation does not mention Linux-specific considerations or tools. The ordering of examples (portal, CLI, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method and the lack of Linux shell examples indicate a Windows bias.

Recommendations:

Add explicit bash/shell examples for Linux users, especially for common tasks like creating a resource group and an IoT Central application.
Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific installation guidance if needed.
Consider moving the PowerShell section after CLI, or labeling it as 'for Windows users' to clarify its intended audience.
Include troubleshooting notes or links relevant to Linux environments (e.g., permissions, package dependencies).
Where screenshots or UI references are given, note any differences for Linux users if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows/PowerShell bias. All code examples and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks that use PowerShell cmdlets. Windows-specific tools and patterns (such as PowerShell cmdlets, .NET types, and C# SDK examples) are used exclusively, with no equivalent Bash, Linux shell, or cross-platform CLI examples. The Python section is minimal and lacks parity in detail or examples. There are no references to Linux-native tools, and PowerShell is always presented first and in the most detail.

Recommendations:

Add equivalent examples for starting and managing runbooks using Azure CLI (az), which is cross-platform and widely used on Linux.
Provide Bash or shell script examples for interacting with Azure Automation via REST API or Azure CLI.
Expand the Python section to include detailed parameter handling, example scripts, and parity with PowerShell examples.
Mention and demonstrate how to use Linux/macOS environments for authoring and running runbooks, including any differences or considerations.
Where PowerShell-specific types or patterns are discussed, note their Linux/Python/CLI equivalents or limitations.
Ensure that references to tools and workflows are not Windows-first; present Azure CLI or REST API approaches before or alongside PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows and PowerShell, providing only Windows-centric examples (such as installing IIS), referencing only Windows VMs in prerequisites, and using only PowerShell cmdlets throughout. There are no Linux-specific examples, commands, or guidance, and Linux support is only briefly mentioned in passing. The documentation assumes the use of Windows tools and patterns, with no parity for Linux users.

Recommendations:

Add Linux-specific examples, such as configuring a Linux VM with a DSC configuration (e.g., ensuring nginx or Apache is installed).
Include Bash/CLI commands or scripts for onboarding and managing Linux nodes, not just PowerShell.
Update prerequisites to mention Linux VMs and provide links to creating Linux VMs in Azure.
Clarify the current support status for Linux in Azure Automation State Configuration, especially given the referenced retirement announcement.
Provide guidance or references for managing Linux nodes, including any differences in onboarding, configuration, or compliance checking.
Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias, particularly in the prerequisites and local testing sections. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and instructions for setting environment variables list Windows Command Prompt and PowerShell before Linux/macOS equivalents. The workflow assumes Visual Studio usage and references Windows-specific tools and patterns, with Linux parity only addressed as an afterthought.

Recommendations:

Add explicit instructions and examples for developing and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
Present environment variable setting commands for Linux/macOS before or alongside Windows commands, rather than after.
Include guidance for using .NET CLI and editors available on all platforms, not just Visual Studio.
Clarify that the quickstart is applicable to all platforms and provide parity in screenshots and workflow steps for Linux/macOS users.
Mention and link to documentation for developing Azure Functions on Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific tools, commands, and configuration steps are often mentioned before their Linux equivalents, or Linux is only referenced as an afterthought. Several CLI examples and deployment instructions are presented with Windows as the default or primary context, and PowerShell is included as a recommended tool for resource creation. In some sections, Linux-specific instructions are present but less emphasized or appear after Windows instructions. There are also areas where only Windows or Visual Studio workflows are detailed, with less parity for Linux or cross-platform alternatives.

Recommendations:

Ensure all CLI and deployment examples are provided for both Windows and Linux equally, using cross-platform tools (e.g., Azure CLI) as the default.
When listing tools or methods (e.g., Visual Studio, PowerShell, Azure CLI), avoid listing Windows-specific options first; instead, present cross-platform options first or in parallel.
Where PowerShell is mentioned, always include Bash or shell equivalents for Linux users.
In sections discussing configuration or deployment, provide explicit Linux examples and highlight any differences or required steps for Linux environments.
Where Visual Studio is referenced, ensure Visual Studio Code (cross-platform) instructions are equally detailed and prominent.
Review all code snippets and command-line instructions to ensure they are not Windows-centric (e.g., avoid backslashes in paths, use environment-agnostic syntax).
Add a summary table or section at the start that clearly indicates which instructions apply to Windows, Linux, or both, and link to the relevant sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally aims for cross-platform coverage, but there are several areas where Windows is prioritized or receives more detailed attention. Windows-specific tools and commands (such as PowerShell and 'py') are often mentioned before their Linux equivalents, and in some cases, Linux/Bash examples are less detailed or missing. There is also a tendency to reference Windows development environments and patterns (e.g., 'pip freeze' from Windows, Visual Studio Code with Windows settings) before or more prominently than Linux alternatives.

Recommendations:

Ensure that all command-line examples are provided for both Windows (PowerShell/CMD) and Linux (Bash), and present them in parallel or with equal prominence.
When referencing tools like 'py' (Windows Python launcher), also provide the equivalent Linux command ('python3') and clarify platform differences.
Avoid listing Windows commands or tools first by default; alternate the order or present both at the same time.
Expand on Linux-specific troubleshooting steps and examples, especially for common deployment and environment issues.
Where platform-specific behaviors are discussed (e.g., 'pip freeze' on Windows vs. Linux), provide explicit guidance for Linux users.
In sections referencing Visual Studio Code or other tools, clarify any platform-specific setup steps or differences for Linux users.
Audit for any missing Linux/Bash examples, especially in troubleshooting or mitigation steps, and add them to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, such as creating and connecting to Windows VMs, referencing RDP, and omitting Linux-based alternatives. There are no Linux VM setup or usage instructions, and the sample walkthrough assumes a Windows workflow throughout.

Recommendations:

Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity on Linux.
Include steps for copying and running the sample application on a Linux VM (e.g., using SSH and .NET Core on Linux).
Mention and link to Linux-specific documentation for connecting to Azure VMs (e.g., SSH instead of RDP).
Ensure code samples and instructions are platform-agnostic or provide both Windows and Linux variants where applicable.
Clarify that the sample applications can be run on both Windows and Linux, and provide any prerequisites or differences for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows command prompt and PowerShell instructions before macOS and Linux equivalents. The use of MSBuild and .csproj scripting is more common in Windows-centric workflows. Visual Studio Code is mentioned as cross-platform, but the primary application example is an ASP.NET Core app, which is historically Windows-centric, though now cross-platform. No Linux-specific tools or patterns are highlighted, and the structure subtly prioritizes Windows users.

Recommendations:

Present Linux/macOS and Windows instructions in parallel or randomize their order to avoid always listing Windows first.
Include examples using Linux-native build tools or scripting (e.g., bash scripts, Makefiles) alongside MSBuild.
Highlight cross-platform compatibility explicitly, and provide more context for Linux users (e.g., file path conventions, shell differences).
Where possible, use neutral language and tools (e.g., .NET CLI, Azure CLI) that work identically across platforms.
Add troubleshooting tips or notes for Linux-specific issues that may arise in CI/CD pipelines.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides deployment instructions and examples exclusively using PowerShell, a Windows-centric tool, without offering equivalent examples for Linux or cross-platform environments (such as Azure CLI or Bash). The only command-line deployment example is PowerShell, and there is no mention of Linux or macOS workflows. The documentation implicitly assumes a Windows environment by default.

Recommendations:

Add Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell examples for resource group creation and template deployment.
Explicitly mention that the instructions apply to all platforms, and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) users.
Reorder or parallelize examples so that Windows and Linux instructions are presented together, rather than Windows/PowerShell first or exclusively.
Where possible, use platform-neutral language and tools in the main flow, relegating platform-specific instructions to separate sections or tabs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for creating Azure resources, but consistently lists PowerShell as an alternative to CLI, which is a Windows-centric tool. There are no explicit Linux shell or Bash-specific examples, and keyboard shortcuts (e.g., Ctrl+C) are presented in a Windows-centric way. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux or macOS users beyond the CLI.

Recommendations:

Provide explicit Bash or shell command examples where appropriate, especially for common tasks like navigation or process termination.
List Azure CLI (cross-platform) examples first, and clarify that PowerShell is optional, not required.
Include notes or sections for Linux/macOS users, such as alternative keyboard shortcuts (e.g., Ctrl+C is universal, but confirmation prompts may differ).
Mention that all commands work on Linux/macOS unless otherwise stated, and highlight any OS-specific differences.
If referencing screenshots or terminal output, ensure they are not Windows-specific, or provide Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. PowerShell is given its own dedicated section, and instructions for command-line usage reference Windows PowerShell and opening a Windows PowerShell command window. There is no mention of Linux-specific shells or tools, and no explicit Linux/Bash examples are provided. The Azure CLI section mentions Windows PowerShell as an example of a command console, but does not mention Bash or other Linux shells. This may make Linux users feel less supported or unsure if the instructions are applicable to their environment.

Recommendations:

In the Azure CLI section, mention both Windows PowerShell and Bash (or other Linux shells) as valid environments for running Azure CLI commands.
Add explicit instructions or notes for Linux/macOS users, such as 'Open a terminal (e.g., Bash, zsh) on Linux/macOS' alongside Windows PowerShell.
Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide equivalent Bash/Azure CLI examples where possible.
Avoid language that assumes a Windows environment (e.g., 'Open a Windows PowerShell command window') unless the instructions are truly Windows-specific.
Consider adding a 'Linux/macOS' tab or section for parity with the PowerShell and Portal tabs, especially for command-line operations.
Ensure screenshots and UI references are not Windows-specific unless necessary, and clarify when steps are identical across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page exhibits a subtle Windows bias. Command-line examples are consistently shown using the Windows (DOS) command prompt format (e.g., code blocks labeled as 'dos'), and no explicit Linux/bash shell examples are provided for redis-benchmark, despite the tool being cross-platform. The documentation refers to 'client VMs' generically, but the example commands and code formatting implicitly prioritize Windows users. While memtier-benchmark examples use bash syntax, redis-benchmark examples do not, and there is no mention of Linux-specific setup or usage patterns. There are also no references to Linux-native tools or package managers (e.g., apt, yum) for installing Redis, nor are there any PowerShell-specific commands, but the overall example and formatting order suggest a Windows-first approach.

Recommendations:

Provide both Windows (cmd/PowerShell) and Linux (bash/sh) command examples for redis-benchmark, using appropriate code block labels.
Explicitly mention installation steps for redis-benchmark on both Windows and Linux, including references to package managers (e.g., apt-get, yum, brew).
When referring to 'client VMs', clarify that both Windows and Linux VMs are supported and provide any OS-specific considerations.
Balance the order of examples so that Linux/bash examples are given equal prominence to Windows/cmd examples.
If referencing tools like stunnel, note installation and usage differences between Windows and Linux.
Consider adding a section or callout for common troubleshooting steps or environment setup for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes deploying an Azure App Services app using Visual Studio 2019, a Windows-centric IDE, with no mention of Linux, macOS, or cross-platform tools. All steps and screenshots are based on Windows/Visual Studio workflows, and there are no examples or instructions for deploying from Linux environments or using command-line tools like Azure CLI or GitHub Actions.

Recommendations:

Add parallel instructions for deploying using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include examples for deploying from Linux or macOS environments, such as using VS Code, Azure CLI, or Git-based deployment.
Mention and provide steps for alternative deployment methods (e.g., GitHub Actions, Azure DevOps, FTP, or ZIP deploy) that are not tied to Visual Studio.
Clearly indicate which steps are Windows-specific and provide equivalent steps for other operating systems.
Add a section summarizing cross-platform deployment options and linking to relevant documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it mentions both Azure PowerShell and Azure CLI for configuring data persistence, the PowerShell instructions and references are presented before the CLI ones, and the CLI section is less detailed. There are no explicit Linux-specific examples or guidance, and the PowerShell environment is highlighted (including in prerequisites and Cloud Shell references) without equivalent emphasis on Linux-native tools or scripting. No Linux shell (bash) or OS-specific instructions/examples are provided outside of Azure CLI, and no mention is made of Linux-specific considerations or troubleshooting.

Recommendations:

Present Azure CLI (cross-platform) instructions before or alongside PowerShell instructions to avoid Windows-first ordering.
Add explicit bash/Linux shell script examples for common persistence management tasks, especially for automation scenarios.
Include notes or troubleshooting tips relevant to Linux environments (e.g., file permissions, CLI installation on Linux, integration with Linux-based automation tools).
Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for all platforms.
Where PowerShell is mentioned, also mention bash or other Linux-native scripting environments as alternatives.
Ensure screenshots and UI walkthroughs do not assume a Windows environment (e.g., avoid PowerShell-only Cloud Shell tabs).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets and management instructions, without providing equivalent Azure CLI (cross-platform) or Bash examples. All automation and scripting guidance is centered on PowerShell, which is traditionally associated with Windows environments. There is no mention of Linux-native tools or cross-platform command-line alternatives, and PowerShell is presented as the primary or sole automation method.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
When referencing management tools, mention both PowerShell and Azure CLI, and present them in parallel or alternate the order to avoid 'windows_first' bias.
Include Bash scripting examples where relevant, especially for automation scenarios.
Explicitly state that PowerShell Core is cross-platform if recommending it, and clarify if the instructions work on Linux/macOS as well as Windows.
Add links to Azure CLI documentation for managing Azure Cache for Redis, and ensure parity of coverage between PowerShell and CLI.
Consider including screenshots or terminal output from Linux environments, not just Windows/PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation tool for scaling, with explicit PowerShell examples and references. Azure CLI is also covered, but PowerShell instructions and links are consistently given before Azure CLI, and there are no explicit Linux/bash shell examples or references to Linux-specific tooling or patterns. There is no mention of Linux environments, nor are there any bash or shell script equivalents, which may make the documentation less approachable for Linux users.

Recommendations:

Provide bash/shell script equivalents for all PowerShell examples, especially for Azure CLI commands, to demonstrate usage in Linux/macOS environments.
When presenting automation options, alternate the order of PowerShell and Azure CLI, or present Azure CLI first to avoid implicit prioritization of Windows tools.
Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in bash or other shells.
Include screenshots or terminal snippets from Linux environments where appropriate, not just from the Azure portal.
Add a section or note clarifying that all features and instructions are applicable to both Windows and Linux users, and provide links to Linux-specific setup guides for Azure CLI and PowerShell if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by providing a connectivity verification example using the Windows-only 'tcping.exe' tool, without mentioning Linux alternatives. The only explicit command-line example is for Windows, and there is no parity example or tool recommendation for Linux users. Additionally, the documentation refers to PowerShell as a creation method before mentioning Azure CLI, which may subtly prioritize Windows-native tooling.

Recommendations:

Provide Linux-equivalent examples for connectivity verification, such as using 'nc' (netcat), 'nmap', or 'tcping' for Linux.
When listing creation methods, mention cross-platform tools (Azure CLI, ARM templates) before or alongside PowerShell to avoid implying a Windows-first workflow.
Explicitly state that the instructions and tools are applicable to both Windows and Linux, or provide separate sections/examples for each platform where relevant.
For any tool recommendations (like 'tcping'), include links or installation instructions for both Windows and Linux versions, or suggest platform-agnostic alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (AzCopy, PowerShell cmdlets) for key migration steps without mentioning Linux equivalents or alternatives. PowerShell is presented as the primary scripting interface for import/export operations, and no Linux command-line or cross-platform examples are provided. This may hinder users on Linux or macOS from following the migration steps easily.

Recommendations:

For every mention of PowerShell cmdlets (e.g., Import-AzRedisCache, Export-AzRedisCache), provide equivalent Azure CLI commands or REST API examples, which are cross-platform.
When referencing AzCopy, clarify that it is available for Linux and macOS as well, and provide example commands for those platforms.
Include Linux shell (bash) examples for file operations and cache management tasks, not just Windows/PowerShell.
Explicitly mention that all steps can be performed from Linux/macOS and provide links or references to relevant documentation.
Where possible, avoid presenting Windows tools or patterns first; instead, present cross-platform solutions or provide both Windows and Linux/macOS options side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by mentioning Windows-specific features (such as the Windows certificate store and TPMs being standard on Windows devices) without providing equivalent Linux examples or guidance. Windows tools and patterns are referenced, but Linux alternatives are not discussed, and there are no Linux-specific instructions or examples for certificate or TPM management.

Recommendations:

When referencing the Windows certificate store, also mention common Linux certificate storage locations (e.g., /etc/ssl/certs, or using OpenSSL).
When discussing TPM support, note that TPMs are also supported on Linux and provide links or examples for Linux TPM tools (such as tpm2-tools or trousers).
Include examples or references for certificate installation and management on Linux-based devices, not just Windows.
Where software tools are mentioned for certificate installation, provide cross-platform or Linux-specific tool suggestions (e.g., OpenSSL, tpm2-tools, or shell scripts).
Explicitly state that the guidance applies to both Windows and Linux devices, and call out any OS-specific differences or considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only explicit example for configuring certain settings (such as the 'databases' parameter), mentioning PowerShell and CLI together but only linking to PowerShell examples, and omitting Linux-specific or cross-platform command-line examples. There is no mention of Linux shell commands or parity in scripting, and the documentation does not provide equivalent Bash/Azure CLI walkthroughs where PowerShell is referenced.

Recommendations:

Provide Azure CLI (az) command examples alongside or before PowerShell examples for all configuration tasks, especially for settings like 'databases' during cache creation.
Include explicit Bash/Linux shell command examples where scripting or automation is discussed.
Ensure that links to management client documentation include both PowerShell and Azure CLI (and, where relevant, REST API) guides.
When referencing command-line management, avoid listing PowerShell first by default; alternate or list CLI first to balance perceived platform preference.
Add a section or callout for Linux/macOS users, clarifying that all features are available cross-platform and showing parity in tooling.
Audit all screenshots and UI instructions to ensure they do not assume a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Azure Portal (GUI) and Azure PowerShell instructions before Azure CLI, and by providing only PowerShell scripting examples for automation before CLI equivalents. There are no explicit Linux shell or cross-platform scripting examples (e.g., Bash), and the workflow assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Provide Azure CLI and Bash scripting examples alongside or before PowerShell examples to ensure parity for Linux and cross-platform users.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide guidance for running them in Bash or other common Linux shells.
Where automation is discussed, include both PowerShell and Bash/CLI scripts, and clarify any OS-specific prerequisites or differences.
Consider including screenshots or walkthroughs for Azure CLI in Cloud Shell (which is cross-platform) in addition to Azure Portal.
Review terminology and instructions to ensure they are not implicitly Windows-centric (e.g., avoid assuming use of PowerShell or Windows file paths).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias, particularly in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey, ARMClient, PowerShell commands) are provided for interacting with Azure resources. There are no equivalent instructions or examples for Linux or cross-platform environments. Additionally, the troubleshooting section mentions 'Test-NetConnection' (a PowerShell cmdlet) alongside 'nslookup', but does not provide Linux-native alternatives or examples, and Windows tools are mentioned first.

Recommendations:

Provide equivalent Linux and cross-platform instructions for installing and using ARMClient (e.g., via npm or .NET global tool), and show how to authenticate and run the same API calls from Linux/macOS.
Include Linux-native commands (such as curl, wget, or Azure CLI) for querying Azure REST APIs instead of or in addition to PowerShell/ARMClient.
In troubleshooting, add Linux equivalents for network testing, such as 'dig', 'host', or 'curl', and mention them alongside or before Windows-specific tools.
Avoid referencing Windows package managers (like Chocolatey) as the only installation method; provide installation steps for Linux (apt, yum, snap, etc.) and macOS (brew) where applicable.
When listing tools or commands, present cross-platform or Linux-native options first or at least equally, to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only Windows-specific instructions for setting environment variables (Windows Command Prompt and PowerShell), referencing Visual Studio exclusively as the development environment, and omitting Linux/macOS equivalents for key steps such as environment variable setup and project creation. There are no Bash or cross-platform CLI instructions, and the workflow assumes a Windows-centric toolchain.

Recommendations:

Add instructions for setting environment variables on Linux/macOS using Bash (e.g., export ConnectionString=...).
Include cross-platform .NET CLI commands (e.g., dotnet new console) for project creation, in addition to Visual Studio steps.
Mention and provide examples for using editors and IDEs available on Linux/macOS (e.g., VS Code, JetBrains Rider).
Ensure all code and configuration steps are clearly marked as cross-platform where applicable, and explicitly state any Windows-only requirements.
Reorder or parallelize instructions so that Windows and Linux/macOS steps are presented with equal prominence.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in its troubleshooting guidance. While it mentions the cross-platform redis-cli tool, it provides a connectivity test example using PSPING in Azure PowerShell (a Windows-specific tool) without offering a Linux equivalent. The order of presentation also places the Windows tool example before any Linux alternatives, and no Linux-native command (such as nc or telnet) is suggested for connectivity testing.

Recommendations:

Provide Linux-native command examples (e.g., using nc or telnet) alongside or before Windows-specific tools like PSPING.
Clearly indicate which tools/commands are platform-specific and offer parity in troubleshooting steps for both Windows and Linux users.
Consider reordering examples so that cross-platform or Linux tools are not always presented after Windows tools.
Include a table or section summarizing equivalent commands for Windows, Linux, and macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references PowerShell explicitly as a method to trigger the Redis version upgrade, and does not provide Linux-specific command-line examples or mention Linux tools. The ordering of upgrade methods (REST API, Azure CLI, PowerShell) puts PowerShell before any Linux-specific shell or scripting environment. There are no examples or instructions tailored for Linux users.

Recommendations:

Include explicit Linux shell (bash) examples for triggering the upgrade, alongside PowerShell.
Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
Avoid listing PowerShell before Linux equivalents unless there is a technical reason; consider rotating or randomizing order, or grouping by platform.
Add notes or links to Linux-specific documentation or troubleshooting where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring active geo-replication, but it consistently lists PowerShell after CLI and does not provide any Linux- or macOS-specific instructions or examples. There are no references to Linux-native tools, Bash scripts, or cross-platform shell usage. The focus on PowerShell, which is traditionally associated with Windows, and the absence of explicit Linux/Bash examples or notes about cross-platform usage, indicate a mild Windows bias.

Recommendations:

Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for Bash, PS> for PowerShell) to clarify cross-platform compatibility.
Add Bash-specific examples or notes where appropriate, especially for scripting or automation scenarios.
Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/Unix shell commands if possible.
Include a section or note about running these commands on Linux/macOS, including any prerequisites or differences (e.g., installation of Azure CLI or PowerShell Core).
Ensure screenshots and UI instructions do not assume a Windows environment unless unavoidable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, with no mention of Bash, Linux shell, or cross-platform scripting examples. There are no explicit Linux examples or references to Linux-native tools, and the documentation does not clarify that Azure CLI is cross-platform or provide Linux-specific guidance.

Recommendations:

Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Provide example commands for both Azure CLI (in Bash/shell) and PowerShell, making it clear which is suitable for Linux users.
Add a section or note for Linux users, including installation instructions or links for Azure CLI on Linux.
If possible, include references to automation or scripting approaches common on Linux (e.g., Bash scripts, cron jobs) alongside PowerShell.
Reorder the CLI tools table to list Azure CLI first, emphasizing its cross-platform nature.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line instructions and automation scripts are provided exclusively in PowerShell, with no mention or example of Bash, Azure CLI, or Linux-compatible alternatives. The prerequisites specifically require Azure PowerShell, and the service principal creation process is described only for PowerShell users. There is no guidance for users on Linux or macOS, nor are cross-platform tools like Azure CLI referenced. The workflow assumes a Windows environment (e.g., use of PowerShell, Set-ExecutionPolicy), and Windows-specific patterns are presented first and exclusively.

Recommendations:

Provide equivalent instructions and scripts using Azure CLI (az) in Bash, which is cross-platform and widely used on Linux and macOS.
Include notes or sections for Linux/macOS users, specifying any differences in setup or execution.
When referencing command-line tools, mention both Azure PowerShell and Azure CLI, and provide links to both installation guides.
Avoid Windows-specific commands like Set-ExecutionPolicy unless absolutely necessary, or provide alternatives for non-Windows platforms.
Add a table or section comparing PowerShell and Bash/Azure CLI approaches for key tasks (e.g., service principal creation).
Explicitly state that the instructions are for Windows/PowerShell and direct users to Linux/macOS guidance if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias. Windows-specific tools and patterns (such as Azure PowerShell and references to Windows Terminal) are mentioned alongside or before Linux equivalents. The instructions for Windows users focus on using WSL to run Linux tools, rather than providing native Windows redis-cli options. Additionally, Azure PowerShell is highlighted as a method to retrieve cache keys, which is a Windows-centric tool, and is listed before the Azure portal in some places.

Recommendations:

Provide native redis-cli installation instructions for Windows (e.g., using precompiled binaries or Chocolatey), not just via WSL.
Ensure that Linux and macOS instructions are as detailed and prominent as Windows instructions.
List cross-platform methods (such as Azure CLI and Azure portal) before platform-specific tools like Azure PowerShell.
When referencing tools like Windows Terminal, also mention equivalent terminal options for Linux and macOS.
Balance the order of examples and tool mentions so that Windows is not always listed first or given more prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias in the environment variable setup section, where Windows Command Prompt and PowerShell commands are listed before the Linux/macOS equivalent. The use of 'setx' (a Windows-specific tool) and explicit mention of PowerShell further reinforce this. Additionally, the build/run instructions use 'cmd' syntax highlighting, which may suggest a Windows-centric approach, even though the commands themselves are cross-platform.

Recommendations:

Present Linux/macOS commands before or alongside Windows commands, rather than after.
Use neutral or platform-agnostic syntax highlighting (e.g., 'bash' or no language) for cross-platform commands like Maven and curl.
Explicitly mention that the build/run commands work identically on Linux/macOS and Windows, and provide any necessary platform-specific notes.
Consider grouping environment variable instructions by platform, or using tabs or collapsible sections for each OS to improve clarity and parity.
Avoid using Windows-specific tools (like 'setx') as the primary example; instead, provide platform-appropriate commands for each OS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits a moderate Windows bias, primarily through the exclusive mention of PowerShell cmdlets (Export/Import-AzRedisCache) and the lack of equivalent CLI or Linux-native instructions. AzCopy is referenced without specifying cross-platform usage, and PowerShell is suggested as a primary automation tool. No Linux shell, Azure CLI, or cross-platform scripting examples are provided, and Windows-centric tools are mentioned before any alternatives.

Recommendations:

Provide Azure CLI equivalents for all PowerShell cmdlets (e.g., az redis export, az redis import) and include them alongside or before PowerShell examples.
Explicitly mention that AzCopy is cross-platform and provide example commands for Linux/macOS shells.
Include bash or shell script examples for exporting/importing RDB files, especially for users on Linux.
Where automation is discussed, reference both PowerShell and bash scripting, or use language-agnostic pseudocode.
Add a section or callouts for Linux/macOS users, ensuring parity in tooling and instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. While it is generally cross-platform, it references Windows-specific tools and patterns (such as performance counters and XML configuration for RedisSessionStateProvider) without providing equivalent Linux guidance or examples. The only explicit Linux mention is a brief pointer to another article for TCP settings, with no in-place Linux monitoring or troubleshooting examples. Windows monitoring methods (like performance counters) are mentioned without Linux alternatives, and the order of presentation often assumes Windows as the default environment.

Recommendations:

Provide Linux equivalents for all monitoring and troubleshooting steps, such as using top, vmstat, free, or sar for CPU and memory monitoring instead of only referencing Windows performance counters.
Include Linux configuration examples for Redis client settings, not just XML-based (typically Windows/.NET) examples.
When referencing tools or metrics (e.g., performance counters), mention both Windows and Linux approaches side by side.
Expand the 'TCP settings for Linux based client applications' section to include concrete troubleshooting steps and examples directly in this document, rather than just linking out.
Ensure that troubleshooting steps and examples are presented in a platform-neutral order, or explicitly provide both Windows and Linux options in each relevant section.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation includes a prominent PowerShell-specific note and provides PowerShell code samples alongside other languages. The only shell/CLI-specific mention is for PowerShell, with no equivalent mention of Bash or Linux-native scripting. The note about sub-orchestrations support in PowerShell references the PowerShell SDK and migration guide, but there is no similar guidance or context for Linux or Bash users. PowerShell is a Windows-centric tool, and its exclusive mention and support note indicate a Windows bias.

Recommendations:

Provide equivalent notes or guidance for Linux/Bash users if there are any platform-specific considerations for sub-orchestrations.
If PowerShell is mentioned as a supported shell, clarify support for Bash or other shells, or explicitly state if they are unsupported.
Consider including Bash or cross-platform shell examples or notes where PowerShell is referenced.
Ensure that CLI or scripting guidance is not exclusively tied to Windows tools, and mention cross-platform alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is exclusively focused on mounting SMB volumes for Windows VMs, providing only Windows client instructions and screenshots. There are no Linux examples or references to Linux tools for mounting SMB volumes, and the title and content are Windows-centric.

Recommendations:

Add a section on mounting SMB volumes from Linux clients, including example commands (e.g., using mount.cifs or smbclient).
Include Linux-specific screenshots or terminal output where appropriate.
Update the title and description to clarify if the guide is Windows-only, or broaden the scope to include Linux.
Ensure parity in detail and clarity between Windows and Linux instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by relying exclusively on PowerShell scripts for configuration and deployment tasks, and referencing Windows-centric tools like Visual Studio Code. While PowerShell 7 is cross-platform, there are no examples or guidance for using native Linux/Unix shell scripting or tools. The documentation does not provide equivalent bash or shell script examples, nor does it mention how to adapt the process for users who prefer or require non-PowerShell environments.

Recommendations:

Provide equivalent bash or shell script examples for all PowerShell scripts, especially for generating and applying configuration files.
Explicitly mention and demonstrate how to run the process on Linux/macOS, including any required dependencies or environment setup.
Reference cross-platform editors and tools more broadly (e.g., mention nano, vim, or other editors alongside Visual Studio Code).
Clarify that while PowerShell 7 is cross-platform, users may use bash or other shells, and provide guidance or links for adapting the scripts.
Where possible, offer Azure CLI or REST API alternatives for steps currently handled by PowerShell scripts.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides a detailed PowerShell command and mount example for Windows clients accessing NFS volumes, but does not provide equivalent Linux command-line examples for mounting NFS volumes or configuring client settings. This creates a bias toward Windows users and leaves Linux administrators without direct guidance for common NFS tasks.

Recommendations:

Add explicit Linux command-line examples (e.g., using 'mount' command) for mounting NFS volumes, including recommended mount options.
Provide Linux-specific guidance for optimizing NFS client performance (e.g., sysctl settings, mount options for performance, troubleshooting tips).
When discussing client configuration (such as case sensitivity or performance tuning), include both Windows and Linux procedures side by side.
Ensure that any PowerShell or Windows-specific instructions are matched with equivalent Linux shell commands where applicable.
Review the documentation for other places where only Windows tools or patterns are mentioned, and add Linux equivalents to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page generally avoids explicit Windows bias in its main instructions, focusing on Visual Studio Code and the Azure Functions extension, which are cross-platform. However, there is a subtle Windows bias in the troubleshooting section, where a solution specifically references Windows and WSL Bash without mentioning equivalent Linux or macOS scenarios. There are no explicit Linux/macOS command-line examples or troubleshooting steps, and the only shell-specific advice is Windows-centric. No PowerShell commands or Windows-only tools are shown, but the troubleshooting advice assumes a Windows environment.

Recommendations:

In the troubleshooting section, add equivalent advice for Linux and macOS users, such as ensuring the default terminal shell is compatible (e.g., Bash, Zsh, etc.), and clarify that the advice about WSL Bash is only relevant for Windows users using WSL.
Wherever troubleshooting or environment setup is discussed, explicitly mention that the instructions apply to all supported operating systems, and provide OS-specific notes where necessary.
If there are any platform-specific behaviors or requirements (such as permissions, path formats, or shell differences), include them for Linux and macOS as well as Windows.
Consider adding a short section or note confirming cross-platform compatibility and linking to platform-specific setup guides if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows development environments, focusing exclusively on Visual Studio and Visual Studio Code workflows. All instructions, screenshots, and tool references assume the use of Windows tools and UI patterns (e.g., Visual Studio, Azurite extension, menu navigation). There is no mention of Linux or macOS-specific instructions, terminal commands, or alternative editors. The use of Azurite and Azure Functions Core Tools is described only in the context of Visual Studio/VS Code, with no CLI or cross-platform guidance. This results in a lack of parity for Linux users.

Recommendations:

Add a dedicated section or pivot for Linux/macOS users, outlining how to create, run, and debug Durable Functions apps using the .NET CLI and Azure Functions Core Tools from the terminal.
Provide explicit instructions for installing prerequisites (e.g., .NET SDK, Azure Functions Core Tools, Azurite) on Linux and macOS, including package manager commands (apt, yum, brew, etc.).
Include CLI-based project creation and management steps as alternatives to Visual Studio/VS Code UI workflows.
Show examples of running and debugging Durable Functions apps from the terminal, including how to use breakpoints with VS Code on Linux/macOS.
Mention any platform-specific considerations, such as file paths, permissions, or differences in emulator usage.
Ensure screenshots and instructions are not exclusively Windows-centric, or provide equivalent visuals for Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates some Windows bias, particularly in the Java example where the ffmpeg path uses a Windows-style executable (ffmpeg.exe) and the guidance for setting the BASE_PATH is tailored to Azure's Linux file structure but does not mention Windows equivalents. Additionally, PowerShell is mentioned as an upload option, but Linux-native tools (like rsync, scp, or standard shell commands) are not referenced. The Python examples are more Linux-oriented, but there is a lack of parity in providing explicit Linux/Unix examples or guidance for Java users, and the documentation does not provide equivalent Windows instructions for file mounting or path handling.

Recommendations:

For Java examples, provide both Windows and Linux path examples for ffmpeg (e.g., ffmpeg.exe for Windows, ffmpeg for Linux) and clarify how to set BASE_PATH on both platforms.
When referencing upload options for Azure Files, mention Linux-native tools (e.g., azcopy, scp, rsync) alongside PowerShell and Azure CLI.
Explicitly state any platform-specific requirements or differences, such as file permissions (chmod) or path separators, for both Windows and Linux.
Where possible, include both Windows and Linux code/configuration snippets, or clearly indicate which platform each snippet targets.
Ensure that all steps (such as mounting file shares or setting environment variables) have instructions for both Windows and Linux development environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows some Windows bias, particularly in the Python section where Windows-specific instructions (such as activating a virtual environment) are presented before Linux equivalents. There are also explicit 'Windows' and 'Linux' tabs, with Windows shown first. The presence of a dedicated PowerShell pivot (even though it is empty in this sample) and references to Docker Desktop (which is branded and Windows-centric, though available on Linux) further reinforce a Windows-first orientation. However, Linux instructions are present and correct, and bash commands are used throughout for cross-platform compatibility.

Recommendations:

Present Linux and Windows instructions side-by-side or in a neutral order (e.g., Linux first, or alphabetical).
Avoid always listing Windows instructions first in tabbed code blocks; consider making Linux the default or randomizing the order.
Where possible, use generic terms like 'Docker' instead of 'Docker Desktop' unless the desktop version is specifically required.
Ensure PowerShell pivots or examples are matched with Bash or shell equivalents for parity.
Explicitly state that all commands work on both Windows and Linux unless there are genuine platform-specific differences.
Consider adding a table or section at the top summarizing OS-specific steps for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several ways: Windows is the default for deployment and hosting (with Linux as an afterthought), Windows-specific tools and patterns (PowerShell, Cmd) are given equal or greater prominence than Linux/Bash, and the default project configuration targets Windows. Linux alternatives are mentioned but often as side notes, and there is little to no discussion of Linux-specific considerations or troubleshooting.

Recommendations:

Present Linux and Windows options with equal prominence, e.g., list Bash/Linux examples before or alongside Windows/PowerShell/Cmd.
In the project configuration (pom.xml), do not default to Windows for 'runtime.os'; instead, explain both options and let the user choose.
Provide Linux-specific troubleshooting tips and highlight any differences in behavior or requirements (such as file permissions, environment variables, or supported Java versions).
Ensure that all command-line examples are available for Bash (Linux/macOS), PowerShell, and Cmd, and clarify which platforms each applies to.
Where Windows-specific tools or terminology are used (e.g., Ctrl+C, pressing 'y' to confirm), also mention the Linux/macOS equivalents.
Add a section or callout for Linux users, especially where the workflow or experience may differ (e.g., Java 21 support is Linux-only).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and provides step-by-step instructions and screenshots for its use. There are no examples or guidance for connecting from Linux or using cross-platform tools. The documentation implicitly assumes a Windows environment, omitting mention of alternatives available on Linux or macOS.

Recommendations:

Include instructions for connecting to Azure Government SQL endpoints using cross-platform tools such as Azure Data Studio, sqlcmd, or third-party clients available on Linux and macOS.
Add a section or note acknowledging that SSMS is Windows-only, and provide links or steps for Linux/macOS users.
Present connection string examples that can be used with command-line tools or programming languages on any platform.
Where possible, offer parity in screenshots and UI walkthroughs for cross-platform tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing images, referencing connecting via PowerShell, and listing Windows VM creation steps before Linux. There are no CLI or Bash examples for Linux users, and Linux VM creation is mentioned last in the next steps.

Recommendations:

Provide equivalent Azure CLI and/or Bash examples for listing VM images in Azure Government.
Include instructions for connecting to Azure Government using the Azure CLI, not just PowerShell.
Balance the order of 'Next steps' by listing Linux and Windows VM creation guides together or alternating their order.
Explicitly mention that the PowerShell example is one of multiple options, and link to Linux/CLI documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a moderate Windows bias, primarily through the exclusive mention of Windows-centric tools (such as Azurite emulator and Visual Studio Code commands) and a lack of explicit Linux/macOS instructions or terminal commands. While the language pivots cover multiple programming languages, there are no explicit examples or notes for Linux or macOS users regarding command-line differences, emulator usage, or environment-specific setup. The instructions for running and debugging functions assume a Visual Studio Code GUI workflow, which is more common on Windows, and do not provide CLI alternatives or mention cross-platform differences.

Recommendations:

Add explicit instructions or notes for Linux/macOS users, especially for installing and running Azurite, and clarify any differences in command-line usage or environment setup.
Provide CLI-based alternatives for steps currently described via Visual Studio Code GUI actions (e.g., creating functions, starting the emulator, running/debugging the app), and show equivalent Bash/zsh commands alongside PowerShell/Windows instructions.
Mention any OS-specific prerequisites or troubleshooting tips, such as permissions, path differences, or package manager commands for installing dependencies.
Ensure that all code snippets and setup steps are verified to work on Linux/macOS, and highlight any platform-specific considerations.
Where possible, use neutral, cross-platform language and tools, or clearly indicate when a step is Windows-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in several areas. In the 'Static IP restrictions' section, access restriction examples and configuration details are provided specifically for 'App Service on Windows', including references to the web.config file and IIS dynamic IP security, with no equivalent Linux guidance. There are no Linux-specific examples or mentions of how to achieve similar configurations on App Service for Linux, nor are cross-platform differences highlighted. Windows tools and patterns (e.g., web.config, IIS) are mentioned exclusively, and Linux is omitted from these discussions.

Recommendations:

Provide equivalent examples and instructions for App Service on Linux wherever Windows-specific guidance is given (e.g., how to configure IP restrictions on Linux).
When referencing Windows-specific tools (such as web.config or IIS features), explicitly state their applicability and offer Linux alternatives (such as using .htaccess for Apache, nginx config, or App Service access restrictions via the Azure portal/CLI).
Ensure that cross-platform differences are clearly documented, and avoid presenting Windows as the default or only supported platform.
Add Linux-specific security configuration examples and clarify any limitations or differences in feature support between Windows and Linux App Service plans.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but it lists Azure CLI first (which is cross-platform) and then Azure PowerShell (which is Windows-centric). However, there are no explicit Linux shell (bash) examples for common tasks such as directory creation or environment variable export, and the PowerShell examples use Windows-style variable assignment. There is also no mention of Linux-specific tools or workflows, and no explicit guidance for Linux/macOS users in the setup or verification steps.

Recommendations:

Add explicit bash/Linux shell examples for all steps involving command-line operations, such as directory creation, variable assignment, and running Terraform commands.
Clarify in the prerequisites or relevant sections that Azure CLI commands are cross-platform and provide bash syntax for variable assignment.
If PowerShell is included, also include equivalent bash commands for parity, especially for environment variable usage and output parsing.
Where file paths or command syntax may differ between Windows and Linux/macOS, provide notes or tabs for both environments.
Consider adding a 'Linux/macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' in the verification section to ensure all users are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration and status checking, with Azure CLI (which is cross-platform and more common on Linux) only mentioned in passing and without explicit command examples. There are no Linux-specific or CLI-first instructions, and the only code blocks are PowerShell. This may disadvantage Linux users or those who prefer CLI tools.

Recommendations:

Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, in code blocks.
When referencing command-line operations, avoid assuming PowerShell as the default; present CLI and PowerShell options equally.
Include notes or sections for Linux/macOS users, clarifying that all operations can be performed via Azure CLI on any platform.
Consider alternating the order of examples (CLI first in some sections, PowerShell in others) to avoid 'Windows first' bias.
Where screenshots or UI steps are shown, clarify that the Azure Portal is platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows Active Directory as the only supported KDC, referencing Windows tools (such as Event Viewer, MMC, and setspn) for management and troubleshooting, and providing detailed workflows and terminology rooted in Windows environments. Powershell and Windows-specific management consoles are mentioned for SPN management, while Linux/UNIX equivalents are not. There are no Linux command-line examples for managing Kerberos or SPNs, and Linux-specific workflows are only briefly mentioned, often as exceptions or notes, rather than as first-class guidance.

Recommendations:

Explicitly mention and, where possible, provide parity for Linux/UNIX tools and workflows (e.g., kadmin, ktutil, klist, and relevant Linux commands for SPN/keytab management).
Include Linux/UNIX command-line examples for common Kerberos tasks, such as creating and managing keytabs, configuring krb5.conf, and troubleshooting Kerberos authentication.
Where Windows tools (e.g., setspn, MMC, Event Viewer) are referenced, also reference Linux/UNIX equivalents or alternatives.
Clarify any Azure NetApp Files limitations regarding non-Windows KDCs, and if only Windows AD is supported, explain the rationale and potential roadmap for broader KDC support.
Balance the order of presentation so that Linux/NFS and Windows/SMB are treated with equal depth and priority, rather than consistently leading with Windows.
Add troubleshooting sections and best practices relevant to Linux environments, including log file locations, common error messages, and diagnostic commands.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows and PowerShell, providing only Windows PowerShell examples and using Windows file paths (e.g., c:\runbooks). There are no examples or guidance for Linux or cross-platform PowerShell Core usage, nor is there mention of Linux-compatible editors or workflows. The use of 'Windows PowerShell' and exclusive reference to Windows tools and conventions demonstrates a clear Windows bias.

Recommendations:

Provide examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility with Linux and macOS.
Include Linux/macOS file path examples (e.g., /home/user/runbooks) alongside Windows paths.
Mention and demonstrate the use of editors available on Linux/macOS (e.g., VS Code, nano, vim) for editing runbooks.
Clarify that Az PowerShell module cmdlets can be used from any OS, not just Windows.
Add a section or notes on how to perform the same tasks from Linux/macOS terminals, including installation instructions for PowerShell Core and Az modules.
Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when something is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific instructions, tools, and examples (such as PowerShell commands, Windows base images, and Kudu/FTP access patterns) are often presented first or in more detail. Some advanced configuration sections (memory, CPU, health ping) are only described for Windows containers, with no Linux equivalents. While Linux content is present and there are Linux-specific pivots, parity in depth and clarity is lacking in several areas.

Recommendations:

For every Windows-specific section (e.g., customizing memory, CPU, health ping), provide equivalent Linux container instructions or explicitly state if the feature is not supported for Linux.
When showing both Bash and PowerShell commands, present Bash (Linux) first or side-by-side, not always after PowerShell.
Ensure that advanced diagnostic and logging instructions (e.g., Kudu, FTP, log access) are equally detailed for Linux containers, not just Windows.
In sections about persistent storage, clarify differences and provide equal detail for both platforms, including Linux-specific caveats and best practices.
Where Windows parent images are listed, provide a similar list or guidance for recommended Linux base images.
Review all examples and ensure Linux tools and patterns (e.g., SSH, Linux file paths, Docker Compose) are as prominent as Windows ones.
Explicitly call out any features that are Windows-only, and provide links or alternatives for Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally maintains cross-platform parity, but there are subtle biases towards Windows. Windows-specific instructions and file extensions (e.g., handler.exe) are mentioned before Linux equivalents in several places. Windows environment variable setting syntax is shown after Linux/macOS, but the distinction is made explicit. There are references to Windows-specific tools (e.g., .exe files, Windows command syntax), and the documentation sometimes refers to Windows patterns first (e.g., 'handler.exe' before 'handler'). However, Linux and macOS instructions are present and correct, and the main workflow is cross-platform.

Recommendations:

When referencing executable names, mention the Linux version ('handler') before the Windows version ('handler.exe'), or present both together (e.g., 'handler (handler.exe on Windows)').
In configuration file examples, use cross-platform language, such as 'handler' for Linux/macOS and 'handler.exe' for Windows, or provide both options explicitly.
Where environment variable setting is required, present Linux/macOS and Windows commands side by side, or use tabs for clarity.
Avoid using Windows-specific terminology or tools as the default; instead, use neutral or Linux-first language where possible.
Ensure all screenshots and code snippets are available for both Linux and Windows environments, or use generic screenshots that do not show OS-specific details.
Consider adding a summary table or section at the start that clearly states the parity and any OS-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the primary IDE for .NET Framework, and many screenshots and step-by-step instructions focus on Windows tools and UI. PowerShell is given a dedicated section, but Linux-specific PowerShell examples are commented out and not visible to users. In the PowerShell section, users are explicitly told to use Azure CLI for Linux, but no Linux PowerShell deployment steps are shown. File path examples (e.g., 'cd bin\Release\net8.0\publish') use Windows-style backslashes, and compressing/deploying steps are shown only for Windows. While cross-platform tools (Azure CLI, VS Code) are included, Windows patterns and tools are often mentioned first or exclusively, and Linux parity is not always achieved.

Recommendations:

For every PowerShell deployment example, provide an equivalent Bash/Linux shell example, especially for steps like zipping and deploying files.
Uncomment and fully document the Linux PowerShell deployment steps, or remove PowerShell as a recommended tool for Linux if not supported.
When showing file paths or commands, provide both Windows and Linux syntax (e.g., use both '\' and '/').
Ensure that all screenshots and UI instructions that are Windows-specific are clearly labeled, and provide parallel instructions for macOS/Linux where possible.
In all sections, avoid language that implies Windows is the default or preferred platform; present cross-platform options equally and in parallel.
Expand the Azure CLI and VS Code sections to include more Linux/macOS-specific tips and troubleshooting.
Where possible, add explicit Linux/macOS instructions for tasks like compressing files (e.g., using 'zip' command) and deploying to App Service.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows and Visual Studio users, with all instructions and UI references tailored to the Windows version of Visual Studio. There are no CLI or cross-platform instructions for Linux or macOS users, and all examples assume the use of Visual Studio's GUI and PowerShell/NuGet Package Manager Console, which are primarily Windows-centric. While Azure Storage Explorer is mentioned as cross-platform, the rest of the workflow does not address Linux or macOS development environments.

Recommendations:

Provide equivalent instructions for developing and running Azure Functions using cross-platform tools such as Visual Studio Code or the Azure Functions Core Tools CLI.
Include examples of how to install required NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...'), which works on all platforms.
Add guidance for editing configuration files (like local.settings.json) manually or via CLI, rather than relying solely on Visual Studio UI dialogs.
Explicitly mention and link to Linux/macOS development guides where appropriate, or provide tabs for different OS instructions.
Clarify which steps are specific to Windows/Visual Studio and offer alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias, particularly in the C# sections, where instructions for importing certificates explicitly reference Windows Explorer and the Windows Certificate Import Wizard. The prerequisite section also assumes the use of the Windows command prompt for Node.js commands, even though Node.js is cross-platform. Environment variable setting examples use 'set', which is Windows-specific, and there is no mention of Linux or macOS equivalents. Linux-specific instructions are only present for IoT Edge scenarios, not for the main device connection workflows.

Recommendations:

Provide explicit instructions for Linux and macOS users alongside Windows instructions, especially for certificate import and environment variable setup.
Use cross-platform command syntax (e.g., 'export' for Unix shells, 'set' for Windows) or provide both variants in code blocks.
When referencing tools like the Windows Certificate Import Wizard, also mention and provide steps for Linux/macOS alternatives (e.g., using OpenSSL or keychain utilities).
In prerequisite and code sample sections, avoid language that assumes Windows as the default (e.g., 'the instructions in this tutorial assume you're running the node command at the Windows command prompt'). Instead, clarify that the steps are cross-platform and specify differences where necessary.
For C#/.NET, provide guidance for handling certificates on Linux (e.g., using PEM files directly or importing into the .NET Core certificate store).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by frequently specifying features as 'Windows apps only' and providing more detailed descriptions for Windows-specific diagnostic tools (e.g., Proactive CPU monitoring, Proactive auto-healing, Navigator). Several advanced diagnostic features are described as available only for Windows apps, with Linux equivalents mentioned only briefly or not at all. There are no Linux-specific troubleshooting examples or step-by-step instructions, and Linux support is often described as limited or secondary.

Recommendations:

Provide equivalent Linux examples and step-by-step instructions for diagnostic features wherever possible.
Clearly indicate feature parity or differences between Windows and Linux at the beginning of each relevant section.
Expand documentation for Linux-specific diagnostic tools and workflows, including screenshots and detailed usage guidance.
Where features are Windows-only, suggest alternative approaches or tools for Linux users.
Ensure that Linux and container scenarios are given equal prominence in feature descriptions and troubleshooting workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page is heavily focused on Windows-based App Service environments. It describes file paths, environment variables, and system behaviors using Windows conventions (e.g., %SystemDrive%, c:\, d:\), references Windows-specific tools and frameworks (IIS, ASP.NET, COM, PowerShell), and omits equivalent Linux details or examples. Linux is mentioned only in a brief note, with no further explanation or parity in examples, environment variables, or operational behaviors.

Recommendations:

Add parallel sections or callouts describing Linux App Service behaviors, including file system layout, environment variables (e.g., $HOME, /tmp), and storage persistence.
Provide Linux-specific examples alongside Windows ones, such as shell commands, file paths, and environment variable usage.
Clarify differences in diagnostic logging, process management, and network access for Linux containers, including supported tools and frameworks.
Avoid assuming Windows as the default; structure the documentation to address both Windows and Linux equally, or clearly indicate when content is Windows-specific.
Include links to Linux App Service documentation or quickstarts for readers interested in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally aims for cross-platform coverage, but there are several areas where Windows is prioritized or referenced before Linux. Some examples and settings are Windows-specific or use Windows-style paths (e.g., %HOME%\typescript), and PowerShell is given dedicated sections and examples. In a few cases, Windows tools or terminology are mentioned without always providing Linux equivalents or parity.

Recommendations:

Ensure that all examples using Windows-style paths (e.g., %HOME%\typescript) also include Linux equivalents (e.g., $HOME/typescript).
When referencing tools or commands (such as Azure PowerShell), always mention Azure CLI or other cross-platform alternatives alongside or before Windows-specific tools.
In lists or tables where both Windows and Linux are supported, present Linux examples first or at least equally, rather than defaulting to Windows.
For PowerShell-specific settings or features, provide equivalent guidance for other shells or languages where possible, or clearly indicate when a feature is Windows-only.
Audit for any settings or behaviors that are described as default or standard but are actually Windows-specific, and clarify Linux behavior in those cases.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias primarily by referencing Windows-specific tools (Guidgen.exe, Visual Studio) for GUID generation, without mentioning cross-platform or Linux alternatives. There are no command-line examples for Linux/macOS users, and the only tool suggested for GUID generation is a Windows utility. The documentation also implicitly assumes use of the Azure Portal UI, which is cross-platform, but where command-line or scripting is referenced, it is Windows-centric.

Recommendations:

When suggesting GUID generation, include cross-platform alternatives such as the uuidgen command (available on Linux/macOS) or PowerShell's [guid]::NewGuid() for Windows, and note that online GUID generators are also available.
Wherever a Windows-specific tool is mentioned (e.g., Guidgen.exe), provide equivalent commands or tools for Linux/macOS.
If showing command-line or scripting examples, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) equivalents.
Explicitly state that all steps can be performed on any OS via the Azure Portal, and provide CLI/REST API examples where appropriate.
Review all tool recommendations to ensure they are not Windows-exclusive, or at least present cross-platform options with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based workloads and tools (e.g., Citrix, FSLogix, MSIX app attach, SQL Server on Windows), explicitly stating that Linux SQL Server is not supported, and omitting any Linux-specific examples or guidance. Additionally, it references Windows/Active Directory security privileges without mentioning Linux equivalents.

Recommendations:

Clearly state the lack of Linux support up front and provide a roadmap or estimated timeline for Linux parity, if available.
Include examples or guidance for Linux workloads if/when support becomes available.
Where Windows-specific tools or privileges (e.g., SeSecurityPrivilege, Active Directory) are mentioned, provide Linux equivalents or clarify that these steps are not applicable to Linux environments.
Add a section addressing common Linux use cases and their current support status, to inform Linux administrators.
If Linux support is planned, invite feedback or provide a link for users to request Linux support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the 'Set up your dev environment' section, where Visual Studio for Windows is presented first and in greater detail than alternatives. Windows-specific tools (Visual Studio for Windows, Azure PowerShell) are mentioned explicitly and before their Linux/macOS equivalents. PowerShell is given its own section, and Windows-centric development environments are prioritized in the ordering of instructions. While Linux/macOS options are present, they are less emphasized and sometimes described in terms of their limitations (e.g., Visual Studio for Mac lacking integration).

Recommendations:

Reorder the 'Set up your dev environment' section to present cross-platform or non-Windows options (such as Azure CLI and Visual Studio Code) before Windows-specific tools.
Provide equal detail and positive framing for Linux/macOS development environments, including Visual Studio Code and Azure CLI, rather than highlighting their limitations.
Include explicit examples or notes for common Linux/macOS shells (e.g., bash, zsh) where command-line instructions are given.
Avoid giving Windows tools (Visual Studio for Windows, PowerShell) their own sections unless parity is provided for Linux/macOS tools.
Where possible, mention open-source or cross-platform alternatives alongside Windows-specific tools, and ensure all code samples and instructions are validated on Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools and workflows (such as Visual Studio and the Windows Classic Desktop template), providing only PowerShell/NuGet Package Manager Console commands, referencing the Windows-only Azurite storage emulator, and omitting explicit Linux or cross-platform instructions or examples. There are no examples or guidance for Linux users regarding equivalent development environments, package installation, or running the sample project.

Recommendations:

Provide equivalent instructions for Linux users, including how to set up and run projects using Visual Studio Code or JetBrains Rider, and .NET CLI commands for project creation and package installation.
Include Bash/.NET CLI examples alongside PowerShell/Package Manager Console commands for installing NuGet packages.
Mention cross-platform alternatives to the Azurite storage emulator and clarify how to run it on Linux/macOS.
Avoid using 'Windows Classic Desktop' as the default project template; instead, recommend .NET Core/.NET 6+ console apps, which are cross-platform.
Explicitly state which steps are Windows-specific and provide corresponding Linux/macOS steps where possible.
Add a section or callouts for deploying and running WebJobs from non-Windows environments, including any prerequisites or differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for per-app scaling configuration, without offering equivalent examples for Linux users (such as Azure CLI, Bash, or REST API). The use of PowerShell cmdlets and parameters is specific to Windows environments, and there is no mention of or guidance for Linux-native tools or workflows. The PowerShell section is presented before the ARM template section, reinforcing the Windows-first approach.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, demonstrating how to configure per-app scaling using cross-platform tools.
Include Bash or shell script snippets where appropriate to illustrate Linux workflows.
Explicitly mention that PowerShell examples can be run on Linux using Azure PowerShell, but provide native Linux alternatives for better parity.
Reorganize the documentation to present cross-platform (CLI/REST/ARM) approaches before or alongside PowerShell examples.
Clarify in the introduction that all major platforms are supported and provide links to relevant tooling for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily by mentioning Windows, Windows Server, and SMB 3.0 encryption support explicitly, while omitting equivalent Linux details. There are no Linux-specific examples or mentions of Linux-compatible tools for encryption in transit or at rest. Additionally, references to client-side encryption libraries focus on Java and .NET (commonly associated with Windows), and a blog post list highlights PowerShell attacks but only includes two Linux-specific posts late in the list. There are no Linux command-line or configuration examples, nor are Linux-native tools or patterns discussed.

Recommendations:

Explicitly mention Linux support for encryption in transit and at rest, such as SMB 3.0 support on Linux clients and how to configure it.
Provide Linux-specific examples or references for client-side encryption, such as using Python or OpenSSL.
Include parity in documentation for both Windows and Linux, ensuring that Linux tools, commands, and best practices are described alongside Windows equivalents.
Highlight Linux security monitoring and incident response tools (e.g., auditd, syslog, fail2ban) where relevant.
Balance blog post references to include more Linux-focused security scenarios and investigations.
When referencing Azure services or features, clarify their compatibility and usage patterns for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples present for every operation. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion in parity with CLI can signal a Windows-centric approach. Furthermore, the documentation includes PowerShell examples before or alongside CLI, and does not mention or provide Linux-native shell (e.g., Bash) or scripting examples. There is also no explicit mention of Linux tooling or Linux-specific considerations, despite App Service supporting Linux workloads.

Recommendations:

Clearly state that Azure CLI commands are fully supported on Linux, macOS, and Windows, and recommend CLI as the primary cross-platform tool.
Add explicit Bash shell script examples where relevant, or clarify that Azure CLI commands can be run in Bash or other Linux shells.
If PowerShell is included, clarify that Azure PowerShell is available cross-platform, but avoid implying it is required for Linux users.
Where platform-specific steps are necessary (e.g., for Linux or Windows containers), provide separate, clearly labeled instructions.
Review the order of examples: consider listing Azure CLI (cross-platform) before PowerShell to reinforce Linux parity.
Include troubleshooting or operational notes relevant to Linux environments, such as file permissions, shell differences, or integration caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias: it only provides instructions for deploying Windows Server virtual machines, uses PowerShell exclusively for scripting (including the Azure Cloud Shell example), and installs IIS (a Windows web server) as the backend workload. There are no examples or guidance for deploying Linux VMs, using Bash/CLI, or installing a Linux-based web server such as Apache or Nginx.

Recommendations:

Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
Include examples for installing a web server on Linux VMs (e.g., using apt to install Apache or Nginx).
Offer Azure CLI (Bash) equivalents for all PowerShell commands, especially for VM extension/script installation.
When referencing OS images, mention both Windows and popular Linux distributions, allowing users to choose.
Balance screenshots and walkthroughs to show both Windows and Linux scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by focusing on Windows-specific details, tools, and examples. It provides instructions and examples that are either exclusive to Windows (such as registry queries and references to Windows-specific files like web.config), or are presented only in the context of Windows App Service. There is a lack of equivalent Linux App Service instructions, examples, or references, and the documentation does not address how to obtain OS/runtime information or perform configuration on Linux-based App Service plans.

Recommendations:

Add equivalent instructions and examples for Linux App Service, including how to query OS and runtime versions using Linux commands (e.g., cat /etc/os-release, lsb_release -a).
Clarify when instructions or examples are Windows-specific, and provide parallel Linux-specific guidance where applicable.
Include examples of configuration files and settings relevant to Linux (e.g., appsettings.json, environment variables, or startup scripts) alongside Windows examples like web.config.
Mention Linux-specific tools or methods (such as Bash, SSH, or Linux file paths) for accessing and managing App Service instances.
Ensure that tables and code samples are balanced, showing both Windows and Linux approaches where differences exist.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes connecting to Azure Government using Visual Studio, a Windows-centric IDE, with no mention of Linux-compatible tools or workflows. All instructions, screenshots, and prerequisites assume the use of Visual Studio on Windows, with no alternatives or parity for Linux users. There are no examples or guidance for connecting from Linux environments or using cross-platform tools.

Recommendations:

Include instructions for connecting to Azure Government using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure PowerShell (which are available on Linux).
Provide Linux-specific steps or note any differences for users on Linux or macOS.
Mention and link to alternative tools and workflows that are supported on Linux, such as using the Azure CLI to log in to Azure Government.
Consider rephrasing the quickstart to clarify that it is Windows/Visual Studio-specific, or provide parallel quickstarts for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing installation instructions using the Visual Studio Package Manager Console (a Windows-centric tool) and referencing Visual Studio UI steps. The .NET Core CLI is mentioned, but the ordering and prominence of Windows/Visual Studio tooling is notable. There are no explicit Linux or cross-platform environment examples, nor are Linux-specific instructions or considerations provided.

Recommendations:

Add explicit Linux/macOS instructions for installing the required NuGet packages, such as using the .NET CLI in a bash shell.
Reorder the installation instructions to present the cross-platform .NET CLI method before the Visual Studio/Windows-specific Package Manager Console.
Clarify that Visual Studio steps are Windows-specific and provide equivalent steps for popular Linux/macOS IDEs or editors (e.g., VS Code).
Include a note or section on running and deploying the sample code on Linux-based environments, such as Azure App Service for Linux or local Linux development.
Review all tooling references to ensure parity, avoiding exclusive mention of Windows tools where cross-platform alternatives exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific features (such as Windows Admin Center and Microsoft Antimalware), mentioning Windows-only customization options, and omitting Linux-specific guidance or examples. There are no Linux-specific instructions or parity notes for Linux VMs, and Windows tools are referenced without Linux equivalents.

Recommendations:

Explicitly state which features are Windows-only and which are available for Linux VMs.
Add examples or notes for configuring Automanage custom profiles for Linux VMs, including supported services and any Linux-specific settings.
If certain services (e.g., Antimalware, Windows Admin Center) are not available for Linux, provide equivalent Linux security or management recommendations, or clarify their absence.
Include Linux command-line examples (such as Bash/CLI) where relevant, especially in deployment steps.
Consider a table or section comparing feature support between Windows and Linux VMs in Automanage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell, which is traditionally a Windows-centric tool, and does not provide any equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI). All code samples, explanations, and cleanup instructions use PowerShell commands, and there is no mention of Linux tools or cross-platform alternatives.

Recommendations:

Add equivalent Azure CLI (az) examples for each PowerShell command, including setup, deployment, and cleanup steps.
Include a section or note explaining how to perform these tasks on Linux/macOS using Bash and Azure CLI.
Present both PowerShell and Azure CLI examples side-by-side or in tabs, so users can easily select their preferred environment.
Avoid assuming the user is on Windows or using PowerShell by default; clarify cross-platform options in the introduction.
Link to both PowerShell and Azure CLI documentation for further reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. Windows-specific features and limitations (such as Windows Containers subnet sizing) are discussed in detail, while Linux-specific scenarios are only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies). There are no Linux-specific configuration examples or parity in troubleshooting or operational guidance. Windows terminology and patterns (such as references to Windows Server Active Directory, Windows Containers, and Kudu console UI) are used without equivalent Linux context or alternatives.

Recommendations:

Add Linux-specific examples and guidance where Windows-specific details are provided (e.g., subnet sizing for Linux containers, Linux-specific environment variables, or troubleshooting steps).
Include Linux-focused operational notes, such as how to access environment variables or logs in Linux-based App Service environments.
Balance references to Windows tools (like Kudu console UI) with Linux equivalents (such as SSH or Azure CLI usage in Linux containers).
Where Windows limitations or features are discussed (e.g., Windows Server Active Directory domain join), explicitly mention Linux equivalents or note if not applicable.
Expand the Linux continuous deployment section to include more comprehensive guidance and examples, similar to the detail given for Windows Containers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. In the manual setup section, the Maven plugin configuration explicitly sets the runtime OS to 'windows' without mentioning Linux or cross-platform options. In the Maven command section, while Bash, PowerShell, and Cmd examples are provided, the order places Bash first, but Windows-specific shells (PowerShell, Cmd) are given equal prominence. Visual Studio Code instructions are cross-platform, but there is no mention of Linux-specific considerations or troubleshooting. The documentation references Azure Functions Core Tools, which is cross-platform, but does not clarify any Linux-specific installation or usage notes. There is no explicit Linux example or guidance, and the only OS explicitly mentioned in configuration is Windows.

Recommendations:

In the Maven plugin configuration, provide examples for both Windows and Linux runtimes, or clarify that 'os' can be set to 'linux' and explain when to use each.
Add a note or section about Linux/macOS installation and usage of Azure Functions Core Tools, including any known issues or differences.
Where PowerShell and Cmd examples are given, ensure that Bash (Linux/macOS) is always listed first and is the default in code tabs, or provide a clear cross-platform command.
Explicitly state that all steps work on Linux and macOS, and call out any differences or additional steps required.
Consider including troubleshooting tips or links for common Linux/macOS issues (e.g., permissions, path differences, case sensitivity).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention or examples of Azure CLI (which is cross-platform and preferred on Linux/macOS) or ARM templates. The prerequisites and instructions reference Windows PowerShell and related tools exclusively. There are no Linux shell, Bash, or Azure CLI equivalents provided, nor any guidance for users on non-Windows platforms.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include a section or callout for Linux/macOS users, clarifying that all steps can be performed using Azure CLI and linking to relevant CLI documentation.
Avoid language that assumes the user is on Windows or using PowerShell (e.g., 'switch PowerShell mode'), or at least provide parallel instructions for Bash/CLI environments.
Consider including ARM/Bicep template examples for users who prefer declarative infrastructure-as-code approaches, which are platform-agnostic.
Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation instructions for all major platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page lists both Linux and Windows Azure App Service template samples, but there is a subtle bias towards Windows. Windows examples are often listed before Linux equivalents, and there are more detailed or varied Windows scenarios (e.g., Windows container, Windows with MySQL/PostgreSQL) compared to Linux. Some resource combinations are only shown for Windows, and there is no parity in example coverage for Linux (e.g., no Linux container example, no Linux app with Azure SQL Database). There are no command-line examples, so no PowerShell bias is present, but the pattern of presenting Windows first and more frequently is evident.

Recommendations:

Ensure Linux and Windows examples are presented in parallel, with equal coverage for each scenario (e.g., provide Linux container, Linux app with Azure SQL Database, Linux app with Redis, etc.).
Alternate the order of Linux and Windows examples or group them together to avoid always listing Windows first.
Where a scenario is only available for Windows, explicitly state this to avoid confusion.
Add missing Linux equivalents for all connected resource scenarios currently only shown for Windows.
Consider a dedicated section for Linux-specific templates to highlight parity and encourage cross-platform usage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses PowerShell for all examples and instructions, assumes the use of Azure PowerShell tooling, and does not mention or provide equivalent Bash, CLI, or Linux-native examples. All command references and cleanup instructions are PowerShell-specific, which may disadvantage users on Linux or macOS platforms.

Recommendations:

Provide equivalent Azure CLI (az) script examples alongside PowerShell, as Azure CLI is cross-platform and commonly used on Linux/macOS.
Include Bash script samples for deployment and cleanup steps.
Mention both PowerShell and CLI installation guides, clarifying cross-platform support.
Structure the documentation to present both Windows (PowerShell) and Linux/macOS (CLI/Bash) options equally, or link to Linux-specific guides.
Add a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained, and provide installation instructions for those platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by prioritizing Windows and Visual Studio (Windows) workflows, providing PowerShell and sqlcmd examples without Linux alternatives, and omitting explicit Linux/macOS development environment instructions for key steps such as database permission grants. Linux and cross-platform tooling are mentioned only in passing or as secondary options, and there are no bash or Linux-native SQL client examples for database administration.

Recommendations:

Provide explicit Linux/macOS equivalents for all command-line instructions, especially for database permission grants (e.g., using sqlcmd or Azure Data CLI on Linux).
Include examples using bash and cross-platform SQL clients (such as sqlcmd on Linux, Azure Data CLI, or Python-based tools) alongside PowerShell.
Reorganize sections so that cross-platform or Linux instructions are presented alongside or before Windows-specific instructions, rather than after.
Add a dedicated section or tab for Linux/macOS development environments, covering setup, authentication, and debugging workflows.
Ensure all tooling recommendations (e.g., for Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell) are presented with parity for Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell and Windows-centric tools and APIs (such as System.Net.FtpWebRequest), with no mention of Linux or cross-platform alternatives. All examples and cleanup instructions are provided only in PowerShell, and there are no Bash, Azure CLI, or Linux-native FTP tool examples. The focus on PowerShell and Windows APIs may make it less accessible or relevant for Linux users.

Recommendations:

Add equivalent Bash/Azure CLI examples for creating resources and uploading files via FTP, using common Linux tools such as curl, lftp, or ftp.
Include instructions for installing and using Azure CLI, which is cross-platform, alongside PowerShell.
Reference Linux-native FTP tools and provide sample scripts for Linux/macOS environments.
Structure the documentation to present both Windows (PowerShell) and Linux (Bash/CLI) approaches, or clearly indicate platform-specific sections.
Avoid exclusive reliance on Windows APIs (like System.Net.FtpWebRequest) and mention cross-platform alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All code samples use PowerShell cmdlets, and there are no examples or guidance for using Linux-based tools or Bash scripting. The instructions for installing modules and running commands assume a PowerShell environment, and there is no mention of cross-platform alternatives or how to perform these tasks on Linux-based Hybrid Runbook Workers. The documentation also refers to Windows concepts (e.g., elevated PowerShell prompt) and does not provide parity for Linux users.

Recommendations:

Provide equivalent Bash/CLI examples for connecting to Azure SQL Database using managed identities (e.g., using Azure CLI and sqlcmd).
Document how to set up and use Hybrid Runbook Workers on Linux, including module installation and authentication steps.
Include instructions for installing required modules or tools on Linux (e.g., using pip for Azure CLI, apt/yum for sqlcmd).
Mention cross-platform compatibility of Azure Automation and clarify which steps or commands are OS-specific.
Add a section or note explicitly addressing Linux users and linking to relevant resources for Linux-based automation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling logging, omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The use of PowerShell is presented as the primary (and only) scripting interface, and there is no mention of cross-platform tools or Linux-specific workflows. Additionally, tools like Excel and Visual Studio are referenced for log analysis and conversion, which are traditionally Windows-centric, without suggesting Linux-friendly alternatives. The ordering of examples and tool recommendations further reinforces a Windows-first perspective.

Recommendations:

Add equivalent Azure CLI and/or Bash examples alongside PowerShell commands for enabling diagnostic logging.
Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS users.
Include references to Linux-friendly tools for log analysis, such as jq, csvkit, or open-source alternatives to Excel and Visual Studio.
Ensure that tool recommendations (e.g., for log conversion) include cross-platform or Linux-native options, such as Python scripts or open-source utilities.
Balance the order of presentation so that Windows and Linux approaches are given equal prominence, or alternate which is presented first.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a dedicated PowerShell example and section before the Azure CLI example, without offering any Linux shell or Bash-specific guidance. There is no mention of Linux-native tools or workflows, and the PowerShell example is more prominently featured. This may make Linux users feel less supported or require them to adapt Windows-centric instructions.

Recommendations:

Add explicit Bash or Linux shell examples alongside PowerShell, especially for common tasks.
Present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Include troubleshooting steps or tool recommendations that are relevant for Linux environments (e.g., using curl, openssl, or Linux-based network troubleshooting tools).
Ensure that any references to scripts or automation include both PowerShell and Bash equivalents where possible.
Review the order of examples and avoid always listing Windows/PowerShell first unless there is a clear reason.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET Web Forms (.NET Framework), which is only supported on Windows. Visual Studio (Windows-only) is required, and all project setup instructions assume a Windows environment. While environment variable setup commands are provided for Windows Command Prompt, PowerShell, and (last) macOS/Linux, the overall workflow and prerequisites are Windows-centric, with no mention of Linux-compatible alternatives for development or deployment.

Recommendations:

Add a note at the beginning clarifying that ASP.NET Web Forms (.NET Framework) is Windows-only, and suggest .NET Core/ASP.NET Core for cross-platform scenarios.
Provide equivalent instructions for setting up and running a similar dynamic configuration sample using ASP.NET Core, which is cross-platform.
Include Linux/macOS-friendly IDE alternatives (e.g., Visual Studio Code, JetBrains Rider) and instructions for using the dotnet CLI where possible.
Reorder environment variable instructions to present Linux/macOS commands first or alongside Windows commands, rather than always after.
Where possible, highlight any differences or limitations for Linux/macOS users, and link to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides extensive PowerShell-based automation and scripting examples for configuring Azure Application Gateway with App Service, but does not include equivalent examples for Linux/Unix users (e.g., Azure CLI, Bash). All command-line automation is shown exclusively in PowerShell, which is primarily associated with Windows environments. There is no mention of cross-platform tools or Linux-native workflows, and no Bash, Azure CLI, or REST API examples are provided.

Recommendations:

Add Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
Where automation is shown, provide both PowerShell and Bash/Azure CLI tabs, or at least link to equivalent Azure CLI documentation.
Explicitly mention that all PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide guidance for non-Windows users.
Include REST API or ARM template examples for users who prefer declarative or cross-platform approaches.
Review and update the 'ms.custom' metadata to reflect cross-platform tooling, not just 'devx-track-azurepowershell'.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias: Windows issues and features are consistently listed before Linux equivalents, and some sections provide detailed workarounds or recommendations only for Windows (e.g., use of base64_decode_tostring() for Windows, but not for Linux). There are also references to Windows-specific tools and concepts (Windows Registry, Windows Services) without Linux equivalents being described in similar detail. In some extension versions, Linux changes are marked as 'None' or are less detailed, and Linux-specific issues or workarounds are not elaborated.

Recommendations:

Ensure Linux issues and features are described with equal detail and prominence as Windows.
Provide Linux-specific workarounds or equivalent commands/tools where Windows-specific ones are mentioned (e.g., if a KQL workaround is given for Windows, note if/how it applies to Linux).
List Linux and Windows changes/issues in parallel, rather than always listing Windows first.
Include examples or references for Linux tools and patterns (e.g., mention systemd for Linux daemons, or relevant Linux file/daemon tracking specifics).
Avoid marking Linux sections as 'None' without further context; if there are no changes, briefly explain why or what users should expect.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by exclusively referencing Visual Studio (a Windows-centric IDE) for application development and deployment, and by only providing .NET/ASP.NET Core code samples without mention of Linux or cross-platform development environments. There are no examples or instructions for Linux users, such as using VS Code, command-line tools, or deployment from Linux environments. The documentation assumes a Windows development workflow and omits Linux alternatives.

Recommendations:

Add instructions for setting up and configuring the application using cross-platform tools such as Visual Studio Code or JetBrains Rider, which are available on Linux.
Include command-line examples (e.g., using dotnet CLI) for application configuration and deployment, suitable for Linux/macOS users.
Mention and provide steps for deploying and running the ASP.NET Core application from Linux environments, including how to edit configuration files and run the app.
Ensure that references to Visual Studio are accompanied by alternatives or notes for Linux users.
Where possible, provide bash shell commands alongside any PowerShell or Windows-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell runbooks exclusively in the 'Next steps' section, without mentioning Linux or Python runbooks. There are no examples or guidance for Linux users or for using non-Windows scripting environments. The documentation assumes the use of PowerShell as the default automation language, which is more common on Windows.

Recommendations:

Include links to tutorials for creating Python runbooks using managed identity, as Python is commonly used for automation on Linux.
Explicitly mention that Automation accounts support both PowerShell and Python runbooks, and provide parity in examples and next steps.
Add a section or note for Linux users, clarifying that the steps apply regardless of OS, and reference relevant Linux-friendly tools or scripts.
Ensure that future documentation alternates or balances the order of PowerShell and Python/Linux examples, rather than defaulting to Windows-first patterns.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows and PowerShell by providing detailed PowerShell examples and references first, with Azure CLI examples following and no explicit Linux shell (bash) or cross-platform scripting examples. The 'Next steps' section directs users to a PowerShell-specific guide, and there is no mention of Linux tools or workflows for certificate extraction or management. The documentation assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Provide equivalent bash/Linux shell examples for certificate extraction, management, and Azure CLI usage.
In the 'Next steps' section, include links to both PowerShell and Azure CLI (bash) guides for mutual authentication configuration.
When listing configuration options (Portal, PowerShell, CLI), avoid always listing PowerShell first; alternate or clarify that CLI is cross-platform.
Add references or examples for common Linux tools (e.g., openssl) for certificate chain extraction and validation.
Explicitly state that Azure CLI commands can be run on Windows, Linux, or macOS, and provide sample commands in bash syntax where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides extensive examples using Azure PowerShell and references to PowerShell scripting, which is primarily a Windows-centric tool. In several cases, PowerShell is presented as a primary or parallel option to Azure CLI, and some code blocks are labeled as 'azurepowershell-interactive' even under CLI sections. There is no explicit mention of Linux shell scripting or Linux-specific command-line environments, and no examples are provided for Bash or other common Linux shells. The documentation assumes familiarity with PowerShell and does not offer parity for Linux users in scripting or tooling guidance.

Recommendations:

Add explicit Bash or Linux shell script examples alongside PowerShell for all relevant operations, especially for token retrieval and identity management.
Clarify in each section whether the Azure CLI and PowerShell examples are cross-platform, and provide notes or links for Linux/macOS users where appropriate.
Avoid labeling CLI examples as 'azurepowershell-interactive' when they are meant for Azure CLI, to reduce confusion.
Where PowerShell is not supported (e.g., user-assigned identity for App Service), explicitly mention alternative Linux-compatible approaches.
Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
Ensure that all code samples and instructions are tested and confirmed to work on both Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Script-based migration is only described using PowerShell, with no mention of Bash, shell, or native Linux scripting alternatives. Prerequisites and instructions for scripting focus on PowerShell installation and modules, which are more familiar to Windows users. While Linux is mentioned as a supported platform, and Linux-specific data types (like Linux files and daemons) are referenced, the scripting and automation guidance is Windows-centric. The documentation also lists Windows data types before Linux ones and generally presents Windows concepts first.

Recommendations:

Provide equivalent Bash or shell script examples for Linux users, or explicitly document how to run the migration using native Linux tools.
Include Linux-first or Linux-parity instructions and examples, such as using Azure CLI or Bash scripts for migration.
Clarify any platform-specific differences or limitations in the migration process for Linux VMs.
List Linux and Windows data types in a neutral or alternating order to avoid implicit prioritization.
Reference Linux-native tools and patterns (e.g., systemd, cron) where relevant, not just PowerShell and Windows modules.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows paths and referencing a Windows 64-bit machine for package download). There are no equivalent instructions or examples for Linux or macOS users, and Windows tools and patterns are mentioned exclusively.

Recommendations:

Provide equivalent Linux (and optionally macOS) instructions for downloading packages and dependencies, such as using the 'pip' command in a Linux shell.
Include Linux command-line examples alongside Windows examples, using standard Linux paths and conventions.
Avoid referencing only Windows-specific tools or environments; instead, offer cross-platform guidance or clarify when steps are platform-specific.
Add a note or section explicitly addressing how users on non-Windows systems can perform the same tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows environments by exclusively using Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate) for all steps. There are no examples or instructions for Linux users (e.g., using Azure CLI, OpenSSL, or Bash), and the prerequisites and workflow assume a Windows administrative PowerShell session. This makes it difficult for users on Linux or macOS to follow the tutorial.

Recommendations:

Provide parallel instructions and code examples using Azure CLI (az) for all resource creation and management steps.
Include Linux/macOS-compatible commands for certificate creation (e.g., using OpenSSL) and file path conventions.
Update the prerequisites section to mention both Azure PowerShell and Azure CLI, and clarify which is required for each example.
Where possible, use cross-platform tools or note platform-specific differences, ensuring Linux users are not excluded.
Reorder or balance examples so that Linux and Windows approaches are presented equally, rather than Windows-first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references Windows-centric tools and patterns, such as DSC resources and WaitFor resources, with links pointing to Windows PowerShell DSC documentation. There are no Linux-specific examples or references to Linux equivalents of DSC resources, and the documentation does not mention Linux-specific considerations for network configuration or agent communication.

Recommendations:

Include references and links to Linux DSC resources and documentation, such as the Linux DSC resource kit or documentation for Linux OMI-based DSC.
Provide examples or notes on configuring network requirements for Linux Hybrid Runbook Workers and State Configuration nodes.
Mention any Linux-specific ports, URLs, or agent behaviors if they differ from Windows.
Balance references to Windows and Linux in resource links and examples, ensuring Linux users can find relevant information easily.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All examples, terminology, and cmdlets are PowerShell-centric, with no mention of Linux, Bash, or cross-platform scripting. Windows tools and patterns (e.g., PowerShell cmdlets like Start-AzVM, Write-Warning, Get-AutomationVariable) are used exclusively, and there are no Linux or Bash equivalents provided. The error handling concepts are described solely in the context of PowerShell, and the documentation implicitly assumes the reader is operating in a Windows/PowerShell environment.

Recommendations:

Include examples using Bash or Python runbooks, which are supported in Azure Automation, to illustrate error handling in non-Windows environments.
Mention and demonstrate how error handling works in Linux-based runbooks, including differences in error types and handling patterns.
Provide parallel examples for common tasks (e.g., starting a VM, sending notifications) using both PowerShell and Bash/Python.
Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to address both Windows and Linux automation scenarios equally.
Reference relevant Linux tools or scripting patterns (e.g., try/catch in Bash, error codes, set -e) where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, exclusively using Windows Server, PowerShell, and Windows-specific tools (Chocolatey, PowerShell DSC, WindowsFeature, xNetworking) in all examples and instructions. Linux is only mentioned in passing, with no equivalent examples or guidance for Linux systems. The workflow, commands, and tooling are all tailored to Windows, with no parity for Linux users.

Recommendations:

Provide equivalent Linux examples using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or Azure Automation State Configuration for Linux if available).
Include step-by-step instructions for setting up continuous deployment on Linux VMs, including sample configuration files and automation scripts.
Mention and demonstrate cross-platform tools or patterns where possible, and clarify any Azure Automation features that are Windows-only or deprecated for Linux.
Balance the documentation by presenting Linux scenarios alongside Windows, especially in sections describing high-level concepts, workflows, and automation patterns.
Clearly indicate the current support status for Linux in Azure Automation State Configuration, and provide links or references to Linux-specific guidance if Windows is the only supported platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including a PowerShell/winget example) are presented before Linux instructions. The Windows-specific tool 'winget' is highlighted, and the PowerShell command is shown, while the Linux example is more generic. However, both platforms are covered, and most of the rest of the guide uses cross-platform Azure CLI and Bash commands.

Recommendations:

Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetically) to avoid implicit prioritization.
Provide equally detailed installation steps for both Windows and Linux, including package manager options for Linux (e.g., apt, yum, snap) rather than only a curl script.
Avoid highlighting Windows-specific tools (like winget) without mentioning Linux equivalents (such as apt, yum, or snap).
Where possible, use cross-platform commands and clarify when a command is platform-specific.
Consider adding a macOS section if relevant, to further improve parity and inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments. All examples and instructions use PowerShell, reference Windows-style paths (e.g., D:\examplefiles), and mention only Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Linux shell commands or file path formats provided. The documentation assumes the user is operating in a Windows environment throughout.

Recommendations:

Provide equivalent examples for Linux-based Hybrid Runbook Workers, including bash shell commands for file creation and Linux file path formats (e.g., /home/examplefiles).
Mention that Azure Automation Hybrid Runbook Workers can run on Linux, and provide any relevant prerequisites or differences.
Include sample runbooks or scripts that work on Linux, or explain how to adapt the provided PowerShell scripts for Linux environments (e.g., using PowerShell Core on Linux or bash scripts).
Clarify in the prerequisites and steps where instructions diverge for Windows vs. Linux, and offer both sets of instructions side by side.
Avoid assuming the use of Windows tools (like PowerShell) exclusively; reference cross-platform tools or provide alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page for Azure Automation updates demonstrates a Windows and PowerShell bias. Most examples and feature announcements focus on PowerShell runbooks, with PowerShell versions and modules (e.g., AzureRM, Az) being highlighted more frequently and in greater detail than their Linux or cross-platform equivalents. Python support is mentioned, but typically as a secondary note. There is a lack of explicit Linux shell (Bash) or native Linux automation examples, and Windows/PowerShell tools and terminology are often presented first or exclusively.

Recommendations:

Include explicit Bash or native Linux shell script examples and announcements alongside PowerShell updates.
When announcing new features (e.g., runtime environments, CLI support), provide parity in examples and explanations for both Windows/PowerShell and Linux/Bash users.
Highlight Linux-specific tools, modules, or best practices where relevant, not just Windows/PowerShell ones.
Ensure that migration and retirement notices (e.g., for modules or workers) address both Windows and Linux users equally, with clear guidance for each.
Balance the order of presentation so that Linux and cross-platform options are not always secondary to Windows/PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas: Windows-specific deployment methods (such as source control, Local Git, and FTPS) are called out as 'Windows-only' in the availability table, with no Linux equivalents or alternatives described. Explanations of remote build and deployment behaviors often start with Windows, providing more detail for Windows scenarios (e.g., Kudu/SCM site), and Linux instructions are less prominent or require additional manual configuration. There are also references to Visual Studio (a Windows-centric tool) before cross-platform or Linux-native tools, and some deployment methods (e.g., FTPS, Local Git) lack Linux-specific guidance or alternatives.

Recommendations:

Provide Linux equivalents or alternatives for deployment methods currently marked as 'Windows-only' (e.g., Source Control, Local Git, FTPS), or clearly state if no equivalent exists and suggest best practices for Linux users.
Ensure that deployment examples and instructions are given for both Windows and Linux platforms, ideally side-by-side or with equal prominence.
When listing tools, mention cross-platform options (e.g., Azure Functions Core Tools, VS Code) before Windows-specific tools (e.g., Visual Studio), or present them together.
Expand explanations for Linux deployment scenarios, including details on how to perform common tasks (such as remote build, trigger syncing, or storage configuration) on Linux.
Where a feature is not available on Linux, provide a rationale and suggest alternative workflows for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is mentioned explicitly and equally alongside the cross-platform Azure CLI. There are no Linux- or bash-specific examples or mentions, and PowerShell is referenced without clarifying its cross-platform availability. The ordering of instructions often lists PowerShell before or alongside CLI, but never bash or Linux-native tooling. No Linux-specific guidance or screenshots are provided.

Recommendations:

Emphasize Azure CLI as the primary example, as it is cross-platform and works natively on Linux, macOS, and Windows.
Clarify that PowerShell Core is available cross-platform, or otherwise avoid implying it is Windows-only.
Add explicit bash shell examples for ARM template deployment, e.g., using curl and az CLI together.
Where screenshots or UI instructions are given, ensure they are not Windows-specific or clarify that the Azure portal is OS-agnostic.
If mentioning PowerShell, always mention Azure CLI first to avoid the perception of Windows-first bias.
Consider including a section or note for Linux users, highlighting any differences or confirming parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page is heavily oriented toward Windows environments, focusing exclusively on PowerShell-based automation, Windows file paths, and Windows-specific tools and patterns. There are no examples or guidance for Linux users, nor any mention of Bash, Linux-compatible modules, or cross-platform considerations. All examples and tool references (such as the Runbook Converter and integration modules) assume a Windows environment.

Recommendations:

Provide examples for Linux users, such as using Bash or Azure CLI where possible.
Clarify whether the Runbook Converter and integration modules can be used on Linux or only on Windows, and provide alternatives or workarounds if not.
Include file path examples using Linux conventions (e.g., /home/user/runbooks) alongside Windows paths.
Mention any cross-platform compatibility or limitations for Azure Automation and related tools.
If PowerShell Core (pwsh) is supported, specify this and provide examples using it on Linux.
Add a section or note for Linux users outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples use Windows PowerShell cmdlets, and there are no equivalent examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide guidance for Linux-native tools or workflows. The structure and ordering of the content also present Windows/PowerShell methods before platform-neutral or Linux-friendly alternatives.

Recommendations:

Add equivalent Azure CLI examples for starting and managing runbooks, including parameter passing and job status retrieval.
Clarify that PowerShell Core (pwsh), which is cross-platform, can also be used, and provide examples where appropriate.
Avoid using 'Windows PowerShell' exclusively; refer to 'PowerShell' and specify when examples are compatible with both Windows and Linux.
Include a section or table row for Linux/macOS users, highlighting supported tools and methods (e.g., Azure CLI, REST API, PowerShell Core).
Ensure that all parameter handling examples are shown in both PowerShell and Azure CLI syntax.
Review terminology and ordering to avoid presenting Windows-specific tools and workflows before cross-platform or Linux-native options.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the 'Try the sample' section by exclusively providing PowerShell-based deployment instructions and referencing PowerShell as a prerequisite. There are no equivalent instructions or scripts for Linux or macOS users (e.g., Bash scripts or shell commands). The use of PowerShell and the lack of cross-platform deployment guidance may hinder Linux users from following the tutorial seamlessly.

Recommendations:

Provide equivalent Bash shell scripts and instructions for Linux/macOS users alongside PowerShell examples.
Clearly indicate which steps are platform-specific and offer alternatives where necessary (e.g., use Bash for Linux, PowerShell for Windows).
If the deployment script is inherently cross-platform (e.g., via Azure CLI), demonstrate usage in both PowerShell and Bash.
List prerequisites for both Windows and Linux environments, including installation steps for PowerShell Core on Linux if it is required.
Consider restructuring the 'Try the sample' section to present both Windows and Linux instructions in parallel, ensuring parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by only providing examples for creating a Windows virtual machine (no Linux VM example), and by referencing Windows-specific tools and patterns (e.g., Azure PowerShell, Windows image names). There is no mention or example of creating a Linux VM, nor are Linux-specific considerations or commands provided.

Recommendations:

Add parallel examples for creating a Linux virtual machine using both Azure CLI and Azure PowerShell, including appropriate image references (e.g., Ubuntu, CentOS).
Explicitly mention that the tutorial applies to both Windows and Linux VMs, and highlight any differences in configuration or prerequisites.
Include Linux-specific notes or troubleshooting tips where relevant (e.g., SSH key authentication, Linux admin username requirements).
Ensure that all tool references (Azure CLI, PowerShell) are presented with equal prominence and that Linux users are not implicitly directed to Windows-centric tools or workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows/Powershell bias. It references PowerShell as the tool for viewing job logs outside the portal and discusses error streams in the context of PowerShell. There are no examples or mentions of Linux tools or command-line interfaces (such as Azure CLI, Bash, or Linux shell scripting) for interacting with Azure Automation logs. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide Linux-specific guidance or parity in examples.

Recommendations:

Include examples using Azure CLI for querying or managing Automation logs, alongside or instead of PowerShell.
Explicitly mention that the log querying and monitoring features are available and supported on Linux systems, not just Windows.
Provide sample scripts or command-line instructions for Linux users (e.g., Bash scripts, use of az CLI, or Kusto queries executed via CLI).
Clarify that runbooks can be authored and managed from Linux environments, and provide links or references to Linux-compatible tooling.
Avoid language that assumes PowerShell is the default or only way to interact with Azure Automation logs; present alternatives equally.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent examples for Bash, curl, or other common Linux tooling. Even REST API usage is shown via PowerShell's Invoke-RestMethod. There are no references to Linux command-line tools, and the workflow assumes a Windows/PowerShell environment throughout. This limits accessibility for Linux users and those working in cross-platform environments.

Recommendations:

Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.).
Show how to authenticate and interact with Azure using Azure CLI (az) commands, not just PowerShell Az module.
For REST API sections, include examples using curl or httpie, not only PowerShell's Invoke-RestMethod.
When presenting multiple approaches, do not always list PowerShell first; alternate or present both together.
Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
Where possible, include notes or troubleshooting tips relevant to Linux environments (e.g., file path formats, authentication differences).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by consistently referencing Windows-specific instructions and tools (such as the Hybrid Runbook Worker VM extension with '?tabs=windows'), and omitting Linux-specific examples or guidance. All links and examples for installing or managing Hybrid Runbook Workers default to Windows, with no mention of Linux equivalents or cross-platform considerations. This may lead Linux users to feel unsupported or unclear about best practices for their environments.

Recommendations:

Provide explicit Linux-specific instructions and examples alongside Windows ones, especially for installing and managing Hybrid Runbook Workers.
Ensure all links that currently default to '?tabs=windows' also reference or highlight the Linux tab or equivalent documentation.
Mention Linux tools, patterns, and security considerations where relevant, such as differences in permissions, authentication, or network isolation on Linux systems.
Add a section or callout clarifying cross-platform support and any differences in implementation or security best practices between Windows and Linux environments.
Review all examples and ensure parity by including both PowerShell (Windows) and Bash/Shell (Linux) script examples where automation or scripting is discussed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All code examples are in PowerShell, with no Bash, CLI, or Linux-native scripting examples. File paths and script types referenced (e.g., .ps1, C:\Runbooks\) are Windows-centric. There is no mention of Linux shell scripting, Azure CLI, or cross-platform automation tools. The documentation assumes the user is operating from a Windows environment and using PowerShell, omitting guidance for Linux users.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands for each PowerShell example, especially for creating, importing, publishing, and managing runbooks.
Include Bash shell script examples and reference Linux file paths (e.g., /home/user/Runbooks/) alongside Windows paths.
Explicitly mention and demonstrate how to use runbooks authored in Python or Bash, not just PowerShell.
Clarify which features and procedures are available or different on Linux-based Hybrid Runbook Workers.
Add a section or callouts for Linux/macOS users, including prerequisites and environment setup.
Ensure that references to tools and patterns (such as credential management, file import, and job status retrieval) include both PowerShell and cross-platform alternatives.
Review and update terminology to avoid assuming a Windows-only environment (e.g., avoid only referencing .ps1 files and C:\ paths).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-specific settings and examples. The JSON script heavily details Windows registry paths and file settings, while Linux settings are less detailed and lack equivalent examples. The only reference example for file settings is for Windows paths, with no Linux file path example provided. Windows-specific tools and patterns (e.g., registry keys, Windows directory paths) are mentioned exclusively, and Windows is consistently presented before Linux.

Recommendations:

Provide equivalent Linux file settings examples alongside Windows examples, such as a JSON snippet for tracking files in typical Linux directories (e.g., /var/log/* or /etc/*).
Include more detailed Linux-specific configuration options, similar to the depth given for Windows registry and file settings.
When listing both Windows and Linux extensions or settings, present them in parallel or alternate the order to avoid always listing Windows first.
Add explanatory notes or tables comparing Windows and Linux settings, highlighting differences and similarities.
Ensure that all examples and reference sections include both Windows and Linux use cases to achieve parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell and Windows-centric tooling (such as PowerShell ISE and the AWSPowerShell module) for all examples and instructions. There are no references to Linux-native tools, Bash scripting, or cross-platform alternatives such as AWS CLI or Python. The workflow assumes a Windows environment and does not provide parity for Linux users, omitting any Linux shell or cross-platform scripting guidance.

Recommendations:

Provide equivalent examples using AWS CLI commands in Bash scripts, which can be run on Linux or macOS Automation Hybrid Workers.
Include instructions for importing and using the AWS Tools for PowerShell Core, which is cross-platform, or clarify if only Windows PowerShell is supported.
Add a section or callout for Linux/macOS users, describing how to author and execute runbooks using Python or Bash, and how to install necessary modules or packages.
Mention and demonstrate the use of cross-platform editors (such as VS Code) instead of PowerShell ISE, which is Windows-only.
Clarify any platform limitations in prerequisites, and provide links to Azure Automation documentation for Linux Hybrid Workers.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page provides only PowerShell-based examples for disabling a system-assigned managed identity via the REST API, with no equivalent examples for Linux or cross-platform tools (such as Azure CLI or curl). The scripting and authentication steps are tailored to Windows environments and PowerShell users, and there is no mention of Linux-native workflows or tools.

Recommendations:

Add equivalent Azure CLI examples for authentication and sending the PATCH request, which work cross-platform (Windows, Linux, macOS).
Provide a curl example for sending the REST API request, including details on how to obtain an access token using Azure CLI (az account get-access-token).
Explicitly mention that the PowerShell example is Windows-centric and offer alternative instructions for Linux/macOS users.
Consider reordering or parallelizing the examples so that Windows and Linux instructions are presented together, or at least ensure Linux examples are not omitted.
Reference relevant documentation for Linux users, such as Azure CLI authentication and REST API invocation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments: it explicitly states support for C# class library functions on Windows, references Azure Files (default for Windows), and omits Linux-specific guidance or examples. There are no Linux or cross-platform command-line examples, and Linux-specific deployment patterns are only briefly mentioned in passing, without actionable steps.

Recommendations:

Clearly indicate Windows-specific limitations at the top and provide equivalent Linux guidance or note when features are unavailable.
Add parallel instructions and examples for Linux-based function apps, including how to handle storage and identity configuration on Linux.
Include CLI (az), Bash, or cross-platform scripting examples alongside or instead of portal-only instructions.
Discuss Linux-specific storage options and deployment patterns (e.g., how to handle AzureWebJobsStorage and Azure Files on Linux Consumption and Premium plans).
Where features differ (e.g., Azure Files not being default on Linux), explain the implications and provide alternatives.
Ensure that references to tools and patterns (such as ARM templates or portal steps) are not Windows-centric and clarify any OS-specific behaviors.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Visual Studio and its project settings in detail, with no equivalent coverage for Linux-native development environments or tools. Visual Studio (a Windows tool) is discussed first and in depth, while Visual Studio Code and Azure Functions Core Tools (which are cross-platform) are mentioned only briefly and without Linux-specific guidance or examples. There are no explicit Linux command-line examples or instructions for Linux users, and the process of pinning to a minor version is said to differ between Windows and Linux, but only a link is provided with no Linux-specific explanation or example.

Recommendations:

Provide explicit Linux command-line examples for tasks such as changing runtime versions, pinning to minor versions, and local development.
Include parity in tooling instructions by offering equivalent steps for Linux-native environments (e.g., JetBrains Rider, VS Code on Linux, or CLI-only workflows) alongside Visual Studio instructions.
When mentioning differences between Windows and Linux (e.g., pinning to a minor version), include both sets of instructions or examples directly in the documentation.
Avoid presenting Windows tools or workflows first by default; consider parallel presentation or starting with cross-platform tools.
Add a section or callout specifically for Linux/macOS users to ensure their workflows are equally represented.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows, providing only Windows and PowerShell-based instructions and tooling (usbipd-win, PowerShell modules, Windows Package Manager, Windows Services, etc.) for connecting USB devices to Azure IoT Edge for Linux on Windows (EFLOW). There are no equivalent Linux command-line examples or instructions for users who may want to perform similar operations from a Linux host or within the EFLOW VM using native Linux tools. Linux patterns and tools are either missing or only referenced as secondary considerations.

Recommendations:

Provide equivalent Linux command-line instructions for installing and using usbip (e.g., using apt, yum, or other package managers) for users who may be running EFLOW on a Linux host or want to interact with usbip from within the EFLOW VM.
Include bash shell examples for listing, attaching, and detaching USB devices using native Linux usbip tools, in addition to the PowerShell examples.
Mention Linux-native tools and workflows (such as lsusb, usbip, modprobe, etc.) earlier and in parallel with Windows tools, not only as an afterthought.
Clarify which steps are specific to Windows hosts and which can be performed from within the EFLOW VM or a Linux environment.
Add a section or callout for users who may want to use or test USB over IP from a Linux host, or who are troubleshooting from within the Linux VM.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is explicitly targeted at C# class library functions on Windows, with no mention of Linux or cross-platform support. All examples and instructions assume use of the Azure portal or .NET CLI, with no Linux-specific guidance or parity checks. There are no examples for Linux-based deployments or for using the Azure Functions Core Tools on Linux/macOS, and no mention of Bash or cross-platform shell commands.

Recommendations:

Clearly indicate at the beginning of the tutorial whether the steps are applicable to Linux and macOS, and provide equivalent instructions where possible.
Add Linux/macOS-specific examples for creating and deploying function apps, including using Bash shell commands and Azure CLI from non-Windows environments.
Include notes or sections for differences in environment variable configuration on Linux (e.g., case sensitivity, file paths, use of export in Bash).
Provide cross-platform guidance for local development, such as how to set up local.settings.json and assign roles using Azure CLI or Bash scripts.
If certain features are Windows-only, explicitly state the limitations and provide workarounds or alternatives for Linux users.
Ensure that all code and command-line examples are tested and valid on both Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page references 'Powerscribe', a tool that is primarily Windows-based, and includes a sample document with Windows-style line endings (\r\n). There are no Linux or cross-platform equivalents mentioned, nor are there examples or references to Linux tools or patterns. The documentation does not provide parity for Linux users.

Recommendations:

Include examples or references to Linux-compatible tools for radiology report distribution or dictation (e.g., open-source alternatives or cross-platform solutions).
Ensure sample data uses platform-neutral line endings (\n) or clarify that the API is agnostic to line ending style.
Add a note or section describing how Linux users can interact with or process the data, including any relevant command-line tools or scripts.
If Powerscribe is required, clarify its platform limitations and suggest alternatives for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI, often before or with more detail than Linux-specific workflows. Several features and tools (such as Kudu, App Service Editor, and in-portal console) are described as available or fully functional only on Windows, with Linux support either missing, limited, or explicitly marked as unsupported. Migration steps and plan management are documented only for Windows, with Linux migration called out as unsupported or limited. There are also several places where Windows terminology and patterns are used by default, and Linux alternatives are not described or are marked as unavailable.

Recommendations:

Provide explicit Linux examples and workflows where possible, especially for command-line and deployment operations.
Clarify feature parity and limitations for Linux up front, and offer Linux-specific guidance or workarounds where features are missing.
Balance the use of PowerShell and CLI examples, and avoid presenting Windows tools or patterns first unless they are the only option.
Where features are Windows-only (such as Kudu, App Service Editor, or in-portal console), suggest alternative Linux-compatible tools or approaches.
For plan migration and management, document Linux-specific scenarios and clearly outline supported migration paths for Linux-hosted function apps.
Review screenshots and UI instructions to ensure they are relevant for both Windows and Linux users, or provide parallel guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux (bash) and Windows (PowerShell, Cmd) instructions for most steps, but consistently lists Windows-specific commands and tools (PowerShell, Cmd, 'py' launcher) before or alongside Linux equivalents. Some troubleshooting and environment setup guidance is Windows-specific, and Windows tools (e.g., registry edits, 'py' launcher) are mentioned without Linux/macOS parallels. There is a slight preference for Windows-first presentation and more detailed Windows troubleshooting.

Recommendations:

Alternate the order of platform-specific tabs or examples, sometimes listing bash/Linux first to avoid implicit prioritization of Windows.
Where Windows-specific troubleshooting is provided (e.g., registry edits for long paths), add equivalent Linux/macOS troubleshooting tips if applicable, or explicitly state when an issue is Windows-only.
When referencing tools like the 'py' launcher (Windows), clarify the equivalent commands for Linux/macOS (e.g., always show 'python3' or 'python' usage).
Ensure that all environment setup, activation, and troubleshooting steps are equally detailed for Linux/macOS as for Windows.
Consider adding a summary table of commands for all platforms at the end of each section for quick reference.
Review the order of platform-specific instructions to avoid always listing Windows first, which can reinforce a Windows-centric perspective.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows and PowerShell, with all examples and terminology referencing PowerShell commands, workflows, and Windows-centric assemblies. There are no Linux or cross-platform scripting examples, nor is there mention of Bash, Python, or other non-Windows automation tools. The SDK and activities are described exclusively in terms of PowerShell, and the prerequisites and workflows assume a Windows environment.

Recommendations:

Add explicit statements about platform support, clarifying whether the SDK and graphical runbooks can be authored or executed on Linux/macOS environments.
If supported, provide equivalent examples using Bash, Python, or other cross-platform scripting languages.
Mention any Linux-compatible tools or workflows, or clearly state if the SDK is Windows-only.
Include guidance for Linux users on how to interact with Azure Automation graphical runbooks, or provide alternative automation options for non-Windows environments.
Reorder explanations and examples to avoid always presenting Windows/PowerShell first, or provide parallel examples for other platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for deploying Bicep files, but the inclusion of Azure PowerShell (which is primarily a Windows-centric tool) alongside Azure CLI (which is cross-platform) introduces a Windows bias. PowerShell examples are given equal prominence to CLI, and the documentation refers to 'Azure PowerShell' as a primary deployment method, which may not be as relevant for Linux users. There are no Linux-specific shell (bash) examples or explicit mention of Linux environments, and PowerShell is presented as a first-class option rather than as an alternative for Windows users.

Recommendations:

Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows.
Add bash/zsh shell examples for common Linux workflows, especially for validation and cleanup steps.
If PowerShell is included, clarify its cross-platform availability but note its prevalence on Windows.
Consider reordering sections to present Azure CLI (or bash) before PowerShell, or group PowerShell as a Windows-specific alternative.
Explicitly mention Linux/macOS compatibility in the prerequisites and throughout the instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only a PowerShell script for identifying function apps to migrate, referencing Azure PowerShell as the primary tool for this task, and omitting equivalent Bash, Azure CLI, or Linux-native instructions. The initial migration steps and tooling recommendations (e.g., Visual Studio, PowerShell) are presented from a Windows-centric perspective, with no parity for Linux or cross-platform users in the core discovery and migration workflow.

Recommendations:

Provide equivalent Azure CLI and/or Bash script examples alongside the PowerShell script for identifying function apps to migrate, ensuring Linux and macOS users have clear guidance.
When referencing Azure PowerShell, also mention Azure CLI as an alternative, and provide links or examples for both.
Avoid language such as 'use the following PowerShell script' without offering a cross-platform alternative.
In sections discussing publishing or migration tooling (e.g., Visual Studio), mention and provide instructions for cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
Audit all code snippets and workflow steps to ensure Linux users are not required to adapt Windows-specific instructions on their own.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows and PowerShell, with all examples and instructions using Windows PowerShell. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and no Linux or cross-platform alternatives are provided. The use of Windows-specific tools and patterns (such as Send-MailMessage and credential assets for PowerShell) further reinforces the Windows bias. There are no Bash, Azure CLI, or PowerShell Core examples, nor any mention of how to perform these tasks on Linux or macOS.

Recommendations:

Provide equivalent examples using PowerShell Core (pwsh), which is cross-platform, and clarify which cmdlets are supported.
Include Azure CLI examples for authentication and management where possible, as Azure CLI is cross-platform.
Explicitly state platform limitations and suggest workarounds or alternatives for Linux/macOS users.
Highlight any Office 365 or Azure Automation features that are not available on non-Windows platforms.
Where Windows PowerShell is required, suggest using cloud-based automation (e.g., Azure Automation runbooks) that abstracts away the local OS, and clarify that local scripting on Linux/macOS is not supported for these features.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell-based automation, with all code samples and instructions using PowerShell cmdlets and modules (Az, AzureRM), which are most commonly used in Windows environments. There are no examples or guidance for using other scripting languages or tools (such as Python, Bash, or CLI), nor is there mention of Linux-native automation patterns. The documentation assumes the use of the Azure portal UI, which is platform-agnostic but often associated with Windows workflows. Linux or cross-platform automation scenarios are not addressed.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
Include sample scripts in Bash or Python for authenticating with managed identities in Azure Automation, especially for hybrid runbook workers running on Linux.
Explicitly mention support for Linux-based hybrid runbook workers and provide migration steps or code samples for those environments.
Clarify that managed identities and Azure Automation are supported on both Windows and Linux, and link to relevant Linux documentation.
Balance the order of presentation by including Linux or cross-platform examples alongside or before PowerShell/Windows examples.
Reference Linux tools (such as cloud-init, systemd, or cron) where relevant for automation scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows and PowerShell tooling for configuring multiple NICs on Azure IoT Edge for Linux on Windows (EFLOW). All configuration steps are performed using PowerShell commands and Windows-specific tools, with no equivalent Linux command-line or cross-platform alternatives provided. The workflow assumes the user is operating from a Windows environment, and Linux-native methods or tools are not mentioned or demonstrated.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using SSH, nmcli, ip, or netplan) for managing network interfaces inside the EFLOW VM.
Document how to perform these configuration steps from a Linux or cross-platform environment, if possible.
Clarify which steps must be performed on the Windows host versus inside the Linux VM, and provide Linux-native alternatives for in-VM configuration.
Consider including Azure CLI or portal-based instructions where possible to reduce reliance on Windows-specific tools.
Explicitly state if certain operations are only possible from Windows, and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI throughout, but there are no explicit Linux shell (bash) or scripting examples. Migration between plans is only supported on Windows, with Linux migration explicitly unsupported. In several places, Windows is mentioned first (e.g., in region scale-out tables and migration), and Windows-specific tools (PowerShell) are given equal prominence to cross-platform tools (CLI), but Linux-native scripting or commands are not. There is also a lack of Linux-specific guidance or parity in some features.

Recommendations:

Provide bash or Linux shell script equivalents for all Azure PowerShell examples, or clarify that Azure CLI commands are cross-platform and sufficient.
When listing operating systems (e.g., in region tables, migration sections), alternate the order or explicitly address both equally, rather than defaulting to Windows-first.
For migration, clarify the roadmap or alternatives for Linux users, or provide a workaround if possible.
Include Linux-specific considerations or troubleshooting tips where relevant, especially in sections where Windows-specific behaviors or limitations are discussed.
Review all examples and ensure that Linux users are not left without guidance or are not required to use Windows tools for management tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation for Azure Functions Core Tools demonstrates a moderate Windows bias. The page references Windows-specific tools and patterns (such as func.exe and the use of .pfx certificates), and some features or instructions are described in a way that assumes a Windows environment. There is a lack of explicit Linux/macOS examples, and certain options (like certificate handling) are described in a way that is more familiar to Windows users. Additionally, PowerShell is mentioned as a supported runtime with special features, but there is little parity discussion for Linux shells or scripting environments.

Recommendations:

Provide explicit Linux/macOS command-line examples alongside or in place of Windows-centric ones.
Avoid referencing Windows-specific binaries (e.g., func.exe) in the title or introductory text; use cross-platform terminology (e.g., Azure Functions Core Tools CLI).
Where features are Windows-specific (such as .pfx certificate handling), clarify cross-platform support and provide equivalent instructions for Linux/macOS (e.g., using OpenSSL-generated certificates).
When mentioning PowerShell-specific features, also discuss parity or alternatives for Bash or other common Linux shells.
Ensure that any references to local emulators, encryption, or file paths include Linux/macOS equivalents.
Add notes or tables indicating OS support for each feature or command where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) command examples for onboarding and configuring Azure Large Instances, without offering equivalent Azure CLI or Linux shell examples. The instructions for enabling ExpressRoute Fast Path and related tasks are exclusively shown using PowerShell cmdlets, and there is no mention or example of how to perform these tasks using Linux-native tools or cross-platform CLI. Additionally, the guidance to install PowerShell modules is presented before any mention of Linux compatibility, and there is no explicit parity for Linux users.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all configuration steps, especially for ExpressRoute and networking setup.
Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant cross-platform documentation.
Where PowerShell is required, clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions for those platforms.
Add Linux shell (bash) script examples for variable declaration and command execution, ensuring Linux users can follow the onboarding process without switching to Windows tools.
Review all sections for implicit Windows-first language or assumptions, and ensure Linux and cross-platform scenarios are treated with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a strong Windows bias. All examples and instructions for managing SMB volume permissions and share properties are provided exclusively for Windows environments, specifically referencing Windows SMB clients, Microsoft Management Console (MMC), and Windows File Explorer. There are no examples or guidance for Linux clients, even though SMB is cross-platform and Linux clients (e.g., using smbclient, mount.cifs, or Nautilus) are common in enterprise environments. The documentation assumes Windows as the default or only client, omitting Linux tools and workflows.

Recommendations:

Add parallel instructions and screenshots for managing SMB share and NTFS permissions from Linux clients, using tools such as smbclient, mount.cifs, or GUI file managers (e.g., Nautilus, Dolphin).
Include examples of mounting the SMB volume from Linux, with sample mount commands and troubleshooting tips.
Mention Linux equivalents for tasks like viewing shares (e.g., smbclient -L), modifying permissions (e.g., setfacl, or using smbclient's 'chmod' and 'chown' commands where supported).
Clarify that SMB volumes can be accessed and managed from both Windows and Linux clients, and provide links to relevant Linux documentation.
Avoid assuming Windows as the only or primary environment by rephrasing sections to be platform-neutral where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All operational steps and verification commands are presented exclusively for Windows environments, specifically referencing Windows systems and PowerShell commands. There are no examples or guidance for Linux or macOS clients, nor is there mention of how to verify or interact with SMB CA from non-Windows platforms.

Recommendations:

Add equivalent instructions for Linux clients, including how to remount SMB shares after enabling CA and how to verify CA status using Linux tools (e.g., 'smbstatus', 'mount', or 'smbclient').
Mention that SMB CA is a Windows-centric feature but clarify any relevant behaviors or limitations for Linux/macOS clients.
Provide command-line examples for Linux (and optionally macOS) environments, or explicitly state if verification is not possible or not supported from those platforms.
Avoid assuming all users are on Windows; update language to be inclusive of cross-platform scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias: all command-line examples use Windows PowerShell cmdlets (e.g., Get-SmbClientNetworkInterface, set-SmbClientConfiguration), and only Windows tools (Performance Monitor, Hyper-V adapters) are referenced for monitoring and configuration. There are no Linux or macOS SMB client examples, nor is there any mention of how to achieve similar monitoring or tuning on non-Windows platforms. References and links are exclusively to Windows documentation, and Windows terminology is used throughout.

Recommendations:

Include equivalent Linux (e.g., smbclient, mount.cifs, smbstatus, /proc/fs/cifs) and macOS (mount_smbfs, system profiler) commands and examples for all configuration and monitoring steps.
When referencing tools like Performance Monitor or PowerShell cmdlets, also mention and provide examples for open-source or cross-platform alternatives (e.g., iostat, iftop, netstat, atop, nload, or perf tools on Linux).
Add a section or callouts for Linux and macOS SMB client tuning, including sysctl parameters, mount options, and relevant kernel modules.
When describing SMB features (Multichannel, Signing, Encryption), clarify support and configuration steps for non-Windows clients, including any limitations or differences.
Provide links to official Samba and Linux SMB client documentation alongside Windows references.
Avoid assuming the reader is using Windows by default; use neutral language and structure sections to address all major platforms equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by mentioning Windows tools (robocopy) alongside Linux tools (rsync), but consistently lists the Windows tool second. There is a slight preference for Windows terminology and tools, and the only SMB example given is robocopy, which is Windows-specific. There are no explicit Linux SMB examples (such as smbclient or Linux mount/cp commands), and no PowerShell or command-line examples are provided, but the tool recommendations lean toward Windows environments for SMB.

Recommendations:

Provide explicit Linux-based SMB migration examples (e.g., using smbclient, mount.cifs with cp/rsync, or other Linux-native tools).
When listing tools, alternate the order or group by protocol rather than platform, or explicitly state parity (e.g., 'For NFS, use rsync (Linux/macOS) or robocopy (Windows); for SMB, use robocopy (Windows) or smbclient (Linux)').
Include example commands for both Windows and Linux environments for each protocol (NFS and SMB).
Mention cross-platform tools (e.g., rclone, or third-party migration tools that run on both OSes) where appropriate.
Clarify that migration can be performed from both Windows and Linux clients, and provide links to relevant documentation for both.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by requiring the use of PowerShell commands (Set-ADComputer) and referencing Windows-specific tools (RSAT) for critical configuration steps, such as setting Kerberos encryption types on Active Directory computer accounts. These steps are presented without Linux or cross-platform alternatives, and the Windows/PowerShell approach is described first and exclusively, even though the NFS client is Linux-based.

Recommendations:

Provide equivalent instructions for setting Kerberos encryption types using Linux-based tools such as 'ldapmodify', 'adcli', or 'samba-tool', for environments where administrators do not have access to Windows or PowerShell.
Include examples of how to perform Active Directory-related tasks from a Linux host, especially since the NFS client is Linux.
Clearly indicate whether the PowerShell/RSAT steps are mandatory or if there are alternative approaches for non-Windows environments.
Consider restructuring the documentation to present both Windows and Linux methods side by side, or at least mention Linux alternatives where only Windows tools are referenced.
Add a note or section addressing cross-platform administration scenarios, acknowledging that not all environments will have Windows domain controllers or administrators with Windows access.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively discusses SMB file permissions in the context of NTFS ACLs, referencing only Microsoft/Windows concepts and documentation. There are no examples or mentions of Linux tools, commands, or perspectives for managing SMB permissions, nor is there guidance for Linux administrators.

Recommendations:

Include examples of managing SMB/NTFS permissions from Linux clients, such as using the 'smbcacls' or 'setfacl' tools where applicable.
Reference Linux documentation or community resources for interacting with SMB shares and NTFS ACLs.
Clarify whether and how Linux clients can view or modify SMB permissions on Azure NetApp Files, and provide guidance if there are limitations.
Present both Windows and Linux approaches in parallel, or at least acknowledge Linux scenarios and provide links to further information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by referencing Windows file paths (e.g., c:\Templates\...), using PowerShell examples and terminology first, and not providing explicit Linux/macOS path or shell examples. Directory creation and file path instructions assume a Windows environment, and there are no explicit Linux/macOS equivalents or notes for cross-platform users.

Recommendations:

Provide Linux/macOS file path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
When instructing users to create directories, include both Windows (File Explorer, Command Prompt, PowerShell) and Linux/macOS (mkdir command) instructions.
Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
Add explicit notes or callouts for cross-platform compatibility, clarifying that all commands and templates work on Linux/macOS as well as Windows.
Where variable assignment or scripting differs between Windows (PowerShell) and Linux/macOS (bash), provide both syntaxes.
Avoid assuming the user's environment; use neutral language such as "your local computer" and provide both Windows and Linux/macOS context where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by consistently mentioning SMB (a Windows protocol) before NFS (a Linux/UNIX protocol) in several sections, and by providing more detailed explanations for Windows/SMB features such as ACLs and permission inheritance. Integration with Active Directory (a Windows-centric directory service) is highlighted as the only supported LDAP service, with no mention of alternatives or Linux-based directory services. There are no command-line examples or configuration snippets for either platform, but the text assumes familiarity with Windows tools and patterns, while Linux/UNIX equivalents are less emphasized or described in less detail.

Recommendations:

Alternate the order of SMB and NFS discussions to avoid always placing Windows protocols first.
Provide equal depth and detail for NFS (Linux/UNIX) features, including advanced NFSv4.x ACLs and Linux-based permission management.
Include practical configuration examples for both Windows (PowerShell, GUI) and Linux (command-line, shell scripts) environments.
Mention or acknowledge Linux-based directory services (such as OpenLDAP) even if not currently supported, and clarify roadmap or alternatives.
Ensure that terminology and explanations are balanced, avoiding the assumption that Active Directory or Windows ACLs are the default or only approach.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI (which is most commonly used on Windows), mentioning Windows Communication Foundation (WCF) relays (a Windows-centric technology), and omitting any command-line or scripting examples (such as Azure CLI, PowerShell, or Bash) that would be relevant for Linux users. There are no Linux-specific instructions or parity in tooling or workflow.

Recommendations:

Add Azure CLI examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
Include PowerShell examples as an alternative, but ensure CLI/Bash examples are presented first or alongside PowerShell.
Mention that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line tools.
Clarify that WCF relays are a Windows-specific technology and suggest alternatives or note limitations for Linux users.
Provide guidance for editing JSON templates using common Linux text editors (e.g., vim, nano) in addition to generic 'editor of your choice'.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell commands and update instructions before or instead of equivalent Linux/Azure CLI examples. PowerShell (a Windows-centric tool) is mentioned and exemplified in detail, while Azure CLI (cross-platform) is referenced but not exemplified. There are no explicit Linux shell or Bash examples, and the PowerShell module update process is described in more detail than the Azure CLI update process.

Recommendations:

Provide explicit Azure CLI command examples alongside PowerShell examples for all operations, especially for feature registration and status checking.
Include Linux/Bash-specific instructions for updating Azure CLI and using CLI commands.
When listing prerequisites or steps, present Azure CLI (cross-platform) instructions before or alongside PowerShell (Windows-centric) instructions to avoid a 'Windows-first' impression.
Ensure that all command-line examples are provided in both PowerShell and Bash/Azure CLI syntax, with clear labels for each.
Consider adding a table or section comparing PowerShell and Azure CLI commands for common tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by frequently referencing Windows tools and concepts (such as NTFS, Windows RPC, and Active Directory) before or more prominently than their Linux/NFS equivalents. There are no practical Linux/NFS command examples (e.g., no explicit 'chmod' or 'chown' usage shown), and management tools for NFS/UNIX permissions are only briefly mentioned (e.g., nfs4_getfacl/nfs4_setfacl) without examples. The documentation assumes familiarity with Windows-centric identity and permission management, and Linux/NFS scenarios are less detailed.

Recommendations:

Provide practical Linux/NFS examples (e.g., show how to use chmod, chown, nfs4_getfacl, nfs4_setfacl for managing permissions).
Balance the order of presentation so that Linux/NFS tools and workflows are described alongside or before Windows/SMB equivalents where appropriate.
Include explicit Linux/NFS troubleshooting scenarios and command-line outputs, similar to the detail given for Windows/SMB/NTFS.
Expand on NFS/UNIX identity management, including example LDAP configurations and group mapping for Linux environments.
Add diagrams or workflows that illustrate both Windows and Linux client interactions with Azure NetApp Files.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by exclusively referencing Microsoft Active Directory as the only supported LDAP server, focusing on AD DS and Microsoft Entra Domain Services. It describes LDAP security and schema extensions primarily in the context of Windows tools and features (e.g., Identity Management for UNIX, Service for UNIX, Centrify). The only concrete example for querying LDAP SRV records uses Windows nslookup syntax, with a brief mention of the Linux dig command but no example. There are no Linux/OpenLDAP-specific instructions, examples, or parity in tool usage, and the documentation repeatedly positions Windows/Active Directory as the default or only scenario.

Recommendations:

Provide equivalent Linux/OpenLDAP examples where possible, such as showing how to query LDAP SRV records using the dig command with a full example.
Clarify early in the documentation that only Microsoft Active Directory is supported, but also acknowledge common Linux LDAP servers (e.g., OpenLDAP) and explain any limitations or roadmap for support.
When discussing LDAP schema extensions, mention Linux/UNIX approaches (such as using RFC 2307 attributes in OpenLDAP) and how they compare to Windows extensions.
Include examples or notes for Linux administrators, such as how to configure LDAP clients on Linux to work with Azure NetApp Files, even if only Active Directory is supported.
Balance the discussion of tools and terminology by not assuming a Windows-centric environment; reference both Windows and Linux tools and patterns where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration, with Azure CLI (cross-platform) commands only mentioned secondarily in text and not shown as code blocks. There are no explicit Linux/CLI examples or screenshots, and the UI instructions reference right-click actions, which are more typical of Windows environments. No Linux-specific tools or workflows are discussed.

Recommendations:

Provide Azure CLI command examples in code blocks alongside PowerShell, not just as a mention in text.
Include explicit Linux/macOS instructions or notes where workflows may differ (e.g., right-click actions in the Azure Portal).
Ensure screenshots and UI instructions are platform-neutral or clarify that the steps apply equally across OSes.
Where possible, add Bash shell examples for scripting or automation tasks.
Review for any terminology or workflow that assumes a Windows environment and generalize for cross-platform users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references Azure CLI/PowerShell scripts as a primary automation method, with PowerShell mentioned alongside Azure CLI but without explicit mention of Bash or Linux shell scripting. The use of Windows-style environment variables (e.g., %HOME%\site) in the persisted local storage section further centers Windows conventions. There are no explicit Linux or Bash examples, and Linux-specific patterns are only briefly referenced (e.g., 'Apps running on Linux might be using an explicitly mounted share'), but not elaborated with examples or parity in instructions.

Recommendations:

When mentioning automation, explicitly list Bash or Linux shell scripting alongside Azure CLI and PowerShell, and provide equivalent Bash examples.
In sections referencing environment variables or file paths, provide both Windows (%HOME%\site) and Linux ($HOME/site) formats.
Where PowerShell is mentioned, ensure that Azure CLI examples are shown in Bash syntax as well, and clarify that Azure CLI is cross-platform.
Expand on Linux-specific scenarios, such as mounting file shares, with concrete examples or links to relevant documentation.
Review for other subtle Windows-first language or patterns and ensure Linux users are equally addressed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All examples, tools, and troubleshooting steps reference Windows environments, utilities, and protocols (e.g., MMC, Active Directory Users and Computers, Windows Server DFS, Windows clock sync, Windows Update). There are no Linux or cross-platform examples, nor is there mention of how to interact with Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or Samba). The documentation assumes the reader is using Windows or Windows Server, omitting guidance for Linux administrators.

Recommendations:

Add examples and troubleshooting steps for accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or gvfs).
Include Linux equivalents for Windows tools mentioned (e.g., how to view share/session/open files using smbstatus or similar).
When discussing Active Directory integration, mention how to join Linux clients to AD domains and access SMB shares securely.
Provide parity in configuration and troubleshooting guidance for both Windows and Linux environments.
Avoid assuming the administrator is always using Windows; clarify when a step is Windows-specific and offer alternatives for other platforms.
Reference relevant Linux documentation or man pages where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by presenting Windows/Powershell examples and instructions first, providing detailed step-by-step instructions for setting SACLs via the Windows GUI, and referencing Windows tools (e.g., robocopy) without Linux equivalents. There are no equivalent step-by-step instructions or command-line examples for Linux users, especially for setting Audit ACEs on NFSv4.1 shares. The registration section also prioritizes Azure PowerShell, with only a brief mention of Azure CLI. This may hinder Linux administrators from easily following the documentation.

Recommendations:

Provide equivalent step-by-step instructions for setting Audit ACEs on NFSv4.1 shares from a Linux client, including example commands (e.g., using nfs4_setfacl).
Include Linux command-line examples for relevant operations, such as registering the feature with Azure CLI, alongside or before PowerShell examples.
Mention Linux tools (e.g., rsync) alongside Windows tools like robocopy when discussing migration scenarios.
Ensure that instructions and screenshots are balanced between Windows and Linux environments, or provide tabs for each platform where applicable.
Clarify in each section which steps are for Windows and which are for Linux, and avoid assuming a Windows administration host as the default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows/Active Directory bias. All configuration and indexing examples are exclusively based on Microsoft Active Directory, with detailed instructions and screenshots for Windows tools (ADSI Edit). There are no examples or guidance for equivalent LDAP schema/indexing management on Linux-based LDAP servers (such as OpenLDAP). The terminology and attribute mapping tables are also oriented toward Active Directory defaults, and Linux/UNIX LDAP server administration is not addressed.

Recommendations:

Add equivalent examples and instructions for managing LDAP schemas and attribute indexing in common Linux LDAP servers (e.g., OpenLDAP), including command-line and configuration file methods.
Provide screenshots or code snippets for Linux tools (such as ldapmodify, slapd.conf, or LDIF files) to illustrate how to index attributes like uid and uidNumber.
Reorganize sections to present both Windows and Linux approaches in parallel, or clearly indicate when content is specific to Active Directory.
Expand the attribute mapping table to clarify which attributes are standard across LDAP implementations and which are specific to Active Directory.
Include a section discussing differences and best practices for both Windows and Linux LDAP environments, especially for organizations using non-AD LDAP servers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. When listing tools for snapshot management, PowerShell is mentioned alongside Azure CLI, REST API, and the Azure portal, but no Linux-specific command-line examples (such as Bash scripts or Linux-native tools) are provided. PowerShell is referenced explicitly, and there are no Linux shell or scripting examples. The documentation does not provide example commands for Linux environments, nor does it mention Linux-first tooling or patterns. While the documentation is generally platform-neutral in its conceptual explanations, the practical guidance and tool references lean toward Windows/PowerShell, and Linux parity is not fully achieved.

Recommendations:

Include explicit Linux/Bash command-line examples for snapshot management using Azure CLI.
When listing tools, mention Azure CLI and Bash scripting before or alongside PowerShell, to avoid Windows-first ordering.
Provide example scripts for both PowerShell (Windows) and Bash (Linux/macOS) in the 'Scripts' section.
Clarify that Azure CLI is cross-platform and provide usage examples on Linux.
Where PowerShell modules are referenced, also reference equivalent Bash/CLI usage or scripts.
Consider adding a section or callout for Linux administrators, highlighting relevant tools and patterns.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and security features (such as Group Policy, registry settings, and Windows Server advisories), and omitting Linux/NFS client configuration examples or tools. SMB encryption and UNC hardening are discussed in detail before NFS/Kerberos, and LDAP security is explained mainly in the context of Microsoft Active Directory, with configuration guidance focused on Windows environments. There are no Linux or cross-platform command-line examples or references to common Linux tools for configuring or verifying encryption.

Recommendations:

Provide parallel Linux/NFS client configuration examples for enabling and verifying Kerberos encryption, including example commands (e.g., mount options, krb5.conf settings).
Include references to Linux tools (such as kinit, mount.nfs, or sssd) and describe how to configure NFS and LDAP encryption from Linux clients.
When discussing LDAP signing and channel binding, add guidance for configuring these features on non-Windows LDAP servers (such as OpenLDAP) and clients.
Balance the order of presentation so that NFS/Linux scenarios are given equal prominence to SMB/Windows scenarios.
Add troubleshooting and verification steps for both Windows and Linux clients (e.g., using tcpdump or Wireshark on Linux to inspect encrypted traffic).
Reference relevant Linux documentation or man pages alongside Microsoft/Windows links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, Notepad, Notepad++, Windows Terminal) and workflows are often mentioned first or in greater detail than their Linux equivalents. Several sections provide detailed PowerShell and Windows-specific instructions or screenshots, while Linux tools and commands are sometimes mentioned only later or in passing. Some encoding conversion and file inspection examples are Windows-centric, with Linux alternatives appearing as secondary notes. There are also cases where Windows-specific troubleshooting steps are detailed, but equivalent Linux troubleshooting is not provided.

Recommendations:

Ensure Linux and macOS examples are presented alongside Windows examples, not just as afterthoughts.
When introducing tools or workflows (e.g., file encoding inspection, font settings), provide Linux-native equivalents (e.g., 'file', 'iconv', 'locale', terminal font configuration) with equal detail and screenshots.
Balance the order of presentation: alternate between Windows and Linux examples, or group by OS rather than consistently leading with Windows.
Expand troubleshooting and configuration guidance for Linux clients (e.g., how to adjust terminal fonts, locale settings, or encoding in GNOME Terminal, Konsole, or iTerm2).
Where PowerShell or CMD commands are given, provide equivalent bash/zsh commands for Linux/macOS.
Include more Linux/macOS screenshots to match the number and detail of Windows screenshots.
Explicitly mention macOS where relevant, especially since it is a common SMB/NFS client.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a PowerShell example for URL encoding but omits equivalent Linux/macOS (e.g., Bash) command-line examples. This creates a bias toward Windows users and assumes familiarity with Windows tools, while not addressing how Linux users can perform the same task.

Recommendations:

Add a Bash example for URL encoding, such as using `python3 -c 'import urllib.parse, sys; print(urllib.parse.quote(sys.argv[1]))' "$url"` or `jq -sRr @uri <<< "$url"`.
Explicitly mention that the PowerShell example is for Windows and provide parity for Linux/macOS users.
Review the documentation for other places where only Windows tools or workflows are referenced, and ensure Linux alternatives are included.
Consider a short section or callout box that summarizes cross-platform options for common tasks like URL encoding.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-centric bias by focusing primarily on Windows tools and patterns for Active Directory Domain Services (AD DS) site design. Windows terminology and utilities (such as Active Directory Sites and Services, nslookup, and references to Windows Server documentation) are used exclusively, with no equivalent Linux tooling or procedures provided. While Linux clients are mentioned in the context of Kerberos authentication, there are no Linux-specific configuration examples, tools, or troubleshooting steps. The documentation assumes the use of Windows-based management tools and does not address how to perform equivalent tasks from Linux environments.

Recommendations:

Provide Linux-based examples for verifying DNS SRV records (e.g., using dig or host commands) alongside nslookup.
Include instructions or references for managing AD DS site and subnet assignments using cross-platform tools or via command-line interfaces (such as PowerShell Core on Linux, or relevant LDAP tools).
Offer guidance for Linux administrators on integrating with AD DS, including troubleshooting connectivity and authentication from Linux clients.
Reference open-source or cross-platform alternatives for AD DS management where possible, or clarify which steps require Windows-only tools.
Balance the order of presentation so that Linux and Windows scenarios are treated equally, especially in authentication and connectivity sections.

Create pull request

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 authentication methods, listing Azure PowerShell before other options, and not providing any Linux- or macOS-specific guidance or examples. There are no examples or notes about using Bicep or related tools on Linux, nor is there mention of cross-platform differences or considerations.

Recommendations:

Include explicit examples and notes for Linux and macOS users, such as how to authenticate using Azure CLI on those platforms.
Avoid listing Azure PowerShell before Azure CLI or at least clarify that both are cross-platform, but PowerShell is more Windows-centric.
Mention that Azure CLI is fully supported on Linux and macOS, and provide links or notes for installing and using it on those systems.
Add a section or callout about cross-platform compatibility, especially for authentication and environment setup.
Where credential types are listed, clarify which are available or recommended for Linux/macOS users (e.g., Azure CLI, Environment, Managed Identity).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides deployment guidance and troubleshooting specifically referencing Azure PowerShell cmdlets (e.g., New-AzDeployment), which are primarily Windows-centric tools. There are no examples or mentions of equivalent Linux/CLI tools (such as Azure CLI), and the only deployment scenario discussed is via PowerShell. This creates a bias towards Windows users and omits guidance for those using Linux or cross-platform environments.

Recommendations:

Include equivalent Azure CLI (az deployment ...) examples and notes alongside PowerShell examples.
Mention that Azure CLI is cross-platform and provide guidance for both PowerShell and CLI users.
If discussing parameter name conflicts, explain whether similar issues exist with Azure CLI commands and how to resolve them.
Reorder or parallelize examples so that Windows and Linux/cross-platform tools are given equal prominence.
Add a note clarifying that the guidance applies to both PowerShell and CLI users, and link to relevant documentation for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows-centric bias in several ways: it references Windows tools, protocols, and behaviors extensively (e.g., NTFS, Hyper-V, MS SQL Server, Windows Indexing Service, LMHOSTS, FSCTL codes, and Windows-specific features like Offline Files and Previous Versions). Windows terminology and tools are mentioned first or exclusively, while Linux or macOS equivalents are rarely referenced or are only mentioned in passing (e.g., UNIX extensions, dual protocol, or POSIX/UNIX security). There are no Linux or macOS-specific configuration examples, troubleshooting tips, or usage scenarios, and the documentation assumes familiarity with Windows administration concepts.

Recommendations:

Add Linux/macOS client configuration and usage examples for connecting to SMB shares hosted on Azure NetApp Files.
Include references to Linux tools (e.g., smbclient, mount.cifs) and describe how to mount and interact with SMB shares from non-Windows systems.
Document differences in behavior between Windows and Linux/macOS clients, especially regarding permissions, symlinks, and file deletion semantics.
Provide troubleshooting guidance for common issues encountered by Linux/macOS clients (e.g., authentication, encryption, protocol compatibility).
Balance references to Windows-specific features with equivalent or alternative workflows for Linux/macOS environments where possible.
Clarify when features or behaviors are Windows-only and suggest alternatives or workarounds for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows and PowerShell environments. PowerShell is heavily featured in both script examples and deployment steps, with PowerShell-based commands provided first and in more detail. Uploading scripts to Azure Storage is only shown with PowerShell, and Docker volume mount examples use Windows drive letter syntax (e.g., d:/docker), with no corresponding Linux/macOS examples. There are no Bash/Azure CLI examples for uploading files or running deployments from non-Windows systems, and the file path conventions are Windows-centric.

Recommendations:

Provide equivalent Bash/Azure CLI examples for uploading deployment scripts to Azure Storage, especially for Linux/macOS users.
Include Docker run examples using Linux/macOS path syntax (e.g., /home/user/docker:/data) alongside Windows examples.
When presenting PowerShell and CLI examples, alternate the order or present both together to avoid a 'Windows-first' impression.
Clarify in each section that the instructions apply to all platforms, and explicitly mention any differences or additional steps for Linux/macOS.
Where possible, use platform-neutral language and file path conventions, or provide both Windows and Linux/macOS variants.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-only application, and all instructions are given through its GUI. There are no examples or mentions of Linux tools, command-line alternatives, or cross-platform considerations. The documentation assumes a Windows environment throughout.

Recommendations:

Clarify early in the documentation that MABS is a Windows-only product, if that is the case, to set expectations for Linux users.
If any telemetry management is possible via command-line (e.g., PowerShell), provide those commands and note their platform compatibility.
If there are equivalent Azure Backup solutions or telemetry management options for Linux servers, link to those or provide a brief mention.
Explicitly state the platform requirements and limitations to avoid confusion for non-Windows administrators.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation presents Azure PowerShell (which is Windows-centric) examples before Azure CLI in each code section, and consistently refers to Visual Studio Code as the editor, which is more commonly associated with Windows workflows. The PowerShell examples use Windows-specific concepts like splatting, and the instructions for opening a terminal default to PowerShell first, with Bash (and Git Bash) as a secondary note. There are no explicit Linux-only examples or Linux-specific tooling mentioned, and the documentation does not address platform-specific nuances for Linux users.

Recommendations:

Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first, as it is cross-platform and more commonly used on Linux.
Explicitly mention that Visual Studio Code and all tools are available on Linux, and provide links or notes for Linux installation where relevant.
Instruct users to open a Bash terminal (or their preferred shell) first, not just PowerShell, and clarify that all steps work on Linux/macOS as well as Windows.
Add troubleshooting notes or tips for Linux users where file paths, permissions, or shell behavior may differ.
Where PowerShell-specific features (like splatting) are used, briefly explain or provide equivalent Bash/CLI idioms.
Consider including at least one example using native Linux tools (e.g., zip/unzip commands, or using the Azure CLI from a Linux shell) to demonstrate parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows development environments. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. The tutorial relies on .NET Framework (not .NET Core/.NET 5+), WCF, and Windows-specific tooling and patterns. There are no instructions or code samples for Linux users, nor any guidance on using cross-platform tools or editors.

Recommendations:

Provide equivalent instructions for setting up the development environment on Linux, including using Visual Studio Code or JetBrains Rider, and installing the Azure SDK for .NET on Linux.
Include examples using .NET Core or .NET 5+ (which are cross-platform), rather than only .NET Framework.
Offer guidance on running and debugging the sample applications on Linux (e.g., using the dotnet CLI, configuring launch.json in VS Code).
If WCF is required, clarify its Windows-only limitations and suggest alternatives for Linux (such as gRPC or REST APIs with ASP.NET Core).
Mention and provide examples for using Azure CLI (which is cross-platform) instead of only GUI-based steps in Visual Studio.
Explicitly state the platform requirements and, if Windows is required, explain why and what Linux/macOS users can do as alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. PowerShell examples are given their own section, and Visual Studio Code (a Microsoft tool) is emphasized for decompilation and editing. In the export section, Azure CLI (cross-platform) is shown first, but Azure PowerShell (Windows-centric) is also highlighted, and Visual Studio Code features are referenced throughout. There are no explicit Linux/macOS shell examples (e.g., bash), and no mention of Linux-specific editors or workflows.

Recommendations:

Add explicit bash or shell examples for Linux/macOS users, especially in sections showing command-line usage (e.g., show 'cat' or 'less' for file viewing, or use 'mv' for renaming).
Balance the editor/tooling recommendations by mentioning cross-platform editors such as VS Code (already present) and alternatives like Vim or nano for basic edits.
Clarify that PowerShell examples can be run on Windows, macOS, and Linux (since PowerShell Core is cross-platform), or provide bash equivalents.
Where Visual Studio Code is referenced, note that it is available on all major platforms.
Consider adding a short section or callout for Linux/macOS users, summarizing any differences or confirming parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page provides a detailed overview of Bicep file functions but demonstrates bias by only including a PowerShell script example (myscript.ps1) in the 'loadTextContent' section. There are no examples for Linux shell scripts (e.g., .sh files) or references to Linux scripting environments. The deployment script resource uses 'AzurePowerShell' exclusively, with no mention of 'AzureCLI' or cross-platform alternatives. No Linux or cross-platform command-line usage is shown.

Recommendations:

Include examples that demonstrate loading and deploying Linux shell scripts (e.g., myscript.sh) using the same Bicep functions.
Show how to use the 'AzureCLI' deployment script kind in addition to 'AzurePowerShell', with corresponding examples.
Explicitly mention that the file functions work with both Windows and Linux file types and encodings.
Where possible, provide parallel examples for both Windows (PowerShell) and Linux (Bash) script scenarios.
Clarify that the Bicep CLI and file functions are cross-platform, and reference any platform-specific considerations if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for obtaining access tokens and making REST API calls. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as deploying resources with templates), only PowerShell is referenced for further reading. There is no explicit mention or example of Linux-native tools or workflows beyond the CLI/cURL, and PowerShell is not clearly marked as Windows-specific, which may confuse Linux users. References to Visual Studio Code and PowerShell for template deployment further reinforce a Windows-centric perspective.

Recommendations:

Clearly indicate that Azure PowerShell examples are primarily for Windows or explain cross-platform availability.
Provide explicit bash or shell script examples for Linux users alongside PowerShell, especially for multi-step workflows.
When referencing further documentation (such as deploying templates), include links to both PowerShell and CLI/Linux-native guides.
Avoid referencing Visual Studio Code as the only editor for template creation; mention alternatives or note its cross-platform support.
Ensure that CLI examples are always presented first or in parallel with PowerShell to avoid a Windows-first impression.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows and PowerShell bias. All scripting examples use PowerShell (.ps1) scripts, and the only script-based deployment method shown is via Azure PowerShell. The 'Copy and deploy' task examples use the 'windows-latest' agent pool, and there is no mention or example of using Bash, Linux agents, or cross-platform scripting. Windows tools and patterns (such as Visual Studio project scripts and PowerShell) are referenced exclusively or before any Linux alternatives, with no Linux/Unix shell or CLI equivalents provided.

Recommendations:

Provide equivalent Bash or Azure CLI examples for deploying ARM templates, especially for users on Linux or macOS.
Demonstrate the use of 'ubuntu-latest' or other Linux agent pools in the 'Copy and deploy' section, not just in the PowerShell example.
Reference cross-platform tools (e.g., AzCopy, Azure CLI) and show how to use them in YAML pipelines, including sample scripts.
Mention and link to documentation for running scripts on Linux/macOS agents, and clarify any differences or limitations.
Balance references to Visual Studio and PowerShell with alternatives like VS Code and Bash/Azure CLI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell alongside Azure CLI when discussing export options, and by listing PowerShell before REST API in the 'Next steps' section. There are no explicit Linux-specific instructions or examples, and the mention of PowerShell may suggest a preference for Windows tooling. However, Azure CLI is mentioned, which is cross-platform, but Linux-specific workflows or screenshots are absent.

Recommendations:

Ensure that Azure CLI (which is cross-platform) is mentioned before Azure PowerShell in all lists and examples, as it is more relevant for Linux users.
Add explicit notes or examples for Linux/macOS users, such as CLI commands in a Bash shell, or clarify that the Azure CLI instructions apply equally to Linux, macOS, and Windows.
Include screenshots or terminal snippets from Linux environments where possible, or at least mention that the steps are platform-agnostic.
Avoid listing Windows-specific tools (like PowerShell) before cross-platform alternatives unless there is a technical reason.
Consider adding a section or note that highlights parity between platforms and reassures users that all steps can be performed on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it states that both Azure CLI (Linux) and Azure PowerShell scripts are supported, examples and instructions often present PowerShell/Windows-centric approaches first or exclusively. Script deployment and management examples frequently use Azure PowerShell, and there are no explicit Linux shell (e.g., Bash) deployment commands for deploying Bicep files, only PowerShell. Additionally, some instructions and tool references (e.g., use of PowerShell cmdlets, ARMClient in PowerShell) assume a Windows environment, and there is a lack of parity in showing how to perform equivalent actions from a Linux shell.

Recommendations:

Provide Linux shell (Bash) equivalents for all PowerShell deployment and management examples, especially for deploying Bicep files and interacting with the REST API.
When listing Azure CLI and PowerShell tabs, alternate the order or present CLI (cross-platform) first to avoid implicit prioritization of Windows tools.
Explicitly mention that Azure CLI commands can be run from any platform, and provide sample Bash scripts for common tasks (e.g., resource group creation, Bicep deployment).
Where ARMClient or other Windows-specific tools are referenced, suggest cross-platform alternatives or show equivalent curl/az CLI REST calls.
Ensure that all code samples and walkthroughs are available in both PowerShell and Bash (or at least CLI) variants, and clarify any platform-specific requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all examples, regardless of shell. There are no Linux/macOS path examples or notes for cross-platform users. Additionally, references to Visual Studio Code and PowerShell are prominent, and the only role-based access control tutorial linked is for PowerShell. While Azure CLI is included (which is cross-platform), the lack of Linux/macOS-specific guidance and the default to Windows conventions may confuse or exclude non-Windows users.

Recommendations:

Provide both Windows (C:\path\to\file) and Linux/macOS (/home/user/path/to/file or ~/path/to/file) path examples in all command samples.
Add notes or tabs clarifying file path differences between platforms.
Include links to role-based access control tutorials for Azure CLI and/or portal, not just PowerShell.
Mention that Azure CLI and Bicep are cross-platform and provide installation/use guidance for Linux/macOS.
Where PowerShell is referenced, clarify that it is available on Linux/macOS, or provide Bash equivalents where appropriate.
Review all code snippets and instructions to ensure they are not Windows-centric by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing PowerShell-specific export instructions and linking to a PowerShell-centric guide for exporting blueprint definitions. There are no examples or guidance for performing equivalent tasks using cross-platform tools like Azure CLI or Bash, and the only command-line tooling mentioned for configuring DenySettingsMode is Azure PowerShell (with Azure CLI mentioned only as an alternative, but without examples). No Linux- or Bash-specific instructions or examples are provided.

Recommendations:

Include Azure CLI and Bash examples alongside or before PowerShell examples for all migration steps, especially for exporting blueprint definitions and configuring DenySettingsMode.
Update links to reference both PowerShell and Azure CLI documentation where available, or provide new cross-platform instructions if needed.
Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide parity in tooling guidance.
Add a sample workflow using Azure CLI for exporting blueprints and managing deployment stacks to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI (cross-platform) and PowerShell examples, but the PowerShell section relies on ARMClient, a Windows-centric tool, without mentioning Linux alternatives or cross-platform REST tools. There are no examples using Linux-native tools (such as curl or httpie) for REST operations, and the documentation assumes ARMClient is available, which is not the case on Linux. This creates a bias towards Windows environments and PowerShell users.

Recommendations:

For REST operations, provide examples using curl or httpie, which are available on Linux, macOS, and Windows. This ensures parity for Linux users.
Explicitly mention that ARMClient is primarily for Windows and suggest cross-platform alternatives for Linux/macOS users.
In the prerequisites, list Linux-compatible tools for REST calls, such as curl, httpie, or Postman CLI.
Where PowerShell examples are given, consider also providing Bash shell equivalents for Linux users, especially for variable assignment and command chaining.
Review the documentation for any assumptions about the user's OS and clarify when a tool or command is platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a subtle Windows bias in the 'Next steps' section, where Azure PowerShell and Visual Studio Code (a Microsoft product) are mentioned as primary tools for deploying and authoring Bicep files. Azure CLI is mentioned, but PowerShell is listed first, and there is no mention of Linux-native editors or deployment workflows. No explicit Linux examples or tools are highlighted, and the guidance assumes familiarity with Windows-centric tooling.

Recommendations:

List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is fully cross-platform.
Explicitly mention that all Bicep examples and deployment steps work on Linux, macOS, and Windows.
Include links or references to Linux-native editors (such as Vim, Emacs, or JetBrains IDEs) that support Bicep, if available.
Provide a brief example of deploying a Bicep file using Azure CLI from a Linux shell (e.g., Bash), to demonstrate parity.
Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but PowerShell is always presented as an equal alternative, not as a fallback. There is a reference to a Windows-specific scenario (WinRM on a Windows VM) in the introduction, and the PowerShell examples use Windows-style line continuations (backticks). There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, although it is now cross-platform. The ordering of examples sometimes places Azure CLI first, which is more cross-platform, but the presence of PowerShell throughout and the Windows VM reference indicate a mild Windows bias.

Recommendations:

Add explicit Bash shell examples alongside Azure CLI commands to demonstrate Linux parity, including line continuations and environment variable usage.
Avoid referencing Windows-specific scenarios (such as WinRM on a Windows VM) without also providing Linux equivalents or alternatives.
Clarify that Azure CLI commands are cross-platform and can be used on Windows, macOS, and Linux.
If PowerShell is included, note that it is available cross-platform, but consider adding Bash alternatives for users on Linux.
Ensure that any tool or pattern mentioned (such as PowerShell line continuations) is accompanied by the equivalent for Bash or other common Linux shells.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by focusing on deploying a Windows VM, referencing a Windows-specific Quickstart template, and instructing users to verify deployment via RDP (a Windows protocol). While both PowerShell and Bash/CLI deployment examples are provided, the template and post-deployment steps are Windows-centric, and there is no mention of Linux VM deployment or SSH access.

Recommendations:

Include a parallel example/template for deploying a Linux VM (e.g., link to or use the 'Deploy a simple Linux VM' Quickstart template).
Demonstrate how to connect to the deployed VM using SSH for Linux, alongside the RDP instructions for Windows.
When referencing Quickstart templates, mention both Windows and Linux options, or provide a choice at the start of the tutorial.
In post-deployment verification, show both RDP (for Windows) and SSH (for Linux) connection steps.
Ensure that examples and screenshots are balanced between Windows and Linux scenarios, or clearly state that the tutorial is Windows-specific if that is the intent.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page consistently references Windows Server Active Directory as the primary or only identity provider for user and group management in vCenter Server. There are no examples or mentions of Linux-based identity sources (such as OpenLDAP) or integration patterns, and Windows terminology and tools are presented exclusively.

Recommendations:

Include examples and guidance for integrating Linux-based identity sources, such as OpenLDAP, with vCenter Server.
Mention Linux equivalents alongside Windows Server Active Directory when discussing user and group management.
Provide parity in documentation by referencing both Windows and Linux identity management tools and patterns.
Clarify whether non-Windows identity sources are supported or not, and if so, provide configuration steps or references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. PowerShell examples and references are consistently presented before Azure CLI (cross-platform) examples. The use of PowerShell-specific cmdlets and terminology (e.g., Get-AzContainerRegistry, Publish-AzBicepModule) is prominent, and Windows paths are listed first in local cache examples. There is little to no mention of Linux-specific shell usage, and no explicit Linux shell (bash) or scripting examples are provided. The documentation assumes familiarity with Windows tools and patterns, with Linux and Mac paths only briefly mentioned.

Recommendations:

Alternate the order of examples so that Azure CLI (cross-platform) is presented before PowerShell, or present both side-by-side.
Include Linux/macOS shell (bash) examples where relevant, especially for scripting or automation scenarios.
Provide more detailed Linux and Mac path examples, matching the detail given for Windows.
Avoid Windows-centric terminology and tools as the default; clarify that PowerShell is available cross-platform, or provide bash equivalents.
Explicitly state that all Azure CLI commands work identically on Linux, macOS, and Windows, and consider adding notes or troubleshooting tips for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides detailed examples for both Azure CLI and Azure PowerShell, but the PowerShell section is prominent and detailed, reflecting a Windows-centric approach. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary automation tool, which is traditionally associated with Windows environments. The documentation does not mention or provide parity for Linux-native scripting or tooling beyond Azure CLI.

Recommendations:

Add explicit bash (Linux shell) examples alongside Azure CLI commands to demonstrate usage in Linux environments.
Clarify that Azure CLI commands work cross-platform and can be used in both Windows (cmd, PowerShell) and Linux (bash) shells.
If mentioning PowerShell, also mention that PowerShell Core is cross-platform, but provide bash alternatives for Linux users.
Ensure that any references to scripting or automation tools include Linux-native options, not just PowerShell.
Consider reordering sections so that cross-platform tools (Azure CLI, bash) are presented before Windows-specific tools (PowerShell).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides command-line examples only for Azure CLI and Azure PowerShell, both of which are available cross-platform but are traditionally associated with Windows environments. There are no explicit Linux shell (bash) examples, nor are there references to Linux-native tools or workflows. The tooling recommendations (Visual Studio, Visual Studio Code) are Windows-centric, with no mention of Linux editors or shell environments. PowerShell examples are given equal prominence to Azure CLI, and in some places, PowerShell is mentioned before Linux alternatives.

Recommendations:

Add explicit bash/zsh shell examples for all CLI commands, demonstrating usage in a typical Linux terminal environment.
Mention that Azure CLI is fully supported on Linux and macOS, and provide installation links for those platforms.
Include Linux-native editor recommendations (e.g., Vim, Emacs, nano) or at least acknowledge their use.
Clarify that PowerShell Core is cross-platform, but also show how to use CLI commands in bash scripts.
When referencing tools, avoid listing Windows tools (Visual Studio) before cross-platform or Linux-native options.
Add a section or callout for Linux/macOS users, highlighting any differences or tips for those environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows development environments. All examples and instructions assume the use of Visual Studio (a Windows-centric IDE), and there is no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', project creation, and configuration are described only for Visual Studio. There are no instructions or code samples for Linux users, nor any mention of .NET Core/.NET 5+ cross-platform capabilities or command-line alternatives (e.g., dotnet CLI). The use of Windows-specific tools and terminology (e.g., Solution Explorer, App.config, NuGet via Visual Studio UI) further reinforces the Windows bias.

Recommendations:

Add equivalent instructions for Linux and macOS environments, including how to use the dotnet CLI to create, build, and run projects.
Mention and provide examples using cross-platform editors such as VS Code.
Include steps for installing prerequisites (e.g., .NET SDK) on Linux and macOS.
Show how to manage NuGet packages via the command line (dotnet add package) instead of only through Visual Studio UI.
Clarify that WCF on .NET Core/.NET 5+ is limited (client-only), and suggest alternatives or workarounds for Linux users.
Avoid assuming the reader is using Windows or Visual Studio; provide generic instructions where possible.
If certain features are Windows-only, explicitly state this and provide guidance for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell tab is the only programmatic alternative to the Azure Portal, and all scripting and automation steps are shown using PowerShell cmdlets, which are most familiar to Windows users. There is no mention of Linux-native tools or workflows, and the documentation refers to PowerShell-specific migration guides. This may disadvantage users on Linux or macOS who prefer or require cross-platform tools.

Recommendations:

Add Azure CLI (az) examples alongside PowerShell for all command-line steps, including exporting, modifying, and deploying ARM templates.
Include Bash shell script examples where applicable, especially for template manipulation and deployment.
Reference cross-platform documentation and migration guides that use Azure CLI, not just PowerShell.
Ensure that tabs for command-line instructions are labeled as 'Azure CLI' and 'PowerShell', not just 'PowerShell', to encourage parity.
Review all links and references to ensure they do not exclusively point to PowerShell-based guides.
Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide any OS-specific notes if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. File path examples use Windows-style paths (e.g., c:\jsontemplates) without providing Linux equivalents. In sections discussing local cache locations, the Windows path is listed first, and the Linux/Mac examples are less detailed. The documentation references Azure PowerShell and Windows-specific patterns (such as named pipes with Windows syntax) before or instead of Linux alternatives. There are no explicit Linux shell (bash) command examples, and Linux file path conventions are not shown alongside Windows ones.

Recommendations:

For every file path example using Windows-style paths (e.g., c:\jsontemplates), provide a Linux/Mac equivalent (e.g., /home/user/jsontemplates) alongside or immediately after.
When listing cache or configuration file locations, present all platforms with equal detail and avoid always listing Windows first.
Where named pipes or other OS-specific features are discussed, present Linux/OSX and Windows examples together, and avoid putting Windows first.
Add bash/zsh shell command examples where only Azure CLI or PowerShell examples are shown, especially for common tasks.
Ensure that references to Azure PowerShell are balanced with references to bash or other cross-platform tools where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI, and the PowerShell examples use Windows file paths (e.g., c:\Templates\azuredeploy.json) without offering Linux/macOS equivalents. There is no explicit mention or example for Linux/macOS users regarding file paths or shell differences, and the CLI section only briefly notes that Bash syntax may differ in other environments without providing concrete Linux/macOS alternatives.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows prioritization.
For file paths, provide both Windows (e.g., c:\Templates\azuredeploy.json) and Linux/macOS (e.g., ~/Templates/azuredeploy.json) examples in relevant commands.
Explicitly mention and provide examples for Linux/macOS users, especially where shell syntax or environment variables differ (e.g., use $HOME or ~/ for paths, note differences in date command usage).
Clarify in the introductory text that both Windows and Linux/macOS are supported, and link to platform-specific guidance if available.
Where PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide Bash/zsh alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples (including advanced usage with -Debug), referencing a PowerShell script on GitHub, and presenting PowerShell before Azure CLI. While Azure CLI is included, there are no explicit Linux shell (bash/curl) or cross-platform REST API examples, and the scripting focus is on Windows-centric tools.

Recommendations:

Add equivalent Linux shell (bash/curl) examples for retrieving response headers, showing how to use curl or wget and jq to extract relevant header values.
Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform parity, as Azure CLI is available on all major OSes.
Include a REST API example using curl to demonstrate how to retrieve throttling headers in a platform-agnostic way.
Reference cross-platform scripting approaches (e.g., Python requests) for extracting headers, not just C# and PowerShell.
Ensure that all example links (such as the GitHub PowerShell script) are complemented by links to cross-platform or Linux-friendly scripts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In the 'Find resource provider' section, the PowerShell example is given immediately after the Azure CLI example, with no mention of Linux shell equivalents (such as Bash scripting or use of jq for output parsing). The PowerShell example assumes the use of Windows tooling. Additionally, the only OS-specific tool mentioned elsewhere is 'Azure Serial Console for Windows', and some resource providers reference Windows-specific services (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP), but there are no Linux-specific counterparts or examples. There are no Linux shell or scripting examples, and Windows tools are referenced before or instead of Linux alternatives.

Recommendations:

Add Linux shell (Bash) examples alongside PowerShell, especially for common tasks like listing resources.
When referencing OS-specific tools or services (e.g., Serial Console for Windows), provide parity by mentioning or linking to Linux equivalents (e.g., Serial Console for Linux).
Ensure that scripting examples (such as Python) are presented as cross-platform, and clarify that Azure CLI is available on all major platforms.
Where possible, balance the order of examples so that Windows and Linux users are equally represented (e.g., alternate the order of PowerShell and Bash examples, or present both together).
Explicitly mention when a tool or service is Windows-only, and provide guidance for Linux users if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Visual Studio and Visual Studio Code (both Windows-centric or Windows-first tools) as primary editors for ARM templates, and by providing guidance and screenshots for these tools exclusively. There are no examples or mentions of Linux-native editors or workflows (such as Vim, Emacs, nano, or Linux-specific VS Code usage). Additionally, the only explicit mention of deploying templates with multi-line strings refers to Azure PowerShell (Windows-first) and Azure CLI, but does not provide Linux-specific instructions or considerations. There are no Linux shell (bash) or cross-platform command-line examples, and the documentation does not acknowledge Linux users' needs for editor configuration or deployment nuances.

Recommendations:

Include examples and guidance for editing ARM templates using popular Linux editors (e.g., Vim, nano, Emacs) and how to enable JSONC or handle comments in those environments.
Add explicit instructions or screenshots for using Visual Studio Code on Linux, or mention that VS Code is cross-platform.
When discussing deployment via Azure CLI, clarify that the instructions apply equally to Linux, macOS, and Windows, and provide bash/zsh shell command examples where relevant.
Reference Linux-native tools and workflows where appropriate, such as using jq for JSON validation or manipulation.
Ensure that any references to PowerShell or Visual Studio are balanced with equivalent Linux-friendly alternatives (e.g., Azure CLI in bash, VS Code on Linux, or other editors).
Add a note that ARM template development and deployment is fully supported on Linux and macOS, not just Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows tools and patterns, such as Task Manager, Control Panel, and Windows file paths, without mentioning Linux equivalents or providing Linux-specific troubleshooting steps. There are no examples or instructions for users running Azure Backup on Linux systems.

Recommendations:

Include troubleshooting steps for Linux environments, such as using 'ps', 'systemctl', or 'journalctl' to check and manage the agent process.
Provide Linux file path examples for log locations (e.g., /var/opt/microsoft/azure-recoveryservices-agent/log/).
Mention both Windows and Linux agent process names and management commands.
Structure instructions so that both Windows and Linux users can easily find relevant guidance, possibly with separate sections or side-by-side examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), using Windows-centric terminology (such as Kudu and FTP credentials), and prioritizing PowerShell and portal-based workflows. There is a lack of explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tools or patterns. The only scripting example linked in 'Next steps' is PowerShell-based, and there are no Azure CLI or Bash examples provided.

Recommendations:

Provide equivalent Linux/Bash command-line examples alongside PowerShell, especially for backup/restore and resource creation.
Reference cross-platform tools (e.g., Azure CLI) before or alongside PowerShell in all procedural sections.
Replace or supplement Windows-specific paths (e.g., %HOME%\site) with their Linux equivalents (e.g., $HOME/site or /home/site) and clarify that these paths are platform-dependent.
Include links to Linux-friendly documentation (e.g., Azure CLI, Bash scripting) in the 'Next steps' section.
Mention and provide examples for using SFTP or other Linux-native file transfer methods where FTP/Kudu is referenced.
Ensure that all configuration and troubleshooting steps are platform-agnostic or provide both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions for the Azure Portal and Azure PowerShell, but does not include any examples or guidance for Linux users or cross-platform CLI tools such as Azure CLI. The PowerShell examples assume a Windows environment (e.g., use of 'notepad' for editing files), and there are no Bash or shell script equivalents. This creates a bias toward Windows and PowerShell users, leaving Linux and macOS users without parity in command-line instructions.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell steps, including exporting, editing, and deploying ARM templates.
Provide cross-platform file editing instructions (e.g., using 'vi', 'nano', or 'code' editors) instead of only 'notepad'.
Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify if the instructions are Windows-only.
Ensure that all command-line steps are presented for both PowerShell and Azure CLI, with clear tabs or sections for each.
Include notes or links for Linux/macOS users on how to perform each step, especially for file manipulation and command execution.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. In several sections, Windows-specific instructions or tools are mentioned before Linux equivalents, and examples (such as the script reference) are Azure PowerShell-centric. While Linux is referenced, it is often as an afterthought (e.g., 'On Linux VMs, refer to distributor guidance'), and there are no concrete Linux command-line examples or step-by-step instructions. The documentation also references Windows Update specifically, but for Linux, only generic advice is given. There are no Linux CLI or shell script examples for bulk operations, and the on-premises backup section implicitly assumes Windows (MARS agent), with no mention of Linux backup agents.

Recommendations:

Provide parallel Linux-focused examples and instructions wherever Windows-specific steps are given (e.g., include Bash/Azure CLI scripts alongside PowerShell).
When referencing OS-specific maintenance (like updating certificates), give concrete Linux commands or point to official distro documentation.
In bulk scripting examples, include both PowerShell and Bash/Azure CLI equivalents.
In on-premises backup sections, mention and link to Linux backup agent documentation if available, or clarify Windows-only applicability.
Avoid always listing Windows steps first; alternate or group by OS where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page references Azure PowerShell before Azure CLI and REST API when discussing version requirements for zero-count support, and the only explicit deployment guide linked in 'Next steps' is for Azure PowerShell. There are no Linux- or Bash-specific examples or deployment instructions, and the focus on PowerShell and Windows-centric tools may make Linux users feel secondary.

Recommendations:

List Azure CLI before Azure PowerShell when mentioning supported tools, or present them together to avoid implying a Windows-first approach.
In the 'Next steps' section, add links to deployment guides for Azure CLI and Bash, not just PowerShell.
Wherever deployment instructions are referenced, ensure parity by providing both CLI and PowerShell links/examples.
Explicitly mention that both Windows and Linux users can use Azure CLI, and provide Bash shell examples where relevant.
Review other linked articles (such as 'Deploy resources with ARM templates and Azure PowerShell') to ensure Linux/CLI parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and frequently references PowerShell scripts and usage patterns. There is no mention of Linux-specific tools, shells, or workflows, and the examples assume familiarity with PowerShell syntax and conventions. While Azure CLI is cross-platform, the documentation's ordering and emphasis on PowerShell may give the impression of a Windows-first or Windows-preferred environment.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to reflect its cross-platform nature.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands (e.g., bash) where appropriate.
Avoid language that implies PowerShell is the default or preferred tool; clarify that both PowerShell and CLI are supported equally.
Where scripting is discussed, provide both PowerShell and bash (or sh) script snippets to illustrate parity.
If referencing scripts or automation, mention both PowerShell scripts and shell scripts (bash/sh) as valid approaches.
Consider adding a brief section or note for Linux/macOS users highlighting any differences or confirming full support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for command-line operations, with no equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). All scripting and automation guidance is centered on PowerShell, and references to obtaining region codes or deploying resources are given exclusively with PowerShell commands. There is no mention of Bash, Linux shell, or Azure CLI alternatives, and the structure consistently presents PowerShell before or instead of any cross-platform tooling.

Recommendations:

Add Azure CLI examples alongside PowerShell for all command-line operations, including exporting, modifying, and deploying Resource Manager templates, as well as deleting resources.
Explicitly mention that AzCopy is cross-platform and provide example commands for both Windows and Linux/macOS shells.
Where PowerShell is referenced, provide equivalent Bash or shell script snippets for Linux users.
Instruct users on how to install and use Azure CLI on Linux/macOS, and link to relevant documentation.
Ensure that any references to tools or commands (such as obtaining region codes) include both PowerShell and Azure CLI methods.
Consider reordering sections or using tabs to present PowerShell and Azure CLI equally, rather than defaulting to PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation presents both Azure PowerShell (typically associated with Windows/PowerShell environments) and Azure CLI (cross-platform) examples in parallel, but consistently lists Azure PowerShell first in every code example section. Instructions for opening a terminal default to PowerShell (in VS Code) before mentioning Bash, and there is more detailed explanation of PowerShell-specific syntax (such as the backtick escape character) than for Bash. Visual Studio Code is listed as a prerequisite, which is cross-platform, but no mention is made of other editors or shells common on Linux. There are no outright missing Linux examples, but the ordering and depth of PowerShell coverage indicate a Windows-first bias.

Recommendations:

Alternate the order of Azure CLI and Azure PowerShell examples, or present Azure CLI first to better reflect cross-platform usage.
Ensure explanations of Bash/Linux shell syntax (such as escape characters and line continuation) are as detailed as those for PowerShell.
Explicitly mention that all CLI examples work on Linux, macOS, and Windows, and clarify that Bash is the default shell on Linux/macOS.
Consider referencing other popular Linux editors (e.g., nano, vim) or terminal environments in addition to Visual Studio Code.
Where possible, use neutral language (e.g., 'open a terminal') instead of 'open a PowerShell terminal', unless the example is PowerShell-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary management tools, without mentioning Linux-native alternatives (such as Azure CLI or Bash scripting). There are no Linux-specific examples or guidance, and Windows/PowerShell tools are mentioned first and exclusively.

Recommendations:

Include examples and references for managing API Management using Azure CLI and Bash, alongside PowerShell.
Explicitly mention that management can be performed from Linux, macOS, and Windows environments.
Provide sample commands or automation scripts for Linux users, ensuring parity with PowerShell examples.
Rephrase tool mentions to be platform-neutral (e.g., 'using Azure CLI, PowerShell, or the Azure portal').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently presents Azure PowerShell (which is most commonly used on Windows) before Azure CLI in all code example sections. It also assumes the use of Visual Studio Code and PowerShell terminals, both of which are more prevalent on Windows. There is a strong emphasis on PowerShell scripting patterns (e.g., splatting), and some instructions (such as opening a PowerShell terminal in VS Code) are Windows-centric. However, Azure CLI and Bash examples are provided throughout, and there are no outright missing Linux examples.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows preference.
Explicitly mention that Visual Studio Code, PowerShell, and Azure CLI are cross-platform, and provide guidance for Linux/macOS users (e.g., how to open a Bash terminal in VS Code on Linux).
Where PowerShell-specific features (like splatting) are discussed, consider providing equivalent Bash scripting tips for parity.
Add a brief note in the prerequisites that all tools and instructions apply equally to Windows, Linux, and macOS, and clarify any OS-specific steps.
When referencing terminal usage, include instructions for both PowerShell and Bash (or other common Linux shells) without assuming the user is on Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and PowerShell examples throughout, but PowerShell is featured equally and sometimes before CLI, and there is a notable focus on PowerShell (a Windows-centric tool). There are no Linux-specific shell examples (e.g., Bash), and references to Windows tools and patterns are present, such as the mention of a Windows-specific quickstart template for installing certificates. The documentation does not mention or demonstrate Linux-native scripting environments or workflows, and the PowerShell examples use Windows-style line continuations and variable syntax.

Recommendations:

Add explicit Bash shell examples alongside Azure CLI, demonstrating Linux-native workflows (e.g., using export for environment variables, Linux-style line continuations, and file paths).
When referencing quickstart templates or scenarios, provide both Windows and Linux equivalents (e.g., link to a Linux VM certificate install template as well as the Windows one).
Ensure that CLI examples use syntax and conventions that are platform-neutral or show both Windows and Linux variants where they differ.
Consider adding a section or callout for Linux users, highlighting any differences or best practices for Linux environments.
Review the order of examples to avoid always listing PowerShell before CLI, or alternate the order to avoid implicit prioritization of Windows tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric resources and tools before or instead of Linux equivalents. The only example template linked is for deploying a Windows VM with data disks, with no Linux VM example provided. Additionally, the 'Next steps' section directs users to a PowerShell deployment guide, with no mention of Azure CLI or Linux-specific deployment instructions. While Azure CLI is mentioned in passing regarding version requirements, practical examples and links are Windows/PowerShell-focused.

Recommendations:

Include example templates for both Windows and Linux VM deployments, or provide a generic example that is OS-agnostic.
In the 'Example templates' table, add a Linux VM example (e.g., a link to a quickstart template for Linux VMs with data disks).
In the 'Next steps' section, add links to deploying ARM templates using Azure CLI and Bash, not just PowerShell.
When mentioning deployment tools (Azure PowerShell, Azure CLI), present them in parallel and provide equal guidance/examples for both.
Ensure that any referenced quickstart templates or tutorials have both Windows and Linux variants, or clarify their applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias: the main template example is for a Windows VM, all deployment scripts are in PowerShell, and there are no equivalent Azure CLI (Bash) or Linux VM examples. The instructions and screenshots focus on Windows-centric tools and workflows, with Linux alternatives either missing or mentioned only in passing.

Recommendations:

Provide parallel examples for Linux VMs, including links to Linux-based Quickstart templates.
Include Azure CLI (az) commands for template deployment alongside PowerShell scripts.
Show both Bash and PowerShell usage in Cloud Shell, with explicit step-by-step instructions for each.
Balance references to Windows and Linux tools (e.g., mention both Visual Studio Code and common Linux editors).
Add screenshots and walkthroughs for Linux environments where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell and Azure CLI examples are provided for role assignment, but PowerShell is presented first in the permissions section. There are no explicit Linux-specific instructions or examples, and the use of PowerShell commands may implicitly favor Windows users. No mention is made of running commands in Bash or Linux shells, nor are there references to Linux-native tools or patterns. The documentation assumes familiarity with PowerShell and does not clarify cross-platform usage for the CLI or PowerShell modules.

Recommendations:

Ensure that Azure CLI (which is cross-platform) examples are always presented before PowerShell, or at least in parallel, to avoid a Windows-first impression.
Explicitly mention that Azure CLI and Azure PowerShell are both cross-platform and can be used on Windows, Linux, and macOS.
Where PowerShell examples are given, provide equivalent Bash (Linux shell) examples, especially for scripting scenarios.
Clarify in the documentation that commands can be run from Azure Cloud Shell, which supports both Bash and PowerShell, to reinforce cross-platform accessibility.
Avoid using PowerShell-specific syntax (such as backticks for line continuation) without also showing the Bash/Linux equivalent (backslash for line continuation).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by emphasizing Windows-specific security features (such as BitLocker and credential protection), mentioning Windows operating systems before Linux in guest OS support, and referencing Windows-specific threats and use cases. There are no Linux-specific examples or mentions of Linux disk encryption or security tooling, and the benefits and scenarios are described primarily in a Windows context.

Recommendations:

Include Linux-specific security features that benefit from vTPM, such as LUKS/dm-crypt disk encryption or Secure Boot for Linux distributions.
List Linux guest OS support before or alongside Windows in all relevant sections.
Describe use cases and threats relevant to Linux environments (e.g., rootkits, Linux kernel module signing).
Provide examples or references for configuring vTPM and Secure Boot with popular Linux distributions.
Balance the description of VBS and credential protection to include Linux security mechanisms or clarify if VBS is Windows-only.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for key steps (such as uploading templates to storage) and referencing Windows/PowerShell tooling first and most prominently. The Azure CLI (cross-platform) example is only provided for the deployment step, not for the earlier template upload step. There is no mention of Linux-specific considerations or examples for uploading templates, and the workflow assumes familiarity with PowerShell and Windows-centric patterns.

Recommendations:

Provide Azure CLI examples for all steps, including uploading templates to storage, not just deployment.
Explicitly mention that both PowerShell and Azure CLI are cross-platform, and clarify when a script is Windows-specific.
Add Linux/macOS shell (bash) examples for downloading files (e.g., using curl or wget) and uploading to Azure Storage (using az CLI).
Reorder examples so that Azure CLI (cross-platform) appears before PowerShell, or present both in parallel tabs.
Include notes about any OS-specific differences (such as file paths, command syntax, or required tools) for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows and Visual Studio users, with all instructions and examples assuming the use of Visual Studio (a Windows-centric IDE) and PowerShell scripts for deployment. There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor is there mention of cross-platform tools or workflows (such as Azure CLI, VS Code, or Bash scripts). The exclusive use of PowerShell and Visual Studio, and the lack of Linux/macOS alternatives, demonstrates a strong Windows bias.

Recommendations:

Add sections or notes describing how to perform equivalent resource group deployments using cross-platform tools such as Azure CLI and VS Code, which are available on Linux and macOS.
Provide Bash script examples for deploying ARM templates, alongside the PowerShell scripts.
Mention and link to cross-platform alternatives (e.g., VS Code with Azure extensions) early in the documentation, not just Visual Studio.
Clarify which steps are Windows/Visual Studio-specific and offer parallel instructions for users on other operating systems.
Include sample commands for deploying templates using Azure CLI (az deployment group create ...) as an alternative to PowerShell.
Explicitly state the platform requirements and suggest alternatives for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based automation instructions for converting templates, referencing a .ps1 script, and omitting any Linux/bash/CLI alternatives. The only automation example uses PowerShell, which is primarily associated with Windows environments, and there is no mention of Bash, Azure CLI, or cross-platform scripting. Manual steps are portal-based and platform-agnostic, but all scripting guidance assumes a Windows/PowerShell context.

Recommendations:

Provide equivalent automation instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
If the migration script is PowerShell-only, mention whether it works with PowerShell Core on Linux/macOS, and provide installation guidance if so.
Offer Bash script examples or reference community tools/scripts for Linux users.
Explicitly state platform compatibility for provided scripts and tools.
Consider presenting CLI or Bash examples before or alongside PowerShell to ensure Linux parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: PowerShell is frequently used for scripting examples, often before or instead of Linux/Unix alternatives; Windows-centric tools and patterns (such as PowerShell DSC and .ps1 scripts) are referenced without equivalent Bash or Linux-native examples; and sample artifact locations and scripts are Windows-specific, with no Linux shell script examples provided. While Azure CLI is included in some places, PowerShell is often presented first or exclusively, and there is a lack of parity in Linux/Unix-focused guidance.

Recommendations:

For every PowerShell example, provide an equivalent Bash/Azure CLI example, especially for scripting and automation tasks.
When referencing scripts or VM extensions (e.g., Custom Script Extension), include both Windows (.ps1) and Linux (.sh) script examples.
Avoid using Windows-specific artifact locations or script names as defaults (e.g., 'configure-music-app.ps1'); instead, provide parallel Linux examples (e.g., 'configure-music-app.sh').
When discussing VM images, include Linux publishers/offers/SKUs alongside Windows ones.
In sections about VM extensions, mention and provide examples for Linux extensions (e.g., Custom Script for Linux, OMS Agent for Linux) as well as Windows ones.
Ensure that all CLI and scripting guidance is cross-platform, and explicitly state when a command or feature is platform-specific.
Balance the order of presentation: alternate or randomize whether Windows or Linux examples are shown first, or present them side-by-side.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally cross-platform, but it contains a notable Windows bias in the section discussing integer parameter limits. It mentions PowerShell (a Windows-centric tool) as the example for SDK/CLI limitations, without referencing Azure CLI or Linux-based tools. No Linux or cross-platform command-line examples or notes are provided, and the only tool-specific guidance is for PowerShell.

Recommendations:

When discussing SDK or command-line tool limitations, mention both PowerShell and Azure CLI (which is cross-platform), and provide information about their respective behaviors.
If there are differences in parameter handling or integer ranges between PowerShell and Azure CLI, document both.
Include examples or notes relevant to Linux/macOS users, such as Azure CLI commands, to ensure parity.
Avoid using only Windows-centric tools (like PowerShell) as the sole example when discussing cross-platform scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell (Windows-centric) command-line examples for deploying templates and by referencing 'AzurePowerShell' in resource definitions. There are no examples using cross-platform tools such as Azure CLI (az), nor are Linux shell or Bash examples provided. Windows tools and patterns are mentioned exclusively, and Linux or cross-platform equivalents are missing.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell examples for template deployment and parameter passing.
When referencing deployment scripts, include examples for both 'AzurePowerShell' and 'AzureCLI' in the 'kind' property to demonstrate parity.
Explicitly mention that both PowerShell and CLI are supported, and provide guidance for Linux/macOS users.
Where shell commands are shown, provide both PowerShell and Bash (or sh) syntax.
Review all examples to ensure that Windows-specific tools or patterns are not presented as the only or primary option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned multiple times (e.g., deployment scripts, ARM TTK testing), and the only explicit tooling example for template testing is a PowerShell script. Visual Studio and Visual Studio Code are highlighted as authoring tools, both of which are most strongly associated with Windows. While Azure CLI and Bash are mentioned, PowerShell and Windows-centric tools are often listed first or exclusively detailed, and Linux-specific workflows or tools are not given equal prominence or examples.

Recommendations:

Provide explicit Linux/Bash examples alongside PowerShell, especially for deployment scripts and template testing.
Highlight cross-platform tools (e.g., Azure CLI, VS Code) before Windows-only tools (e.g., Visual Studio, PowerShell scripts).
Mention and link to Linux-compatible alternatives for template testing (e.g., running ARM TTK via PowerShell Core on Linux, or using other validation tools).
Clarify that Visual Studio Code is cross-platform, and suggest Linux-friendly editors (e.g., Vim, Emacs) where appropriate.
Ensure that all command-line and scripting examples are shown in both PowerShell and Bash where possible.
When listing deployment options, alternate the order or explicitly state cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (like Fiddler), Windows debugging patterns (such as using Visual Studio's 'Just My Code' and CLR exceptions), and .NET/ASP.NET-centric troubleshooting steps. There are no Linux-specific examples or equivalent instructions for common Linux environments (e.g., using curl, tcpdump, Wireshark, or Linux debugging tools). The guidance assumes the reader is running on Windows or using Windows-based development environments, with no mention of how to perform similar troubleshooting on Linux servers or containers.

Recommendations:

Add Linux-specific troubleshooting steps and examples, such as using curl, tcpdump, Wireshark, or equivalent tools for network inspection.
Include instructions for enabling and viewing logs on Linux (e.g., using journalctl, systemd, or tailing log files).
Provide parity in code/configuration examples for Linux-based hosting (e.g., how to set environment variables or configure TLS on Linux).
Mention cross-platform tools (such as Wireshark or browser DevTools) alongside Windows-only tools like Fiddler.
Clarify when instructions are Windows-specific and offer Linux alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the section discussing parameter naming conflicts, only the PowerShell deployment command (New-AzResourceGroupDeployment) is mentioned, with no reference to Azure CLI or other cross-platform tools. In the 'Resources' section, links to Windows-specific VM connection methods are listed before the Linux equivalent. Additionally, the only command-line tool mentioned for deployment is PowerShell, and no Linux/CLI examples or tools are provided.

Recommendations:

Include Azure CLI examples and references alongside PowerShell, especially when discussing deployment commands and parameter naming conflicts.
When listing links or instructions for connecting to VMs, alternate the order or present Linux and Windows options together to avoid prioritizing Windows.
Mention cross-platform tools (such as Azure CLI and Bash scripting) wherever PowerShell or Windows tools are referenced.
Provide examples or notes for both Windows and Linux users in relevant sections, ensuring parity in guidance and tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows/PowerShell bias by providing detailed PowerShell-based instructions and omitting equivalent Azure CLI (cross-platform) examples. The PowerShell approach is given equal or greater prominence than the Azure Portal, and there are no Linux shell or Azure CLI command examples for key steps like exporting, modifying, or deploying templates. This may hinder users on Linux or macOS who rely on Azure CLI or Bash scripting.

Recommendations:

Add Azure CLI examples for all major steps (exporting, modifying, and deploying templates), as Azure CLI is cross-platform and widely used on Linux/macOS.
When listing options for configuration (e.g., configuring service endpoints), mention Azure CLI before or alongside PowerShell to avoid 'windows_first' ordering.
Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
Where PowerShell scripts are shown, provide equivalent Bash/Azure CLI scripts to ensure parity.
Consider adding a 'Platform compatibility' note clarifying that the steps are not Windows-specific and can be accomplished on any OS with the appropriate tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias. It references SQL Server Management Studio (SSMS) and the New Subscription Wizard—both Windows-only tools—before mentioning cross-platform alternatives like Azure Data Studio. There are no explicit Linux command-line examples or guidance for Linux-based environments, and the documentation assumes the use of Windows-centric workflows and tools throughout.

Recommendations:

Provide explicit examples for configuring replication using command-line tools available on Linux, such as sqlcmd or Azure Data Studio's cross-platform features.
Mention Azure Data Studio as an equal alternative to SSMS, and provide step-by-step instructions for both tools where possible.
Clarify that the described procedures can be performed from Linux environments, and include any necessary prerequisites or differences.
If any PowerShell scripts or Windows-specific steps are referenced, add equivalent Bash or shell script examples for Linux users.
Add a section or note highlighting support for cross-platform management and any limitations or differences when using Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Azure PowerShell is featured prominently and often presented before or alongside Azure CLI, but without explicit Linux/Bash shell examples. The CLI examples are described as working in Bash or Azure PowerShell, but there are no dedicated Linux shell (e.g., Bash) or macOS terminal screenshots, nor are there any notes about differences in command usage or environment setup for non-Windows platforms. The PowerShell examples assume familiarity with Windows scripting conventions. No Linux-specific tools or guidance are provided, and the documentation does not address cross-platform nuances.

Recommendations:

Provide explicit Bash/Linux terminal examples and screenshots, especially for Azure CLI usage.
Clarify that Azure CLI commands can be run natively on Linux/macOS, and note any differences in quoting, environment variables, or authentication.
Balance the order of examples: present Azure CLI (cross-platform) before Azure PowerShell (Windows-centric) where possible.
Add notes or sections for Linux/macOS users, including troubleshooting tips or environment setup guidance.
Avoid assuming PowerShell as the default scripting environment; mention alternatives like Bash or zsh.
Where PowerShell is used, clarify if the example is for Windows PowerShell or cross-platform PowerShell Core.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. PowerShell is mentioned before Azure CLI in both prerequisites and command examples. Additionally, Windows-centric tools and patterns (such as PowerShell cmdlets like Get-AzSubscription, Get-AzADUser, and Get-AzADServicePrincipal) are referenced in parameter descriptions, with no Linux/CLI alternatives provided. However, Azure CLI examples are present alongside PowerShell, and there are no explicit missing Linux examples for the core deployment steps.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples throughout the documentation, or present Azure CLI first in some sections to balance exposure.
When referencing how to obtain values (such as tenantId or objectId), provide both PowerShell and Azure CLI commands (e.g., az account show, az ad user show) so Linux/macOS users have clear guidance.
Clarify that both Azure CLI and PowerShell are cross-platform, but highlight CLI as the default for Linux/macOS users.
Where possible, avoid referencing Windows-specific tools or patterns exclusively in parameter descriptions; always include CLI equivalents.
Consider adding a short section or note for Linux/macOS users, confirming that all steps are supported on their platforms and linking to relevant installation guides.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides detailed instructions for performing the NSG relocation using the Azure Portal and PowerShell, with all CLI-based automation examples using PowerShell cmdlets. There are no examples or guidance for performing these tasks using Azure CLI (az), Bash, or other cross-platform tools, which are commonly used on Linux and macOS. The PowerShell approach is presented as the only scripting/automation method, and even text editor examples reference Notepad, a Windows tool.

Recommendations:

Add equivalent step-by-step instructions using Azure CLI (az) commands for all automation tasks, including exporting, editing, and deploying ARM templates.
Provide Bash shell examples for editing JSON files, such as using vim, nano, or other cross-platform editors, instead of only referencing Notepad.
Ensure that all PowerShell examples are accompanied by Azure CLI equivalents, and present both options in parallel tabs or sections.
Avoid referencing Windows-only tools or patterns (like Notepad) without mentioning cross-platform alternatives.
Consider including a note at the top clarifying that the instructions apply equally to Windows, Linux, and macOS, and link to Azure CLI documentation for users on non-Windows platforms.

Create pull request

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 primary scripting language for both Azure PowerShell and Azure CLI container workflows, and all upload/deployment examples use PowerShell commands. There are no equivalent Linux shell (bash) or cross-platform CLI examples for uploading files or deploying templates. The Docker section uses Windows drive letter syntax (e.g., d:/docker), and the volume mount instructions are Windows-centric. Linux-native workflows and tools are not covered or are mentioned only after Windows/PowerShell approaches.

Recommendations:

Provide equivalent bash/Azure CLI examples for uploading deployment scripts to Azure Storage (e.g., using az storage file upload).
Include Linux/macOS-specific instructions for mounting directories in Docker (e.g., using /home/user/docker:/data syntax).
When presenting PowerShell examples, offer corresponding bash or shell script alternatives, especially for common tasks like resource group creation and template deployment.
Avoid using Windows drive letter syntax exclusively in Docker commands; show both Windows and Linux/macOS variants.
Clarify that all steps can be performed from Linux/macOS, and highlight any differences or prerequisites.
Consider reordering sections or providing parallel instructions so that Linux and Windows users see their workflows presented equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation presents both Azure PowerShell and Azure CLI deployment examples, but PowerShell is listed first, which may suggest a Windows-first approach. There is no explicit mention of Linux or macOS environments in the prerequisites or deployment verification steps. The instructions for tool installation and usage do not provide Linux-specific guidance or examples, and the portal screenshots and terminology are generic but do not address cross-platform nuances. The 'Clean up resources' and verification steps rely solely on the Azure portal, with no CLI-based alternatives, which could be more relevant for Linux users.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and widely used on Linux.
Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for all platforms.
In the prerequisites, clarify that Visual Studio Code and the Resource Manager Tools extension are available cross-platform.
Add Linux/macOS-specific notes or examples where relevant, such as using bash variables instead of PowerShell variables.
Provide CLI-based instructions for verification and clean-up steps, not just portal-based steps.
Include screenshots or terminal examples from Linux environments where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/PowerShell bias by exclusively providing instructions for enabling debug logging using Azure PowerShell, which is traditionally associated with Windows environments. There is no equivalent method or workaround provided for Linux users, as debug logging cannot be enabled via Azure CLI. The documentation also focuses on PowerShell cmdlets and patterns, with Azure CLI only being mentioned for retrieving or deleting logs, not for enabling debug logging itself.

Recommendations:

Clearly state the platform limitations at the beginning, emphasizing that enabling debug logging is only possible with Azure PowerShell, and suggest installation or usage options for Linux/macOS users (e.g., PowerShell Core).
Provide explicit instructions for installing and using Azure PowerShell on Linux and macOS, including links to relevant documentation.
If possible, advocate for parity in Azure CLI functionality or suggest alternative approaches for Linux users to achieve similar debug logging outcomes.
Add a section or note addressing Linux/macOS users, outlining their options and any current limitations, so they are not left without guidance.
Monitor and update the documentation if/when Azure CLI gains support for enabling debug logging, ensuring cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second, which is acceptable. However, in other areas, such as the 'SubnetsNotInSameVnet' error, the Windows VM documentation link is listed before the Linux VM equivalent. Additionally, there are no explicit Linux shell (bash) command examples or references to Linux-native tools, and PowerShell is referenced as a primary tool for context management. There are no Linux-specific troubleshooting patterns or examples, and Windows terminology (such as PowerShell) appears more frequently or with higher prominence.

Recommendations:

Ensure that for every PowerShell example or reference, an equivalent Azure CLI (bash-friendly) example is provided and listed first or side-by-side.
When linking to OS-specific documentation (e.g., multiple NICs for VMs), alternate the order or present both Windows and Linux links together, or list Linux first to balance historic bias.
Include Linux-native troubleshooting tools or commands where relevant, not just PowerShell.
Audit for any missing Linux-specific troubleshooting scenarios and add them where appropriate.
Use neutral language when referring to command-line tools (e.g., 'Azure CLI or PowerShell') and avoid defaulting to Windows-first terminology.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in command examples and explanations, with more detailed PowerShell output samples. Output examples and walkthroughs default to PowerShell syntax and screenshots, even when Azure CLI (cross-platform) equivalents are available. There is no mention of Linux-specific shell environments or considerations, and the only installation guidance for PowerShell assumes a Windows context. The documentation does not provide Linux-specific troubleshooting, nor does it mention using Bash or other native Linux shells.

Recommendations:

Alternate the order of PowerShell and Azure CLI sections/examples, or present Azure CLI first to reflect its cross-platform nature.
Provide output and walkthrough examples for both PowerShell and Azure CLI, including screenshots and text outputs for each.
Explicitly mention that Azure CLI commands work natively on Linux/macOS and provide any relevant Linux-specific notes (e.g., differences in shell syntax, file paths, or color support).
Include installation instructions for Azure PowerShell on Linux/macOS, or clarify that Azure CLI is the recommended tool for those platforms.
Where possible, use neutral, cross-platform language (e.g., 'shell' instead of 'PowerShell') and avoid assuming a Windows environment.
Add troubleshooting tips or notes for common Linux/macOS issues (e.g., permissions, environment variables, color output in different terminals).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and the use of PowerShell (a Windows-centric tool) is emphasized. The prerequisites mention Visual Studio Code and the Resource Manager Tools extension, which are cross-platform, but do not mention any Linux-specific editors or tools. There is no explicit mention of Linux or macOS environments, and the CLI examples use syntax that is compatible with both, but the ordering and tool recommendations subtly prioritize Windows users.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to avoid implicit prioritization of Windows tools.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
Include references to popular Linux/macOS editors (such as Vim, Nano, or Sublime Text) alongside Visual Studio Code.
In the prerequisites, clarify that all tools and steps are cross-platform, and provide links to installation instructions for Linux/macOS where appropriate.
Add a note or section highlighting any differences or considerations for Linux/macOS users, if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias in several areas: configuration and deployment instructions reference the Azure portal and GUI-based workflows (which are more familiar to Windows users), and CORS configuration for local development only provides a JSON example for local.settings.json without mentioning Linux-specific considerations. The CORS section explicitly notes that CORS configuration is not available for Azure Functions Linux Consumption plan, but does not provide equivalent Linux command-line or configuration alternatives. There are no CLI or cross-platform examples for tasks like enabling CORS or deploying functions, and no mention of Linux-specific tools or workflows. The documentation assumes use of the Azure portal and omits Linux shell or Azure CLI examples, which would be more familiar to Linux users.

Recommendations:

Add Azure CLI and/or PowerShell examples for all configuration steps (e.g., enabling CORS, setting connection strings), and ensure both are presented together or with CLI first.
For local development, provide Linux-specific guidance for editing local.settings.json, including common Linux editors and file paths.
Where the Azure portal is referenced, provide equivalent command-line instructions using Azure CLI or ARM templates.
Explicitly address Linux Consumption plan limitations and provide recommended workarounds or alternatives for Linux users.
Include deployment examples using cross-platform tools (e.g., Azure CLI, GitHub Actions) rather than only referencing portal-based workflows.
Ensure that all code/configuration samples are clearly marked as OS-agnostic or provide both Windows and Linux variants where differences exist.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates bias towards Windows by exclusively referencing and providing examples for Windows-specific tools such as SQL Server Management Studio (SSMS), SqlPackage.exe, and cmd.exe commands. There are no equivalent instructions or examples for Linux users, such as using Azure Data Studio on Linux, sqlcmd in a bash shell, or Linux-compatible versions of SqlPackage. The ordering of tool recommendations also places Windows tools first, with no mention of Linux alternatives.

Recommendations:

Include explicit instructions and examples for Linux users, such as using Azure Data Studio or sqlcmd from a bash shell.
Provide Linux-compatible SqlPackage usage examples, including installation and command-line usage on Linux/macOS.
Mention cross-platform tools (like Azure Data Studio and sqlcmd) before Windows-only tools (like SSMS), or at least present them in parallel.
Clarify which tools are cross-platform and which are Windows-only, and provide download links or installation instructions for Linux/macOS where applicable.
Where command-line examples are given, provide both Windows (cmd.exe/PowerShell) and Linux (bash) syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows a moderate Windows bias. Visual Studio Code is the only editor mentioned, and the instructions reference the Resource Manager Tools extension, which is most commonly used on Windows. In the deployment section, PowerShell is presented as an equal option to Bash/CLI, but the PowerShell tab is listed before the CLI tab, and PowerShell is called out explicitly. There are no Linux-specific tools or editors mentioned, and the workflow assumes familiarity with Windows-centric patterns (e.g., Visual Studio Code, PowerShell).

Recommendations:

Explicitly mention that Visual Studio Code is cross-platform, and suggest alternative editors (such as Vim, Emacs, or nano) for Linux users.
Include instructions for using native Linux editors and tools to open and edit ARM templates.
When presenting deployment commands, alternate the order of CLI and PowerShell tabs, or present CLI (Bash) first to avoid Windows-first bias.
Clarify that both Bash and PowerShell are available in Azure Cloud Shell, and that Bash is often the default for Linux users.
Add a note or section for Linux users, highlighting any differences or tips for working with ARM templates on Linux.
Avoid assuming Visual Studio Code is installed; provide alternatives for users who prefer not to use it.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by referencing .NET-specific tools (such as the .NET secret manager), using configuration patterns and environment variable conventions that are most familiar to Windows/.NET developers, and omitting explicit Linux or cross-platform examples for environment variable setting or secret management. While the Azure CLI is mentioned (which is cross-platform), there are no shell-specific examples for Linux, and the documentation assumes familiarity with Windows-centric development workflows.

Recommendations:

Add explicit Linux/macOS shell examples for setting environment variables (e.g., export Azure__SignalR__ConnectionString=...) alongside the .NET secret manager and Windows environment variable examples.
Mention and provide examples for common Linux secret management tools (such as using environment variables in bash/zsh, or referencing Azure Key Vault from Linux-based deployments).
Clarify that the .NET secret manager and configuration patterns are cross-platform, and provide guidance for developers working outside of Windows (e.g., on Docker, Linux VMs, or CI/CD pipelines).
Where possible, present cross-platform or Linux-first examples before or alongside Windows/.NET-specific tools.
Include a note or section about configuring connection strings in popular Linux deployment scenarios (such as systemd services, Docker containers, or Kubernetes pods).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively using Windows VM examples, PowerShell scripts, and Windows-specific tools (such as Install-WindowsFeature and IIS). There are no Linux VM examples, no Bash or shell script alternatives, and no mention of Linux extensions or tools. The template and deployment steps are all tailored to Windows environments, with no guidance for Linux users.

Recommendations:

Add parallel Linux examples throughout the tutorial, including deploying a Linux VM and using a Custom Script Extension to run a Bash script (e.g., installing Apache).
Provide both PowerShell and Bash script samples for the Custom Script Extension.
Include references and links to Linux VM extensions documentation, such as the Linux features page.
Show how to retrieve the public IP address using both Azure CLI (az) and PowerShell.
When mentioning tools or commands (e.g., Install-WindowsFeature), provide the Linux equivalent (e.g., apt-get install apache2).
Ensure that the quickstart template section includes a Linux VM template alongside the Windows one.
Balance the order of presentation so that Linux and Windows are given equal prominence, or clearly indicate when content is Windows-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by using Windows file paths (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, and by not providing Linux/macOS equivalents or notes. All examples reference Windows-style paths, and there is no mention of Linux shell or PowerShell Core on non-Windows platforms. While both Azure PowerShell and Azure CLI examples are given, the CLI examples also use Windows paths, and there are no explicit Linux/macOS instructions or screenshots. The documentation assumes a Windows environment for file storage and command usage.

Recommendations:

Provide both Windows and Linux/macOS file path examples (e.g., c:\Templates\deployTS\azuredeploy.json and ~/Templates/deployTS/azuredeploy.json).
Add notes or tabs for Linux/macOS users, especially for file paths and shell commands.
Clarify that Azure CLI and PowerShell can be used cross-platform, and provide examples or screenshots for non-Windows environments.
Avoid assuming a default file system structure; use environment variables or platform-agnostic paths where possible.
Mention any platform-specific issues (such as the PowerShell variable assignment note) for both Windows and non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In the 'Getting started' section, PowerShell is mentioned first among automation clients, ahead of CLI and SDK options. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, nor are Linux-specific tools or workflows referenced. The sample queries are platform-agnostic (Kusto), but the automation guidance implicitly prioritizes Windows/PowerShell users.

Recommendations:

List Azure CLI before PowerShell when mentioning automation clients, or present both together to avoid implying a platform preference.
Explicitly mention that both PowerShell and Azure CLI are cross-platform, and provide links to installation/use on Linux/macOS as well as Windows.
Add sample usage snippets for both PowerShell and Azure CLI (and/or Bash) to demonstrate parity.
Reference Linux/macOS environments in automation and scripting contexts, not just Windows.
Consider including a short section or note on using ARG queries from Linux terminals, with example commands.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell deployment instructions and referencing the Azure PowerShell module as a prerequisite. There are no examples or instructions for deploying the Bicep template using Azure CLI, Bash, or other cross-platform tools. This may hinder Linux or Mac users who are more likely to use CLI or Bash scripts.

Recommendations:

Add equivalent Azure CLI (az) deployment instructions alongside the PowerShell example, including both script and command-line usage.
Mention both Azure PowerShell and Azure CLI as valid prerequisites for deployment, and provide installation links for both.
Explicitly state that the deployment steps can be performed on any platform (Windows, Linux, Mac) using the Azure CLI.
Where possible, provide Bash script snippets for Linux/Mac users, or at least show the az deployment group create command.
Ensure that references to shell actions (e.g., 'right-click the shell window') are platform-neutral or include alternatives for Linux/Mac terminals.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI (with Bash scripting) and PowerShell examples, but the PowerShell section is given equal prominence, and there is no explicit mention of Linux or macOS environments. The Bash scripting in the Azure CLI section assumes a Unix-like shell but does not clarify compatibility with Windows (e.g., WSL, Git Bash, or native Windows shell). The PowerShell section is implicitly Windows-centric, and there is no mention of cross-platform PowerShell Core or how to run these commands on Linux/macOS. There is also no explicit guidance for users on non-Windows platforms regarding prerequisites or shell compatibility.

Recommendations:

Explicitly state that the Azure CLI examples require a Bash shell and provide alternatives or notes for Windows users (e.g., using WSL, Git Bash, or PowerShell equivalents).
Clarify that PowerShell examples can be run on PowerShell Core, which is cross-platform, and provide instructions for Linux/macOS users if any differences exist.
Consider adding a dedicated section or notes for Linux/macOS users to ensure parity and clarify any environment-specific requirements.
Where possible, provide examples that are explicitly cross-platform or indicate which platforms each example is tested on.
Add a table or quick reference indicating which tools/shells are supported on which operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing the Key Vault and deploying templates use Azure PowerShell, with no equivalent Azure CLI (Bash) or Linux-native examples. The sample ARM template is for a Windows VM, and the deployment validation steps focus on RDP (Windows Remote Desktop Protocol) access. While Cloud Shell is mentioned as supporting both PowerShell and Bash, only PowerShell scripts are provided, and there is no guidance for Linux VM scenarios or SSH access. Windows tools and patterns (e.g., RDP, PowerShell) are mentioned exclusively or before any Linux alternatives.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all PowerShell scripts, especially for key vault creation, secret management, and template deployment.
Include a Linux VM example alongside the Windows VM example, with instructions for using SSH keys and connecting via SSH.
When describing Cloud Shell, show both PowerShell and Bash workflows, and clarify which commands work in each environment.
For deployment validation, add steps for connecting to a Linux VM using SSH, not just RDP for Windows.
Mention and link to Linux password requirements and documentation, not just Windows VM password requirements.
Balance the order of presentation so that Linux and Windows tools/examples are given equal prominence, or alternate which comes first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. Several JSON examples for UI controls include the property "osPlatform": "Windows" or are tailored to Windows-specific scenarios (such as username conventions and credential controls). There are no examples or mentions of Linux-specific UI controls, values, or scenarios. The documentation does not provide parity for Linux users, omitting Linux platform examples or guidance where relevant.

Recommendations:

Add examples that use "osPlatform": "Linux" for controls such as user name, credentials, and VM size selectors.
Where examples include Windows-specific values (e.g., default usernames, password policies), provide equivalent Linux-focused examples.
Explicitly mention Linux support in relevant sections, and clarify any differences in behavior or requirements between Windows and Linux platforms.
For controls that support both Windows and Linux (such as Microsoft.Compute.CredentialsCombo or Microsoft.Compute.UserNameTextBox), provide parallel examples for each OS.
Review all examples and ensure that Linux scenarios are represented equally, especially in areas where platform-specific behavior is relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI (cross-platform) examples. It also recommends Visual Studio Code and its extensions for syntax validation, which, while cross-platform, are more commonly associated with Windows workflows. There are no explicit Linux shell or scripting examples, and no mention of Linux-specific tools or patterns. However, Azure CLI examples are present and correct, and no examples are strictly Windows-only.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
Explicitly mention that both Azure CLI and Visual Studio Code are available on Linux, macOS, and Windows.
Where appropriate, provide Linux shell (bash) command-line examples, especially for common troubleshooting tasks.
Highlight any differences in experience or troubleshooting steps between Windows and Linux environments, if applicable.
Consider referencing additional editors or tools popular in Linux environments (e.g., Vim, Emacs, nano) for template editing and validation, if relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the tool for restoring encrypted VMs, and by linking only to Windows-specific disk encryption documentation. There are no Linux-specific examples or references for restoring encrypted VMs or for file-level restore scenarios. The documentation mentions Windows tools and patterns exclusively or before Linux equivalents, and omits Linux parity in restore instructions.

Recommendations:

Include Linux-specific restore instructions and examples, especially for encrypted VMs (e.g., using Azure CLI or relevant Linux tools).
Provide links to Linux disk encryption documentation (such as for VMs encrypted with Azure Disk Encryption for Linux).
When referencing PowerShell, also mention Azure CLI or Bash alternatives for cross-platform parity.
Ensure that file-level restore instructions and examples cover both Windows and Linux VMs, including any OS-specific considerations.
Avoid listing only Windows scenarios or tools; always present Linux equivalents alongside or before Windows examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks, but it demonstrates a Windows bias by listing PowerShell (a Windows-centric tool) as an equal alternative to Azure CLI, and by not mentioning or providing any Linux- or macOS-specific shell examples (such as Bash). The prerequisites section lists Visual Studio Code and PowerShell before Azure CLI, and does not mention Linux-native editors or shells. There are no explicit Linux or macOS instructions, and the use of PowerShell is emphasized throughout, which may not be as familiar or available to Linux users.

Recommendations:

Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and clarify that PowerShell is optional.
Provide Bash shell examples or clarify that the Azure CLI examples are suitable for Bash on Linux/macOS.
In the prerequisites, mention that Visual Studio Code and Azure CLI are cross-platform, and suggest Linux-native editors as alternatives.
Consider reordering examples to show Azure CLI (cross-platform) before PowerShell, or clarify that PowerShell Core is available on Linux/macOS.
Add notes or callouts for Linux/macOS users regarding any platform-specific considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong bias toward Windows and PowerShell. All deployment script examples use PowerShell exclusively, and the deploymentScripts resource is configured with 'kind: AzurePowerShell' only. The script content and debugging instructions are PowerShell-centric, with no Bash or cross-platform scripting alternatives. While Azure CLI examples are provided for template deployment, the core automation and scripting are PowerShell-only. There is no mention of Linux shell scripting or Bash-based deployment scripts, and PowerShell is presented as the default or only supported scripting language.

Recommendations:

Provide equivalent examples using Bash scripting and 'AzureCLI' deployment script kind, where possible.
Explicitly mention support for Linux-based scripting and tools, and clarify any current limitations.
Add Bash or shell script content for the deploymentScripts resource, or note if only PowerShell is currently supported.
Ensure that both PowerShell and Bash/CLI examples are presented in parallel throughout the documentation, not just for template deployment but also for scripting and debugging.
Avoid language that implies PowerShell is the only or default choice unless it is a technical limitation, in which case, state this clearly and provide a roadmap or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is heavily PowerShell-centric, as the ARM template test toolkit is implemented as a set of PowerShell scripts. All usage examples, regardless of platform (Windows, Linux, macOS), require PowerShell and provide only PowerShell commands. The Windows installation section is presented first, and there are no examples using native Linux tools or shell scripting. The toolkit itself is fundamentally tied to Windows/PowerShell paradigms, and Linux instructions are essentially adaptations for running PowerShell Core on Linux, rather than offering a native Linux experience.

Recommendations:

Clearly state at the beginning that the toolkit is PowerShell-based and requires PowerShell on all platforms.
Consider providing or linking to a cross-platform wrapper or alternative (e.g., a Docker image or a CLI tool) for users who prefer not to use PowerShell.
Offer bash or shell script examples for common tasks, even if they simply invoke PowerShell scripts, to better align with Linux user expectations.
If possible, develop and document a native Linux/Unix CLI interface or provide guidance for integrating the toolkit into typical Linux CI/CD workflows.
In the installation sections, present Linux and macOS instructions before or alongside Windows, or group them together to avoid a Windows-first impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias: it exclusively lists Windows-specific prerequisites (Visual Studio 2019, .NET Framework 4.6.1), assumes the use of Visual Studio for development and debugging, and provides instructions and tooling (such as NuGet Package Manager Console with a PowerShell command) that are only available or typical on Windows. There are no instructions or examples for developing or running the sample on Linux or macOS, nor are cross-platform tools or editors (like VS Code or JetBrains Rider) mentioned.

Recommendations:

Add a section or notes for Linux/macOS users, including supported development environments (e.g., Visual Studio Code, JetBrains Rider) and .NET Core/Mono equivalents.
Provide instructions for installing dependencies and running the sample using cross-platform .NET SDKs (e.g., dotnet CLI) instead of only Visual Studio.
Include alternative commands for package installation using the dotnet CLI (e.g., 'dotnet add package') in addition to the NuGet Package Manager Console.
Clarify which steps are Windows-specific and offer parallel steps for Linux/macOS where possible.
Mention any platform limitations or requirements explicitly, so non-Windows users know what is and isn't supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation relies exclusively on PowerShell cmdlets and Azure portal UI steps, with no mention of equivalent Linux CLI tools or workflows. Windows terminology and tools are referenced first or exclusively, and there is a lack of Linux-specific examples or parity in operational guidance.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using VMware's govc CLI or REST APIs) alongside PowerShell cmdlets.
Include instructions for performing these operations from Linux environments, not just via the Azure portal or PowerShell.
When listing prerequisites or VM requirements, present Linux and Windows information together and with equal prominence.
Reference cross-platform tools and workflows where possible, and avoid assuming the administrator is using Windows.
Add links to official VMware documentation for Linux-based management and automation of vSAN.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows subtle Windows bias by referencing Windows-specific tools and configuration paths before or instead of Linux equivalents. For example, the 'Client Network Configuration' link points to a Windows-only page, and there are no explicit Linux command examples or Docker-based configuration walkthroughs, despite Azure SQL Edge being primarily deployed on Linux containers. The mention of the absence of 'mssql-conf' utility is present, but there is no compensating Linux-centric guidance or examples.

Recommendations:

Provide Linux-specific examples for client configuration, such as using sqlcmd or ODBC on Linux, and link to relevant Linux documentation.
Include Docker-based configuration and security best practices, as Azure SQL Edge is typically deployed in containers on Linux.
Balance references to Windows and Linux tools, ensuring that Linux-first or cross-platform instructions are given equal prominence.
When referencing configuration files or utilities, provide explicit Linux paths and examples (e.g., editing mssql.conf on Linux, using environment variables in Docker Compose).
Replace or supplement Windows-only links (such as 'Client Network Configuration') with Linux or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on GUI-based steps via the Azure portal and VMware vSphere, which are more familiar to Windows users. There are no command-line examples for Linux environments, nor are Linux-native tools or workflows mentioned. The only CLI example provided uses Azure CLI, which is cross-platform, but there are no Linux-specific considerations or examples (e.g., shell scripts, Linux authentication nuances). VMware Tools is referenced, but no mention is made of open-vm-tools (the Linux equivalent).

Recommendations:

Add Linux-specific examples, such as enabling guest management or installing extensions via SSH or Linux shell commands.
Mention open-vm-tools as the Linux equivalent of VMware Tools and provide installation/verification steps for Linux VMs.
Include command-line instructions for both Windows (PowerShell) and Linux (Bash) environments where applicable.
Clarify any differences in prerequisites or workflows for Linux VMs, such as authentication or agent installation steps.
Ensure that screenshots or navigation steps are supplemented with CLI alternatives suitable for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell scripts and cmdlets, referencing Windows-centric tools (e.g., PowerShell, New-AzVM), and using Windows path notation in examples. While Azure CLI commands are included (which are cross-platform), the PowerShell section is more extensive and advanced. There are no explicit Linux shell (bash) or macOS-specific examples, and the REST example uses a Windows-style path for output. The documentation does not mention or show Linux-native scripting or tools for querying SKUs.

Recommendations:

Add bash (Linux/macOS) shell script examples for filtering and processing az vm list-skus output, such as using jq or grep.
Ensure REST API examples use cross-platform path notation (e.g., ./sku-list.json instead of .\sku-list.json) or provide both Windows and Linux variants.
Balance the depth of PowerShell and CLI sections, ensuring advanced filtering and scripting examples are available for both.
Explicitly mention that Azure CLI commands work on Linux/macOS and provide example outputs from those environments.
Avoid referencing Windows-specific tools (e.g., New-AzVM) before their CLI equivalents, or present both together.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for Azure PowerShell, which is most commonly used on Windows. It references Windows-specific tools (e.g., Notepad) and omits any examples or guidance for Linux or cross-platform CLI tools such as Azure CLI, Bash, or editors commonly used on Linux/macOS. The PowerShell-based workflow is presented as the only scripting/command-line option, and Windows tools are mentioned before any cross-platform alternatives.

Recommendations:

Add parallel instructions and examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
When referencing file editing, suggest cross-platform editors (e.g., nano, vim, code) or use generic language such as 'open the file in your preferred text editor.'
Include Bash shell command examples alongside PowerShell, especially for template export, editing, and deployment.
Explicitly state that the process can be performed on any OS, and provide OS-agnostic steps where possible.
If referencing PowerShell, clarify that Azure PowerShell is available on Linux and macOS, and provide installation links or notes for those platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments. All instructions, screenshots, and procedures assume the use of Windows tools (e.g., Certificate Import Wizard, Windows Registry Editor, right-click context menus), and there are no examples or guidance for performing equivalent tasks on Linux systems. The process for enabling TLS, importing certificates, and managing the backup server is described exclusively with Windows-specific steps, with no mention of Linux alternatives or parity.

Recommendations:

Provide equivalent instructions for Linux environments, such as using OpenSSL or command-line tools to import certificates.
Include Linux-based examples for enabling TLS 1.2 and managing certificates (e.g., updating .NET Core settings, using update-ca-certificates, etc.).
Clarify whether Azure Backup Server is supported on Linux, and if not, explicitly state this early in the documentation.
If Azure Backup Server is Windows-only, suggest alternative backup solutions for Linux users or provide links to relevant documentation.
Add a section or callout that addresses cross-platform considerations and explicitly mentions any limitations or differences for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively referencing Windows Server Active Directory as the LDAP provider, requiring Windows Server domain controllers and certificates, and omitting any examples or guidance for integrating with Linux-based LDAP servers (such as OpenLDAP). All prerequisites, instructions, and screenshots are centered on Windows environments, with no mention of Linux alternatives or parity.

Recommendations:

Include examples and instructions for integrating NSX with Linux-based LDAP servers, such as OpenLDAP, alongside Windows Server Active Directory.
Update prerequisites to mention that any standards-compliant LDAP server (not just Windows Server) can be used, and provide guidance for Linux-based deployments.
Add screenshots or configuration steps that demonstrate connecting to a Linux LDAP server.
Reference Linux-based certificate authorities (e.g., OpenSSL, FreeIPA) as alternatives for issuing LDAPS certificates.
Ensure terminology and examples are platform-neutral where possible, and only specify Windows-specific steps when absolutely necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), using Azure portal workflows that assume a Windows-centric environment, and mentioning Windows Server Failover Clusters as a supported feature without equivalent Linux clustering references. There are no Linux CLI or shell examples, nor are Linux tools or workflows mentioned for managing vSAN ESA features.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using VMware's govc CLI, or REST API calls via curl) for all PowerShell cmdlets.
Include instructions for managing vSAN ESA features from Linux or cross-platform environments, such as using the vSphere API or SDKs (Python, Go, etc.).
Mention Linux clustering solutions (e.g., Pacemaker, Corosync) in the context of guest cluster support, if applicable.
Clarify that the documented procedures can be performed from non-Windows environments where possible, or note any limitations.
Add explicit notes or sections for Linux administrators to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows development environments, specifically Visual Studio, and omits Linux-specific instructions or parity. All GUI instructions and screenshots are for Visual Studio on Windows, and there is no mention of Visual Studio Code, command-line editors, or Linux-specific workflows. The only alternative to Visual Studio is a brief mention of the .NET CLI for project creation, but subsequent steps (debugging, publishing, secret management) assume Visual Studio usage. There are no Linux or cross-platform publishing/deployment instructions, and all troubleshooting and tool references are Windows-centric.

Recommendations:

Provide parallel instructions for Linux and macOS users, including using Visual Studio Code or JetBrains Rider, and command-line workflows.
Include CLI-based steps for publishing to Azure (e.g., using 'dotnet publish' and 'az webapp deploy') instead of only Visual Studio GUI.
Add Linux-specific notes for running and debugging the app (e.g., using 'dotnet run', browser access, and terminal debugging).
Mention cross-platform secret management tools and workflows (e.g., 'dotnet user-secrets', environment variables).
Include screenshots or descriptions for non-Windows environments where relevant.
Explicitly state that the tutorial is cross-platform and highlight any differences or prerequisites for Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows/Azure-centric bias by exclusively referencing Azure portal and Azure Run commands for deployment and management, with no mention of Linux-based tools, CLI, or cross-platform alternatives. All operational instructions assume use of the Azure portal and its Run command feature, which is typically accessed via a browser on Windows or via PowerShell. There are no examples or guidance for Linux users or those preferring CLI-based or non-portal workflows.

Recommendations:

Provide equivalent instructions for deploying and managing VMware Cloud Director Availability using cross-platform tools such as Azure CLI and PowerShell Core (which runs on Linux, macOS, and Windows).
Include explicit Linux-based examples or workflows, such as using Azure CLI on Linux to invoke Run commands or manage resources.
Mention and document any prerequisites or differences for users operating from Linux or macOS environments, including authentication, tooling, and access methods.
If Run commands can be triggered via REST API or CLI, provide sample commands for those interfaces.
Ensure screenshots and UI references are supplemented with command-line alternatives for parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell (PowerCLI) examples for verifying DNS resolution, with no equivalent Linux or cross-platform CLI examples. The use of PowerShell cmdlets is presented as the sole method for interacting with the NSX-T DNS Forwarder Service, and there is no mention of Linux-native tools or instructions for users on non-Windows platforms.

Recommendations:

Add equivalent Linux/Unix command-line examples (e.g., using curl, wget, or direct API calls with tools like curl or httpie) for interacting with the NSX-T Policy API.
Provide nslookup or dig command examples that can be run from a Linux shell to verify DNS resolution, especially since the raw output shown is from DiG on Ubuntu.
Mention and document how to use cross-platform tools (such as Python scripts or REST API calls) to perform the same verification steps.
Reorganize sections so that platform-agnostic or Linux examples are presented alongside or before Windows/PowerShell examples to ensure parity.
Explicitly state that PowerCLI is a Windows-centric tool and provide guidance for users on macOS and Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing SQL Server Management Studio (SSMS) as the client tool for connecting to Azure SQL Edge, which is a Windows-only application. There are no examples or mentions of Linux-native or cross-platform tools (such as Azure Data Studio or sqlcmd) for connecting to the SQL Edge instance. The checklist and connection instructions both prioritize SSMS, and there is no guidance for Linux users on how to connect or manage the deployment from non-Windows environments.

Recommendations:

Include examples and explicit instructions for connecting to Azure SQL Edge using cross-platform tools such as Azure Data Studio and sqlcmd.
Update checklists and connection sections to mention both SSMS (Windows) and alternative tools (Linux/macOS/cross-platform) equally.
Provide sample connection commands for Linux/macOS terminals using sqlcmd or Azure Data Studio.
Where possible, use neutral terminology (e.g., 'Connect with a SQL client') and list both Windows and Linux options.
Add a note or section for Linux users, clarifying supported tools and providing installation links.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell scripts for resource deployment, referencing Windows-centric tools (Visual Studio 2019, Azure IoT Edge tools), and omitting equivalent Linux/bash instructions. While some commands use Azure CLI, they are embedded within PowerShell scripts, and there are no standalone bash or Linux shell examples. The prerequisites and workflow assume a Windows environment, making it less accessible for Linux or cross-platform users.

Recommendations:

Provide equivalent bash/Linux shell scripts for all PowerShell examples, especially for resource deployment steps.
List cross-platform tools (such as VS Code with Azure extensions) alongside or before Windows-only tools like Visual Studio 2019.
Clearly indicate which steps are platform-specific and offer alternatives for Linux/macOS users.
Separate Azure CLI commands from PowerShell scripts and provide standalone CLI/bash instructions.
Review and update prerequisites to include Linux-compatible development environments and tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tooling references are specific to Windows Server (e.g., Server Manager, ReFS, PowerShell cmdlets). There are no Linux equivalents or cross-platform guidance, and the prerequisites explicitly require Windows Server. PowerShell is the only scripting interface mentioned.

Recommendations:

Clearly state in the introduction that Azure Backup Server is only supported on Windows, if that is the case. If Linux support is planned or available, provide equivalent instructions for Linux environments.
If any features are available on Linux (or via Azure-native tools), add parallel sections with Linux commands, tools, and screenshots.
Where PowerShell is used, provide Bash or CLI equivalents if possible, or explain why only PowerShell is supported.
Reference cross-platform Azure tools (such as Azure CLI or REST APIs) where applicable, and provide examples for both Windows and Linux.
If the product is fundamentally Windows-only, add a prominent note to clarify this, and consider linking to alternative backup solutions for Linux workloads.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools, terminology, and examples. Windows-specific monitoring targets (registry, files, Microsoft services) are mentioned before Linux equivalents, and there is a lack of Linux-specific operational guidance. The only Linux-specific instruction is a workaround for sudo prompts, with no deeper Linux integration or troubleshooting examples. No Linux command-line or configuration examples are provided, and the documentation assumes familiarity with Windows patterns and tools.

Recommendations:

Provide Linux-specific examples for monitoring and extension installation, such as sample commands for installing the Log Analytics agent on Linux VMs.
Include Linux monitoring targets (e.g., systemd services, log files) alongside Windows registry and services, and mention them with equal prominence.
Offer troubleshooting steps and operational guidance for both Windows and Linux VMs, including common issues and solutions.
Balance the order of presentation so that Linux and Windows are treated equally, rather than listing Windows tools and patterns first.
Add references to Linux documentation and best practices for integrating with Azure native services.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes recovery using Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-based tools. There are no references to Linux-based recovery workflows, nor are there examples or instructions for Linux systems. The screenshots and terminology are all specific to Windows environments, and no parity is provided for Linux users.

Recommendations:

Include a section or separate instructions for recovering data from Linux-based systems protected by Azure Backup.
Mention and provide examples for Linux-compatible tools or command-line workflows, such as using Azure CLI or REST API for recovery operations.
Clarify in the introduction that the documented process is specific to Windows environments, and link to Linux-specific recovery documentation if available.
Add parity in screenshots and step-by-step guides for Linux users, or explicitly state if Linux is not supported by Azure Backup Server.
If Linux is unsupported in this scenario, provide alternative recovery options for Linux workloads protected by Azure Backup.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes a Windows environment throughout: all file paths use Windows conventions, only Windows-specific examples (such as Drive: notation and cscript for VBScript) are provided, and there is no mention of Linux or cross-platform considerations. There are no Linux shell script examples, no Linux file path formats, and no guidance for non-Windows environments.

Recommendations:

Add explicit guidance for Linux environments, including examples using Linux file paths (e.g., /opt/Microsoft/DataProtectionManager/DPM/Scripting).
Provide sample scripts and command-line usage for Linux shells (e.g., bash, sh) alongside Windows examples.
Clarify whether MABS supports Linux agents and, if so, document any differences in script execution, permissions, and configuration.
Mention Linux equivalents for Windows tools (e.g., using bash or sh instead of cscript for script execution).
Ensure all instructions and XML examples are platform-agnostic or provide both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes the upgrade process for the Microsoft Azure Recovery Services (MARS) agent on Windows-based systems. All instructions, screenshots, and tool references (such as Remote Desktop, DPM Console, and the MARS agent itself) are Windows-specific. There are no mentions of Linux systems, Linux tools, or cross-platform considerations, indicating a strong Windows bias.

Recommendations:

Explicitly state in the introduction whether the MARS agent is supported only on Windows, or clarify if Linux support is unavailable.
If Linux support exists or is planned, provide equivalent instructions and examples for Linux systems, including command-line steps, package management, and remote connection methods (e.g., SSH).
Include a section addressing cross-platform environments, even if only to clarify platform limitations.
Where possible, use neutral language and avoid assuming Remote Desktop or Windows GUI tools are the only management options.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, with no mention of Linux shell, Bash, or cross-platform scripting alternatives. All operational examples and terminology are centered around PowerShell and Windows-centric tools, with no Linux or macOS parity or guidance.

Recommendations:

Include examples of using Run Command with Bash or shell scripts for Linux administrators, if supported.
Clarify whether Run Command supports only PowerShell or if cross-platform scripting (e.g., Bash, Python) is possible, and document accordingly.
If PowerShell is required, mention that PowerShell Core is cross-platform and provide guidance for Linux/macOS users on how to use it.
Add explicit notes or sections for Linux/macOS users, including prerequisites and usage patterns relevant to those environments.
Where possible, provide equivalent command-line examples for both Windows (PowerShell) and Linux (Bash/shell) to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing Windows uninstall instructions before Linux, using Windows GUI tools (Control Panel) for agent removal, and referencing Windows-specific folder paths. While Linux instructions are present and reasonably detailed, the ordering and prominence of Windows tools and patterns suggest a Windows-centric approach.

Recommendations:

Alternate the order of Windows and Linux instructions, or present them in parallel (side-by-side tabs or sections) to avoid implying priority.
For uninstall steps, provide CLI-based instructions for Windows (e.g., using PowerShell or command prompt) in addition to GUI steps, to match the CLI focus of Linux instructions.
Avoid referencing Windows-specific folder paths or tools (like Control Panel) without providing Linux equivalents or context.
Where possible, generalize instructions or explicitly state that steps apply to both Windows and Linux, only diverging where necessary.
Consider adding a summary table comparing Windows and Linux steps for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several ways: Windows terminology and tools (e.g., 'Download Executable', registry edits, Windows Explorer/File Explorer) are often mentioned before or in more detail than their Linux equivalents. Powershell and Windows-specific troubleshooting steps are prominent, while Linux steps are sometimes less detailed or appear after Windows instructions. Some advanced Windows scenarios (like registry edits for iSCSI timeouts) are described in depth, while Linux equivalents are less emphasized or missing. The 'Next steps' section also lists PowerShell before Azure CLI, reinforcing the Windows-first pattern.

Recommendations:

Ensure Linux instructions and troubleshooting steps are as detailed and prominent as Windows ones, especially for advanced scenarios (e.g., provide more in-depth guidance for Linux iSCSI/RAID/LVM troubleshooting).
Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
Include Linux CLI examples and tools (e.g., show how to browse and copy files using common Linux file managers or CLI commands, not just Windows Explorer).
In 'Next steps', alternate the order of PowerShell and CLI links, or group them by platform to avoid reinforcing a Windows-first impression.
Where Windows registry edits are described, provide equivalent Linux configuration file changes (e.g., for iSCSI timeouts) with equal prominence and explanation.
Use neutral language and headings (e.g., 'For Windows and Linux' or 'Platform-specific steps') to avoid implying Windows is the default or primary platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias primarily through its references to Windows-specific tools (such as the Storage Emulator), lack of explicit Linux alternatives or parity in certain steps, and the ordering of instructions that may implicitly favor Windows users. While the main development workflow is cross-platform (using Azure CLI and Azure Functions Core Tools), there are notable areas where Linux users are underserved or must infer their own solutions.

Recommendations:

Where the Storage Emulator is referenced, explicitly mention and provide instructions for the cross-platform Azurite emulator, which is the recommended storage emulator for Linux and macOS.
When discussing browser compatibility (e.g., suggesting Edge), clarify that any modern browser can be used and avoid recommending a Windows-specific browser unless necessary.
In steps that mention file path handling or project file modifications (such as .csproj updates for static content), add notes or examples for Linux/macOS users, especially regarding case sensitivity and path separators.
Ensure that all prerequisite tools and installation instructions are clearly marked as cross-platform, and provide links or commands for Linux/macOS where relevant (e.g., for installing Azure Functions Core Tools or the Azure CLI).
Review all command-line examples to ensure they work identically on Linux/macOS, and add troubleshooting notes for common platform-specific issues (such as file permissions or environment variables).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by listing Azure PowerShell as a primary method for backup/restore operations in the 'Next steps' section, sometimes before or alongside Azure CLI, and never mentioning Bash, Linux shell, or kubectl-native workflows. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify parity or differences between Windows and Linux environments for AKS backup operations.

Recommendations:

Ensure that all example commands and references include both Azure CLI (cross-platform) and Azure PowerShell, with CLI listed first to reflect its cross-platform nature.
Explicitly mention that all operations can be performed from Linux, macOS, and Windows environments, and clarify any OS-specific requirements or differences.
Where possible, provide kubectl-native or Bash shell examples for common tasks, especially for AKS users who may be operating from Linux-based environments.
In the 'Next steps' section, list Azure CLI before PowerShell, and add links or notes for Linux/macOS users.
Add a brief section or note confirming that all prerequisites and operations are supported equally on Linux, macOS, and Windows, or detail any exceptions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows environments, specifically using Data Protection Manager (DPM), which is a Windows-only tool. All instructions, screenshots, and workflows assume the use of Windows Server, Windows-based SQL Server, and Windows authentication patterns (e.g., NTAuthority\System). There are no examples or guidance for Linux-based SQL Server deployments, nor are any Linux tools or commands mentioned.

Recommendations:

Add a section or parallel guide for backing up SQL Server on Linux to Azure, using supported tools (e.g., Azure Backup integration with Linux, or native SQL Server backup to Azure Blob Storage).
Explicitly state that DPM is a Windows-only solution and provide links or references to Linux-compatible backup solutions for SQL Server.
Include examples, prerequisites, and screenshots for Linux environments where possible, or clarify the scope of the article as Windows-only at the outset.
Mention alternative backup and recovery workflows for SQL Server on Linux, such as using sqlcmd, bash scripts, or Azure CLI.
If Azure Backup supports Linux SQL Server workloads, provide step-by-step instructions for those scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools, UI elements, and features (such as Volume Shadow Copy Service, Data Deduplication, and the MABS console), and by omitting any Linux-specific instructions or examples. There is no mention of Linux client support, installation, or recovery procedures, nor are any Linux command-line or UI examples provided.

Recommendations:

Include explicit instructions and examples for backing up and recovering file data from Linux machines, if supported by MABS.
Document the process for installing the MABS protection agent on Linux systems, including any required dependencies or configuration steps.
Provide parity in examples: for every Windows UI workflow, offer equivalent Linux command-line or UI steps.
Clarify any limitations or unsupported features for Linux clients (e.g., if VSS or Data Deduplication is not available on Linux, state this clearly).
Reference Linux-native backup and recovery tools or methods where appropriate, and explain how they integrate with MABS.
If Linux is not supported, explicitly state this in the prerequisites or supported platforms section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS), which is itself a Windows-based solution. Linux is only briefly mentioned as a supported guest OS for file-consistent backups, with no detailed instructions or examples. All procedures, prerequisites, and recovery steps are described exclusively in the context of Windows tools, roles, and patterns (e.g., VSS, SCSI controllers, registry keys, Windows authentication methods, and Windows Server roles). There are no Linux command-line examples, nor any mention of Linux-specific backup or recovery nuances beyond a single line in the prerequisites table.

Recommendations:

Add explicit Linux guest backup and recovery examples, including step-by-step instructions for both backup and restore operations involving Linux VMs.
Clarify any limitations or differences in backup and recovery workflows for Linux VMs, such as the lack of application-consistent backups or item-level recovery.
Provide Linux-specific troubleshooting tips and best practices, including how to verify backup consistency and restore files within Linux VMs.
Include examples of how to interact with MABS from Linux environments, if supported (e.g., via SMB/NFS shares, agent installation, or command-line tools).
Balance the documentation by introducing Linux scenarios earlier and more prominently, rather than as a brief note in a prerequisites table.
If MABS does not support certain Linux features, clearly state these limitations and suggest alternative solutions or workarounds.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell scripts as the primary or default method for granting privileges to database users, both in the prerequisites and during the backup configuration flow. While it briefly mentions alternatives like PG admin or PSQL tool, these are listed after PowerShell and without any concrete examples or guidance. No Linux-specific or cross-platform command-line examples are provided, and the documentation assumes familiarity with Windows-centric tools and workflows.

Recommendations:

Provide equivalent Linux/bash/psql command examples alongside PowerShell scripts for all privilege-granting and configuration steps.
List cross-platform or Linux-native tools (such as psql or bash scripts) before or alongside PowerShell, not only as an afterthought.
Include explicit instructions or code snippets for using psql or PG admin to grant privileges, ensuring Linux users have clear, actionable guidance.
Clarify that all steps can be performed from Linux or macOS environments, and highlight any differences or requirements for non-Windows users.
Where ARM templates or Azure CLI are referenced, ensure examples are platform-agnostic and not reliant on Windows-specific tooling.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a clear Windows bias. It focuses heavily on Windows-centric backup tools (MARS agent, DPM, MABS), provides detailed architectural explanations only for Windows/on-premises Windows Server scenarios, and lacks equivalent Linux backup workflows or examples. Linux is mentioned only to state that certain features are unsupported. The documentation also introduces Windows tools and patterns first, with little to no mention of Linux-native backup agents or processes.

Recommendations:

Add explicit Linux backup scenarios and workflows, including supported agents or third-party options for on-premises Linux machines.
Provide architectural diagrams and step-by-step processes for Linux backup, similar to the detailed Windows/MARS agent sections.
Include Linux command-line examples and tools where relevant, not just Windows or PowerShell-based instructions.
Clarify Linux support limitations up front, and link to alternative solutions or roadmap items for Linux parity.
Ensure that tables and feature matrices indicate Linux support status, and avoid presenting Windows-only tools as the default or only option.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references System Center Data Protection Manager (DPM), a Windows-only backup solution, and provides instructions and screenshots for a Windows GUI workflow. There are no Linux equivalents, examples, or alternative tools mentioned. All prerequisite steps and tooling (e.g., ConfigureSharePoint.exe) are Windows-specific, and the documentation assumes a Windows environment throughout.

Recommendations:

Acknowledge that DPM is a Windows-only tool and clarify this limitation early in the documentation.
Provide information or links to alternative solutions for backing up SharePoint data from Linux environments, if any exist.
If Azure Backup supports Linux-based backup agents or third-party tools for SharePoint or similar workloads, include examples or references.
Where possible, offer parity by mentioning command-line or scriptable options (e.g., PowerShell, CLI) and note if these are Windows-only.
Add a section explicitly addressing Linux/Unix users, outlining their options or the lack thereof.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. In the discussion of Azure Disk Encryption (ADE), BitLocker (a Windows-specific tool) is mentioned before DM-Crypt (the Linux equivalent), and the explanation of TDE-encrypted database restores links to SQL Server (a Microsoft/Windows-centric product) without mentioning cross-platform or Linux SQL options. There are no Linux-specific command examples or references to Linux tooling, and the documentation implicitly assumes familiarity with Windows technologies.

Recommendations:

When mentioning Azure Disk Encryption, present DM-Crypt (Linux) and BitLocker (Windows) with equal prominence, or alternate the order in which they are listed.
Include explicit examples or references for both Windows and Linux scenarios, such as command-line instructions or links to relevant Linux documentation.
Where SQL Server is referenced, clarify support for cross-platform (Linux) SQL Server deployments and provide links or notes for Linux-specific procedures.
Review all sections to ensure Linux tools and workflows are described with the same detail and priority as Windows equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, focusing exclusively on System Center Data Protection Manager (DPM), a Windows-only product. All instructions, requirements, and tooling (such as the use of Windows PowerShell, .NET Framework, and .exe installers) are specific to Windows environments. There are no Linux equivalents, examples, or mentions of cross-platform support. The documentation assumes the reader is operating in a Windows ecosystem and does not address Linux-based backup scenarios or tools.

Recommendations:

Clearly state at the beginning that DPM is a Windows-only product, and provide links to equivalent Azure Backup documentation for Linux environments.
Where possible, mention or link to Azure Backup solutions and agents for Linux, such as the MARS agent for Linux or Azure VM backup for Linux VMs.
If relevant, provide parallel instructions or references for Linux-based backup scenarios, or clarify that the described steps are not applicable to Linux.
Avoid assuming the presence of Windows-only components (e.g., PowerShell, .NET Framework) without noting their platform specificity.
Include a comparison table or section outlining backup options for both Windows and Linux workloads in Azure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as a primary automation method for configuring permissions and restoring encrypted VMs, without mentioning or providing equivalent examples for Linux environments (such as Azure CLI or Bash scripts). There are no Linux-specific instructions or parity in tooling references, and the only command-line example given is PowerShell.

Recommendations:

Include Azure CLI and/or Bash script examples alongside PowerShell for all automation steps, especially for configuring permissions and restoring VMs.
Explicitly mention that steps can be performed from both Windows and Linux environments, and provide links or references to Linux-compatible tools.
Add a section or callouts for Linux users, ensuring that all procedures are accessible regardless of the administrator's operating system.
Review all references to ensure that Windows tools are not presented as the default or only option.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes backup and recovery procedures for Microsoft Exchange using Microsoft Azure Backup Server (MABS), a Windows-only tool. All instructions, screenshots, and file paths are Windows-centric (e.g., referencing C:\Program Files), and there are no mentions of Linux equivalents, support, or examples. The documentation assumes the use of Windows-based Exchange servers and does not address scenarios for Linux environments.

Recommendations:

Explicitly state that MABS and Exchange Server are Windows-only, if that is the case, to clarify platform limitations.
If Azure Backup supports Linux-based workloads or other cross-platform backup scenarios, provide parallel documentation or links for those cases.
Include a section on backing up Linux servers or applications with Azure Backup, if supported, to ensure Linux parity.
Where possible, mention alternative tools or approaches for Linux environments, such as Azure Backup integration with Linux VMs or third-party solutions.
Avoid hardcoding Windows paths and terminology unless the product is strictly Windows-only; otherwise, provide Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (such as 'net stop dpmra'), Windows service management patterns, and concepts like NT AUTHORITY\SYSTEM. There are no examples or troubleshooting steps for Linux systems, nor any mention of Linux equivalents or cross-platform considerations. The documentation assumes the use of Windows throughout.

Recommendations:

Include troubleshooting steps and examples for Linux-based backup agents or workloads, if supported.
When referencing service management (e.g., restarting services), provide both Windows (e.g., 'net stop dpmra') and Linux (e.g., 'systemctl restart <service>') equivalents.
Clarify whether Data Protection Manager is Windows-only, or explicitly state platform limitations at the start of the documentation.
If Linux workloads or agents are supported, add sections or notes for Linux-specific errors, logs, and commands.
Avoid assuming Windows-specific user accounts (e.g., NT AUTHORITY\SYSTEM) without mentioning Linux alternatives or stating that this is Windows-only.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed instructions and examples for managing soft delete of VM backups using the Azure portal and Azure PowerShell, but does not mention or provide examples for Linux CLI tools (such as Azure CLI), Bash scripting, or Linux-specific workflows. PowerShell is featured exclusively in the automation section, and there are no Linux command-line equivalents or parity in the examples.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell operations (delete, undelete, resume backup) to support Linux and cross-platform users.
Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links or code snippets.
Where automation is discussed, provide both PowerShell and Bash (with Azure CLI) script examples.
Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing right-click if not applicable cross-platform).
Include a section or note on cross-platform compatibility and tool choice for users on non-Windows systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is the only scripting example given in detail for moving Recovery Services vaults, with no equivalent Bash or Linux shell script provided. The CLI section is present but less detailed and lacks context or troubleshooting guidance. Throughout the document, Windows-specific instructions (such as installing Windows updates) are mentioned before Linux equivalents, and Linux guidance is less explicit or refers users to external distributor documentation. There are no Linux-specific command-line or automation examples.

Recommendations:

Provide Bash or Linux shell script examples for moving Recovery Services vaults, especially for common automation scenarios.
Expand the Azure CLI section to include more detailed steps, troubleshooting, and context, matching the depth of the PowerShell section.
When mentioning OS-specific prerequisites (e.g., updating certificates), give equal detail for Linux, including example commands for popular distributions (e.g., apt, yum, zypper).
Ensure that Linux tools and workflows are mentioned alongside Windows tools, not just as a reference to distributor documentation.
Consider including a table or section that summarizes equivalent commands and steps for Windows (PowerShell), Linux (Bash/CLI), and possibly MacOS where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Windows troubleshooting steps are often presented first and in greater detail, with explicit GUI walkthroughs (e.g., Server Manager, Disk Management, ISCSI initiator Properties). Windows-specific tools and error codes (e.g., deduplication, 0x80070780) are mentioned without Linux equivalents. Linux troubleshooting is generally referenced via links to other articles, with fewer in-place step-by-step instructions or screenshots. Some Linux scenarios lack direct examples or detailed guidance, especially for common tasks like mounting volumes or handling deduplication.

Recommendations:

Provide Linux troubleshooting steps alongside Windows, not just as links but with in-place, step-by-step instructions and screenshots.
Include Linux equivalents for all Windows tools and error codes (e.g., show how to check and mount disks using lsblk, mount, or parted; address deduplication or file access errors on Linux).
Balance the order of presentation: alternate or parallelize Windows and Linux sections, or clearly separate them under OS-specific headings.
Add Linux-specific error messages and their resolutions where only Windows errors are currently described.
Where GUI steps are given for Windows, provide equivalent CLI or GUI steps for common Linux desktop environments (e.g., using GNOME Disks, KDE Partition Manager, or command-line tools).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload extension, NT Service accounts), and does not mention or provide guidance for SQL Server on Linux VMs. There are no examples or notes for Linux-based SQL Server VMs, and the process described assumes a Windows environment throughout.

Recommendations:

Explicitly state whether the described process applies only to Windows-based SQL Server VMs or also to Linux-based ones.
If Linux-based SQL Server VMs are supported, provide equivalent instructions, examples, and screenshots for configuring Azure Backup on Linux VMs.
Mention and document any Linux-specific requirements, extensions, or limitations (e.g., use of different agents, service accounts, or backup plugins).
If Linux is not supported for this feature, add a clear note at the beginning of the article to inform users.
Ensure parity in terminology and step-by-step guidance for both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is exclusively focused on backing up Windows Server system state using Azure Backup. All instructions, screenshots, and tools (such as the Microsoft Azure Recovery Services (MARS) Agent) are Windows-specific. There are no references to Linux systems, Linux backup tools, or cross-platform alternatives. The workflow, terminology, and examples are tailored entirely to Windows environments, with no mention of how to achieve similar outcomes on Linux or other operating systems.

Recommendations:

Add a section or a separate article explaining how to back up Linux system state or equivalent using Azure Backup, if supported.
Include Linux-specific tools, commands, and examples (e.g., using Azure CLI, shell scripts, or Linux backup agents).
If Azure Backup does not support Linux system state backup, clearly state this limitation at the beginning of the article and provide links to alternative solutions for Linux.
Ensure parity in documentation structure and detail for both Windows and Linux backup scenarios, including screenshots, step-by-step guides, and troubleshooting tips.
Avoid using Windows terminology (e.g., 'System State', 'MARSAgentInstaller.exe') exclusively; provide Linux equivalents or clarify OS-specific concepts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and tool recommendations are specific to Windows environments. Windows tools like Performance Monitor are mentioned exclusively, and all file paths and agent references are Windows-specific. There are no Linux equivalents or examples provided, and the language assumes the user is operating in a Windows environment.

Recommendations:

Add troubleshooting steps and examples for Linux environments, including relevant commands and log file locations.
Mention and explain Linux equivalents for Windows tools (e.g., using 'iostat', 'vmstat', 'top', or 'htop' for performance monitoring instead of Performance Monitor).
Provide Linux file paths and agent installation instructions where applicable.
Clarify whether the Azure Backup agent or MARS agent is supported on Linux, and if not, direct Linux users to the appropriate Azure Backup solutions (such as Azure Backup for Linux VMs or Azure Backup Server).
Ensure that all recommendations and troubleshooting steps are presented for both Windows and Linux, or clearly state platform limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell examples before CLI examples, using Windows-centric tooling (PowerShell cmdlets), and offering more step-by-step guidance for PowerShell users. The CLI section is less detailed and lacks parity in explanation and context. There are no explicit Linux-specific examples or references to Linux shell environments, and the documentation assumes familiarity with Windows tools and patterns.

Recommendations:

Provide Linux shell (bash) equivalents for all PowerShell examples, especially for tasks like date/time manipulation and JSON policy creation.
Ensure CLI examples are as detailed as PowerShell ones, including step-by-step breakdowns and explanations of parameters.
Explicitly mention compatibility and usage on Linux/macOS platforms, including any prerequisites or differences in behavior.
Add notes or examples for common Linux tools (e.g., jq for JSON manipulation, date for time handling) where relevant.
Reorder sections or present CLI and PowerShell examples side-by-side to avoid the perception of Windows-first bias.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-style file paths (e.g., C:\SQLfiles\Default.ldf), using SQL Server (primarily a Windows workload) as the example, and omitting any mention of Linux-based SQL Server VMs or Linux file path conventions. There are no examples or notes for restoring SQL Server databases on Linux VMs, and all directory path examples use Windows syntax. No Linux tools, patterns, or considerations are mentioned.

Recommendations:

Include examples of restoring SQL Server databases on Linux-based Azure VMs, using Linux file path conventions (e.g., /var/opt/mssql/data/).
Add notes or sections that clarify any differences or additional steps required for SQL Server on Linux VMs.
Where file paths are shown (such as in alternateDirectoryPaths), provide both Windows and Linux examples side by side.
Explicitly state whether the documented process is supported and tested for both Windows and Linux SQL Server VMs, and highlight any OS-specific limitations.
If PowerShell or Windows-specific tooling is referenced elsewhere, ensure parity by including Bash/CLI or Linux-native alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and CLI versions for standard policy support, mentioning PowerShell before CLI, and not providing explicit Linux or cross-platform command-line examples. The only non-portal automation path mentioned is through Azure CLI and PowerShell, but no Linux shell or bash-specific guidance is given. The documentation also lacks screenshots or instructions for Linux environments, focusing exclusively on the Azure Portal UI (which is platform-agnostic but often associated with Windows workflows in Azure documentation).

Recommendations:

Provide explicit Linux/bash command-line examples for migration operations, including sample az CLI commands with Linux shell syntax.
When referencing automation tools, mention CLI before PowerShell or present both together to avoid Windows-first ordering.
Include notes or links to Linux-specific guidance or troubleshooting, especially for users managing Azure from Linux environments.
Add clarification that the Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide sample usage in a Linux terminal context.
If possible, include screenshots or terminal output from Linux environments to reinforce parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only PowerShell-based (Windows-centric) examples for configuring snapshot retention, with no equivalent CLI or Linux-native instructions. The only automation example is in PowerShell, and there is no mention of Azure CLI, Bash, or cross-platform scripting options. This may lead Linux or cross-platform administrators to feel unsupported or unclear about how to perform these tasks without Windows tools.

Recommendations:

Add equivalent Azure CLI examples for configuring snapshot retention and other operations, as Azure CLI is cross-platform and widely used on Linux.
Include Bash script examples or references for common tasks, ensuring parity with PowerShell instructions.
When presenting automation or scripting options, list Azure CLI (or Bash) before or alongside PowerShell to avoid the impression of Windows-first bias.
Explicitly mention that all features are available regardless of the OS used for management, and provide links to relevant cross-platform tooling documentation.
Consider a section or note highlighting cross-platform management options for Azure Backup, including links to both PowerShell and CLI documentation.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, tools, screenshots, and command-line examples are specific to Windows environments (e.g., Windows Server Backup, wbadmin, MARS agent, Windows Recovery Environment). There are no references to Linux systems, Linux tools, or cross-platform considerations. The documentation assumes the reader is operating in a Windows-only context.

Recommendations:

If Azure Backup supports similar system state or configuration backup/restore for Linux servers, add equivalent sections and walkthroughs for Linux, including relevant tools (e.g., rsync, tar, Timeshift, or native Azure Linux backup agents).
If Linux system state backup is not supported, clearly state this limitation at the beginning of the article to set expectations for cross-platform users.
Where possible, provide parity in troubleshooting and recovery guidance for Linux environments, or link to relevant Linux documentation.
Consider restructuring the documentation or titling it more explicitly as 'Restore System State to a Windows Server (Windows Only)' to avoid confusion for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes backup and recovery using Azure Backup Server, which is a Windows-based tool, and all instructions reference a GUI workflow typical of Windows environments. There are no examples or guidance for Linux-based VMs, command-line workflows, or cross-platform backup tools. The documentation assumes the use of Windows patterns and tools throughout, with no mention of Linux equivalents or considerations.

Recommendations:

Add explicit guidance for backing up and recovering files from Linux-based Azure Stack VMs, including any supported tools or agent installation steps.
Include CLI-based examples (e.g., using Azure CLI, Bash scripts, or relevant Linux backup agents) alongside or in place of GUI walkthroughs.
Mention any limitations or requirements for Linux VM backup and recovery with Azure Backup Server, and provide links to Linux-specific documentation if available.
If Azure Backup Server does not support Linux VMs, clearly state this and suggest alternative backup strategies or tools for Linux workloads.
Ensure parity in documentation structure and detail for both Windows and Linux environments, including troubleshooting and recovery scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, referencing Windows-centric tools and cmdlets, and omitting any Linux-native CLI (such as Azure CLI/bash) examples. The structure and order of examples prioritize PowerShell after the portal, with no mention of Linux shell usage or cross-platform scripting approaches. This may hinder accessibility for Linux users or those preferring non-Windows environments.

Recommendations:

Add Azure CLI (az) command examples alongside PowerShell for all command-line instructions, especially for enabling/disabling soft delete and managing backup items.
Explicitly mention that PowerShell examples are cross-platform only if true, or clarify if they require Windows.
Include bash/shell script snippets where appropriate to demonstrate parity for Linux users.
Reorder or parallelize the presentation of PowerShell and Azure CLI examples to avoid implicit prioritization of Windows tools.
Reference Linux-compatible tooling and workflows in the prerequisites and throughout the documentation.
Add a note or section addressing cross-platform support and best practices for both Windows and Linux administrators.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerShell/MSAL.PS examples for obtaining OAuth tokens, but does not include equivalent Linux-native or cross-platform command-line examples (e.g., curl, Python, or bash). The focus on PowerShell and the MSAL.PS module, which is Windows-centric, may disadvantage Linux or macOS users. There is also a lack of explicit Linux or cross-platform guidance for authentication flows.

Recommendations:

Add examples using curl or HTTPie to demonstrate how to obtain OAuth tokens from the command line on Linux/macOS.
Include a Python example using MSAL or requests to show cross-platform programmatic authentication.
Explicitly mention that Azure CLI is cross-platform and provide more detailed CLI-based authentication flows.
Where PowerShell is used, provide equivalent bash or shell script examples for Linux users.
Review all sections for Windows-specific terminology or tool references and ensure Linux alternatives are presented with equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently listing PowerShell as the primary non-portal client, mentioning it before Azure CLI and REST API. The term 'PowerShell' is highlighted in multiple places, and there are references to Windows-centric backup agents and tools (e.g., Azure Backup Agent, DPM, Azure Backup Server) without equivalent Linux-focused examples or tools. There are no explicit Linux command-line examples or references to Linux-native tooling, and the documentation does not provide parity in guidance for Linux administrators.

Recommendations:

Provide explicit Linux/Unix examples using Azure CLI and Bash scripts alongside PowerShell examples.
Mention Azure CLI before or alongside PowerShell when listing non-portal clients to avoid the impression of Windows-first tooling.
Include references to Linux-supported backup agents or clarify cross-platform compatibility where relevant.
Add sample monitoring and alerting workflows tailored for Linux environments, such as integrating with Linux-native notification systems or scripts.
Ensure that documentation for custom dashboards and automation includes both PowerShell and CLI/Bash script examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. All examples, instructions, and screenshots assume SQL Server is running on Windows. Only Windows authentication, Windows service accounts (NT SERVICE, NT AUTHORITY), Windows file paths, and Windows tools (SSMS, PowerShell, Task Manager, SMB shares) are referenced. There are no instructions, examples, or notes for running SQL Server on Linux VMs, nor for using Linux-native tools or authentication methods.

Recommendations:

Add explicit guidance and examples for SQL Server on Linux VMs, including any differences in agent installation, permissions, and backup configuration.
Include Linux command-line equivalents (e.g., using sqlcmd, systemctl, chown/chmod for permissions) alongside PowerShell and SSMS instructions.
Document how to configure service accounts or required permissions on Linux (e.g., using system users or sudoers) instead of only referencing Windows service accounts.
Provide Linux file path examples and instructions for configuring local backup folders and permissions.
Clarify any limitations or differences in Azure Backup support for SQL Server on Linux, and link to relevant Linux-specific documentation if available.
Ensure that REST API and portal instructions are platform-agnostic or note any platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All examples, workflows, and tool references are specific to Windows Server, Windows Server Backup, and PowerShell cmdlets. There is no mention of Linux support, Linux backup workflows, or equivalent Linux tools. The documentation assumes the reader is operating in a Windows-only environment, with no guidance for Linux systems or cross-platform scenarios.

Recommendations:

Clearly state at the beginning whether Azure Backup Server supports Linux system state and bare-metal recovery, and if not, provide links to Linux backup documentation.
If Linux is supported, include equivalent Linux backup and recovery workflows, referencing tools such as rsync, tar, dd, or native Linux backup solutions.
Provide Linux command-line examples alongside PowerShell and Windows Server Backup commands.
Mention Linux-specific prerequisites, limitations, and supported distributions if applicable.
Ensure parity in the documentation structure: for every Windows-specific section, provide a Linux equivalent or explicitly note if not supported.
If Azure Backup Server is Windows-only for system state/BMR, add a clear note and suggest alternative Azure/Linux backup solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All instructions, prerequisites, and examples assume the use of Windows Server (specifically Windows Server 2019/2022), Windows file paths (C:\, D:\), Windows domain membership, and Windows-specific tools (e.g., PowerShell cmdlets, Windows Update, .NET Framework). There are no references to Linux-based installations, tools, or alternative workflows, and no mention of Linux compatibility or support.

Recommendations:

Clearly state at the beginning whether Azure Backup Server supports only Windows or if Linux is also supported. If Linux is not supported, explicitly mention this to set expectations.
If Linux is supported, provide equivalent installation and configuration instructions for Linux environments, including prerequisites, file paths, and commands.
Include Linux-based examples for network connectivity checks, such as using curl, wget, or other Linux-native tools, in addition to the PowerShell cmdlet.
Mention Linux equivalents for domain joining (e.g., joining to Active Directory via realmd/sssd) if applicable.
Reference Linux-compatible backup agents or tools if Azure Backup Server can protect Linux workloads, and provide links to relevant documentation.
Avoid using only Windows terminology (e.g., C:\, D:\, Windows Update) or provide Linux alternatives where possible.
If the product is Windows-only, consider providing guidance for Linux workload protection using other Azure Backup solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page for Azure Backup Server v4 demonstrates a strong Windows bias. Windows workloads, tools, and patterns are presented first and in detail, while Linux support is minimal and only described in the context of being a guest VM on Windows-based hypervisors. There are no Linux-specific backup scenarios, examples, or tooling mentioned. Windows-specific technologies (e.g., NTFS, VSS, system state, bare metal recovery) and requirements are referenced throughout, with little to no equivalent Linux guidance.

Recommendations:

Provide explicit Linux backup scenarios, including agent-based backup for native Linux workloads (not just as VMs on Windows hosts).
Include Linux-specific examples and workflows, such as file-level recovery for Linux VMs, supported file systems, and backup/restore procedures.
Mention Linux tools and patterns (e.g., integration with LVM snapshots, ext4/xfs support, Linux-specific restore options) where relevant.
Balance the order of presentation: introduce Linux and Windows support in parallel where possible, rather than always listing Windows first.
Clarify any limitations or differences in Linux support (e.g., snapshot consistency, supported distributions) in the same detail as for Windows.
If PowerShell or Windows-specific tools are referenced, provide equivalent Linux command-line or scripting examples where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page primarily focuses on using the Azure portal for backup operations and only briefly mentions automation via PowerShell and CLI, with PowerShell listed first. There are no explicit Linux-specific examples or references to Linux tools or shell environments. The 'Next steps' section lists PowerShell before CLI, and there is no mention of Bash, Linux shell, or cross-platform scripting considerations. This ordering and lack of Linux-specific guidance may suggest a Windows-first or PowerShell-heavy bias.

Recommendations:

When mentioning automation or scripting, list Azure CLI before or alongside PowerShell to reflect cross-platform parity.
Include explicit Bash/Linux shell examples or references, especially in automation contexts.
Clarify that both PowerShell and CLI are cross-platform, and provide links or notes for Linux/macOS users.
Add a section or callout for Linux administrators, highlighting any platform-specific considerations or best practices.
Ensure that all referenced scripts or templates are available in both PowerShell and Bash/CLI formats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is exclusively focused on Windows environments, with all examples, tools, and troubleshooting steps tailored to Windows servers. Only Windows tools (PowerShell, Server Manager, wbadmin, Windows Server Backup) are mentioned, and there are no references or examples for Linux systems or their equivalents. The structure and language assume a Windows-only context, and Linux users are not addressed.

Recommendations:

If System State Backup is not supported on Linux, explicitly state this early in the documentation to set user expectations.
If similar backup or troubleshooting functionality exists for Linux, provide parallel sections or links to Linux-specific documentation.
Where possible, mention cross-platform tools or alternatives, or clarify the scope is strictly for Windows.
Add a comparison table or note outlining differences in backup approaches between Windows and Linux environments, if relevant.
Ensure future documentation on backup and recovery covers both Windows and Linux scenarios, or clearly separates them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All instructions, screenshots, and terminology are specific to Windows (e.g., 'Microsoft Azure Backup' snap-in, references to Windows OS versions, and Windows-style file paths). There are no examples, instructions, or even mentions of Linux or cross-platform usage, and the MARS Agent is presented as a Windows-only tool.

Recommendations:

Explicitly state in the introduction whether the MARS Agent supports Linux, and if not, provide links to equivalent Linux backup/restore documentation.
If Linux is supported, add parallel instructions and screenshots for Linux environments, including command-line examples (e.g., Bash) and Linux-native tools.
Avoid Windows-specific terminology where possible, or provide Linux equivalents alongside (e.g., refer to 'machines' or 'servers' rather than only Windows computers).
Include a section or note clarifying platform support and guiding non-Windows users to appropriate resources.
If the product is Windows-only, make this clear early in the documentation to set expectations and avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All examples, tools, and procedures assume a Windows Server context, including the use of Windows command prompts, Windows-specific tools (like ConfigureSharePoint.exe, Registry Editor, and CMD commands), and Windows filesystem paths. There is no mention of Linux support, nor are there any examples or guidance for Linux-based environments. The documentation assumes the use of Windows authentication and permissions models, and all screenshots and UI references are for Windows-only applications.

Recommendations:

Explicitly state whether Linux-based SharePoint deployments are supported or not. If not, clarify this early in the documentation.
If Linux is supported, provide parallel instructions for Linux environments, including command-line examples, file paths, and permission settings.
Include information about cross-platform compatibility for MABS and SharePoint, or provide links to Linux-specific backup solutions if MABS is Windows-only.
Avoid assuming Windows-only tools and patterns; where possible, mention equivalent Linux tools or note their absence.
Add a section on prerequisites and limitations that clearly addresses OS support and any platform-specific constraints.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows resources and examples over Linux. In the 'Deploy a protected VM using a Resource Manager template' section, only a Windows VM template is linked, with no equivalent Linux example. Additionally, PowerShell is referenced for automation, but there is no mention of CLI or Bash alternatives. While both Windows and Linux quick-create links are provided in step 3, subsequent examples and automation guidance focus on Windows or Windows-centric tools.

Recommendations:

Provide equivalent Linux Resource Manager template links for deploying and backing up Linux VMs.
Include Azure CLI and Bash script examples alongside PowerShell for automation tasks, such as configuring the Azure Backup resource group.
Ensure that all automation and scripting references include both Windows and Linux approaches, or clearly indicate cross-platform options.
When listing instructions or examples, alternate the order or present Windows and Linux options side by side to avoid 'windows_first' bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All deployment and management instructions are provided exclusively using Azure PowerShell, with no Azure CLI or Bash examples. The Bicep template provisions only Windows VMs, and the allowed OS versions are all Windows Server variants. There is no mention of Linux VM deployment, nor are there instructions for Linux users or cross-platform tooling. The clean-up and backup monitoring steps also reference only PowerShell cmdlets.

Recommendations:

Add Azure CLI/Bash examples for deploying the Bicep template, including Cloud Shell Bash instructions.
Provide a Bicep template or parameterization for deploying Linux VMs (e.g., Ubuntu, CentOS) alongside or instead of Windows.
Include Linux VM OS options in the Bicep template's allowed values and document how to select them.
Offer clean-up and backup management instructions using Azure CLI commands, not just PowerShell.
Rephrase instructions to be platform-neutral where possible, and mention both Windows and Linux workflows.
Ensure links to further reading or tutorials include Linux/CLI options, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for retrieving VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/CLI/bash examples. The deployment options also list PowerShell and Visual Studio before mentioning templates, with no mention of Azure CLI or Linux-native workflows.

Recommendations:

Add equivalent Azure CLI (az) and/or Bash examples alongside PowerShell scripts for listing available VM sizes.
Explicitly mention and provide examples for Linux users, such as using Azure CLI on Linux or macOS.
In the 'Next steps' section, list cross-platform tools (e.g., Azure CLI, ARM/Bicep templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Where possible, clarify that the service definition file and deployment process are OS-agnostic, and provide links to Linux/macOS documentation if available.
Consider including a table or section that maps common Windows tools/workflows to their Linux equivalents for Azure Cloud Services (extended support).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, terminology, and screenshots are based on the Windows GUI and Windows-specific concepts (e.g., NTAuthority\System, MMC-style wizards, 'blades', and right-click context menus). There are no examples, instructions, or even mentions of Linux-based SQL Server deployments or backup workflows, nor are any Linux command-line or tool alternatives provided.

Recommendations:

Explicitly state that MABS is a Windows-only solution and clarify support limitations for Linux-based SQL Server deployments.
If Azure Backup supports Linux SQL Server (even partially), provide equivalent instructions, examples, and screenshots for Linux environments, including command-line (bash) workflows.
Mention and link to any Azure-native or cross-platform backup solutions that support Linux SQL Server, or clarify if none exist.
Where possible, use neutral terminology (e.g., 'system account' instead of 'NTAuthority\System') and provide Linux equivalents (e.g., 'root' or relevant service accounts).
Add a section or note addressing Linux users, outlining their options or limitations for SQL Server backup on Azure Stack.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively demonstrates authentication using the .NET library and the C# AccountManagement sample, both of which are Windows-centric. There are no Linux or cross-platform code examples, nor is there mention of Linux-specific tools or workflows. The Azure portal instructions and terminology (e.g., 'Windows Azure Service Management API') further reinforce a Windows-first perspective.

Recommendations:

Provide equivalent code samples in cross-platform languages (e.g., Python, Java) using their respective Azure SDKs.
Include instructions or references for registering and authenticating applications using CLI tools available on Linux, such as Azure CLI or PowerShell Core (cross-platform).
Mention and demonstrate how to run the sample or equivalent workflows on Linux or macOS environments.
Avoid using 'Windows' in API names or instructions unless strictly necessary, and clarify when something is cross-platform.
Add a section or links for Linux users, covering authentication and application registration steps relevant to their environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation consistently lists PowerShell as the first automation method, with extensive PowerShell support and example links for nearly every operation. PowerShell is a Windows-centric tool, and its prominence throughout the support matrix (often before CLI or REST) suggests a Windows-first approach. While Azure CLI is also supported (and cross-platform), the documentation does not highlight Linux-native scripting or tools, and there are no bash/shell script examples or explicit Linux guidance. The focus on PowerShell and the absence of Linux-specific automation patterns or examples indicate a bias toward Windows environments.

Recommendations:

Alternate the order of PowerShell and CLI columns or list CLI first in some tables to avoid implicit prioritization of Windows tools.
Add explicit bash/shell script examples for common automation tasks, especially where CLI is supported, to demonstrate Linux parity.
Include a section or callout on cross-platform automation, highlighting how Linux users can accomplish the same tasks using Azure CLI, REST, or scripting.
Where PowerShell is referenced, clarify that Azure CLI is fully supported on Linux and provide direct links to Linux-specific documentation or tutorials.
Consider adding a 'Linux automation' or 'Cross-platform automation' row or column to the support matrix to make Linux support more visible.
Review example links to ensure they include both PowerShell and CLI (bash) tabs or code blocks, not just PowerShell.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and tooling references are Windows-specific, with no mention of Linux or cross-platform support. Windows tools and patterns (such as registry edits, MMC, PowerShell, DISM.exe) are referenced throughout, and there are no Linux equivalents or guidance. The documentation assumes the reader is using Windows, and Linux is not addressed at all.

Recommendations:

Clearly state early in the documentation that the MARS agent is only supported on Windows, and provide a reference to Azure Backup solutions for Linux if available.
If Linux is not supported, add a section explaining alternative backup solutions for Linux workloads in Azure (such as Azure Backup for Linux VMs or third-party solutions).
Where Windows tools or patterns are mentioned (e.g., registry edits, PowerShell, MMC), clarify that these are not applicable to Linux and provide equivalent Linux instructions or explicitly state that no Linux support exists.
Consider adding a comparison table or FAQ addressing backup agent support for both Windows and Linux, to help cross-platform administrators quickly understand their options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) and omitting any guidance for Linux-based systems. All examples, troubleshooting, and configuration steps are tailored to Windows, with no mention of Linux equivalents or cross-platform considerations. References and links are also Windows-centric.

Recommendations:

Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS) and relevant configuration files (such as OpenSSL or system-wide crypto policies).
Provide Linux command-line examples (e.g., using openssl, update-alternatives, or editing /etc/ssl/openssl.cnf) for checking and enforcing TLS 1.2 support.
Include troubleshooting steps and error messages relevant to Linux environments, such as logs or common misconfigurations.
Reference Linux-specific documentation and best practices for TLS configuration in the 'Additional resources' section.
Clarify in the introduction or prerequisites which operating systems the instructions apply to, and explicitly state if Linux is not supported or requires different steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation assumes SQL Server is running on Windows VMs and does not mention or provide examples for Linux-based SQL Server deployments. There is no discussion of Linux-specific considerations, tools, or commands, and the backup extension and registration workflows are described in a way that presumes a Windows environment. The absence of Linux parity is notable given that SQL Server is supported on Linux.

Recommendations:

Explicitly state whether the described procedures and Azure Backup support apply to SQL Server on Linux VMs as well as Windows VMs.
If Linux is supported, add Linux-specific instructions for registering AG nodes, installing the workload backup extension, and handling failover scenarios.
Include examples or notes about any differences in backup workflows, error codes, or limitations for SQL Server AGs on Linux.
Mention any Linux-specific prerequisites, such as required packages, permissions, or service management commands.
If Azure Backup does not support SQL Server AGs on Linux, clearly state this limitation early in the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias in both structure and content. Windows scenarios, tools, and agents (such as MARS, DPM, MABS, and PowerShell) are described in detail and often appear before or instead of Linux equivalents. Linux support is frequently described in terms of limitations or as 'not supported' for features available to Windows. Examples and tool references (e.g., PowerShell for restore, MARS agent) are Windows-centric, with minimal or no equivalent Linux command-line or tool guidance. Linux-specific backup scenarios are less detailed, and advanced features (like file-level restore, agent-based backup with MARS/DPM/MABS) are not available or not documented for Linux.

Recommendations:

Provide Linux CLI (az CLI, Bash) examples alongside or before PowerShell examples for all backup and restore operations.
Include Linux-specific guidance and parity for agent-based backup and restore, or clearly state roadmap/alternatives if not supported.
Where features are Windows-only (e.g., MARS agent, DPM/MABS integration), offer Linux alternatives or workarounds, or explain the technical limitations.
Document Linux backup/restore scenarios with the same level of detail as Windows, including step-by-step instructions and troubleshooting.
Highlight Linux-specific best practices, supported distributions, and scripting options (e.g., using custom scripts for app-consistent backups) more prominently.
Avoid presenting Windows tools and workflows (e.g., PowerShell, Windows agents) as the default or only option; always mention Linux options in parallel where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing .NET (C#) code samples, referencing Visual Studio as the development environment, and mentioning Windows-specific tools and workflows. There are no Linux or cross-platform examples, nor are alternative development environments or command-line workflows discussed. The documentation assumes the use of Windows-centric tools and patterns throughout.

Recommendations:

Provide equivalent code samples using cross-platform .NET Core/.NET 6+ that can be run on Linux and macOS, not just Windows.
Include instructions for setting up and running the sample using cross-platform editors like VS Code or JetBrains Rider, and command-line tools (e.g., dotnet CLI) instead of only Visual Studio.
Add explicit guidance for running Azure Batch tasks on Linux pools, including any differences in environment variables, file paths, or runtime considerations.
Reference and link to Linux/macOS compatible Azure Storage client libraries and usage patterns.
Clarify that the File Conventions library and Azure Batch support both Windows and Linux compute nodes, and provide examples or notes for both.
If possible, provide a sample project or walkthrough that demonstrates persisting output from a Linux-based Batch task (e.g., using .NET on Ubuntu).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools (such as the MARS agent) for automation and hybrid backup scenarios, while not providing equivalent Linux or cross-platform examples. There is a lack of explicit Linux command-line (Bash/CLI) examples or references to Linux-native backup tools and patterns, especially in hybrid and automation contexts. The documentation assumes or highlights Windows/PowerShell workflows and tools, with Linux scenarios either omitted or not given parity.

Recommendations:

Include explicit Linux/Bash/Azure CLI examples alongside PowerShell for automation and scripting tasks.
When referencing the MARS agent (which is Windows-only), clarify Linux alternatives (such as Azure Backup Server, or native Linux agent support) and provide guidance for Linux workloads.
Ensure hybrid backup sections mention both Windows and Linux on-premises scenarios, with clear instructions or links for Linux users.
Where PowerShell is mentioned for automation (e.g., auto-retry of failed jobs), also provide Azure CLI or Bash script equivalents.
Audit all examples and tool mentions to ensure Linux administrators can follow the guidance without needing to translate from Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is exclusively focused on installing and using the Microsoft Azure Recovery Services (MARS) agent for Windows environments. All instructions, examples, and references are specific to Windows operating systems, including references to Windows-specific installers (.exe), wizards, and tools. There is no mention of Linux support, alternatives, or parity, and Linux users are not addressed at all.

Recommendations:

Clearly state in the introduction and prerequisites whether the MARS agent is supported on Linux. If not, provide links to Linux backup solutions (such as Azure Backup for Linux or third-party options).
If Linux support is available or planned, add equivalent installation and usage instructions for Linux systems, including command-line examples (bash, shell scripts) and package management details.
Include a comparison table or section outlining backup options for both Windows and Linux, helping users choose the correct tool for their platform.
Avoid Windows-centric language such as only referencing .exe installers, Windows wizards, or Windows-specific settings without mentioning Linux equivalents or alternatives.
If the product is Windows-only by design, make this explicit at the top of the documentation to set expectations for cross-platform users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong bias towards Windows and PowerShell. All deployment and cleanup examples are provided exclusively in PowerShell, with no equivalent Azure CLI or Bash examples. The template specifically deploys a Windows VM, and Linux alternatives are not mentioned or demonstrated. Although the Azure CLI and portal are referenced as options, practical guidance and code samples are only given for PowerShell, which is more familiar to Windows users.

Recommendations:

Add equivalent Azure CLI (bash) examples for deploying the ARM template, including parameter input and resource group creation.
Provide a sample template or instructions for deploying a Linux VM, or clarify how to modify the template for Linux.
Include cleanup instructions using Azure CLI commands.
When referencing multiple tools (PowerShell, CLI, portal), provide code samples for at least PowerShell and CLI, and present them in parallel or with equal prominence.
Explicitly mention cross-platform compatibility and provide guidance for users on macOS/Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing individual file recovery instructions for Windows Server VMs, omitting Linux VM scenarios. The only registry key example for parallel restore is Windows-specific, and there are no references to Linux tools, file systems, or recovery workflows. The documentation assumes the use of Windows-based management tools and environments throughout.

Recommendations:

Add explicit guidance and examples for restoring individual files from Linux-based VMs, including any limitations or alternative workflows if direct item-level restore is not supported.
Mention Linux file system compatibility and any required steps for Linux VM recovery (e.g., mounting VMDKs on a Linux system, using third-party tools, or exporting files via NFS/Samba).
Clarify in the documentation whether item-level restore is supported for Linux VMs, and if not, provide workarounds or references to relevant tools.
Where registry edits are mentioned, note that this is a Windows-only operation and provide equivalent configuration steps for Linux environments if applicable.
Balance the documentation by including Linux terminology, screenshots, and examples where possible, or explicitly state platform limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page primarily focuses on Azure CLI commands, which are cross-platform, but it introduces Windows bias by mentioning Azure PowerShell as an alternative in the introduction and linking to a PowerShell-specific guide. There are no explicit Linux- or macOS-specific instructions, nor are there examples of shell environments or command differences for non-Windows platforms. The use of redirection operators (e.g., '>restoreconfig.json') is compatible with both Windows and Unix shells, but there is no discussion of shell-specific nuances, environment variable syntax differences, or prerequisites for Linux/macOS users. The documentation implicitly assumes a Windows-first perspective by mentioning PowerShell before any Linux alternatives and not providing parity guidance for Linux users.

Recommendations:

Add explicit notes or sections for Linux/macOS users, including any prerequisites (e.g., az CLI installation, shell compatibility, jq usage for JSON parsing, etc.).
If PowerShell is mentioned as an alternative, also mention Bash or other common Linux shells as alternatives for scripting.
Provide example commands using both Windows (PowerShell) and Linux/macOS (Bash) syntax where there are differences (e.g., environment variable usage: $VAR vs. $env:VAR).
Clarify that the Azure CLI commands are cross-platform and highlight any platform-specific considerations.
Link to Linux/macOS-specific guides or troubleshooting pages if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Azure Portal (a GUI tool most familiar to Windows users) for installation steps, mentioning Azure PowerShell before Azure CLI in the 'Next steps' section, and not providing any Linux shell or cross-platform command-line examples directly in the main flow. The focus on Azure Portal and PowerShell, both of which are more commonly used in Windows environments, may make Linux users feel secondary or unsupported.

Recommendations:

Add step-by-step instructions for installing the Azure Backup extension using Azure CLI directly in the main guide, not just as a link in 'Next steps'.
Ensure that Azure CLI (which is cross-platform) examples are given equal or higher prominence than PowerShell examples.
Include Linux shell (bash) command examples where relevant, especially for DevOps engineers who may be working in Linux environments.
Balance screenshots and instructions to reflect both Windows and Linux user experiences, or clarify that the steps are platform-agnostic.
Explicitly state that the procedures work on all platforms, and provide any platform-specific notes if necessary.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows environments, specifically the Microsoft Azure Recovery Services (MARS) agent, which is a Windows-only backup tool. All operational instructions, screenshots, and automation references are based on the MARS agent console, PowerShell cmdlets, and Windows-centric patterns. There are no examples or guidance for Linux systems or cross-platform backup agents, and the automation references (e.g., Set-OBMachineSetting) are PowerShell-specific. The documentation assumes the user is operating in a Windows environment throughout.

Recommendations:

Clearly state at the beginning that the MARS agent is Windows-only, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure Backup Server).
Where possible, include parity guidance for Linux-based backup agents, or explicitly mention that the described workflow does not apply to Linux.
If Azure CLI or REST API alternatives exist for agent registration or passphrase management, provide those examples to support automation from non-Windows platforms.
Add a comparison table or section outlining backup and passphrase management options for both Windows and Linux environments in Azure.
Review automation script references to clarify their platform dependencies and suggest alternatives for Linux users where available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and the Teams Admin Center (TAC) portal as the only methods for configuring emergency calling policies, without mentioning or providing Linux/macOS alternatives. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows-centric tools for administration.

Recommendations:

Explicitly mention if Teams administration and configuration tasks (such as policy assignment) can be performed using cross-platform tools or REST APIs, and provide links or examples for Linux/macOS users.
If PowerShell is required, clarify whether PowerShell Core (pwsh), which is cross-platform, is supported and provide installation instructions for Linux/macOS.
Include alternative command-line or scripting examples for Linux environments, or acknowledge any current limitations for non-Windows users.
Reference the Teams Admin Center web portal as a cross-platform option, if applicable, and clarify any features that are only available on Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates several forms of Windows bias. Windows-specific tools and patterns (such as PowerShell and OS disk swap documentation linking to Windows-specific pages) are mentioned before or instead of Linux equivalents. Step-by-step instructions and automation examples reference PowerShell, but there are no corresponding CLI or Linux-native examples. The Linux-specific restore process is relegated to a separate, brief step, and lacks detailed guidance or parity with the Windows instructions.

Recommendations:

Provide equivalent Linux examples alongside Windows/PowerShell instructions, such as using Azure CLI or Bash scripts for restoring VMs and creating new instances from restored disks.
When referencing features like OS disk swap, include links and instructions for both Windows and Linux VMs, or clarify any differences.
Avoid presenting Windows tools (e.g., PowerShell) as the default or only automation method; always offer cross-platform alternatives.
Expand the Linux restore section to include detailed, step-by-step instructions, matching the depth provided for Windows.
Ensure that all screenshots, notes, and linked resources are inclusive of both operating systems, or clearly indicate when a process is OS-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and all scripting examples are in PowerShell and Azure CLI, with no Linux shell or bash-specific examples. Windows-specific terminology (e.g., C: drive, BitLocker) is mentioned before Linux equivalents (e.g., root filesystem, dm-crypt). There are no explicit bash or Linux shell command examples for managing selective disk backup, and the only Linux-specific guidance is limited to ensuring the presence of 'lsblk' and 'lsscsi' tools. The documentation assumes familiarity with Windows tools and patterns, and Linux is treated as an afterthought in several sections.

Recommendations:

Add bash/Linux shell command examples for all CLI operations, demonstrating usage in a typical Linux environment (e.g., using variables, jq for parsing output, etc.).
When discussing OS-specific details (e.g., used space calculation), present Linux and Windows information in parallel, not Windows first.
Include troubleshooting steps and examples specific to common Linux distributions (e.g., Ubuntu, CentOS) for disk enumeration and backup validation.
Expand the section on required Linux tools (lsblk, lsscsi) with installation instructions for multiple distributions, and provide sample output to help users verify correct setup.
Where PowerShell is referenced, explicitly note cross-platform availability or provide equivalent bash/Linux shell alternatives.
Ensure that any references to Windows tools (e.g., BitLocker, C: drive) are matched with Linux equivalents (e.g., dm-crypt, / root filesystem) in the same context and order.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. It references Azure PowerShell alongside Azure CLI for authentication, even though only Azure CLI is supported for Terraform authentication. In the 'Next steps' section, PowerShell is consistently mentioned before Azure CLI and REST API, and there is no mention of Linux-specific shells or tooling. All command-line examples use generic 'Console' blocks, but the narrative and tool ordering favor Windows/PowerShell users.

Recommendations:

Explicitly state that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash) environments where relevant.
In all lists (such as 'Next steps'), alternate or randomize the order of PowerShell and CLI, or mention CLI first to reflect its cross-platform nature.
Clarify that Azure PowerShell is not supported for Terraform authentication, and remove or de-emphasize PowerShell references in that context.
Where possible, include example shell commands (e.g., export environment variables) for both Bash and PowerShell.
Add a note or section highlighting that all steps are fully supported on Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by emphasizing Windows Server features and benefits (such as Azure Hybrid Benefit and Extended Security Updates) before mentioning Linux, and by providing detailed instructions and processes specifically for Windows workloads (e.g., requesting ESU keys for Windows VMs) without equivalent Linux examples. The documentation also references Windows-specific licensing and support scenarios, while Linux is only briefly mentioned in passing, with no concrete examples or guidance for Linux users.

Recommendations:

Provide parallel examples and instructions for Linux workloads, such as how to leverage Azure Hybrid Benefit for Linux distributions and how to manage Linux VMs in NC2 on Azure.
Include information about Linux-specific support, security update processes, and licensing benefits, similar to the detailed steps provided for Windows Server.
Balance the mention of Windows and Linux in benefit and feature lists, ensuring that Linux scenarios are not only acknowledged but also explained with actionable guidance.
If certain features (like ESU) are Windows-only, explicitly state this and offer alternative recommendations or resources for Linux users.
Add sample use cases or migration scenarios for both Windows and Linux workloads to demonstrate parity and inclusiveness.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows/Azure Portal-centric bias. It exclusively describes restore operations using the Azure Portal UI, with no command-line examples for Linux environments. Where scripting is mentioned, only PowerShell or CLI scripts are referenced, but no explicit Linux shell (bash) examples are provided. The workflow and permissions guidance are oriented around Azure patterns familiar to Windows administrators, and there is no mention of Linux-native tools or commands for mounting disks or handling SAP HANA restores outside the Azure Portal.

Recommendations:

Add explicit Linux (bash) command-line examples for mounting and attaching restored disks to Linux-based Azure VMs.
Provide step-by-step instructions for performing SAP HANA restores using Azure CLI and shell scripts, not just via the Azure Portal.
Include references to Linux-native tools (such as mount, lsblk, etc.) for disk operations post-restore.
Ensure that scripting examples are cross-platform, showing both PowerShell and bash equivalents where relevant.
Clarify in each section whether the instructions apply to both Windows and Linux VMs, or specify any OS-specific steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows bias. It explicitly states that Linux is not supported for SQL Server backup in Azure VMs, only lists Windows Server versions as supported operating systems, and references Windows-specific tools and frameworks (e.g., PowerShell, .NET Framework). There are no Linux equivalents or examples provided, and the documentation does not address Linux users or scenarios at all.

Recommendations:

Clearly state the roadmap or plans for Linux support, if any, and provide guidance or alternatives for Linux users.
If partial Linux support exists or is planned, include Linux-specific instructions, examples, and supported distributions.
Mention cross-platform tools (such as Azure CLI) where possible, and avoid referencing only Windows tools like PowerShell unless absolutely necessary.
Provide a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux environments for SQL Server backup in Azure VMs.
If Linux is not supported, suggest alternative backup strategies or products for Linux-based SQL Server deployments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by providing troubleshooting scripts and automation examples exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. References to scripts (such as for finding Recovery Services vaults or undeleting file shares) link only to PowerShell-based solutions, and there are no CLI, Bash, or Linux-native instructions or examples. This may hinder Linux or cross-platform administrators from efficiently following the guidance.

Recommendations:

Provide equivalent troubleshooting scripts and automation examples using Azure CLI and Bash, ensuring they are cross-platform and runnable on Linux, macOS, and Windows.
When referencing scripts, clearly indicate if they are PowerShell-specific and offer alternative links or code snippets for Linux/CLI users.
Include examples and instructions for performing common tasks (such as undeleting file shares or finding Recovery Services vaults) using Azure CLI commands.
Review all troubleshooting steps to ensure that any tool or script mentioned has a Linux-compatible alternative, and document both options side by side.
Add a section or note at the beginning of the document clarifying that all examples are available for both Windows (PowerShell) and Linux (CLI/Bash), with links to the relevant sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a bias towards Windows by referencing a PowerShell script for undeleting file shares and not providing equivalent CLI or Linux-native examples. The only script-based automation mentioned is a PowerShell script, and there are no instructions or links for performing the same tasks using Azure CLI, Bash, or other cross-platform tools. This may hinder Linux or cross-platform users from following the guidance efficiently.

Recommendations:

Provide equivalent Azure CLI and Bash script examples for undeleting file shares and other automation tasks, alongside PowerShell.
When referencing scripts (such as the 'Undelete File Share Script'), include links or instructions for both PowerShell and Azure CLI/Bash versions.
Avoid referencing only Windows-specific tools (like PowerShell) in automation scenarios; always mention cross-platform alternatives.
Explicitly state that all operations can be performed from any OS using Azure CLI, and provide relevant command examples.
Review linked documentation to ensure Linux and macOS users are not excluded from automation or management scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by listing PowerShell as a primary configuration method and not providing explicit Linux or cross-platform examples. The mention of RDP before SSH and the lack of Linux-specific tools or workflows further reinforce this bias.

Recommendations:

Provide explicit Linux examples or workflows, such as using SSH from a Linux terminal.
List Azure CLI before PowerShell, as CLI is cross-platform and more familiar to Linux users.
Include references to Linux-native tools or commands where relevant.
Ensure that both RDP (Windows) and SSH (Linux) use cases are equally described and demonstrated.
Add a section or examples for accessing Azure Bastion from Linux/macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides a PowerShell script sample for managing backup policies with the MARS agent, referencing Windows-specific tools and environment variables. There are no examples or instructions for Linux environments, nor is there any mention of Linux-compatible tools or scripting alternatives.

Recommendations:

Add equivalent script samples for Linux environments, using Bash, Python, or other common Linux scripting languages.
Clearly state the platform limitations of the MARS agent and whether Linux is supported or not.
If Linux is supported, provide guidance on how to automate backup policy management on Linux, including relevant tools and commands.
If only Windows is supported, explicitly mention this at the beginning of the documentation to set user expectations.
Consider including a comparison table or section outlining differences in backup policy management between Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All examples, file paths, and tool references (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files, SSMS) are Windows-specific. There are no Linux-specific instructions, examples, or mentions of restoring SQL Server databases on Linux-based Azure VMs, despite SQL Server being supported on Linux. The use of Windows command-line tools and patterns is pervasive, and there is no parity in guidance for Linux users.

Recommendations:

Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths (e.g., /var/opt/mssql/), permissions, and service management.
Provide Linux equivalents for Windows tools and commands, such as using 'sudo' for permissions, and alternatives to PsExec for privilege escalation.
Include examples using sqlcmd or Azure CLI for Linux environments, and clarify any differences in process or prerequisites.
Mention and demonstrate how to mount Azure File Shares on Linux VMs, including necessary package installations and mount commands.
Ensure that all references to SSMS are supplemented with Linux-compatible tools or instructions (e.g., Azure Data Studio, sqlcmd).
Clearly state at the beginning of the article whether the instructions apply to both Windows and Linux SQL Server VMs, and provide links to Linux-specific documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All operational examples, tool references, and recovery procedures are specific to Windows, using tools such as PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, and referencing Windows file paths and sharing mechanisms. There are no examples or guidance for performing these tasks on Linux systems, nor are cross-platform alternatives mentioned. The documentation assumes the administrator is working exclusively in a Windows environment.

Recommendations:

Provide explicit statements clarifying platform support (e.g., if MABS is Windows-only, state this clearly at the top).
If any components can be managed or accessed from Linux (e.g., SQL Server backups, Azure Backup), provide equivalent Linux command-line examples (e.g., using sqlcmd, Azure CLI, or mounting VHDs on Linux).
Mention cross-platform tools or alternatives where possible, such as using SMB shares from Linux, or restoring SQL Server databases using Linux tools.
Where Windows-specific tools are required, explain why and suggest any possible workarounds for non-Windows environments.
Add a section summarizing platform limitations and supported scenarios, so Linux administrators are aware of any constraints.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell-based (Windows-centric) instructions and tools. PowerShell is presented as the primary scripting interface, with detailed, step-by-step examples and explanations. The CLI section is present but less detailed and is positioned after the PowerShell section. There is no mention of Linux-native tools, shell scripting, or Linux-specific considerations, and the CLI examples do not reference Linux explicitly. The documentation assumes familiarity with Windows/PowerShell paradigms and does not provide parity for Linux users.

Recommendations:

Add explicit Linux shell/bash scripting examples alongside PowerShell, especially for automation scenarios.
Clarify that Azure CLI commands are cross-platform and provide Linux-specific usage notes (e.g., shell syntax, environment variables, file paths).
Include Linux-native troubleshooting tips or references (e.g., common issues with az CLI on Linux, package dependencies, permissions).
Balance the order of presentation: alternate or parallelize PowerShell and CLI/Linux instructions, or provide a clear navigation structure for both audiences.
Mention and link to Linux installation and environment setup guides for Azure CLI and related tools.
Where screenshots or UI references are given, note any differences in experience for Linux users (if applicable).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by prioritizing RDP (a Windows protocol) in both the portal and CLI examples, listing it before SSH. There are no explicit Linux-specific examples or screenshots, and the instructions for connecting via SSH (the typical Linux method) are minimal and lack detail compared to RDP. There are no references to Linux tools or workflows, and the documentation does not provide parity in guidance for Linux users.

Recommendations:

Provide Linux-specific examples and screenshots, especially for SSH connections, including details on using SSH keys and common Linux authentication patterns.
List SSH (Linux) and RDP (Windows) connection methods with equal prominence, or alternate their order in examples.
Include instructions for connecting from Linux/macOS terminals, not just via Azure CLI, and mention any required tools or dependencies.
Clarify any differences in experience or prerequisites for Linux users (e.g., SSH agent usage, file permissions for private keys).
Add troubleshooting tips relevant to Linux environments, such as SSH key permissions or common SSH errors.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by providing PowerShell scripts as the primary or only automation example for granting privileges to database users. There are no equivalent Linux shell or cross-platform command-line examples (e.g., Bash, psql). PowerShell is mentioned first and repeatedly, and Linux-native tools or workflows are only referenced as alternatives, not as first-class instructions. This may make the tutorial less accessible to Linux users or those managing PostgreSQL on non-Windows platforms.

Recommendations:

Provide equivalent Bash or shell script examples alongside PowerShell scripts for granting privileges and other automation steps.
Include explicit instructions and examples using the psql command-line tool for privilege management.
When referencing automation scripts, mention both PowerShell and Bash/psql options together, or default to cross-platform approaches.
Clarify that PowerShell is not required and that all steps can be performed on Linux-based systems using standard PostgreSQL tools.
Add screenshots or CLI instructions from Linux environments where relevant, not just Windows/Azure Portal UI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally provides both Bash (Linux/macOS) and CMD (Windows) commands for environment variable setup, and all code samples are cross-platform. However, there is a subtle Windows bias: (1) In the environment variable setup, the Windows CMD example is given after the Bash example, but both are present. (2) The documentation assumes the use of Azure CLI, which is cross-platform, but does not mention Linux-specific tools or patterns (such as systemd for running servers, or Linux-specific troubleshooting). (3) The documentation references the awps-tunnel tool, which is Node.js-based and cross-platform, but does not mention alternatives like ngrok, which is commonly used in Linux/macOS developer workflows. (4) There is no explicit mention of Linux-specific shell or scripting patterns, and no troubleshooting guidance for Linux users. (5) The documentation does not provide PowerShell-specific examples, but the presence of CMD and Bash examples may still leave PowerShell users (common on Windows) or zsh/fish users (common on Linux/macOS) without direct guidance.

Recommendations:

Explicitly state that all commands and tools are cross-platform and tested on both Windows and Linux/macOS.
Provide PowerShell examples for environment variable setup, as many Windows users use PowerShell instead of CMD.
Include Linux-specific troubleshooting tips (e.g., handling permissions, using systemd or supervisord for running servers in the background).
Mention and provide examples for popular Linux/macOS tunneling tools like ngrok as alternatives to awps-tunnel.
Clarify any platform-specific prerequisites or differences (e.g., how to install Node.js or Python on Linux vs. Windows).
Add notes about activating Python virtual environments on Windows (using .venv\Scripts\activate) as well as on Linux/macOS (using . .venv/bin/activate).
Ensure that all code and command snippets are clearly marked for their intended shell (Bash, CMD, PowerShell) and platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias. Windows VMs and tools are mentioned first in several places, such as in the prerequisites (port 3389 for Windows is listed before port 22 for Linux), and the example links for creating VMs list Windows before Linux. Keyboard shortcut guidance is focused on Windows VMs, with only a brief mention of Mac clients connecting to Windows VMs. There are no explicit Linux command-line or desktop usage examples, and the guidance for connecting and using the Bastion service is written with Windows-centric terminology and scenarios.

Recommendations:

Alternate the order of Windows and Linux references throughout the documentation to avoid always listing Windows first.
Provide explicit Linux desktop and keyboard shortcut examples, especially for remote desktop scenarios (e.g., how to send Ctrl+Alt+Del to a Linux VM, or common Linux desktop shortcuts).
Include screenshots or walkthroughs for both Windows and Linux VMs to ensure parity.
When referencing ports, clarify that 3389 is for Windows (RDP) and 22 is for Linux (SSH), and consider listing them in varying order or together.
Add a section or callout for connecting to Linux VMs, including any differences in authentication, desktop environments, or troubleshooting.
Ensure that all instructions and terminology are equally applicable to both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed instructions for using the Azure Portal and Azure PowerShell to manage soft delete for SQL Server and SAP HANA backups in Azure VMs. However, it exclusively features PowerShell examples for command-line operations, with no mention of Linux-native tools, Azure CLI, or Bash scripting. The PowerShell section is prominent and detailed, while Linux users are not provided with equivalent guidance, creating a Windows-centric bias.

Recommendations:

Add equivalent Azure CLI (az backup ...) examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that the steps can be performed from Linux environments using Azure CLI or REST API, and provide links or examples.
If any operations require PowerShell, clarify whether PowerShell Core (cross-platform) is supported, and provide installation guidance for Linux users.
Reorder or parallelize the documentation so that Azure CLI and PowerShell examples are presented together, or allow users to select their preferred environment (PowerShell, CLI, Bash) via tabs.
Include a note or section addressing Linux administrators and their typical workflows, ensuring parity in instructions and examples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows-centric backup solutions (such as DPM and SQL in Azure VM) more prominently and in greater detail than Linux equivalents. There are no explicit Linux or cross-platform command-line examples, and the only workload-specific examples provided are for Windows technologies. Linux workloads (e.g., Azure Database for PostgreSQL) are mentioned only in the context of limitations or unsupported features, not as primary examples. There is also a lack of guidance or examples for Linux-based backup scenarios.

Recommendations:

Include examples and screenshots for Linux-based workloads (e.g., Azure Backup for Linux VMs, Azure Database for PostgreSQL) alongside Windows examples.
Provide parity in explanations for both Windows and Linux workloads, ensuring that Linux scenarios are not only mentioned in the context of limitations.
Add command-line examples using both Azure CLI and PowerShell, and ensure that Linux shell commands are represented where relevant.
Highlight cross-platform backup scenarios and tools, and avoid referencing only Windows-specific tools (such as DPM) without Linux equivalents.
Ensure that any workload-specific optimizations or troubleshooting steps are covered for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is heavily focused on Windows and PowerShell usage for deploying Azure Bastion. All code examples and setup instructions use Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples provided inline. References to creating VMs link to Windows-specific quickstarts first, and Linux VM creation is only mentioned in passing. There are no Linux or Bash-specific instructions or examples for deploying Bastion, and the workflow assumes familiarity with PowerShell and Windows tooling.

Recommendations:

Add parallel Azure CLI (az) command examples for each PowerShell example, ideally side-by-side or in a dedicated section.
Include explicit instructions and links for deploying Bastion from Linux/macOS environments using Azure CLI.
When referencing VM creation, provide both Windows and Linux quickstart links equally, or link to a cross-platform VM creation guide.
Clarify that Azure PowerShell can be used on any platform, but highlight Azure CLI as the primary cross-platform tool.
Add a section or callout for Bash/terminal users, ensuring parity in the deployment workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All code examples use Windows command-line syntax (cmd.exe /c echo ...), with no mention of Linux or cross-platform shell equivalents. The documentation exclusively references Windows tools (cmd.exe), and does not provide any Linux/bash examples or guidance for non-Windows users. There is no mention of how to adapt the task commands or environment for Linux pools, which are common in Azure Batch scenarios.

Recommendations:

For every example using Windows command-line syntax (e.g., cmd.exe /c echo ...), provide an equivalent Linux/bash example (e.g., /bin/bash -c 'echo ...').
Explicitly mention that Azure Batch supports both Windows and Linux pools, and clarify any differences in task command lines between platforms.
When referencing tools or shell environments (such as cmd.exe), provide Linux alternatives (such as /bin/bash) and explain how to select the appropriate shell for the pool OS.
Add a section or note about cross-platform considerations, including how to write portable task commands and how to detect the OS of the compute node.
Ensure that links to sample code or repositories include Linux examples or instructions for adapting to Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias. All command-line and scripting examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. The workflow assumes use of Windows tools (e.g., PowerShell scripts, .ps1 files, Cloud Shell in PowerShell mode), and file paths are shown in Windows format (e.g., C:\<filepath>). There are no Linux/Unix command equivalents or guidance for non-Windows environments, and the documentation refers to Windows-centric patterns and tools before (or instead of) cross-platform alternatives.

Recommendations:

Provide equivalent Azure CLI (az) commands and Bash script examples alongside PowerShell for all automation and scripting steps.
Include Linux/Unix file path examples and instructions for uploading and running scripts from Linux/macOS environments.
Mention that Cloud Shell supports both Bash and PowerShell, and show how to perform steps in both environments.
Where PowerShell scripts are referenced, provide Bash or Python alternatives, or clarify if the scripts are cross-platform.
Explicitly state platform requirements for any scripts or tools, and offer guidance for Linux/macOS users.
Add a section or callouts for Linux administrators, highlighting any differences or additional steps required.
Ensure screenshots and UI instructions are not Windows-specific unless the UI is identical across platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary automation/scripting option alongside the Azure CLI and portal, with detailed PowerShell examples and outputs. There is a strong emphasis on PowerShell cmdlets, which are traditionally associated with Windows environments, and no mention of Linux-native scripting tools (e.g., Bash, shell scripts) or Linux-specific considerations. Additionally, the documentation references BitLocker for Windows before DM-Crypt for Linux in the context of Azure Disk Encryption, subtly prioritizing Windows technologies.

Recommendations:

Include Bash/shell script examples for key operations, especially for Linux users who may prefer scripting outside of Azure CLI.
When mentioning encryption technologies, present Linux (DM-Crypt) and Windows (BitLocker) options in parallel, or alternate their order to avoid implicit prioritization.
Where possible, clarify that PowerShell is cross-platform, or provide explicit guidance for Linux users on installing and using PowerShell if it is required.
Add notes or links to Linux-specific best practices or troubleshooting tips for common backup and encryption scenarios.
Ensure that all automation examples (PowerShell, CLI) are equally detailed and that CLI examples are not less comprehensive than PowerShell ones.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias. PowerShell cmdlets are listed as the first command-line tool, and the use of Remote Desktop (RDP) for accessing compute nodes is mentioned without reference to SSH or Linux alternatives. While the Azure CLI is described as cross-platform and Batch Explorer is available for all OSes, the prominence of PowerShell and RDP, both Windows-centric tools, suggests a preference for Windows workflows. There are no explicit Linux shell or Bash examples, and Linux-native troubleshooting or access patterns are not highlighted.

Recommendations:

List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
Mention SSH as an alternative to RDP for accessing compute nodes, especially for Linux-based pools.
Include examples or references to Linux shell (Bash) usage where appropriate, such as troubleshooting or file access.
Ensure that all tooling and workflow descriptions explicitly note Linux compatibility or provide Linux-specific guidance where workflows differ.
Consider adding a note or section on best practices for Linux-based Batch pools, including access, debugging, and environment setup.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Configure user subscription mode' section, where only PowerShell cmdlets (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) are provided for accepting legal terms, with no equivalent Azure CLI or REST API examples. The rest of the page is Azure portal-focused and generally platform-neutral, but the only explicit command-line instructions are Windows/PowerShell-centric. Alternative tools like Azure CLI are only mentioned in a list at the end, not in the main workflow or examples.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell examples, especially for accepting Marketplace legal terms (e.g., using 'az vm image terms accept').
When referencing command-line tools, mention both PowerShell and Azure CLI options together, or present Azure CLI first to avoid implicit Windows prioritization.
Include explicit Linux/macOS-compatible instructions and screenshots where relevant, or clarify that all steps are cross-platform unless otherwise noted.
Where possible, link to REST API documentation for users who may prefer scripting outside of PowerShell or CLI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux and Windows configuration tables and some parity in example sections. However, there is a noticeable Windows bias: Windows examples (especially for installing drivers and MPI) are more detailed, appear first in example sections, and reference Windows-specific tools (e.g., PowerShell, Remote Desktop, Microsoft MPI) without always providing equivalent Linux command-line or tool examples. The Linux example for GPU drivers is less detailed and lacks explicit command-line instructions, while the Windows example includes a full start task command. There is also a reliance on Windows-centric patterns (e.g., RDP, PowerShell), and the documentation sometimes references Windows tools before Linux equivalents.

Recommendations:

Provide Linux examples with the same level of detail as Windows, including explicit shell command lines for installing drivers and configuring pools.
When listing options or examples, alternate the order or present Linux and Windows in parallel to avoid 'windows_first' bias.
Include Linux-native tools and workflows (e.g., SSH, Bash scripts) in examples, not just Windows tools like PowerShell or RDP.
For each Windows-specific instruction (e.g., PowerShell commands, RDP), provide the Linux equivalent (e.g., Bash/CLI commands, SSH).
Ensure that all example tables (such as start task commands) include both Linux and Windows variants.
Link to up-to-date Linux documentation and avoid referencing EOL Linux versions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting .NET (C#) and Windows-specific examples and references before Linux or cross-platform alternatives. The .NET example uses a Windows Server image, and PowerShell cmdlets are mentioned as a primary tool. While a Python example with Ubuntu is included, it appears after the Windows/.NET example. There are no explicit Linux shell or CLI examples, and the documentation does not provide parity in tool coverage or ordering.

Recommendations:

Provide Linux/Bash CLI examples alongside or before Windows/PowerShell/.NET examples.
Include explicit instructions and code samples for creating and managing autoscale pools using Azure CLI and Bash scripts, not just PowerShell or .NET.
When referencing VM images, alternate or equally present Ubuntu/Linux and Windows images in code samples.
Mention cross-platform tools (e.g., Azure CLI) before or alongside platform-specific tools (e.g., PowerShell).
Ensure that all SDK and API references (Python, Java, CLI) are given equal prominence and ordering as .NET/Windows.
Add a section or callout for Linux users, highlighting any differences or considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows Server OS families, Windows-based configuration files, and PowerShell scripts. There are no references to Linux-based guest OS families, tools, or migration paths. All examples and recommendations assume a Windows environment, with no parity for Linux users.

Recommendations:

Include information about Linux-based guest OS families, if supported by Azure Cloud Services, and clarify if this retirement notice is Windows-only.
Provide equivalent command-line examples using Azure CLI (cross-platform) or Bash scripts, not just Azure PowerShell.
Mention migration or support options for Linux workloads, if applicable, or explicitly state that the guidance is only relevant for Windows-based services.
Balance references to development tools (e.g., mention VS Code or cross-platform SDKs, not just Visual Studio for Windows).
Clarify in the introduction whether Linux users are affected or not, to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. Windows tools and patterns (e.g., cmd.exe, drive letters, backslashes in paths) are often mentioned first or exclusively. Some examples and directory postfixes use Windows conventions (e.g., backslashes), and Linux equivalents are sometimes less detailed or presented second. There is also a lack of parity in some explanations, such as the use of drive letters for Windows mounts and the absence of explicit Linux mount path examples.

Recommendations:

Present Linux and Windows examples in parallel, with equal detail and prominence.
Avoid using Windows path conventions (e.g., backslashes, drive letters) as the default; provide both Windows and Linux path formats in tables and examples.
When referencing tools (e.g., cmd.exe), always include the Linux equivalent (e.g., /bin/sh) with equal detail.
For environment variables or features that differ by OS (e.g., AZ_BATCH_APP_PACKAGE naming), provide clear, side-by-side examples for both platforms.
Where possible, use OS-agnostic language or clarify when something is OS-specific.
Ensure that all instructions, especially those involving directory structures or shell commands, have Linux equivalents and are not Windows-centric.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: Windows tools and patterns (such as cmdkey, net use, and Windows-style azcopy syntax) are presented in detail, with explicit examples and command lines. In contrast, Linux equivalents (such as mounting Azure Files with SMB or using azcopy with Linux syntax) are either missing or only briefly mentioned without examples. The order of presentation often places Windows solutions and tools before Linux ones, and there is a lack of parity in the depth of guidance for Linux users.

Recommendations:

Provide Linux-specific command-line examples for azcopy, including syntax and parameters as used in bash.
Include explicit instructions and sample commands for mounting Azure Files shares on Linux VMs (e.g., using mount.cifs or SMB tools).
Balance the order of presentation so that Linux and Windows solutions are introduced together or alternate, rather than consistently leading with Windows.
Where Windows tools or patterns (e.g., cmdkey, net use) are described, provide the direct Linux equivalents (e.g., mount commands, credential handling) with equal detail.
Ensure that all tools mentioned (such as Azure CLI, azcopy, Storage Explorer) are described with usage notes for both platforms, and clarify any platform-specific limitations or differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows terminology and examples. In the VM preparation section, RDP (Windows) is mentioned before SSH (Linux), and the only code sample for pool creation uses a Windows node agent SKU ('batch.node.windows amd64') with no Linux equivalent shown. There are no explicit Linux command-line or configuration examples, and the .NET SDK example is Windows-centric. While Linux is mentioned in passing, practical Linux guidance and parity in examples are lacking.

Recommendations:

Provide parallel Linux examples wherever Windows-specific instructions or code samples are given (e.g., show both 'batch.node.windows amd64' and a Linux node agent SKU in code).
Instruct on connecting to VMs using SSH (Linux) before or alongside RDP (Windows), or present both equally.
Include Linux command-line examples (e.g., az CLI, Bash) for creating snapshots, images, and pools, not just general references.
Ensure all code samples and configuration snippets demonstrate both Windows and Linux scenarios, including REST and SDK usage.
Balance references to Windows and Linux documentation links, and avoid defaulting to Windows-first language or ordering.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively covers Windows Server-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1) and their release history for Azure Cloud Services. There is no mention of Linux-based Guest OSes, no Linux configuration strings, and no Linux-specific guidance or parity. All references, examples, and recommendations (e.g., Visual Studio, .NET Framework, RDP) are Windows-centric, with no acknowledgment of Linux alternatives or support.

Recommendations:

Clearly state in the introduction whether Linux-based Cloud Services Guest OSes are supported or not. If not, explain why.
If Linux-based Guest OSes are supported for Cloud Services, add equivalent release tables, configuration strings, and update processes for major Linux distributions (e.g., Ubuntu, CentOS, Red Hat).
Provide Linux-specific guidance for SDK compatibility, update processes, and management tools (e.g., using Azure CLI, SSH, Linux package managers).
Include references to Linux tools and patterns (such as SSH instead of RDP, or using VS Code/JetBrains IDEs in addition to Visual Studio).
If only Windows is supported, make this explicit at the top of the page to avoid confusion for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias by referencing PowerShell as the only example for programmatically checking VM series support for ephemeral OS disks, without mentioning or providing equivalent Linux/CLI commands. The mention of PowerShell occurs before any cross-platform alternatives, and there are no Linux shell or Azure CLI examples for this task. While the code examples for SDK usage are cross-platform (Python and C#), the operational guidance and tooling references are Windows-centric.

Recommendations:

Provide equivalent Azure CLI and/or Bash examples for checking VM series support for ephemeral OS disks, alongside or before PowerShell examples.
Explicitly mention that PowerShell is available cross-platform, or clarify if the example is Windows-only.
Ensure that operational instructions reference both Windows and Linux tools where applicable.
Add a note or section for Linux users, highlighting how to perform the same checks and configurations using Linux-native tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively guiding users to create a pool of Windows compute nodes, specifying Windows Server 2019 as the OS, and providing only Windows command-line examples (using 'cmd', 'set', and 'timeout'). There is no mention of Linux node options, nor are there equivalent Linux shell command examples. The documentation does not mention or demonstrate how to use Linux-based pools or tasks, nor does it provide parity for Linux users.

Recommendations:

Include instructions for creating a pool of Linux compute nodes, specifying a common Linux distribution (e.g., Ubuntu).
Provide Linux shell command equivalents for the task command line (e.g., using 'bash', 'env', and 'sleep').
Present both Windows and Linux options side by side or clearly indicate how to adapt the steps for Linux environments.
Mention that Azure Batch supports both Windows and Linux pools, and link to documentation for both.
Ensure screenshots and UI steps clarify where OS selection can be changed, and what options are available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation consistently lists PowerShell (a Windows-centric tool) as the first example for querying supported VM sizes and images, and refers to PowerShell-specific cmdlets throughout. While Azure CLI (cross-platform) and REST API options are also provided, there are no Linux shell or scripting examples, and the ordering and emphasis suggest a Windows-first perspective. There is no mention of Linux-native tools or patterns for interacting with Azure Batch, nor any Linux-specific considerations or examples.

Recommendations:

Alternate the order of examples so that Azure CLI (which is cross-platform and popular on Linux) appears before PowerShell, or present both together without prioritizing one.
Include Linux shell (bash) scripting examples for querying and processing Azure Batch information, such as using jq to parse JSON output from Azure CLI.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for bash) to reinforce cross-platform usage.
If relevant, add Linux-specific considerations or tips (e.g., environment variable handling, file system paths) when discussing VM images or node configuration.
Avoid referring to PowerShell as the primary or default tool, and instead present it as one of several options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows-based Batch pools and Windows application packages (specifically the Windows 64-bit version of FFmpeg). ARM templates are configured for Windows nodes only, and there are no Linux pool or application examples. The build and deployment steps focus on Windows artifacts, and the agent specification is set to 'windows-latest' without mention of Linux alternatives. While there is a brief note that Azure Pipelines and Batch support Linux, no Linux-specific instructions, templates, or examples are provided.

Recommendations:

Provide parallel examples for Linux-based Batch pools, including ARM templates with Linux VM images and nodeAgentSkuId for Linux.
Include instructions for downloading and packaging the Linux version of FFmpeg, and show how to deploy it to Linux nodes.
Demonstrate how to set the agent specification to 'ubuntu-latest' or another Linux agent in Azure Pipelines.
Add Linux-specific YAML build and deployment steps, highlighting any differences in file packaging or deployment.
Wherever Windows-specific tools or patterns are mentioned (such as PowerShell Core), offer equivalent Bash or Linux shell alternatives.
Ensure screenshots and code snippets reflect both Windows and Linux scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing a command-line example only for Windows nodes (using .exe files), omitting equivalent Linux/bash examples. The only explicit example of invoking a custom script is for Windows, and there is no mention of Linux shell scripts or Linux-specific patterns. Additionally, the documentation refers to .NET and C# libraries first, with no parity for other languages or platforms, and does not mention Linux tools or patterns.

Recommendations:

Provide equivalent Linux/bash examples alongside Windows examples, e.g., show how to call a shell script (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh') after the Windows .exe example.
Mention both Windows and Linux nodes explicitly when discussing custom file movement solutions, and provide guidance for both environments.
Include references to cross-platform tools and patterns, not just .NET/C# libraries, and highlight any SDKs or libraries available for other languages.
Where possible, present examples in a platform-neutral way, or always provide both Windows and Linux variants.
Clarify that Azure Batch supports both Windows and Linux nodes, and link to relevant documentation for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. While it is mostly platform-agnostic in its main guidance, several sections either mention Windows tools or patterns first, provide more detail for Windows, or lack parity in Linux-specific examples. For example, remote access ports are listed as '3389 (Windows), 22 (Linux)', with Windows mentioned first. There are references to PowerShell and RDP (Windows Remote Desktop) without equivalent Linux command-line or SSH examples. The prerequisites mention Azure PowerShell before Azure CLI, and there are no explicit Linux command-line or shell examples for creating or managing resources. The documentation assumes familiarity with Windows-centric tooling and patterns, and Linux users may find the guidance less tailored to their workflows.

Recommendations:

When listing remote access ports, alternate the order or mention Linux (SSH/22) first in some places to balance visibility.
Provide explicit Linux command-line (bash/CLI) examples alongside or before PowerShell examples, especially in prerequisites and resource creation steps.
Mention Azure CLI as prominently as Azure PowerShell in all relevant sections, and provide equivalent instructions for both.
Reference SSH and Linux-native tools (e.g., scp, sftp) alongside RDP and Windows tools when discussing remote access.
Where screenshots or UI elements are shown, clarify that the instructions are platform-neutral or provide notes for Linux users if there are differences.
Add a section or callout for Linux users, highlighting any special considerations or best practices for Linux-based Batch pools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\<version>\schemas) and mentioning the Azure SDK in the context of Windows installation. There are no Linux or cross-platform installation paths, nor are there any examples or notes for Linux users. All tooling and directory references are Windows-centric.

Recommendations:

Include Linux and macOS installation paths for the Azure SDK and schema files, or clarify if the SDK/tools are Windows-only.
Add notes or sections explaining how to work with csdef files on Linux (e.g., file locations, compatible editors, or CLI tools).
If relevant, provide cross-platform command-line examples (e.g., using Azure CLI, bash, or PowerShell Core) instead of only referencing Windows tools or directories.
Explicitly state platform support and any differences in workflow for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by providing only a Windows-based VM image example (MicrosoftWindowsServer) and node agent SKU (batch.node.windows amd64) in the code sample, with no equivalent Linux example or mention. The example uses Windows-specific values and does not demonstrate how to update a pool to use a Linux image or node agent. There is no discussion of Linux VM images, node agent SKUs, or Linux-specific considerations, and the only concrete example is for Windows. This may lead Linux users to feel unsupported or unclear about the process for Linux pools.

Recommendations:

Add a parallel example demonstrating how to update a pool to use a Linux VM image and the appropriate Linux node agent SKU.
Explicitly mention both Windows and Linux options in all relevant sections, including lists of supported publishers, offers, and SKUs.
In code samples, provide both Windows and Linux variants, or use a generic template with comments explaining how to substitute for either OS.
Include a table or section listing common Windows and Linux VM image references and node agent SKUs for Batch pools.
Review all examples and ensure Linux is given equal prominence and clarity as Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as a primary method for creating Key Vaults, omitting equivalent Linux/CLI examples. The certificate format required is .PFX, which is most commonly associated with Windows environments. Deployment options prioritize Windows-centric tools (PowerShell, Visual Studio) and do not provide parity for Linux users (e.g., Azure CLI, Bash scripts). There are no examples or instructions for Linux users on how to generate, upload, or manage certificates.

Recommendations:

Include Azure CLI examples alongside PowerShell for creating and managing Key Vaults and certificates.
Provide instructions or references for generating .PFX certificates on Linux (e.g., using OpenSSL).
List Linux-friendly deployment options (e.g., Bash, Azure CLI) alongside or before Windows tools.
Add explicit Linux/macOS command-line examples for uploading and referencing certificates.
Clarify that .PFX files can be generated and used cross-platform, and provide guidance for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a Windows bias in the 'Next steps' section, where deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before any cross-platform or Linux-native options. There is no mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS. No Linux-specific examples or tools are provided.

Recommendations:

Include Azure CLI and Bash scripting examples alongside or before PowerShell examples.
Mention cross-platform tools (e.g., Azure CLI) in the 'Next steps' deployment options.
Provide links to Linux/macOS deployment guides or documentation.
Ensure that Visual Studio Code (cross-platform) is mentioned if an IDE is referenced, not just Visual Studio (Windows-only).
Balance the order of tool mentions so that Windows-specific tools do not always appear first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. Windows tools and patterns (e.g., PowerShell, RDP) are often mentioned first or exclusively, and some examples or instructions are more detailed for Windows than Linux. While Linux is referenced, parity in examples and tool coverage is lacking in some sections.

Recommendations:

When listing supported images or tools, present Azure CLI (cross-platform) examples before or alongside PowerShell, and ensure both Windows and Linux are equally represented.
Provide explicit Linux command-line examples (e.g., SSH connection commands, Linux-specific disk mounting instructions) where only Windows (RDP) or PowerShell examples are given.
In portal instructions, detail both RDP (Windows) and SSH (Linux) connection steps, including example commands for SSH.
Ensure that all code snippets and tool references (e.g., for checking purchase plan info, mounting disks, etc.) have both Windows and Linux variants, or clarify when a step is OS-agnostic.
Where possible, use neutral language (e.g., 'Connect via RDP (Windows) or SSH (Linux)') and avoid always listing Windows first.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in several ways: all code examples are in C# and use Windows-centric command lines (e.g., 'cmd /c'), with no Linux shell equivalents provided. The only detailed example of application execution uses Windows paths and environment variable conventions first, with Linux differences mentioned only as an aside. There are no Linux-specific code snippets or shell command examples, and the documentation consistently references Windows node configuration and tools before Linux. This may hinder Linux users from easily applying the guidance.

Recommendations:

Provide parallel Linux/bash examples for all command-line and code snippets, especially for task command lines and environment variable usage.
Include at least one example of deploying and executing an application package on a Linux compute node, using bash syntax and Linux file paths.
When describing environment variables and application package paths, present Linux and Windows formats side-by-side, rather than Windows first.
Mention Linux node configuration and requirements with equal prominence as Windows, including any differences in application ID rules or file system layout.
If possible, include code samples in additional languages (e.g., Python) that are popular in Linux environments, or at least reference their documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Windows-based examples for both REST API and SDK usage. The sample configurations and code exclusively reference Windows images (e.g., MicrosoftWindowsServer, WindowsServer, batch.node.windows amd64) and Windows-specific properties (windowsConfiguration, enableAutomaticUpdates). There are no examples or guidance for provisioning Linux-based pools, nor are Linux image references or configuration options discussed. The documentation also references Windows Update and in-VM patching in a way that is specific to Windows, without mentioning the Linux equivalents.

Recommendations:

Add parallel examples for Linux pools, including REST API and SDK (C#) snippets that use Linux image references (e.g., Ubuntu, CentOS) and nodeAgentSkuId values appropriate for Linux.
Explicitly document Linux-specific configuration options, such as linuxConfiguration blocks, and discuss any differences in automatic OS upgrade behavior between Windows and Linux.
Mention Linux update mechanisms (e.g., package manager updates) where Windows Update is discussed, or clarify if/how automatic upgrades differ for Linux nodes.
Ensure that references to image publishers, offers, and SKUs include both Windows and Linux options, and provide guidance for selecting Linux images.
Where Windows-specific properties are required (e.g., windowsConfiguration), clarify their Linux equivalents or state when they are not applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by consistently referencing PowerShell scripts and 'Command tools (PowerShell/CLI)' as the primary or only command-line automation option. PowerShell is mentioned explicitly and repeatedly, while Linux-native tools or Bash examples are not provided. Where CLI is mentioned, it is always paired with PowerShell, and no explicit Linux/Bash command examples or screenshots are shown. There is no mention of Linux-specific workflows, and all automation appears to assume a Windows-centric environment.

Recommendations:

Provide explicit Bash/Azure CLI command examples alongside PowerShell, especially in sections where scripts are offered for download.
Include screenshots or instructions that demonstrate the process on Linux or macOS terminals, not just Windows/PowerShell environments.
When referencing 'Command tools (PowerShell/CLI)', clarify that Azure CLI is cross-platform and provide parity in examples for both Windows (PowerShell) and Linux/macOS (Bash).
Add a note or section for Linux users, highlighting any differences or additional steps required for common scenarios.
Ensure that downloadable scripts are available in both PowerShell (.ps1) and Bash (.sh) formats where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. In several sections, Windows tools (such as PowerShell) are mentioned before or more prominently than their Linux equivalents. Some examples and guidance are provided only for Windows (e.g., using PowerShell cmdlets to enumerate disks), while Linux examples are less detailed or missing. Additionally, certain recommendations (like using pool scope for short tasks) specifically reference Windows nodes, and Windows-specific issues (directory junctions, Windows Services) are discussed in more detail than their Linux counterparts.

Recommendations:

Ensure that for every Windows/PowerShell example or tool mentioned, a Linux/bash equivalent is provided with equal detail and prominence.
When listing tools or APIs (e.g., for discovering EOL dates), mention cross-platform options first (such as Azure CLI or REST API), or present both Windows and Linux options together.
Expand sections that currently only provide Windows-specific guidance (e.g., disk preparation, directory management) to include equivalent Linux commands and best practices.
Balance the discussion of OS-specific pitfalls (e.g., directory junctions in Windows) with Linux-specific considerations (e.g., symlink handling, systemd service management).
Where recommendations are OS-specific (such as 'Use pool scope for short tasks on Windows nodes'), clarify if and how they apply to Linux nodes.
Review for any missing Linux examples, especially in sections where only PowerShell or Windows tools are referenced, and add bash or Linux-native command examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias in several areas. Windows tools and patterns (such as 'cmd.exe', 'cmd /c', and references to Windows Data Protection API) are used in code examples and scenarios, often without Linux equivalents or with Linux-specific details provided later or omitted. Powershell/Windows command patterns are used in code snippets for .NET, Java, and Python, and Windows terminology is frequently introduced before Linux alternatives. Some Linux-specific configuration is present, but Linux command-line examples are missing, and Windows tools are referenced without Linux alternatives.

Recommendations:

Provide Linux shell command examples (e.g., using '/bin/bash -c' instead of 'cmd /c') alongside or before Windows examples in all code snippets.
When referencing Windows-specific tools (such as DPAPI), include equivalent Linux approaches (e.g., GnuPG, file permissions, or other secret management solutions).
Ensure that all code samples that show Windows VM configuration also show Linux VM configuration, and vice versa, with parity in detail and explanation.
Avoid using Windows terminology or tools as the default; instead, present both Windows and Linux options equally, or alternate which is presented first.
In the 'Update your code' section, provide Linux-specific migration guidance if any differences exist.
Add explicit Linux SSH usage examples for running tasks and managing user accounts, not just configuration.
Review all scenarios and ensure Linux is treated as a first-class platform, not an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. It exclusively references Visual Studio 2015 for project setup, assumes the use of Windows-specific UI paths (e.g., File > New > Project), and only provides instructions for using tools like NuGet Package Manager Console and PowerShell, which are primarily Windows-centric. There are no examples or guidance for Linux or cross-platform development environments, such as using .NET CLI, VS Code, or running the sample on Linux/macOS. The only alternative mentioned is Node.js, but within the .NET section, all instructions are Windows-specific.

Recommendations:

Provide equivalent instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
Include guidance for using cross-platform editors like Visual Studio Code, not just Visual Studio.
Avoid UI instructions that are specific to Windows (e.g., Visual Studio menus) or provide parallel steps for Linux/macOS users.
Mention and demonstrate how to install required packages and run the application on Linux/macOS.
If referencing PowerShell, also provide Bash or shell script equivalents for common tasks.
Clarify that the .NET SDK and Azure SDK libraries are cross-platform, and show how to authenticate and run the sample on non-Windows systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before any Linux or cross-platform alternatives, and by omitting explicit Linux CLI examples. The 'Next steps' section prioritizes PowerShell and Visual Studio, both of which are traditionally Windows-focused, and does not mention Azure CLI or Bash scripting, which are more common in Linux environments.

Recommendations:

Include Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Mention deployment options using Bash or shell scripts where appropriate.
List cross-platform tools (e.g., Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio) to avoid the appearance of Windows-first bias.
Explicitly state that the Azure portal and Azure CLI are supported on all major operating systems.
Provide links to Linux-specific documentation or guides where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation presents Windows requirements and details first, with extensive specificity about Windows tools (e.g., BitLocker, VBS, HVCI) and dependencies, while Linux is described as 'not yet supported' and its requirements are marked as 'expected'. Windows-specific tools and features are named and linked, whereas Linux equivalents are only briefly mentioned (e.g., dm-crypt, dm-verity, IMA) and lack the same level of detail or guidance. There are no Linux command-line or configuration examples, and some requirements reference Windows versions or features without Linux parity.

Recommendations:

Provide Linux support and requirements at parity with Windows, including finalized (not 'expected') requirements.
Include Linux-specific examples and configuration guidance, similar to the detail given for Windows (e.g., how to enable dm-crypt, dm-verity, IMA, or set up secure boot with U-Boot).
Reference and link to Linux documentation and tools with the same prominence as Windows tools (e.g., provide links to Linux security baseline guides, dm-crypt documentation, etc.).
Avoid presenting Windows requirements first by default; consider a neutral introduction or parallel presentation for all platforms.
Where Windows tools are mentioned (e.g., BitLocker, VBS, HVCI), explicitly mention and describe Linux equivalents (e.g., dm-crypt, SELinux, AppArmor, etc.) in the same context.
Add Linux-specific resources and troubleshooting links, and ensure that all requirements have actionable Linux guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by referencing PowerShell and Windows-centric tools exclusively when discussing command-line or automation options. There are no examples or explicit mentions of Linux shell equivalents, Bash, or cross-platform scripting. PowerShell is mentioned as the primary or only automation tool, and no Linux-specific guidance or parity is provided for key migration steps.

Recommendations:

Include Azure CLI (az) command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that all migration operations (validate, prepare, commit, abort) can be performed using Azure CLI, and provide sample commands.
When referencing automation or scripting, avoid assuming PowerShell as the default; instead, provide both PowerShell and Bash/Azure CLI equivalents.
Add a section or callout for Linux/macOS users, clarifying that the migration process is fully supported from non-Windows environments and linking to relevant cross-platform tooling documentation.
Review all troubleshooting steps to ensure that Linux users are not directed solely to PowerShell, and provide REST API or Azure CLI alternatives where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting interface for both Windows and Linux examples, rather than showing native Linux shell commands. In several sections, Windows-specific tools and patterns (such as 'cmdkey', 'net use', and RDP) are described in detail, sometimes before their Linux equivalents. Troubleshooting and manual mounting instructions also emphasize Windows tools and workflows, with Linux alternatives provided but less prominently. Native Linux command-line examples (e.g., using 'mount' or 'smbclient') are missing.

Recommendations:

Provide native Linux shell (bash) command examples for mounting file systems, in addition to or instead of PowerShell for Linux.
When describing mounting and troubleshooting workflows, present Linux and Windows instructions in parallel, or lead with Linux examples where appropriate.
Include Linux-native troubleshooting steps (e.g., using 'mount', 'dmesg', 'journalctl', or 'lsblk') alongside Windows tools.
Reference Linux documentation and tools (such as 'mount.cifs', 'smbclient', or 'systemctl') as prominently as Windows tools.
Ensure that all code samples and manual steps are equally detailed for both platforms, and avoid assuming PowerShell is the default interface for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric: it only references the Key Vault VM extension for Windows, describes certificate handling in terms of the Windows certificate store, and provides no mention of Linux support or Linux-specific instructions. All examples and configuration snippets (such as certificate store location and names) are tailored to Windows environments, and there is no guidance for Linux users.

Recommendations:

Clarify in the introduction whether the Key Vault VM extension is available for Linux VMs in Azure Cloud Services (extended support). If not, explicitly state this limitation.
If Linux support exists, add equivalent instructions and configuration examples for Linux, including how certificates are handled and where they are stored.
Provide parallel documentation sections or notes for Linux users, including any differences in authentication, certificate management, and extension installation.
Avoid using Windows-specific terminology (such as 'certificate store location', 'LocalMachine', 'My') without Linux equivalents or explanations.
Include links to Linux-specific Key Vault VM extension documentation if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for configuring diagnostic settings and enabling logs. There are no equivalent instructions or examples for Linux users (e.g., using Azure CLI or Bash scripts). The exclusive use of PowerShell and the absence of cross-platform command-line alternatives make the instructions less accessible to users on Linux or macOS. Additionally, the documentation references 'Azure PowerShell' as the primary automation tool, reinforcing a Windows-centric approach.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell-based instructions, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance on choosing the appropriate tool for the user's environment.
Where possible, provide Bash script examples alongside PowerShell scripts, especially for automation scenarios.
Reorganize sections so that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools (PowerShell), or provide a clear tabbed interface for different platforms.
Review and update any references to 'Azure PowerShell' as the default automation tool to a more inclusive phrasing, such as 'Azure PowerShell or Azure CLI'.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK), mentioning Visual Studio and .NET SDK tools exclusively, and omitting any Linux or cross-platform equivalents for SDK installation, file locations, or tooling. There are no Linux-specific instructions, examples, or references, which may hinder Linux users' ability to follow the documentation.

Recommendations:

Include Linux file path examples for SDK schema locations, such as /usr/local/share/azure-sdks or similar, alongside the Windows paths.
Mention cross-platform or Linux-compatible tools for schema validation and editing, such as VS Code, Azure CLI, or open-source XML editors.
Clarify whether the Azure SDK and related tools are available for Linux, and provide installation instructions or references for Linux users.
Avoid assuming Visual Studio or .NET SDK as the only tooling; reference cross-platform alternatives where possible.
Add a note or section explicitly addressing Linux/macOS users, outlining any differences or parity in the workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for Azure Cloud Shell exhibits a moderate Windows bias. While it acknowledges the Linux foundation of Cloud Shell and lists many Linux tools, it gives prominent and repeated attention to PowerShell features (such as the Azure drive and PowerShell-specific modules), lists Windows/PowerShell tools and examples before or more prominently than their Linux equivalents, and highlights Microsoft-centric (often Windows-first) tools. Some features, such as the Azure drive, are described only for PowerShell with no Bash/Linux equivalent mentioned.

Recommendations:

Provide equivalent Bash/Linux examples or features alongside PowerShell-specific features (e.g., explain how to navigate Azure resources in Bash, if possible).
Balance the order of tool listings so that Linux/Bash tools are not always listed after PowerShell/Windows tools.
Highlight cross-platform capabilities and clarify when features are PowerShell-only versus available in Bash.
Include more Bash/Linux-centric usage scenarios and examples, especially for Azure resource management.
Where PowerShell modules are listed, consider also listing popular Bash/Linux tools or scripts for the same tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific features (such as the Azure: drive and PowerShell provider) are discussed in detail, with Windows/PowerShell examples and terminology often appearing before or instead of Linux equivalents. Some troubleshooting and usage scenarios focus on Windows tools or workflows, and Linux/Bash examples are less prominent or missing in some sections.

Recommendations:

Ensure that for every PowerShell example, an equivalent Bash/Linux example is provided and given equal prominence.
When discussing features like the Azure: drive (PowerShell-specific), clarify their absence or alternatives in Bash/Linux environments.
In sections where browser developer tools are referenced, include instructions for Firefox and Linux browsers, not just Edge/Chrome (which are more common on Windows/macOS).
When listing keyboard shortcuts, consider listing Linux before or alongside Windows, or group them without implied priority.
Review troubleshooting steps to ensure they are platform-agnostic or provide platform-specific guidance for both Windows and Linux users.
Highlight any differences in experience or limitations for Linux users explicitly, so expectations are clear.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions using PowerShell cmdlets and concepts. There are no references to Bash or Linux-native shells, nor are there equivalent examples for users who might use Bash in Azure Cloud Shell. The documentation assumes the user is operating in a PowerShell environment, which is more closely associated with Windows, and does not mention or provide parity for Linux/Bash users.

Recommendations:

Add equivalent instructions and examples for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features in Bash (e.g., using 'bash-preexec', 'bash-completion', or 'fzf').
Explicitly state at the beginning that the instructions are specific to PowerShell and provide links or references to documentation for Bash users.
Where possible, provide side-by-side examples for both PowerShell and Bash to ensure Linux users are equally supported.
Mention any limitations or differences in predictive features between PowerShell and Bash in Azure Cloud Shell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for resource creation and deployment, referencing Visual Studio (a Windows-centric tool), and omitting any CLI or Linux-native instructions. Steps for creating resources and deploying templates consistently mention the Azure portal and PowerShell, with no mention of Azure CLI or Bash equivalents. The only deployment command shown is in PowerShell, and the extension profile example is for RDP (a Windows protocol), further reinforcing the Windows-centric approach.

Recommendations:

Add equivalent Azure CLI (az) commands for all resource creation and deployment steps, alongside or before PowerShell examples.
Include Linux/Bash shell examples for uploading files to storage and deploying ARM templates.
Reference cross-platform tools (such as Azure CLI and VS Code) in addition to or instead of Windows-only tools like Visual Studio.
Provide extension profile examples relevant to Linux (e.g., SSH extension) in addition to RDP.
Ensure that all instructions and links are platform-neutral or provide parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisites, setup, and resource management steps all assume a PowerShell environment, and there are no alternative instructions or code samples for Linux users. The article title and repeated references to PowerShell reinforce this bias.

Recommendations:

Provide equivalent Azure CLI (az) command examples for each PowerShell example, ideally side-by-side or in separate tabs.
Update the article title and description to reflect cross-platform support, or create a parallel article for Azure CLI/Linux users.
Add a section on how to perform these tasks using Bash or in the Azure Cloud Shell with Bash.
Mention both PowerShell and CLI options in the prerequisites and setup sections, including installation links for both.
Ensure that references to tools and commands do not assume a Windows environment by default.
Where possible, use neutral language (e.g., 'using Azure PowerShell or Azure CLI') and avoid Windows-first phrasing.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through its exclusive mention of Windows-specific tools and patterns, such as PowerShell and the Teams Admin Center (TAC portal), for administrative tasks. There are no examples or guidance for performing equivalent operations on Linux or cross-platform environments. The documentation assumes the use of Windows-centric administration without acknowledging or providing alternatives for Linux users.

Recommendations:

Provide equivalent command-line examples for Linux environments, such as using Azure CLI, Microsoft Graph API, or Bash scripts, alongside or instead of PowerShell.
When referencing administrative tools like the TAC portal or PowerShell, clarify if these are available cross-platform or provide links to cross-platform alternatives.
Explicitly mention any platform limitations or requirements for the administrative steps, and offer guidance for Linux-based administrators where possible.
Include a section or callout that addresses cross-platform support and best practices for both Windows and Linux environments.
Review all prerequisite and configuration steps to ensure they are not exclusively tailored to Windows, and update them to be inclusive of Linux workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias: it assumes a Windows development environment by default, provides detailed steps and tooling instructions for Windows (e.g., Visual Studio, .NET Core SDK, Simulator.exe), and omits or relegates Linux/macOS instructions to external links. There are no explicit Linux or macOS command-line examples, and Windows-specific tools and patterns (like Visual Studio, Simulator.exe, and Windows command prompts) are referenced throughout, often without Linux equivalents or alternatives.

Recommendations:

Provide explicit Linux and macOS instructions and examples alongside Windows steps, not just as external links.
Include Linux/macOS command-line examples (e.g., using bash, make, gcc, or cross-platform build tools) wherever Windows commands or tools are shown.
Mention and demonstrate Linux-compatible TPM simulators and how to run them (e.g., using tpm2-software or other open-source TPM simulators).
Offer guidance for installing dependencies and building/running samples on Linux/macOS (e.g., using gcc/clang, CMake, Maven, npm, etc. on those platforms).
Avoid assuming Visual Studio or Windows-specific tools are required; clarify when cross-platform alternatives are available.
Where possible, use cross-platform language and tools (e.g., 'terminal' instead of 'command prompt', 'editor of your choice' instead of 'Visual Studio').
Ensure all code snippets and instructions are tested and validated on Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references the Teams Admin Center and PowerShell as the primary methods for learning and configuring Teams meeting settings, without mentioning Linux-compatible alternatives or command-line tools. There are no examples or guidance for Linux users, and Windows tools are presented as the default or only options.

Recommendations:

Include equivalent instructions for Linux users, such as using the Teams web interface or cross-platform CLI tools where available.
Mention that PowerShell is primarily a Windows tool and provide alternatives (e.g., Azure CLI, Microsoft Graph API) that are cross-platform.
When referencing the Teams Admin Center, clarify that it is web-based and accessible from any OS, not just Windows.
Provide explicit Linux/macOS examples or note when a tool or method is Windows-only.
Encourage the use of platform-agnostic APIs (like Microsoft Graph) for configuration and management tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing troubleshooting steps and code examples that assume the use of Windows-specific tools (Visual Studio, NuGet Package Manager Console, PowerShell) without mentioning or providing alternatives for Linux or macOS users. Instructions for package installation and Microsoft Entra configuration are exclusively given using PowerShell commands, and there are no corresponding CLI or cross-platform instructions. This may hinder users on non-Windows platforms from following the guidance effectively.

Recommendations:

Provide equivalent instructions for Linux/macOS environments, such as using the .NET CLI (dotnet add package) for NuGet package installation instead of only referencing Visual Studio and the Package Manager Console.
Include Azure CLI or Microsoft Graph CLI examples for Microsoft Entra ID administrative tasks, not just PowerShell.
Explicitly mention cross-platform alternatives and note any platform-specific limitations or differences.
Reorder or parallelize instructions so that Windows and Linux/macOS guidance are presented together, rather than Windows-first.
Add a section or callout for users on non-Windows platforms, linking to relevant setup or troubleshooting resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows a subtle Windows bias by referencing the Teams Desktop client (which is primarily associated with Windows) in all usage examples, and in one scenario, explicitly mentions 'Windows, Chrome browser' for a user. The only command-line tool referenced is a PowerShell cmdlet (Set-CsPhoneNumberAssignment), with no mention of Linux or cross-platform alternatives. There are no examples or explicit mentions of Linux clients, tools, or environments, and all example scenarios use Windows-centric language or tools.

Recommendations:

Include explicit references to Linux and macOS Teams clients where applicable, e.g., 'Teams web, desktop (Windows, macOS, Linux), and mobile clients'.
Provide command-line examples using cross-platform tools (such as Azure CLI or REST API) alongside or instead of PowerShell cmdlets.
Avoid specifying 'Windows' in user scenarios unless necessary; if specifying OS, also mention Linux and macOS where supported.
Add example scenarios where users join from Linux desktops or browsers on Linux, to demonstrate parity.
Clarify that Teams web client and SDKs are cross-platform and supported on Linux, not just Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides deployment and management instructions using both Azure CLI and Azure PowerShell, but PowerShell is given equal or sometimes more prominence than CLI, and there are no explicit Linux shell/bash examples or references. The use of PowerShell-specific cmdlets and terminology may be less familiar to Linux users. There is no mention of Linux-specific tools, shell environments, or command-line patterns, and the documentation does not clarify that Azure CLI commands are cross-platform or show them in a Linux context.

Recommendations:

Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and show example commands in a bash shell context (e.g., using $ instead of az> or PS> prompts).
Add Linux shell-specific notes or examples, such as using bash variables or scripting patterns.
Clarify that PowerShell is primarily a Windows tool, and provide guidance for Linux users who may not have PowerShell installed.
Where PowerShell is mentioned, ensure that CLI (bash) examples are given equal or greater prominence, and consider listing CLI examples first.
Include a section or note on installing and using Azure CLI on Linux, and link to relevant documentation.
Avoid using Windows-centric terminology (such as 'local computer' without specifying OS) or clarify when instructions are OS-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates subtle Windows bias. Code examples are given in C# (commonly associated with Windows development), and there are no Linux-specific or cross-platform command-line examples (such as Bash, curl, or Python). The only instructions for role assignment reference Azure CLI and Azure PowerShell, but PowerShell is mentioned first, and there is no explicit mention of Bash or Linux shell equivalents. The documentation does not provide parity for Linux users in terms of examples or tooling references.

Recommendations:

Provide code examples in cross-platform languages such as Python or Node.js, or include Bash/curl command-line snippets alongside C#.
When referencing Azure CLI, clarify that it is cross-platform and provide explicit Bash/Linux shell usage examples.
Avoid listing PowerShell before CLI or at least mention both equally, with examples for each.
Include explicit instructions or notes for Linux/macOS users where relevant, such as file system paths or shell commands.
Where SDKs or APIs are referenced, link to language-agnostic or multi-language documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the section on Quality of Service (QoS), where it references 'Windows Group Policy objects' as the method for implementing QoS and does not mention Linux or cross-platform alternatives. There are no Linux-specific tools, commands, or examples provided for network configuration, diagnostics, or log collection. The documentation assumes a Windows-centric approach in network management and does not provide parity for Linux environments.

Recommendations:

Include Linux-specific instructions or references for implementing QoS, such as using 'tc', 'iptables', or 'firewalld' for traffic shaping and prioritization.
Mention cross-platform or Linux-native tools for network diagnostics and monitoring, such as 'iftop', 'nload', or 'netstat', alongside any Windows tools.
When discussing configuration or troubleshooting steps (e.g., log collection, network setup), provide examples or links for both Windows and Linux environments.
Avoid referencing Windows-specific features (like Group Policy) as the only or primary method; instead, present platform-agnostic approaches first, or in parallel with Windows methods.
Add a section or callout for Linux administrators to ensure they can achieve the same outcomes as Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by referencing Microsoft Teams PowerShell cmdlets (e.g., Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for tenant configuration, without mentioning or providing alternatives for Linux or cross-platform environments. The prerequisite and authorization steps assume access to Windows-centric tools and administrative patterns, and PowerShell is referenced as the primary method for configuration. No Linux-native or cross-platform CLI alternatives are discussed, and the order of presentation puts Windows tooling first.

Recommendations:

Provide equivalent Azure CLI or REST API instructions for tenant-level and user policy configuration steps, so Linux and macOS users can follow along without relying on PowerShell.
Explicitly mention whether the PowerShell modules used (MicrosoftTeams, SkypeForBusiness) are available and supported on non-Windows platforms, and provide installation guidance for those environments if possible.
Add notes or links to cross-platform tools or scripts for administrative steps, or clarify if certain steps must be performed on Windows.
Where possible, present cross-platform or OS-neutral methods (such as Graph API or Azure Portal) before or alongside Windows-specific tools.
Include example commands for Linux/macOS shells (bash, zsh) where relevant, especially for steps involving API calls or scripting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is generally Linux-focused for the main tutorial steps, but there are subtle Windows biases. Windows file paths and PowerShell output are shown in examples before or instead of Linux equivalents. References to Windows-specific tools and documentation (such as opening ports in the Azure portal for Windows VMs) are present, and some output examples use Windows-style formatting. However, the actual configuration and deployment steps are performed using Bash and Azure CLI, which are cross-platform and primarily Linux-oriented.

Recommendations:

Provide Linux output examples (e.g., 'ls' command) alongside or before Windows PowerShell output when showing directory contents.
When referencing how to open ports on VMs, include links and instructions for both Windows and Linux virtual machines, not just Windows.
Avoid using Windows file paths (e.g., C:\nested-edge\output) as the only example; show Linux paths (e.g., /home/user/nested-edge/output) as well.
If showing PowerShell output, also show equivalent Bash output for parity.
Ensure that all troubleshooting and configuration steps are equally documented for both Windows and Linux environments, or clarify when steps are OS-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. It references enabling Teams Phone features via PowerShell, links to Windows-centric Teams deployment documentation, and does not provide Linux-specific guidance or examples for any administrative steps. All code samples are cross-platform JavaScript, but prerequisite and setup steps assume a Windows/PowerShell environment, with no mention of Linux alternatives or parity.

Recommendations:

Where PowerShell is referenced for enabling Teams Phone features, provide equivalent instructions for Linux/macOS users (e.g., using cross-platform PowerShell Core, or via the Teams Admin Center web UI).
When linking to Teams deployment documentation, clarify if the instructions are Windows-only or provide links to cross-platform or web-based alternatives.
Explicitly state that the JavaScript code samples and development workflow (using Node.js, webpack, etc.) are cross-platform and can be run on Linux/macOS as well as Windows.
If any administrative steps (such as retrieving Teams user IDs or managing licenses) can be performed via the Azure Portal or web interfaces, highlight these as OS-neutral options.
Add a note in the prerequisites section to reassure Linux/macOS users that the quickstart is not Windows-specific and provide any needed platform-specific tips.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a file creation command using the Windows-specific 'type nul > messages-quickstart.py' pattern, without offering an equivalent Linux/macOS example (such as 'touch messages-quickstart.py'). This prioritizes Windows tooling and omits guidance for users on other platforms.

Recommendations:

Provide both Windows and Linux/macOS commands for file creation, e.g., 'type nul > messages-quickstart.py' (Windows) and 'touch messages-quickstart.py' (Linux/macOS).
Wherever possible, use cross-platform language in instructions, or explicitly note platform differences.
Review the documentation for other implicit Windows-first patterns and ensure parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in its instructions for setting environment variables. All examples use the Windows-specific 'setx' command, and there are no equivalent instructions or examples for Linux or macOS users. Additionally, references to restarting Visual Studio as an editor reinforce a Windows-centric perspective. There are no bash or cross-platform shell examples provided.

Recommendations:

Provide equivalent Linux/macOS instructions for setting environment variables, such as using 'export' in bash/zsh or editing ~/.bashrc or ~/.zshrc.
Include both Windows (setx) and Linux/macOS (export) commands side by side or in tabbed sections.
Mention cross-platform editors (e.g., VS Code) in addition to or instead of Windows-only editors like Visual Studio.
Add a note clarifying that the instructions apply to Windows, and provide links or guidance for other operating systems.
Ensure screenshots and references are not exclusively Windows-centric, or supplement them with cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell module) for all examples and instructions. There are no CLI, Bash, or cross-platform alternatives provided, and all command-line examples are presented in a Windows PowerShell context. This creates a strong Windows bias and may hinder Linux or macOS users.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Mention and link to installation instructions for Azure CLI alongside Az PowerShell.
Clearly indicate that the PowerShell examples work on PowerShell Core (cross-platform) if applicable, or specify any Windows-only limitations.
Include Bash or shell script examples where appropriate, especially for automation scenarios.
Reorder sections or provide parallel examples so that Linux/macOS users are not required to translate Windows/PowerShell instructions themselves.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by specifically referencing Windows system tools (volume mixer, app volume settings) and providing a screenshot of the Windows volume mixer, without mentioning or illustrating equivalent controls on Linux or macOS. No Linux-specific instructions or examples are provided for checking or adjusting system or application audio settings.

Recommendations:

Add parallel instructions for checking and adjusting audio settings on Linux (e.g., using PulseAudio Volume Control/pavucontrol, ALSA mixer, or system sound settings).
Include screenshots of audio settings dialogs from popular Linux desktop environments (such as GNOME or KDE) alongside the Windows example.
Mention macOS audio controls and provide similar guidance for users on that platform.
Use neutral language such as 'system volume settings' and provide platform-specific steps in subsections or callouts, rather than focusing on Windows first.
Where possible, provide cross-platform command-line instructions (e.g., amixer for Linux, or referencing system settings for macOS) to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates some Windows bias, particularly in the 'Run the code' section, where Visual Studio Code and Visual Studio are the only editors/IDEs mentioned, with Visual Studio (a Windows-only tool) given a dedicated section. There are no explicit Linux-specific instructions or examples, and no mention of Linux-native editors or terminal usage patterns. The documentation assumes familiarity with Windows-centric tools and omits guidance for Linux users.

Recommendations:

Add a section for running the application on Linux, including instructions for using common Linux editors (e.g., Vim, Emacs, GNOME Text Editor) and terminal commands.
Include instructions for running the Python application from a generic terminal, not just from within Visual Studio Code or Visual Studio.
Mention cross-platform editors/IDEs such as PyCharm, Sublime Text, or JetBrains Fleet, and provide generic instructions that apply to all platforms.
Clarify that Visual Studio is Windows-only, and suggest equivalent steps for Linux users (e.g., running 'python main.py' from the terminal).
Ensure that all command-line instructions (such as those for Azure DevTunnels and pip) are verified to work on both Windows and Linux, and note any platform-specific differences if they exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only PowerShell (Windows-centric) commands for registering the Event Grid resource provider, with no mention of equivalent Azure CLI or Bash commands suitable for Linux or cross-platform users. This prioritizes Windows tools and patterns, potentially excluding Linux and macOS users.

Recommendations:

Add equivalent Azure CLI commands (e.g., 'az provider register --namespace Microsoft.EventGrid') alongside PowerShell examples.
Present both PowerShell and CLI/Bash examples, or default to Azure CLI for cross-platform compatibility.
Explicitly mention that the PowerShell commands are for Windows users and provide guidance for Linux/macOS users.
Consider reordering examples or providing a tabbed interface for different platforms to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_examples

⚠️ windows_heavy_symptom_descriptions

Summary:

The documentation generally provides Linux-oriented troubleshooting steps and examples (e.g., use of bash, Linux file paths, systemctl), but there are several instances of Windows bias. Windows-specific networking patterns (NAT), error messages, and symptom descriptions are mentioned before or in more detail than their Linux equivalents. Some troubleshooting sections reference Windows containers and Windows VM hostname issues, and error logs include Win32-specific messages. There are no PowerShell or explicit Windows command-line examples, but Windows is often referenced first or exclusively in certain contexts, and Windows-specific issues are described in more detail than Linux-specific ones.

Recommendations:

For every Windows-specific symptom, cause, or error message, provide the equivalent Linux details and error messages.
Where Windows networking (NAT) is discussed, explicitly describe the Linux (bridge) equivalent and troubleshooting steps.
If referencing Windows-specific error logs (e.g., hnsCall failed in Win32), provide the corresponding Linux error logs for parity.
Ensure that Linux and Windows troubleshooting steps are presented in parallel, rather than Windows-first.
If a solution is only applicable to Windows or Linux, clearly label it as such and provide the counterpart for the other OS.
Add PowerShell or Windows command-line examples where appropriate, but always provide Linux equivalents (and vice versa).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell commands and Azure PowerShell modules for all examples and instructions, with no mention of Linux-compatible alternatives such as Azure CLI, Bash, or cross-platform scripting. The prerequisite section only references the Azure Az PowerShell Module, and all code snippets are PowerShell-specific, which may not be natively available or preferred on Linux or macOS environments. There is no guidance for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
In the prerequisites, mention both Azure PowerShell and Azure CLI as options, with links to their respective installation guides.
For each operation (create, update, list, delete, verify), provide both PowerShell and Azure CLI/Bash examples side by side or in tabs.
Explicitly state that the instructions apply to all platforms, and clarify any platform-specific requirements or differences.
Consider including a note or section on how to use these commands in Bash or other shells commonly used on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows-centric tools and workflows, particularly in administrative steps involving Teams. It exclusively references the Teams Admin Center (a web interface optimized for Windows/Edge environments) and Microsoft Graph Explorer, and does not mention or provide alternatives for Linux users. There are no examples or guidance for performing equivalent administrative or setup tasks using Linux-friendly tools (e.g., Azure CLI, PowerShell Core on Linux, or REST API calls via curl). The page also omits any mention of Linux environments for development or administration, despite referencing macOS for app development.

Recommendations:

Provide alternative instructions for managing Teams Auto Attendants and Resource Accounts using cross-platform tools such as Azure CLI, Microsoft Graph API via curl, or PowerShell Core (which runs on Linux).
Include explicit Linux-compatible examples for obtaining Object IDs and managing Teams resources, such as sample curl commands for Microsoft Graph API.
Clarify that the Teams Admin Center is a web-based tool accessible from any OS, but also mention any browser or OS limitations if they exist.
Add a note or section for Linux users, outlining any differences or additional steps required for setup or administration.
Where possible, present cross-platform or Linux-first alternatives before or alongside Windows-centric tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing console usage, using PowerShell syntax for package installation, and omitting explicit Linux/macOS instructions or examples for setup and execution. All examples and setup steps assume a .NET/C# environment, which is cross-platform, but the supporting instructions and tools are presented with a Windows-first perspective.

Recommendations:

When mentioning console windows, list Bash (Linux/macOS) first or equally alongside cmd and PowerShell.
Provide explicit Linux/macOS installation and usage instructions, such as using terminal and package managers relevant to those platforms.
Show package installation commands in both PowerShell and Bash syntax, or use a generic 'dotnet' command block.
Clarify that .NET Core and the Azure Communication Services SDK are cross-platform, and provide any Linux/macOS-specific prerequisites (e.g., installing .NET SDK on Ubuntu/macOS).
Include notes or troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path differences).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by using a Windows-style file path (C:\Users\Documents\attachment.pdf) in the code example, without mentioning or providing a Linux/macOS equivalent. There are no examples or notes for Linux users regarding file paths or environment differences. The sample code and instructions assume a Windows environment, and there is no guidance for cross-platform usage.

Recommendations:

Provide file path examples for both Windows (C:\Users\Documents\attachment.pdf) and Linux/macOS (/home/user/Documents/attachment.pdf) in the code sample or add a note about cross-platform file paths.
Explicitly mention that the .NET SDK and the example code are cross-platform and can be run on Windows, Linux, and macOS.
Add a section or note about running the sample on Linux/macOS, including any relevant differences (such as file permissions or path separators).
Ensure that all examples and instructions are inclusive of non-Windows environments to improve accessibility for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides instructions and code examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no examples or guidance for sending email via SMTP from Linux or cross-platform environments, nor are alternative tools (such as sendmail, mailx, or Python scripts) mentioned. This creates a Windows-centric bias and limits accessibility for users on Linux or macOS.

Recommendations:

Add equivalent SMTP email sending examples for Linux, such as using the 'mail' or 'sendmail' command-line utilities.
Provide a cross-platform example using a language like Python (e.g., with smtplib), which works on both Windows and Linux.
Explicitly mention that the provided PowerShell example is Windows-specific, and guide users to alternative tools for other operating systems.
Include troubleshooting notes or links for common Linux SMTP tools and how to install/configure them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a subtle Windows bias. In the prerequisites, enabling Teams Phone for users references a PowerShell-based process and links to a PowerShell-specific guide, with no mention of Linux or cross-platform alternatives. There are no explicit Linux instructions or examples, and the only referenced tooling for Teams user enablement is Windows-centric. However, the main code and web app instructions are platform-agnostic.

Recommendations:

Provide Linux/macOS alternatives or clarify if the PowerShell steps can be performed using cross-platform PowerShell Core.
Explicitly mention that the web app and SDK instructions are platform-independent.
If possible, link to Teams user enablement instructions that are not Windows-specific, or clarify the requirements for Linux users.
Add a note about how to perform prerequisite steps on non-Windows systems, or state if they must be done from a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently presents Windows instructions and examples before Linux, uses PowerShell-specific commands and scripts for Windows, and references Windows-specific tools and installation methods (such as vcpkg and Set-ExecutionPolicy). While Linux parity is generally maintained with corresponding bash examples, the ordering and depth of Windows-specific tooling and scripting create a subtle Windows bias.

Recommendations:

Alternate the order of Windows and Linux sections in each major step, or present both platforms side-by-side where possible.
Provide equal detail for Linux tooling and prerequisites (e.g., mention common Linux OpenSSL installation methods, such as apt or yum, not just for Windows).
Where possible, use cross-platform tooling or highlight cross-platform compatibility of scripts.
Avoid Windows-specific terminology and tools (e.g., vcpkg, Set-ExecutionPolicy) unless a Linux equivalent or explanation is provided.
Include troubleshooting tips and environment setup steps for Linux with the same depth as for Windows.
Consider a summary table at the start showing parity of steps and commands for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias in several ways: it provides only PowerShell commands for administrative tasks (such as creating a service principal), assumes the use of Windows tools (PowerShell, Install-Module), and does not mention or provide equivalent instructions for Linux or macOS environments. There are no CLI or cross-platform alternatives for key steps, and the troubleshooting guidance is Windows-centric.

Recommendations:

Provide equivalent Azure CLI or Microsoft Graph CLI commands for all PowerShell examples, ensuring Linux and macOS users can follow the same steps.
Explicitly mention cross-platform alternatives where PowerShell is referenced (e.g., 'You can also use Azure CLI or Microsoft Graph CLI on Linux/macOS').
Add notes or sections for Linux/macOS users, including installation and usage instructions for required tools.
Where possible, use platform-agnostic language and avoid assuming the user is on Windows.
Include troubleshooting steps for non-Windows environments, such as how to install required modules or authenticate using CLI tools on Linux/macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on .NET and C# code samples, which are most commonly associated with Windows development environments. There are no examples or instructions for Linux or cross-platform usage, such as using the Azure Communication Services SDK in other languages (e.g., Python, Java, Node.js) or on non-Windows operating systems. Additionally, the prerequisite to download the .NET SDK and the lack of mention of Linux-specific tools or shell commands further reinforce a Windows-centric bias.

Recommendations:

Provide equivalent code samples in other popular languages supported by Azure Communication Services SDK (e.g., Python, Java, JavaScript/Node.js) to demonstrate cross-platform compatibility.
Include instructions or notes on how to set up the .NET SDK and run the samples on Linux and macOS, not just Windows.
Mention and provide examples of using CLI tools (such as Azure CLI) and shell commands that work across platforms, rather than focusing solely on C# and .NET.
Explicitly state the cross-platform nature of the SDKs and provide troubleshooting or environment setup tips for Linux users.
If possible, add a section or callout highlighting any platform-specific considerations or differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code) and workflows, mentioning PowerShell before Bash, and focusing on Windows development environments. There is a lack of explicit Linux or cross-platform examples, and the documentation does not provide parity for Linux users in terms of tooling or workflow guidance.

Recommendations:

Include explicit Linux and macOS examples and workflows alongside Windows ones, especially in sections discussing code editors and CLI usage.
When mentioning scripting or automation, present Bash and PowerShell examples side by side, or clarify that both are supported.
Highlight cross-platform tools (e.g., Docker CLI, VS Code) and provide guidance for users on Linux and macOS.
Add references to popular Linux editors (e.g., Vim, Emacs, JetBrains IDEs) or at least acknowledge their use.
Ensure that all resource links and tutorials are accessible and relevant for Linux users, not just Windows/Visual Studio users.
Avoid listing Windows tools or patterns first unless there is a clear reason; alternate the order or group by platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing any Linux- or macOS-specific instructions or examples. All terminal commands are generic, but there is no explicit mention of Linux or macOS environments beyond the brief mention of Bash. There are no Linux-specific troubleshooting tips, environment variable setup instructions, or editor recommendations, and the documentation implicitly assumes familiarity with Windows patterns.

Recommendations:

Explicitly mention Linux and macOS as supported platforms wherever relevant, not just in passing.
Provide Linux/macOS-specific instructions for setting environment variables (e.g., export VAR=VALUE) alongside Windows (set VAR=VALUE or $env:VAR=VALUE in PowerShell).
List Bash (or other Unix shells) first or equally when mentioning console options, e.g., 'in a console window (such as Bash, cmd, or PowerShell)'.
Include notes on using popular Linux/macOS editors (e.g., nano, vim, VS Code) for editing files, not just generic 'text editor'.
Add troubleshooting tips or notes for common Linux/macOS issues (e.g., permissions, .NET SDK installation differences).
Ensure all screenshots, if any, are cross-platform or provide both Windows and Linux/macOS examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by emphasizing Windows-specific tools and workflows, such as recommending the Universal Windows Platform workload for Unity, referencing the Windows tab in Unity Editor, and suggesting the Mixed Reality Feature Tool (a Windows-only tool). There is no mention of Linux or macOS compatibility, nor are alternative instructions or notes provided for non-Windows users. This may hinder Linux developers from following the guide or understanding platform-specific requirements.

Recommendations:

Explicitly state platform compatibility for the SDK and sample (e.g., Windows, Linux, macOS).
Provide alternative instructions for Linux and macOS users, such as how to install Unity and required workloads on those platforms.
Replace or supplement references to Windows-only tools (e.g., Mixed Reality Feature Tool) with cross-platform alternatives or clarify their platform limitations.
Avoid phrases like 'found under the Windows tab' without noting the equivalent on other platforms, or clarify if a feature is Windows-only.
If certain features are only available on Windows, clearly document this and provide workarounds or alternatives for Linux/macOS where possible.
Include troubleshooting notes or links for Linux/macOS users, especially for steps that may differ from Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it mentions Bash alongside cmd and PowerShell as possible consoles, it consistently uses Windows-centric terminology and tools first (e.g., 'cmd, PowerShell, or Bash'), and all command-line examples use the generic 'dotnet' CLI without clarifying any Linux-specific differences. There are no explicit Linux or macOS-specific instructions, troubleshooting, or environment notes, and no mention of package managers or shell conventions common to Linux users. The documentation assumes parity but does not verify or illustrate it.

Recommendations:

Explicitly state that all commands work on Windows, Linux, and macOS, and provide any OS-specific caveats if they exist.
When listing console options, rotate or randomize the order (e.g., 'Bash, cmd, or PowerShell') or mention that any terminal is supported.
Add Linux/macOS-specific notes where appropriate (e.g., file path conventions, permissions, or dependency installation).
Include at least one example of running commands in a Linux terminal (e.g., screenshots or explicit Bash prompt).
Mention how to install .NET Core on Linux and macOS, including links to official documentation for those platforms.
If there are any known differences in behavior or troubleshooting steps for Linux/macOS, document them explicitly.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing the Teams Admin Center (a web interface but often associated with Windows-centric workflows), providing resource creation links with a 'tabs=windows' parameter, and omitting any explicit Linux-specific instructions or examples. There are no mentions of Linux tools, terminal differences, or alternative admin methods (e.g., CLI, PowerShell vs. Bash). The setup and run instructions use generic commands but do not clarify cross-platform considerations, and all admin steps assume familiarity with Microsoft/Windows-centric environments.

Recommendations:

Provide explicit instructions or notes for Linux users, especially for steps involving resource creation (remove or supplement 'tabs=windows' links with Linux/CLI equivalents).
Mention and link to cross-platform or Linux-friendly tools (e.g., Azure CLI, Microsoft Graph CLI) for tasks like finding Object IDs, rather than only referencing web portals.
Clarify that all terminal/console commands are cross-platform, or provide platform-specific notes if there are differences.
Where possible, include screenshots or examples from Linux environments or clarify that the instructions are not Windows-specific.
Avoid defaulting to Windows-centric terminology or links; ensure parity in documentation structure and examples for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but the PowerShell section is given equal prominence to the CLI, and no explicit Linux or cross-platform shell examples (such as Bash or curl for REST) are provided. The UI instructions reference 'your computer's IP address' without clarifying platform differences, and screenshots are from the Azure Portal, which is platform-agnostic. However, the scripting examples are limited to Windows-centric tools (PowerShell) and the Azure CLI (which is cross-platform but not shown in a Linux-specific context), with no mention of Linux-native tools or workflows.

Recommendations:

Add explicit Bash or shell examples for Linux users, especially for REST API usage (e.g., using curl).
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and consider showing CLI output in a Linux terminal context.
If possible, provide examples using common Linux text processing tools (jq, grep) when parsing JSON output.
Mention that PowerShell Core is cross-platform, but also offer native Linux alternatives for users who may not use PowerShell.
Ensure that references to 'your computer's IP address' include notes for how to find this on both Windows and Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a subtle Windows bias: it mentions 'IBM Informix for Windows running in Azure virtualization' as a cloud-based example before any mention of Linux, and references 'Windows (kerberos)' as an authentication type without clarifying Linux support. There are no explicit Linux examples or references to Linux-specific tools or authentication patterns, and the documentation does not clarify whether the on-premises data gateway or Informix connector works equally well on Linux systems.

Recommendations:

Explicitly mention support for Linux-based Informix servers, both on-premises and in the cloud, alongside or before Windows examples.
Provide example connection strings and authentication patterns for Linux Informix deployments.
Clarify whether the on-premises data gateway can be installed and used on Linux hosts, and provide installation instructions if supported.
If authentication methods differ on Linux (e.g., Kerberos on Linux), document these options and provide guidance.
Include screenshots or walkthroughs that reference Linux environments, not just Windows.
Avoid listing Windows as the only or first example when describing supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides instructions and command-line examples for collecting verbose logs on Windows, referencing Windows file paths, executables, and omitting any mention of Linux or macOS equivalents. There are no examples or guidance for users on non-Windows platforms.

Recommendations:

Add equivalent instructions and command-line examples for Linux and macOS, including typical executable paths (e.g., /usr/bin/google-chrome, /Applications/Google Chrome.app/Contents/MacOS/Google Chrome).
Explain where log files are stored on Linux and macOS, and provide example file paths.
Mention platform-specific differences in launching browsers with command-line arguments.
Present Windows, Linux, and macOS instructions in parallel sections or tables to ensure parity and clarity for all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides troubleshooting steps for audio issues but specifically mentions Windows tools (volume mixer, app volume settings) and includes a screenshot of the Windows volume mixer. There are no equivalent instructions or screenshots for Linux or macOS systems, nor are cross-platform differences discussed. This results in a Windows-first bias and a lack of Linux parity.

Recommendations:

Add equivalent troubleshooting steps for Linux (e.g., checking PulseAudio or ALSA mixer settings) and macOS (e.g., Sound preferences, per-app volume controls).
Include screenshots of audio settings/mixers from Linux desktop environments (such as GNOME, KDE) and macOS alongside the Windows example.
Explicitly mention that app-specific volume controls and system mixers exist on other platforms, and provide guidance or links for those systems.
Rephrase instructions to address all major platforms equally, rather than focusing on Windows first.
Where platform-specific limitations exist (e.g., browser support for output device selection), clarify which platforms are affected.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows by exclusively referencing Microsoft Teams Admin Center, Microsoft Graph Explorer, and other Microsoft-centric tools, all of which are primarily web-based or Windows-oriented. There are no mentions of Linux-compatible alternatives or command-line options for Linux users. Additionally, the documentation assumes familiarity with Microsoft 365 administration patterns, which are more common in Windows environments. No Linux-specific instructions or examples are provided for managing Teams resources or interacting with Graph API.

Recommendations:

Provide CLI-based alternatives (such as using Azure CLI, Microsoft Graph CLI, or curl commands) for steps like retrieving the Call Queue Object ID, so Linux users can follow along without relying on web portals.
Explicitly mention that the Teams Admin Center and Graph Explorer are web-based and accessible from any OS, but also provide guidance for users who prefer or require command-line tools.
Include Linux-friendly instructions for all administrative steps, such as using PowerShell Core (which is cross-platform) or bash scripts where applicable.
Add a section or callout for Linux/macOS users, clarifying any platform-agnostic steps and highlighting any differences or additional requirements.
Ensure parity in tooling recommendations by listing both Windows and Linux options side-by-side where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates some Windows bias, particularly in the use of PowerShell for required configuration steps and the frequent mention of Windows-centric tools (e.g., PuTTY) and patterns. PowerShell is the only example given for service principal setup, and Windows tools are referenced before or instead of native Linux alternatives. While Linux is mentioned, parity in examples and tool recommendations is lacking.

Recommendations:

Provide equivalent Azure CLI or Bash commands for service principal and key creation steps, not just PowerShell.
When referencing SSH clients, mention native Linux/macOS SSH first, with PuTTY as an alternative for Windows users.
In connection instructions, show both command-line (ssh) and GUI (PuTTY) methods, and clarify which are for which OS.
Ensure that any step requiring scripting or automation includes both Windows (PowerShell) and Linux (Bash/Azure CLI) examples.
Review the order of presenting Windows and Linux instructions to avoid always listing Windows first.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on C# and .NET, which are traditionally Windows-centric technologies. There are no examples or guidance for Linux or cross-platform development environments. The code samples and instructions assume the use of Windows tools and patterns (such as Dispatcher, CoreDispatcherPriority, BitmapImage, and running from an IDE), with no mention of Linux equivalents or how to adapt the tutorial for non-Windows platforms.

Recommendations:

Provide equivalent code samples for Linux environments, such as using .NET Core/5+/6+ on Linux, and clarify any platform-specific dependencies.
Mention and demonstrate how to run the sample code on Linux (e.g., using VS Code, JetBrains Rider, or command-line dotnet CLI) and not just an IDE typically associated with Windows.
Replace or supplement Windows-specific UI elements (e.g., BitmapImage, Dispatcher) with cross-platform alternatives or explain how to handle image rendering in Linux-friendly frameworks (such as Avalonia, Gtk#, or MAUI).
Explicitly state platform requirements and, if possible, provide Docker or container-based instructions for maximum portability.
Add a note or section on any differences in behavior or setup when running on Linux versus Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows and Mac (Visual Studio) workflows, mentioning Windows-specific tools (GitBash, WSL) for running shell scripts, and omitting explicit instructions or support for running the sample on native Linux environments. There are no Linux-specific setup or run instructions, and the guidance assumes Visual Studio as the primary IDE, which is not natively available on Linux.

Recommendations:

Add explicit instructions for running the sample on native Linux environments, including required dependencies and compatible IDEs (e.g., VS Code, JetBrains Rider).
Provide Linux-specific alternatives for running shell scripts (e.g., bash in a Linux terminal) instead of only referencing GitBash or WSL on Windows.
Clarify which steps are cross-platform and which are specific to Windows or Mac, and ensure Linux users are not left out.
Include troubleshooting tips or notes for Linux users, especially regarding .NET MAUI support and any known limitations.
Consider referencing cross-platform tools and editors before or alongside Windows-specific ones.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing multiple PowerShell-specific examples for resource cleanup, referencing Windows command-line conventions (e.g., 'PS C:\>'), and omitting equivalent Linux/bash commands. Azure CLI is mentioned, but PowerShell commands are more prominent and appear first for some tasks. There is no explicit Linux/bash example for deleting Email Communication Services or Domain resources.

Recommendations:

Provide equivalent bash/Azure CLI commands for all resource management and cleanup tasks, especially for deleting Email Communication Services and Domain resources.
Ensure that examples are presented in a platform-neutral order or grouped by platform, rather than prioritizing Windows/PowerShell.
Avoid using Windows-specific command prompts (e.g., 'PS C:\>') unless also providing bash equivalents (e.g., '$').
Explicitly mention Linux/macOS compatibility where possible, and provide guidance for non-Windows users.
Consider adding a table or section summarizing commands for each platform (PowerShell, Azure CLI on bash, Python, etc.) to improve parity and discoverability.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for splitting reservations, with no equivalent Azure CLI (cross-platform) or Bash examples. The exclusive use of PowerShell commands assumes a Windows environment and omits guidance for Linux or macOS users. There is also a lack of mention or prioritization of cross-platform tools where applicable.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI example, which is cross-platform and works on Windows, Linux, and macOS.
Explicitly mention that the Azure CLI can be used for these operations and provide sample CLI commands.
Where possible, include Bash script examples or note that the CLI commands can be run in Bash or other shells.
Add a section or note clarifying tool availability and platform compatibility (e.g., 'The following examples use PowerShell, but you can also use Azure CLI on any platform').
Review for other sections where Windows-specific tools or patterns are referenced and ensure Linux/macOS parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ cmd_examples

⚠️ missing_linux_example

Summary:

The documentation provides a mix of Bash and CMD examples, but in several sections, Windows CMD syntax is used without equivalent Linux/Bash examples, especially for commands like 'iotedge logs', 'docker rm', and 'iotedge restart'. Some code blocks are marked as 'cmd' or use Windows-centric syntax, and in a few cases, the documentation does not clarify cross-platform differences or provide Linux alternatives. While the initial troubleshooting steps use Bash, later sections implicitly assume Windows usage or present Windows commands first.

Recommendations:

For every CMD/Windows example, provide an equivalent Bash/Linux example side-by-side or clearly indicate cross-platform compatibility.
Use neutral code block labeling (e.g., 'shell') unless the command is truly platform-specific.
Clarify any differences in command usage or output between Windows and Linux environments.
Audit all command examples to ensure Linux users are not left to infer the correct syntax or behavior.
Where tools or paths differ between platforms, explicitly document both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft-centric tools and workflows, such as Visual Studio Code, Microsoft Teams Toolkit, and Azure Functions, without mentioning or providing guidance for Linux environments. There are no examples or instructions for Linux users, and all tooling references assume a Windows or Microsoft ecosystem. This may hinder accessibility for developers working on Linux or non-Windows platforms.

Recommendations:

Include explicit instructions or notes for Linux users, such as how to install and use the Teams Toolkit and Azure Functions CLI on Linux.
Provide cross-platform command-line examples (e.g., using bash or zsh) alongside any GUI-based instructions.
Mention alternative editors and development environments (such as VS Code on Linux, or JetBrains IDEs) and clarify that the Teams Toolkit is available cross-platform.
Add troubleshooting tips or links for common Linux-specific issues (such as permissions, package installation, or environment setup).
Ensure that all code samples and project setup steps are tested and documented for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows mild Windows bias. While the main tutorial flow is Linux-focused (Linux containers, Linux device quickstart), there are several signs of Windows bias: (1) The sample images are sourced from a repository named 'Cognitive-CustomVision-Windows', with no mention of a Linux equivalent or alternative; (2) The device setup section lists 'Linux device' before 'Windows device', but only provides a link to a Windows quickstart as an alternative, not as a parallel path; (3) There are no explicit PowerShell or Windows command-line examples, but the documentation does not provide any Linux-specific troubleshooting or alternative flows for common Windows-only issues (e.g., file paths, permissions); (4) The use of Visual Studio Code and Azure IoT Edge Dev Tool is cross-platform, but the documentation does not clarify any Linux-specific nuances or provide Linux-first examples for all steps.

Recommendations:

Provide sample images from a neutral or Linux-named repository, or clarify that the 'Cognitive-CustomVision-Windows' repo is cross-platform.
Include explicit Linux and Windows command-line examples where relevant, especially for file paths and Docker commands.
Add troubleshooting notes for common Linux-specific issues (e.g., permissions, Docker group membership, file system case sensitivity).
Ensure that all tool references (e.g., Visual Studio Code, Docker) clarify cross-platform compatibility and provide links to both Linux and Windows installation guides.
Where device setup is discussed, offer parallel quickstart links and instructions for both Linux and Windows, rather than listing Windows as an alternative.
If referencing Windows tools or repositories, provide Linux equivalents or clarify their cross-platform usage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows and PowerShell users. All code samples are written in PowerShell, and the instructions assume the use of PowerShell as the scripting environment. Installation links and prerequisite checks are Windows-centric, and there are no equivalent Bash or Linux shell examples. This makes it difficult for Linux or macOS users to follow the guide without significant adaptation.

Recommendations:

Provide parallel Bash (Linux/macOS) script examples for all PowerShell commands, especially for Azure CLI usage, variable initialization, and scripting logic.
Include installation instructions and links for Azure CLI and Azure PowerShell for Linux and macOS, not just Windows.
When referencing command-line environments, mention both Windows (PowerShell/Command Prompt) and Linux/macOS (Bash/Terminal) explicitly.
Add a section or callouts that highlight any differences or considerations for Linux/macOS users.
Consider using cross-platform scripting approaches (e.g., pure Azure CLI in Bash) for automation tasks, or at least provide both PowerShell and Bash versions side by side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the use of PowerShell for configuration changes to Microsoft Teams Direct Routing, without mentioning or providing alternatives for Linux or cross-platform environments. There are no examples or references to Linux tools or command-line interfaces, and the workflow is described in a way that presumes a Windows-centric administrative environment.

Recommendations:

Provide equivalent instructions or references for performing Microsoft Teams Direct Routing configuration using cross-platform tools (such as Azure CLI, Microsoft Graph API, or Teams Admin Center web UI) where possible.
Explicitly mention whether PowerShell Core (which is cross-platform) can be used, and provide installation guidance for Linux/macOS if applicable.
Include examples or notes for Linux administrators, such as how to access required admin centers or perform tasks from non-Windows systems.
Clarify any steps that are inherently Windows-only, and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias in the prerequisites section by linking only to Windows-specific Azure CLI installation instructions and using a resource creation link with a 'tabs=windows' parameter. There are no Linux or macOS equivalents or instructions provided for these steps, and no mention of cross-platform compatibility for the CLI or resource setup. The rest of the documentation is platform-agnostic JavaScript, but the initial setup is Windows-centric.

Recommendations:

Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows instructions.
Use neutral or platform-agnostic links for resource creation and CLI installation, or include tabs for all major platforms.
Explicitly state that the Azure CLI and SDK are cross-platform, and provide guidance for users on Linux and macOS.
Review all prerequisite steps to ensure parity and clarity for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation shows evidence of Windows bias, primarily through the use of Windows-specific tools and patterns. The prerequisite section requires Visual Studio (a Windows-centric IDE) and the package installation example uses PowerShell syntax. There are no Linux/macOS equivalents or alternatives mentioned for development environment setup or package installation. The documentation assumes a Windows development environment and does not provide parity for Linux users.

Recommendations:

Include instructions for installing the .NET SDK and the Azure Communication Services Chat SDK using cross-platform tools (e.g., dotnet CLI) and show command-line examples in bash/zsh as well as PowerShell.
Mention Visual Studio Code as an alternative to Visual Studio, and provide setup steps for Linux/macOS users.
Add explicit notes or sections for Linux/macOS users in the prerequisites, including any required dependencies or differences in environment setup.
Avoid using PowerShell-specific syntax for generic .NET package installation; prefer the dotnet CLI, which is cross-platform.
Where possible, provide side-by-side or clearly marked examples for both Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both Bash and PowerShell examples for querying logs, but the Bash examples use the non-standard 'SET' command for variable assignment, which is a Windows CMD syntax, not valid in Bash or Linux shells. This may confuse Linux users. Additionally, PowerShell examples are always present, and sometimes appear before or alongside Bash, indicating a slight Windows-first approach. There are no Linux-specific instructions or troubleshooting tips, and the CLI examples do not use standard Linux shell conventions.

Recommendations:

Replace 'SET $WORKSPACE_ID=<WORKSPACE_ID>' in Bash examples with the correct Bash syntax: 'WORKSPACE_ID=<WORKSPACE_ID>'.
Ensure Bash/Linux examples use standard shell conventions and are tested in a Linux environment.
Consider placing Bash/Linux examples before PowerShell to reflect the prevalence of Linux in containerized/cloud environments.
Add Linux-specific notes or troubleshooting tips where relevant.
Clarify which examples are for Windows CMD, PowerShell, or Bash, and avoid cross-polluting syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the use of Windows-specific terminology and claims in example outputs (e.g., 'x-ms-azurevm-is-windows': true, 'x-ms-azurevm-ostype': 'Windows'), and by referencing Windows as the default or only operating system in JSON web token examples. There are no explicit Linux or cross-platform usage examples, nor are Linux-specific tools, claims, or patterns mentioned. The documentation does not provide parity in examples or guidance for Linux-based confidential VMs.

Recommendations:

Include example JSON web tokens and claims for Linux-based confidential VMs, such as 'x-ms-azurevm-ostype': 'Linux' and related fields.
Explicitly mention that the attestation process and APIs are cross-platform, and provide guidance or notes for both Windows and Linux environments.
Add Linux-specific operational scenarios or diagrams, or clarify that the described scenarios apply equally to Linux workloads.
Reference Linux tools or libraries (if available) for guest attestation, or provide sample code snippets for both Windows and Linux.
Ensure that any sample outputs, especially in the 'JSON web token' section, alternate or include Linux values and not just Windows defaults.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI, but often associated with Windows-centric workflows), and by providing instructions and screenshots that assume use of the Azure portal UI. There is no mention of Linux command-line tools (such as Azure CLI or azcopy), nor are there any PowerShell or CLI examples, but the only non-portal tool mentioned is Visual Studio Code, which is cross-platform. However, all step-by-step instructions for finding connection strings, access keys, and configuring storage accounts are written in terms of navigating the Azure portal UI, which is more familiar to Windows users. There are no examples or instructions for performing equivalent tasks using the Azure CLI, Bash, or other Linux-native tools. Additionally, the documentation refers to App Service Environment v3 as 'Windows plans only' without clarifying Linux support or alternatives.

Recommendations:

Add parallel instructions and examples for performing all key tasks (such as retrieving storage account keys, connection strings, and configuring networking/firewall rules) using the Azure CLI, which is available on Linux, macOS, and Windows.
Where screenshots are provided for the Azure portal, also provide equivalent CLI commands (e.g., az storage account show-connection-string, az storage account keys list, az storage container create, etc.).
Explicitly mention that Visual Studio Code is cross-platform and provide any Linux/macOS-specific setup notes if relevant.
Clarify whether App Service Environment v3 or other features are available or supported on Linux plans, and provide guidance for Linux users if there are differences.
Include a section or callout for Linux/macOS users, summarizing the parity of features and tools, and linking to relevant documentation for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the on-premises data gateway and Oracle client are installed on a generic 'computer', but all troubleshooting, installation, and service references (e.g., PBIEgwService) are specific to Windows environments. There are no Linux-specific instructions, examples, or troubleshooting steps, and the gateway is implicitly treated as a Windows-only tool.

Recommendations:

Explicitly state whether the on-premises data gateway is supported on Linux, and if so, provide installation and troubleshooting steps for Linux environments.
Include Linux-specific examples for installing the Oracle client and managing the gateway service (e.g., systemd commands).
When referencing services (like PBIEgwService), clarify that this is the Windows service name and provide the equivalent for Linux if available.
Add troubleshooting steps and common error resolutions for Linux users.
Avoid using generic terms like 'computer' when the instructions are Windows-specific; specify the OS or provide parallel instructions for both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in the 'Run a sample application' section, where instructions and commands are provided specifically for Windows environments (Visual Studio, .cmd commands, .exe output), with only a brief mention that other environments are possible and a link to external documentation for Linux or cross-platform builds. There are no explicit Linux or macOS build/run instructions, and Windows tools (Visual Studio, Visual Studio Code) are referenced first and in detail.

Recommendations:

Add explicit Linux and macOS instructions for building and running the C SDK sample, including required dependencies (e.g., gcc/clang, make, cmake) and terminal commands.
Provide example shell commands (bash) for cloning, building, and running the sample on Linux/macOS, alongside the Windows .cmd examples.
Mention cross-platform editors (such as VS Code, which is already referenced) and provide parity in instructions for both Windows and Linux/macOS users.
Where Windows-specific tools (Visual Studio, .exe) are mentioned, add equivalent alternatives for Linux/macOS (e.g., gcc, ./iothub_ll_telemetry_sample).
Consider reordering or parallelizing instructions so that Windows and Linux/macOS steps are presented together, rather than Windows-first.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias primarily through its exclusive reliance on Windows-only tooling (the 3270 Design Tool requires Microsoft .NET Framework 4.8), lack of mention of Linux-compatible alternatives, and by referencing App Service Environment v3 'with Windows plans only' without clarifying Linux support or alternatives. There are no Linux-specific instructions, examples, or tool recommendations, and the prerequisites and setup steps assume a Windows environment.

Recommendations:

Provide information on whether the 3270 Design Tool can run on Linux (e.g., via Mono or Wine), or recommend Linux-compatible alternatives if available.
Clarify whether the Logic Apps Standard environment supports Linux plans and, if so, provide equivalent instructions for Linux users.
Include explicit notes or examples for Linux users, such as how to upload HIDX files or interact with Azure Logic Apps from Linux-based environments.
If no Linux alternatives exist for required tools, state this clearly and suggest possible workarounds or roadmap intentions for Linux support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer and requiring Microsoft .NET Framework 4.8 for metadata generation, both of which are Windows-only tools. There are no mentions of Linux-compatible alternatives or instructions for Linux users. All setup and prerequisite instructions assume a Windows environment, and the documentation does not acknowledge or provide parity for Linux-based development workflows.

Recommendations:

Explicitly state platform requirements and limitations (e.g., HIS Designer is Windows-only) at the start of the prerequisites section.
Provide guidance or workarounds for Linux users, such as using a Windows VM, Docker container, or remote desktop to access HIS Designer.
Investigate and document any cross-platform or open-source alternatives for generating HIDX files, or clarify if none exist.
Include a section addressing Linux/macOS users, outlining the steps they need to take or the limitations they will encounter.
If possible, advocate for or develop a cross-platform version of the HIS Designer tool, or provide a REST API for HIDX generation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed Azure PowerShell instructions and troubleshooting, while omitting equivalent examples for Linux-native tools (such as Azure CLI, Bash, or scripting with curl). The PowerShell method is given a dedicated section, and no Linux/Unix shell examples are provided for updating configuration or troubleshooting. The focus on PowerShell and lack of cross-platform command-line guidance may disadvantage Linux users.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell instructions, including configuration updates and troubleshooting steps.
Provide Bash/curl examples for interacting with the Azure Resource Management API, showing how to PATCH the resource using standard Linux tools.
Explicitly mention that all command-line steps can be performed on Linux/macOS, and provide platform-agnostic instructions where possible.
Ensure troubleshooting steps are not PowerShell-specific and include guidance for Linux users.
Consider reordering or presenting PowerShell and CLI/Bash examples side-by-side to avoid a 'Windows-first' impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a moderate Windows bias. Portal-based troubleshooting steps are described in a way that assumes familiarity with the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. In the 'Verify accessibility of container image' section, the only explicit OS-specific note is for Docker on Windows, with no mention of Linux or macOS Docker usage. In the 'Verify latest version of Azure Container Apps extension is installed' section, both Bash (Azure CLI) and PowerShell examples are provided, but PowerShell is given a dedicated tab and more detailed instructions, including module installation and update commands. There are no Linux-specific troubleshooting tools, commands, or notes, and no mention of running commands in a Linux shell or terminal. The only command-line example that could be OS-specific (docker run) is shown in a generic way, but the supporting text references 'elevated command prompt' and Docker on Windows, with no equivalent Linux/macOS instructions.

Recommendations:

When referencing Docker, include instructions or notes for both Windows and Linux/macOS users (e.g., mention 'open a terminal or command prompt' and provide links to Docker installation for all platforms).
Where 'elevated command prompt' is mentioned, add Linux/macOS equivalents (e.g., 'use sudo if necessary').
In sections with PowerShell examples, ensure Bash/Azure CLI examples are equally prominent and detailed.
If referencing OS-specific issues (like Docker Desktop on Windows), add parallel notes for Linux/macOS (e.g., checking Docker daemon status on Linux).
Consider including troubleshooting steps or examples that are specific to Linux environments, such as checking system logs or network configuration using Linux tools.
Review the ordering of examples and avoid always listing Windows/PowerShell first; alternate or present Bash/Azure CLI first where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on the Power BI app and Power BI Desktop, which are primarily Windows-based tools. There are no examples or instructions for Linux users, nor are alternative cross-platform tools or methods mentioned. The only operating system-specific reference is to Windows Server AHB usage, with no mention of Linux VM equivalents. The documentation assumes the reader is using Windows and does not provide parity for Linux environments.

Recommendations:

Explicitly state the platform requirements for Power BI App and Power BI Desktop, including any limitations for Linux or Mac users.
If possible, provide alternative instructions or tools for Linux users, such as using Power BI on the web or exporting data for analysis in cross-platform BI tools (e.g., Tableau, Apache Superset, or Jupyter Notebooks).
Include a section addressing Linux users, clarifying what is and isn't supported, and suggest workarounds or equivalent workflows.
When referencing VM usage (e.g., Windows Server AHB Usage), also mention Linux VM cost management features or reports, if available, to provide parity.
Ensure troubleshooting and authentication steps note any OS-specific differences, especially for authentication dialogs or file downloads.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates Windows bias primarily through its exclusive reference to the Windows PowerShell cmdlet (Get-AzAccessToken) for obtaining a Bearer access token, without mentioning Linux or cross-platform alternatives. There are no CLI or Bash examples, and the only tool referenced for authentication is a Windows-centric PowerShell module. This may hinder Linux users or those using non-Windows environments from easily following the instructions.

Recommendations:

Provide equivalent Azure CLI (az account get-access-token) instructions for obtaining a Bearer access token, which works on Windows, Linux, and macOS.
Include Bash/cURL examples for making REST API requests, not just REST request syntax.
Avoid referencing only PowerShell modules; when mentioning tools, list cross-platform options first or alongside Windows-specific tools.
Explicitly state that the instructions apply to all platforms, and provide links to relevant Linux/macOS guidance where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by recommending Docker Desktop (which is primarily for Windows and macOS) as the default Docker installation method, and by not mentioning Linux installation or tools explicitly. Visual Studio Code is presented as the primary editor, with no mention of Linux-native editors or workflows. There are no Linux-specific installation instructions or troubleshooting steps, and the document assumes the reader is using tools and patterns most common on Windows or macOS. No Linux package manager commands or Linux-specific Docker installation guidance is provided.

Recommendations:

Add explicit instructions for installing Docker Engine on Linux distributions (e.g., Ubuntu, Fedora), including package manager commands.
Mention Linux-native editors (such as Vim, Emacs, or JetBrains IDEs) as alternatives to Visual Studio Code, or clarify that VS Code is cross-platform.
Include verification steps and troubleshooting commands that are relevant to Linux environments (e.g., using systemctl to check Docker service status).
When referencing Docker Desktop, clarify that on Linux, Docker Engine is installed directly and Docker Compose may need to be installed separately.
Provide example shell commands that work on Linux (e.g., using sudo where appropriate, or noting differences in file paths and permissions).
Ensure that all tool recommendations and workflows are presented in a cross-platform manner, or provide parallel instructions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas: Windows-based tools and workflows (Visual Studio, PowerShell, Windows command prompt) are presented as defaults or with more detailed instructions, while Linux alternatives are either referenced externally, presented after Windows, or lack parity in detail. Some sections (notably for C/C#) assume a Windows environment and only briefly mention Linux, often redirecting to external documentation. Windows-specific tools (e.g., Visual Studio, PowerShell) are emphasized, and Linux instructions are sometimes missing or less detailed.

Recommendations:

Provide Linux and macOS instructions alongside Windows in all language pivots, not just as external references.
Avoid language such as 'This tutorial is oriented toward a Windows-based workstation' or, if necessary, ensure equivalent Linux/macOS guidance is present in the same document.
For C/C++ development, include explicit Linux build instructions (e.g., using gcc/clang, make, or CMake on Linux) within the main flow, not just as a link.
For device key derivation, ensure Linux and macOS examples are as prominent and detailed as Windows/PowerShell ones.
Where Windows tools (Visual Studio, PowerShell) are mentioned, provide direct Linux/macOS alternatives (e.g., GCC/Clang, shell scripts) in the same section.
Use neutral language in prerequisites and setup steps (e.g., 'On your development machine' instead of 'on your Windows-based machine'), and clarify cross-platform compatibility.
Ensure all code samples and command-line instructions are provided for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh), with clear tabbed or side-by-side presentation.
Where possible, avoid requiring Windows-only tools for cross-platform SDKs, or provide equivalent open-source alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by describing performance tests and sample applications exclusively on Windows 10, using .NET and the Azure Data Movement Library (DML), which are Windows-centric technologies. There are no examples or mentions of Linux or cross-platform alternatives for copying blobs or automating exports. The test environment, tooling, and code samples are all Windows-focused, and Linux users are not provided with equivalent guidance or tooling references.

Recommendations:

Include equivalent Linux-based examples for copying large Azure storage blobs, such as using AzCopy, Azure CLI, or Python SDK scripts.
Mention and provide sample commands for cross-platform tools (e.g., AzCopy, Azure CLI) before or alongside Windows/.NET examples.
Describe performance testing or usage on Linux environments, including any differences or considerations.
Reference and link to documentation or guides for Linux users on automating exports and handling large blob transfers.
Avoid assuming the reader is using Windows by default; clarify that the .NET/DML approach is one of several options.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell for automation and GUID generation, referencing Windows-centric tools (Visual Studio, PowerShell), and omitting Linux-specific or cross-platform command-line examples for key tasks. While curl is mentioned, the primary automation flow and examples assume a Windows/PowerShell environment, with no Linux shell or CLI parity.

Recommendations:

Provide equivalent Linux/bash command-line examples for all PowerShell commands (e.g., show how to generate a GUID with uuidgen or openssl).
List cross-platform tools (curl, httpie, Postman, etc.) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Include Linux/macOS authentication and scripting guidance (e.g., Azure CLI usage, bash scripts) alongside PowerShell.
Clarify that all REST API examples are platform-agnostic and provide sample requests using curl or httpie.
Avoid assuming the user is on Windows; use neutral language and tool ordering.
Where screenshots or instructions reference Windows UI, note any differences for Linux/macOS users or provide alternative instructions if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by consistently presenting command-line examples with Windows-style prompts (C:\>), listing PowerShell instructions before Azure CLI, and referencing PowerShell modules and workflows. There is no mention of Linux or macOS environments, and all CLI examples use Windows paths and conventions, which may confuse or alienate Linux/macOS users.

Recommendations:

Provide command-line examples using both Windows (PowerShell/CMD) and Linux/macOS (bash) syntax, including appropriate prompts (e.g., $ for bash).
Avoid using Windows-specific paths (C:\>) in Azure CLI examples; use generic or cross-platform prompts (e.g., $ or az ...).
Explicitly mention that the Azure CLI and PowerShell modules are cross-platform, and provide installation or usage notes for Linux/macOS where relevant.
Ensure that instructions for installing tools (like Azure CLI extensions) include Linux/macOS commands and package managers.
Consider reordering sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell.
Add a note or section addressing any platform-specific differences or requirements.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively provides a PowerShell script and instructs users to use PowerShell in Azure Cloud Shell, with no mention of Bash, Linux shell scripting, or cross-platform alternatives. The instructions and screenshots prioritize PowerShell, and there are no examples or guidance for users on Linux or macOS who may prefer Bash or other scripting environments.

Recommendations:

Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify if the process can be performed in Bash.
Include notes or links to cross-platform tools or scripts where possible.
If PowerShell is required due to specific module support, explain why and provide installation instructions for PowerShell Core on Linux/macOS.
Add a section addressing Linux/macOS users, outlining any differences or additional steps needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows some Windows bias, particularly in the .NET/C# section, where Windows (ETW and PowerShell scripts) is described first and in more detail, with Linux instructions following. The Windows approach uses specialized tools (ETW, PowerShell scripts), while the Linux approach uses a more generic tool (dotnet-trace). There is also a slight bias in the Java example, where the log file path uses a Windows-style path (c/temp/logs) without a Linux alternative.

Recommendations:

Present Linux and Windows instructions in parallel or in a consistent order (e.g., alphabetical or by usage share), rather than always listing Windows first.
Ensure that Linux tooling is described with equal detail and prominence as Windows tools (e.g., provide troubleshooting tips, links, and context for dotnet-trace similar to ETW).
Avoid using Windows-centric paths (e.g., 'c/temp/logs') in cross-platform examples; instead, provide both Windows and Linux path examples or use neutral paths.
Where possible, mention cross-platform tools and approaches before platform-specific ones.
If PowerShell scripts are provided for Windows, consider providing equivalent Bash scripts for Linux where feasible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented around the Azure portal web interface, with all instructions and screenshots assuming use of a graphical browser. There are no command-line examples or automation options provided (e.g., Azure CLI, PowerShell, or REST API), and no mention of Linux or cross-platform tooling. The only tool mentioned for automation is Terraform, but even that is referenced as a link rather than an integrated example. This approach implicitly favors Windows users, who are more likely to use the Azure portal and PowerShell, and does not address the needs of Linux users or those who prefer command-line or automated workflows.

Recommendations:

Add equivalent instructions and examples for managing billing accounts using the Azure CLI (az), which is cross-platform and widely used on Linux.
Where possible, provide REST API examples (with curl or similar tools) for key operations, to support automation and scripting on any OS.
If PowerShell is referenced, ensure Azure CLI or bash alternatives are given equal prominence and appear before or alongside PowerShell examples.
Explicitly mention that all portal-based steps can be performed from any OS with a supported browser, but highlight CLI/API options for users who prefer or require non-GUI workflows.
Include links to Azure CLI and REST API documentation for billing/account management tasks.
Consider adding a section or callout for Linux/macOS users, summarizing available tools and approaches for managing billing outside the Azure portal.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by referencing Windows-centric tools and workflows, such as Visual Studio Code and C# SDK examples, without providing equivalent Linux or cross-platform alternatives. The only code sample for decoding messages refers to a C# method, and the monitoring tip suggests using the Visual Studio Code extension, which is more commonly associated with Windows development. There are no explicit Linux or cross-platform code examples for tasks like decoding messages or monitoring the IoT Hub, and the documentation does not mention Linux-specific tools or workflows.

Recommendations:

Provide code examples for decoding messages in cross-platform languages such as Python or Bash, in addition to the C# example.
Mention and provide instructions for using cross-platform editors and tools (e.g., VS Code is cross-platform, but clarify this and suggest alternatives like Vim, nano, or CLI-based monitoring tools).
Include Linux-specific instructions or tips for tasks such as downloading and viewing files, decoding base64/UTF-8 messages using command-line utilities (e.g., base64, iconv, cat).
When referencing SDK samples, link to equivalent samples in other languages (e.g., Python, Node.js) that are popular on Linux.
Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific caveats if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias by exclusively referencing Windows Server and SQL Server on Windows, with no mention of Linux-based SQL Server deployments or examples. All references to SQL Server VMs and IaaS extensions point to Windows-specific documentation. There are no examples or guidance for users running SQL Server on Linux VMs in Azure, nor are Linux tools or management patterns discussed.

Recommendations:

Include explicit references to SQL Server on Linux, clarifying whether Azure Hybrid Benefit applies equally to Linux-based SQL Server VMs.
Provide parallel documentation links and examples for registering SQL Server on Linux VMs with the SQL IaaS Agent extension.
Mention any differences (or confirm parity) in license assignment, management, and monitoring for SQL Server on Linux versus Windows.
If certain features or extensions are Windows-only, clearly state this and provide alternative guidance for Linux users.
Ensure that all screenshots, walkthroughs, and step-by-step instructions are inclusive of both Windows and Linux scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows-based VM examples (Standard_DS1_v2 Windows virtual machine) and referencing Windows software costs. There are no examples or mentions of Linux VMs or Linux-specific considerations, and the only software cost discussion is for Windows. This may give the impression that reservations are primarily or only relevant for Windows workloads, and omits guidance for Linux users.

Recommendations:

Include parallel examples using a popular Linux VM SKU (e.g., Standard_DS1_v2 running Ubuntu or another Linux distribution) alongside the Windows example.
Discuss how reservation usage and software costs apply to Linux VMs, including any differences (such as the absence of extra OS licensing charges for most Linux distributions).
Reference Linux-specific documentation or considerations where relevant, such as Azure Hybrid Benefit for Linux or BYOL (Bring Your Own License) scenarios.
Ensure that screenshots and CSV file examples include both Windows and Linux VM reservations to illustrate parity.
Add a section or note explicitly stating that the reservation process and CSV analysis apply equally to Linux VMs, and highlight any differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by prioritizing PowerShell-based instructions and tools, referencing Windows-centric patterns, and not providing explicit Linux/macOS guidance or examples. PowerShell is mentioned and exemplified before Azure CLI, and there is no discussion of cross-platform shell usage or Linux-specific considerations. The documentation assumes familiarity with Windows tools and does not address potential differences or requirements for Linux users.

Recommendations:

Provide explicit Linux/macOS instructions and examples, especially for authentication and environment setup (e.g., clarify that Azure CLI and PowerShell Core are cross-platform, and show usage in bash/zsh).
When listing tooling (e.g., PowerShell, Azure CLI), present Azure CLI examples first or in parallel, as it is natively cross-platform.
Include notes or sections on any OS-specific prerequisites, such as package managers for installing Azure CLI or PowerShell on Linux/macOS.
Where PowerShell cmdlets are referenced, clarify if they require Windows PowerShell or if they work with PowerShell Core on Linux/macOS.
Add screenshots or terminal output examples from Linux/macOS environments where applicable.
Explicitly state that all command-line steps can be performed on Linux/macOS, and provide troubleshooting tips for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong bias toward Windows by exclusively providing Azure PowerShell scripts and instructions for managing Azure reservations. There are no examples or guidance for using cross-platform tools such as Azure CLI, nor are there any references to Linux or macOS environments. The use of PowerShell, which is traditionally associated with Windows (despite now being cross-platform), and the absence of Azure CLI or REST API examples, limits accessibility for Linux and macOS users.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell scripts and management tasks, as Azure CLI is widely used on Linux and macOS.
Explicitly mention that PowerShell Core is cross-platform, and provide installation instructions for Linux/macOS if PowerShell usage is retained.
Include REST API examples or references for advanced users who may prefer scripting without PowerShell.
Ensure that all instructions and screenshots (if any) are applicable to users on Linux, macOS, and Windows.
Review and update the documentation to use neutral, cross-platform language (e.g., 'command line' instead of 'PowerShell prompt').

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides examples using armclient with PowerShell syntax and Azure PowerShell code blocks. There are no examples or instructions for Linux or cross-platform CLI tools (such as Azure CLI or curl), nor is there mention of how to perform these tasks on non-Windows systems. The use of PowerShell and armclient (which is most commonly used on Windows) is presented as the default and only method, indicating a Windows-first and PowerShell-heavy bias.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
Include REST API call examples using curl or httpie, which are standard tools on Linux.
Use generic code blocks (e.g., ```bash or ```sh) for REST API examples, not just ```azurepowershell-interactive.
Explicitly mention that the operations can be performed from any OS, and clarify any tool prerequisites for Linux/macOS users.
If armclient is required, provide installation and usage instructions for Linux/macOS, or suggest alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing PowerShell scripts for license usage analysis, without providing equivalent examples or guidance for Linux users. No mention is made of Bash, Azure CLI, or cross-platform tooling, and the only script linked is a PowerShell script. There are no Linux-specific instructions or examples, and the documentation assumes the use of Windows-centric tools.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for analyzing SQL license usage, ensuring Linux and macOS users can follow along.
Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, or provide guidance for cross-platform compatibility.
Include references to cross-platform tools (such as Azure CLI) wherever PowerShell is mentioned, and offer side-by-side examples.
Review all instructions and ensure that Linux users are not required to use Windows-specific tools or interfaces.
Add a note clarifying platform compatibility for any scripts or tools referenced.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses Microsoft Excel for all examples and instructions, implicitly assuming a Windows environment. There are no examples or guidance for users on Linux or macOS, such as using LibreOffice Calc or command-line tools (e.g., csvkit, pandas). Keyboard shortcuts and UI references are specific to Excel, and no alternatives are mentioned. This creates a Windows-centric experience and may alienate users on other platforms.

Recommendations:

Include parallel instructions and screenshots for at least one cross-platform or Linux-native spreadsheet application, such as LibreOffice Calc or Google Sheets.
Mention and provide basic examples for command-line tools (e.g., csvkit, pandas) to manipulate and analyze CSV usage files, especially for large files.
Use neutral language when referring to spreadsheet applications (e.g., 'spreadsheet application such as Excel or LibreOffice Calc') and avoid assuming Excel is available.
Provide keyboard shortcuts and menu navigation for both Windows and Linux/macOS environments where relevant.
Add a section or callout for Linux/macOS users outlining alternative workflows for analyzing large CSV files.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes components and environments for Azure-SSIS Integration Runtime on Windows Server 2019, with no mention of Linux support, alternatives, or parity. All listed tools, drivers, and tasks are Windows-centric (e.g., Access Database Engine, WMI, MSMQ, SQL Server Native Client), and there are no Linux equivalents or cross-platform notes. The documentation assumes a Windows-only environment and does not acknowledge or provide guidance for Linux users.

Recommendations:

Explicitly state in the introduction that Azure-SSIS IR currently only supports Windows, if that is the case, or clarify any Linux roadmap.
If Linux support is planned or available, provide a parallel table or section listing Linux-compatible components, drivers, and tasks.
For each Windows-specific tool or component (e.g., WMI, MSMQ, Access Database Engine), mention if a Linux equivalent exists or if the functionality is unavailable on Linux.
Add a section on cross-platform considerations, including any limitations or workarounds for Linux users.
Where possible, provide examples or documentation links for configuring or running SSIS packages on Linux (e.g., using containers, Mono/.NET Core, or alternative runtimes).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both SSH (Linux) and RDP (Windows) connection methods, but Windows-specific tools and workflows (such as the Microsoft RDP client and RDP tunneling) are described in more detail. There are explicit instructions for launching the Microsoft RDP client on Windows and OSX, but no equivalent details for Linux RDP clients. Additionally, when discussing connecting to services, the only concrete example given is for Windows Remote Desktop, with no Linux service examples provided.

Recommendations:

Include explicit examples of connecting to Linux services (e.g., tunneling to a web server or database on a Linux VM) to balance the Windows RDP example.
When describing RDP access, mention and provide example commands for popular Linux RDP clients (such as Remmina or rdesktop) alongside Windows and OSX.
Ensure that instructions for launching remote desktop clients are provided for all major platforms, not just Windows and OSX.
Consider alternating the order of Windows and Linux examples, or presenting them in parallel, to avoid a 'windows_first' perception.
Where possible, provide parity in depth and detail for both Windows and Linux workflows throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the Azure Batch section, where PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are referenced as primary methods for resource creation and management, with no equivalent CLI, Bash, or Linux-native instructions provided. Additionally, Microsoft Azure Storage Explorer (a Windows-centric tool) is recommended for blob storage management, and references to 'CMDLETs & APIS' for VM sizing reinforce a Windows-first approach. While the HDInsight examples are Linux-based and the JSON configuration is OS-agnostic, the overall pattern prioritizes Windows tools and workflows.

Recommendations:

Provide equivalent Azure CLI and Bash script examples alongside PowerShell cmdlets, especially for Azure Batch and resource management tasks.
Mention and link to cross-platform or Linux-native tools for Azure Blob Storage management (e.g., Azure CLI, azcopy, or third-party Linux tools) in addition to Microsoft Azure Storage Explorer.
When referencing 'CMDLETs & APIS', clarify that Azure CLI commands and REST APIs are equally valid and provide sample usage.
Ensure that all example workflows and instructions are presented in a platform-neutral way, or explicitly include both Windows and Linux variants where differences exist.
Review all tool recommendations to ensure Linux users are not required to use Windows-only utilities for common tasks.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily through exclusive references to Microsoft Excel for CSV report handling and troubleshooting. All instructions for importing and formatting CSV files are tailored to Excel, with no mention of Linux-compatible tools (such as LibreOffice Calc or command-line utilities). There are no examples or guidance for users on Linux or macOS platforms, and the documentation assumes the use of Windows-centric workflows and tools throughout.

Recommendations:

Include instructions for opening and formatting CSV reports using cross-platform tools such as LibreOffice Calc, Google Sheets, or command-line utilities (e.g., csvkit, awk, pandas).
Provide examples or notes for Linux and macOS users, especially in sections related to CSV handling and report downloads.
Avoid assuming that users will use Microsoft Excel by default; offer alternative workflows for non-Windows environments.
Where screenshots or step-by-step guides are provided, consider adding parallel instructions for at least one major Linux-compatible tool.
Explicitly state that the Azure portal is accessible from any modern browser on any OS, and clarify that report downloads are not limited to Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or troubleshooting notes, and the only referenced prerequisites link is to a Windows-focused article. No Linux or cross-platform parity is addressed.

Recommendations:

Clearly state whether Linux is supported or not for the self-hosted integration runtime in this context. If not, explain the limitation.
If Linux support is available or planned, provide equivalent instructions, examples, and prerequisites for Linux environments.
Where possible, avoid language that implies Windows is the only supported or primary platform unless this is a hard technical limitation.
If Windows-only support is a technical constraint, suggest workarounds or alternatives for Linux users (e.g., running the integration runtime in a Windows container or VM on Linux hosts).
Add troubleshooting notes or FAQs for users attempting to use Linux, clarifying expected behaviors and support boundaries.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows documentation links before or instead of Linux equivalents in the disk types section, and by omitting any Linux-specific commands or examples for mounting or formatting disks. While the initial link to managed disks points to a Linux page, subsequent references (especially for disk types) use Windows documentation. There are no examples of Linux CLI commands or tools (e.g., fdisk, mkfs, mount), nor is there any mention of Linux-specific patterns for disk management.

Recommendations:

Ensure that all Azure documentation links reference both Linux and Windows pages equally, or prefer Linux links when the context is Linux-heavy (as with CycleCloud).
Provide Linux command-line examples for mounting and formatting disks (e.g., using fdisk, mkfs, mount) directly in this documentation or as inline examples.
Mention Linux disk management tools and patterns alongside any references to Windows tools or documentation.
If referencing both OSes, present Linux and Windows options side by side, or clarify when instructions are OS-agnostic.
Review and update the 'Further reading' section to include direct links to Linux disk management documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias. Windows authentication is explicitly supported and documented, with an example provided, but there is no mention of Linux authentication equivalents (such as Kerberos or NTLM from a Linux host). The authentication examples and property tables list 'Windows' authentication as a primary option, but do not clarify cross-platform support or limitations. Additionally, the instructions for obtaining tenant information reference a Windows-centric UI pattern (hovering in the Azure portal), and no Linux command-line or open-source tool alternatives are mentioned. The only external tool referenced is Postman, which is cross-platform, but there are no CLI or Linux-native alternatives suggested for obtaining OAuth tokens.

Recommendations:

Clarify whether 'Windows' authentication is supported from non-Windows/self-hosted integration runtimes running on Linux, and document any limitations.
If 'Windows' authentication is only supported on Windows hosts, explicitly state this and provide alternative authentication methods for Linux users.
Include examples or references for obtaining OAuth tokens using cross-platform tools (e.g., curl, httpie, Azure CLI) in addition to Postman.
When referencing UI actions (like retrieving tenant info), provide equivalent CLI or cross-platform instructions.
If Linux-specific configuration or troubleshooting steps exist for OData connectors, include them to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear Windows bias: instructions and examples are consistently written for Windows environments, with explicit references to Windows tools (Visual Studio, CMD, Git Bash, etc.) and Windows-specific workflows. Linux and macOS alternatives are either mentioned as afterthoughts or deferred to external documentation, and there are no concrete, step-by-step Linux shell examples. Environment setup, build, and run instructions are all Windows-centric, and the use of Windows command prompts and tools is pervasive.

Recommendations:

Provide parallel Linux (and macOS) instructions alongside Windows steps, including shell commands (bash) for cloning, building, and running samples.
List Linux prerequisites (e.g., gcc, make, cmake, mono/dotnet, openjdk, python3, pip, etc.) explicitly in the prerequisites section, not just as a link to external documentation.
For each programming language, include Linux-specific build and run commands (e.g., using make/gcc for C, dotnet on Linux, npm/node, python3, mvn/java) and clarify any differences in environment variable syntax (export vs set).
When referencing tools like Visual Studio, also mention and provide instructions for Linux alternatives (e.g., gcc/g++, VS Code, CLion, etc.).
Avoid phrases like 'on your Windows-based machine' unless the instructions are truly Windows-only; otherwise, use neutral language or provide both OS options.
Include screenshots or terminal output from Linux environments where possible, not just Windows.
If certain steps are only possible on Windows, clearly state this and provide workarounds or alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing login examples using Windows-style DOMAIN\username formats, and referencing Windows authentication patterns. There are no explicit Linux or OpenLDAP examples, and Linux-specific authentication patterns are only briefly mentioned in the context of Entra ID and SSH keys, with no equivalent detail or step-by-step guidance for Linux environments.

Recommendations:

Add explicit Linux/OpenLDAP configuration examples, including sample settings and login formats (e.g., uid=username,ou=users,dc=example,dc=com).
Provide Linux-centric authentication scenarios and troubleshooting tips, such as integration with PAM or sssd.
Balance the order of presentation by introducing LDAP (and Linux authentication) before or alongside Active Directory.
Include screenshots or configuration walkthroughs for Linux environments, not just Active Directory.
Clarify that both Windows and Linux authentication patterns are supported, and provide parity in documentation depth for each.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., diawp.exe.config) and configuration steps (disabling FIPS mode on the VM) without providing equivalent instructions for Linux environments. There are no Linux-specific troubleshooting steps or examples, and the language assumes a Windows context for the self-hosted integration runtime.

Recommendations:

Provide equivalent instructions for disabling FIPS mode or handling MD5/FIPS issues on Linux-based self-hosted integration runtime installations.
Mention Linux configuration files or paths where relevant, alongside Windows examples.
Explicitly state whether the troubleshooting steps apply to both Windows and Linux, or provide separate sections/examples for each platform.
Include notes or links to Linux-specific documentation for common troubleshooting scenarios.

Create pull request

Bias Types:

⚠️ missing_windows_example

⚠️ linux_first

⚠️ linux_tools

Summary:

The documentation provides detailed Linux-specific examples (including a Bash script and references to Linux file paths and tools), while Windows is only mentioned in passing with no equivalent example or detailed instructions. Linux tools and patterns are described first and in greater detail, and Windows support is described as limited (Python scripts only), but without practical guidance or examples.

Recommendations:

Add a Windows-specific HealthCheck script example (e.g., in Python), showing placement and execution on Windows VMs.
Include Windows file paths and instructions alongside Linux ones when describing where to place scripts and how to configure HealthCheck.
Clarify any differences in behavior or configuration between Linux and Windows, and provide parity in documentation structure and detail.
Where Linux tools or commands are referenced (e.g., Bash, /proc/uptime), provide Windows equivalents or note their absence.
Consider presenting both Linux and Windows instructions/examples side-by-side to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation provides both Linux and Windows script examples, but Windows paths and script types are consistently mentioned alongside or before Linux equivalents. Windows-specific details (e.g., C:\cycle\jetpack\scripts, .bat scripts) are given equal prominence, and there is an implicit assumption of Windows familiarity (e.g., referencing .bat files, Windows paths) without offering Linux-specific guidance or troubleshooting. No Linux-specific tools or patterns are highlighted, and there are no Linux-first examples.

Recommendations:

Provide Linux-first examples or alternate between Linux and Windows in examples and explanations.
Include Linux-specific troubleshooting tips or notes, such as permissions for .sh scripts or SELinux considerations.
Highlight Linux tools or commands (e.g., using chmod to ensure scripts are executable) where appropriate.
Where both platforms are mentioned, consider leading with Linux examples if the primary audience is likely to use Linux.
Add a section summarizing differences or best practices for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell command examples and referencing Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux or cross-platform command-line tools (such as Azure CLI or Bash). The only automation walkthrough is for Azure PowerShell, and no mention is made of how to perform equivalent tasks on Linux or macOS systems.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax and Linux/macOS file paths (e.g., ~/ADF).
Include a section or note on cross-platform support, clarifying that all operations can be performed from Linux, macOS, or Windows.
When referencing file paths, provide both Windows (C:\ADF) and Linux/macOS (~/ADF) variants.
Consider providing sample scripts in both PowerShell and Bash where automation is discussed.
Explicitly mention that Azure Data Factory and Synapse pipelines can be managed from any OS, and link to cross-platform tooling documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for creating linked services, referencing it before cross-platform or Linux-native options, and omitting explicit Linux CLI or scripting examples. There is no mention of Azure CLI, Bash, or Linux-specific workflows, and the quickstart/tutorial links prioritize .NET and PowerShell, both of which are traditionally Windows-centric.

Recommendations:

Add examples and quickstart links for Azure CLI and Bash scripts to create linked services, ensuring Linux users have clear, first-class guidance.
Reorder tool/SDK lists so that cross-platform options (Azure CLI, REST API, portal) appear before or alongside PowerShell and .NET.
Explicitly mention that PowerShell Core is cross-platform if referencing PowerShell, or clarify which instructions are Windows-only.
Include sample commands for creating linked services using Azure CLI and Bash, not just PowerShell or .NET.
Ensure that all tool references and tutorials are balanced between Windows and Linux environments, and avoid implying Windows is the default or preferred platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in several ways: authentication options and examples prioritize Windows (Kerberos/Windows authentication) and Windows-specific tools (Ksetup, netdom), with command-line examples and configuration steps focused on Windows environments. Linux equivalents or instructions are either missing or only briefly mentioned, and Windows terminology is used as the default throughout.

Recommendations:

Provide equivalent Linux-based setup instructions for Kerberos authentication, including commands for joining a Linux host to a Kerberos realm and configuring krb5.conf.
Include Linux shell command examples (e.g., kinit, klist, editing /etc/krb5.conf) alongside or before Windows command examples.
Clarify that 'Windows authentication' refers to Kerberos authentication and explain how it maps to Linux/Unix environments.
Add explicit guidance for configuring the self-hosted integration runtime on Linux hosts, if supported.
Balance the order of presentation so that Linux/Unix approaches are described before or alongside Windows approaches, rather than after.
Reference Linux-native tools and patterns (such as MIT Kerberos utilities) wherever Windows tools (Ksetup, netdom) are mentioned.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing BizTalk Server and SQL Server Integration Services (SSIS)—both Windows-centric technologies—without mentioning Linux or cross-platform alternatives. Migration scenarios and integration examples focus exclusively on moving from these Windows tools to Azure services, with no discussion of Linux-based integration platforms or data tools. No Linux-specific examples, tools, or migration paths are provided.

Recommendations:

Include references to Linux-based integration platforms (e.g., Apache Camel, Talend, MuleSoft) and discuss migration or integration strategies for users coming from those environments.
Mention cross-platform data integration tools and how they can be lifted and shifted or integrated with Azure Data Factory.
Provide examples or case studies for users migrating from Linux or open-source middleware to Azure Integration Services.
Balance the discussion of Windows tools (BizTalk, SSIS) with Linux/open-source equivalents to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 (a Windows-specific HPC solution) as notable features, while Linux equivalents or details are only briefly mentioned (e.g., Ubuntu 22 support for Slurm) and not highlighted equally. There are no Linux-specific tools or distributions mentioned with the same prominence, and no Linux command-line or usage examples are provided.

Recommendations:

Highlight Linux support with equal prominence as Windows (e.g., mention supported Linux distributions in the same section as Windows Server).
If mentioning Windows-specific HPC tools (like HPC Pack), also mention Linux alternatives (e.g., OpenHPC, Slurm) and their support status.
Provide examples or links for both Windows and Linux where relevant (e.g., installation instructions, supported OS lists).
Ensure that new features or resolved issues affecting Linux are described with the same detail as those for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Azure DevOps, PowerShell, and Visual Studio/NUnit, with little to no mention of Linux or cross-platform alternatives. Examples and recommendations for CI/CD, automated testing, and scripting focus on Windows tools and environments, while Linux-native or cross-platform approaches are omitted.

Recommendations:

Include Linux and cross-platform examples for CI/CD pipelines, such as using GitHub Actions, Azure CLI in Bash, or other popular CI/CD tools (e.g., Jenkins, GitLab CI) that are commonly used on Linux.
Provide sample scripts and automation steps using Bash and Azure CLI, not just PowerShell.
Mention and demonstrate cross-platform testing frameworks (e.g., pytest for Python, Mocha for Node.js) alongside NUnit/Visual Studio.
Clarify that Azure CLI and Data Factory tools are available on Linux/macOS and provide installation or usage notes for those platforms.
When referencing tools like PowerShell or Visual Studio, also reference their Linux/macOS equivalents or alternatives.
Ensure screenshots and UI walkthroughs do not assume a Windows environment exclusively.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell, SSMS (SQL Server Management Studio), and Windows-centric tooling and workflows. There are no examples or instructions for Linux users, such as using Azure CLI, cross-platform SQL tools, or alternative scripting environments. The documentation assumes the use of Windows-based tools for key operations, and does not provide parity for Linux or cross-platform users.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell instructions, ensuring cross-platform compatibility.
Offer examples using cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd) alongside SSMS.
Explicitly mention when steps can be performed from Linux/macOS, and provide guidance for those environments.
Avoid assuming the use of Windows-only tools; where SSMS is referenced, suggest Azure Data Studio or other cross-platform alternatives.
Add notes or callouts for Linux users, especially for scripting, orchestration, and database management steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell and .NET as primary tooling options for creating datasets, both in the main text and in the quickstart links. There is no mention of Linux-native tools, Bash, or cross-platform CLI examples. PowerShell is referenced before REST API or other platform-neutral options, and there are no Linux-specific instructions or parity in example tooling.

Recommendations:

Add examples and quickstart links for using Azure CLI (az), which is cross-platform and commonly used on Linux.
Include Bash shell scripting examples alongside PowerShell, especially for automation scenarios.
Explicitly mention that REST API and Azure Resource Manager templates are platform-agnostic and suitable for Linux users.
Reorder tooling references so that cross-platform tools (Azure CLI, REST API) are listed before Windows-specific tools (PowerShell, .NET).
Consider adding a section or note for Linux/macOS users, highlighting supported tools and any differences in experience.
Ensure that screenshots and UI instructions do not assume a Windows environment unless necessary.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on SQL Server and T-SQL (Transact-SQL) queries, which are primarily associated with Windows environments. There are no examples or troubleshooting steps for Linux-based SQL sources (such as SQL Server on Linux, PostgreSQL, or MySQL), nor is there mention of command-line tools or shell environments outside of Windows-centric tools. The guidance assumes a Windows/SQL Server context, omitting Linux-native workflows or tools.

Recommendations:

Include examples for Linux-based SQL sources, such as SQL Server on Linux, PostgreSQL, or MySQL, where CDC is supported.
Provide equivalent shell (bash) commands or scripts for Linux users, especially for database management and troubleshooting.
Mention and link to Linux-compatible tools (e.g., sqlcmd for Linux, Azure CLI) alongside or before Windows-specific tools.
Clarify whether the instructions apply equally to SQL Server on Linux, and note any differences in behavior or prerequisites.
Add troubleshooting steps or notes for common Linux-specific issues (e.g., permissions, service management, environment variables).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a command-line example only for Azure PowerShell (a Windows-centric tool), with no equivalent example for Linux users (such as Azure CLI, Bash, or cross-platform scripting). The only automation example is PowerShell, and there is no mention of Linux-native or cross-platform alternatives, which may make Linux users feel unsupported or excluded.

Recommendations:

Add Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation guidance.
Where possible, provide Bash or REST API examples for automation to ensure parity for Linux and macOS users.
Reorder or supplement the documentation so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools.
Include a note clarifying that the UI steps are platform-agnostic, but that command-line automation can be performed from any OS with the appropriate tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits a moderate Windows bias. While most of the content is platform-neutral (focused on Azure Data Factory and Microsoft 365), there are notable areas where Windows/PowerShell tools and patterns are referenced or prioritized. Specifically, certificate conversion is demonstrated using PowerShell, and PowerShell is listed as a primary SDK/tool for pipeline creation. There are no explicit Linux or cross-platform CLI examples, and Windows-centric tools are mentioned before or instead of Linux alternatives.

Recommendations:

Provide Linux and cross-platform alternatives for certificate conversion (e.g., using OpenSSL commands) alongside PowerShell instructions.
Include Azure CLI and/or Bash script examples for common tasks such as pipeline creation and certificate management.
When listing tools or SDKs, avoid listing Windows-specific tools (like PowerShell) first or exclusively; instead, present Azure CLI, REST API, and SDKs in a neutral order.
Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI, REST API, or other cross-platform tools.
Add example commands and scripts for Linux environments where relevant, especially for tasks like certificate manipulation and automation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows authentication, Windows-style usernames (domain\username), and Windows-specific tools and patterns (such as SQL Server Management Studio and Windows Firewall). Troubleshooting steps and configuration instructions are written solely for Windows environments, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, such as using sqlcmd, Azure Data Studio, or Linux firewall configuration.

Recommendations:

Add Linux authentication guidance, including examples for Kerberos or SQL authentication from Linux hosts.
Provide alternative instructions for connecting to Amazon RDS for SQL Server from Linux, such as using sqlcmd or Azure Data Studio.
Include Linux-based troubleshooting steps, such as configuring iptables or firewalld for port access.
Clarify that the instructions for tools like SQL Server Management Studio and Windows Firewall are Windows-specific, and suggest cross-platform or Linux-native alternatives.
When giving username examples, include both Windows (domain\username) and Linux/SQL (username@hostname or just username) formats.
Explicitly state any platform limitations or requirements, and provide links to relevant Linux documentation where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows support and tools (such as the self-hosted integration runtime's Windows prerequisites) without mentioning Linux equivalents or support. There are no Linux-specific instructions, examples, or clarifications about cross-platform compatibility for the integration runtime or connector. All example configurations and property descriptions are generic or reference Azure services, but the only explicit OS reference is to Windows, and there is no guidance for Linux users.

Recommendations:

Explicitly state whether the self-hosted integration runtime and Hive connector support Linux hosts, and provide a link to Linux prerequisites if available.
If Linux is supported, add Linux-specific setup instructions or notes alongside Windows instructions.
Include examples or troubleshooting tips relevant to Linux environments (e.g., certificate paths, permissions, service management).
Avoid phrasing that implies Windows is the only supported or primary platform unless that is actually the case; if so, clarify this limitation up front.
Where referencing OS-specific features (such as the system trust store), clarify how this applies on both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Microsoft Access ODBC driver, which is only available on Windows. All example connection strings use Windows-style file paths (e.g., C:\mydatabase.accdb), and there is no mention of Linux or cross-platform alternatives for running the Integration Runtime or accessing Microsoft Access data. The prerequisites and setup instructions implicitly assume a Windows environment, and there are no examples or guidance for Linux users.

Recommendations:

Explicitly state that the Microsoft Access ODBC driver is only available on Windows, and clarify platform limitations in the prerequisites.
If possible, provide guidance or workarounds for Linux users, such as using third-party ODBC drivers (e.g., MDBTools) or running the Integration Runtime in a Windows container/VM on Linux.
Include example connection strings and file paths for both Windows and Linux (if supported), or clearly indicate that only Windows is supported.
Add a section addressing cross-platform considerations and alternatives for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias, primarily through the explicit mention and prioritization of PowerShell and Windows-centric tools in the 'Monitor' and 'Related content' sections. PowerShell is listed as a primary automation/monitoring method, and the quickstart links highlight PowerShell before cross-platform options like Python or REST. There are no explicit Linux CLI or Bash examples, nor is there mention of Linux-native tooling or parity in automation/monitoring approaches.

Recommendations:

Add explicit examples and quickstart links for Bash/CLI usage, especially for common Linux environments.
When listing automation or monitoring tools (e.g., PowerShell, API), ensure cross-platform options (such as Azure CLI, Bash scripts) are mentioned alongside or before Windows-specific tools.
In the 'Monitor' section, include examples using Azure CLI and REST API, not just PowerShell.
Review the order of quickstart links to avoid implying PowerShell is the primary or preferred method; consider listing cross-platform options first or grouping by platform.
Where PowerShell is referenced, add a note or link to equivalent Azure CLI documentation for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows authentication as a primary supported authentication method, omitting any mention of Linux authentication or setup. There are no Linux-specific instructions, examples, or troubleshooting steps. The documentation assumes the use of Windows-based Integration Runtime and does not address Linux environments or tools.

Recommendations:

Add explicit instructions for setting up the Integration Runtime and Sybase data provider on Linux hosts, if supported.
Include Linux authentication options (such as Kerberos or other supported mechanisms) and clarify if only Windows authentication is supported.
Provide Linux command-line examples for installation and configuration, alongside or before Windows examples.
Mention any limitations or differences when using Linux as the Integration Runtime host.
Clarify in the prerequisites and configuration sections whether Linux is supported or not, and provide parity guidance if it is.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, without mentioning or providing Linux alternatives or examples. The related content also highlights Windows authentication and PowerShell usage, further reinforcing the Windows-centric approach.

Recommendations:

Explicitly state the platform requirements and limitations for the mentioned tools (e.g., SSDT, SSMS, dtutil, AzureDTExec), clarifying if they are Windows-only.
If Linux support is unavailable for these tools, provide a clear note to inform users and suggest any possible workarounds (such as using Docker containers or remote Windows VMs).
If any cross-platform or Linux-compatible deployment options exist (e.g., Azure CLI, REST APIs, or third-party tools), include examples and instructions for those.
Balance the order of presentation by mentioning any available cross-platform methods before or alongside Windows-specific tools.
Add a section addressing Linux/macOS users, outlining their options and any current limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias, particularly in the FIPS troubleshooting section, where only Windows file paths and configuration steps are provided (e.g., referencing 'C:\Program Files\Microsoft Integration Runtime' and editing 'diawp.exe.config'). There are no equivalent instructions or examples for Linux environments, nor is there any mention of Linux-based Self-hosted Integration Runtime scenarios. The troubleshooting steps and environment assumptions are Windows-centric, with no parity for Linux users.

Recommendations:

Include equivalent troubleshooting instructions for Linux-based Self-hosted Integration Runtime environments, if supported.
When referencing file paths or configuration files, provide both Windows and Linux examples (e.g., 'C:\Program Files\...' and '/opt/...').
Explicitly state if certain features or troubleshooting steps are only applicable to Windows, and provide guidance or alternatives for Linux users.
Review all environment-specific instructions to ensure Linux users are not excluded from critical troubleshooting guidance.
Add notes or links to Linux-specific documentation where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell commands for generating a Shared Access Signature (SAS) token, with no equivalent CLI, Bash, or cross-platform examples. The exclusive mention of PowerShell and the absence of Linux/macOS command-line alternatives may hinder users on non-Windows platforms. Additionally, the documentation refers to Windows tooling first and does not acknowledge or provide parity for Linux users.

Recommendations:

Add Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script examples or reference REST API calls for SAS generation to ensure Linux parity.
When mentioning PowerShell, always provide an equivalent Azure CLI or REST API example immediately after or before, and clarify that PowerShell is Windows-centric.
Audit the documentation for any other places where Windows tools or patterns are mentioned exclusively, and ensure Linux/macOS alternatives are present.
Explicitly state that all features and steps are supported on both Windows and Linux, or note any exceptions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell (Windows-specific) command for troubleshooting SAP connector connectivity, with no equivalent Linux or cross-platform example. The use of Test-NetConnection is exclusive to Windows, and there is no mention of Linux tools or commands, nor any guidance for non-Windows environments.

Recommendations:

Add equivalent Linux troubleshooting commands, such as using 'nc' (netcat) or 'telnet' to test connectivity to the SAP server port.
Explicitly mention that the provided PowerShell command is for Windows, and provide parallel instructions for Linux and macOS environments.
Where possible, use cross-platform tools or provide guidance for both Windows and Linux users equally.
Review related content and troubleshooting steps to ensure Linux users are not excluded from guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias, particularly in the 'Legacy model' section, where SMB path syntax (\\server\share) and user ID formats (AZURE\username) are presented in a Windows-centric way. There are no explicit Linux or cross-platform examples for mounting or accessing Azure Files, nor is there mention of Linux-specific tools or syntax. The documentation assumes familiarity with Windows conventions and omits guidance for Linux users.

Recommendations:

Add Linux-specific examples for mounting Azure Files, such as using the 'mount.cifs' command and appropriate credential formats.
When showing SMB paths, provide both Windows (\\server\share) and Linux (/mnt/point with //server/share) syntax.
Clarify that the 'userid' and 'host' formats differ between Windows and Linux clients, and provide examples for each.
Mention Linux tools (e.g., cifs-utils) alongside Windows tools when discussing legacy SMB access.
Review all authentication and connection examples to ensure they are platform-agnostic or provide parallel Linux instructions where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically identifying impacted objects, with no mention of Linux-compatible alternatives such as Bash, Azure CLI, or Python scripts. This creates a bias toward Windows users and tools, potentially excluding Linux or cross-platform users from easily following the guidance.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux and macOS users.
Mention cross-platform scripting options such as Python with the Azure SDK.
Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide instructions if so.
Include notes or links to documentation for running automation tasks on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by instructing users to use 'curl' in a 'Command Prompt window' without mentioning Linux or macOS terminals. Additionally, it recommends 'Fiddler', a Windows-only tool, for SSL troubleshooting, with no Linux or cross-platform alternatives suggested. No Linux- or macOS-specific instructions or examples are provided.

Recommendations:

When referencing 'curl', use neutral language such as 'terminal' or 'command line' instead of 'Command Prompt window', and clarify that 'curl' is available on Windows, Linux, and macOS.
Provide example 'curl' commands that work on both Windows and Linux/macOS, noting any syntax differences if relevant.
When recommending tools like 'Fiddler', also mention cross-platform alternatives such as 'mitmproxy' or 'Charles Proxy' for Linux/macOS users.
Explicitly state that the troubleshooting steps apply to all major operating systems, and, where appropriate, provide OS-specific guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a bias toward Windows environments by exclusively referencing SQL Server Management Studio (SSMS) for running SQL scripts, without mentioning cross-platform or Linux-compatible alternatives. There are no examples or instructions for Linux users, and the workflow assumes access to Windows tools. The documentation also refers to SQL Server-specific features (e.g., OPENJSON) without discussing parity or alternatives for other database engines commonly used on Linux.

Recommendations:

Include instructions for running the generated SQL scripts using cross-platform tools such as Azure Data Studio, sqlcmd (available on Linux), or psql for PostgreSQL if supported.
Mention that SSMS is a Windows-only tool and provide Linux/macOS alternatives for connecting to SQL databases.
Add examples or notes for users who may be using Linux-based environments, including how to execute the scripts from the command line.
Clarify database engine requirements and discuss any limitations or differences for users running non-SQL Server databases, especially on Linux.
Review all screenshots and UI references to ensure they are not Windows-specific, or provide parallel guidance for Linux/macOS users where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as SQL Server Management Studio and Windows Firewall), linking to Windows-centric configuration guides, and omitting Linux or cross-platform alternatives. There are no PowerShell scripts or command-line examples, but the troubleshooting steps and references assume a Windows environment and do not provide parity for Linux users.

Recommendations:

When referencing tools like SQL Server Management Studio (SSMS), also mention cross-platform alternatives such as Azure Data Studio.
For firewall configuration, provide guidance for both Windows Firewall and common Linux firewalls (e.g., iptables, firewalld, ufw), or link to cross-platform documentation.
Where examples reference Windows-specific paths or tools, include equivalent instructions for Linux environments.
Explicitly state when a troubleshooting step is platform-agnostic, or provide separate sections/examples for Windows and Linux where necessary.
Audit all external documentation links to ensure Linux users are not excluded and that cross-platform resources are available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Notepad, C:\ paths), omitting Linux/macOS equivalents, and using Windows directory conventions. There are no examples or instructions for Linux or cross-platform users for tasks like file creation or directory navigation.

Recommendations:

Include equivalent instructions for Linux/macOS users, such as using nano, vim, or gedit as text editors.
Provide file path examples using both Windows (C:\...) and Unix-style (/home/user/...) conventions.
Mention cross-platform tools or approaches (e.g., VS Code, Azure CLI) where possible instead of only Windows-specific tools.
Explicitly state that the steps apply to all platforms, or provide platform-specific sections as needed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by referencing the SAP HANA ODBC driver specifically as 'SAP HANA CLIENT for Windows' in the prerequisites, without mentioning Linux or cross-platform alternatives. No Linux installation guidance or examples are provided for setting up the ODBC driver or Integration Runtime, and authentication examples prioritize Windows authentication. There are no Linux-specific instructions or parity in tool references.

Recommendations:

Explicitly mention and provide download links for both Windows and Linux versions of the SAP HANA ODBC client in the prerequisites.
Add instructions or references for installing the SAP HANA ODBC driver on Linux-based Integration Runtime hosts.
Include Linux-specific examples or notes where authentication or configuration differs (e.g., Kerberos or other Linux authentication methods).
Avoid using 'Windows authentication' as the default or primary example; instead, present both Windows and Linux authentication options equally, or clarify OS applicability.
Where screenshots or UI steps are shown, note any OS-specific differences or limitations.
Review all tool and command references to ensure Linux equivalents are mentioned and demonstrated where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Command Prompt), providing only Windows-centric troubleshooting commands (nslookup in Command Prompt), and omitting Linux/macOS equivalents. Browser troubleshooting steps are platform-agnostic, but when it comes to command-line diagnostics, only Windows is addressed, leaving out users on Linux or macOS.

Recommendations:

Include Linux/macOS equivalents for command-line troubleshooting steps. For example, provide Terminal commands for nslookup or dig.
When referencing 'Command Prompt', also mention 'Terminal' for Linux/macOS users.
Add screenshots or example outputs from Linux/macOS terminals where relevant.
Use inclusive language such as 'Open Command Prompt (Windows) or Terminal (Linux/macOS)' to address all users.
Ensure that all troubleshooting steps are cross-platform or provide platform-specific tabs/sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides troubleshooting steps using the SharePoint Online Management Shell, a Windows-only tool, and PowerShell commands. There are no equivalent instructions or examples for Linux or cross-platform environments. The guide assumes the user is on Windows and does not mention alternatives for Linux or macOS users.

Recommendations:

Provide equivalent instructions for Linux and macOS users, such as using cross-platform PowerShell Core or Azure CLI where possible.
Mention whether the SharePoint Online Management Shell can be run on PowerShell Core (which is cross-platform) or if there are REST API alternatives.
If no direct Linux alternative exists, explicitly state this and suggest possible workarounds (e.g., using a Windows VM, Docker container, or REST API calls).
List both Windows and Linux/macOS steps side by side where applicable to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates bias toward Windows by exclusively recommending Microsoft Excel (2016/2013) and Power BI—both Windows-centric tools—for extracting the index of a table in an HTML page. There are no Linux or cross-platform alternatives mentioned, nor are command-line or open-source approaches provided. The documentation assumes access to Windows environments and Microsoft Office products, which may not be available to Linux users.

Recommendations:

Provide alternative instructions using cross-platform or Linux-native tools, such as Python scripts (with pandas and BeautifulSoup), curl, or command-line HTML parsers to extract table indices.
Include examples or step-by-step guides for Linux users, ensuring parity with the Windows/Excel workflow.
Mention open-source tools (e.g., LibreOffice Calc, csvkit, or web scraping utilities) that can accomplish the same task on non-Windows platforms.
Reorder or supplement the documentation so that Windows-specific tools are not the only or primary method described for key tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by highlighting Windows-specific updates (such as the Windows VHD base image and cumulative Windows/.NET updates) without mentioning equivalent Linux images, updates, or considerations. There are no examples or notes for Linux users, and the focus on Windows tools and updates appears before any cross-platform or Linux-specific information.

Recommendations:

Include information about Linux-based images or support, if available, alongside Windows updates.
Mention whether similar updates (e.g., kernel, security, or framework updates) are applied to Linux-based deployments.
Add explicit notes or sections for Linux users, clarifying any differences in behavior, requirements, or known issues.
Ensure that future release notes provide parity in coverage for both Windows and Linux environments, including examples and troubleshooting steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing REST API examples exclusively in PowerShell, referencing PowerShell and Windows-specific tools throughout, and omitting equivalent Linux/bash/cURL examples. PowerShell is used as the default scripting language for REST API and dedicated PowerShell sections, with no mention of cross-platform alternatives. This may hinder Linux users or those working in non-Windows environments.

Recommendations:

Add REST API examples using bash and cURL to complement the existing PowerShell scripts, ensuring Linux and macOS users have clear guidance.
Explicitly mention that PowerShell examples are Windows-centric and provide equivalent bash/cURL commands where possible.
Reorganize sections so that cross-platform or OS-neutral examples (e.g., Python, REST API with cURL) are presented before or alongside Windows-specific tools.
Where PowerShell is used, note if it can be run cross-platform (e.g., PowerShell Core), or clarify any Windows-only dependencies.
Include a table or note summarizing which tools and SDKs are available and supported on different operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows environments by referencing PowerShell for backup configuration, mentioning Windows authentication for on-premises data stores, and using Windows-centric patterns (UNC paths, SSMS, and File System linked services). There are no Linux-specific instructions or examples, and alternative Linux tools or workflows are not discussed.

Recommendations:

Provide equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts) alongside or instead of PowerShell instructions, especially for tasks like configuring backup storage redundancy.
Clarify whether features such as file system access, SSMS management, and UNC paths are supported or have alternatives on Linux-based environments.
Include guidance for connecting to on-premises data stores from non-Windows environments, such as using Kerberos or other authentication methods available on Linux.
Mention and link to cross-platform tools (e.g., Azure Data Studio) where SSMS is referenced.
Explicitly state platform requirements or limitations where Windows-specific tools or patterns are necessary, and suggest Linux-compatible alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides detailed instructions and code samples exclusively using Azure PowerShell cmdlets, which are most commonly used and natively supported on Windows. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The focus on PowerShell and absence of Linux-oriented tools or examples indicates a Windows-centric bias.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation or usage notes if PowerShell is required.
Where possible, provide Bash script examples or REST API calls to demonstrate reconfiguration and deletion tasks in a platform-agnostic way.
Ensure that any references to tools or scripting environments include both Windows and Linux options, or clarify cross-platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell scripts and Azure PowerShell tasks for all CI/CD automation examples, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All sample code, instructions, and YAML pipeline tasks are PowerShell-centric, and there are no Linux-native or cross-platform examples provided. The documentation assumes the use of PowerShell Core but does not address Linux environments or provide parity for non-Windows users.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment automation, ensuring Linux users have clear guidance.
Explicitly mention that PowerShell Core is cross-platform and provide instructions for running scripts on Linux agents.
Include YAML pipeline examples that use AzureCLI@2 or Bash tasks alongside AzurePowerShell tasks.
Reference or link to documentation on setting up Linux build agents and running deployment scripts in non-Windows environments.
Clarify any limitations or differences when running the scripts on Linux versus Windows, and offer troubleshooting tips for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias: it is explicitly written for a Windows environment, with Windows-specific tools (Visual Studio, Windows command prompt, Git Bash for Windows, winpty), and Windows instructions always presented first or exclusively. Linux and macOS are only referenced as alternatives, often via links to external SDK documentation, and not given equal, inline treatment. In many sections, only Windows command-line examples are shown, or the Linux equivalents are relegated to secondary tabs or notes. Some steps (e.g., opening Visual Studio, using Windows command prompt) have no direct Linux equivalent described, and the overall workflow assumes a Windows user.

Recommendations:

Provide Linux (and macOS) instructions and examples inline, not just as links or secondary tabs. For each step, show both Windows and Linux commands side-by-side.
Avoid assuming the use of Windows-specific tools (e.g., Visual Studio) as the default; instead, offer cross-platform alternatives (e.g., GCC/Clang, VS Code, or JetBrains IDEs).
Where Git Bash or winpty is used for Windows, clarify the native Linux equivalent (plain Bash, no winpty needed).
For environment setup, give equal detail for Linux (package managers, build tools, etc.), not just refer to SDK docs.
In all code and command examples, present both Windows and Linux syntax, and avoid Windows-only command prompt instructions.
Consider restructuring the quickstart to have parallel sections for Windows and Linux/macOS, or use clear pivots/tabs for each OS, ensuring parity in depth and clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows machines and VMs for installing the Data Factory self-hosted integration runtime, both on-premises and in Azure. There are no examples or guidance for Linux-based installations, nor is there mention of Linux as a supported platform for the integration runtime. This may lead users to believe that only Windows environments are supported or recommended, despite the prevalence of Linux in Hadoop ecosystems.

Recommendations:

Explicitly mention that the Data Factory self-hosted integration runtime can be installed on Linux (if supported), and provide equivalent instructions and recommendations for Linux environments.
Include architecture diagrams and configuration examples that use Linux VMs or machines, especially given the commonality of Linux in Hadoop clusters.
When discussing VM sizing and scaling, provide example configurations for both Windows and Linux VMs.
Clarify authentication and credential management steps for Linux-based deployments, including any differences in setup or best practices.
If Linux is not supported for the integration runtime, clearly state this limitation early in the documentation to set expectations for users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples and device interactions are shown using PowerShell, with explicit references to Windows paths (e.g., C:\Users\<username>\.kube), and no Linux or cross-platform equivalents are provided. The instructions for connecting to the device, managing Kubernetes config files, and running kubectl commands are all shown from a Windows environment. There is no mention of how to perform these steps from a Linux or macOS client, nor are there any bash or shell examples. Windows-specific tools and patterns (such as PowerShell cmdlets and Windows directory structures) are used exclusively throughout the guide.

Recommendations:

Provide equivalent Linux/macOS instructions and examples for all steps, including connecting to the device, managing Kubernetes config files, and running kubectl commands.
Include bash or shell command examples alongside PowerShell examples, especially for kubectl and file operations.
Mention Linux and macOS as supported client platforms where applicable, and link to any prerequisites or setup guides for those systems.
Show Linux file paths (e.g., ~/.kube/config) in addition to Windows paths when instructing users where to save configuration files.
If device management cmdlets are only available on Windows, explicitly state this limitation and, if possible, suggest alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides instructions and examples using Azure PowerShell, a Windows-centric tool, with no mention of Linux alternatives or cross-platform CLI options. All provisioning steps and code samples assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.

Recommendations:

Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Clearly indicate whether the Azure-SSIS IR can be provisioned and managed from non-Windows environments, and provide guidance if there are limitations.
Include bash or shell script examples alongside PowerShell, or at least reference the Azure CLI documentation for Linux/macOS users.
Review references to Windows-specific authentication or configuration steps and provide Linux/macOS alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by referencing Notepad and Windows file paths (e.g., C:\ADFv2QuickStartPSH), omitting Linux/macOS equivalents for file creation and editing. All command-line cleanup instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. There are no Linux/macOS-specific instructions or screenshots, and Windows-centric patterns are presented as the default.

Recommendations:

Provide parallel instructions for Linux/macOS users, such as using nano, vim, or other common editors, and using POSIX file paths (e.g., /home/user/ADFv2QuickStart).
Include Azure CLI commands (az group delete, az datafactory delete) alongside PowerShell for resource cleanup, and clarify which shell each command is for.
Avoid referencing Windows-specific tools (like Notepad) exclusively; suggest cross-platform editors or provide alternatives.
Add notes or callouts for platform-specific differences, and ensure screenshots or instructions are not Windows-only.
Consider a section or tabbed examples for Windows, Linux, and macOS users to improve accessibility and parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively providing PowerShell commands for monitoring integration runtimes, referencing Windows-specific tools and patterns (such as the self-hosted IR being described as running on 'on-premises Windows machine'), and omitting any Linux or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or REST API alternatives, and all code snippets and operational guidance assume a Windows/PowerShell environment.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for monitoring integration runtimes.
Include REST API sample requests and responses for monitoring tasks, to support automation and cross-platform use.
Clarify whether self-hosted integration runtime can be installed and monitored on Linux, and if so, provide relevant instructions and examples.
When referencing tools or commands, present cross-platform options (e.g., Azure CLI, REST API) before or alongside PowerShell.
Avoid language that assumes the self-hosted IR is always on Windows unless this is a technical limitation; if so, state it explicitly.
Add Bash shell examples where appropriate, especially for scripting and automation scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All examples, tools, and scripts assume a Windows OS (e.g., .cmd, .bat, .ps1 files, use of msiexec.exe, cmdkey, odbcconf.exe, and PowerShell). There are no Linux or cross-platform examples, and all instructions and sample scripts are Windows-specific. The documentation does not mention or provide alternatives for Linux-based environments, nor does it clarify that Azure-SSIS IR is Windows-only, which may confuse users seeking Linux support.

Recommendations:

Explicitly state early in the documentation that Azure-SSIS IR is a Windows-based service, and Linux customizations are not supported. This will set clear expectations for cross-platform users.
If any Linux or cross-platform support is planned or available (e.g., for other Azure Data Factory runtimes), provide links or references to those options.
Where possible, clarify that all script and tool references (e.g., .cmd, .ps1, msiexec.exe) are Windows-specific, and suggest alternatives or workarounds for users on non-Windows platforms (such as preparing scripts on Linux and uploading via cross-platform tools).
Add a section or FAQ addressing the lack of Linux support, and direct users to appropriate Azure documentation for Linux-based data integration scenarios.
If any steps (such as uploading files to Azure Storage) can be performed with cross-platform tools (e.g., Azure CLI, azcopy), provide those examples alongside Windows-specific ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools and workflows (e.g., Event Viewer, Windows Performance Counters, Log Analytics agent for Windows), and by omitting any mention of Linux equivalents or instructions for configuring log analytics collection on Linux-based SHIR hosts. All examples and screenshots are Windows-specific, and there is no guidance for Linux users.

Recommendations:

Add a dedicated section for configuring log analytics collection on Linux-based SHIR hosts, including references to the Log Analytics agent for Linux and relevant documentation.
Provide Linux-specific examples for selecting and forwarding logs (e.g., syslog, journald) and performance counters (e.g., using collectd or telegraf).
Include screenshots or command-line instructions relevant to Linux environments.
Mention both Windows and Linux options in all relevant sections, or clarify if SHIR is only supported on Windows (if that is the case).
Ensure parity in troubleshooting and verification steps for both operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Azure PowerShell and Windows-specific tools (SSMS, SSDT, SQL Server Agent) for monitoring and querying SSIS operations, without providing equivalent Linux or cross-platform alternatives. There are no examples or instructions for Linux users, and the only command-line example mentioned is Azure PowerShell, which is primarily associated with Windows environments.

Recommendations:

Include Azure CLI examples alongside or instead of Azure PowerShell for checking SSIS IR operational status, as Azure CLI is cross-platform.
Mention and provide examples for querying logs using cross-platform tools such as Azure Data Studio, which runs on Linux, macOS, and Windows.
Clarify whether SSIS monitoring and management tasks can be performed from Linux environments, and if so, provide relevant instructions.
When referencing tools like SSMS or SSDT, note their platform limitations and suggest alternatives or workarounds for non-Windows users.
Ensure that all monitoring and alerting workflows described can be executed from Linux or cross-platform environments, or clearly state any limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by referencing Azure PowerShell as the primary or only CLI-based method for provisioning and managing Azure-SSIS IR. There are no examples or mentions of equivalent Linux-friendly tools such as Azure CLI or Bash scripting. The related content and step-by-step instructions focus on Azure PowerShell and ADF UI, both of which are more familiar to Windows users, with no parity for Linux command-line environments.

Recommendations:

Include equivalent Azure CLI (az) commands alongside or in place of Azure PowerShell examples for all provisioning and management tasks.
Add explicit instructions or links for performing tasks using Bash or cross-platform scripting environments.
Ensure that all references to command-line tooling mention both Azure PowerShell and Azure CLI, with examples for each.
Review related content and tutorials to provide Linux-friendly workflows, not just Windows-centric ones.
Clarify in the documentation that both Windows and Linux users are supported, and provide troubleshooting tips relevant to both environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first bias by listing Windows operating systems and tools before Linux equivalents, providing a detailed list of required Windows software (including PowerShell, .NET Framework, and BitLocker) while only briefly mentioning Linux requirements. Windows-specific tools and patterns (e.g., PowerShell, BitLocker) are highlighted, and there is no parity in the depth of explanation or tool listing for Linux environments.

Recommendations:

List Linux operating systems and requirements before or alongside Windows, not after.
Provide equal detail for Linux client requirements, including versions and installation instructions for required tools.
Include Linux command-line examples or references where Windows tools (like PowerShell) are mentioned.
Mention Linux-native disk encryption and management tools with the same prominence as BitLocker.
Ensure parity in troubleshooting and validation steps for both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific security tools (Windows Defender, Device Guard, BitLocker), providing instructions for connecting via PowerShell, and omitting equivalent Linux-based tools or management methods. There are no examples or guidance for Linux-based hypervisors, security tooling, or remote management, which may leave Linux users without clear instructions.

Recommendations:

Include Linux equivalents for security features, such as recommending and providing instructions for using dm-crypt/LUKS for disk encryption instead of only BitLocker.
Add examples and instructions for connecting to and managing the Data Box Gateway device from Linux systems, such as using SSH or cross-platform management tools, not just PowerShell.
Mention and provide guidance for Linux-based hypervisors (e.g., KVM, VMware on Linux) alongside Hyper-V, and link to relevant documentation.
Reference Linux-native malware protection solutions (e.g., ClamAV, Sophos) where appropriate, or clarify if only Windows is supported.
Ensure that all security and management steps are presented in a cross-platform manner, or clearly state any platform limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, dtexec, DMA) and workflows, without mentioning Linux-compatible alternatives or providing Linux-specific guidance. All examples and tool references assume a Windows environment, and there is no discussion of how to perform these tasks on Linux or cross-platform environments.

Recommendations:

Include information about running SSIS-related command-line utilities (such as dtexec, dtutil) on Linux, if supported, or clarify their platform limitations.
Mention and provide guidance for any cross-platform or Linux-compatible tools for SSIS package management and migration, or explicitly state if such tools are not available.
If SSMS/SSDT are required and only available on Windows, suggest alternatives for Linux users (such as Azure Data Studio, if applicable) or provide remote access strategies.
Add a section or notes addressing Linux users, outlining what is and isn't possible from non-Windows environments and any workarounds.
Ensure that any scripts or automation examples are provided in a cross-platform manner (e.g., PowerShell and Bash, where possible).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows environments. All instructions, examples, and tooling are based on PowerShell, with explicit references to Windows-only features (e.g., PowerShell 5.1, Windows Update/WSUS, Windows file paths). There are no Linux or cross-platform instructions, nor any mention of running the tool or equivalent checks on Linux or macOS systems.

Recommendations:

Provide explicit information about Linux and macOS support: State whether the Azure Stack Network Readiness Checker can be run on non-Windows platforms, and if not, clarify this limitation early in the documentation.
If the tool is Windows-only, suggest alternative methods or scripts for Linux users to perform similar network readiness checks (e.g., using curl, dig, traceroute, or custom scripts).
If cross-platform PowerShell (PowerShell Core/7+) is supported, include installation and usage instructions for Linux and macOS, with corresponding examples.
Include Linux/macOS file path examples for log and report locations, if applicable.
Rephrase sections that assume a Windows environment (e.g., references to C:\Users\..., Windows Update, etc.) to be more inclusive or to provide Linux/macOS alternatives where possible.
Add a note in the prerequisites section about platform compatibility and any required dependencies for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows PowerShell as the primary local management interface, referencing Windows-specific tools (such as WSUS for updates), and omitting Linux or cross-platform CLI examples for device management. There are no examples or mentions of using Linux shells or tools for local management, nor is there guidance for Linux users on connecting or managing the device.

Recommendations:

Include equivalent Linux/Bash shell instructions and examples for local device management, such as using SSH or cross-platform Azure CLI.
Mention cross-platform tools (e.g., Azure CLI, kubectl) before or alongside Windows PowerShell, and clarify which management interfaces are supported on Linux.
Provide update instructions for Linux users, including how to manually apply updates without WSUS or Windows tools.
Explicitly state whether the local web UI and other management interfaces are accessible from Linux clients, and provide any necessary prerequisites or troubleshooting steps.
Ensure all feature tables and instructions present both Windows and Linux options where applicable, or clearly note if a feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-centric bias by referencing Windows authentication, Windows environment variables, registry entries, UNC paths, and Windows-specific tools (e.g., cmdkey) without providing equivalent Linux/Unix guidance or examples. There is a lack of parity in addressing Linux scenarios, and the documentation assumes a Windows environment for SSIS workloads and migration steps.

Recommendations:

Provide equivalent Linux/Unix examples or guidance where Windows-specific features (e.g., environment variables, authentication, registry, UNC paths) are discussed.
Clarify whether SSIS Integration Runtime supports Linux-based execution, and if not, state this explicitly.
If Linux is not supported, briefly explain why and provide alternative approaches for cross-platform compatibility.
For sections referencing Windows tools (e.g., cmdkey), mention if there are Linux equivalents or note their absence.
When discussing file paths, include examples using both Windows (UNC/absolute) and Linux (POSIX) path formats.
For environment variables, explain how to set and use them in both Windows and Linux contexts, if applicable.
Where registry usage is mentioned, suggest Linux alternatives (such as config files) or clarify limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows mild Windows bias. In the descriptions of HDInsight activities (Hive, Pig, MapReduce, Streaming), clusters are described as 'Windows/Linux-based', with Windows mentioned first. The Stored Procedure activity only references SQL Server and Azure SQL, which are traditionally Windows-centric, with no mention of Linux-based alternatives. The custom activity section focuses on .NET, a technology historically associated with Windows, and does not provide examples for Linux-native scripting or environments. There are no explicit Linux shell or bash examples, and the only tutorial linked is for Spark with PowerShell, a Windows-first tool.

Recommendations:

When listing supported platforms (e.g., 'Windows/Linux-based HDInsight cluster'), alternate the order or use 'Linux/Windows-based' to avoid implicit prioritization.
Include explicit examples or references for Linux-native tools and scripting (e.g., bash, Python scripts) alongside .NET and PowerShell.
For the Stored Procedure activity, mention support for open-source or Linux-based databases if applicable, or clarify platform support.
Provide at least one tutorial or example using Linux-native tools (e.g., bash, Python CLI) instead of only PowerShell.
In the custom activity section, highlight support for running custom scripts in Linux environments and provide sample code for both Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. The installation and configuration steps assume a Windows environment (e.g., references to Local Security Policy, NT SERVICE accounts, and C:\ProgramData paths). Windows authentication and tools like Visual Studio/SSDT are discussed without Linux equivalents or alternatives. There is no guidance for Linux users, and no mention of whether the self-hosted IR or SSIS proxy features are supported or unsupported on Linux.

Recommendations:

Clearly state platform support at the beginning of the documentation (e.g., if only Windows is supported, make this explicit).
If Linux is supported, provide equivalent Linux/Bash command-line instructions alongside PowerShell examples.
Mention Linux-specific considerations for installing drivers, setting up service accounts, and configuring authentication.
Provide file path examples and log locations for both Windows and Linux, if applicable.
If features are Windows-only, suggest alternatives or workarounds for Linux users, or link to relevant documentation.
Consider including a table or section comparing Windows and Linux setup steps, highlighting any differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias, particularly in the Azure PowerShell section. The PowerShell instructions explicitly reference installing Azure PowerShell on Windows and use Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json). The prerequisites for PowerShell only mention Windows installation, omitting cross-platform guidance. While the Azure CLI and SDK sections are platform-neutral, the PowerShell section is both Windows-centric and appears before the CLI section, which is more cross-platform friendly. There are no explicit Linux or macOS examples or notes for PowerShell usage.

Recommendations:

In the Azure PowerShell section, clarify that Azure PowerShell is cross-platform and provide installation instructions for Linux and macOS, not just Windows.
Use platform-neutral file paths in examples (e.g., ./MyTrigger.json or mention both Windows and Linux/macOS path formats).
Add a note that PowerShell Core is available on Linux and macOS, and provide links to installation guides for those platforms.
Consider presenting Azure CLI examples before PowerShell, as CLI is more commonly used on Linux/macOS.
Wherever file paths or shell commands are shown, provide both Windows and Linux/macOS variants, or use variables/placeholders.
Explicitly state that all SDKs and CLI tools are cross-platform, and provide any platform-specific caveats if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally avoids explicit Windows bias in most troubleshooting steps, focusing on cross-platform tools like Azure CLI and kubectl. However, in the section on capturing network packet traces for Layered Network Management, the Windows host instructions (using Wireshark) are presented before the Linux host instructions (using tcpdump), and Wireshark (a GUI Windows tool) is mentioned as the default for opening trace files. There are no PowerShell-specific examples, but the ordering and tool choices show a mild Windows-first and Windows-tools bias. In other sections, Linux-native commands (kubectl, bash) are used, but there are no explicit Linux-first or Linux-only examples, and some steps (e.g., rebooting the host) are generic.

Recommendations:

Present Linux and Windows instructions in parallel tabs or sections, or alternate which platform appears first to avoid Windows-first ordering.
When suggesting tools for packet capture, mention both Wireshark and tcpdump for both platforms, and clarify that Wireshark is available on Linux as well.
Where possible, provide CLI-based alternatives for Windows users (e.g., using tshark or tcpdump on Windows), not just GUI tools.
Ensure that all examples and troubleshooting steps are clearly marked as applicable to both Windows and Linux, or provide explicit instructions for both.
Consider including a table or matrix summarizing which tools/commands are available on which platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation displays a Windows bias by referencing PowerShell cmdlets as the primary method for troubleshooting, mentioning Windows-specific tools (like SSMS), and omitting Linux equivalents or examples. There are no instructions or troubleshooting steps tailored for Linux users, nor are cross-platform command-line tools or patterns (such as Azure CLI or SQLCMD) presented. The guidance assumes a Windows environment for local testing and management.

Recommendations:

Include Azure CLI examples alongside or instead of PowerShell cmdlets for cross-platform compatibility.
Mention and provide examples for using SQLCMD or Azure Data Studio, which are available on Linux, instead of only referencing SSMS.
Explicitly state whether the troubleshooting steps are applicable to both Windows and Linux environments, and provide Linux-specific guidance where necessary.
When recommending local testing of scripts, clarify how to do so on Linux (e.g., using bash scripts or compatible shells) and note any differences.
Ensure that all references to tools or commands are accompanied by their cross-platform alternatives, and avoid assuming the user is on Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page shows a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer), Windows command syntax, and PowerShell interfaces, with little or no mention of Linux equivalents. In some cases, only Windows-centric instructions are provided, and Linux alternatives are missing or less prominent.

Recommendations:

For file copy operations, provide Linux equivalents (e.g., rsync, cp) alongside Windows tools like robocopy and Explorer.
When giving mount command examples, include both Windows and Linux syntax (e.g., show 'mount -o nolock ...' for Linux, and 'net use' or Windows mount for Windows).
For PowerShell-specific instructions (e.g., connecting to the device), add equivalent bash/ssh or Linux-native instructions.
Ensure all command-line examples are cross-platform or provide parallel examples for both Windows and Linux users.
Mention Linux tools and patterns (e.g., bash, Linux file managers) wherever Windows tools are referenced.
Review all steps and workarounds to ensure Linux users are not left without guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by referencing Notepad for file creation, omitting Linux/macOS equivalents, and not providing cross-platform command-line instructions for file or data manipulation. The only desktop tool mentioned for interacting with Azure Blob Storage is Azure Storage Explorer, which is cross-platform, but the initial file creation and manipulation steps assume a Windows environment. No Linux shell or macOS Terminal examples are provided, and there is no mention of Linux-native editors or commands.

Recommendations:

When instructing users to create a text file, provide alternative commands for Linux/macOS (e.g., using echo/cat or nano/vi).
Explicitly mention that Azure Storage Explorer is available on Windows, macOS, and Linux.
Where file movement or manipulation is required, offer cross-platform command-line examples (e.g., cp/mv for Linux/macOS, copy/move for Windows).
Avoid referencing Windows-specific tools (like Notepad) without also listing Linux/macOS equivalents.
Consider adding a table or callout box with equivalent steps for Windows, Linux, and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by only referencing Windows Server (IIS) as the web server deployed on the virtual machines, with no mention of Linux alternatives. The verification step specifically instructs users to expect the default IIS Windows Server web page, and the template configures IIS, which is Windows-specific. There are no examples or guidance for deploying or verifying with a Linux-based web server (e.g., Apache, Nginx), nor are there any Linux command-line or deployment instructions.

Recommendations:

Include parallel instructions and screenshots for deploying and verifying a Linux-based web server (such as Apache or Nginx) in addition to IIS.
Modify the ARM template or provide an alternative template that configures a Linux VM with a popular web server.
In the verification section, show what users should expect if they deployed a Linux VM (e.g., default Apache/Nginx page).
Explicitly mention that the tutorial can be followed with either Windows or Linux VMs, and provide parameter options or guidance for both.
Avoid assuming Windows as the default platform; present both Windows and Linux options equally throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux-compatible alternatives or cross-platform workflows. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows authentication and file system conventions. Windows tools are mentioned first and exclusively throughout.

Recommendations:

Explicitly state the platform requirements for tools like SSDT, SSMS, dtutil, and AzureDTExec, clarifying that they are Windows-only and suggesting workarounds for Linux users (e.g., using Windows containers, remote desktop, or Azure-hosted VMs).
Provide guidance or links for Linux users on how to interact with Azure Data Factory and Azure-SSIS IR, such as using the Azure Portal, REST APIs, or Azure CLI (where applicable).
If possible, mention any cross-platform or web-based alternatives for package deployment and management, or clarify the lack thereof.
Add a section or notes highlighting the absence of native Linux support for SSIS tooling, and suggest best practices for Linux-based development environments (e.g., using cloud-hosted Windows environments for SSIS tasks).
Ensure that any command-line examples or references are clearly marked as Windows-specific, and consider providing equivalent steps (if available) for Linux or macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by requiring Azure PowerShell, referencing Windows file paths (e.g., C:\Windows\System32\drivers\etc), and providing instructions only for Windows environments (such as editing the Windows hosts file). There are no examples or guidance for performing equivalent steps on Linux-based VMs, nor are cross-platform tools or commands (like Azure CLI or Linux file paths) mentioned. This could hinder users working in Linux environments or those preferring non-Windows tooling.

Recommendations:

Provide equivalent instructions for Linux-based VMs, such as how to edit /etc/hosts for DNS resolution.
Include Azure CLI commands as alternatives to Azure PowerShell for all steps, or clarify which steps are cross-platform.
Explicitly mention that the self-hosted integration runtime can be installed on both Windows and Linux VMs, and provide installation steps for both.
When referencing file paths or system modifications (like editing hosts files), show both Windows and Linux syntax.
Review all screenshots and UI references to ensure they are not exclusively Windows-centric, or add Linux equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), providing setup instructions that assume a Windows environment, and omitting any Linux-specific guidance or alternatives. There are no examples or instructions for Linux users, such as using sqlcmd or Azure Storage CLI tools on Linux, nor is there mention of Linux-compatible SQL Server management or integration runtime installation steps.

Recommendations:

Add parallel instructions for Linux users, such as using sqlcmd or Azure Data Studio to create databases and tables.
Include guidance for installing and configuring the self-hosted integration runtime on Linux (if supported), or clearly state platform limitations.
Provide examples of how to interact with Azure Blob Storage using cross-platform tools like Azure CLI or AzCopy, not just via the Azure Portal.
Explicitly mention any platform-specific requirements or limitations early in the prerequisites section.
Ensure screenshots and step-by-step instructions are inclusive of both Windows and Linux environments where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page exhibits several signs of Windows bias. Windows tools and workflows (e.g., robocopy, Explorer, RDP, PowerShell commands) are mentioned or exemplified, sometimes without Linux equivalents or with Windows examples given first. Some workarounds and instructions are specific to Windows environments, and Linux alternatives are either missing or less detailed. This can make it harder for Linux users to follow or apply the documentation effectively.

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux commands (e.g., rsync, cp, bash commands) and examples.
When giving example commands for mounting NFS shares, include both Windows and Linux syntax, and present them side by side or in parallel sections.
If referencing Windows-specific troubleshooting (e.g., using RDP, Get-Process), add Linux-based troubleshooting steps (e.g., SSH, ps, systemctl) where applicable.
Avoid listing Windows tools or workflows before Linux equivalents; alternate or group them by platform.
Review all sections for implicit assumptions of a Windows environment and clarify when instructions are platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows Server Failover Clustering concepts, terminology, and tools, with no mention of Linux-based clustering, commands, or alternative witness mechanisms. All examples, requirements, and explanations assume a Windows environment, and there are no Linux equivalents or cross-platform considerations provided.

Recommendations:

Include a section clarifying whether Linux-based clustering is supported or not on Azure Stack Edge, and if so, provide equivalent guidance for Linux clusters.
If Linux is not supported, explicitly state this early in the documentation to set user expectations.
If Linux is supported, add Linux-specific examples for setting up cluster witnesses (e.g., using corosync/pacemaker, NFS shares, or other Linux-native mechanisms).
Mention Linux-compatible file sharing protocols (such as NFS) alongside SMB, or clarify SMB support on Linux if relevant.
Avoid using Windows-specific terminology (such as 'Windows Server Failover Clustering') exclusively; instead, use more generic clustering terms where possible, or provide cross-references to Linux equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by requiring Azure PowerShell for setup, referencing only PowerShell installation instructions, and omitting any Linux or cross-platform CLI alternatives for uploading files or managing resources. No Linux shell or Azure CLI examples are provided, and the prerequisite section assumes a Windows environment by default.

Recommendations:

Provide equivalent instructions for Linux and macOS users, such as using the Azure CLI (az) for resource management and file uploads.
Include examples for uploading files to Azure Blob Storage using cross-platform tools like Azure CLI or AzCopy, not just PowerShell.
In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, and link to installation guides for both.
Where scripting or command-line actions are required, present both Windows (PowerShell) and Linux/macOS (bash) command examples side by side.
Explicitly state that the tutorial is cross-platform and highlight any steps that are platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first bias, particularly in the sections on enabling ICMP and connecting to lab VMs. Only Windows 11 is used as the example VM image, and instructions for enabling ICMP are provided exclusively for Windows via PowerShell. There are no equivalent Linux examples or commands for enabling ICMP or connecting to Linux VMs (e.g., via SSH). The documentation also references RDP before SSH and does not provide Linux command-line examples for tasks like firewall configuration or connectivity testing.

Recommendations:

Provide parallel Linux examples throughout, especially for enabling ICMP (e.g., using ufw or firewalld commands).
When showing how to connect to VMs, include both RDP (for Windows) and SSH (for Linux) instructions, with equal prominence.
When suggesting VM images, mention both Windows and popular Linux distributions (e.g., Ubuntu, CentOS) and show how to select them.
In sections that use PowerShell, add equivalent bash or shell commands for Linux users.
Ensure screenshots and walkthroughs are balanced between Windows and Linux scenarios, or clarify when steps are OS-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by specifying Windows as the guest OS in the VM creation process, using Windows-specific cmdlets (e.g., Set-HcsIpAddress), and omitting any mention of Linux-based management or examples. All command-line examples and instructions assume a Windows environment, with no guidance for Linux users or alternative tooling.

Recommendations:

Provide explicit instructions for provisioning the Data Box Gateway VM with a Linux guest OS, if supported, or clarify if only Windows is supported.
Include Linux shell command equivalents for network configuration (e.g., using ip, ifconfig, or nmcli) alongside the PowerShell cmdlets.
Mention any Linux-compatible management tools or interfaces, or clarify limitations if only Windows tools are supported.
Add a note early in the documentation about OS compatibility and management expectations for users on non-Windows platforms.
Where possible, provide screenshots or walkthroughs using Linux-based VMware management tools (such as the vSphere Web Client accessed from Linux) to ensure parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments, with all examples and instructions provided exclusively for Windows and PowerShell. There are no Linux or cross-platform command examples, and Windows-specific tools and file paths are referenced throughout. The installation and usage of kubectl are shown only for Windows, and even basic steps like editing the hosts file are described only for Windows systems.

Recommendations:

Provide equivalent Linux (and macOS, if possible) instructions and examples for all steps, including connecting to the device, managing namespaces/users, and installing kubectl.
Include Linux shell command examples (e.g., bash, curl, cp, nano/vim for editing hosts file) alongside PowerShell commands.
Reference Linux file paths (e.g., ~/.kube/config) and explain how to save and use the config file on Linux systems.
Mention Linux package managers (e.g., apt, yum, snap) for installing kubectl, and provide download links for Linux binaries.
Clarify any platform-specific requirements or limitations, and ensure that all supported client OSes are treated equally in the documentation.
Add screenshots or terminal outputs from Linux environments where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools and defaults (such as 'time.windows.com' as the default NTP server and NTLM authentication for proxies), and by omitting Linux-specific instructions or examples. There are no Linux or cross-platform command-line examples, and the documentation assumes familiarity with Windows environments and tools.

Recommendations:

Provide Linux-specific guidance or examples where relevant (e.g., how to access the web UI from a Linux environment, or how to configure network settings using Linux tools).
Mention alternative, platform-neutral NTP servers (such as pool.ntp.org) alongside 'time.windows.com'.
Explain proxy authentication options that are common in Linux environments (e.g., Basic, Digest) or clarify NTLM limitations.
Ensure that screenshots and terminology are not exclusively Windows-centric and clarify that the instructions are applicable regardless of the underlying OS.
Explicitly state that the device can be managed from any modern browser on any OS, and provide troubleshooting tips for Linux users if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples and device management instructions are provided exclusively using PowerShell cmdlets, with no equivalent Linux shell or cross-platform CLI examples. The documentation refers to Windows-centric tools and patterns (such as PowerShell, Windows cmdlets, and references to Windows documentation like NUMA support), and Linux is only mentioned in passing (e.g., 'Windows or Linux VHD'), with no Linux-specific operational guidance or examples. There are no instructions for performing these tasks from a Linux environment or using cross-platform tools like Azure CLI or SSH.

Recommendations:

Provide equivalent Linux shell (bash) commands for all PowerShell cmdlet examples, or clarify if device management is only possible via PowerShell.
Include instructions for connecting to the device and managing NUMA/vCPU reservations from a Linux or cross-platform environment (e.g., via SSH, Azure CLI, or REST API if available).
If PowerShell is required, explicitly state this requirement and provide guidance for Linux users (e.g., using PowerShell Core on Linux, or alternatives).
Reference both Windows and Linux documentation for NUMA concepts and VM image preparation.
Ensure that any prerequisites or workflows that are platform-specific are clearly marked, and provide parity in documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Windows PowerShell and Windows-specific cmdlets for configuring MetalLB via BGP on Azure Stack Edge. All examples, instructions, and sample outputs are based on the Windows environment, with no mention of Linux equivalents or cross-platform alternatives. There is no guidance for users who may want to perform similar tasks from a Linux or non-Windows environment.

Recommendations:

Provide equivalent Linux-based instructions, such as using SSH and standard Linux networking tools (e.g., ip, nmcli, or BGP daemons like FRR or Bird) for configuring BGP sessions if supported.
Include examples using cross-platform PowerShell Core (pwsh) and clarify any differences in command usage or prerequisites.
Explicitly state if configuration is only possible via Windows PowerShell, and if so, explain why and suggest workarounds for Linux users (e.g., using a Windows jump host or container).
Add a section comparing Windows and Linux approaches, or at least acknowledge the lack of Linux support and provide links to relevant Linux-native MetalLB/BGP configuration guides.
Where possible, use platform-neutral language and tools, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page displays a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell cmdlets like Get-VM and Start-VM, RDP, waappagent.exe), and instructions often assume a Windows environment or provide Windows examples first. In some cases, Linux alternatives are missing or only mentioned in passing, leading to incomplete guidance for Linux users.

Recommendations:

For every Windows-specific tool or example (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, SSH, systemctl, ps, etc.).
When showing command-line examples, include both Windows and Linux syntax side by side.
Avoid referencing only Windows utilities (e.g., sqlcmd, robocopy) without mentioning how to perform the same tasks on Linux.
In sections discussing connecting to VMs or devices (e.g., RDP), mention SSH and Linux-native tools as alternatives.
For PowerShell-heavy troubleshooting steps, provide bash or shell equivalents for Linux-managed devices.
Review all examples and ensure Linux parity, especially in troubleshooting and workaround sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing SMB (the Windows file sharing protocol) as the default, referencing Windows tools like File Explorer for permission management, and omitting concrete Linux/NFS client usage examples. While NFS is mentioned as an option for Linux clients, there are no step-by-step instructions or Linux-specific guidance, and Windows-centric patterns are presented first and in more detail.

Recommendations:

Provide parallel Linux/NFS client usage examples, such as how to mount and access NFS shares from a Linux machine.
Include Linux command-line examples (e.g., using mount, showmount, or nfsstat) alongside or after Windows/SMB instructions.
When discussing permissions, explain how to manage NFS share permissions from a Linux perspective, not just via File Explorer.
Balance the order of presentation: if SMB is described first, ensure NFS/Linux is given equal detail and visibility.
Reference Linux tools and workflows where appropriate, not just Windows tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting the Windows onboarding process and PowerShell script editing steps in detail before the Ubuntu/Linux process. The Windows section includes explicit instructions for modifying and running a PowerShell script, while the Ubuntu section focuses mainly on repository configuration and omits a step-by-step onboarding example. Windows-specific tools (e.g., OnboardingScript.ps1, azcmagent.exe) are highlighted, and there is a lack of parity in Linux onboarding instructions.

Recommendations:

Provide a detailed, step-by-step onboarding example for Ubuntu/Linux hosts, including the exact commands to run (e.g., azcmagent connect) and any required parameters or flags, mirroring the detail given for Windows.
Include Linux shell script examples or command-line equivalents alongside PowerShell/Windows examples.
Present Windows and Linux onboarding instructions in parallel sections or tables to emphasize equal support.
Reference both Windows and Linux tools/utilities equally, and avoid assuming the use of Windows-specific scripts or editors.
Clarify any differences in onboarding steps between platforms, and ensure that Linux users are not required to infer steps from Windows instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing on PowerShell-based management, referencing Windows clients and tools first, and omitting Linux-specific instructions or examples. All command-line examples use PowerShell syntax, and there is no mention of Linux shell equivalents or guidance for Linux users. The documentation assumes or prefers a Windows environment for device management and configuration.

Recommendations:

Provide equivalent Linux/bash command-line instructions for all PowerShell examples, especially for device management and configuration tasks.
Explicitly mention support for Linux clients where applicable, and clarify any OS-specific requirements or limitations.
Include screenshots or walkthroughs using Linux terminals or Azure CLI in bash, not just PowerShell or Windows UI.
When referencing tools (e.g., PowerShell interface), also describe how to access and use these tools from Linux systems.
Avoid assuming the user is on Windows; structure prerequisites and instructions to be OS-agnostic or to present Linux and Windows options equally.
Add a section or callouts for Linux users, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Hyper-V and a YouTube link for adding a hard drive to a Hyper-V virtual machine) without mentioning Linux or cross-platform equivalents. There are no Linux examples or references to Linux hypervisors (like KVM or VMware), and instructions for expanding device capacity are tailored to Windows environments.

Recommendations:

Include instructions and examples for adding data disks and expanding capacity using popular Linux hypervisors (e.g., KVM, VMware) alongside Hyper-V.
Provide links to documentation or tutorials for Linux-based virtual machine management.
Ensure that all platform-specific instructions are clearly labeled and that Linux alternatives are presented with equal prominence.
Where possible, use neutral, cross-platform language and tools, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. Most configuration and management instructions reference the PowerShell interface, Az cmdlets, and Windows-specific tools or workflows. Examples and workarounds often assume a Windows environment (e.g., use of robocopy, Explorer, and Windows command syntax), with little or no mention of Linux equivalents. Linux tools, shell commands, or alternative workflows are rarely provided, and when present, are not given equal prominence or detail.

Recommendations:

Provide equivalent Linux/bash command examples alongside PowerShell commands for all device management and configuration tasks.
Mention Linux-native tools (e.g., rsync, cp, scp) wherever Windows tools like robocopy or Explorer are referenced.
Document how to connect to and manage the device from Linux systems, including remote management, VLAN configuration, and Az module usage.
Ensure that instructions for features like AzCopy, SQL connectivity, and NFS mounting include both Windows and Linux command-line examples.
Where PowerShell cmdlets are referenced, indicate if and how the same functionality can be achieved from a Linux shell or via cross-platform tools.
Review all troubleshooting and workaround sections to ensure Linux users are not excluded or left to infer their own solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows some Windows bias, particularly in the ordering and detail of prerequisites. Windows instructions (Visual Studio, CMake, Mosquitto installer) are listed first and in more detail, while Linux instructions are more concise. The repository cloning example uses Windows command prompt syntax (git clone in a code block labeled 'cmd'), and there is no explicit Linux shell example for this step. The build output locations are described for both platforms, but Windows is mentioned second. There are no PowerShell-specific commands, but the overall structure and tool recommendations (Visual Studio, CMake installer) lean toward Windows development patterns.

Recommendations:

Alternate the order of Windows and Linux instructions or present them side-by-side to avoid always listing Windows first.
Provide equivalent detail for Linux prerequisites (e.g., mention recommended IDEs or editors, clarify where binaries are located after build).
Include Linux shell examples for repository cloning and other steps, not just Windows command prompt.
Where possible, use cross-platform instructions (e.g., 'git clone' in a generic shell block) or show both Windows and Linux command syntax.
Mention Linux-native tools or workflows (such as using VS Code, Makefiles, or GCC directly) alongside Windows tools like Visual Studio.
Ensure parity in troubleshooting tips and notes for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for Azure resource provider registration, with no equivalent instructions for Linux users (such as Azure CLI or Bash examples). The use of PowerShell as the only command-line interface and the absence of Linux-specific guidance or parity in examples may hinder Linux administrators.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell examples, especially for resource provider registration and listing.
Include explicit instructions or notes for Linux/macOS users, clarifying that all operations can be performed via Azure CLI or Bash.
Where screenshots or UI references are made, ensure that any OS-specific nuances (such as browser or terminal differences) are acknowledged.
Consider a 'Platform parity' section or callouts to reassure users that all features are available regardless of OS, and link to cross-platform tools documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing explicit instructions and links for using Azure PowerShell to set blob tiers, while not mentioning or providing equivalent CLI or Linux-native examples. The only scripting example given is for Azure PowerShell, and there is no reference to Azure CLI, Bash, or Linux-specific workflows. The documentation also refers to SMB protocol (commonly associated with Windows environments) before NFS, and does not clarify Linux compatibility or provide Linux-centric guidance.

Recommendations:

Add Azure CLI and Bash script examples for setting blob tiers and managing lifecycle policies, alongside or before PowerShell examples.
Explicitly mention Linux compatibility for Data Box Gateway, including supported protocols and any required configuration steps for Linux clients.
Provide NFS-based examples and workflows, especially for data transfer and share creation, to cater to Linux/Unix users.
Ensure that all instructions referencing PowerShell have equivalent CLI or REST API alternatives documented.
Review the order of protocol/tool mentions (e.g., mention NFS before SMB where appropriate, or present both equally) to avoid implicit prioritization of Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by repeatedly instructing users to use a Windows command prompt and the Windows Subsystem for Linux (WSL) to execute Linux commands. There are no native Linux or macOS instructions, and the workflow assumes a Windows environment. This excludes users on Linux or macOS from following the steps directly, and Windows-specific tools and patterns are mentioned without Linux equivalents.

Recommendations:

Provide native Linux and macOS instructions alongside Windows instructions, especially for command-line steps.
Avoid assuming the use of WSL; instead, show how to run commands directly in a Linux or macOS terminal.
When referencing command prompts, clarify which OS is being used and offer alternatives for other platforms.
If using online tools or Azure Portal steps, ensure that any OS-specific instructions are clearly marked and alternatives are provided.
Consider restructuring the step order so that no platform is prioritized over another (e.g., 'On Windows, do X. On Linux/macOS, do Y.').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows evidence of Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer), commands (PowerShell, Get-Process), and workflows (RDP, Windows services) without providing Linux equivalents. In some cases, Windows paths and mounting syntax are shown, while Linux alternatives are omitted or only briefly mentioned. Linux tools and workflows are underrepresented or missing in scenarios where cross-platform parity would be expected.

Recommendations:

For every Windows-specific example (e.g., robocopy, Explorer, PowerShell commands), provide equivalent Linux commands (e.g., rsync, cp, systemctl, ps).
When showing mount commands, include both Windows (e.g., net use, Explorer) and Linux (e.g., mount -t nfs) syntax.
For troubleshooting steps involving Windows services or processes, add parallel instructions for Linux (e.g., using systemctl, service, or kill commands).
When referencing tools like sqlcmd, clarify installation and usage for both Windows and Linux clients.
Avoid referencing Windows tools or patterns (e.g., RDP, Windows Guest Agent) as the only option; mention SSH or Linux agents where applicable.
Review all examples and ensure Linux parity, especially in sections involving file operations, mounting, and VM/cluster management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias by consistently listing Windows before Linux in recommendations and descriptions, and by mentioning Windows-specific tools (e.g., Schannel, Win32 sockets) alongside but before or more prominently than Linux equivalents (e.g., OpenSSL, Berkeley sockets). There are no code examples for either platform, but references to Windows tools and APIs are more explicit. Linux is mentioned, but often after Windows, and there are no Linux-specific tools or patterns highlighted.

Recommendations:

List Linux and Windows in a neutral or alternating order (e.g., 'Linux and Windows' or 'Windows and Linux') to avoid implicit prioritization.
When mentioning platform-specific tools (e.g., Schannel for Windows, OpenSSL for Linux), ensure both are described with equal detail and prominence.
Include explicit Linux examples or references to Linux-specific tools (e.g., GnuTLS, epoll) where appropriate.
Highlight Linux as a first-class supported platform, not just as an alternative to Windows.
If mentioning Windows-specific APIs (e.g., Win32 sockets), also mention and describe Linux equivalents (e.g., POSIX/Berkeley sockets) in the same context.
Consider adding sample commands or code snippets for both Windows and Linux environments where relevant.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (such as Azure PowerShell and Windows Server Update Services) and includes screenshots showing certificate downloads in Windows File Explorer. There are no explicit Linux or cross-platform command-line examples for certificate creation, management, or installation, and no mention of Linux tools or workflows. The guidance for certificate conversion and installation is generic, but the only concrete tool references are Windows-centric. The order of tool recommendations (PowerShell before Readiness Checker) also subtly prioritizes Windows environments.

Recommendations:

Provide explicit Linux and macOS examples for certificate creation, management, and installation (e.g., using OpenSSL or Linux CLI tools).
Include screenshots or instructions for downloading and handling certificates on Linux and macOS systems, not just Windows File Explorer.
Mention cross-platform tools (such as OpenSSL) alongside or before Windows-specific tools like Azure PowerShell.
Clarify that the procedures are applicable to all supported client OSes, and add notes or links to platform-specific instructions where workflows differ.
When referencing tools for certificate creation, list cross-platform options first or in parallel with Windows tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates several types of Windows bias. Windows tools and patterns (e.g., PowerShell, RDP, Windows-specific services and commands) are referenced frequently and sometimes exclusively, especially in troubleshooting and workaround steps. In several cases, only Windows command-line examples (e.g., PowerShell cmdlets, Windows paths) are provided, with no equivalent Linux commands or steps. Windows-specific terminology and tools (e.g., Explorer, robocopy, RDP, waappagent.exe) are mentioned before or instead of Linux alternatives, and Linux parity is sometimes only mentioned as an afterthought or not at all.

Recommendations:

For every Windows-specific command or tool mentioned (e.g., PowerShell cmdlets, robocopy, Explorer, RDP), provide equivalent Linux commands or tools (e.g., bash/ssh, cp/rsync, Nautilus, SSH).
When describing troubleshooting steps for Windows VMs, also include parallel steps for Linux VMs where applicable.
Avoid using Windows paths or syntax exclusively in examples (e.g., show both C:\ paths and /mnt/ paths for NFS mounts).
Mention Linux tools and workflows alongside Windows ones, and do not assume Windows as the default environment.
Where PowerShell is referenced for device management, provide bash/CLI alternatives if supported.
Review all examples and workarounds to ensure Linux users are not left without guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows environments for the SAP system (e.g., 'Sign in to the SAP Windows virtual machine'), providing only Windows-based installation paths and instructions (such as copying DLLs from 'C:\Program Files'), and mentioning only the SAP Connector for Microsoft .NET (Windows-only). There are no examples or guidance for Linux-based SAP systems or cross-platform alternatives.

Recommendations:

Include parallel instructions for configuring SAP systems running on Linux, including relevant screenshots and SAP GUI steps.
Mention and provide guidance for Linux-compatible SAP connectors (e.g., SAP Java Connector or other cross-platform options) where applicable.
When referencing file paths or installation procedures, provide both Windows and Linux equivalents.
Clarify in prerequisites or relevant sections whether the solution is limited to Windows-based SAP systems, or expand support to Linux-based SAP deployments.
If certain features (such as the .NET connector) are Windows-only, suggest Linux alternatives or note the limitation explicitly.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation shows evidence of Windows bias in several areas: Windows-specific tools and commands (e.g., robocopy, Explorer, PowerShell, RDP) are mentioned without Linux equivalents or before them; some examples and workarounds are only provided for Windows environments; and Linux alternatives or parity are often missing or underexplained. This may hinder Linux users from effectively following the guidance.

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell, RDP), provide equivalent Linux commands or tools (e.g., rsync/cp, Nautilus/Thunar, SSH, Linux shell commands).
When giving command-line examples (such as mounting NFS shares or using sqlcmd), include both Windows and Linux syntax side by side.
Avoid referencing Windows tools or patterns (e.g., 'use robocopy or Explorer') without also mentioning Linux alternatives.
If a workaround or procedure is only described for Windows (e.g., PowerShell commands, RDP), add clear, step-by-step Linux alternatives.
Review all troubleshooting and workaround sections to ensure Linux users are equally supported, especially for VM management, file operations, and connectivity.
Consider reordering examples so that neither platform is always presented first, or present both together.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific certificate providers (Microsoft RSA/Schannel Cryptographic Provider), defaulting to Windows export behaviors (3DES as default from Windows 10/Server 2016), and only providing next steps for certificate creation using Azure PowerShell cmdlets and the Azure Stack Hub Readiness Checker tool (both Windows-centric). There are no examples or guidance for Linux or cross-platform certificate management, export, or creation.

Recommendations:

Include equivalent Linux/OpenSSL commands and workflows for certificate creation, export, and management.
Mention and provide examples for Linux-compatible cryptographic providers and how to ensure compatibility with Azure Stack Edge Pro.
Clarify whether certificates generated on Linux (e.g., with OpenSSL) are supported and, if so, provide explicit instructions.
List both Windows and Linux tools in parallel when discussing certificate export, password requirements, and encryption algorithms.
Add troubleshooting steps and references for common Linux certificate management scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows (and specifically Windows Server) instructions and screenshots first and in greater detail, especially for SMB shares. Windows-specific tools and workflows (Notepad, File Explorer, net use, Windows Run dialog) are emphasized, while Linux instructions are more concise and lack equivalent visual aids or troubleshooting tips. The 'hosts' file modification is described only for Windows, and there is no mention of macOS clients or cross-platform alternatives for SMB access.

Recommendations:

Provide Linux (and optionally macOS) instructions and examples alongside Windows instructions, not after them.
Include Linux-specific screenshots (e.g., editing /etc/hosts, using Nautilus or command-line tools to access SMB shares).
Offer SMB connection instructions for Linux clients (e.g., using smbclient, mount.cifs) and not just NFS.
Balance the level of detail and troubleshooting tips between Windows and Linux sections.
Mention cross-platform tools and approaches where possible (e.g., using the same share from different OSes).
Clarify that the 'hosts' file modification applies to Linux (/etc/hosts) and provide the relevant steps.
Consider including a table summarizing steps for Windows, Linux, and macOS clients for both SMB and NFS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Windows instructions and PowerShell usage are prioritized or exclusively shown in several sections, such as the AzCopy example and output, and the steps for downloading and copying VHDs. Linux-specific instructions are present for image preparation, but parity is lacking for subsequent steps (e.g., AzCopy usage and output are only shown for Windows/PowerShell). The documentation also references Windows tools and patterns (e.g., command prompt, PowerShell) more prominently than Linux equivalents.

Recommendations:

Provide parallel Linux/bash examples for all command-line operations, especially for AzCopy usage (e.g., show azcopy commands and sample output in a Linux shell).
Include instructions for navigating to directories and running commands in Linux (e.g., using bash or sh instead of PowerShell/cmd).
When showing sample output, include both Windows (PowerShell/cmd) and Linux (bash) outputs where relevant.
Avoid using Windows paths (e.g., C:\azcopy\...) exclusively; show Linux path equivalents (e.g., ~/azcopy/...).
Ensure that Linux instructions are given equal prominence and not relegated to secondary tabs or notes.
Where possible, mention cross-platform tools and clarify that AzCopy is available for both Windows and Linux, with download links for both.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. The PowerShell examples are prominent and include references to Windows file paths (e.g., D:\testFiles\textfile.csv) and Windows-centric tooling. There is no mention of Linux-specific tools, shell environments, or file path conventions. PowerShell is presented as a primary automation method, and the PowerShell tab includes instructions for running commands locally or in Azure Cloud Shell, but does not address Bash or Linux-native scripting. The CLI examples are cross-platform, but the PowerShell content and file path examples show a Windows bias.

Recommendations:

Add explicit Bash examples alongside PowerShell, especially for automation and scripting tasks.
When referencing file paths, use cross-platform examples or provide both Windows (e.g., D:\testFiles\textfile.csv) and Linux (e.g., /home/user/testFiles/textfile.csv) path formats.
Mention that Azure CLI commands can be run in Bash on Linux/macOS, and provide guidance for those environments.
Clarify that PowerShell Core is cross-platform, but provide Bash alternatives for users who prefer native Linux tools.
Avoid referring to Windows-specific folders or drive letters without Linux equivalents.
Include links to Linux-specific quickstarts or guides where available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell (Get-AzResource) example for listing Edge resource groups but does not mention or provide equivalent CLI or Linux-native commands. The only command-line example uses Azure PowerShell, which is most commonly used on Windows, and there is no mention of Azure CLI or Bash alternatives. This results in a bias towards Windows users and leaves Linux users without clear guidance.

Recommendations:

Add Azure CLI examples (e.g., using 'az resource list') alongside PowerShell examples to ensure Linux and cross-platform parity.
Explicitly mention that Azure PowerShell can be used on Linux and macOS, or provide installation links for non-Windows platforms.
Wherever PowerShell is referenced, provide equivalent Bash or shell command examples if possible.
Review the documentation for other places where only Windows-centric tools or instructions are given and ensure Linux alternatives are included.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows (e.g., Hyper-V, YouTube video for adding a hard drive to a Hyper-V VM) without providing equivalent Linux or cross-platform instructions. There are no Linux-specific examples or mentions of Linux hypervisors (like KVM or VMware), and the guidance for expanding device capacity is tailored to Windows environments. The documentation also omits Linux command-line or UI examples for monitoring or managing the device.

Recommendations:

Provide equivalent instructions for adding data disks and expanding capacity using popular Linux hypervisors (e.g., KVM, VMware, VirtualBox).
Include Linux-specific examples or references for device monitoring and management, such as using Linux browsers or command-line tools to access the local web UI.
Replace or supplement the Hyper-V/Windows-specific YouTube video with cross-platform or Linux-focused tutorials.
Explicitly mention supported Linux distributions and tools in relevant sections, ensuring parity with Windows coverage.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as WSUS for updates), mentioning Windows-centric patterns (like referencing Microsoft Update and WSUS before any cross-platform update options), and omitting Linux-specific instructions or examples for key steps (such as configuring network settings or connecting to the device). There are no PowerShell commands, but the overall workflow assumes a Windows environment and does not provide Linux alternatives or parity.

Recommendations:

Include explicit instructions or examples for Linux and macOS users, especially for steps like configuring network adapters, connecting to the device, and managing certificates.
Mention cross-platform update mechanisms (such as using public NTP servers or Linux-compatible update solutions) alongside or before Windows-specific options like WSUS.
Provide command-line examples (e.g., using ip, nmcli, or ifconfig for network setup) for Linux and macOS, not just GUI/browser-based steps.
Clarify that the procedure is cross-platform where possible, and highlight any steps that are platform-specific.
Add troubleshooting tips for Linux/macOS environments, such as browser certificate warnings or network configuration nuances.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias. Device management and remote access are described exclusively in terms of Windows tools and patterns, such as PowerShell and BitLocker. There are no Linux command-line examples or references to Linux-compatible management methods. Security features like BitLocker and Windows Defender Application Control are mentioned without Linux equivalents or alternatives. The documentation assumes a Windows-centric environment for both administration and security, with no guidance for Linux users.

Recommendations:

Provide Linux-based management and remote access instructions, such as using SSH or Linux CLI tools, alongside PowerShell examples.
Mention and, where possible, support Linux-compatible encryption and security tools (e.g., LUKS/dm-crypt) or clarify if only BitLocker is supported.
Include examples for connecting to the device from Linux clients, such as mounting SMB/NFS shares from Linux, and managing certificates using Linux tools (e.g., OpenSSL).
Clarify any platform limitations and explicitly state if certain features are Windows-only, while suggesting workarounds or alternatives for Linux environments.
Ensure that documentation sections referencing logs, password management, and device access include Linux workflows and commands where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits some Windows bias, primarily through the exclusive mention of a PowerShell cmdlet (Set-HcsMacAddressPool) for configuring MAC addresses, with no equivalent Linux/CLI example or mention. There are no Linux shell commands or tools referenced, and the only command-line example is Windows-specific. While the document is otherwise platform-neutral in many sections, the lack of Linux parity in command-line instructions and tooling is notable.

Recommendations:

Provide equivalent Linux shell commands or instructions wherever PowerShell cmdlets are mentioned (e.g., show how to configure MAC addresses using Linux tools or REST APIs if available).
Include examples or references to cross-platform CLI tools (such as Azure CLI) when discussing device management.
Explicitly state whether certain configuration steps (like setting MAC addresses) are only possible via PowerShell, or if there are Linux alternatives.
Review all command-line and tooling references to ensure Linux administrators have clear, actionable guidance.
Consider adding a section or table summarizing management options for both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Azure PowerShell as the method for managing local storage accounts, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI or Bash). The prerequisite to configure the client via Azure PowerShell further centers Windows tooling, and there are no Linux-specific examples or alternatives provided.

Recommendations:

Include Azure CLI (cross-platform) instructions alongside or instead of Azure PowerShell, especially for tasks like adding local storage accounts and configuring clients.
Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide example commands.
If certain features are only available via PowerShell, clearly state this limitation and provide workarounds or alternatives for Linux users where possible.
Add a section or callout for Linux/macOS users, ensuring parity in management tasks and tooling.
Review all referenced scripts and procedures to ensure they are not Windows-specific unless absolutely necessary, and provide Bash or shell equivalents where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-specific tools and workflows. PowerShell is mentioned repeatedly as a primary management interface, and the password reset extension is described as being used via PowerShell. In the VM image preparation section, Windows image preparation is listed first and in more detail, while Linux-specific preparation is not directly referenced. There are more explicit links and instructions for Windows workflows, and Linux examples are less prominent or missing. The overall structure and tool recommendations favor Windows environments.

Recommendations:

Include equivalent Linux CLI (bash) examples and workflows alongside or before PowerShell examples.
Provide explicit links and instructions for preparing Linux VM images, not just Windows.
Mention and document Linux-native tools (e.g., SSH, cloud-init) for VM management and configuration.
Ensure that extension documentation (such as password reset) covers both Windows and Linux scenarios equally.
Balance the order of presentation so that Linux and Windows are treated with parity in all sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides examples using Windows-centric paths (e.g., C:\Workspaces), Windows images (e.g., microsoftwindowsdesktop_windows-ent-cpc_win11-24H2-ent-cpc), and PowerShell tasks. There are no examples or guidance for Linux-based Dev Boxes, Linux file paths, or Linux shell commands, which may disadvantage users working in Linux environments.

Recommendations:

Add parallel examples using Linux-based images (e.g., Ubuntu) in the YAML samples.
Include Linux file paths (e.g., /home/dev/Workspaces) alongside Windows paths in examples.
Demonstrate use of Linux shell commands (e.g., bash) in addition to PowerShell tasks.
Explicitly mention support for both Windows and Linux Dev Boxes, if applicable, and clarify any limitations.
Ensure that any tooling or workflow described (such as cloning repositories) is shown in a cross-platform manner.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing instructions and file paths specific to Windows (e.g., editing C:\Windows\System32\Drivers\etc\hosts), referencing Windows certificate installation steps and screenshots, and omitting equivalent instructions or examples for Linux or macOS clients. There are no Linux-specific paths, commands, or guidance for certificate import or hosts file editing, making it less accessible for users on non-Windows platforms.

Recommendations:

Add parallel instructions for Linux and macOS clients, including how to edit /etc/hosts and import certificates using system tools (e.g., update-ca-certificates, certutil, or browser-specific steps).
Include Linux/macOS command-line examples and screenshots where appropriate, such as using nano/vim for hosts file editing or certificate management GUIs.
Clearly indicate when a step is platform-specific and provide alternatives for other operating systems.
Review all file paths and UI references to ensure they are either cross-platform or have platform-specific variants.
Consider adding a section or callout at the beginning noting supported client OSes and linking to relevant platform-specific instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell for VPN configuration, mentioning BitLocker (a Windows-specific encryption tool), and not providing equivalent Linux command-line or tooling examples. All scripting and automation references are Windows-centric, and there are no instructions or guidance for Linux or cross-platform users.

Recommendations:

Provide Linux command-line examples (e.g., using OpenSSL for certificate generation, or Linux VPN configuration steps) alongside or in place of PowerShell instructions.
Mention and document Linux-compatible encryption solutions (such as LUKS/dm-crypt) where BitLocker is referenced, or clarify if BitLocker is required due to hardware/firmware constraints.
When linking to automation or scripting guides (such as VPN configuration), include Bash or cross-platform Azure CLI examples, not just PowerShell.
Explicitly state platform requirements and, if Windows-only tools are required, offer workarounds or alternatives for Linux/Mac users.
Add a section or callout for Linux users, summarizing any differences or additional steps needed for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by exclusively referencing PowerShell for command-line operations, mentioning BitLocker (a Windows encryption tool), and providing no Linux or cross-platform command-line examples. Remote access is described only in terms of PowerShell sessions, and all CLI instructions use PowerShell syntax. There is no mention of Linux shells, tools, or alternative workflows for non-Windows users.

Recommendations:

Provide equivalent Linux/Bash command examples for resource provider registration and other Azure CLI operations (e.g., using 'az' CLI).
Mention and document how to access the device remotely from Linux/macOS systems, including SSH or cross-platform PowerShell Core if supported.
Clarify whether BitLocker is the only supported encryption technology, and if so, note the limitation; if not, document Linux-compatible alternatives.
When referencing tools or workflows, present cross-platform options or explicitly state platform limitations.
Add notes or sections for Linux/macOS users where workflows or tools differ, ensuring parity in instructions and troubleshooting.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions and cmdlets for configuring Azure Monitor on the Azure Stack Edge Pro GPU device. There are no equivalent Bash, Linux shell, or cross-platform CLI examples for key configuration steps. The only interactive shell output shown is PowerShell, and the user is explicitly directed to connect to the device via PowerShell, with no mention of Linux or Bash alternatives.

Recommendations:

Provide equivalent Bash or Azure CLI examples for all PowerShell cmdlets and configuration steps, especially for Linux/macOS users.
Clarify whether the device can be managed via SSH or Bash, and if so, include those instructions alongside PowerShell.
If certain steps are Windows-only, explicitly state this and offer alternative guidance for Linux users where possible.
Include screenshots or terminal output from both Windows (PowerShell) and Linux (Bash) environments to ensure parity.
Review all references to shell environments and tools to ensure they are inclusive of both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses on troubleshooting IoT Edge issues on Azure Stack Edge Pro GPU devices, but it demonstrates a Windows bias. The 'Next steps' section specifically references debugging via the PowerShell interface, and there are no explicit Linux or cross-platform command examples or troubleshooting steps. The documentation appears to assume a Windows environment, omitting Linux equivalents or guidance.

Recommendations:

Include Linux-based troubleshooting steps and examples alongside or before Windows/PowerShell instructions.
Reference cross-platform tools (e.g., Bash, SSH, Linux command-line utilities) where applicable.
Ensure that links and included content provide parity for both Windows and Linux users.
Explicitly state if certain steps are Windows-only, and provide alternatives for Linux environments.
Add a section or note clarifying platform support and any differences in troubleshooting procedures.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by repeatedly referencing Windows-specific features and limitations (such as ReFS metadata and SMB protocol), describing the Data Box as a Windows-based device, and omitting Linux-specific guidance or examples. There are no Linux or cross-platform instructions or caveats, and Windows terminology is used exclusively when discussing file system and protocol compatibility.

Recommendations:

Include explicit information about Linux compatibility, such as supported file systems (e.g., ext4, XFS) and any caveats when using Data Box with Linux clients.
Provide examples and limitations for both Windows and Linux environments, especially regarding file naming, protocol support (e.g., NFS vs SMB), and case sensitivity.
Clarify whether features like ReFS metadata space consumption are relevant only to Windows or if there are analogous considerations for Linux file systems.
Add a section or table comparing Windows and Linux behaviors and limitations when using Data Box.
Mention Linux tools/utilities (e.g., rsync, NFS mount commands) alongside Windows tools where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All certificate import instructions and screenshots are exclusively for Windows, with no mention of Linux or macOS equivalents. The only installation guidance for openssl is via Chocolatey and PowerShell, and all command-line examples are shown in a Windows/PowerShell context. There are no examples or instructions for certificate management on Linux clients, nor are Linux tools or workflows mentioned.

Recommendations:

Add parallel instructions and screenshots for importing certificates on Linux (e.g., using 'update-ca-certificates', 'certutil', or 'openssl' commands).
Provide openssl installation instructions for Linux (e.g., 'apt install openssl' for Debian/Ubuntu, 'yum install openssl' for RHEL/CentOS, etc.), and mention macOS (e.g., 'brew install openssl').
Include Linux/macOS command-line examples for certificate creation and management, and show terminal output from those platforms.
Generalize language to refer to 'client systems' rather than only 'Windows clients', and clarify which steps are platform-specific.
Ensure that references to certificate stores (e.g., 'Personal store', 'Trusted Root Certificate Authorities') are mapped to Linux/macOS equivalents or explain how to achieve similar trust configuration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias by referencing Windows tools and workflows (e.g., File Explorer, Storage Explorer) as the default for interacting with shares and viewing data, without providing equivalent Linux instructions or examples. While there is a mention of rsync for NFS shares (a Linux/Unix tool), the majority of user interaction steps (such as connecting to shares and verifying data movement) assume a Windows environment. There are no explicit Linux file manager or CLI examples for these tasks.

Recommendations:

Provide explicit Linux examples for connecting to SMB/NFS shares (e.g., using the mount command, Nautilus, or Dolphin file managers).
When referencing File Explorer, also mention common Linux alternatives (e.g., 'In File Explorer (Windows) or your Linux file manager...').
For Storage Explorer, clarify if there is a Linux version or suggest az CLI/portal alternatives for Linux users.
Where possible, provide CLI commands for both Windows (e.g., net use) and Linux (e.g., mount, smbclient) to ensure parity.
Review screenshots and UI instructions to ensure they are not exclusively Windows-centric, or provide Linux equivalents where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias. While the main focus is on Linux-based IoT Edge deployments (with a strong recommendation to use Linux VMs), the only explicit command-line interface mentioned for device interaction is PowerShell. The documentation refers users to 'Connect to the PowerShell interface of the device' and provides no equivalent Linux shell/CLI instructions. Additionally, the use of SMB shares as a primary example for storage may be more familiar to Windows users, and the order of presenting PowerShell before any Linux alternatives (which are missing) indicates a 'windows_first' pattern.

Recommendations:

Provide equivalent Linux shell (bash) commands for managing and querying IoT Edge modules, alongside PowerShell instructions.
Mention and demonstrate the use of Linux-native tools (e.g., SSH, Linux CLI utilities) for device management and module monitoring.
Include NFS-based storage examples and clarify SMB/NFS parity for both Windows and Linux users.
When referencing device interfaces, present Linux and Windows options in parallel, or default to Linux-first given the recommendation to use Linux VMs.
Add explicit instructions or links for Linux users to perform common tasks (e.g., listing modules, checking IP addresses) without requiring PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows connection instructions and tools (such as 'net use', File Explorer, and Robocopy) first and in detail, while Linux instructions are minimal and potentially inaccurate (using NFS instead of SMB). Linux copy tool examples are missing, and only Windows-specific tools are referenced for data copy operations.

Recommendations:

Provide Linux connection instructions using the correct SMB mounting command (e.g., 'mount -t cifs ...') instead of NFS.
Include Linux copy tool examples (such as 'cp', 'rsync', or 'smbclient') alongside Robocopy.
Present Windows and Linux instructions in parallel sections or give equal prominence to both.
Reference cross-platform or Linux-native tools for file copying, not just Windows tools.
Ensure all screenshots and UI instructions have Linux equivalents or clarify OS-specific steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the 'Enable compute network' section, where it references the use of the PowerShell cmdlet `Set-HcsKubeClusterNetworkInfo` for changing Kubernetes subnets. There is no mention of Linux or cross-platform alternatives for this operation, nor are there examples or instructions for Linux users. The documentation assumes access to a PowerShell interface, which is a Windows-centric tool, and does not provide parity for Linux environments. No Linux command-line equivalents or guidance are offered throughout the page.

Recommendations:

Provide Linux-compatible instructions or clarify if the device's management interface is accessible from Linux systems (e.g., via SSH or a web UI).
If PowerShell is required, mention whether PowerShell Core (cross-platform) can be used, and provide installation guidance for Linux users.
Offer equivalent Linux shell commands or scripts for any device management tasks that can be performed outside the web UI.
Explicitly state platform requirements and, where possible, ensure that all administrative actions can be performed from both Windows and Linux environments.
Include screenshots or examples from Linux environments if the device supports cross-platform management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd) and providing instructions only for enabling long paths on Windows clients, without mentioning Linux or macOS equivalents. There are no examples or guidance for Linux users regarding path length issues, validation, or copy tools, and no mention of cross-platform alternatives.

Recommendations:

Include equivalent instructions for handling long file paths on Linux and macOS clients, or clarify if such limitations do not apply.
Mention or provide cross-platform data copy and validation tools, or explicitly state if the provided tools are Windows-only.
Add Linux/macOS-specific caveats or best practices for copying data to Data Box Disk, especially regarding file system compatibility and naming conventions.
If the Data Box Disk workflow is only supported on Windows, state this clearly at the beginning of the documentation. Otherwise, ensure parity in examples and tool references for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and defaults (e.g., Windows Server Update Services, time.windows.com as the default NTP server), and does not mention or provide examples for Linux equivalents or alternatives. No Linux-oriented update or time server options are discussed, and the documentation assumes a Windows-centric environment for device integration.

Recommendations:

Include examples or references for using Linux-based update servers (such as apt-mirror, Spacewalk, or other Linux patch management solutions) where applicable.
Mention and provide examples of using public or enterprise NTP servers commonly used in Linux environments (e.g., pool.ntp.org) as alternatives to time.windows.com.
Clarify that WSUS is a Windows-specific solution and suggest Linux-compatible update server options for heterogeneous environments.
Add guidance or notes for administrators managing devices from Linux systems, including any relevant interoperability considerations.
Ensure that screenshots and instructions do not assume only Windows infrastructure, and highlight cross-platform compatibility where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (WSUS, Windows Update server) as defaults for update management, and does not mention or provide Linux equivalents or alternatives. There are no Linux-specific instructions or examples, and the documentation assumes a Windows-centric environment for certain features (e.g., update server configuration).

Recommendations:

Include references to Linux-compatible update mechanisms or clarify how updates can be managed in non-Windows environments.
Provide examples or guidance for Linux users, such as how to configure NTP, static IP, or proxy settings using Linux tools.
Mention cross-platform alternatives where possible (e.g., using open-source update servers, or clarifying that WSUS is optional and what Linux users should do).
Avoid assuming Windows as the default environment; explicitly state support for both Windows and Linux clients where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. It explicitly assumes a Windows client, provides all command-line examples in Windows PowerShell format (including drive letters and backslashes), and references Windows-specific tools and paths. There are no Linux or macOS command-line examples, nor are there instructions or notes for users on non-Windows systems. The prerequisites and procedural steps are written from a Windows perspective, with only a brief mention that other operating systems are supported, but without any concrete guidance or examples.

Recommendations:

Provide parallel Linux/macOS command-line examples for all kubectl commands, using standard POSIX shell syntax and file paths (e.g., /home/user/.kube).
Include instructions for installing kubectl and managing kubeconfig on Linux/macOS clients.
Replace or supplement Windows PowerShell-specific commands and output with bash/zsh equivalents.
Explicitly state in the prerequisites and throughout the guide that the procedure is applicable to Linux/macOS clients, and link to relevant OS-specific setup guides.
Where file paths are referenced (e.g., saving YAML files), show both Windows and Linux/macOS path formats.
If any steps are different for Linux/macOS (such as permissions or environment setup), provide those details.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and workflows (such as Azure PowerShell and Windows Server Update Services), showing screenshots of Windows File Explorer, and omitting explicit Linux or cross-platform certificate management examples. There are no instructions or examples for Linux users on how to generate, convert, or install certificates, nor are Linux-native tools mentioned.

Recommendations:

Add Linux-specific instructions and examples for generating, converting, and installing certificates (e.g., using OpenSSL, Linux command line, or relevant Linux tools).
Include screenshots or descriptions of certificate handling on Linux systems, such as using Nautilus or the terminal, alongside Windows File Explorer.
Mention and provide parity for Linux equivalents of Windows tools (e.g., instead of only Azure PowerShell, reference Azure CLI and OpenSSL).
Avoid referencing Windows-specific services (like WSUS) without also mentioning Linux alternatives or clarifying their relevance.
Ensure that all steps involving certificate management, download, and installation are documented for both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (e.g., WSUS, Windows Update server) and omitting Linux equivalents or alternatives. There are no examples or instructions for Linux environments, and Windows patterns are mentioned exclusively or first (e.g., update server defaults to Windows Update, no mention of Linux package update mirrors or tools). The absence of Linux-specific guidance for network readiness, device connection, and update management further highlights the bias.

Recommendations:

Include instructions for configuring Linux-based update servers (e.g., apt/yum mirrors) as alternatives to WSUS/Windows Update.
Provide examples or notes for performing device network readiness checks from Linux or macOS systems, not just Windows.
Mention cross-platform tools or provide parity in examples for both Windows and Linux environments (e.g., how to change IPv4 settings on Linux laptops).
Clarify that device management and configuration can be performed from non-Windows systems, if supported, and provide relevant steps.
Reference Linux-compatible certificate management and VPN setup tools where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. The only explicit command-line example is a PowerShell cmdlet (`Set-HcsMacAddressPool`), with no equivalent Linux command or guidance. The reference to 'PowerShell interface of the device' assumes familiarity with Windows tooling, and there are no Linux CLI or shell examples provided. While some sections mention Linux (e.g., Log Analytics agent for Linux), practical instructions and examples are Windows-centric.

Recommendations:

Provide equivalent Linux shell (bash) commands or instructions wherever PowerShell cmdlets are mentioned, or clarify if the device interface is only accessible via PowerShell.
If the device supports SSH or Linux-based management, include examples and guidance for Linux users.
Balance references to Windows tools with Linux alternatives, ensuring both platforms are equally represented in practical steps.
Explicitly state platform limitations if certain management actions are only possible from Windows.
Review all included content (e.g., referenced INCLUDES) to ensure Linux parity in examples and tool recommendations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page shows a moderate Windows bias. It references Windows-specific technologies and documentation (such as NIC Teaming on Windows Server, Failover Clustering, and PowerShell), and links to Windows-centric resources before or instead of cross-platform or Linux alternatives. PowerShell is mentioned as the CLI method for certain tasks, with no mention of Linux shell equivalents. There are no explicit Linux command-line examples or references to Linux-native tools for network configuration or clustering.

Recommendations:

Provide equivalent Linux shell (bash) or cross-platform CLI instructions alongside PowerShell references, especially for tasks like changing Kubernetes workload profiles.
When referencing clustering or network teaming, include links to Linux-based solutions (e.g., Linux bonding, Pacemaker/Corosync for clustering) or clarify if only Windows Server is supported.
Avoid linking exclusively to Windows Server documentation for concepts like NIC Teaming and Failover Clustering; instead, explain the underlying concepts in a platform-neutral way or provide Linux alternatives where possible.
Explicitly state platform requirements and limitations (e.g., if only Windows-based clustering is supported, clarify this up front).
Add Linux-specific troubleshooting tips or references for network configuration and validation, if the device or environment supports Linux management.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Windows PowerShell, Windows Firewall logs, Bitlocker), providing log examples and instructions that are Windows-centric, and omitting Linux equivalents or examples. There are no instructions or examples for Linux-based workflows, and all command-line references assume a Windows environment.

Recommendations:

Provide equivalent Linux command-line instructions (e.g., using Bash or SSH) for collecting logs and running diagnostics, if supported.
Include examples of firewall logs and intrusion logs from Linux-based systems (e.g., iptables, ufw, or systemd journal logs).
Mention Linux-compatible tools for disk encryption (e.g., LUKS) alongside Bitlocker.
Clarify if the device management UI and support package collection are accessible and function the same way from non-Windows clients.
If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide Linux usage examples.
Add a section or notes for users managing Azure Stack Edge from Linux or macOS environments, including any limitations or differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All command-line examples use PowerShell syntax and are shown from a Windows command prompt. Instructions for editing system files, installing certificates, and interacting with the device are written specifically for Windows (e.g., editing C:\Windows\System32\Drivers\etc\hosts, using the Certificate Import Wizard). There are no Linux/macOS equivalents or alternative instructions provided, and no bash or shell examples. Windows tools and paths are referenced exclusively, and the use of PowerShell cmdlets is pervasive throughout the guide.

Recommendations:

Provide parallel Linux/macOS instructions for all steps, including editing /etc/hosts, installing certificates (using update-ca-certificates or similar), and restarting Docker.
Include bash/shell command examples alongside PowerShell, especially for Docker and kubectl commands.
Replace or supplement PowerShell-specific cmdlets (e.g., Set-HcsKubernetesContainerRegistry) with REST API or cross-platform CLI alternatives, if available.
Show sample outputs from Linux/macOS terminals as well as Windows.
Explicitly state which steps are OS-specific and provide clear navigation for users on different platforms.
Reference Linux/macOS Docker installation guides in addition to Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing instructions and examples using Windows PowerShell, including explicit references to 'elevated Windows PowerShell session' and Windows-specific output. No Linux or cross-platform CLI examples (such as Azure CLI, Bash, or Python) are provided, and the workflow assumes the user is on a Windows system with PowerShell 5.0 or higher.

Recommendations:

Add equivalent examples using Azure CLI (az storage blob update) that work on Linux, macOS, and Windows.
Provide Bash and/or Python script examples for blob tiering to support non-Windows environments.
Avoid language such as 'Open an elevated Windows PowerShell session'; instead, use neutral phrasing or provide parallel instructions for Linux/macOS terminals.
Include a section or callout for Linux/macOS users, clarifying how to perform the same operations using cross-platform tools.
Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific security features (such as Windows Defender Device Guard and BitLocker), providing only PowerShell-based remote management instructions, and omitting Linux equivalents or examples. There is no mention of Linux tools, commands, or management patterns, and Windows technologies are presented as the default or only option.

Recommendations:

Include Linux-based management options, such as SSH or Linux CLI instructions, for remote device access and administration.
Document equivalent Linux security features or clarify if the device is Windows-only. If Linux is not supported, state this explicitly.
Provide examples using Linux tools for data encryption and protection, or explain how Linux clients interact with the device.
When mentioning Windows tools (e.g., BitLocker, Device Guard), also mention or compare with Linux alternatives (e.g., LUKS, SELinux/AppArmor) where applicable.
Ensure that documentation sections and examples are balanced, presenting both Windows and Linux usage patterns where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows (and Windows-specific tools like Robocopy) first and in greater detail, providing comprehensive step-by-step instructions and command output for Windows users, while Linux instructions are minimal and lack equivalent detail or examples. Linux users are only given a basic mount command, with no guidance on file copy tools, performance tuning, or sample output, and no mention of Linux-native alternatives to Robocopy.

Recommendations:

Provide Linux examples for copying data, such as using rsync or cp, including sample commands and recommended flags for performance and metadata preservation.
Include sample output for Linux copy operations, similar to the Robocopy output shown for Windows.
Offer performance tuning advice for Linux file copy tools (e.g., rsync options for parallelism, preserving ACLs, etc.), and compare them to the Robocopy recommendations.
Present Windows and Linux instructions in parallel sections or tables, rather than always listing Windows first and in more detail.
Mention and link to Linux-specific documentation or community resources for troubleshooting SMB mounts and file copy issues.
Clarify which features (such as metadata preservation) are supported or unsupported on Linux, and provide workarounds or references where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits Windows bias primarily by referencing Windows PowerShell as the next step for managing Azure Stack Edge devices, without mentioning or providing equivalent instructions for Linux or cross-platform tools. No Linux-specific examples, tools, or guidance are present, and the only management interface highlighted is Windows PowerShell.

Recommendations:

Include equivalent instructions and links for managing Azure Stack Edge devices from Linux environments, such as using Azure CLI, Bash, or cross-platform PowerShell Core.
Provide examples or references for Linux users alongside Windows/PowerShell instructions, ensuring parity in guidance.
Avoid presenting Windows tools or workflows as the default or only option; instead, offer platform-agnostic or multi-platform alternatives where possible.
Explicitly mention cross-platform management options in the 'Next steps' section, such as 'Manage via Azure CLI (Windows, Linux, macOS)' or 'Manage via PowerShell Core (cross-platform)'.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in several ways: all command-line examples (including for Linux VMs) use PowerShell and Azure PowerShell cmdlets, with no native Bash/CLI equivalents provided for Linux users. The sample outputs and instructions are shown from a Windows environment (e.g., PS C:\WINDOWS\system32>), even when managing Linux VMs. Windows-specific tools and paths are referenced first and more thoroughly. There is a lack of Linux-native command-line or scripting examples, and the removal command is only shown in PowerShell.

Recommendations:

Provide Azure CLI (az) command examples alongside or instead of Azure PowerShell cmdlets, especially for Linux VM scenarios.
Show Linux-native shell (Bash) commands and sample outputs for Linux users, including connecting to VMs, deploying templates, and removing extensions.
Balance the order of presentation: do not always present Windows first; alternate or present both OSes in parallel.
Include Linux-specific troubleshooting and log file locations in parity with Windows.
Clarify when commands are cross-platform (e.g., Azure CLI) and when they are Windows-only (e.g., PowerShell), and guide users to install necessary tools on their platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric patterns and tools. Examples include only providing SMB paths in Windows UNC format (\\Server\Share), specifying username formats in Windows domain style, and referencing Windows UI actions (right-click, Properties, Security tab) for permissions. There are no Linux/NFS examples or guidance, and compatibility with non-Windows NAS devices is explicitly stated as not officially supported.

Recommendations:

Provide explicit examples for Linux environments, such as NFS mount paths and Linux-compatible username formats.
Include instructions for setting permissions and accessing shares from Linux systems (e.g., using chmod/chown, setfacl, or Linux SMB/NFS clients).
Clarify the extent of support for non-Windows NAS devices and, if possible, provide troubleshooting or best-practices for Linux users.
When referencing file paths or commands, offer both Windows and Linux syntax where applicable.
If the service is truly Windows-only, state this clearly at the beginning to set user expectations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias, primarily through the exclusive mention of BitLocker (a Windows encryption tool) and VPN configuration via PowerShell in the context of encryption and device security. There are no Linux equivalents or cross-platform alternatives mentioned for these features. No explicit Linux or cross-platform command-line examples are provided, and the documentation references Windows-centric tools and patterns first or exclusively.

Recommendations:

When mentioning BitLocker for encryption, also reference Linux-compatible encryption solutions (e.g., LUKS/dm-crypt) and provide links or guidance for Linux users.
For VPN configuration, include instructions or references for configuring VPN using Linux tools (such as strongSwan, OpenVPN, or NetworkManager) alongside PowerShell-based instructions.
Ensure that any PowerShell or Windows-specific instructions are paired with equivalent Linux command-line examples where possible.
Review all referenced documentation (such as system requirements and VPN configuration) to ensure Linux support is clearly documented and easily discoverable.
Explicitly state supported operating systems and tools for device management and security features, clarifying cross-platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All command-line examples are shown in PowerShell, with Windows paths (e.g., C:\Users\<username>\.kube), and sample outputs are from PowerShell terminals. The prerequisites and instructions explicitly reference Windows PowerShell and Windows client systems, with only a brief mention that 'any other client with a Supported operating system' can be used, but no Linux or macOS instructions or examples are provided. There is no guidance for Linux users regarding equivalent commands, file paths, or shell environments.

Recommendations:

Add parallel Linux (bash) examples for all kubectl commands, including sample outputs from a Linux terminal.
Include Linux file paths (e.g., ~/.kube) alongside Windows paths when discussing configuration directories.
In the prerequisites, explicitly list supported Linux distributions and provide installation instructions for kubectl and any required tools on Linux.
Provide notes or callouts for any differences in behavior or setup between Windows and Linux clients.
Ensure that all instructions, especially those involving file manipulation or navigation, are cross-platform or have platform-specific sections.
Consider using neutral shell prompts (e.g., $ or >) in generic examples, or provide both PowerShell and bash prompts.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line interface for device reset, without mentioning or providing equivalent instructions for Linux or cross-platform users. There are no Linux shell (bash) examples or references to Linux tools for managing or resetting the device. The documentation also refers to using email applications generically, but the context and linked instructions are more likely to be familiar to Windows users. Overall, Linux users are not provided with parity in instructions or tool references.

Recommendations:

Provide equivalent Linux (bash/CLI) instructions for device reset and management alongside PowerShell examples.
Explicitly mention whether the local web UI and Azure portal are fully cross-platform, and clarify any OS-specific requirements.
If PowerShell is required, note whether PowerShell Core (cross-platform) is supported and provide installation guidance for Linux/macOS.
Include references to Linux-compatible tools for data management and device operations where possible.
Add screenshots or examples from Linux environments to demonstrate parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell deployment instructions, but PowerShell is given equal prominence despite being Windows-centric. The example workload is Internet Information Services (IIS), a Windows-only web server, with no mention of Linux alternatives. There are no Linux-specific examples or guidance for deploying or testing with Linux-based VMs or tools.

Recommendations:

Include Linux-focused deployment and testing examples, such as using Apache or Nginx on Linux VMs.
Provide explicit instructions for connecting to Linux VMs (e.g., SSH) and verifying deployment from a Linux perspective.
Clarify that Azure CLI is cross-platform and recommend it as the default for broader compatibility.
Add a Linux tab or section alongside PowerShell for parity, especially in deployment and validation steps.
Show how to configure and test the load balancer with both Windows and Linux backend VMs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias in the data copy section, where Windows tools (Robocopy) are mentioned first and in more detail, with a direct link to Robocopy documentation. Linux/Unix equivalents (cp, rsync) are mentioned only as alternatives for NFS hosts, with no further explanation or links. There are no explicit Linux command-line examples, and the documentation assumes familiarity with Windows SMB paths and tools. No Linux-specific troubleshooting or mounting instructions are provided.

Recommendations:

Provide Linux/Unix command-line examples for copying data (e.g., mounting SMB shares with mount.cifs, using rsync/cp for both SMB and NFS).
Include links to Linux/Unix documentation for relevant tools (e.g., rsync, mount.cifs, NFS client setup).
Mention Linux/Unix tools and workflows before or alongside Windows tools to avoid 'windows_first' ordering.
Add troubleshooting tips for Linux/Unix environments (e.g., handling SMB credentials, SELinux, firewall issues).
Clarify that both Windows and Linux hosts are supported, and provide parity in detail and guidance for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by presenting Windows tools (robocopy) and detailed usage instructions first, with extensive examples and option explanations. In contrast, Linux instructions are minimal, lacking detailed examples for copying metadata (ACLs, attributes, timestamps) and omitting step-by-step guidance for Linux-specific tools (e.g., smbcacls, cifsacl). The Linux section does not provide equivalent depth or clarity, making it harder for Linux users to achieve parity in functionality.

Recommendations:

Provide Linux examples with the same level of detail as the Windows section, including step-by-step commands for copying both data and metadata (ACLs, attributes, timestamps).
Include explanations of relevant Linux tools (e.g., smbcacls, cifsacl, getfacl/setfacl) and their options, similar to the robocopy option table.
Present Linux and Windows instructions in parallel sections or side-by-side, rather than Windows-first, to avoid the perception of prioritizing one platform.
Clarify any limitations or differences in metadata preservation between Windows and Linux up front, and offer workarounds or best practices for Linux users.
Add links to Linux-specific documentation or tutorials for copying ACLs and metadata to Azure Files.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by listing Windows-specific tools and paths before Linux equivalents, providing more detailed troubleshooting steps for Windows (e.g., AzCopy for Windows has its own section before Linux), and referencing Windows infrastructure (e.g., time.windows.com) without mentioning Linux alternatives. Some sections lack parity in Linux-specific troubleshooting details or examples.

Recommendations:

Ensure that Linux and Windows troubleshooting sections are presented with equal prominence and detail, possibly by combining them or alternating their order.
When referencing file paths (such as hosts file), always present both Windows and Linux paths together, or alternate their order to avoid Windows-first bias.
For system-level operations (like certificate import), provide explicit Linux commands and steps, not just generic instructions.
When referencing time synchronization (e.g., time.windows.com), mention Linux NTP pools (such as pool.ntp.org) as alternatives.
Include PowerShell and Bash (or shell) command examples side by side where applicable.
Review all sections to ensure Linux users are not left with less actionable or less detailed guidance compared to Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools, logs, and patterns (e.g., Windows account names, domains, and log formats in audit logs), and by omitting explicit Linux or cross-platform command-line examples for log inspection or troubleshooting. The documentation assumes familiarity with Windows conventions and does not provide parity for Linux users in terms of examples or guidance.

Recommendations:

Include explicit Linux examples for accessing and interpreting logs (e.g., using Linux commands to view error.xml, BOM, or audit logs).
Provide sample audit log entries from Linux/NFS access, not just Windows event logs.
Clarify that Data Box supports both SMB (Windows) and NFS (Linux/Unix) protocols, and offer troubleshooting/logging examples for both.
When referencing file paths or log formats, show both Windows-style (\path\file) and Linux-style (/path/file) examples.
Add guidance for Linux users on how to download and inspect logs, including recommended tools (e.g., cat, less, grep) and any differences in log content or access.
Ensure that any scripts or tools referenced (e.g., CRC checksum tool) are cross-platform or provide Linux-specific alternatives/instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by highlighting PowerShell commands alongside Azure CLI, and mentioning them first in the context of automating firmware analysis workflows. There are no explicit Linux shell or bash examples, and the documentation does not clarify parity or provide Linux-specific guidance where PowerShell is mentioned. However, the page does reference Linux distributions and features, and does not exclusively focus on Windows tools.

Recommendations:

When mentioning automation tools, always list cross-platform options (e.g., Azure CLI, Bash scripts) before or alongside PowerShell, and clarify their OS compatibility.
Provide explicit Linux/Bash command examples wherever PowerShell is referenced, or link to equivalent Linux documentation.
Clarify in the documentation which tools are cross-platform and which are Windows-specific.
Add a section or note on how Linux users can perform the same tasks, especially for onboarding and automation workflows.
Ensure that screenshots and UI references are not Windows-centric, or provide Linux equivalents if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page lists 'Windows event scans' and WMI as the only example of event scanning, with configuration instructions specifically for Windows. There are no Linux or cross-platform event scan examples, nor are Linux tools or methods mentioned. The DNS scan is generic, but the only detailed scan type is Windows-specific.

Recommendations:

Add examples and configuration instructions for Linux event scanning, such as using syslog, auditd, or other Linux-native monitoring tools.
Include Linux or cross-platform protocols and methods in the scan type table, ensuring parity with Windows.
If Linux event scanning is not supported, explicitly state this to avoid confusion and clarify platform limitations.
Reorder the table or provide both Windows and Linux examples side by side to avoid a Windows-first impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows Explorer as the rationale for file extensions, and by not providing any Linux-specific guidance or examples. The explanations for file types (.crt, .key) are framed in terms of Windows compatibility, and there are no instructions or considerations for Linux users, such as common Linux tools or file handling patterns.

Recommendations:

Include Linux-specific guidance, such as referencing common Linux file browsers or command-line tools (e.g., Nautilus, ls, cat) when discussing file extensions.
Provide examples for both Windows and Linux environments for certificate creation, file management, and validation.
Clarify that the file extensions are for compatibility across both Windows and Linux, and mention how these files are typically handled or recognized in Linux.
Add a section or callout for Linux users, highlighting any differences or additional steps they may need to take.
Avoid framing file format requirements solely in terms of Windows compatibility (e.g., 'for support in Windows Explorer'), and instead use neutral language or mention both platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Microsoft-centric tools and workflows (Azure portal, Microsoft 365 admin center, Microsoft tenants) without mentioning or providing alternatives for Linux users or cross-platform command-line options. There are no examples or instructions for Linux environments, and the documentation assumes the user operates within the Microsoft ecosystem, which is most commonly associated with Windows.

Recommendations:

Include guidance or references for users accessing the Azure portal and Microsoft 365 admin center from Linux systems, such as supported browsers or CLI alternatives.
Provide examples or links for performing key actions (e.g., license management, plan creation) using cross-platform tools like Azure CLI or PowerShell Core, which are available on Linux.
Clarify any platform dependencies or limitations, and explicitly state if all steps can be completed from non-Windows operating systems.
Add a section addressing Linux users, outlining any differences or additional steps required for onboarding sensors or managing subscriptions from Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All example images are Windows-based (Visual Studio on Windows), and the image requirements are exclusively for Windows OS (Windows 10/11 Enterprise). All command-line and configuration instructions use Windows-specific tools (PowerShell, DISM.exe, chkdsk, defrag), and UI instructions reference Windows features. There are no examples, instructions, or references for Linux images, tools, or workflows. Linux is not mentioned as a supported or considered platform.

Recommendations:

Add explicit guidance on whether Linux images are supported for Dev Box, and if so, provide equivalent Linux image requirements.
Include examples of creating and preparing Linux images for use in Azure Compute Gallery, including references to Linux-compatible tools (e.g., waagent, cloud-init, relevant shell commands).
For each Windows-specific command or tool (e.g., sysprep, DISM, chkdsk, defrag), provide Linux equivalents or note if not applicable.
Clarify in prerequisites and requirements sections if the service is Windows-only, or explicitly state Linux support status.
Where UI or portal instructions are given, note any differences or additional steps for Linux-based images if supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a mild Windows bias. Windows-based OPC UA server tools (e.g., KEPServerEx) are mentioned first and specifically, while Linux equivalents are not named. Powershell examples are provided alongside Bash, but Windows UI tools are referenced before generic or Linux alternatives. There is no explicit omission of Linux instructions, but the ordering and tool references prioritize Windows environments.

Recommendations:

When mentioning OPC UA server certificate export, provide named examples of Linux-based OPC UA servers and their certificate management methods, not just Windows (e.g., reference open62541, Prosys, or Unified Automation servers).
If referencing Windows-based configuration UIs (like KEPServerEx), also mention common Linux server management patterns (e.g., file system paths, command-line tools) with equal prominence.
In all sections where Powershell and Bash are shown, ensure Bash appears first or alternate the order to avoid implicit prioritization.
Add explicit guidance or links for Linux users on how to locate, export, and manage certificates on popular Linux OPC UA servers.
Where possible, avoid phrases like 'Windows-based configuration UI' without balancing with 'Linux-based' or 'cross-platform' alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists networking requirements for Microsoft Defender for IoT, and while it is largely platform-neutral, it does show some Windows bias. Specifically, it references WMI (Windows Management Instrumentation) and Windows Endpoint Monitoring as a monitoring method, with no equivalent mention of Linux monitoring tools or protocols. Additionally, the Windows-specific tool (WMI) is mentioned before SNMP, which is cross-platform, and there are no Linux-specific examples or references.

Recommendations:

Include Linux monitoring protocols and tools (e.g., SSH-based monitoring, collectd, or syslog) alongside WMI.
Provide examples or references for Linux endpoint monitoring, not just Windows.
When listing protocols, avoid putting Windows-specific tools (like WMI) before cross-platform or Linux-native options unless there is a clear reason.
Add a section or note on how to monitor Linux endpoints, including relevant ports and protocols.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-based licensing (Windows 10/11 Enterprise), using a Windows-based image (Visual Studio 2022 Enterprise on Windows 11 Enterprise), and omitting any mention of Linux-based dev box images or workflows. There are no examples or instructions for deploying or configuring Linux environments, nor are Linux tools or patterns referenced.

Recommendations:

Include examples or options for deploying Linux-based dev box images, if supported.
Mention Linux-compatible licensing or requirements where applicable.
Provide screenshots and walkthroughs for setting up a Linux dev box environment alongside Windows examples.
Reference Linux tools, shells, or development patterns where relevant.
Clarify in prerequisites and throughout the guide whether Linux is supported, and if not, explicitly state this to set user expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as a primary method for user and role assignment in Azure, and by focusing on Microsoft Entra ID and Active Directory integration, which are traditionally Windows-centric technologies. There are no explicit Linux or cross-platform command-line examples, and Linux-native tools or workflows are not mentioned. The documentation assumes familiarity with Windows tools and does not provide parity for Linux administrators.

Recommendations:

Include Azure CLI examples alongside PowerShell for user and role management, as Azure CLI is cross-platform and widely used on Linux.
Mention and provide examples for managing users and roles using REST APIs or SDKs, which are platform-agnostic.
Clarify whether on-premises OT sensors can be managed via Linux tools or interfaces, and provide relevant instructions if available.
Reference LDAP integration in a more platform-neutral way, and provide examples for integrating with non-Active Directory LDAP servers (such as OpenLDAP).
Ensure that any diagrams or examples referencing Active Directory also mention alternatives or generic LDAP groups.
Add a section or callout for Linux administrators, summarizing which tools and commands are available for user management on non-Windows systems.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by specifically recommending the use of the Defender for IoT Windows Management Instrumentation (WMI) tool to enhance device data visibility for Windows-based devices, without mentioning equivalent tools or processes for Linux-based devices. There are no examples or guidance for Linux environments, and Windows tooling is mentioned exclusively and first when discussing device data enhancement.

Recommendations:

Include equivalent guidance and tooling for enhancing device data visibility for Linux-based devices, such as using SSH, SNMP, or Linux-native inventory scripts.
Provide examples or references for both Windows and Linux environments when discussing device data enhancement.
Rephrase enhancement recommendations to be platform-neutral, or present Windows and Linux options side by side.
Clarify if certain features are Windows-only, and if so, provide alternative recommendations for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by focusing exclusively on Windows-based tools, services, and terminology (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) without mentioning or providing equivalent Linux tools or workflows. There are no examples or guidance for Linux users, and all app references and scenarios assume a Windows-centric environment.

Recommendations:

Include explicit guidance or notes for Linux users, such as how to access Dev Boxes from Linux clients using supported RDP clients (e.g., FreeRDP, Remmina) or via browser.
List and describe cross-platform or Linux-compatible tools for connecting to Dev Boxes, not just Microsoft Remote Desktop.
Clarify whether Conditional Access policies and Dev Box management are supported from Linux environments, and provide examples or links to relevant documentation.
Add a section or callout addressing Linux developer scenarios, including any limitations or required configurations.
Ensure that app tables and scenario descriptions mention Linux compatibility or alternatives where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias by providing a PowerShell example for granting group access to Azure resources, without offering equivalent examples for Linux users (e.g., Azure CLI or Bash). The PowerShell example is listed before any mention of cross-platform tools, and there are no Linux-specific instructions or references. This may make it less accessible for users managing Azure from Linux or macOS environments.

Recommendations:

Provide Azure CLI (cross-platform) examples alongside or before PowerShell examples for managing Azure RBAC and user permissions.
Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and link to relevant documentation.
Wherever PowerShell is referenced, add a parallel section or note for Bash/Azure CLI usage.
Review all external links and ensure they include both PowerShell and CLI options, or clarify when a feature is only available in one.
Consider reordering examples so that cross-platform tools (Azure portal, Azure CLI) are presented before Windows-specific tools (PowerShell).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a significant Windows bias. All VM creation steps use Windows Server images by default, and there are no instructions or examples for deploying or configuring Linux VMs. The IIS installation and configuration are provided exclusively with Windows PowerShell commands, and the test instructions assume the use of Internet Explorer. No Linux alternatives (such as Apache/Nginx installation, Bash commands, or Linux VM images) are mentioned or offered.

Recommendations:

Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
Include Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash commands.
Offer both PowerShell (Windows) and Bash (Linux) command examples for server configuration.
When referencing tools (e.g., Internet Explorer), mention Linux equivalents (e.g., Firefox, curl, wget).
Explicitly state that the process works for both Windows and Linux VMs, and link to relevant Linux documentation.
Consider alternating the order of Windows and Linux examples, or presenting them side-by-side for parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally platform-neutral but contains subtle Windows bias in certain sections. Specifically, endpoint management guidance and tooling (e.g., Sysinternals PsGetSid) are Windows-specific, and the discussion of endpoint management focuses on Windows VM scenarios. There are no equivalent Linux tools or management patterns mentioned, and no Linux-specific examples are provided for endpoint management or content filtering. The only explicit Linux mention is in the context of a Data Science VM image, but operational guidance and tooling are Windows-centric.

Recommendations:

For endpoint management, include information about Linux VM management, such as handling machine IDs (e.g., /etc/machine-id) and tools for verifying uniqueness on Linux.
Mention Linux-compatible endpoint management solutions (e.g., Ansible, Puppet, Chef, Azure Automation for Linux) alongside Windows tools.
When referencing tools like PsGetSid, provide Linux equivalents (e.g., commands to check machine IDs or hostnames).
In the content filtering section, suggest Linux-compatible filtering software and note any differences in managing admin/non-admin accounts on Linux VMs.
Review all operational examples and ensure both Windows and Linux scenarios are covered where applicable, especially in sections discussing VM preparation, management, and security.

Create pull request

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.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing configuration steps and file paths exclusively for Windows environments (e.g., 'c:\Program Files\PrivateArk\Server\dbparam.xml'), referencing Windows-specific tools (Server Central Administration, Traffic Light controls), and omitting equivalent instructions or file paths for Linux-based CyberArk deployments. No Linux or cross-platform alternatives are mentioned, and all examples assume a Windows server environment.

Recommendations:

Add parallel instructions for configuring CyberArk PSM on Linux servers, including Linux file paths (e.g., '/opt/PrivateArk/Server/dbparam.xml') and service management commands (e.g., using 'systemctl' or 'service' to restart the CyberArk service).
Clearly indicate whether the integration is supported on both Windows and Linux CyberArk deployments. If not, state the limitation explicitly.
Provide screenshots or CLI commands relevant to Linux environments where applicable.
Use platform-agnostic language where possible, or present both Windows and Linux steps side by side.
Mention any differences in syslog configuration or file placement between Windows and Linux installations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Microsoft-centric tools and patterns (Azure portal, Active Directory, Microsoft Entra join/hybrid join) without mentioning or providing parity for Linux-based workflows, tools, or directory services. There are no Linux command-line examples, nor is there guidance for users who might manage networks or authentication using Linux-native tools or open standards. The linked 'Network requirements' page is under a Windows-365 path, reinforcing the Windows-centric approach.

Recommendations:

Include examples or references for managing network connections using Azure CLI, which is cross-platform and commonly used on Linux.
Mention or provide guidance for integrating with non-Active Directory identity providers or open standards (e.g., LDAP, Kerberos) where possible.
Clarify whether Linux-based dev boxes are supported and, if so, provide specific instructions or considerations for Linux environments.
Add notes or sections for users who may be managing network connections from Linux or macOS systems, including relevant tools and commands.
Balance references to Windows-specific tools with cross-platform alternatives (e.g., Azure CLI, REST API) and ensure documentation is inclusive of non-Windows workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The code blocks and instructions are PowerShell-specific, which may disadvantage Linux/macOS users or those preferring CLI tools. While the text briefly mentions that Azure CLI and portal are also options, no concrete CLI or Bash examples are given.

Recommendations:

Add Azure CLI examples alongside PowerShell for all deployment steps, using Bash syntax where appropriate.
Present both PowerShell and CLI examples in parallel, or use tabs to allow users to select their preferred environment.
Explicitly mention that the Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Avoid language or steps that assume a Windows-first workflow (e.g., PowerShell-specific commands as the default).
Ensure all code blocks are available in both PowerShell and CLI/Bash formats to improve accessibility for Linux and macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and WinGet tasks as the primary means for Dev Box customization. There is no mention of Linux shell scripting, Bash, or Linux package managers, nor are there examples or guidance for non-Windows environments. The documentation assumes a Windows-centric workflow and does not address Linux developer scenarios.

Recommendations:

Include examples and guidance for Linux-based Dev Boxes, such as using Bash scripts and Linux package managers (e.g., apt, yum, zypper) in customization tasks.
Explicitly state whether Dev Box supports Linux images and, if so, provide parity in documentation for Linux customization workflows.
Add sample YAML customization files that use Linux scripting and tools, alongside the existing PowerShell/WinGet examples.
Clarify in the documentation if certain features are Windows-only, and provide alternative approaches for Linux users where possible.
Mention and document the use of cross-platform scripting (e.g., Python, Node.js) for tasks that need to run on both Windows and Linux Dev Boxes.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (such as SysPrep and PsGetSid) and scenarios are discussed. The GPU VM size tables also repeatedly specify '(Windows only)' for certain visualization scenarios, but do not clarify Linux support or provide Linux equivalents. There are no PowerShell-heavy examples or command-line instructions, but Linux tools, patterns, or management scenarios are not mentioned or are missing where relevant.

Recommendations:

In the 'Endpoint management' section, add information about Linux endpoint management tools and considerations (e.g., how to ensure unique host identifiers for Linux VMs, or mention tools like cloud-init).
Where Windows-only GPU VM sizes are listed, clarify Linux support for GPU visualization workloads, or explicitly state if Linux is not supported for those VM sizes.
If mentioning Windows tools (e.g., SysPrep, PsGetSid), provide Linux equivalents or note how similar tasks are handled on Linux (e.g., using 'hostnamectl', 'machine-id', or other Linux imaging best practices).
Add examples or notes for Linux-based labs where relevant, especially in sections discussing VM image preparation, endpoint management, and content filtering.
Review for other sections where Windows-specific terminology or tools are used, and ensure Linux parity or at least mention of Linux alternatives.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows and PowerShell. All code examples use PowerShell, and instructions reference Windows-specific tools and file paths (e.g., c:/temp). There is no mention or example of using Linux or Bash, and the image creation process is demonstrated only for Windows images. Even where the Azure CLI is mentioned, no CLI or Linux/Bash examples are provided. The customization step in the image template uses PowerShell scripts and Windows-specific package managers (Chocolatey), with no Linux alternatives.

Recommendations:

Provide parallel examples using Azure CLI and Bash for each PowerShell example, including registration, identity creation, and deployment steps.
Include instructions and examples for creating Linux images, not just Windows images.
When referencing file paths, use cross-platform notation or provide both Windows and Linux path examples.
Show how to customize images using Linux shell scripts and package managers (e.g., apt, yum) in the image template.
Explicitly state support for Linux where applicable, or clarify if the process is Windows-only.
Balance the order of presentation so that Linux and Windows approaches are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows images (e.g., Windows 11 Enterprise, Visual Studio on Windows) and Microsoft 365 apps. There are no mentions or examples of Linux-based images, nor any guidance for configuring or using Linux dev boxes. All recommended images and scenarios are Windows-centric, and the documentation does not acknowledge or provide parity for Linux development environments.

Recommendations:

Explicitly mention support (or lack thereof) for Linux images in Microsoft Dev Box, and if supported, provide examples for selecting and configuring Linux-based dev box definitions.
Include Linux image options in the 'Image' selection step, such as Ubuntu or other popular distributions, and provide example use cases for Linux development teams.
Offer guidance on configuring dev box definitions for Linux development, including recommended images, tools, and best practices.
Balance the documentation by presenting both Windows and Linux scenarios, ensuring that Linux development teams are equally supported.
If Linux is not supported, clearly state this limitation early in the documentation to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The 'Windows App' is highlighted as the default and recommended client for connecting to dev boxes, with detailed instructions and screenshots for Windows and legacy Remote Desktop clients. There is no mention of Linux-specific remote desktop clients or workflows, nor are there any Linux command-line or desktop environment examples. The browser-based connection is mentioned as an alternative, but Linux users are not directly addressed, and Linux-native tools are not discussed.

Recommendations:

Include explicit instructions and examples for connecting to a dev box from Linux systems, such as using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop) or relevant Linux packages.
Mention Linux compatibility and provide parity in guidance for Linux users alongside Windows and macOS.
Add screenshots or CLI examples from a Linux environment where applicable.
Clarify whether the 'Windows App' is available or supported on Linux (e.g., via web or preview builds), and if not, suggest alternatives.
Ensure that any references to remote desktop clients or connection methods are platform-neutral or provide equal detail for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias in the testing and validation steps. While the Azure CLI commands are cross-platform, all VM creation examples use Windows images, and all instructions for testing DNS resolution are written for Windows (PowerShell commands, Windows firewall configuration, and Windows command prompt outputs). There are no Linux VM creation examples, nor are there instructions for configuring or testing from a Linux environment.

Recommendations:

Add parallel Linux VM creation examples using a common Linux image (e.g., Ubuntu) alongside the Windows examples.
Provide instructions for configuring the firewall on Linux VMs to allow ICMP (e.g., using ufw or firewalld).
Include Linux command-line examples for testing DNS resolution (e.g., using ping, dig, or nslookup from a bash shell).
Show sample output from Linux terminals in addition to Windows PowerShell.
Explicitly state that the Azure CLI commands work on all supported platforms, and ensure parity in validation steps for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively discusses troubleshooting Remote Desktop (RDP) connectivity to dev boxes, focusing on Windows-specific tools and concepts. All examples and checks are centered around Windows environments (e.g., RDP, Windows Guest OS readiness), with no mention of Linux-based dev boxes, alternative remote protocols (like SSH), or Linux troubleshooting steps. This creates a strong Windows-first impression and omits guidance for users of Linux dev boxes.

Recommendations:

Explicitly state whether the Troubleshoot & Repair tool supports Linux-based dev boxes, and if not, clarify its scope.
Include troubleshooting steps and examples for Linux dev boxes, such as SSH connectivity issues, relevant diagnostic checks, and Linux guest OS readiness.
Mention Linux remote access protocols (e.g., SSH, VNC) alongside RDP where appropriate.
Provide parity in documentation by listing both Windows and Linux troubleshooting scenarios, tools, and expected outcomes.
If the tool is Windows-only, add a section for Linux users with alternative troubleshooting resources or a roadmap for future support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically focusing on Visual Studio and Microsoft Dev Box, which are Windows-centric. All command-line examples use PowerShell and Windows tools (e.g., devenv.exe), with no mention of Linux equivalents or cross-platform alternatives. There are no instructions or examples for performing similar tasks on Linux-based dev boxes, nor is there guidance for non-Windows environments.

Recommendations:

Provide equivalent instructions and examples for Linux environments, such as using VS Code or cross-platform .NET CLI tools for solution caching.
Include bash or shell script examples alongside PowerShell commands where possible.
Clarify whether the described features (e.g., Visual Studio solution cache, commit-graph optimizations) are available or relevant on Linux-based dev boxes, and if not, explicitly state this.
Mention cross-platform alternatives (e.g., Rider, VS Code, or MonoDevelop) and how to optimize their startup or cache behavior if applicable.
Reorganize sections to avoid implicit prioritization of Windows tools and workflows, or add a 'Platform support' section to clarify scope.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments, with all configuration steps, compatibility notes, and troubleshooting focused exclusively on Windows OS and tooling. There are no references to Linux or cross-platform scenarios, and all examples (including UI steps and CLI flags) assume Windows-based images and features. Linux users or those interested in non-Windows dev boxes are not addressed.

Recommendations:

Explicitly state whether hibernation is supported or not for Linux-based dev boxes, and provide parity guidance if/when it is.
If Linux support exists, add equivalent Linux image configuration steps (e.g., for Ubuntu or other supported distros), including CLI flags and any required OS settings.
Include troubleshooting steps and compatibility notes for Linux images, or clarify if only Windows images are supported.
Where possible, use neutral language (e.g., 'your OS' or 'the guest OS') and provide both Windows and Linux UI/CLI examples.
If hibernation is a Windows-only feature, clearly state this at the top of the documentation to set expectations for cross-platform users.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily uses Azure CLI examples, which are cross-platform, but it contains a key example for passing parameters that uses PowerShell-style variable assignment ($params = ...) and single quotes in JSON, which is not valid in Bash or Linux shells. There are no equivalent Linux/Bash examples for this scenario, and the only variable assignment shown is in a Windows/PowerShell style. This may confuse or exclude Linux/macOS users.

Recommendations:

Provide both PowerShell and Bash/Linux examples for variable assignment and parameter passing, especially for the --parameters argument.
Use JSON syntax compatible with both shells, or clearly distinguish between Windows/PowerShell and Linux/Bash usage.
Add a note or section clarifying cross-platform differences in CLI usage, particularly for scripting and variable handling.
Review all code snippets to ensure they are either shell-agnostic or have equivalents for both major platforms.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash equivalents, which are more commonly used on Linux and macOS. The DNS testing example uses nslookup in a Windows PowerShell prompt, and there are no examples using dig or host, which are standard on Linux. The documentation refers to Windows tools and patterns exclusively and does not provide Linux-specific guidance or parity.

Recommendations:

Provide Azure CLI (az) command examples alongside or in place of PowerShell for all DNS record creation and web app configuration steps.
Include DNS query examples using dig and/or host, which are standard on Linux, in addition to or instead of nslookup.
Avoid showing only PowerShell prompts (e.g., 'PS C:\>') and instead use generic shell prompts or show both Windows and Linux terminal examples.
Explicitly mention that the steps can be performed from any OS, and provide links or notes for installing required tools on Linux/macOS.
Consider restructuring the documentation to present cross-platform examples side-by-side, or default to Azure CLI, which is cross-platform.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by using PowerShell-style variable assignment (e.g., $VAR = ...) and line continuations (`) in all CLI examples, which are specific to Windows/PowerShell environments. There are no equivalent bash/Linux shell examples, nor any notes on how to adapt the commands for non-Windows platforms. This may confuse or exclude Linux/macOS users who use bash/zsh shells.

Recommendations:

Provide parallel bash/zsh examples for all CLI commands, using appropriate variable assignment (e.g., VAR=...) and line continuation (\).
Add a note at the top indicating which shell the examples are for, and link to guidance for adapting commands to other shells.
Where possible, use shell-agnostic syntax or clearly separate PowerShell and bash examples.
Explicitly mention that Azure CLI is cross-platform and provide links to installation/use instructions for Linux/macOS.
Review and update all code blocks to ensure Linux/macOS users can follow the steps without confusion.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the example VM OS, referencing RDP for remote access, and using PowerShell scripts for testing DNS resolution. There are no examples or instructions for creating or managing Linux VMs, nor for testing DNS resolution using Linux tools or shells. The documentation does not mention or show parity for Linux users in key steps.

Recommendations:

Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
Include examples for connecting to a Linux VM (e.g., using SSH) and testing DNS resolution with Linux-native tools (e.g., ping, dig, or nslookup from a Bash shell).
When referencing the 'Run command' feature, show both RunPowerShellScript (for Windows) and RunShellScript (for Linux) options.
Avoid assuming the use of RDP or Windows-specific ports; mention SSH and Linux authentication methods as alternatives.
Explicitly state that the process is OS-agnostic where possible, and highlight any differences for Linux users.
Add links to Linux-specific quickstarts or documentation where available.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several areas: all quickstart scripting examples for building and pushing custom container images use PowerShell (.ps1) scripts and PowerShell syntax, with no equivalent Bash or shell script examples for Linux/macOS users. The instructions reference 'Docker Desktop', a tool primarily associated with Windows and macOS, and do not mention Docker Engine or Linux-native Docker workflows. There are no explicit Linux/Bash script alternatives or guidance for non-Windows environments, and the PowerShell examples are presented as the default/only option.

Recommendations:

Provide equivalent Bash/shell script examples for building and pushing images, alongside PowerShell, to support Linux/macOS users.
Explicitly mention and provide instructions for using Docker Engine on Linux, not just Docker Desktop.
Where scripts are referenced (e.g., quickstart-image-build.ps1), offer or link to a Bash (.sh) version, or clarify cross-platform compatibility.
Instruct users on how to run the scripts on Linux/macOS, or provide guidance for adapting the process to those platforms.
Avoid assuming the use of Windows-specific tools or environments; ensure parity in documentation order and detail for both Windows and Linux workflows.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only the PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or linking to Linux/CLI alternatives. There are no command-line examples or instructions for Linux users, and the 'Next steps' section prioritizes PowerShell, which is most commonly associated with Windows environments.

Recommendations:

Include links to Azure CLI and/or Azure Portal guides for creating and managing Private DNS zones, in addition to the PowerShell guide.
Add example commands for both Windows (PowerShell) and Linux/macOS (Azure CLI) users where relevant.
Ensure that references to tooling and instructions are platform-neutral or provide parity between Windows and Linux environments.
In the 'Next steps' section, either generalize the link (e.g., 'create a Private DNS zone using PowerShell, Azure CLI, or Portal') or provide separate links for each platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All examples and built-in tasks focus exclusively on Windows tools such as PowerShell and WinGet. There are no mentions or examples of Linux-based tools, shell scripts, or cross-platform alternatives. The schema and task definitions assume PowerShell as the scripting language, and all sample commands are Windows-specific. No Linux or bash equivalents are provided, and the documentation does not address how to customize Dev Box environments for non-Windows images.

Recommendations:

Add examples and schema references for Linux-based Dev Box images, including the use of bash or shell scripts.
Introduce built-in tasks for common Linux tools (e.g., bash, apt, yum) alongside PowerShell and WinGet.
Provide parallel Linux examples for each Windows example, demonstrating how to achieve similar customizations on Linux environments.
Clarify in the documentation whether Linux-based Dev Boxes are supported, and if so, how to author cross-platform or Linux-specific tasks.
Consider abstracting task definitions to allow specifying the shell or interpreter (e.g., 'shell: bash' or 'shell: powershell') to support both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments and tools. All code samples are in C# and reference .NET SDKs, with setup instructions and project creation steps tailored to Visual Studio and Windows-centric workflows. There are no Linux-specific instructions, shell examples, or alternative tooling guidance. The documentation assumes use of Windows tools (e.g., Visual Studio, right-click 'Save as', dotnet CLI) and omits parity for Linux users.

Recommendations:

Provide explicit instructions for Linux users, such as using VS Code or JetBrains Rider, and include terminal commands for common Linux distributions.
Include bash/zsh shell command examples alongside Windows/PowerShell commands where relevant (e.g., for dotnet CLI, file downloads, and authentication setup).
Mention cross-platform editors and tools (e.g., VS Code, nano, vim) in addition to Visual Studio.
Clarify that the .NET SDK and Azure Digital Twins SDK are cross-platform, and provide any Linux-specific installation or troubleshooting notes.
Show how to download files using wget/curl as alternatives to browser right-click instructions.
Add a note or section on running the sample code on Linux/macOS, including any environment variable setup or authentication differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a moderate Windows bias. When discussing how to obtain an existing DNS zone file, the Windows DNS file location is described in detail before mentioning BIND (the most common Linux DNS server). In the verification section, only the Windows Command Prompt syntax for nslookup is shown, with no Linux/macOS equivalent. There are no explicit Linux shell or macOS Terminal examples for common DNS tools, and the only OS-specific tool usage is for Windows.

Recommendations:

When describing how to obtain a DNS zone file, provide equal detail for both Windows DNS and BIND (Linux), including example file paths and commands for both.
In the verification section, add examples for running nslookup (or dig) from Linux/macOS Terminal, showing the equivalent command and expected output.
Where Windows-specific tools or paths are mentioned, also mention the Linux/macOS equivalents (e.g., /etc/bind for BIND zone files).
Consider including a table or section summarizing OS-specific steps for common tasks (obtaining zone files, running DNS queries) to ensure parity.
Review all examples to ensure that, where OS-specific instructions are needed, both Windows and Linux/macOS users are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates bias towards Windows by linking only to a PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash). There are no Linux or cross-platform examples or references, and the PowerShell path is presented as the default.

Recommendations:

Add links to Linux-friendly guides, such as how to create a Private DNS zone using Azure CLI or Bash.
Wherever PowerShell examples are provided, also include Azure CLI or REST API examples to ensure cross-platform parity.
In the 'Next steps' section, avoid referencing only PowerShell documentation; instead, offer parallel links for both PowerShell and CLI.
Explicitly mention that Azure DNS management can be performed from any platform, and provide examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ visual_studio_only

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using Visual Studio for publishing the Azure Functions app, with no mention of cross-platform alternatives (such as VS Code, Azure Functions Core Tools, or CLI-based deployment). The instructions for running the sample data generator also assume a Windows environment (building and running a .exe), and there are no Linux/macOS-specific instructions or alternatives provided. While the Azure CLI is used for infrastructure deployment (which is cross-platform), the overall workflow assumes a Windows development environment.

Recommendations:

Provide instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools, VS Code, or the Azure CLI, in addition to Visual Studio.
Include guidance for building and running the WindTurbineDataGenerator on Linux/macOS (e.g., using dotnet CLI to build and run the project, rather than referencing the .exe).
Explicitly mention that the sample project can be developed and deployed from Linux/macOS, and provide any necessary prerequisites or steps.
Where screenshots or UI instructions are given, note any differences for non-Windows users or provide CLI alternatives.
Ensure all code and deployment steps are platform-agnostic or provide parallel instructions for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows tools and patterns. PowerShell (Resolve-DnsName) is presented first and in more detail, with multiple examples, while Linux/Unix-native tools (dig) are mentioned but not explained as thoroughly. The documentation references Windows-specific features (such as Group Policy and NRPT) without mentioning Linux equivalents or validation methods. There are no explicit Linux command-line examples (e.g., bash shell usage), and the guidance assumes familiarity with Windows environments.

Recommendations:

Provide Linux/Unix command-line examples (e.g., using dig in bash or sh, with sample output).
Present dig (the cross-platform tool) examples before or alongside PowerShell examples to avoid Windows-first ordering.
Mention Linux/Unix DNSSEC validation methods and tools (e.g., unbound, bind, systemd-resolved) where Windows Group Policy and NRPT are discussed.
Clarify that dig is available by default on most Linux distributions, and provide installation instructions for both Windows and Linux if needed.
Balance the number and detail of examples between Windows and Linux environments.
Reference Linux documentation or man pages for DNSSEC validation and troubleshooting.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line deployment instructions use Azure PowerShell, and the validation step uses Windows Command Prompt syntax (cmd). There are no examples or instructions for using Azure CLI (which is cross-platform and preferred on Linux/macOS), nor are there any Linux shell or terminal examples for validation (e.g., using dig or nslookup in a bash shell). The workflow and screenshots are tailored to Windows users, with no mention of Linux or macOS alternatives.

Recommendations:

Provide equivalent Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and commonly used on Linux/macOS.
Include Linux/macOS shell instructions for validation, such as using nslookup or dig from a bash terminal.
When referencing command-line tools, avoid using only Windows Command Prompt syntax; show both Windows and Linux/macOS alternatives side by side.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Add screenshots or output examples from Linux/macOS terminals where appropriate.
Rephrase steps to be OS-agnostic where possible, or clearly indicate when a step is specific to Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows and PowerShell. All migration steps, prerequisites, and automation are described exclusively using PowerShell scripts and modules, with explicit instructions to use an 'elevated PowerShell window.' There are no equivalent instructions or scripts for Linux or cross-platform environments, nor are alternative methods (such as Bash, Azure CLI, or Python scripts) provided. The documentation assumes the user is on Windows and does not address Linux or macOS users, except for a brief mention of Azure CLI in the discovery step.

Recommendations:

Provide equivalent migration instructions using Azure CLI and/or Bash scripts that can be run on Linux and macOS.
Offer a cross-platform version of the migration script (e.g., in Python or as an Azure CLI extension) and document its usage.
Explicitly state platform compatibility for the provided scripts and offer guidance for non-Windows users.
Include Linux/macOS-specific prerequisites and installation steps (e.g., how to install Azure CLI or PowerShell Core on Linux).
Ensure that all screenshots and command prompts are not Windows-specific, or provide alternatives for other platforms.
Reorder examples or provide parallel instructions so that Linux and cross-platform options are presented alongside or before Windows-specific ones.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Azure PowerShell instructions before Azure CLI, which can indicate a Windows-first bias. PowerShell is primarily associated with Windows environments, and its commands are featured prominently. Although Azure CLI is cross-platform and included, there are no Linux- or macOS-specific notes or examples, and no mention of Bash or shell scripting, which are common for Linux users.

Recommendations:

Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform and widely used on Linux.
Include explicit notes or examples for Linux/macOS users, such as Bash command usage or environment-specific tips.
Clarify that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for each.
Consider adding a section or callout for Linux users, highlighting any differences or best practices.
Avoid implying that PowerShell is the default or preferred method unless there is a technical reason.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only a Windows/Powershell example (nslookup with C:\> prompt) for testing DNS resolution, with no mention of Linux or cross-platform alternatives. The command-line example and screenshot style are Windows-centric, and there is no guidance for users on Linux or macOS systems.

Recommendations:

Include equivalent Linux/macOS command-line examples for DNS resolution, such as using nslookup or dig from a bash shell (e.g., $ nslookup 10.1.2.5 or $ dig -x 10.1.2.5).
Present both Windows and Linux/macOS examples side-by-side or indicate that the instructions apply to multiple platforms.
Use neutral language when referring to command-line operations (e.g., 'Open a terminal or command prompt') rather than assuming a Windows environment.
Add screenshots or output samples from Linux/macOS terminals where appropriate to ensure parity.
Explicitly mention that the Azure portal steps are platform-agnostic, but that command-line verification can be performed from any OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and solutions (such as Windows Device Manager and the Windows maximum path length limitation) without providing equivalent guidance for Linux users. Troubleshooting steps and error messages are often framed in a Windows context, and there are no Linux-specific examples or instructions for common cross-platform tasks like identifying serial ports or handling path length issues.

Recommendations:

For every Windows-specific troubleshooting step (e.g., using Device Manager to find COM ports), provide equivalent instructions for Linux (e.g., using 'ls /dev/tty*' or 'dmesg | grep tty').
When referencing Windows path length limitations, mention that Linux does not typically have this issue, but suggest checking for other filesystem limitations if relevant.
Include Linux-specific error messages or terminal output where applicable, or note differences in expected output.
Ensure that all steps and resolutions are presented in a cross-platform manner, or clearly separate instructions for Windows and Linux users.
Add a section or note at the beginning clarifying that the tutorials are cross-platform and that Linux users should refer to provided Linux-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by referencing Visual Studio and NuGet Package Manager (GUI) as the primary development environment and package management approach, with no mention of Linux-compatible tools or workflows. The service principal creation step links to a PowerShell-based guide, and there are no examples or instructions for Linux users (e.g., using .NET CLI, VS Code, or Bash).

Recommendations:

Add instructions for creating a service principal using Azure CLI (az), which is cross-platform, alongside or instead of PowerShell.
Include steps for installing NuGet packages using the .NET CLI (dotnet add package ...) for users on Linux or macOS.
Reference cross-platform editors such as Visual Studio Code, and clarify that the .NET SDK and libraries work on Linux and macOS as well as Windows.
Provide links to Linux/macOS setup guides for .NET development.
Ensure that all tooling and workflow steps are presented in a platform-neutral way, or provide parallel instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Windows Server and PowerShell-based instructions for configuring DNS conditional forwarders. No Linux or cross-platform DNS server configuration examples are given. Windows terminology and tools (PowerShell, Windows DNS Server role, DNS console) are used exclusively, and the only command-line example for configuring forwarders is in PowerShell. The documentation does not mention or provide steps for common Linux DNS servers (such as BIND or dnsmasq), nor does it acknowledge their usage in on-premises environments.

Recommendations:

Add equivalent instructions for configuring DNS conditional forwarders on popular Linux DNS servers, such as BIND (named.conf options) and dnsmasq.
Include Linux command-line examples (e.g., editing /etc/named.conf or using rndc for BIND) alongside PowerShell examples.
Explicitly state that the procedure applies to both Windows and Linux DNS servers, and provide links or references to relevant Linux documentation.
Where possible, use neutral terminology (e.g., 'on-premises DNS server') and avoid assuming the use of Windows Server.
Present Windows and Linux examples in parallel or alternate the order to avoid 'windows_first' bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While the core authentication concepts are cross-platform and SDK examples are language-agnostic, platform-specific instructions and examples favor Windows and PowerShell. For example, enabling managed identities references a Windows VM link first, and PowerShell is given as a primary scripting example for resource creation. There are no explicit Linux or Bash examples for common tasks, and CLI instructions are present but not highlighted as the default. There is also a lack of parity in step-by-step instructions or screenshots for Linux environments.

Recommendations:

Provide explicit Linux/Bash examples alongside PowerShell for all resource creation and configuration steps.
When referencing enabling managed identities, include links and instructions for both Windows and Linux VMs equally.
In sections showing Azure CLI and PowerShell, present CLI (cross-platform) examples first, or at least in parallel with PowerShell.
Add screenshots or walkthroughs for Linux environments where UI or OS-specific steps are shown for Windows.
Review all references to Windows tools and ensure Linux equivalents are mentioned and documented.
Where environment variables are set in code samples, show both Windows (setx, PowerShell) and Linux (export, Bash) approaches.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively deploying Windows Server 2019 virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any Linux VM deployment or Linux-based testing workflow. While the deployment and validation steps use both Azure CLI and PowerShell (which are cross-platform), all VM interaction and firewall testing instructions assume a Windows environment.

Recommendations:

Include Linux virtual machine deployment in the Bicep template and documentation, or provide an alternative Linux-based workflow.
Add instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux tools (such as curl or wget) instead of only using Remote Desktop and Internet Explorer.
Present both Windows and Linux examples side-by-side when describing how to test connectivity and firewall rules.
Avoid referencing Windows-specific tools (like Internet Explorer) as the only method for testing, or provide Linux browser/command-line alternatives.
Clarify that the scenario can be tested with either Windows or Linux VMs, and provide guidance for both.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All command-line automation and scripting examples are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The only non-portal automation path is via PowerShell, and all command-line DNS query examples use Windows paths (e.g., C:\>) and Windows-native tools (Resolve-DnsName). There are no Linux shell or Azure CLI examples for creating or managing DNS security policies, nor are there instructions for running equivalent DNS queries from Linux environments.

Recommendations:

Add Azure CLI examples for all resource creation, configuration, and management steps, alongside or in place of PowerShell.
Provide Bash shell command examples for DNS queries (e.g., using dig or host) from a Linux VM, including sample output.
When showing command-line DNS queries, use generic prompts (e.g., $ or #) or show both Windows (C:\>) and Linux ($) examples.
Document how to install and use the Azure CLI on Linux for DNS resolver and policy management.
Explicitly mention Linux support and provide parity in instructions, screenshots, and troubleshooting steps.
If certain features are only available via PowerShell, clearly state this and provide a roadmap or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux (Ubuntu/K3s) and Windows (AKS Edge Essentials) guidance, but there is a notable Windows bias in the ordering, tool recommendations, and example depth. Windows/AKS Edge Essentials is often mentioned before or more prominently than Linux equivalents, and the only automated cluster creation script provided is a PowerShell script for Windows. There is also a lack of parity in automation and scripting examples for Linux users.

Recommendations:

Ensure that Linux and Windows instructions are presented with equal prominence, alternating order or grouping by scenario rather than platform.
Provide equivalent automation scripts for Linux environments (e.g., a bash script to automate K3s cluster creation and Arc-enablement, similar to the provided PowerShell script for AKS Edge Essentials).
Where PowerShell scripts are referenced for Windows, offer bash or shell script alternatives for Linux users.
Explicitly state platform limitations or differences (e.g., if a feature is only available on Windows or Linux), and provide guidance for both platforms where possible.
Review all sections to ensure that Linux tools and patterns are not omitted or placed after Windows equivalents without justification.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides configuration steps using the Azure portal and Azure PowerShell, but does not mention or provide examples for Linux-native tools such as Azure CLI, nor does it reference Bash or shell scripting. The PowerShell example assumes the use of Windows or PowerShell Core, and there is no guidance for users on Linux or macOS platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell steps, ensuring Linux and macOS users have clear guidance.
Explicitly mention that PowerShell Core is cross-platform if relevant, or clarify any Windows-specific requirements.
Include Bash or shell scripting examples where appropriate.
Structure the documentation so that Azure CLI and PowerShell examples are presented together or allow the user to select their preferred platform.
Review included content (INCLUDE files) to ensure Linux parity is maintained throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references both Azure CLI and PowerShell for configuring retry policies and batching, but only provides explicit CLI examples (which are cross-platform). However, it refers to 'PowerShell command' alongside CLI in the retry policy section, but does not provide any PowerShell or Linux shell-specific examples. There is no explicit mention or example of Linux-specific tools, nor are there any bash or shell script examples. The order of mention ('CLI and PowerShell') and the lack of Linux-specific context or troubleshooting may suggest a subtle Windows-first or PowerShell-heavy bias.

Recommendations:

Provide explicit bash/Linux shell examples alongside Azure CLI and PowerShell examples, especially where scripting or automation is discussed.
When referencing both CLI and PowerShell, ensure parity by including example commands for both, or clarify that Azure CLI commands are cross-platform.
Include troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, environment variables) where applicable.
Avoid listing PowerShell before CLI or Linux tools unless there is a technical reason; consider rotating the order or stating that both are supported equally.
Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell cmdlets and assumes the use of the Azure PowerShell module, with no mention of equivalent commands or tooling for Linux or cross-platform environments (such as Azure CLI, Bash, or REST API). All examples and prerequisites are Windows/PowerShell-centric, and there is no guidance for users on Linux or macOS systems.

Recommendations:

Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
Include Bash shell examples for retrieving ARP tables or interacting with Azure resources.
Mention REST API options for users who may want to automate or script the retrieval of ARP tables without PowerShell.
Clearly indicate which instructions are Windows/PowerShell-specific, and provide parallel sections for Linux/macOS users.
Update the prerequisites to mention both PowerShell and Azure CLI as supported tools for this operation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides certificate generation instructions and examples exclusively for Windows PowerShell, with no equivalent Linux or macOS command-line examples. The phrase 'Consider installing manually for Windows' suggests a Windows-first approach, and all command snippets are in PowerShell syntax. No Linux or cross-platform shell commands are provided, despite the step CLI being cross-platform.

Recommendations:

Provide equivalent Linux/macOS shell (bash) commands for certificate generation using step CLI.
Explicitly mention that the step CLI works on all major platforms and link to installation instructions for Linux/macOS.
Rephrase instructions to present cross-platform steps first, or at least in parallel, rather than focusing on Windows/PowerShell.
Where possible, use generic command syntax or provide both PowerShell and bash examples side by side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring Service Bus queues and topics as event handlers for Azure Event Grid events. While Azure CLI is cross-platform, the inclusion of Azure PowerShell commands (which are most commonly used on Windows, despite cross-platform support) and the explicit labeling of 'Azure PowerShell' sections may signal a Windows-centric approach. Additionally, there are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell examples are given equal prominence to CLI, which can be perceived as Windows bias. The documentation does not mention or provide guidance for Linux-native tools or scripting patterns.

Recommendations:

Add explicit Bash or shell script examples alongside Azure CLI to demonstrate Linux-native usage patterns.
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and consider providing sample shell environments or notes for Linux users.
If PowerShell is included, note that PowerShell Core is cross-platform, and provide installation or usage notes for Linux users.
Consider the order of examples: present Azure CLI (cross-platform) before PowerShell, and make it clear that both are supported on all major OSes.
Include troubleshooting or environment setup notes for Linux users where relevant, especially for authentication or identity scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing escaping instructions and examples specifically for PowerShell, without mentioning or providing equivalent guidance for Linux shells (such as Bash or Zsh). The special character escaping section is Windows/PowerShell-centric, and there are no Linux or cross-platform examples for handling topic template syntax in non-Windows environments.

Recommendations:

Add explicit instructions and examples for escaping special characters (such as $ and |) in common Linux shells (e.g., Bash, Zsh), alongside the existing PowerShell examples.
Clearly label which examples are for PowerShell and which are for Linux/macOS shells to avoid confusion.
Where possible, provide cross-platform examples or note any differences in behavior between Windows and Linux environments.
Review other sections for implicit Windows-first assumptions and ensure parity in tooling and workflow descriptions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows and Hyper-V. It assumes the use of Windows-based lab VMs, exclusively describes enabling and managing nested virtualization with Hyper-V, and provides only PowerShell/Windows tool examples. Linux is only mentioned as a possible guest OS, with no instructions or parity for Linux-based host VMs or alternative virtualization technologies. There are no Linux command-line examples, and all configuration steps and recommendations are Windows/Hyper-V-centric.

Recommendations:

Clarify early that nested virtualization is only supported on Windows-based lab VMs, but provide guidance or links for Linux users where possible.
Add examples or notes for Linux-based virtualization solutions (e.g., KVM, QEMU) if/when supported, or explicitly state their lack of support.
Where PowerShell or Hyper-V tools are used, provide Linux equivalents or explain the absence of such features on Linux.
Include Linux command-line examples for any steps that could be performed on Linux, or clearly state that such steps are not applicable.
In the 'Best practices for running Linux on Hyper-V' section, summarize key points directly in the doc instead of only linking out, and provide troubleshooting tips specific to Linux guest VMs.
If Linux-based host VMs are not supported, make this limitation prominent at the top of the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by providing command-line examples exclusively using Windows tools (ARMClient.exe) and PowerShell syntax, with no mention of Linux or cross-platform alternatives for obtaining bearer tokens or interacting with the Azure Resource Manager API. There are no CLI or shell examples for Linux/macOS users, nor are Linux-compatible tools suggested.

Recommendations:

Provide equivalent instructions and examples for Linux/macOS users, such as using Azure CLI (az) or curl to obtain bearer tokens and query the ARM API.
Mention cross-platform tools (e.g., Azure CLI, REST API with curl) alongside Windows-specific tools like ARMClient.exe.
When presenting command-line examples, offer both PowerShell and Bash/shell alternatives, or use cross-platform syntax where possible.
Explicitly state when a tool or command is Windows-only, and offer a Linux-compatible alternative in the same section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing all Azure-side command-line examples exclusively in PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. Additionally, network validation steps from the client side use Windows tools (tracert) and Windows-style paths (C:\Users\...), with no mention of Linux alternatives (e.g., traceroute). This may disadvantage users operating from Linux or macOS environments.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI (az) command example, which is cross-platform and widely used on Linux/macOS.
When demonstrating network validation from the client side, include both Windows (tracert) and Linux (traceroute) command examples.
Use generic file paths or clarify that steps apply to both Windows and Linux environments where possible.
Explicitly mention that the procedures are applicable regardless of the on-premises OS, and provide guidance or links for users on non-Windows systems.
Consider including Bash script snippets or references to Linux-native tools for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by prioritizing Windows and PowerShell instructions, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and lack parity in example commands or troubleshooting. There are also references to Windows path conventions and Docker Desktop, with less emphasis on native Linux workflows.

Recommendations:

Provide equally detailed, step-by-step instructions for Linux and macOS users, including explicit shell commands for cloning repositories, navigating directories, and running scripts.
Avoid assuming Docker Desktop as the default; mention native Docker Engine for Linux and provide installation links for all platforms.
List Linux/macOS instructions before or alongside Windows instructions to avoid a Windows-first impression.
Include troubleshooting notes and path conventions relevant to Linux/macOS (e.g., forward slashes, permissions).
Where PowerShell or Windows-specific commands are given, provide equivalent bash/zsh commands for Linux/macOS.
Clarify when WSL is only needed for Windows, and offer native Linux alternatives where possible.
Add screenshots or terminal output examples from Linux/macOS environments, not just Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra Application in Azure Event Grid. All examples and instructions are tailored to PowerShell, which is traditionally a Windows-centric tool, and there are no equivalent Bash, CLI, or Linux-native examples or guidance. The use of PowerShell modules and cmdlets (e.g., Get-MgServicePrincipal, New-MgServicePrincipal) further reinforces the Windows bias, and there is no mention of how to perform these steps using cross-platform tools or on Linux/macOS environments.

Recommendations:

Provide equivalent examples using Azure CLI (az) and Microsoft Graph CLI or REST API, which are cross-platform and commonly used on Linux/macOS.
Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation instructions for Linux/macOS.
Add Bash script examples or step-by-step instructions for Linux users.
Include a section comparing the different approaches (PowerShell, CLI, REST API) and when to use each.
Ensure screenshots and portal instructions are not Windows-specific, and clarify that the Azure Portal is web-based and OS-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only Azure PowerShell examples for managing the Azure Firewall Management NIC, with no mention of Azure CLI (cross-platform) or ARM/Bicep templates. All command-line automation is shown using PowerShell cmdlets, which are most familiar to Windows users. There are no Linux/Unix shell or Azure CLI equivalents, and the documentation implicitly assumes a Windows-centric workflow.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Mention that both Azure PowerShell and Azure CLI can be used, and provide links to both sets of documentation.
Where possible, provide ARM/Bicep template snippets for infrastructure-as-code scenarios, which are platform-agnostic.
Ensure screenshots and portal instructions do not assume a particular OS, and clarify that all steps can be performed from any supported OS.
Consider the order of presentation: introduce cross-platform tools (Azure CLI, ARM/Bicep) before or alongside PowerShell to avoid the impression that Windows tools are preferred.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides a balanced set of code samples for generating SAS tokens in multiple languages (NodeJS, Java, PHP, C#, PowerShell, Bash). However, there is a mild Windows bias: PowerShell (a Windows-centric tool) is given a dedicated section, and the Bash example (for Linux/macOS) is placed last. Additionally, disabling SAS authentication is only described via the Azure Portal (a GUI tool most accessible on Windows) and ARM templates, with no mention of CLI or Linux-native tooling. There are no explicit Linux command-line (Azure CLI) examples for management tasks, and the documentation references .NET samples first in the 'Samples' section.

Recommendations:

Reorder code samples so that Bash (Linux/macOS) appears before PowerShell, or present them side-by-side.
Add Azure CLI examples for management tasks such as disabling SAS/local authentication, alongside ARM template and Portal instructions.
Include references to SDK samples in other languages (e.g., Python, Java) and not just .NET, to improve cross-platform parity.
Explicitly mention that Bash scripts are suitable for Linux/macOS environments, and PowerShell for Windows, to guide users.
Where possible, provide parity in tooling instructions (e.g., show how to perform management tasks using both Azure CLI and Portal).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by focusing primarily on Windows-based tooling and workflows (Hyper-V Manager, PowerShell) for preparing and converting Linux images. Linux-native hypervisors and tools (such as KVM, qemu-img, or Linux CLI workflows) are only briefly mentioned or referenced as alternatives, without step-by-step guidance. The primary example assumes a Windows host and does not provide equivalent Linux-based instructions.

Recommendations:

Add a parallel section detailing how to prepare, convert, and upload a Linux image using Linux-native tools (e.g., KVM, qemu-img, libvirt, and Linux CLI).
Provide step-by-step instructions for creating and converting VHDs on Linux, including commands for qemu-img and guidance for managing disk formats and sizes.
Include examples of uploading VHDs to Azure from a Linux environment, using tools like AzCopy for Linux, Azure CLI, or REST APIs.
Ensure that Linux-based workflows are presented with equal prominence and detail as Windows-based workflows, ideally in side-by-side or clearly separated sections.
Reference Linux documentation and tools first or equally, rather than defaulting to Windows/Hyper-V as the primary workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references Azure PowerShell as a configuration method for ExpressRoute FastPath, but does not mention or provide examples for Azure CLI, which is cross-platform and commonly used on Linux and macOS. The 'Next steps' section lists Azure PowerShell after the portal, but omits Azure CLI entirely. There are no command-line examples or instructions tailored for Linux users, and the only automation example is Windows-centric (PowerShell).

Recommendations:

Add Azure CLI instructions and examples alongside or before Azure PowerShell in the 'Next steps' section and throughout the documentation.
Explicitly mention that both Azure PowerShell and Azure CLI can be used for configuration, and provide parity in example commands.
Where scripts or automation are referenced, provide both PowerShell and Bash (or CLI) equivalents to ensure Linux users are supported.
Review the documentation for other Windows-centric terminology or tools, and ensure Linux alternatives are equally represented.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation mentions PowerShell as a supported automation method for upgrading/downgrading Azure Firewall SKUs, but does not mention Azure CLI or provide Linux/Unix-oriented examples. The order of mention (PowerShell before Terraform) and lack of Linux-native tooling or examples suggest a Windows-first and PowerShell-heavy bias.

Recommendations:

Explicitly mention Azure CLI as a supported method for performing upgrades/downgrades, if available.
Provide example commands for both PowerShell and Azure CLI to ensure parity for Linux and cross-platform users.
List automation options in a neutral order (e.g., Azure CLI, PowerShell, Terraform) or group them by platform.
Include screenshots or walkthroughs for both Windows (PowerShell) and Linux (Azure CLI) environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by listing Azure PowerShell as a primary management option, providing explicit PowerShell cmdlet references, and not including any Linux-specific shell or scripting examples. While Azure CLI is mentioned (which is cross-platform), there are no explicit Bash or Linux shell examples, and the ordering of examples (Portal, CLI, PowerShell, C#) places Windows-centric tools before cross-platform or Linux-native approaches. No Linux-specific tools, patterns, or troubleshooting steps are provided.

Recommendations:

Add explicit Bash/Linux shell examples for CLI commands, including sample scripts for common failover and management tasks.
Ensure parity in example ordering: alternate or randomize the order of CLI and PowerShell, or explicitly note that CLI is cross-platform and suitable for Linux/macOS.
Include troubleshooting or operational notes relevant to Linux environments (e.g., environment variables, authentication methods, file permissions).
Reference Linux-native automation tools (such as shell scripts or Ansible) where appropriate.
In code samples, provide both Windows and Linux command-line usage where differences exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively provides PowerShell examples and references only the Az.LabServices PowerShell module for retrieving the public IP address of Azure Lab Services labs. There are no examples or instructions for performing the same task using Azure CLI, Bash, or other cross-platform tools. The documentation assumes the user is on Windows or has access to PowerShell, and does not mention or prioritize Linux or macOS workflows.

Recommendations:

Add equivalent examples using Azure CLI (az lab services) commands, which are cross-platform and work on Linux, macOS, and Windows.
Include Bash shell script examples for retrieving the public IP address, especially using Azure CLI.
Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation guidance for non-Windows systems.
Reorganize the documentation to present cross-platform (CLI/Bash) solutions before or alongside PowerShell examples.
Reference relevant Azure CLI documentation and modules, not just PowerShell cmdlets.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the frequent mention of PowerShell and the Azure portal as configuration tools, with no equivalent Linux or cross-platform CLI examples provided. References to REST API and Azure CLI are present but are less emphasized and often listed after PowerShell. There are no Linux-specific instructions, nor are there examples using bash or Linux-native tools. This can make the documentation less accessible or intuitive for Linux users or those preferring cross-platform command-line tools.

Recommendations:

Provide Azure CLI (az) examples alongside or before PowerShell examples for all configuration and management tasks.
Include bash shell snippets and Linux-native command-line instructions where relevant.
Ensure that references to management tools (Azure portal, PowerShell, REST API, Azure CLI) are presented in a neutral or parallel order, not prioritizing Windows tools.
Add explicit notes or sections for Linux users, clarifying any platform-specific considerations or differences.
Where screenshots or images of tools are shown, include both Windows and Linux variants if applicable.
Review all procedural steps to ensure parity between Windows and Linux environments, especially for automation and scripting.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All command-line examples use Azure PowerShell cmdlets, and file paths are shown in Windows format (e.g., C:\Users\SampleUser\Downloads) before Linux/Cloud Shell equivalents. There are no CLI (az) or Bash examples, and Linux-specific guidance is minimal or secondary. The documentation assumes the use of Windows tools and environments, with only a brief mention of Cloud Shell for Linux-like environments.

Recommendations:

Provide Azure CLI (az) command examples alongside or instead of PowerShell, as Azure CLI is cross-platform and widely used on Linux.
For each step, include both Windows (PowerShell) and Linux (Bash/CLI) command examples, clearly labeled.
When referencing file paths, show both Windows (C:\...) and Linux (/home/...) formats together.
Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or Cloud Shell, and provide links to relevant setup guides.
Avoid assuming the user is on Windows or using PowerShell by default; use neutral language and tool-agnostic instructions where possible.
Add a section at the beginning explaining tool options (PowerShell, Azure CLI, Cloud Shell) and their cross-platform availability.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references Azure PowerShell for deployment guidance and does not mention or provide examples for Linux tools or CLI equivalents. There are no Linux-specific instructions or examples, and the only deployment link points to a PowerShell-based guide, suggesting a Windows-centric approach.

Recommendations:

Include equivalent deployment instructions using Azure CLI (az) and Bash, not just Azure PowerShell.
Provide examples or references for configuring proxy settings on popular Linux browsers and applications.
Add guidance for uploading PAC files using Linux tools (e.g., azcopy, Azure CLI) in addition to any Windows-based methods.
Ensure that any screenshots or walkthroughs are platform-agnostic or show both Windows and Linux environments where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) command-line examples for subscription registration, without offering equivalent Azure CLI (cross-platform) or Bash examples. The initial steps for provider registration use PowerShell cmdlets exclusively, which may disadvantage Linux or macOS users. The remainder of the documentation uses REST API examples, which are platform-neutral.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell commands, especially for subscription registration and provider feature registration steps.
Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide guidance for users on Linux/macOS.
Where possible, provide Bash shell examples for REST API calls (e.g., using curl) to demonstrate cross-platform usage.
Review introductory sections to ensure that Windows tools or patterns are not presented as the default or only option.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias. While it states that both Windows and Linux VMs are supported, the only deep-dive example or troubleshooting link is for Windows shutdown behavior. There are no Linux-specific configuration or troubleshooting examples, and the warning section references only a Windows guide. Linux support is mentioned, but without actionable Linux-focused guidance or parity in examples.

Recommendations:

Provide a Linux-specific guide or troubleshooting section analogous to the 'Guide to controlling Windows shutdown behavior', covering common Linux shutdown behaviors and how they interact with auto-shutdown.
Include concrete Linux command-line examples or screenshots for configuring and verifying auto-shutdown, similar to any Windows examples provided elsewhere.
Ensure that references to OS-specific behavior are balanced: if a Windows guide is linked, a Linux equivalent should also be offered.
Clarify any differences in user experience or required steps between Windows and Linux VMs, rather than focusing primarily on Windows scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong bias toward Windows and PowerShell usage. All command-line examples are provided exclusively in Azure PowerShell, with no Azure CLI (cross-platform) or Bash examples. The instructions for deploying, validating, and cleaning up resources rely solely on PowerShell scripts, which are more familiar to Windows users. There is no mention or example of using the Azure CLI, which is commonly used on Linux and macOS, nor are there Bash or shell script equivalents. This limits accessibility and parity for Linux and macOS users.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell scripts, including deployment, validation, and cleanup steps.
Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and show how to select the Bash environment.
Include Bash script snippets where appropriate, especially for steps that involve scripting or automation.
Reorder or parallelize instructions so that CLI/Bash and PowerShell examples are presented together, ensuring equal prominence.
Link directly to Azure CLI documentation and reference pages, not just PowerShell resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. While it does mention Linux support and provides some Linux-specific notes (such as enabling remote desktop and SSH for Linux VMs), Windows is generally presented as the default or primary scenario. The only command-line management tool mentioned is the Az.LabServices PowerShell module, with no mention of equivalent CLI or scripting options for Linux users. Additionally, the documentation refers to password management behaviors with a Windows-centric default, and Windows terminology and tools are referenced before Linux equivalents.

Recommendations:

Include Azure CLI examples for managing labs, alongside or instead of PowerShell, to ensure Linux parity.
Explicitly mention and link to cross-platform management tools (e.g., Azure CLI, REST API) wherever PowerShell is referenced.
When describing features or behaviors that differ between Windows and Linux (such as password management), present both platforms equally and clarify differences in parallel.
Add Linux-specific usage examples or screenshots where relevant, such as connecting to Linux VMs via SSH.
Avoid presenting Windows tools or workflows as the default; instead, structure documentation to address both Windows and Linux users equally.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by providing explicit PowerShell examples and references, while not offering equivalent Linux/bash examples. The CLI and PowerShell are both mentioned, but PowerShell is called out separately, and no bash or Linux shell examples are provided. This may make Linux users feel less supported or require them to adapt Windows-centric instructions.

Recommendations:

Add explicit bash/Linux shell examples alongside PowerShell for all management operations (such as adding a schema to a schema group).
When referencing command-line tools, mention cross-platform options (e.g., Azure CLI) before platform-specific ones (e.g., PowerShell).
Ensure that all sample links and instructions are clearly marked as cross-platform or provide separate instructions for Windows and Linux/macOS.
Include a note clarifying the cross-platform nature of the Azure CLI and provide sample commands for Linux environments.
Review all references to tools and scripts to ensure Linux users are not required to adapt Windows-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses PowerShell scripts and cmdlets for automation, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All automation examples and instructions are based on PowerShell, which is more commonly associated with Windows environments, and there is no guidance for users who may be working from Linux or macOS systems. The documentation also references Windows-centric tools and patterns (e.g., PowerShell runbooks) without acknowledging or providing parity for Linux-native approaches.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands and Bash scripts for automation tasks, alongside PowerShell.
Explicitly state that Azure Automation supports Python runbooks and provide a sample Python script for the same monitoring workflow.
Clarify whether the PowerShell scripts and modules used are compatible with PowerShell Core on Linux/macOS, and if so, provide installation and usage guidance for those platforms.
Include a section or note for Linux/macOS users, outlining any differences or additional steps required to achieve the same result.
Where possible, use cross-platform tools and language in instructions (e.g., refer to 'terminal' instead of 'PowerShell console', and avoid assuming a Windows environment).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses Azure PowerShell cmdlets for all configuration, verification, and management steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code examples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Azure CLI (az) command examples for each PowerShell example, as Azure CLI is cross-platform and widely used on Linux and macOS.
Add a section or notes explaining how to perform these tasks in Bash or from the Azure Cloud Shell using Bash.
Clarify that Azure PowerShell can be used on Linux/macOS, but still offer CLI alternatives for users who prefer native tools.
Ensure that prerequisites and setup instructions include both Azure PowerShell and Azure CLI installation and authentication steps.
Review all references to PowerShell to ensure they are balanced with cross-platform alternatives, and update headings/sections to reflect multi-platform support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell cmdlets as the primary or sole method for certain operations (e.g., updating firewall policy tags), and by mentioning PowerShell/CLI support limitations without clarifying Linux parity or providing Linux-native alternatives. There are no Linux-specific tools, commands, or examples provided, and the documentation assumes familiarity with Windows-centric tooling.

Recommendations:

For every mention of Azure PowerShell, also provide equivalent Azure CLI commands and examples, ensuring that Linux users have clear guidance.
Where PowerShell is referenced as a workaround (e.g., updating tags), explicitly state if Azure CLI or REST API can also be used, and provide those examples.
Include Linux-specific troubleshooting steps or examples where relevant, especially in sections discussing command-line operations.
Review all mitigation steps and ensure that they are platform-agnostic or provide both Windows and Linux approaches.
Where a feature is missing in PowerShell and CLI, clarify if this affects both Windows and Linux users equally, and provide REST API examples if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, omitting equivalent Azure CLI (cross-platform) or Bash examples. Additionally, the validation steps explicitly instruct users to create a Windows VM and do not mention Linux-based alternatives. This prioritizes Windows tools and workflows, making it less accessible for Linux or cross-platform users.

Recommendations:

Provide equivalent Azure CLI (az) and/or Bash script examples alongside PowerShell for all automation and resource creation steps.
In the validation section, include instructions for creating and using a Linux VM, or at least mention that the nslookup command works identically on Linux and macOS.
Where screenshots or step-by-step instructions reference Windows-specific UI or terminology, clarify that the process is similar for Linux-based resources.
Explicitly state that the procedures are platform-agnostic where possible, and highlight any differences for Linux users.
Consider including a table or toggle to switch between PowerShell and Azure CLI/Bash instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows tools (e.g., Visual Studio) as examples of software to install, mentioning Remote Desktop Protocol (RDP) before Secure Shell (SSH) when describing connection methods, and not providing any Linux-specific examples or guidance. There are no Linux tool examples or screenshots, and the workflow implicitly assumes familiarity with Windows environments.

Recommendations:

Provide Linux-specific examples of software to install on the template VM (e.g., GCC, Python, or Gedit) alongside Windows examples.
When describing connection methods, mention SSH before or equally with RDP, and clarify which OS each method applies to.
Include screenshots or instructions that show connecting to Linux-based template VMs.
Add notes or sections that address common Linux configuration tasks in lab templates.
Ensure parity in troubleshooting and known issues for both Windows and Linux template VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias by providing only Azure PowerShell commands for onboarding to ExpressRoute Direct, with no equivalent Azure CLI (cross-platform) or Bash examples. This assumes a Windows or PowerShell-centric workflow, potentially excluding Linux and macOS users. No mention is made of Linux-native tools or alternative onboarding methods.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell for all onboarding and management steps.
Explicitly state that both Windows and Linux/macOS users can manage ExpressRoute Direct, and provide guidance for each platform.
Where possible, include Bash shell examples for common tasks.
Avoid referencing only Windows-specific tools or workflows; ensure parity in instructions and tooling.
Consider a 'Choose your platform' section at the start of procedural steps, linking to both PowerShell and CLI/Bash instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias by providing troubleshooting commands and tool recommendations that are primarily Windows-centric. The main example for checking dropped packets uses 'psping.exe', a Windows-only tool, and the command is shown in Windows shell syntax. Alternative tools are only mentioned generically ('tnc', 'ping'), with no concrete Linux equivalents or examples provided. There is no explicit Linux or cross-platform command shown for key troubleshooting steps.

Recommendations:

Provide equivalent Linux/macOS commands for each troubleshooting step, especially for checking connectivity (e.g., using 'nc', 'nmap', or 'curl' on Linux).
Show both Windows and Linux/macOS command examples side by side where possible.
Explicitly mention and link to cross-platform tools (e.g., 'nmap', 'netcat', 'curl') and provide usage examples.
Avoid referencing only Windows-specific tools (like 'psping.exe') without Linux alternatives.
Ensure that shell command syntax is shown for both Windows (PowerShell/cmd) and Linux (bash/zsh) environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific management APIs (with a link to a Windows documentation page), mentioning PowerShell as the only example for ExpressRoute routing configuration, and omitting any Linux or cross-platform command-line examples or tools. There are no references to Linux-native tools or Azure CLI, and no examples are provided for Linux users.

Recommendations:

Include Azure CLI examples alongside or instead of PowerShell for configuration tasks, such as creating and modifying ExpressRoute circuits and routing filters.
Reference cross-platform management APIs and documentation, not just Windows-specific endpoints.
Explicitly mention that management and configuration can be performed from Linux, macOS, and Windows, and provide relevant examples.
Add links to Linux and cross-platform tooling documentation (e.g., Azure CLI, REST API usage) for ExpressRoute.
Ensure that all procedural steps and code snippets are platform-agnostic or have both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias primarily in the 'Before you begin' section, where only Azure PowerShell commands are provided for the required subscription enrollment step, with no equivalent Azure CLI or cross-platform instructions. Additionally, file path examples (e.g., C:\Users\SampleUser\Downloads\LOA.pdf) use Windows conventions without mentioning Linux alternatives. The initial enrollment step is Windows-first and lacks Linux parity, potentially blocking Linux/macOS users from following the guide end-to-end.

Recommendations:

Provide Azure CLI equivalents for all PowerShell commands, especially for the subscription enrollment step, or clarify if the step is only possible in PowerShell.
Include Linux/macOS file path examples (e.g., ~/Downloads/LOA.pdf) alongside Windows paths when specifying output destinations.
Add notes or links for cross-platform users on how to accomplish prerequisite steps using CLI or REST if PowerShell is unavoidable.
Review all examples and ensure that none assume a Windows environment by default; offer parity for Linux/macOS users throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias. In the section on running the Kafka producer, it specifically references 'On a Windows machine, when using a Node.js command prompt...' and does not provide equivalent instructions or notes for Linux or macOS users. The mention of 'Node.js command prompt' is a Windows-specific tool, and there are no Linux/macOS terminal instructions or clarifications. No PowerShell commands are present, but the guidance assumes a Windows environment for command execution.

Recommendations:

Provide explicit instructions or notes for Linux and macOS users alongside Windows instructions, especially for running Maven commands.
Replace or supplement references to 'Node.js command prompt' with generic terminal/command-line instructions applicable to all platforms.
Add a note clarifying that the provided shell commands (mvn clean package, mvn exec:java) work in any terminal (Windows Command Prompt, PowerShell, Linux/macOS Terminal, etc.).
If there are any platform-specific steps (e.g., setting environment variables, path separators), document them for each OS.
Review the documentation for any other implicit Windows assumptions and ensure parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for upgrading circuit bandwidth, and mentioning it before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify that Azure CLI is cross-platform or provide Bash/Linux shell examples.

Recommendations:

Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Provide example commands for both PowerShell and Bash (using Azure CLI) to ensure Linux users are equally supported.
List Azure CLI before PowerShell to avoid the impression that Windows tools are preferred.
Add a note or section highlighting Linux/macOS compatibility and any OS-specific considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for gateway subnet creation, referencing PowerShell and REST API resources exclusively, and omitting any Azure CLI (cross-platform) or Linux-native command examples. The focus on PowerShell cmdlets and lack of parity with CLI or Bash scripting may disadvantage Linux and macOS users.

Recommendations:

Add Azure CLI examples alongside PowerShell for all command-line operations, especially for gateway subnet creation.
Include references and links to Azure CLI documentation and syntax in the 'REST APIs and PowerShell cmdlets' section.
Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
Where possible, provide Bash script equivalents for common tasks.
Reorder examples or provide both PowerShell and CLI examples together, rather than PowerShell only or first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. References to OS disks and temporary disks use Windows drive letters (C: and D:) exclusively, with no mention of Linux equivalents (such as / or /mnt). There are no Linux-specific examples or terminology, and the documentation assumes familiarity with Windows disk conventions. No Linux or cross-platform command-line examples are provided, and the only references to file systems or data locations are Windows-centric.

Recommendations:

When referring to OS and temporary disks, include Linux equivalents (e.g., 'C: drive on Windows or / on Linux').
Add notes or examples for Linux users where disk paths or conventions differ.
Ensure that any screenshots or instructions that are OS-specific are paired with Linux alternatives, or clarify when steps are OS-agnostic.
Where possible, use neutral terminology (e.g., 'OS disk' and 'temporary disk') and provide both Windows and Linux context.
If there are command-line or scripting examples, provide both PowerShell (Windows) and Bash (Linux) versions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Portal. However, there is a notable bias toward Windows environments: PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows-centric tool (even though cross-platform PowerShell Core exists, most users associate it with Windows). In several places, PowerShell examples are presented immediately after CLI, and there is no mention of Linux-specific shell usage, scripting, or troubleshooting. The document does not clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS, nor does it provide any bash/zsh-specific guidance or highlight differences that Linux users might encounter. There are also no references to Linux-native tools or patterns.

Recommendations:

Explicitly state that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
Add bash/zsh shell examples or notes where relevant (e.g., multi-line commands, environment variable usage, quoting).
Clarify that PowerShell examples are optional and primarily for users on Windows or those using PowerShell Core.
Add troubleshooting notes for common Linux issues (e.g., line endings, path formats, CLI installation).
Where scripting is shown, provide both PowerShell and bash script snippets to ensure Linux users are equally supported.
Consider reordering tabs so that Azure CLI (the most cross-platform tool) appears first, and PowerShell is clearly marked as an alternative.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is heavily biased towards Windows and PowerShell usage. All step-by-step examples and code blocks use Azure PowerShell exclusively, with no equivalent Azure CLI (cross-platform) or Bash examples provided inline. The instructions and workflow assume the use of PowerShell, which is traditionally associated with Windows, and there is no mention of Linux or macOS-specific guidance. While links to Azure CLI and REST API deployment methods are provided, they are secondary and not integrated into the main instructional flow.

Recommendations:

Provide parallel Azure CLI (az) examples alongside PowerShell scripts for all deployment and deletion steps.
Include explicit instructions or code blocks for Bash/shell environments to ensure Linux and macOS users are equally supported.
Reorganize the documentation to present both PowerShell and CLI methods equally, or allow users to select their preferred environment at the top of the page.
Clarify that Azure Cloud Shell supports both PowerShell and Bash, and show how to choose between them.
Avoid language that assumes the user is on Windows or using PowerShell by default; instead, use neutral, cross-platform phrasing.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and the Azure portal. However, the inclusion of Azure PowerShell throughout, with detailed PowerShell command examples, introduces a Windows bias. PowerShell is primarily a Windows-native tool, and its prominence may disadvantage Linux users who are less likely to use PowerShell. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native scripting or tooling. The CLI examples are cross-platform, but the documentation does not clarify this or provide Linux-specific guidance. The PowerShell sections are always present and sometimes precede the CLI sections, reinforcing the Windows-centric approach.

Recommendations:

Clarify that Azure CLI commands are fully cross-platform and provide explicit Bash or Linux terminal examples where appropriate.
De-emphasize PowerShell as a primary automation tool unless specifically targeting Windows users; consider moving PowerShell sections after CLI sections or marking them as Windows-specific.
Add notes or callouts for Linux/macOS users, such as any differences in CLI usage, environment setup, or authentication.
If scripting examples are provided, include Bash scripts or references to shell scripting for Linux users.
Review the order of sections to ensure CLI (cross-platform) instructions come before PowerShell (Windows-centric) instructions.
Explicitly state that PowerShell examples are optional and primarily for users on Windows or those who have installed PowerShell Core on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All instructions for project setup, package installation, and tooling reference Visual Studio 2022 and its GUI, with no mention of cross-platform alternatives like Visual Studio Code or command-line workflows. NuGet package installation is shown exclusively via the Visual Studio Package Manager Console (PowerShell), with no dotnet CLI examples. There are no Linux/macOS-specific instructions or screenshots, and the workflow assumes a Windows development environment throughout.

Recommendations:

Add instructions for creating and managing .NET projects using the dotnet CLI, which is cross-platform.
Provide NuGet package installation commands using 'dotnet add package' alongside or instead of PowerShell/Package Manager Console examples.
Mention and provide guidance for using Visual Studio Code or JetBrains Rider as alternative IDEs, especially for Linux/macOS users.
Include notes or sections that clarify the steps are applicable on Linux/macOS, and highlight any OS-specific differences.
Replace or supplement screenshots of Visual Studio with equivalent command-line instructions or screenshots from cross-platform editors.
Explicitly state that the quickstart is cross-platform and provide parity in instructions for all supported operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell scripts and automation for Windows, referencing Windows-specific tools (such as Control Panel and Windows Firewall), and presenting Windows procedures and scripts before or more prominently than Linux equivalents. Linux instructions are present but are less automated, require manual steps, and are less detailed. There are also references to Windows-specific verification steps without Linux parity.

Recommendations:

Provide equivalent automated scripts for Linux (e.g., a bash script to open firewall ports and configure the agent, similar to the provided PowerShell script for Windows).
Include Linux verification steps (such as commands to check agent status and connectivity) alongside the Windows Control Panel instructions.
Present Windows and Linux instructions in parallel or in clearly separated, equally detailed sections to avoid the perception of Windows-first bias.
Reference Linux tools and configuration files with the same level of detail as Windows tools (e.g., mention systemd, firewalld/iptables, and log file locations for Linux).
Where possible, provide cross-platform CLI examples (such as using Azure CLI) instead of only PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell (Windows-centric) example for cleaning up resources, with no equivalent Bash, Azure CLI, or Linux-native instructions. The use of the Remove-AzResourceGroup cmdlet assumes a Windows or PowerShell environment, and there are no Linux or cross-platform alternatives presented. The rest of the quickstart relies on the Azure Portal, which is platform-agnostic, but the only command-line example is Windows-focused.

Recommendations:

Add equivalent Azure CLI (az group delete) and Bash examples for deleting the resource group, ensuring Linux and macOS users are supported.
Wherever PowerShell cmdlets are shown, provide parallel instructions for Azure CLI and Bash.
Explicitly mention that the Azure Portal steps are platform-agnostic, but provide command-line options for all major platforms.
Review other sections for any implicit Windows tool references and ensure parity with Linux-native tools and workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. It explicitly requires a Windows 10 or 11 PC as a prerequisite, provides only Windows-specific setup scripts (*.bat files), and references Windows tools (such as Termite and File Explorer) without offering Linux alternatives. Instructions for tasks like flashing the device, running setup scripts, and monitoring serial output are all tailored to Windows, with no mention of Linux or cross-platform equivalents. While the Azure CLI is cross-platform, the overall workflow and tooling assume a Windows environment.

Recommendations:

Add explicit support and instructions for Linux (and macOS) users, including prerequisites and alternative tools.
Provide Linux-compatible setup scripts (e.g., get-toolchain.sh) and update instructions to reference them.
Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) alongside or instead of Termite.
Replace or supplement File Explorer instructions with command-line equivalents (e.g., cp command) for Linux/macOS.
Clarify which steps are Windows-specific and provide parallel steps for Linux/macOS where applicable.
Test the workflow on Linux and document any differences or additional requirements.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for command-line migration and subnet management tasks, with no mention of Azure CLI or Bash/Linux alternatives. All automation and scripting guidance is provided only via PowerShell, which is traditionally associated with Windows environments. There are no examples or instructions for Linux users or those preferring cross-platform tools.

Recommendations:

Provide Azure CLI (az) command examples alongside PowerShell for all migration and subnet management tasks.
Explicitly mention that PowerShell can be used on Linux/macOS, or clarify if any steps are Windows-only.
Include Bash or shell script equivalents where appropriate, or link to cross-platform documentation.
Reorder guidance so that cross-platform tools (Azure CLI) are mentioned before or alongside PowerShell.
Add a section or note for Linux/macOS users, outlining supported tools and any differences in procedure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides parity between Azure CLI and Azure PowerShell for most operations, but consistently lists and demonstrates PowerShell (a Windows-centric tool) before CLI, and includes detailed PowerShell scripting examples. There are no Linux-specific shell (e.g., Bash) or scripting examples, and no mention of Linux-native tools or workflows. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for Linux environments.

Recommendations:

Alternate the order of CLI and PowerShell examples, or list CLI (which is cross-platform) first to avoid implicit Windows prioritization.
Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
Add a note or section for Linux users, highlighting any differences or tips for running these commands in Linux environments.
Where PowerShell scripting is shown, consider providing equivalent Bash scripting examples for Linux users.
Avoid assuming PowerShell as the default scripting environment; clarify that both CLI and PowerShell are supported and cross-platform where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only a PowerShell script for deploying Arc-enabled ContainerApps in an Extended Zone, with no equivalent Bash or Linux shell example. The script uses Windows/PowerShell-specific syntax (e.g., backticks for line continuation, Start-Sleep, Write-Debug, Write-Error, and Windows-style paths), and the instructions assume the user is running PowerShell. There is no mention of Linux or cross-platform alternatives, and no guidance for users on macOS or Linux.

Recommendations:

Provide a Bash (Linux/macOS) equivalent script for all deployment steps, using POSIX-compliant shell syntax.
Explicitly state that the provided script is for PowerShell/Windows, and offer a parallel section for Linux/macOS users.
Avoid Windows-specific path syntax (e.g., .\DemoApp) or provide both Windows and Unix-style path examples.
Use cross-platform Azure CLI commands in the main documentation body, and only supplement with OS-specific scripting where necessary.
Add a note in the prerequisites about supported operating systems and shell environments.
Where possible, use code blocks that are OS-agnostic, or provide tabs/switchers for PowerShell and Bash.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by providing all command-line and scripting examples in PowerShell syntax, including the main automation function and even simple Azure CLI invocations. There are no Bash or Linux shell equivalents, and the scripting patterns (e.g., function definition, parameter handling) are tailored to PowerShell users. This may disadvantage Linux or macOS users, who are likely to use Bash or other Unix shells.

Recommendations:

Provide all Azure CLI examples in both PowerShell and Bash syntax, especially for multi-step scripts and automation functions.
Include a Bash script or step-by-step Bash command sequence for creating and connecting the AKS cluster, using standard Bash idioms (e.g., environment variables, shell functions).
When showing Azure CLI commands, use the generic CLI syntax (which is cross-platform) and avoid wrapping them in PowerShell-specific constructs unless necessary.
Explicitly mention that the steps are cross-platform and clarify any OS-specific prerequisites or differences.
For resource cleanup, show both PowerShell and Bash command examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias. Examples and explanations for features such as automatic disconnect on idle are provided only for Windows virtual machines, with explicit notes that certain settings are Windows-only. The documentation references the Windows OS definition of idle, but does not provide equivalent Linux details or links. The 'Next steps' section highlights PowerShell as the primary scripting tool for managing lab accounts, with no mention of CLI or Bash alternatives. Linux support is mentioned only as a caveat or limitation, and Linux-specific instructions or examples are missing.

Recommendations:

Provide Linux-specific examples and instructions where features are supported (e.g., how idle detection or shutdown works on Linux VMs).
Include parity in tooling recommendations, such as Azure CLI or Bash scripts, alongside PowerShell for managing lab accounts.
Where features are Windows-only, offer clear explanations or workarounds for Linux users, and link to relevant Linux documentation.
List Linux and Windows support side-by-side in feature tables or callouts, rather than mentioning Linux only as a limitation.
Ensure screenshots and examples include both Windows and Linux scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by presenting Windows validation steps and tools (such as NVIDIA Control Panel and Task Manager) in detail, while Linux instructions are referenced only via external links without in-page examples or screenshots. Windows instructions and tools are described first and more thoroughly, with Linux relegated to brief mentions or links.

Recommendations:

Provide in-page, step-by-step Linux examples for driver installation and validation, including relevant commands (e.g., nvidia-smi, lspci) and screenshots.
Present Windows and Linux instructions in parallel sections, giving equal prominence and detail to both platforms.
Avoid describing Windows tools (e.g., Control Panel, Task Manager) exclusively; include Linux equivalents (e.g., nvidia-settings, htop, or system monitoring commands).
When referencing external links for Linux, summarize the key steps or commands directly in the documentation for parity with Windows instructions.
Ensure that all screenshots and UI walkthroughs are balanced between Windows and Linux where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively demonstrates deploying a Windows Server VM, with instructions and screenshots focused on RDP (Remote Desktop Protocol) for Windows-based access. There are no examples or guidance for deploying a Linux VM, nor are SSH or Linux-specific access methods mentioned. The use of RDP and Windows Server as the default image and connection method demonstrates a Windows-first and Windows-tools bias, with Linux scenarios entirely omitted.

Recommendations:

Add parallel instructions for deploying a Linux VM (e.g., Ubuntu or CentOS) in the Azure Extended Zone, including selection of a Linux image in the 'Image' step.
Include guidance and screenshots for configuring SSH access (port 22) for Linux VMs, alongside or instead of RDP.
In the 'Connect to virtual machine' section, provide steps for connecting via SSH from Linux, macOS, and Windows clients (e.g., using ssh command-line tools or PuTTY).
Where possible, present both Windows and Linux options side-by-side, or clarify that the instructions are specific to Windows and link to Linux equivalents.
Update caution and security notes to reference best practices for both RDP and SSH access.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists Azure PowerShell cmdlets prominently in a dedicated section, without providing equivalent Azure CLI or REST API examples or references. This creates a bias towards Windows/PowerShell users, as PowerShell is most commonly associated with Windows environments. While the text mentions that IP Groups can be managed via the Azure portal, Azure CLI, or REST API, only PowerShell commands are explicitly documented, and no Linux-friendly command-line examples are provided.

Recommendations:

Add a dedicated section listing equivalent Azure CLI commands for managing IP Groups, similar to the PowerShell cmdlets section.
Provide REST API example calls for creating, updating, and deleting IP Groups.
Ensure that CLI and REST API references are as detailed and prominent as the PowerShell section.
Where possible, present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line deployment instructions and examples are provided exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The workflow assumes use of PowerShell and references Windows-specific cmdlets and output. While there is a brief mention that Azure CLI and REST API are also available, no examples or guidance are given for Linux/macOS users or for cross-platform command-line tools.

Recommendations:

Add equivalent Azure CLI (az) examples for all deployment and cleanup steps, ideally in Bash syntax.
Present both PowerShell and CLI/Bash examples side by side, or allow the user to toggle between them.
Avoid using only PowerShell-specific cmdlets and terminology; reference cross-platform tools equally or first.
Include screenshots or output examples from both PowerShell and CLI where relevant.
Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias: it only deploys Windows Server VMs for testing, instructs users to use Remote Desktop and Internet Explorer, and provides only PowerShell (Windows-centric) commands for resource cleanup. There are no Linux VM deployment or validation instructions, nor are Linux tools or command-line examples mentioned.

Recommendations:

Include Linux VM deployment in the ARM template or as an alternative option, and provide instructions for connecting to Linux VMs (e.g., using SSH).
Add validation steps for Linux, such as using curl or a browser on a Linux VM to test firewall rules.
Provide Azure CLI or Bash commands for resource cleanup, not just PowerShell.
Mention cross-platform tools and browsers (e.g., Edge, Chrome, Firefox) instead of only Internet Explorer.
Present both Windows and Linux examples side-by-side where relevant, or clarify that the steps are specific to Windows and link to Linux equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows and PowerShell usage. All configuration steps and code samples are provided exclusively using Azure PowerShell cmdlets, with explicit references to installing PowerShell modules and using Windows-style file paths (e.g., 'C:\NetworkConfig.xml'). There are no examples or instructions for performing these tasks using Azure CLI, Bash, or other cross-platform tools. The documentation does not mention or provide parity for Linux or macOS users, nor does it reference alternative tooling or scripting environments.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include notes or sections for Linux/macOS users, such as how to install and use Azure CLI and where to store configuration files (e.g., using '/home/user/NetworkConfig.xml' paths).
Where file paths are referenced, show both Windows and Linux/macOS path formats.
Add a table or selector at the top of the article allowing users to choose between PowerShell and Azure CLI (or Bash) instructions.
Explicitly state that the instructions are applicable on Windows, and provide links or guidance for users on other platforms.
Review all referenced scripts and tools to ensure they are available and supported on non-Windows platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell command examples for all CLI-based verification and troubleshooting steps. There are no equivalent examples using Azure CLI (cross-platform) or Bash scripting. Additionally, the recommended network testing tool is PsPing, which is a Windows-only Sysinternals utility, with no mention of Linux alternatives. No Linux-native commands or tools are referenced, and the documentation does not address how Linux users can perform the same tasks.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside all PowerShell examples to ensure cross-platform usability.
Include Linux-native network testing tools (such as hping3, nping, or standard ping/traceroute) as alternatives to PsPing for connectivity testing.
Explicitly mention that all PowerShell commands can be run in Azure Cloud Shell, which is available on all platforms, but also show Bash/Azure CLI syntax.
Where possible, add troubleshooting steps or command examples that use common Linux networking tools (e.g., ip, ifconfig, arp, route, netstat) for validating ARP, BGP, and routing.
Structure sections so that cross-platform or platform-neutral tools are presented first, or at least in parallel with Windows-specific tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The script uses PowerShell-specific syntax and patterns, which may not be directly usable on Linux or macOS systems. The absence of a Linux/Bash example and the exclusive use of PowerShell suggest a Windows-first approach, potentially making it less accessible for Linux users.

Recommendations:

Provide a Bash (Linux/macOS) equivalent script for all deployment steps, using standard shell syntax and environment variable handling.
Explicitly mention that the steps can be performed on both Windows (PowerShell) and Linux/macOS (Bash), and clarify any platform-specific differences.
Ensure that all az CLI commands are shown in a cross-platform way, avoiding PowerShell-specific constructs (e.g., $ENV:, backticks for line continuation, parameter passing).
Add a section or callout for Linux/macOS users, highlighting any required tools or differences in environment setup.
Consider making Bash the default example or presenting both PowerShell and Bash examples side by side for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the example workload VM, referencing RDP (port 3389) for connectivity testing, and omitting any Linux-based VM or SSH-based test scenario. No Linux equivalents or instructions are provided, and Windows is presented as the default/only platform for deployment and validation.

Recommendations:

Include parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
Provide examples for configuring DNAT rules for SSH (port 22) access to a Linux VM, alongside the RDP/Windows example.
In the 'Test the firewall' section, add steps for connecting via SSH to a Linux VM using the firewall's public IP address.
Present both Windows and Linux options side-by-side or in separate sections, ensuring neither is prioritized over the other.
Mention Linux tools (e.g., SSH clients) and patterns where relevant, not just Windows/Remote Desktop.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell example (Remove-AzResourceGroup) for cleaning up resources, with no equivalent command for Linux users (such as Azure CLI or Bash). Additionally, the firewall policy example specifically references Windows Update using the WindowsUpdate FQDN tag, and there are no Linux-specific or cross-platform examples or guidance provided.

Recommendations:

Include Azure CLI (az group delete) and/or Bash examples alongside PowerShell for resource cleanup, to support Linux and macOS users.
When referencing firewall rules, provide examples for both Windows-specific (e.g., Windows Update) and common Linux update endpoints (e.g., Ubuntu, Red Hat repositories) to ensure parity.
Review all command-line instructions and ensure both Windows (PowerShell) and Linux (CLI/Bash) equivalents are presented.
Consider adding a note or section on how to perform all steps using cross-platform tools, not just those available on Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux (K3S/Ubuntu) and Windows (AKS Edge Essentials/Windows 11) setup paths, but there are notable biases. PowerShell syntax is used for environment variable setup and Azure CLI commands even in the Linux/K3S section, which is non-idiomatic for Linux users. Windows-specific tools and commands (e.g., netsh portproxy) are described in detail, while equivalent Linux networking steps (such as iptables or firewall-cmd) are not provided. In several places, Windows instructions are more explicit or appear first. There is also a lack of parity in post-deployment networking configuration for Linux clusters.

Recommendations:

Provide Bash syntax for all Azure CLI and environment variable setup steps in the K3S/Linux sections, instead of PowerShell.
Include Linux-native networking configuration instructions (e.g., iptables, firewall-cmd) for exposing Kubernetes LoadBalancer services, mirroring the detailed Windows netsh portproxy steps.
Ensure that Linux and Windows instructions are presented with equal detail and in parallel, rather than Windows-first or more thoroughly.
Add troubleshooting and verification steps for Linux environments where they exist for Windows.
Review all command examples to ensure they are idiomatic for the target OS (e.g., avoid PowerShell on Linux).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows by exclusively using PowerShell cmdlets for all configuration, management, and viewing tasks. There are no examples or instructions for Linux users, such as Azure CLI or Bash equivalents. The only tooling mentioned is PowerShell, which is traditionally a Windows-centric tool, though it is now cross-platform. No Linux-native patterns or commands are provided.

Recommendations:

Add equivalent Azure CLI (az) command examples for each PowerShell cmdlet shown, as Azure CLI is cross-platform and commonly used on Linux.
Include a section or callout for Linux/macOS users, clarifying how to perform these tasks without PowerShell.
Where possible, provide Bash script examples or references to REST API usage for advanced users.
Reorganize the documentation to present both PowerShell and Azure CLI options side-by-side, or allow users to select their preferred platform at the top of the article.
Explicitly state that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions for those platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides configuration examples only for the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric, and there are no explicit Linux shell (bash) or automation examples. The PowerShell tab is always present, and the documentation metadata includes 'devx-track-azurepowershell', suggesting a Windows/PowerShell bias. There are no Linux-specific instructions or references to Linux-native tools or scripting, and no mention of Linux-specific considerations for DNS or network configuration.

Recommendations:

Add explicit bash/shell script examples for Linux users alongside PowerShell, especially for scripting and automation tasks.
Clarify that Azure CLI commands are cross-platform and provide any Linux-specific notes if needed (e.g., differences in environment variables, quoting, or file paths).
Include troubleshooting or configuration notes relevant to Linux VMs (e.g., how to update /etc/resolv.conf or use cloud-init for DNS settings).
Balance the prominence of PowerShell and CLI examples, and consider renaming tabs to 'Shell (Linux/macOS)' and 'PowerShell (Windows)' for clarity.
Review metadata and custom tags to ensure they do not signal a Windows/PowerShell preference unless justified.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example environment, mentioning only Windows VMs (jump box and server) and omitting Linux VM options. Additionally, the only command-line example for resource cleanup uses PowerShell (`Remove-AzResourceGroup`), with no equivalent Bash/Azure CLI example provided. No Linux tools, patterns, or examples are mentioned.

Recommendations:

Include examples that deploy both Windows and Linux virtual machines, or provide an option to select the OS type in the template or instructions.
When providing command-line instructions (such as for resource cleanup), include both PowerShell and Bash/Azure CLI equivalents.
Mention Linux as a supported platform for jump box/server VMs, and provide guidance or links for deploying and managing Linux VMs in Azure.
Ensure that any references to tools or scripts (e.g., PowerShell) are accompanied by cross-platform alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows by exclusively referencing Windows VM images in the code example, omitting Linux alternatives. Additionally, the 'Next steps' section only mentions Azure PowerShell and Az.LabServices cmdlets, which are traditionally Windows-centric tools, without referencing cross-platform or Linux-native tools. There are no Linux VM image examples or mentions of Linux-specific access methods (e.g., SSH), and the RDP (Windows) access is enabled by default in the sample.

Recommendations:

Include examples that use Linux VM images (e.g., Ubuntu, CentOS) in addition to or instead of only Windows images.
Demonstrate both RDP (for Windows) and SSH (for Linux) connection profiles in the sample code.
In the 'Next steps' section, add references to cross-platform tools such as Azure CLI and Bash scripting, and provide links to relevant documentation.
Explicitly mention that the Python SDK and code samples are cross-platform and can be run on Linux, macOS, and Windows.
If possible, provide guidance or examples for setting up labs with Linux VMs and managing them using Linux-native tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There are no Linux shell-specific examples (e.g., Bash scripts), and PowerShell is referenced as a primary automation tool, which may bias the documentation toward Windows users. The use of 'devx-track-azurepowershell' in metadata and the explicit PowerShell tabs reinforce this bias. No Linux-specific tools or guidance are provided.

Recommendations:

Add Bash shell script examples alongside PowerShell, especially for common Linux automation scenarios.
Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide explicit Bash usage examples where appropriate.
Include references to Linux-native tools (such as curl, dig, or resolvectl) for DNS troubleshooting or verification.
Ensure that PowerShell is not presented as the default or primary automation tool; instead, present CLI and Bash examples first or in parallel.
Review metadata and custom tags to ensure they do not overemphasize PowerShell or Windows-specific tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux (Ubuntu/K3S) and Windows (AKS Edge Essentials) setup instructions, but there is a noticeable Windows bias in several areas. Powershell and Windows-specific tools and commands are used exclusively or given first in key sections (e.g., Arc-enabling the cluster, network/firewall configuration). Some steps, such as environment variable setup and Azure CLI usage, are only shown in Powershell syntax, with no Bash/Linux equivalents. Windows UI steps for DNS configuration are detailed, while the Linux (Ubuntu) DNS configuration is only briefly described and relies on the UI, not CLI. The network configuration and troubleshooting steps are Windows-centric, and some advanced configuration (firewall, port forwarding) is only shown for Windows.

Recommendations:

Provide Bash/Linux equivalents for all Powershell commands, especially for Azure CLI usage, environment variable setup, and Arc-enabling the cluster.
Include Linux CLI-based instructions for DNS configuration (e.g., using nmcli or editing /etc/netplan or /etc/resolv.conf), not just Ubuntu UI steps.
Offer Linux-native alternatives for Windows-only tools and commands (e.g., netsh, New-NetFirewallRule), such as iptables or ufw for firewall rules and socat or iptables for port forwarding.
Ensure that troubleshooting and verification steps (e.g., checking service IPs, verifying DNS) are shown with Linux commands as well as Windows.
Present both Linux and Windows instructions in parallel or in clearly separated tabs, rather than defaulting to Windows-first or Windows-only examples in shared sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, emphasizing PowerShell (a Windows-centric tool), and omitting any Linux-specific guidance or examples. The Azure portal and PowerShell are highlighted as primary configuration methods, with no mention of Linux shell scripting, Bash, or cross-platform automation patterns. The CLI section is present, but only after PowerShell, and there is no discussion of Linux-specific considerations or troubleshooting.

Recommendations:

Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any relevant Linux-specific notes (e.g., shell syntax, environment variables).
Include Bash scripting examples for automation, or reference how to use these commands in Linux shell scripts.
If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, but also highlight that Azure CLI is the preferred tool for Linux environments.
Add troubleshooting tips or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, handling authentication).
Avoid phrasing that implies PowerShell is the default or primary automation tool for all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing heavily on Windows-related FQDN tags (e.g., WindowsUpdate, WindowsDiagnostics, WindowsVirtualDesktop, Windows365, citrixHdxPlusForWindows365) and providing examples and descriptions that are almost exclusively centered on Windows or Microsoft-specific services. There are no Linux-specific examples, tags, or references to non-Windows environments, and the documentation does not mention how FQDN tags might be used for Linux-based services or scenarios.

Recommendations:

Include examples or references for Linux-based services that might benefit from FQDN tags, such as popular Linux distributions' update servers or open-source cloud services.
Add FQDN tags or documentation for non-Windows Microsoft services (e.g., Azure Linux VM management endpoints, Azure Container Instances, etc.).
Provide parity in documentation by mentioning both Windows and Linux scenarios where relevant, or clarify if FQDN tags are only applicable to Microsoft/Windows services.
If possible, add a note explaining the scope of FQDN tags and whether support for Linux/open-source services is planned or available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for Azure-side configuration and validation, referencing the Azure portal (which is platform-agnostic but often used in Windows contexts), and omitting Azure CLI (cross-platform) or Bash examples. All device configuration examples are for Cisco IOS/CSR, with no Linux-based VPN device (e.g., strongSwan, libreswan) configuration or validation commands. The workflow and validation steps consistently present PowerShell commands first or exclusively, with no parity for Linux administrators.

Recommendations:

Add Azure CLI (az) command examples alongside all Azure PowerShell commands for resource creation, configuration, and validation.
Include Linux-based VPN device configuration examples (e.g., strongSwan, libreswan) in addition to Cisco IOS/CSR examples, especially for on-premises device setup and tunnel validation.
When referencing the Azure portal, clarify its cross-platform nature and provide CLI alternatives where possible.
Present both PowerShell and CLI/Bash commands in parallel, or at least link to equivalent Linux/CLI documentation.
Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI, and provide references or links to those instructions.
Add validation and troubleshooting steps using Linux-native tools (e.g., ipsec status, journalctl, tcpdump) for tunnel and BGP session checks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but PowerShell is consistently presented as a primary or parallel option. There is an implicit Windows bias through the frequent mention and use of PowerShell, which is traditionally a Windows-centric tool, and through references to 'adminUsername' and 'adminPassword' patterns that are more common in Windows environments. There are no explicit Linux-specific instructions, notes, or examples, and the documentation does not address Linux shell environments or tools beyond the generic Azure CLI.

Recommendations:

Add explicit Linux shell (bash) examples or notes, especially for steps involving file paths or command syntax that may differ between Windows and Linux.
Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific guidance (e.g., file permissions, path separators).
When referencing PowerShell, note its availability on Linux, or provide bash equivalents for common tasks.
Include Linux-specific troubleshooting tips or caveats, if any, for deploying Bicep or ARM templates.
Avoid using only Windows-centric terminology (e.g., 'adminUsername', 'adminPassword') or clarify that these apply to both Windows and Linux VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Azure PowerShell as a configuration method for certain features (e.g., associating public IP addresses in secured hubs) without mentioning Azure CLI or providing Linux/Unix-specific instructions. There are no Linux-specific tools or examples, and the only command-line tool referenced is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Include Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and commonly used on Linux.
Explicitly mention that both Azure PowerShell and Azure CLI can be used for configuration, and provide links or examples for both.
Where possible, avoid referencing only Windows-centric tools (like PowerShell) and ensure parity by including Linux-friendly alternatives.
Add a note clarifying that all features can be managed from Linux, macOS, and Windows using the Azure CLI, and provide relevant documentation links.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI or ARM template instructions. There are no explicit Linux shell or cross-platform examples, and the PowerShell workflow is described in more detail, including update steps, while the CLI and ARM template sections are brief. The focus on PowerShell as the primary example and lack of Linux-native command-line (e.g., Bash) or cross-platform scripting guidance may disadvantage Linux users.

Recommendations:

Provide equivalent Bash/Azure CLI examples for all operations, including updating an existing Azure Firewall (not just deployment).
Ensure that Azure CLI instructions are as detailed as the PowerShell ones, including update scenarios.
Present CLI and ARM template examples before or alongside PowerShell to avoid the perception of Windows-first bias.
Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample shell commands.
Where possible, include screenshots or code blocks that demonstrate the use of CLI in a Linux shell environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server for all virtual machine examples, providing only PowerShell commands for configuration (specifically for IIS installation), and omitting any Linux-based examples or CLI alternatives. The workflow assumes Windows administrative patterns and tools, such as RDP and PowerShell, without mentioning or providing parity for Linux users (e.g., SSH, Bash, Linux VMs, or Azure CLI).

Recommendations:

Provide parallel instructions for deploying and configuring Linux-based virtual machines (e.g., Ubuntu Server) in both the spoke and on-premises roles.
Include Azure CLI and/or Bash script examples for tasks such as installing web servers (e.g., using apt to install nginx or apache2) in addition to the PowerShell/IIS example.
Demonstrate how to connect to Linux VMs using SSH, and how to test connectivity (e.g., using curl or wget) instead of only RDP and browser-based testing.
When referencing remote desktop access, mention alternatives for Linux (e.g., SSH, xrdp, or other remote access tools).
Ensure that all code snippets and configuration steps have both Windows and Linux equivalents, and present them side-by-side or with clear toggles.
Avoid assuming the administrator is using Windows or PowerShell by default; introduce both Windows and Linux options at the start of the tutorial.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes creating and connecting to a Windows-based lab VM, with all examples and instructions focused on Windows (e.g., selecting 'Windows 11 Pro' as the image, connecting via Remote Desktop). There is no mention of Linux-based lab options, nor are there instructions or examples for connecting to Linux VMs (e.g., via SSH). Windows tools and workflows (RDP) are assumed throughout, with no Linux equivalents provided.

Recommendations:

Include parallel instructions for creating a Linux-based lab VM, such as selecting an Ubuntu or other Linux image during lab creation.
Provide examples and screenshots for connecting to Linux VMs, including SSH connection steps for Windows, macOS, and Linux clients.
Mention and explain Linux-compatible remote access tools (e.g., SSH, xrdp, or web-based terminals) alongside RDP.
Clarify in the introduction that Azure Lab Services supports both Windows and Linux labs, and provide links to Linux-specific documentation if available.
Ensure troubleshooting and cleanup sections address Linux-specific scenarios as well.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., C:\WindowsAzure), tools (System Restore), and disk drive letters (C:, D:) without providing Linux equivalents or examples. Troubleshooting steps and data storage recommendations are oriented toward Windows environments, and Linux-specific guidance is absent.

Recommendations:

Add parallel Linux examples for troubleshooting steps, such as referencing Linux file paths (e.g., /var/log, /etc), and commands for checking disk space or resetting passwords.
When mentioning Windows System Restore, provide Linux alternatives (e.g., using Timeshift, rsnapshot, or manual restoration from backups).
Clarify disk references by explaining Linux equivalents (e.g., /dev/sda1 for OS disk, /mnt for temporary storage) instead of only using Windows drive letters.
Include guidance for storing user data outside the VM using cross-platform solutions (e.g., Azure Files, NFS, or cloud storage options compatible with Linux).
Ensure that all troubleshooting scenarios and resolutions address both Windows and Linux lab VMs equally, with step-by-step instructions for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The tutorial exclusively demonstrates deploying and testing Azure Firewall DNAT using a Windows Server virtual machine and Remote Desktop (RDP) for connectivity testing. There are no examples or instructions for deploying a Linux VM, nor for testing connectivity using SSH or Linux-native tools. The only operating system mentioned for the workload VM is Windows, and the only connectivity test described is via RDP, a Windows-specific protocol.

Recommendations:

Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
Include steps for testing DNAT access using SSH (port 22) to a Linux VM, alongside or instead of RDP.
Provide example NAT rules for both RDP (Windows) and SSH (Linux) scenarios.
When listing OS options for the VM, mention both Windows and Linux images, and show how to select either in the portal.
Generalize connectivity testing steps to cover both Windows (RDP) and Linux (SSH) use cases, ensuring parity.
Where possible, avoid assuming the administrator is using Windows, and provide cross-platform guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, using Windows-centric tooling (Azure PowerShell), and providing a Windows Server image in the PowerShell VM creation example. While CLI examples are present and include a Linux (Ubuntu) image, the PowerShell section is more comprehensive and implicitly assumes a Windows environment, especially for VM provisioning.

Recommendations:

Provide both PowerShell and CLI examples in parallel for each step, ensuring parity in detail and coverage.
In PowerShell VM creation examples, include both Windows and Linux image options, or use a neutral example.
Explicitly mention that Azure PowerShell can be used cross-platform, or provide Bash/Cloud Shell alternatives where possible.
Avoid defaulting to Windows Server images in examples; alternate or provide both Windows and Linux image options.
Consider starting with CLI examples or alternating the order to avoid 'windows_first' bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for enabling and disabling diagnostic logs (Top flows and Flow trace), with no equivalent examples for Linux-native tools or Azure CLI. All command-line instructions use PowerShell cmdlets, which are most familiar and accessible to Windows users. There is no mention of Bash, Azure CLI, or cross-platform scripting, and the documentation assumes the use of PowerShell and Windows-centric workflows.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the operations can be performed using Azure CLI, ARM templates, or the Azure Portal, and provide links or references.
Where possible, provide Bash shell examples or note any differences in command syntax for Linux users.
Clarify that PowerShell can be used on Linux and macOS, but highlight Azure CLI as the preferred cross-platform tool.
Ensure that screenshots and navigation instructions are not specific to Windows-only tools or interfaces.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell and CLI for migration tasks, mentioning PowerShell before CLI, and providing a 'Next steps' link specifically for PowerShell-based migration. There are no Linux-specific examples, nor are there instructions or examples for Bash or Linux-native tooling. The documentation assumes familiarity with PowerShell and Windows-centric workflows, with no parity for Linux users.

Recommendations:

Add explicit Linux/Bash/terminal examples for migration tasks, especially where PowerShell is referenced.
In 'Next steps', provide parallel guides for Linux users (e.g., 'How to migrate using Azure CLI on Linux').
When listing tools or automation options, mention Azure CLI and Terraform before or alongside PowerShell, and clarify that all tools are cross-platform.
Include sample CLI commands (az front-door ...) for common migration actions, not just PowerShell scripts.
Review all references to scripting and automation to ensure Linux users are equally supported and not implicitly deprioritized.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively recommending and linking to PowerShell scripts for automation, with no mention of Azure CLI, Bash, or Linux-based automation alternatives. The term 'PowerShell' is used as the default and only automation method, and there are no Linux/Unix command examples or references to cross-platform tooling. Manual steps reference the Azure Portal, which is cross-platform, but all scripting guidance is Windows-centric.

Recommendations:

Provide equivalent Azure CLI scripts for all PowerShell automation examples, and link to them alongside the PowerShell scripts.
Explicitly mention that automation can be performed from Linux, macOS, or Windows using Azure CLI or PowerShell Core.
Add Bash shell examples or guidance for users on Linux/macOS, especially for common migration tasks.
Rephrase recommendations to present both PowerShell and Azure CLI options equally, rather than defaulting to PowerShell.
Include a table or section summarizing automation options by platform (Windows, Linux, macOS) and tool (PowerShell, Azure CLI, Portal).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by explicitly referencing Azure PowerShell as a primary migration method and providing a dedicated link for it, while not mentioning or linking to equivalent Linux-friendly tools such as Azure CLI or Bash scripts. There are no examples or instructions for Linux users, and the ordering of tools consistently places Windows-centric solutions first or exclusively.

Recommendations:

Add migration instructions and dedicated documentation links for Azure CLI, which is cross-platform and widely used on Linux and macOS.
Wherever Azure PowerShell is mentioned, provide equivalent Azure CLI commands or scripts, and link to relevant documentation.
Ensure that references to command-line tools do not assume a Windows environment; mention Bash, shell, or cross-platform options alongside PowerShell.
In the 'Next steps' and migration sections, list both Azure portal, Azure CLI, and Azure PowerShell options, ideally with CLI first or in parallel.
If Terraform is supported for migration, provide explicit examples or links for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (Fiddler, IIS) and configuration steps for troubleshooting file compression. There are no Linux or cross-platform server examples, and the only origin server configuration guidance is for Microsoft IIS, with no mention of Apache, Nginx, or other common Linux-based servers. The troubleshooting steps and tool recommendations are Windows-centric, and Linux alternatives are not provided.

Recommendations:

Include examples and instructions for popular Linux-based web servers such as Apache and Nginx, detailing how to configure compression and handle proxy headers.
Suggest cross-platform tools for inspecting HTTP headers, such as curl, wget, or httpie, alongside Fiddler and browser developer tools.
Provide parity in troubleshooting steps for both Windows and Linux environments, ensuring that users on any platform can follow the guidance.
Mention Linux-specific considerations for compression and proxy headers, such as relevant Apache or Nginx directives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but does not include explicit Linux shell (bash) examples or clarify that the Azure CLI example is cross-platform. PowerShell is a Windows-centric tool, and its example is given equal prominence to the CLI, which may suggest a Windows bias. There is no mention of Linux-specific tools or workflows, nor is it clarified that the CLI example works on Linux/macOS.

Recommendations:

Clarify that the Azure CLI example is cross-platform and works on Linux, macOS, and Windows.
Consider providing a bash shell example or explicitly labeling the CLI example as suitable for Linux/macOS.
If including PowerShell, consider also including a Linux shell (bash/zsh) example for parity.
Avoid giving the impression that PowerShell is required or preferred by placing CLI (cross-platform) examples first.
Add a note or section on how to perform the same operation using the Azure portal, which is platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing Azure CLI and PowerShell documentation together, but consistently mentioning PowerShell (a Windows-centric tool) alongside or before Linux alternatives. The custom metadata also tracks Azure PowerShell and Azure CLI, but does not mention Bash or other Linux-native shells. There are no Linux-specific command-line examples or references to Linux-native tools, and the overall framing assumes familiarity with PowerShell.

Recommendations:

Provide explicit Bash or Linux shell examples and quickstarts alongside PowerShell and Azure CLI.
Mention Linux-native tools and workflows where relevant, not just Windows-centric ones.
Ensure that Linux and cross-platform instructions are given equal prominence and are not always listed after or secondary to PowerShell.
Add metadata and tracking for Bash or Linux shell usage, not just Azure CLI and PowerShell.
Clarify that Azure CLI is cross-platform and provide guidance for Linux users on installation and usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by consistently presenting PowerShell (a Windows-centric tool) instructions before Azure CLI (which is more cross-platform), and by providing detailed guidance on using Azure PowerShell and Cloud Shell. There is no explicit mention of Linux or macOS environments, and the instructions for local installation and usage focus on PowerShell and Azure CLI without clarifying parity or differences for Linux users. The use of PowerShell as the first/default example and the lack of explicit Linux-specific guidance or troubleshooting may make the documentation less approachable for Linux users.

Recommendations:

Alternate the order of PowerShell and Azure CLI tabs, or present Azure CLI first, as it is cross-platform and widely used on Linux.
Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for all platforms.
Include Linux/macOS-specific notes or troubleshooting tips where relevant (e.g., file paths, shell differences, permissions).
Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for common tasks.
Ensure that all examples and instructions are validated on Linux and macOS, and note any platform-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias, particularly in the VM creation and configuration steps. Only Windows Server images are used for the virtual machines, and the IIS installation instructions are exclusively for Windows, using PowerShell commands. There are no examples or guidance for creating or configuring Linux VMs, nor for installing a Linux web server (such as Apache or Nginx). All scripting and administrative steps are Windows-centric, and Linux users are not provided with equivalent instructions.

Recommendations:

Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside the Windows VM steps.
Include Linux-specific examples for installing a web server (e.g., Apache or Nginx) using bash commands.
Show how to connect to Linux VMs via SSH using Bastion, and provide sample commands for updating the web root.
Ensure that both Windows and Linux options are presented equally in tables and step-by-step guides.
Avoid assuming the use of Windows tools (like PowerShell) exclusively; offer bash or shell alternatives where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., PsPing), linking to Windows-centric tuning guides, and providing troubleshooting steps and error messages primarily for RDP (a Windows protocol). There is a lack of Linux/SSH-specific troubleshooting examples, and Windows tools and patterns are mentioned before or instead of their Linux equivalents. Powershell and Windows Server documentation are referenced, but there are no corresponding Linux command-line or SSH troubleshooting steps.

Recommendations:

Include Linux/SSH-specific troubleshooting steps and examples alongside RDP/Windows instructions.
Mention cross-platform tools (e.g., ping, traceroute, nmap) that are available on both Windows and Linux for network diagnostics.
Provide example error messages and resolutions for SSH (Linux) connections, not just RDP (Windows).
Reference Linux documentation (e.g., adjusting SSH client/server settings, checking firewall rules with ufw/iptables, using journalctl or syslog for logs).
When mentioning tools like PsPing, suggest equivalent Linux tools (e.g., hping, nping, or standard ping).
Balance the order of presentation so that Linux and Windows troubleshooting steps are given equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell scripts and instructions for migration tasks, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code samples and tooling references are PowerShell-centric, which is most commonly associated with Windows environments. There are no Linux-specific or cross-platform migration examples, and PowerShell is presented as the default and only automation method.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation instructions for those platforms.
Include Bash script examples or guidance for users who prefer shell scripting on Linux.
Reorder sections or add notes to clarify that all steps can be performed from any OS, not just Windows, and avoid implying PowerShell is the only or primary method.
Where possible, use neutral language such as 'using Azure PowerShell or Azure CLI' instead of only referencing PowerShell.
Add a table or section comparing migration steps using both PowerShell and CLI to improve parity and user choice.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All examples and instructions assume the use of Windows tools (Hyper-V Manager, PowerShell cmdlets), and there is no mention of Linux-based workflows or tools for creating or importing images. The process is described exclusively for Windows images, with no guidance for users coming from Linux or other non-Windows environments.

Recommendations:

Add a parallel section or notes for importing Linux images, including prerequisites and preparation steps specific to Linux distributions.
Provide examples using Linux-native tools (e.g., qemu-img for disk conversion, KVM/VirtualBox for VM management) alongside Hyper-V and PowerShell.
Mention and link to Azure documentation for uploading and preparing Linux VMs/images.
Clarify in the introduction whether the process is Windows-only or provide cross-platform guidance where possible.
Include command-line examples for Linux (bash, az CLI) in addition to or instead of PowerShell.
If Azure Lab Services only supports Windows images, state this explicitly and provide alternatives or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, and there are no CLI, Bash, or Linux-native instructions. Virtual machines are provisioned with Windows Server images only, and IIS (a Windows web server) is installed using Windows-specific commands. The test steps reference Internet Explorer, a Windows-only browser, and there is no mention of Linux VMs, Apache/Nginx, or cross-platform alternatives.

Recommendations:

Provide parallel Azure CLI (az) or Bash examples for all resource creation and management steps.
Include instructions for creating Linux virtual machines (e.g., Ubuntu) in addition to Windows Server VMs.
Demonstrate installation of a Linux web server (such as Apache or Nginx) using cloud-init or custom script extensions for Linux.
In testing steps, reference cross-platform browsers (e.g., Edge, Chrome, Firefox) and avoid Windows-only tools like Internet Explorer.
Clearly indicate at the top that the guide is Windows/PowerShell-specific, and link to equivalent Linux/CLI quickstarts if available.
Where possible, use neutral terminology and tools that work across platforms, or provide both Windows and Linux alternatives side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and PowerShell examples, but PowerShell is mentioned first in the deployment section and is used in the initial deployment instructions. There are no explicit Linux shell (bash) examples or references to Linux-specific environments, and the PowerShell command for resource deletion is incorrectly placed under the CLI tab, which may confuse Linux users. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for running commands in a native Linux shell.

Recommendations:

Ensure that Azure CLI (bash) examples are presented first or at least equally with PowerShell, as CLI is cross-platform and more familiar to Linux users.
Correct the 'Clean up resources' section: the CLI tab contains a PowerShell command. Replace it with the appropriate Azure CLI command (az group delete --name "${projectName}rg").
Explicitly mention that Azure CLI commands can be run in bash on Linux/macOS as well as in Cloud Shell, and clarify that PowerShell is optional.
Add guidance or links for Linux users on how to set up and use Azure CLI in their environment.
Where possible, include bash script examples for automation alongside PowerShell scripts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias: all virtual machine creation steps use Windows Server images by default, and the only example for configuring the backend web server uses PowerShell scripts to install IIS (a Windows-only web server). There are no examples or guidance for deploying Linux VMs, using Bash/SSH, or installing a Linux-based web server like Apache or Nginx. Windows tools and patterns (PowerShell, IIS) are used exclusively, with no mention of Linux equivalents.

Recommendations:

Provide parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu or CentOS) alongside the Windows Server examples.
Include example scripts for installing a web server on Linux VMs (e.g., using Bash to install Apache or Nginx via apt/yum).
Show how to use the Azure portal's Run Command feature with Bash scripts for Linux VMs, not just PowerShell for Windows.
Mention both Windows and Linux options in all relevant steps, including VM image selection and administrator account setup.
Add screenshots or code snippets that reflect both Windows and Linux scenarios.
Clarify in the prerequisites or introduction that the tutorial is applicable to both Windows and Linux, and provide links to Linux-specific documentation if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents. The structure and language prioritize PowerShell, and there is no mention of Linux-specific considerations, shells, or tooling. The use of PowerShell as the primary example and the presence of the 'devx-track-azurepowershell' custom metadata further reinforce the Windows-centric approach.

Recommendations:

Alternate the order of examples so that Azure CLI (cross-platform) instructions are presented first in some sections, or present both equally without prioritizing one.
Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
Add a brief section or note on using Bash or other Linux shells with Azure CLI, including any differences in command syntax or environment setup.
Review metadata and custom tags to ensure they do not reinforce a PowerShell/Windows bias (e.g., avoid 'devx-track-azurepowershell' unless equally tracking CLI).
Where possible, provide guidance or troubleshooting tips for both Windows and Linux users, especially for environment setup and authentication steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for configuring Azure RBAC, with no mention or examples of cross-platform tools such as Azure CLI. The only command-line instructions use PowerShell cmdlets, which are traditionally associated with Windows environments, and there is no guidance for Linux or macOS users. The Azure portal is also mentioned, but command-line automation is only shown via PowerShell.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell is available on all platforms, but clarify that Azure CLI is often the default on Linux.
Reorganize the 'Configure Azure RBAC' section to present Azure CLI and PowerShell examples side by side, or provide a tabbed interface for different platforms.
Include a brief section or note for Linux/macOS users, pointing to relevant setup instructions for Azure CLI.
Ensure that troubleshooting and role assignment/removal instructions are also available using Azure CLI commands.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exclusively demonstrates creating and configuring Windows Server-based virtual machines (using the 'win2019datacenter' image) and uses Windows-specific tools and commands (such as PowerShell and IIS). There are no examples or instructions for deploying or configuring Linux VMs, nor for installing or testing with Linux-based web servers. The instructions for installing IIS use PowerShell commands, and the test steps reference Internet Explorer, further reinforcing a Windows-centric approach.

Recommendations:

Provide parallel examples for creating Linux-based VMs (e.g., using Ubuntu or CentOS images) alongside the Windows examples.
Include instructions for installing a web server on Linux VMs (e.g., using apt to install nginx or Apache) with corresponding az vm extension set commands.
Show how to test the load balancer using Linux tools (e.g., curl or wget) in addition to or instead of Internet Explorer.
Avoid assuming the use of Windows-only tools (such as PowerShell or Internet Explorer) and offer cross-platform alternatives.
Explicitly mention that the process works for both Windows and Linux VMs, and link to relevant documentation for Linux VM management where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently referencing Windows tools (such as Microsoft Azure Storage Explorer), prioritizing Windows in instructions and examples, and providing PowerShell commands without equivalent Linux/bash examples. In several places, the documentation mentions PowerShell before Azure CLI, and in the function app creation section, Windows is selected as the example OS, with in-portal editing only supported on Windows. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-native tools or workflows.

Recommendations:

Provide equivalent bash/Azure CLI examples alongside PowerShell commands wherever PowerShell is mentioned.
Include explicit instructions or screenshots for Linux/macOS users, especially for tools like Azure Storage Explorer and Azure CLI.
When referencing operating systems, avoid defaulting to Windows in examples; instead, show both Windows and Linux options or use neutral language.
Mention cross-platform alternatives to Windows-only features (e.g., in-portal editing limitations) and provide guidance for Linux/macOS users.
Ensure that all prerequisite and setup steps are platform-agnostic or have clear, parallel instructions for Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias in the 'Install web server' section, where users are instructed to open a PowerShell prompt on Windows and a Bash prompt on Mac/Linux, but all SSH command examples use Windows-style paths (e.g., '.\Downloads\myKey.pem') and do not provide a Linux/macOS equivalent. There are no explicit Linux/macOS command examples for SSH, and the documentation assumes familiarity with Windows conventions. Additionally, the order of instructions often lists Windows before Linux/macOS.

Recommendations:

Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) command examples for SSH, with correct path syntax for each platform.
When instructing users to open a terminal, list Linux/macOS first or present both options equally.
Include notes or callouts clarifying path differences (e.g., '.\Downloads\myKey.pem' for Windows, '~/Downloads/myKey.pem' for Linux/macOS).
Wherever possible, avoid assuming a Windows environment; use cross-platform language and examples.
Consider adding screenshots or terminal output examples for both Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it provides Azure Portal, Azure CLI, and Azure PowerShell instructions, several patterns indicate a preference for Windows-centric tools and workflows. PowerShell is given equal prominence to CLI, and Windows-specific technologies (such as IIS) are assumed in testing. There are no explicit Linux-specific examples or references (e.g., Apache/Nginx for backend VMs), and the documentation does not address Linux shell or scripting nuances, despite the CLI examples being generally cross-platform.

Recommendations:

Include explicit Linux examples for backend pool VMs, such as using Apache or Nginx instead of only referencing IIS.
In test instructions, mention both Windows (IIS) and Linux (Apache/Nginx) default web pages to clarify cross-platform applicability.
Add notes or examples for running Azure CLI commands in Bash or other Linux shells, including handling of environment variables and command output.
Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for common scripting patterns.
Review terminology and instructions to ensure they do not assume a Windows environment (e.g., file paths, shell commands, browser defaults).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively using PowerShell commands and scripts for deployment, referencing Windows PowerShell as the default environment, and omitting equivalent Linux shell or bash examples. The only mention of Linux is a tip on how to install PowerShell, rather than providing native Linux instructions. Additionally, Windows-specific tools and patterns (such as .ps1 scripts and Get-AzLocation) are referenced without Linux alternatives.

Recommendations:

Provide equivalent bash or shell command examples for Linux/macOS users alongside PowerShell commands.
Include instructions for running the deployment script using bash (e.g., if a bash script is available, or instructions for using pwsh on Linux).
Mention Linux-native tools or commands where possible (e.g., az CLI for region listing instead of Get-AzLocation PowerShell cmdlet).
Rephrase steps to be platform-neutral where feasible, or clearly separate Windows and Linux/macOS instructions.
If only PowerShell scripts are available, consider providing or linking to bash alternatives, or at least clarify that PowerShell Core (pwsh) is required on all platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by explicitly stating that the Data Mapper tool only works on Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. The prerequisites and workflow steps assume a Windows environment, and there is no mention of alternative approaches or workarounds for non-Windows platforms.

Recommendations:

Clearly state platform limitations at the top of the documentation, and provide a roadmap or timeline for Linux/macOS support if available.
Offer alternative instructions or workarounds for Linux/macOS users, such as using a Windows VM, container, or remote development environment.
Include a section addressing the lack of Linux/macOS support, with links to feature requests or community discussions.
If possible, provide parity in tooling or recommend equivalent open-source or cross-platform tools for Linux/macOS users.
Regularly update the documentation as platform support evolves, and solicit feedback from non-Windows users to prioritize cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by assuming the on-premises data gateway is installed on a 'local computer' without clarifying cross-platform support, referencing Windows-specific service management (e.g., 'gateway Windows service account'), and repeatedly linking to PowerShell-based automation for gateway management. There are no examples or instructions for Linux environments, nor are Linux tools or command-line alternatives mentioned.

Recommendations:

Explicitly state whether the on-premises data gateway supports installation on Linux or macOS, and provide platform-specific prerequisites if available.
If Linux is supported, add installation and management instructions for Linux (e.g., systemd service management, Linux CLI commands).
Provide automation examples using cross-platform tools such as Azure CLI or REST API, not just PowerShell.
Clarify terminology such as 'local computer' to specify supported operating systems.
If PowerShell is required, note its availability on Linux and provide Linux-compatible command examples.
Ensure that all references to service management (e.g., restarting the gateway) include Linux equivalents if supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Kudu and CMD), mentioning Windows in configuration settings, and omitting Linux-specific instructions or examples for managing app and host settings. The guidance for editing files and using the Azure portal assumes a Windows environment, with no mention of Linux shells, editors, or file paths. Additionally, some settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are described as applying 'when running your logic app workflows on Windows' without clarifying Linux/macOS equivalents or differences.

Recommendations:

Provide explicit instructions for Linux and macOS users, including equivalent shell commands (e.g., Bash) and file path conventions.
When referencing the Kudu environment, clarify its availability and usage on Linux-based App Service plans and provide alternative instructions if necessary.
For settings that are described as Windows-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION), document the behavior and configuration for Linux environments.
Include examples of editing configuration files (local.settings.json, host.json) using cross-platform editors (e.g., VS Code, nano, vim) and clarify that these files and settings are platform-agnostic unless otherwise noted.
Where the Azure CLI is referenced, ensure that examples and instructions are clearly cross-platform and do not assume a Windows shell.
Add a section or notes highlighting any differences, limitations, or considerations when running Logic Apps Standard on Linux versus Windows hosts.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (such as Visual Studio and PowerShell), referencing Windows-specific patterns (like Kudu's CMD console), and providing PowerShell commands without equivalent Bash/Azure CLI examples. Linux-native workflows and tools are not given equal prominence or examples, and there is a lack of explicit Linux or cross-platform guidance for key steps.

Recommendations:

Provide Azure CLI and Bash command examples alongside PowerShell commands (e.g., for retrieving tenant IDs or managing resources).
Mention and demonstrate Linux/macOS-compatible tools (such as VS Code, Azure CLI, and Bash) before or alongside Windows-specific tools like Visual Studio and PowerShell.
Include screenshots or instructions for accessing Kudu/Advanced Tools using Bash or cross-platform shells, not just CMD.
Add explicit notes or sections for Linux/macOS users, clarifying any differences in workflow or tool usage.
Ensure all code snippets and setup instructions are platform-agnostic or provide alternatives for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses PowerShell commands and Windows-centric tooling (e.g., PowerShell modules, ARMClient, C:\ paths) for creating and deploying Azure Logic App templates. There are no equivalent examples or instructions for Linux/macOS users, such as Bash/CLI commands or cross-platform file path conventions. This creates a strong Windows and PowerShell bias, potentially excluding or confusing users on other platforms.

Recommendations:

Provide equivalent Bash/Azure CLI examples for Linux/macOS users, including how to install and use the LogicAppTemplate module (if possible) or alternative tools.
Use cross-platform file path examples (e.g., ~/template.json or ./template.json) instead of Windows-specific paths like C:\template.json.
Mention and demonstrate how to perform the same tasks using Azure CLI and/or REST API, which are available on all platforms.
Clearly state platform requirements or limitations for the LogicAppTemplate module and ARMClient, and suggest alternatives for non-Windows environments.
Reorganize sections so that cross-platform or platform-neutral approaches (e.g., Azure CLI, REST API) are presented before or alongside PowerShell/Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI when discussing automation tools, referencing Visual Studio (a primarily Windows IDE) and its workflows in detail, and mentioning Visual Studio Code only briefly. There are no explicit Linux or cross-platform command-line examples, and the documentation does not provide parity in guidance for Linux users or alternative editors/tools commonly used on Linux. The focus on PowerShell and Visual Studio, both Windows-centric tools, further reinforces this bias.

Recommendations:

List Azure CLI before Azure PowerShell when discussing automation tools, or present both equally with cross-platform context.
Expand the Visual Studio Code section with step-by-step instructions, as VS Code is cross-platform and widely used on Linux.
Include explicit Linux command-line examples for deploying and managing Logic Apps, such as using Azure CLI from a Bash shell.
Mention and provide examples for alternative editors (e.g., Vim, nano, Sublime Text) for editing JSON workflow definitions.
Clarify that all JSON editing and deployment steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific differences.
Avoid assuming Visual Studio as the default IDE; instead, provide equivalent guidance for cross-platform tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Next steps' section, where optimization and best practices links are exclusively for Windows Dockerfiles and Windows containers. There are no equivalent references or guidance for Linux-based web apps or Dockerfiles, despite Linux being a common platform for web applications and AKS workloads. No Linux-specific tools, patterns, or examples are provided throughout the tutorial.

Recommendations:

Include parallel links and guidance for optimizing Linux Dockerfiles and Linux container best practices in the 'Next steps' section.
Reference both Windows and Linux container management documentation when discussing AKS or App Service deployment scenarios.
Add explicit examples or notes for Linux-based web apps where applicable, ensuring parity in instructions and recommendations.
Where Windows-specific terms or tools are mentioned, provide Linux equivalents (e.g., Dockerfile optimization for Linux, Linux-based VM/app discovery).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section and is listed before Azure CLI, with explicit PowerShell command examples. The use of PowerShell scripts is suggested for OAuth authorization, and Windows-centric tools and patterns (such as PowerShell and Azure DevOps) are referenced without equivalent Linux or cross-platform alternatives. There is no mention of Linux shell scripting or other Linux-native tools for deployment or automation.

Recommendations:

Provide Bash or shell script examples alongside PowerShell, especially for tasks like OAuth authorization.
Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
When referencing PowerShell, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
Include references to Linux-native automation tools (e.g., shell scripts, cron jobs) where PowerShell scripts are suggested.
Ensure that the order of examples does not always prioritize Windows tools (e.g., alternate the order of PowerShell and CLI sections, or present them together).
Explicitly mention that all deployment methods (except PowerShell) are available and supported on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools and workflows, such as the Azure portal, KuduPlus console, and CMD shell, without mentioning or providing Linux equivalents. All instructions for file access and script management are given in the context of Windows tools, and there are no examples or guidance for users on Linux systems. There is also an absence of PowerShell-specific bias, but the overall workflow assumes a Windows environment.

Recommendations:

Provide equivalent instructions for accessing and editing files using Linux tools (e.g., Bash shell in Kudu, SSH, or SCP).
Mention that KuduPlus can be accessed via Bash as well as CMD, and show navigation steps for both.
Include notes or examples for users developing or deploying from Linux or macOS environments.
Clarify that the Azure portal and Logic Apps are cross-platform, and highlight any differences or considerations for Linux users.
Where file paths are referenced (e.g., site/wwwroot), note that these are accessible from both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by recommending Visual Studio 2019 and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension (both Windows-only) for schema creation, without mentioning Linux alternatives. Troubleshooting steps reference Windows-specific issues (DPI awareness, registry edits). No Linux or cross-platform schema creation tools or workflows are suggested, and the only code editor example shown is Visual Studio Code, but without explicit Linux guidance. The documentation assumes the use of Windows tools and patterns, with no parity for Linux users.

Recommendations:

Include guidance for creating schemas using cross-platform or Linux-native tools (e.g., XML editors, command-line tools like xmllint, or open-source alternatives).
Mention and provide examples for using Visual Studio Code extensions or other editors available on Linux for schema creation and management.
Remove or supplement Windows-specific troubleshooting (e.g., DPI awareness, registry edits) with Linux/macOS equivalents or note that these steps are Windows-only.
Explicitly state which steps or tools are Windows-only, and provide Linux/macOS alternatives wherever possible.
Add a section or callout for Linux users, outlining recommended tools and steps for schema creation and upload.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by referencing PowerShell for resource group creation, mentioning Windows before Linux in tool/platform requirements, and highlighting Windows-specific tools and development environments. There is a lack of explicit Linux shell/command examples, and the setup steps and authentication guidance mention Windows tools and patterns first or exclusively.

Recommendations:

Provide explicit Linux (bash) command examples alongside or instead of PowerShell for resource group creation and other CLI steps.
When listing prerequisites or supported platforms, mention Linux first or equally, and clarify that all steps are cross-platform.
Include Linux-friendly authentication and development environment instructions (e.g., VS Code on Linux, bash shell usage).
Ensure all referenced tools (like OpenSSL, Azure CLI) have installation and usage notes for both Windows and Linux.
Avoid language that implies Windows is the default or primary platform (e.g., 'on a computer running Windows or Linux' should be 'on Windows or Linux').

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page lists PowerShell and .NET scripting as first-class options for running code from Logic Apps, but does not mention or provide parity for Linux-native scripting languages (such as Bash or Python). There are no explicit Linux or cross-platform CLI examples, and the only scripting language with a clear Windows association (PowerShell) is highlighted. Additionally, there is a lack of Linux-specific deployment or management tooling references, and no examples or guidance for Linux users are provided.

Recommendations:

Add examples and documentation for running Bash and Python scripts from Logic Apps, alongside PowerShell and .NET.
Include cross-platform CLI (e.g., Azure CLI) usage examples for deployment, management, and monitoring tasks, not just Azure Portal or Visual Studio Code.
Explicitly mention Linux support and provide Linux-specific guidance or troubleshooting where relevant.
Ensure that scripting and automation sections do not default to Windows tools, but present cross-platform or Linux-native options equally.
Where PowerShell is referenced, clarify that PowerShell Core is cross-platform and provide Linux installation/use instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Windows-based tools (Visual Studio, Azure Storage Explorer) and workflows, with no mention of Linux equivalents or cross-platform alternatives for key steps. Visual Studio and its extensions are highlighted for map creation and editing, and Azure Storage Explorer (a GUI tool most commonly used on Windows) is the only method described for managing blob storage. There are no CLI or Linux-native instructions, and no mention of PowerShell, but the overall workflow assumes a Windows environment.

Recommendations:

Include instructions for creating and managing maps using cross-platform tools such as the Azure CLI or Azure PowerShell (with explicit Linux/macOS compatibility).
Provide examples for uploading assemblies and maps using the Azure CLI, azcopy, or REST API, which are available on Linux and macOS as well as Windows.
Mention and document the use of Visual Studio Code (which is cross-platform) more prominently, and clarify that the Data Mapper extension works on Linux/macOS.
For storage management, add steps for using az storage blob commands or azcopy for uploading files to blob storage, instead of only Azure Storage Explorer.
Explicitly state that all steps can be performed on Linux/macOS, or provide alternative instructions where certain tools are Windows-only.
Add a table or section comparing tool availability and usage across Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by exclusively referencing Microsoft-centric tools (Host Integration Server, Visual Studio, HIS Designer, 3270 Design Tool) and patterns familiar to Windows/Visual Studio users. There are no examples, tools, or workflows described for Linux or cross-platform development environments. The documentation assumes the use of Windows-based development environments and omits mention of Linux alternatives or parity in tooling.

Recommendations:

Provide equivalent guidance and examples for Linux-based development environments, including how to use Azure Logic Apps connectors from Linux or cross-platform tools.
Mention and, where possible, support open-source or cross-platform alternatives to Visual Studio and Host Integration Server for mainframe integration.
Clarify whether the HIS Designer and 3270 Design Tool are available or supported on Linux, and if not, suggest alternative approaches for Linux users.
Include CLI-based or code-first examples (e.g., using Azure CLI, REST APIs, or other cross-platform tools) for creating and managing Logic Apps connectors, rather than only GUI/Windows-based workflows.
Explicitly state any platform limitations and provide links to Linux-compatible resources or community-supported solutions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively mentioning PowerShell as a scripting language for code snippets, without referencing Bash or other Linux-native scripting options. Additionally, there are no examples or guidance for Linux users, and the development tools highlighted (Visual Studio Code, Azure portal) are cross-platform but the scripting focus remains Windows-centric. No Linux-specific tools, patterns, or examples are provided.

Recommendations:

Include examples for running Bash scripts or other Linux-native scripting languages alongside PowerShell and C#.
Explicitly mention that Visual Studio Code and the Azure portal are cross-platform, and provide setup or usage notes for Linux users where relevant.
Add guidance or links for Linux-based development and deployment workflows, such as using Azure CLI or scripting with Bash.
Where PowerShell is referenced, provide equivalent Bash examples to ensure parity for Linux users.
Highlight any differences or considerations for Linux environments in migration, deployment, or testing steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All instructions, screenshots, and tool references assume the use of Windows and Visual Studio, with no mention of Linux or macOS alternatives. Required tools such as Visual Studio, Azure SDK for .NET, and Azure PowerShell are Windows-centric, and there are no examples or guidance for users on Linux. The use of PowerShell for deployment prompts further reinforces the Windows bias.

Recommendations:

Provide equivalent instructions and examples for Linux and macOS users, such as using Visual Studio Code, the Azure CLI, or other cross-platform tools.
Explicitly mention and link to cross-platform alternatives (e.g., Visual Studio Code, Azure CLI) at the start of the article, not just in passing.
Include Linux/macOS-specific setup steps and screenshots where appropriate.
Clarify which steps are Windows-only and offer parallel guidance for non-Windows platforms.
If PowerShell is required, note how to use it on Linux/macOS, or provide Bash/Azure CLI equivalents.
Consider restructuring the documentation to present cross-platform options first or in parallel, rather than focusing exclusively on Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code (VS Code) and C# for unit test creation, with all examples and instructions tailored to the Windows ecosystem. There are no Linux-specific instructions, examples, or mentions of alternative tools or languages commonly used in Linux environments. The workflow assumes the use of Windows conventions (e.g., folder structure, file paths, and keyboard shortcuts) and does not address cross-platform considerations or parity.

Recommendations:

Add explicit statements confirming cross-platform support for Visual Studio Code and the Azure Logic Apps extension, including any known limitations or differences on Linux.
Provide Linux-specific instructions or notes where relevant, such as alternative keyboard shortcuts, file path conventions, and installation steps for dependencies.
Include examples or guidance for running and managing unit tests in Linux environments (e.g., using .NET CLI instead of Visual Studio tooling, or integrating with Linux-based CI/CD pipelines).
Mention and, if possible, provide sample code for alternative programming languages or frameworks supported on Linux, or clarify if C# is the only supported language.
Ensure screenshots and UI instructions are not Windows-centric (e.g., avoid showing only Windows-style file explorers or context menus).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by providing detailed PowerShell examples before Azure CLI, using Windows-centric tools and terminology (e.g., RDP, Windows images), and omitting explicit Linux/SSH examples for VM creation and access. The VM creation steps default to Windows Server images, and remote access is described only via RDP, with no mention of SSH or Linux images. There are no examples or guidance for deploying or accessing Linux VMs, nor are there instructions for Linux administrators.

Recommendations:

Add explicit Linux/SSH examples for VM creation and remote access, including az vm create commands with --image UbuntuLTS and SSH key authentication.
Include guidance for both Windows and Linux VM images in all relevant steps, making it clear that either OS is supported.
Provide instructions for accessing VMs via SSH (for Linux) as well as RDP (for Windows), and clarify the differences.
Ensure that CLI and PowerShell examples are presented with equal prominence, or alternate which comes first.
Avoid using Windows-specific terminology (e.g., RDP) as the default; instead, use neutral language or mention both RDP and SSH.
Add troubleshooting or verification steps relevant to Linux environments (e.g., checking IPv6 connectivity from a Linux shell).
Where possible, use cross-platform tools and commands, or clearly indicate OS-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on migrating Hyper-V (a Windows-centric hypervisor) servers to Azure, with all examples, terminology, and tooling specific to Windows environments. There are no Linux or cross-platform migration instructions, examples, or tool references. The documentation assumes the use of Windows-based tools and patterns (e.g., Hyper-V Replication provider, Recovery Services agent), and does not mention or provide parity for Linux-based hypervisors or environments.

Recommendations:

Add equivalent migration documentation for Linux-based hypervisors (e.g., KVM, Xen, or VMware on Linux) to ensure parity.
Include Linux-specific instructions or notes where applicable, such as DNS configuration, network connectivity verification, and agent installation.
If the migration tooling supports Linux VMs or appliances, provide explicit examples and screenshots for Linux environments.
Reference or link to documentation for migrating Linux VMs or workloads to Azure, even if on a separate page, to guide non-Windows users.
Clarify in the introduction that this guide is specific to Hyper-V/Windows, and provide navigation to Linux migration resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing Windows-specific tools and best practices (such as optimizing Windows Dockerfiles) in the 'Next steps' section, without providing equivalent Linux guidance. There are no Linux-specific examples, tools, or references, and the only optimization and best practices links are for Windows containers. No PowerShell commands are present, but the overall guidance assumes a Windows-centric environment.

Recommendations:

Include Linux-specific examples and references, such as links to optimizing Linux Dockerfiles or best practices for Linux containers on AKS.
Provide parity in 'Next steps' by offering both Windows and Linux container guidance for AKS.
Mention Linux tools and workflows where relevant, ensuring that Linux users are equally supported in the migration and assessment process.
Review all referenced links and ensure that for every Windows-specific link, a Linux equivalent is also provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio Code (a cross-platform tool, but often associated with Windows development) and C# (primarily a .NET/Windows-centric language). There are no examples or instructions for Linux or macOS environments, nor is there any mention of command-line alternatives or Linux-specific workflows. The document assumes the use of Visual Studio Code and C# without addressing how Linux users might set up or run these tests, or whether .NET dependencies are cross-platform.

Recommendations:

Explicitly mention that Visual Studio Code and the Azure Logic Apps extension are available on Linux and macOS, and provide installation/setup instructions for these platforms.
Clarify that .NET and C# tooling required for unit tests can be installed and used on Linux (e.g., via .NET Core SDK), and provide links or steps for Linux users.
Include at least one example of running or managing tests from the command line (e.g., using dotnet CLI), which is common in Linux workflows.
Avoid language that implies Visual Studio Code is a Windows-only tool, and ensure screenshots or instructions are not Windows-specific.
If there are any platform-specific limitations or differences, document them clearly for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing PowerShell installer script instructions as the only alternative to the OVA method, using Windows-specific tools (e.g., CertUtil in Command Prompt) for file verification, referencing Windows file paths and conventions (e.g., C:\Program Files), and focusing on Windows authentication and IIS web server for discovery. There are no Linux command examples or explicit instructions for Linux-based appliance setup, verification, or credential types, and Linux tools are not mentioned for common tasks.

Recommendations:

Provide equivalent Linux-based instructions for deploying and configuring the appliance, including using Linux shell commands for file verification (e.g., sha256sum) and Linux file paths.
Include Linux authentication and web server (e.g., Apache, Nginx) discovery examples and clarify support for Linux-based workloads.
When referencing credential types, give Linux examples and clarify any differences in required permissions or setup steps.
Where PowerShell or Windows tools are mentioned, offer side-by-side Linux alternatives.
Avoid using Windows paths and tools exclusively; use cross-platform language or provide both Windows and Linux variants.
Explicitly state if certain features are Windows-only, and provide guidance for Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily centered on the Microsoft Rules Composer, a Windows-only GUI tool, and all instructions assume use of this tool. There are no examples or guidance for Linux users, nor are any cross-platform or command-line alternatives mentioned. The workflow and examples are deeply tied to .NET and Windows development patterns, with no mention of Linux-compatible approaches or tools.

Recommendations:

Explicitly state platform requirements and limitations at the start of the documentation, clarifying that the Microsoft Rules Composer is Windows-only.
If possible, provide equivalent command-line or cross-platform alternatives for managing rulesets (e.g., using .NET CLI, PowerShell Core, or REST APIs that work on Linux).
Include examples or workflows for Linux users, such as how to manipulate rulesets programmatically using .NET Core on Linux.
Mention any available or planned Linux-compatible tools, or provide guidance for Linux users on how to interact with rulesets without the GUI.
Reorganize sections to clarify platform dependencies before presenting Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows Server scenarios, mentioning Windows-specific tools and upgrade paths, and omitting explicit Linux migration or upgrade examples. Windows Server end-of-support and upgrade processes are highlighted, while Linux equivalents are not discussed. There are no Linux-specific migration blockers, readiness checks, or tooling references, and no examples or guidance for Linux workloads are provided.

Recommendations:

Include explicit examples and guidance for migrating Linux servers, such as common distributions (Ubuntu, CentOS, RHEL) and their unique considerations.
Add parity for Linux OS upgrades during migration, or clarify if such a feature is not available, and provide recommended upgrade paths for Linux workloads.
Mention Linux-specific migration blockers, readiness checks, and compatibility issues alongside Windows ones.
Reference Linux tools and patterns (e.g., shell scripts, Linux VM extensions) where Windows tools (like Custom Script Extension for Windows) are mentioned.
Ensure that all tables and recommendations (such as end-of-support OS, quick wins, etc.) include Linux operating systems and scenarios.
Balance the focus between Windows and Linux in all sections, especially in migration, assessment, and optimization guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and the Azure PowerShell module for automating VMware migrations. All example commands, script names, and installation instructions are PowerShell-centric, with no mention of Bash, Azure CLI, or cross-platform alternatives. There is no guidance for Linux or macOS users, nor any indication of how to run these automations outside a Windows/PowerShell environment.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for Linux/macOS users, or clarify if such alternatives are not available.
Explicitly state the platform requirements for the scripts (e.g., Windows, Linux, macOS) and, if possible, provide instructions for running PowerShell Core on Linux/macOS.
Include installation and usage instructions for Azure PowerShell on Linux/macOS, or reference cross-platform documentation.
If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported and provide examples using cross-platform syntax.
Mention and, if possible, provide links to any available REST API or SDK alternatives for users who wish to automate migrations without PowerShell.
Add a section addressing common Linux/macOS user scenarios, such as running scripts in containers or using Azure Cloud Shell.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments. It references Windows Server and Software Assurance in the Azure Hybrid Benefit section, and suggests editing the 'hosts file' on the Azure Migrate appliance without clarifying the process for Linux-based appliances. There are no explicit Linux command-line examples or references to Linux tools, and the documentation assumes familiarity with Windows-centric concepts and patterns.

Recommendations:

Provide explicit instructions for both Windows and Linux-based Azure Migrate appliances, especially for tasks like editing the hosts file (e.g., specify the file path and command for Linux: '/etc/hosts').
Include examples or notes for Linux environments where relevant, such as verifying DNS resolution using 'nslookup' or 'dig' on Linux.
Clarify that the Azure Migrate appliance can be deployed on both Windows and Linux, and provide parity in operational steps for both platforms.
When mentioning Azure Hybrid Benefit for Windows Server, also note any relevant licensing or migration considerations for Linux VMs.
Avoid assuming the administrator is using a Windows environment; use cross-platform language and examples where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric workloads (e.g., ASP.NET web apps, SQL Server), mentioning Windows environments (such as Hyper-V and VMware with Windows web apps) without equivalent Linux examples, and referencing tools and migration scenarios that are predominantly relevant to Windows or Microsoft technologies. There is a lack of explicit mention or examples for Linux workloads, Linux-based web apps, or open-source databases, and no Linux-specific migration guidance is provided.

Recommendations:

Include explicit examples and scenarios for migrating Linux servers, Linux-based web applications, and open-source databases (e.g., MySQL, PostgreSQL) to Azure.
Add references to Linux tools and migration patterns, such as SSH-based discovery, Linux agent installation, and migration of workloads running on Apache, NGINX, or Tomcat.
Ensure parity in documentation by providing step-by-step guides or links for both Windows and Linux environments in all relevant sections.
Mention Linux support and compatibility in tool descriptions (e.g., clarify if Data Migration Assistant or App Service Migration Assistant supports Linux workloads).
Highlight Linux-specific considerations, such as handling of file systems, package management, and service management during migration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits Windows bias by referencing Windows-specific paths, tools, and registry keys exclusively. All examples and instructions (such as antivirus exclusions, registry edits, and MMC snap-in usage) are given only for Windows environments, with no mention of Linux equivalents or guidance for Linux-based servers. This may hinder Linux administrators from effectively using or understanding the migration process.

Recommendations:

Provide Linux-specific instructions and examples alongside Windows ones, such as file paths for antivirus exclusions (e.g., /var/lib/...), and commands for installing and managing the Mobility service on Linux.
Include guidance for bandwidth throttling and configuration on Linux servers, such as relevant configuration files or system settings, instead of only referencing Windows registry and MMC snap-ins.
Mention Linux tools and management patterns (e.g., systemd, CLI commands) where appropriate, and ensure parity in troubleshooting and operational guidance.
Clearly indicate which instructions apply only to Windows and provide equivalent steps for Linux where possible.
Add a section or table summarizing differences and requirements for both Windows and Linux server migrations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell (Windows-centric) for configuration examples (e.g., setting FlowTimeoutInMinutes), and by referencing PowerShell-based guides before or instead of cross-platform or Linux-native alternatives. There are no CLI (az), Bash, or Linux-specific instructions or examples provided for key tasks, such as configuring NSG flow logs or setting properties, which may disadvantage Linux users.

Recommendations:

Provide equivalent Azure CLI (az) and/or Bash examples alongside PowerShell for all configuration tasks, especially for setting NSG properties like FlowTimeoutInMinutes.
When listing guides or instructions, present cross-platform (CLI, REST API, Portal) options before or alongside Windows/PowerShell-specific ones.
Explicitly mention that all features and configuration steps are available and supported on Linux, and link to relevant Linux or cross-platform documentation.
Include troubleshooting and usage examples that are relevant to Linux users, such as using jq or grep to parse logs, or automating tasks with Bash scripts.
Ensure that visualization and export tool instructions are not biased toward Windows-only tools (e.g., Power BI), and highlight open-source or cross-platform alternatives equally.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Azure PowerShell (and its LogicAppTemplate module) as the only tool for creating Logic App templates, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. The only explicit tooling guidance is for PowerShell, which is traditionally associated with Windows, and no Linux/macOS-specific instructions or examples are provided. This may lead Linux users to believe that template creation is only possible or best supported on Windows platforms.

Recommendations:

Add equivalent instructions and examples for using Azure CLI (which is cross-platform) to create and deploy Logic App ARM templates.
Where PowerShell is mentioned, also mention that Azure CLI can be used, and provide links or references to relevant Azure CLI documentation.
If certain features are only available in PowerShell (such as the LogicAppTemplate module), clarify this and suggest alternative approaches for Linux/macOS users.
Include at least one example or workflow that demonstrates template deployment or management from a Linux or macOS environment.
Review all tooling recommendations to ensure parity for users on non-Windows platforms, and avoid implying that PowerShell is the default or only supported method.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing command-line instructions specifically for PowerShell, explicitly instructing users to open PowerShell as Administrator, and omitting equivalent instructions for Linux or macOS environments. All CLI examples assume a Windows context, and there are no references to Linux shells or cross-platform usage, despite the Azure CLI being available on multiple platforms.

Recommendations:

Provide equivalent command-line instructions for Linux and macOS users, including shell-agnostic commands or explicit bash/zsh examples.
Avoid specifying 'open PowerShell as Administrator' as the only method; instead, mention that commands can be run in any terminal where Azure CLI is installed (e.g., PowerShell, Command Prompt, Bash).
Add notes or callouts clarifying that Azure CLI commands are cross-platform and provide any necessary adjustments for Linux/macOS environments (e.g., use of sudo, differences in environment variables).
Include screenshots or instructions for non-Windows environments where relevant, or at least acknowledge their usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-based SQL Server deployments and migration targets, such as SQL Server on Azure VM (with Windows), and by linking only to Windows-specific best practices and guidelines. There are no examples, guidance, or references for Linux-based SQL Server deployments or migrations, nor are Linux tools or patterns mentioned. This may leave Linux users without clear guidance for their scenarios.

Recommendations:

Include explicit references and guidance for SQL Server on Linux, both on-premises and as an Azure VM target.
Provide links to best practices and performance guidelines for SQL Server on Linux VMs in Azure (e.g., https://learn.microsoft.com/azure/azure-sql/virtual-machines/linux/).
Add examples and remediation guidance relevant to Linux-based SQL Server deployments, such as file system considerations, disk layout, and supported features.
Clarify in all relevant sections that both Windows and Linux SQL Server sources and targets are supported, and highlight any differences in assessment or migration steps.
Wherever a link or example is provided for Windows, provide a Linux equivalent in parallel.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first and Windows-heavy bias. Throughout the assessment logic, Windows operating systems are listed first and in greater detail, with explicit version-by-version breakdowns, while Linux is referenced generically or as a single row. No Linux-specific examples, screenshots, or troubleshooting guidance are provided. The guidance for discovering Linux kernel versions is indirect and requires extra steps. There are no Linux command-line or tool references, and the documentation assumes familiarity with Windows environments.

Recommendations:

Provide Linux-specific examples and scenarios, such as how to assess readiness for common Linux distributions, including troubleshooting steps for Linux VMs.
Include Linux command-line examples (e.g., how to collect performance data or check OS/kernel versions) alongside or before Windows/Powershell equivalents.
Expand the 'Guest operating system' section to list major Linux distributions and versions explicitly, similar to the Windows breakdown.
Offer guidance for Linux-specific issues (e.g., kernel modules, disk partitioning, network configuration) that may affect migration readiness.
Ensure parity in detail and prominence for Linux and Windows throughout the documentation, including in tables, notes, and examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All setup instructions, installer scripts, and validation steps are explicitly designed for Windows Server environments. Only PowerShell scripts and Windows command-line tools (such as CertUtil) are provided, with no mention of Linux-based alternatives or support. The appliance is required to run on Windows Server 2019/2022, and all examples, screenshots, and troubleshooting steps assume a Windows environment. There are no instructions or parity for Linux-based deployments or administration.

Recommendations:

Provide equivalent instructions and supported tooling for deploying the scale-out appliance on Linux-based servers, if supported.
Include Linux shell (bash) commands for tasks such as checksum validation (e.g., using sha256sum) alongside Windows examples.
Offer Linux-compatible installer scripts or clarify if the appliance is Windows-only, and explicitly state the lack of Linux support if so.
If Linux is not supported, add a clear note early in the documentation stating that only Windows Server is supported for the appliance, and consider providing a roadmap or alternatives for Linux users.
Where PowerShell is used, provide bash or shell script equivalents if Linux support is available.
Ensure that troubleshooting and log file paths are described in a cross-platform manner, or clarify their Windows-specific nature.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools, patterns, and best practices (e.g., Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific performance guidelines) without mentioning or providing equivalent Linux guidance. There are no Linux-specific examples, instructions, or references for scenarios such as SQL Server on Linux, Linux-based failover clustering, or migration from Linux SQL Server environments. The documentation assumes a Windows-centric environment throughout.

Recommendations:

Include explicit guidance and examples for assessing and migrating SQL Server instances running on Linux, including supported distributions and any differences in data collection or assessment.
Reference Linux-based high availability and disaster recovery patterns (e.g., Pacemaker clusters) alongside Windows Server Failover Clusters.
Provide links to Linux-specific best practices for SQL Server on Azure VMs, such as /azure/azure-sql/virtual-machines/linux/performance-guidelines-best-practices-checklist.
Clarify whether the Azure Migrate appliance supports discovery and assessment of SQL Server on Linux, and if so, provide setup instructions for Linux environments.
When mentioning tools like Cloud Witness or Shared Disk for Windows clusters, also mention Linux alternatives or note any limitations.
Ensure that all example links, especially those under 'Learn more' and 'best practices', have Linux equivalents or clearly state platform applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server evaluation licenses, and omitting any mention of Linux-based appliances or examples. There are no Linux/Unix file paths, commands, or troubleshooting steps, and all instructions assume a Windows environment.

Recommendations:

Include equivalent instructions and file paths for Linux-based Azure Migrate appliances, if supported.
Mention whether the diagnostic tool and appliance are available for Linux, and provide parity in troubleshooting steps.
If Linux is not supported, explicitly state this early in the documentation to set user expectations.
Add examples or screenshots for Linux environments where applicable.
Reference Linux tools or patterns (e.g., systemd, /var/log, shell commands) alongside Windows ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on ASP.NET web apps running on IIS (a Windows technology) and omitting explicit mention or examples of Linux-based web app scenarios. There are no Linux-specific instructions, tools, or examples, and the only server technology mentioned for Java is Tomcat, without clarifying if Linux deployments are supported or how to assess them. The documentation also references Windows App Service SKUs and pricing, with no mention of Linux App Service plans or differences.

Recommendations:

Include explicit examples and instructions for assessing Linux-based web apps (e.g., Node.js, Python, PHP, Java on Linux).
Mention and link to Azure App Service for Linux documentation and pricing details.
Clarify whether the Azure Migrate appliance supports discovery and assessment of Linux web servers (e.g., Apache, Nginx, Tomcat on Linux) and provide steps if supported.
Provide parity in assessment workflows and screenshots for both Windows and Linux scenarios.
List both Windows and Linux App Service SKUs and note any differences in features, compatibility, or pricing.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. Deployment and management instructions are centered around PowerShell scripts, with no mention of Bash or Linux-native alternatives. Troubleshooting and certificate management steps are exclusively shown using Windows UI tools (e.g., Certificate Manager, Group Policy Editor), and all screenshots are from Windows environments. There are no examples or instructions for deploying, managing, or troubleshooting the appliance from a Linux or cross-platform perspective, despite the appliance being able to discover Linux servers. Linux tools, commands, or workflows are not mentioned, and Windows-specific paths and patterns (e.g., %ProgramData%, C:\Program Files) are used throughout.

Recommendations:

Provide equivalent Bash or shell script instructions for deploying and managing the appliance on Linux-based hosts, or clarify if only Windows is supported for appliance management.
Include troubleshooting steps and screenshots for certificate validation and MSI signature checking on Linux (e.g., using openssl, certutil, or other Linux tools).
Document how to perform appliance updates, certificate management, and log collection on Linux-based appliances, if supported.
When referencing file paths or environment variables, include Linux equivalents (e.g., /var/lib/, /opt/, $HOME) alongside Windows paths.
Explicitly state OS requirements and clarify if the appliance or its management tools are Windows-only, or provide Linux support guidance if available.
Add examples and guidance for Linux administrators, including how to provide Linux credentials, manage agent health, and troubleshoot common issues from a Linux perspective.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Visual Studio (a Windows-only tool) and providing detailed installation and usage instructions for it before mentioning the cross-platform .NET CLI tool. The prerequisites for the Visual Studio extension explicitly require Windows, and there are no Linux-specific examples, troubleshooting tips, or mentions of Linux development environments. All screenshots and workflows are centered around Windows tools and UI.

Recommendations:

Add explicit instructions and examples for using the .NET CLI tool on Linux and macOS, including installation, usage, and troubleshooting steps relevant to those platforms.
Reorganize the documentation to present the CLI tool (which is cross-platform) before or alongside the Visual Studio extension, emphasizing its suitability for Linux and macOS users.
Include screenshots or terminal output examples from Linux environments to demonstrate parity.
Mention any platform-specific considerations or limitations for Linux users, such as supported shells, file paths, or dependencies.
Clarify that Visual Studio Code (which is cross-platform) can be used for editing .NET projects, and provide guidance for integrating the CLI tool into VS Code workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows Server and SQL Server in cost calculations, licensing, and management tooling (e.g., System Center), with limited or no mention of Linux-specific scenarios, tools, or licensing. While Linux is briefly mentioned in license amortization and support, there are no detailed examples, cost breakdowns, or management considerations for Linux servers. Windows-centric tools and patterns (e.g., System Center, Windows ESU, Azure Hybrid Benefit for Windows) are described in detail, while Linux equivalents are absent.

Recommendations:

Include explicit examples and cost breakdowns for Linux servers, including common Linux distributions and their licensing/support models.
Describe management tooling and monitoring options for Linux (e.g., integration with Azure Monitor, Update Management, and third-party tools commonly used in Linux environments).
Add Linux-specific migration considerations, such as support for open-source databases, web servers, and application stacks.
Ensure parity in describing extended support and security update options for Linux distributions (e.g., Ubuntu ESM, RHEL ELS) where applicable.
Provide sample .csv import templates or appliance setup instructions that reference both Windows and Linux server scenarios.
Balance the discussion of Windows and Linux in all tables and examples, ensuring Linux is not only mentioned but given equal detail.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias, particularly in operational examples and tooling. PowerShell and Windows-specific tools (e.g., NetQosPolicy, Windows Scheduled Tasks) are used exclusively in example scripts for bandwidth throttling, with no Linux equivalents provided. The guidance for operational tasks like scripting, automation, and bandwidth management is Windows-centric. Additionally, Windows OS upgrade during migration is supported and documented, while Linux OS upgrade is explicitly stated as unsupported, with no roadmap or workaround. In several sections, Windows scenarios and tools are mentioned before Linux, and Linux-specific migration nuances are less detailed.

Recommendations:

Provide equivalent Linux-based examples for operational tasks such as bandwidth throttling (e.g., using tc, wondershaper, or iptables on Linux).
Include Linux shell script examples alongside PowerShell for automation and scheduled tasks (e.g., using cron jobs).
Document any Linux-specific migration caveats, best practices, or troubleshooting steps with the same depth as Windows.
Clarify Linux OS upgrade support status and, if unsupported, provide guidance or workarounds for Linux users.
When listing supported operating systems or migration scenarios, alternate the order or present Linux and Windows options with equal prominence.
Reference cross-platform tools where possible, or explicitly state when a feature is Windows-only and suggest alternatives for Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing migration automation and command-line examples exclusively with Azure PowerShell, without mentioning or linking to equivalent Azure CLI or Linux-native tooling. The focus on PowerShell for automation and migration tasks, and the absence of Linux/CLI alternatives, may disadvantage users operating from Linux or cross-platform environments.

Recommendations:

Include Azure CLI examples and tutorials alongside PowerShell for all migration and automation steps.
Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI, and provide links to relevant documentation.
Where automation is discussed, offer both PowerShell and Bash/CLI scripts to ensure parity.
Review referenced tutorials to ensure they are not Windows/PowerShell exclusive, or add Linux/CLI alternatives if missing.
Add a section or note clarifying cross-platform support and tools for the migration process.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily by including PowerShell-based instructions for resource group creation via an include file, without providing equivalent Linux/bash examples inline or in parallel. The setup and tooling sections mention Windows before Linux, and there is no explicit demonstration of Linux command-line usage for resource group management. The rest of the quickstart is platform-agnostic, but the initial setup and resource group creation steps favor Windows users.

Recommendations:

Provide both PowerShell and Bash/Azure CLI examples for resource group creation, either side-by-side or with clear tabs for Windows and Linux/macOS users.
Ensure that all command-line instructions (such as resource group creation and provider registration) are shown in both Windows (PowerShell) and Linux (Bash) syntaxes.
When referencing prerequisites or tools (such as OpenSSL), list Linux and Windows equally, or mention Linux first to avoid implicit prioritization.
Review all included content (such as 'includes/powershell-resource-group-create.md') to ensure Linux parity, or add explicit Linux alternatives in the main documentation.
Consider adding a note or table at the start of the quickstart clarifying that all steps are supported on both Windows and Linux, with links to OS-specific instructions where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently presents Windows-specific tools, commands, and patterns first or exclusively, especially in sections about software inventory, storage, and application discovery. Windows-centric technologies (WMI, PowerShell, Registry, Windows Features) are detailed with specific commands and properties, while Linux equivalents are sometimes grouped together or described in less detail. Some advanced features (e.g., ASP.NET, Spring Boot, Java web app data) are described only for Windows servers, with no mention of Linux support or parity.

Recommendations:

For each section that provides Windows-specific commands (e.g., PowerShell, WMI, Registry), ensure Linux equivalents are given with equal detail and prominence.
Reorder sections so that Linux and Windows examples are presented together, or alternate which OS is presented first to avoid implicit prioritization.
Where advanced application discovery (e.g., Java/Spring Boot web apps) is described only for Windows, clarify whether Linux is unsupported or provide Linux-specific collection details if available.
For storage and feature discovery, provide Linux-specific commands (e.g., for NFS, SMB, disk enumeration) alongside Windows PowerShell cmdlets.
In summary tables, ensure Linux and Windows data collection methods are described with similar granularity and clarity.
Explicitly state any limitations or differences in Linux support, rather than omitting Linux details.
Where only Windows tools (e.g., Get-WindowsFeature, Get-SmbShare) are mentioned, add corresponding Linux commands (e.g., systemctl, exportfs, showmount, etc.) or note if not applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias, with troubleshooting steps and examples often referencing Windows technologies (WinRM, WMI, PowerShell cmdlets) before or instead of Linux equivalents. Windows-specific tools and patterns (such as WinRM TrustedHosts, Get-WmiObject, and application pool configuration) are mentioned explicitly, while Linux troubleshooting is less detailed and lacks parity in example commands or tool references. Linux instructions are present but less comprehensive, and Linux-specific troubleshooting steps are sometimes generalized or omitted.

Recommendations:

Provide Linux troubleshooting steps and examples with equal detail and prominence as Windows steps, including specific commands (e.g., SSH troubleshooting, systemd/service checks, relevant log file locations).
When mentioning Windows tools (e.g., WinRM, WMI, PowerShell cmdlets), also mention Linux equivalents (e.g., SSH, systemctl, journalctl, relevant shell commands) in the same context.
Avoid always listing Windows steps or tools first; alternate the order or present both OSes side by side.
For web app migration errors, include equivalent checks and recommendations for common Linux-based web servers (e.g., Apache, Nginx, Tomcat) where relevant.
Link to Linux-specific documentation or troubleshooting guides where possible, just as is done for Windows.
Ensure that all error codes and troubleshooting sections address both Windows and Linux scenarios explicitly, not just by implication.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily in the management and configuration sections. It provides only Windows-specific tooling and examples (e.g., PowerShell cmdlets like New-NetQosPolicy, references to Windows services such as GatewayWindowsService.exe, and configuration file paths like C:\ProgramData\Microsoft Azure\Config). There are no equivalent Linux commands, tools, or file paths mentioned, nor is there guidance for Linux-based appliances or environments. The documentation implicitly assumes the Azure Migrate appliance is running on Windows, and all operational instructions are Windows-centric.

Recommendations:

Provide equivalent Linux-based instructions for bandwidth throttling (e.g., using tc or similar Linux network QoS tools) and reference Linux services/processes if supported.
Include Linux file path examples (e.g., /etc/ or /var/lib/...) for configuration files like GatewayDataWorker.json if the appliance can run on Linux.
Clarify whether the Azure Migrate appliance is Windows-only or if Linux is supported; if Linux is not supported, state this explicitly.
If Linux-based appliances are supported, add sample commands and configuration steps for Linux environments alongside Windows examples.
Avoid using Windows-specific terminology (e.g., C:\ProgramData) without providing cross-platform alternatives or context.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows examples, tools, and configuration steps are often presented before their Linux equivalents, and in greater detail. Windows-specific tools and UI instructions (e.g., WMI Control Panel, WinRM, Start menu) are described step-by-step, while Linux instructions are more concise and sometimes lack equivalent depth or screenshots. SQL Server (a Windows-centric technology) is covered extensively, while MySQL (more common on Linux) receives minimal coverage. Some sections (e.g., Hyper-V) are inherently Windows-only, but the overall pattern is to foreground Windows workflows.

Recommendations:

Ensure Linux instructions are as detailed as Windows ones, including step-by-step guides, screenshots, and troubleshooting tips.
Present Linux and Windows examples in parallel, or alternate which comes first, to avoid the impression of Windows being the default.
For every Windows-specific tool or UI step (e.g., WMI Control Panel), provide the Linux equivalent (e.g., relevant commands, config files, or tools).
Expand MySQL/Linux database discovery instructions to match the depth of SQL Server/Windows coverage.
Where possible, use cross-platform language and avoid assuming a Windows environment (e.g., avoid 'Start menu' as the default entry point).
Include PowerShell and Bash (or shell) script examples side-by-side for automation tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, specifically Hyper-V, and consistently provides instructions, commands, and tooling references that are exclusive to Windows. PowerShell and Windows command-line tools are used for verification and configuration steps, and there is no mention of Linux equivalents or cross-platform alternatives. Linux is only referenced as a possible credential type, with no guidance or examples for Linux-based appliance setup, verification, or troubleshooting.

Recommendations:

Wherever command-line verification or configuration is shown (e.g., file hash verification), provide equivalent Linux commands (e.g., sha256sum) alongside Windows examples.
Clarify whether the Azure Migrate appliance can be deployed or managed from Linux hosts, and if so, provide explicit instructions and examples for Linux users.
If PowerShell scripts are required, note whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script alternatives where possible.
For steps involving Hyper-V Manager or other Windows-only tools, mention if there are CLI or cross-platform alternatives, or explicitly state the Windows requirement.
Include troubleshooting and configuration guidance for Linux-based environments, especially for network/proxy configuration, credential delegation, and appliance access.
Ensure parity in screenshots and UI walkthroughs for Linux users if a Linux-based workflow is supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Hyper-V, a Windows-based virtualization platform, and only discusses assessment and migration scenarios for Windows environments. There are no references to Linux-based hypervisors (e.g., KVM, Xen), nor are there any Linux-specific instructions, examples, or tools mentioned. The guidance assumes the user is operating in a Windows/Hyper-V context, with no parity for Linux environments.

Recommendations:

Include equivalent guidance for assessing and migrating servers from Linux-based hypervisors (such as KVM or Xen) to Azure.
Provide Linux-specific examples and instructions, including how to deploy and configure the Azure Migrate appliance on Linux platforms if supported.
Mention and link to documentation for Linux environments where appropriate, or clearly state if the process is not supported for non-Windows hypervisors.
Ensure that any prerequisites, limitations, and planning considerations are addressed for both Windows and Linux environments to promote parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: Windows Server and PowerShell are referenced as defaults or primary examples, especially for the replication appliance setup and credential policies. Windows registry and group policy checks are detailed, while equivalent Linux checks are not. The process for installing the Mobility agent on Linux is present, but less detailed compared to Windows, and Windows tools (e.g., SetupDiag, registry, group policy) are mentioned without Linux equivalents. Some steps (e.g., OVA template setup) implicitly assume a Windows environment, and Linux-specific troubleshooting or configuration is less emphasized.

Recommendations:

Provide Linux-first or Linux-parity examples alongside Windows instructions, especially for appliance setup and agent installation.
Include Linux equivalents for registry and group policy checks (e.g., systemd, sudoers, SELinux, firewall rules).
Document Linux troubleshooting steps, such as log file locations, common permission issues, and required packages.
Where PowerShell is referenced, provide Bash or shell script alternatives for Linux environments.
Clarify when steps are OS-agnostic and when they are specific to Windows or Linux.
Ensure all screenshots and UI references are applicable to both Windows and Linux scenarios, or provide alternatives.
Expand on Linux-specific post-migration best practices and activation/troubleshooting steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and extensions (such as the Network Watcher extension for Windows), mentioning Windows/PowerShell automation before Linux equivalents, and lacking explicit Linux-focused migration instructions or examples. While Linux is mentioned in compatibility tables, there are no detailed Linux agent installation or migration steps, and references to documentation or extensions are Windows-centric.

Recommendations:

Include explicit Linux migration steps and examples, such as how to install and configure the Network Watcher extension on Linux VMs.
When referencing automation (PowerShell, Azure CLI, Terraform), provide Linux/Unix shell examples alongside or before Windows/PowerShell examples.
Link to both Windows and Linux agent documentation where relevant, not just to Windows-specific pages.
Clarify any differences in agent behavior or prerequisites between Windows and Linux platforms.
Add troubleshooting steps and error messages specific to Linux environments, if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias, particularly in the section instructing users to install and use the Azure CLI. It explicitly directs users to open PowerShell as Administrator and provides command-line instructions in a PowerShell context, with no mention of Linux/macOS terminals or shell equivalents. There are no Linux-specific instructions or screenshots, and the workflow assumes a Windows environment.

Recommendations:

Provide parallel instructions for Linux and macOS users, including how to open a terminal and run Azure CLI commands.
Avoid specifying 'PowerShell' unless the instructions are truly Windows-specific; otherwise, use neutral language like 'terminal' or 'command prompt'.
Include example commands and outputs as they would appear in Bash or other common Linux shells.
Add notes or callouts where behavior or prerequisites differ between Windows and Linux/macOS (e.g., installation paths, permissions).
Ensure screenshots and step-by-step instructions are not exclusively from Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Windows/Windows Phone-specific notification examples (using Windows toast XML and SendWindowsNativeNotificationAsync), mentioning Windows platforms explicitly, and omitting equivalent Linux, Android, or cross-platform notification examples. The SDK usage is shown only for Windows notifications, and there are no Linux command-line, REST API, or cross-platform code samples.

Recommendations:

Add equivalent examples for sending notifications to Android (using FCM) and iOS (using APNS) with the Notification Hubs SDK.
Include REST API examples for sending notifications, which are platform-agnostic and runnable from any OS, including Linux.
Provide Node.js or Python code samples that demonstrate sending notifications from non-Windows environments.
Rephrase sections that mention Windows platforms first or exclusively, ensuring cross-platform parity in both order and content.
Explicitly mention that the SDK and REST APIs can be used from Linux and macOS, not just Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific resources (such as a link to 'support for TLS protocols on Windows') and omits equivalent Linux guidance or examples. There are no Linux-specific instructions or links, and Windows is mentioned explicitly before Linux. This creates a bias toward Windows users and leaves Linux users without clear guidance.

Recommendations:

Add a section or examples describing how to verify or configure TLS 1.2 support on common Linux distributions.
Include links to Linux-specific documentation or tools (e.g., OpenSSL, curl, or distro-specific TLS configuration guides).
Mention Linux and macOS alongside Windows when discussing operating system compatibility and configuration.
Provide parity in troubleshooting steps or verification commands for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently presenting Windows instructions and tooling (such as PowerShell and Windows Admin Center) before Linux equivalents, providing more detailed steps for Windows, and emphasizing Windows-specific tools. Linux instructions are present but less detailed and lack parity in tooling examples (e.g., no Bash/CLI automation equivalent to PowerShell or Windows Admin Center).

Recommendations:

Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid always listing Windows first.
Provide Linux-specific automation examples, such as using Bash scripts or Azure CLI, in parity with PowerShell examples.
Include references to Linux-native management tools or workflows where Windows Admin Center is mentioned for Windows.
Ensure that all steps and details provided for Windows are also present for Linux, including troubleshooting and verification steps.
Where PowerShell cmdlets are highlighted, also mention equivalent Azure CLI or Bash commands for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear Windows bias. Windows tools and patterns (such as PowerShell remoting, WMI, and WinRM) are mentioned first and in detail, while Linux equivalents are often only briefly referenced or described as secondary. Many requirements and examples are specific to Windows (e.g., detailed PowerShell and SQL Server authentication scripts for Windows, explicit mention of Windows ports and permissions), and Linux support is sometimes missing or not supported (e.g., SQL Server discovery on Linux is not supported, ASP.NET web app discovery is Windows-only). Where Linux is supported, the documentation provides less detail, fewer examples, and less guidance compared to Windows.

Recommendations:

Provide Linux-first or at least Linux-equal examples and explanations alongside Windows ones, especially for setup, permissions, and troubleshooting.
Include detailed Linux command-line examples (e.g., for configuring SSH, required permissions, and package installation) similar to the PowerShell examples provided for Windows.
Where features are not supported on Linux (e.g., SQL Server discovery), clearly state roadmap or alternatives, and provide links to relevant Linux migration/discovery documentation.
Balance the order of presentation so that Linux and Windows requirements are described in parallel, not always with Windows first.
Expand on Linux-specific troubleshooting, error messages, and best practices, matching the depth provided for Windows.
Where possible, provide parity in supported features for Linux and document any gaps transparently.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as PowerShell remoting, WMI, and WinRM) are mentioned and described in detail, often before or instead of Linux equivalents. Windows permissions and account setup are explained with more granularity, and PowerShell is referenced as the primary method for many operations. In contrast, Linux instructions are present but less detailed, and some features (such as SQL Server discovery and ASP.NET web app discovery) are not supported on Linux at all. Example scripts and troubleshooting steps are provided for Windows but are missing or less comprehensive for Linux.

Recommendations:

Provide Linux-first or parallel Linux examples and instructions wherever Windows instructions are given, especially for permissions, account setup, and troubleshooting.
Include Linux-specific troubleshooting guidance and example scripts for common setup and permission issues, similar to the detailed steps provided for Windows.
Where features are not supported on Linux (e.g., SQL Server discovery, ASP.NET web app discovery), clearly state the roadmap or alternatives for Linux users, and consider parity where technically feasible.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, rather than listing Windows first by default.
Where PowerShell scripts are provided for Windows, offer Bash or shell script equivalents for Linux setup and management tasks.
Ensure that all tables and matrices include Linux-specific details and not just Windows-centric requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias: the Azure Migrate: App Containerization tool must be installed and run on a Windows machine, with no mention of Linux or macOS support. All installation instructions and troubleshooting paths are Windows-specific (e.g., PowerShell commands, Windows file paths). There are no examples or guidance for using the tool from a Linux environment, despite the fact that the applications being containerized are running on Linux servers. The documentation assumes the user has access to a Windows environment and is familiar with Windows tools and conventions.

Recommendations:

Provide installation and usage instructions for Linux (and optionally macOS) environments, or clearly state if the tool is Windows-only and explain why.
Offer Linux shell (bash) equivalents for PowerShell commands, or provide a CLI/installer that works cross-platform.
Document file paths and log locations for Linux systems if/when supported.
If the tool is Windows-only, suggest alternative approaches for Linux users (e.g., using Docker CLI, manual containerization steps, or other Azure-supported tools).
Clarify in the prerequisites section that a Windows machine is mandatory, and consider linking to a feature request or roadmap for Linux support if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a significant Windows bias. The Azure Migrate appliance is only described as being installed on Windows Server (2019/2022), with no mention of Linux as a supported OS for the appliance. All installation and verification steps use Windows-specific tools (PowerShell, CertUtil, Windows command prompt), and the script provided is a PowerShell script (.ps1) with no Linux equivalent. The appliance setup instructions exclusively reference Windows roles and features (IIS, PowerShell ISE, Windows Activation Service), and there are no Linux-based installation or usage examples. While Linux server discovery is supported, the documentation assumes a Windows environment for all tooling and setup, omitting Linux alternatives.

Recommendations:

Provide explicit support and instructions for deploying the Azure Migrate appliance on Linux-based EC2 instances, if supported. If not supported, clearly state this limitation.
Include Linux shell (bash) equivalents for all command-line steps, such as file hash verification (e.g., using sha256sum), and provide Linux-based installation and troubleshooting guidance.
If the appliance is Windows-only, add a prominent note early in the documentation to inform users that Linux is not supported as a host OS for the appliance.
Offer parity in examples: for every Windows-specific instruction (e.g., PowerShell script execution, CertUtil usage), provide a Linux alternative or clarify the absence thereof.
Review and update the documentation to ensure Linux administrators can follow the process without needing access to a Windows environment, or clearly state the requirement for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no CLI, Bash, or Linux-native command examples provided, and the prerequisites and workflow assume the use of PowerShell (either locally or in Cloud Shell). This creates a Windows-centric experience, even though the VM created is Linux-based.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux and macOS.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
Include Linux/Bash shell command snippets for each step, especially for users who prefer or require a non-Windows workflow.
Clarify that all steps can be performed from any OS using Azure CLI, not just from a Windows/PowerShell environment.
Where possible, link to documentation for both PowerShell and CLI approaches, and avoid implying PowerShell is the default or only method.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Cloud Witness for Windows Server Failover Clusters, links to Windows-specific best practices), mentioning Windows scenarios before Linux equivalents, and omitting Linux-specific guidance or examples for SQL Server migrations. There are no Linux or cross-platform command-line examples, and Linux licensing (RHEL/SLES) is only briefly mentioned in the context of Azure Hybrid Benefit, without further guidance.

Recommendations:

Include explicit examples and guidance for assessing SQL Server instances running on Linux, such as Ubuntu or RHEL, alongside Windows examples.
Provide parity in high availability and disaster recovery sections by describing Linux-based clustering and witness options (e.g., using Linux Pacemaker clusters or file share witness on Linux).
Add links to Linux-specific best practices for SQL Server on Azure VMs, similar to the Windows link provided.
Clarify any differences in the Azure Migrate appliance setup or assessment process for Linux-based SQL Server instances.
Where licensing or Azure Hybrid Benefit is discussed, provide concrete steps or references for Linux (RHEL/SLES) subscriptions, not just Windows.
Ensure screenshots and UI references are not Windows-centric and, where possible, show cross-platform applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing command-line examples (such as nslookup) with Windows-style prompts (e.g., 'c:\ >nslookup'), referencing PowerShell-specific tools like Test-NetConnection, and omitting equivalent Linux/macOS commands or instructions. The guidance for editing the hosts file and DNS troubleshooting is written from a Windows perspective, with no mention of Linux file paths or tools (e.g., /etc/hosts, dig, or host commands). This may hinder users operating Azure Migrate appliances on Linux or mixed environments.

Recommendations:

Provide Linux/macOS equivalents for all command-line examples (e.g., show both 'nslookup' and 'dig' or 'host' commands, with appropriate shell prompts).
When referencing PowerShell-specific tools like Test-NetConnection, also mention cross-platform alternatives such as 'telnet', 'nc' (netcat), or 'curl' for port connectivity tests.
Include instructions for editing the hosts file on Linux (/etc/hosts) and macOS, not just Windows (C:\Windows\System32\drivers\etc\hosts).
Use neutral command prompts (e.g., '$' for shell, or generic 'command line') instead of Windows-specific prompts.
Explicitly state that the troubleshooting steps apply to both Windows and Linux appliances, and clarify any differences in procedure.
Add screenshots or terminal output examples from Linux environments where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. In troubleshooting steps, PowerShell commands and Windows-specific tools (like PsPing and Invoke-WebRequest) are highlighted, while Linux equivalents are either less detailed or omitted. In sections on resolving failed states, only PowerShell and Azure Resource Explorer (browser-based, with a browser recommendation) are provided, with no CLI or Linux-native alternatives. In the connectivity validation table, Windows tools are linked and described in more detail than their Linux counterparts. Windows approaches are often listed before Linux ones.

Recommendations:

Provide equivalent Linux CLI (e.g., Azure CLI, Bash) commands alongside PowerShell examples for managing network interfaces and troubleshooting failed states.
Expand Linux tool recommendations in the connectivity validation table, e.g., suggest 'curl' or 'wget' for TCP tests, and 'socat' or 'iperf' for UDP tests, with example commands.
Avoid recommending only Windows-specific tools (like PsPing) without mentioning cross-platform or Linux alternatives.
Where PowerShell is used, add Azure CLI or REST API examples for parity.
Ensure Linux and Windows instructions are presented with equal detail and prominence, and avoid consistently listing Windows approaches first.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on PowerShell, providing only PowerShell-based examples and instructions for troubleshooting VPN gateways and connections. There are no equivalent examples using the Azure CLI, Bash, or other Linux-friendly tools within this page. The prerequisites and workflow assume the use of PowerShell (either in Cloud Shell or locally), which is more familiar to Windows users. While there is a link to a separate Azure CLI-based troubleshooting guide in the 'Related content' section, this page itself does not provide parity for Linux users or those preferring CLI/Bash workflows.

Recommendations:

Add parallel Azure CLI (az) command examples alongside PowerShell examples for all troubleshooting steps.
Include explicit instructions for running these commands in Bash (Cloud Shell or local Linux/macOS terminal).
Update prerequisites to mention both PowerShell and Azure CLI as supported options, with links to installation guides for each.
Consider using tabbed code blocks (e.g., 'PowerShell' and 'Azure CLI') to allow users to select their preferred environment.
Reference the Azure CLI troubleshooting page more prominently at the start of the document, and clarify that all steps can be performed with either tool.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a significant Windows bias. All troubleshooting steps and command-line examples are provided exclusively for Windows environments, using PowerShell, Command Prompt, and Windows-specific tools (e.g., services.msc, MMC snap-ins, Windows file paths). There are no Linux or cross-platform alternatives, and the instructions assume the Azure Migrate appliance is accessed and managed via Windows tools. Linux users are not provided with equivalent commands or guidance.

Recommendations:

Provide Linux shell (bash) equivalents for all PowerShell/Command Prompt commands (e.g., using curl, nc, dig, systemctl).
Document how to check and manage the Azure Migrate appliance if it is deployed on Linux, or clarify if only Windows is supported.
Offer cross-platform tools or methods for connectivity checks (e.g., using telnet/nc for port checks, dig/nslookup for DNS, azcopy for Linux).
Mention Linux file locations and configuration steps where relevant (e.g., /etc/hosts instead of only C:\Windows\System32\drivers\etc\hosts).
Explicitly state OS requirements and, if Windows-only, provide rationale and alternatives for Linux-based environments.
Include screenshots or CLI output examples from Linux terminals where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, with exclusive use of Windows Server, PowerShell, and Windows-specific tools and patterns. All setup, configuration, and scripting instructions are provided for Windows/PowerShell, with no equivalent Linux-based examples or guidance. Linux is only mentioned as a supported guest OS for discovery, but not as a platform for running the appliance or performing administrative tasks.

Recommendations:

Provide explicit instructions and examples for deploying and managing the Azure Migrate appliance from a Linux host, if supported.
Include Linux shell (bash) equivalents for PowerShell commands where possible, or clarify if Linux-based management is not supported.
Document any Linux-based tooling or automation options for preparing environments, validating prerequisites, and managing credentials.
Clarify early in the documentation whether the appliance and management workflows are Windows-only, and if so, suggest alternative approaches for Linux-centric environments.
Ensure parity in examples and screenshots for both Windows and Linux, especially in sections covering credential management, connectivity validation, and troubleshooting.
If Linux is not supported for appliance hosting or management, explicitly state this limitation to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias. While both Windows and Linux are mentioned as supported platforms, Windows is often referenced first (e.g., 'Manage Network Watcher extension for Windows' before Linux), and PowerShell is highlighted as a primary automation method. There are no explicit Linux CLI or shell command examples, and Linux-specific tooling or workflows are not equally emphasized. The documentation lacks parity in example commands or guidance for Linux users, especially for automation and agent management.

Recommendations:

Ensure that references to Windows and Linux are presented with equal prominence, alternating order or listing both together (e.g., 'Manage Network Watcher extension for Windows or Linux').
Provide equivalent example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) wherever automation or agent installation is discussed.
Include Linux-specific troubleshooting steps or notes where relevant, not just generic or Windows-centric guidance.
Highlight Azure CLI usage alongside PowerShell for cross-platform automation, and provide links to both sets of documentation.
Where screenshots or UI steps are shown, clarify any OS-specific differences or provide Linux-centric visuals if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits several signs of Windows bias. While it mentions that VPN troubleshoot can be called via Azure portal, PowerShell, CLI, or REST API, the only specific example of command-line tooling is PowerShell (in the 'Considerations' section). There are no Linux-specific examples or instructions. Several log file examples and error messages reference Windows-specific error codes and terminology (e.g., 'Windows error 13801', 'Windows error 13843'). The log file paths and formats (e.g., C:\Resources\...) are Windows-centric. There is no mention of Linux tools or workflows for accessing or analyzing logs, nor are there CLI examples tailored for Linux environments.

Recommendations:

Provide explicit Linux/Azure CLI examples alongside or before PowerShell examples, especially in sections discussing command-line usage.
Reference Linux-compatible tools (e.g., azcopy, Azure CLI, or standard Linux utilities) for downloading and analyzing logs from Azure Storage.
When showing log file paths, use platform-agnostic or Linux-style paths as well, or clarify that paths may differ on Linux.
If error codes are Windows-specific, add explanations or mappings for Linux users, or clarify how similar issues would appear on non-Windows systems.
Ensure that troubleshooting workflows and recommendations are equally accessible and actionable for Linux administrators.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All scripting and automation instructions are provided exclusively using PowerShell (.ps1 script), with no mention or example of Bash, Azure CLI, or Linux-native alternatives. The prerequisites and instructions assume the use of PowerShell, and there are no Linux-specific considerations or examples, despite PowerShell Core being cross-platform. There is also no guidance for users who may prefer or require Bash scripting or Azure CLI for automation.

Recommendations:

Provide equivalent migration instructions and scripts using Azure CLI and/or Bash, ensuring Linux users have a first-class experience.
Explicitly mention that PowerShell 7 is cross-platform and provide Linux/macOS installation and usage notes, including any known issues or differences.
Offer downloadable migration scripts in both PowerShell (.ps1) and Bash (.sh) formats, or provide guidance on how to adapt the process for non-PowerShell environments.
Include Linux/macOS-specific screenshots or terminal examples where relevant.
Clarify any limitations or differences in running the migration process on Linux/macOS versus Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is given a prominent, detailed section before Azure CLI, with explicit instructions for installing and using the Azure PowerShell module (a Windows-centric tool). The PowerShell section is more verbose and includes troubleshooting steps for module installation and versioning, which are specific to Windows environments. Although Azure CLI is covered, there is no mention of Linux-specific usage patterns, and the PowerShell/Windows approach is presented first and in greater detail.

Recommendations:

Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid defaulting to Windows-centric tooling.
Provide explicit Linux usage notes, such as mentioning that Azure CLI is pre-installed on many Linux distributions and can be installed via package managers like apt or yum.
Include example commands for common Linux shells (e.g., bash, zsh) and clarify that Azure CLI is cross-platform.
Reduce the emphasis on PowerShell-specific troubleshooting (e.g., module installation/versioning) unless paralleled with Linux/CLI troubleshooting steps.
Add a brief section or note about using Azure CLI and Cloud Shell from Linux/macOS environments, highlighting parity and any differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell cmdlets and Windows-oriented tooling (PowerShell, Azure Cloud Shell with PowerShell), with no mention or examples for Linux users (such as Azure CLI or Bash). All code samples and instructions are PowerShell-based, and there is no guidance for users who may prefer or require Linux-native tools or scripting environments.

Recommendations:

Add equivalent Azure CLI (az) command examples for each PowerShell cmdlet shown, and present them alongside or before the PowerShell examples.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
Include guidance or links for Linux/macOS users on how to install and use Azure CLI, and how to perform the same diagnostics using CLI commands.
Where possible, use neutral language that does not assume the user is on Windows or using PowerShell.
Consider restructuring the article to present cross-platform solutions first (e.g., Azure CLI), or provide parallel sections for PowerShell and CLI/Bash.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by referencing Windows-specific tools (Visual Studio, Solution Explorer) and platforms (Windows Phone, Windows Store, Universal Windows Platform) before or more prominently than their Linux or cross-platform counterparts. There are no examples or instructions for Linux development environments, and the workflow assumes the use of Visual Studio on Windows.

Recommendations:

Include instructions and screenshots for performing the same tasks using cross-platform IDEs or editors, such as Visual Studio Code or JetBrains Rider, on Linux.
Provide command-line alternatives for project navigation and file editing, suitable for Linux and macOS users.
Mention and demonstrate how to run and debug the sample code on Linux (e.g., using .NET CLI commands like 'dotnet run', 'dotnet publish').
Balance references to Windows-specific platforms (e.g., Windows Store, UWP) with equivalent information for iOS, Android, and other platforms.
Clarify that the tutorial is applicable to non-Windows environments and provide any necessary setup instructions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows by exclusively using an ASP.NET WebAPI backend for the server-side component, with no mention of Linux-friendly or cross-platform alternatives (such as Node.js, Python, or Java backends). The backend example assumes familiarity with Windows-centric technologies and does not provide guidance or code samples for users on Linux or macOS. There are no references to Linux tools, deployment patterns, or command-line instructions, and the only backend stack shown is one most commonly associated with Windows environments.

Recommendations:

Provide equivalent backend implementation examples using cross-platform technologies such as Node.js (Express), Python (Flask/FastAPI), or Java (Spring Boot), and reference these alongside the ASP.NET example.
Include instructions for deploying and running the backend on Linux (e.g., using Docker, Azure App Service for Linux, or other Linux-based hosting).
Add notes or links for users who may be developing on macOS or Linux, clarifying that the client-side (Android) code is platform-agnostic and that the backend can be implemented in any language or framework.
Where possible, use neutral terminology (e.g., 'backend API' instead of 'ASP.NET backend') and provide a selector or toggle in the documentation for different backend stacks.
Reference tools and workflows that are available on all platforms, and avoid assuming the use of Windows-only development environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions for moving Azure Load Balancers using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux users or cross-platform CLI tools such as Azure CLI (az). All command-line examples are in PowerShell, and there are references to Windows-specific tools (e.g., notepad.exe). There is no mention of Bash, shell scripting, or Linux-native editors, which may hinder Linux or macOS users.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Replace or supplement references to Windows-only tools (e.g., 'notepad.exe') with cross-platform alternatives (e.g., 'nano', 'vim', or 'code'), or use generic language like 'open the file in your preferred text editor'.
Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI and standard text editors.
Where possible, provide Bash script snippets or guidance for users on non-Windows platforms.
Review all prerequisites and instructions to ensure they are not assuming a Windows environment by default.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several ways. PowerShell is given a prominent, detailed walkthrough with extensive explanations and code samples, often before CLI/Linux-native alternatives. The PowerShell sections reference Windows-specific tools and installation patterns (e.g., Azure PowerShell module, Get-Module), and the ARM template cleanup instructions reference PowerShell rather than CLI/bash. While Linux is represented (e.g., Ubuntu VM examples, CLI usage), the documentation structure and depth of PowerShell content suggest a Windows-first approach.

Recommendations:

Ensure that CLI (az) and bash examples are as detailed and prominent as PowerShell, including explanations for environment setup and troubleshooting.
Where PowerShell-specific instructions are given (e.g., module installation, cleanup), provide equivalent bash/CLI/Linux-native instructions alongside or before them.
In ARM and Bicep template deployment and cleanup sections, include both PowerShell and CLI/bash commands for parity.
Review the order of tabs and sections to avoid consistently placing PowerShell/Windows content before CLI/Linux content.
Audit for references to Windows-specific tools or patterns (such as 'Get-Module') and ensure Linux equivalents (such as checking az CLI version) are also provided.
Highlight that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for cluster setup and connection, without offering equivalent Bash/CLI commands for Linux or macOS users. The use of PowerShell-specific syntax and cmdlets, as well as the absence of cross-platform Azure CLI alternatives, makes the instructions less accessible to non-Windows users.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell, using Bash syntax for environment variable assignment and command execution.
Explicitly mention that both PowerShell and Bash/CLI can be used, and clarify any platform-specific requirements.
Reorder or parallelize examples so that Linux/macOS (Bash/CLI) and Windows (PowerShell) instructions are given equal prominence.
Include notes or links to official Azure CLI documentation for users on Linux or macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a Windows PowerShell example (Remove-AzResourceGroup) for deleting the resource group, with no equivalent example or mention of how to perform the same task using Azure CLI, Bash, or other Linux-friendly tools. This prioritizes Windows tooling and omits guidance for Linux/macOS users.

Recommendations:

Add an Azure CLI example (e.g., az group delete --name myResourceGroup) alongside the PowerShell example.
Include a Bash shell example for Linux/macOS users.
Present both PowerShell and CLI examples in parallel tabs or sections to ensure equal visibility.
Review documentation for other instances where only Windows tools are referenced and add cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong bias toward Windows and PowerShell usage. All command-line examples use Azure PowerShell cmdlets, with no equivalent Azure CLI (bash) or native Linux shell examples provided. The instructions assume the user is running PowerShell locally or in Cloud Shell, and reference Windows-centric tools and patterns (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroup) without mentioning or prioritizing cross-platform alternatives. There is a brief mention of using Bash in Azure Cloud Shell, but all detailed steps and code samples are PowerShell-specific.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all resource management steps.
Explicitly mention that Azure CLI can be used from Bash in Cloud Shell and on Linux/macOS systems.
Reorder instructions or provide parallel sections so that Linux/Bash/Azure CLI usage is not secondary to PowerShell.
Reference both PowerShell and CLI documentation links where appropriate.
Clarify that both PowerShell and CLI are cross-platform, and help users choose the tool that best fits their environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows/Azure environments by focusing exclusively on Azure-specific tools, providers, and workflows, with no mention of Linux-specific tools, shell commands, or parity in examples. All examples and references are centered around Azure CLI, Microsoft Entra ID, and Azure-specific Terraform providers, with no Linux or cross-platform command-line examples or guidance.

Recommendations:

Include Linux shell (bash) examples alongside or in place of Azure CLI/PowerShell commands where relevant.
Mention and provide parity for Linux-native tools and workflows (e.g., OCI CLI usage on Linux, authentication methods, environment setup).
Add explicit notes or sections for Linux users, including installation and configuration steps for Terraform, OCI CLI, and Azure CLI on Linux.
Ensure that any scripts or code snippets are cross-platform or provide both Windows and Linux variants.
Reference documentation or quickstarts for Linux environments, not just Azure/Windows-focused resources.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell (Register-AzProviderFeature) commands for required registration steps, without offering equivalent Azure CLI (az) or Bash examples. The use of PowerShell syntax and cmdlets assumes a Windows environment or familiarity with Windows tooling, and there are no Linux-specific instructions or cross-platform alternatives provided. This may hinder users working from Linux or macOS environments.

Recommendations:

Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for registration steps. For example, include 'az feature register' commands alongside 'Register-AzProviderFeature'.
Explicitly state that both PowerShell and Azure CLI can be used, and clarify any differences in syntax or prerequisites.
Add Bash shell examples where appropriate, or clarify that the commands can be run from any OS with the Azure CLI installed.
Consider including a table or section that shows both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) command examples side by side.
Review the documentation for other implicit Windows assumptions (such as references to Windows-only tools or terminology) and ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates bias towards Windows/Azure environments by exclusively referencing Azure portal tools and workflows, without providing command-line or Linux-native alternatives. All troubleshooting steps and examples rely on the Azure portal GUI, with no mention of Linux CLI tools, shell commands, or cross-platform approaches. There are no examples or guidance for users who may be operating from Linux systems or prefer automation via CLI.

Recommendations:

Provide equivalent instructions using Azure CLI and/or PowerShell, and ensure Azure CLI examples are prioritized or at least presented alongside portal-based steps.
Include Linux shell command examples (e.g., using curl, jq, or az CLI) for checking resource status, policies, or logs.
Reference cross-platform tools and workflows, not just the Azure portal GUI, to ensure users on Linux or macOS can follow the guidance.
Explicitly mention that all steps can be performed from Linux environments using CLI tools, and provide links to relevant documentation.
Where screenshots are used, consider including text-based outputs or CLI equivalents for accessibility and parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. While the main workflow is cross-platform (using Azure CLI, Docker, and Helm), there are several instances where Windows is mentioned first or exclusively, and some guidance is tailored to Windows users. For example, the note 'If you are using Windows, you must have Docker Desktop running during the publish step' singles out Windows, but does not mention the equivalent for Linux (e.g., Docker Engine). File path examples use Linux-style slashes but explicitly instruct Windows users to use them, rather than showing both formats. There are no explicit Linux command-line examples or troubleshooting notes for Linux users, and the only OS-specific tool mentioned is Docker Desktop (Windows/macOS), with no mention of Linux Docker installation nuances.

Recommendations:

Provide explicit Linux examples or notes where Windows-specific instructions are given (e.g., mention that on Linux, Docker Engine must be running, and provide troubleshooting tips for common Linux Docker issues).
When referencing file paths, show both Windows and Linux formats, or clarify that the CLI expects Linux-style slashes on all platforms.
Avoid mentioning Windows or macOS first; instead, use neutral phrasing or list Linux first to balance representation.
Include a section or note on installing and running Docker on Linux, similar to the note about Docker Desktop for Windows.
Where OS-specific behavior is relevant (e.g., authentication, permissions), provide parity in documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by providing a PowerShell (az CLI) example for deploying the ARM template but omitting equivalent Linux/macOS shell (bash) examples. The only command-line deployment example is shown using PowerShell syntax, and there is no mention of Linux or cross-platform CLI usage, nor are there instructions for using bash or other common Linux tools. The Azure portal is referenced, which is cross-platform, but the CLI example is Windows-centric.

Recommendations:

Provide both PowerShell and bash (Linux/macOS) examples for CLI commands, especially for az deployment group create.
Explicitly mention that the Azure CLI can be used on Windows, Linux, and macOS, and show syntax for both environments where it differs.
Consider using neutral CLI syntax (e.g., $HOME or ~ for home directory, forward slashes in paths) or clarify any OS-specific differences.
Add a note or section for Linux/macOS users, ensuring parity in instructions and examples.
Where possible, use 'az' CLI commands in a way that is copy-paste friendly for all platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows environments by providing only a PowerShell example for resource cleanup, omitting equivalent Azure CLI or Bash commands that would be more familiar to Linux or cross-platform users. The only command-line tool shown is Remove-AzResourceGroup, which is specific to Azure PowerShell (commonly used on Windows). No Linux-native or cross-platform command-line instructions are provided.

Recommendations:

Add equivalent Azure CLI (az group delete) and/or Bash examples alongside the PowerShell command for deleting the resource group.
Explicitly mention that both Azure PowerShell and Azure CLI are supported, and provide links or instructions for both.
Wherever command-line instructions are given, ensure parity by presenting both Windows (PowerShell) and Linux (CLI/Bash) options.
Consider including a table or tabs to let users select their preferred environment (PowerShell, CLI, Bash, etc.).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing ESRI ArcGIS Pro (a Windows-only GIS application) as the example for desktop GIS integration, without mentioning or providing guidance for Linux-compatible GIS tools such as QGIS. No Linux or cross-platform examples are provided for GIS connectivity, and the only desktop workflow described is Windows-centric. Additionally, the related content and integration sections prioritize Windows tools and do not address Linux alternatives.

Recommendations:

Include examples and instructions for integrating with popular cross-platform or Linux-native GIS applications such as QGIS.
Provide sample workflows or connection guides for Linux users, ensuring parity with the ArcGIS Pro (Windows) guidance.
Explicitly mention support for non-Windows environments in all relevant sections, especially in GIS connectivity.
Add related content links for Linux and cross-platform tools, not just Windows-based applications.
Where possible, use generic or cross-platform terminology and avoid assuming the use of Windows-only software.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias, particularly in the section about monitoring App Services with the New Relic agent. It explicitly states that App Service extensions are only supported for Windows, and App Services running on Linux are not displayed or supported. There are no Linux-specific instructions, examples, or parity in tooling or guidance for Linux-based environments. The documentation also omits any mention of Linux command-line tools or patterns, and the only supported scenario for App Services is Windows.

Recommendations:

Provide clear guidance and examples for monitoring Linux-based App Services, or explicitly state the roadmap or alternatives for Linux users.
If Linux support is not available, add a prominent note at the top of the relevant sections to inform users early.
Include parity in documentation for Linux environments wherever possible, such as instructions for installing the New Relic agent on Linux VMs or App Services.
Mention and link to any CLI or scripting options (e.g., Azure CLI, Bash) for Linux users, not just portal-based workflows.
If certain features are Windows-only, offer alternative monitoring approaches for Linux users or direct them to relevant resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by prioritizing .NET/NUnit examples (commonly associated with Windows), using XML-based .runsettings files, and omitting explicit Linux or cross-platform CLI instructions. There are no Linux shell, bash, or cross-platform command-line examples, and the documentation does not mention Linux-specific considerations or tools.

Recommendations:

Add explicit Linux/macOS examples, such as using bash or shell commands for Playwright configuration and test execution.
Include instructions for running Playwright tests from the command line on Linux/macOS, not just via .runsettings or TypeScript configs.
Mention cross-platform compatibility and any OS-specific requirements or differences in setup.
If possible, provide parity in examples by showing both Windows (.runsettings/NUnit) and Linux (e.g., CLI, bash, or YAML for CI) configurations side by side.
Clarify that the features and configurations apply equally to Linux environments, and note any exceptions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively describing how to connect to the VM using Remote Desktop Protocol (RDP), which is a Windows-centric approach. There are no instructions for connecting via SSH, which is the standard for Linux VMs. The example assumes the use of IIS (Internet Information Services), a Windows web server, and does not mention Linux alternatives. While both Azure CLI and PowerShell are provided for deployment and management, the post-deployment access and validation steps are Windows-specific.

Recommendations:

Include instructions for connecting to Linux VMs using SSH, including example commands and expected outputs.
Provide examples using a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
Clarify that the steps for connecting and validating the deployment differ for Linux and Windows VMs, and provide parallel instructions for both.
Mention that RDP is specific to Windows VMs and suggest SSH for Linux VMs.
Ensure that screenshots and walkthroughs are not limited to Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first and PowerShell-heavy bias, particularly in the 'Apply Kubernetes Secret Objects' section, where users are instructed to use Azure Cloud Shell and specifically select PowerShell. No equivalent instructions or examples are provided for Linux users or those preferring Bash, despite earlier mentioning Bash for base64 encoding. This may cause confusion or additional effort for Linux users.

Recommendations:

Provide parallel instructions for both PowerShell and Bash environments when using Azure Cloud Shell, including how to select Bash and run the same kubectl commands.
Avoid assuming PowerShell as the default shell; explicitly state that users can use either Bash or PowerShell, and provide command examples for both where differences exist.
Where possible, use shell-agnostic commands (e.g., kubectl) and clarify any differences in syntax or environment setup between Windows/PowerShell and Linux/Bash.
Ensure that all steps, especially those involving command-line operations, are demonstrated for both Windows and Linux users to improve parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for connecting to the VM using Remote Desktop Protocol (RDP), which is a Windows-centric tool. The cleanup step uses a PowerShell cmdlet (Remove-AzResourceGroup) without mentioning an equivalent Azure CLI or Bash command. There are no examples or guidance for Linux users (e.g., SSH access), and Windows tools and patterns are mentioned exclusively and before any Linux alternatives.

Recommendations:

Add parallel instructions for connecting to the VM using SSH, including steps for Linux and macOS users.
Provide Azure CLI or Bash command examples for resource cleanup alongside the PowerShell example.
Mention both RDP (for Windows) and SSH (for Linux/macOS) as options for connecting to the VM, and clarify which OS images are used in the template.
Ensure that all steps that currently reference Windows tools or workflows have Linux/macOS equivalents presented with equal prominence.
Consider including screenshots or code snippets that reflect both Windows and Linux user experiences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows and PowerShell. All command-line instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The virtual machine created is explicitly a Windows Server VM, and the connectivity test steps assume the use of Windows PowerShell and SQL Server Management Studio (a Windows-only tool). There are no examples or guidance for Linux users, nor are cross-platform tools (like Azure CLI or Data Studio) mentioned.

Recommendations:

Provide parallel instructions using Azure CLI (az commands) and Bash for all resource creation steps.
Include an example for creating a Linux VM and connecting from it, using native Linux tools (e.g., sqlcmd, Azure Data Studio, or ODBC).
When testing connectivity, show how to use nslookup or dig on Linux, and how to connect to SQL Server using cross-platform tools.
Mention and link to cross-platform tools (e.g., Azure Data Studio) as alternatives to SQL Server Management Studio.
Avoid assuming the use of Windows-only tools or workflows; present both Windows and Linux options side by side.
Consider renaming the tutorial or clearly indicating its Windows focus if Linux parity is not intended.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by referencing PowerShell for site creation and management, and by mentioning tools and workflows (such as Power BI) that are primarily associated with Windows. There are no Linux or cross-platform CLI examples, and Linux-native tools or workflows are not discussed. This may make it harder for Linux users to follow or replicate the instructions.

Recommendations:

Provide equivalent CLI examples using Azure CLI (az), Bash, or other cross-platform tools alongside PowerShell examples.
Explicitly mention Linux support and provide instructions or scripts that work on Linux systems.
Reference cross-platform tools (e.g., Azure CLI, REST API, or open-source analytics tools) in addition to or instead of Windows-centric tools like PowerShell and Power BI.
Ensure that all automation and scripting guidance is available in both PowerShell and Bash (or at least Azure CLI) formats.
Add a section or note clarifying platform compatibility for all tools and scripts mentioned.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing detailed instructions for connecting to the VM using RDP (a Windows protocol), instructing users to open PowerShell (a Windows shell), and referencing SQL Server Management Studio (a Windows-only tool). There are no examples or alternatives for Linux users, such as SSH access, Bash shell usage, or cross-platform SQL tools. The CLI and PowerShell deployment instructions are presented, but the validation and usage steps are Windows-centric.

Recommendations:

Add instructions for connecting to the VM using SSH for Linux/macOS users, including example SSH commands.
Provide examples of running DNS queries using Bash (e.g., 'dig' or 'nslookup' in Linux) in addition to PowerShell.
Suggest cross-platform SQL client tools (such as Azure Data Studio or sqlcmd) and provide connection instructions for those.
Include both RDP (Windows) and SSH (Linux/macOS) connection methods in the 'Connect to a VM' section.
Ensure that all validation and cleanup steps have both Windows and Linux command examples where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Windows PowerShell commands for connectivity testing, referencing Windows-specific tools (such as Microsoft Azure Storage Explorer with a Windows tab), and omitting equivalent instructions or examples for Linux users. All command-line and tool installation steps assume a Windows environment, with no mention of Linux alternatives or parity.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using bash and nslookup or dig) alongside PowerShell examples.
Include instructions for installing and using Microsoft Azure Storage Explorer on Linux, or mention cross-platform compatibility.
Explicitly state that the tutorial applies to both Windows and Linux VMs, and provide steps for both where relevant.
When referencing tools or commands, avoid assuming a Windows environment by default; present both Windows and Linux options in parallel.
Add screenshots or terminal output examples from Linux environments to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by specifying a Windows PC and Windows Administrator account as prerequisites, listing PowerShell as a required tool, and referencing Windows-specific technologies (e.g., WinRM, Windows Server Failover Clustering). There are no Linux equivalents or alternatives mentioned for these requirements, and no Linux-specific instructions or examples are provided. The documentation assumes a Windows environment throughout, even though Azure CLI and kubectl are cross-platform tools.

Recommendations:

Update the prerequisites to include support for Linux and macOS platforms, clarifying that Azure CLI and kubectl are cross-platform.
Provide Linux (and optionally macOS) equivalents for all steps, including installation instructions for required tools (Azure CLI, kubectl, PowerShell) on those platforms.
Where PowerShell is required, clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide usage examples.
For steps referencing Windows-specific technologies (e.g., WinRM, Windows Server Failover Clustering), explain if/how these steps can be performed from Linux/macOS, or provide alternative approaches.
Avoid language that assumes the user is on Windows (e.g., 'A Windows PC with internet access'), and instead use inclusive phrasing such as 'A computer with internet access (Windows, Linux, or macOS)'.
Add explicit notes or callouts wherever a step is only supported or tested on Windows, and provide a roadmap or workaround for users on other platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on Windows-based workflows: it instructs users to connect to the VM via RDP (a Windows protocol), open PowerShell (a Windows shell), and install SQL Server Management Studio (a Windows-only tool). No Linux alternatives or cross-platform instructions are provided for connecting to the VM, running DNS queries, or accessing the SQL database. The cleanup step uses a PowerShell cmdlet without mentioning Azure CLI or Bash equivalents.

Recommendations:

Provide alternative instructions for connecting to the VM using SSH, which is standard on Linux and also available on Windows.
Include examples of running DNS queries using Linux tools (e.g., dig or nslookup in Bash) in addition to PowerShell.
Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) alongside SQL Server Management Studio.
Offer resource cleanup instructions using Azure CLI (az group delete) and Bash, not just PowerShell.
Clearly indicate when instructions are Windows-specific and provide parallel steps for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-centric DNS concepts (such as conditional forwarders and DNS forwarders) and linking to Windows Server documentation for DNS configuration. There are no explicit Linux or cross-platform DNS server examples, nor are Linux-native DNS solutions (like BIND or dnsmasq) mentioned. The guidance assumes familiarity with Windows DNS paradigms and omits Linux-specific configuration steps or references.

Recommendations:

Include explicit examples and references for configuring DNS forwarding and conditional forwarding using popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
Provide links to both Windows and Linux DNS server documentation when discussing DNS forwarders and conditional forwarders.
Add sample configuration snippets for Linux-based DNS servers alongside any Windows Server or Azure Firewall examples.
Use neutral terminology (e.g., 'DNS server' instead of 'DNS forwarder') and clarify that both Windows and Linux DNS solutions are supported.
Ensure diagrams and scenario descriptions mention cross-platform DNS options, not just Windows-centric tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (Export/Import), mentioning AzCopy (primarily a Windows tool) without Linux alternatives, and providing no Linux or cross-platform command examples. Windows-specific tools and patterns are mentioned before or instead of Linux equivalents, and there are no explicit Linux instructions or examples for migration steps.

Recommendations:

Provide equivalent CLI examples using Azure CLI (az redis ...) alongside or instead of PowerShell cmdlets.
Mention and provide examples for using AzCopy on Linux/macOS, or suggest alternative tools (such as rsync, scp, or Azure CLI storage commands) for copying RDB files.
Explicitly state that all migration steps can be performed from Linux, and provide sample shell commands (bash) for relevant steps.
Where PowerShell is referenced, add parallel instructions for Linux environments.
Include a table or section comparing Windows and Linux approaches for common migration tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and PowerShell is referenced as a primary management tool throughout. There is no mention of Linux-specific shell usage or examples, and the CLI examples, while cross-platform, are not explicitly shown in a Linux/bash context. Additionally, some CLI example descriptions mistakenly refer to 'Azure PowerShell command' instead of 'Azure CLI command', reinforcing the Windows-centric perspective.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) first to better serve Linux users.
Explicitly mention that Azure CLI commands can be run in Bash (Linux/macOS) and provide sample commands in bash syntax (e.g., with export statements, bash variables).
Correct any mislabeling of CLI examples as 'Azure PowerShell command' to avoid confusion.
Where possible, include notes or examples for Linux/macOS users, such as using bash variables instead of PowerShell variables.
Add a section or note about installing and using Azure CLI on Linux/macOS, and clarify that PowerShell is optional for management tasks.
Ensure screenshots and output samples are not exclusively from Windows environments (e.g., avoid showing only PowerShell output).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it mentions Linux in one section (TCP settings for Linux based client applications), most troubleshooting steps and examples assume a Windows/.NET/StackExchange.Redis environment. There is a strong focus on Windows-specific tools and patterns (e.g., performance counters, NuGet, RedisSessionStateProvider XML config), and no Linux-specific monitoring or troubleshooting examples are provided. Powershell or Windows-centric terminology appears first or exclusively in several sections, and Linux equivalents (such as using top, htop, or Linux system metrics) are missing.

Recommendations:

Add Linux-specific examples for monitoring CPU and network bandwidth (e.g., using top, htop, sar, ifstat, or netstat).
Provide equivalent Linux configuration and troubleshooting steps alongside Windows/.NET examples, especially for client-side monitoring and configuration.
Include examples for popular Linux Redis clients (e.g., redis-py, Jedis) and their error messages or troubleshooting steps.
When mentioning tools like performance counters or NuGet, also mention and provide instructions for Linux alternatives (e.g., system metrics, pip for Python clients).
Ensure that Linux and Windows troubleshooting steps are presented with equal prominence, ideally side-by-side or in clearly labeled sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows environments, requiring the use of PowerShell, WinRM, and Windows-specific tools for accessing the minishell and managing kubeconfig files. There are no instructions or examples for performing these tasks from Linux or macOS systems, and Windows is assumed as the default and only supported platform for these procedures.

Recommendations:

Provide equivalent instructions for Linux and macOS users, including how to access the minishell or perform similar operations using SSH or other cross-platform tools.
Offer shell (bash) command examples alongside PowerShell, and clarify any platform-specific prerequisites.
Document any platform limitations explicitly, and if Windows is truly required, state this clearly at the beginning of the guide.
Where possible, use platform-agnostic methods for downloading and managing kubeconfig files, or provide alternative workflows for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively referencing PowerShell for command-line operations and omitting any Linux or cross-platform shell examples. The instructions for testing connectivity on the VM assume a Windows OS (PowerShell, Windows-style nslookup output, and browser usage), with no mention of Linux alternatives or commands. There is no guidance for users who may have deployed a Linux VM, nor are there Bash or Linux command equivalents provided.

Recommendations:

Add parallel instructions and screenshots for Linux VMs, including how to open a terminal and run equivalent commands (e.g., 'nslookup' or 'dig' in Bash).
Provide both PowerShell and Bash command examples for connectivity testing.
Clarify that the test VM can be either Windows or Linux, and offer guidance for both scenarios.
Include notes or callouts for any OS-specific steps, such as opening a browser or interpreting command output.
Ensure that any referenced tools (e.g., PowerShell) are paired with their Linux equivalents (e.g., Bash, Terminal) where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by instructing users to open Windows PowerShell on the test VM and providing only a PowerShell-based workflow for DNS testing. There are no Linux or cross-platform command-line examples, and the test VM's OS is implicitly assumed to be Windows. This may disadvantage users who prefer or require Linux-based environments.

Recommendations:

Include explicit instructions and examples for both Windows and Linux virtual machines when testing DNS resolution (e.g., show how to use nslookup or dig in Linux shells).
When instructing users to open a shell, use neutral language such as 'open a terminal' and specify both Windows PowerShell and Linux Bash equivalents.
Provide example outputs for both Windows and Linux command-line tools.
Clarify that the test VM can be either Windows or Linux, and offer guidance for both OS types throughout the tutorial.
Where browser instructions are given, note any differences in default browsers between Windows and Linux, or use browser-neutral language.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell explicitly, while not offering equivalent examples for Linux environments (e.g., Bash scripting). The CLI example is present but lacks explicit Linux context or shell usage, and PowerShell is often listed before CLI. There are no Linux-specific instructions or considerations, and the validation steps focus on PowerShell and the Azure Portal, omitting Bash or cross-platform scripting guidance.

Recommendations:

Add Bash shell examples alongside PowerShell for all command-line instructions, especially for enabling and validating High Scale Private Endpoints.
Ensure CLI examples are explicitly shown in a Linux/Bash context, including export statements and shell syntax.
When listing multiple command-line options, alternate the order or present CLI/Bash before PowerShell to avoid 'windows_first' bias.
Include a section or tab for Linux users, highlighting any OS-specific considerations or differences.
Review validation steps to ensure parity for Linux users, such as using Azure CLI in Bash to validate configuration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows development environments. It assumes the use of Visual Studio (a Windows-centric IDE), references .NET Framework (not .NET Core/.NET 5+ which are cross-platform), and provides instructions specific to Windows workflows (e.g., right-clicking in Visual Studio, editing app.config). There are no examples or guidance for Linux or cross-platform development environments, such as using VS Code, the .NET CLI, or running the sample on Linux/macOS.

Recommendations:

Add instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
Include guidance for using cross-platform editors like Visual Studio Code.
Mention .NET (Core/5/6/7+) as an alternative to .NET Framework for cross-platform compatibility.
Provide Linux/macOS-specific instructions for installing prerequisites and running the sample.
Avoid assuming the use of Visual Studio or Windows-specific workflows; present cross-platform alternatives first or alongside.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section with detailed examples, and its capabilities (such as selective enabling of policies) are highlighted. The PowerShell example appears before the CLI example, and the CLI section notes its limitations compared to PowerShell. There is no mention of Linux-specific tools or shell environments, and the CLI examples, while cross-platform, are presented after PowerShell and described as less capable.

Recommendations:

Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) to reinforce cross-platform support.
Where PowerShell-specific features are discussed, clarify if and how they can be achieved using Azure CLI or other cross-platform tools, or note the limitation clearly.
Consider including Bash or shell script snippets for common tasks, or at least acknowledge the typical Linux workflow.
Avoid language that positions PowerShell as the primary or most capable tool unless this is strictly true for the scenario.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by listing PowerShell and Azure portal instructions before or alongside Azure CLI, with no explicit Linux or cross-platform command-line examples. The SDK example is .NET-focused, which is more common on Windows. There are no Linux-specific instructions or examples, and the documentation does not mention or show parity for Linux/macOS environments.

Recommendations:

Provide explicit Linux/macOS command-line examples, especially for authentication steps (e.g., using Azure CLI on Bash).
List Azure CLI instructions before PowerShell, or present them side-by-side, clarifying cross-platform compatibility.
Include SDK usage examples for other popular cross-platform languages (such as Python or JavaScript), not just .NET.
Mention that Azure CLI is available on all major platforms and highlight any differences in usage between Windows and Linux/macOS.
Where portal instructions are given, clarify that the Azure portal is web-based and platform-independent.
Review all examples to ensure that none assume a Windows environment by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias, particularly in the 'Data Persistence or Data Backup' section, where PowerShell is mentioned as a tool for triggering data export before CLI or SDKs, and no explicit Linux or cross-platform command-line examples are provided. There are no Linux-specific tools or patterns mentioned, and the guidance on tooling is not platform-neutral. The absence of Linux/Bash examples and the ordering of PowerShell before CLI suggest a Windows-first approach.

Recommendations:

When listing tools or command-line interfaces, mention cross-platform options (like Azure CLI) before platform-specific ones (like PowerShell).
Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) where relevant, especially for common operations like data export/import.
Explicitly state when a tool or method is cross-platform, and provide links to relevant documentation for both Windows and Linux users.
Avoid assuming the use of Windows-specific tools or patterns unless the majority of the audience is known to be on Windows.
Add a section or callout for Linux/macOS users if there are any differences or additional considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets for export/import operations, linking to PowerShell documentation, and mentioning a compiled Windows binary for a migration tool before its source code. There are no explicit Linux/bash examples or references to Linux-native tools, and the order of presentation favors Windows-centric approaches.

Recommendations:

Provide equivalent bash/CLI examples for export/import operations, not just PowerShell.
Link to both Windows and Linux instructions or clarify cross-platform compatibility for CLI commands.
When mentioning downloadable tools, indicate if they are cross-platform or provide Linux build instructions.
Avoid referencing only PowerShell cmdlets; include Azure CLI and bash scripting alternatives.
Explicitly state OS compatibility for all tools and commands, and ensure Linux users are not left out of migration guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples before Azure CLI, mentioning PowerShell scripting for automation, and omitting any Linux-specific shell (e.g., Bash) or cross-platform scripting examples. There is no mention of Linux tools or guidance for Linux users, and the scripting automation section only references PowerShell and Azure CLI, with PowerShell listed first.

Recommendations:

Provide Bash shell examples alongside PowerShell and Azure CLI for all command-line instructions.
When discussing automation, mention Bash scripts and Linux cron jobs as alternatives to PowerShell scripting.
Alternate the order of examples (sometimes show Azure CLI or Bash first) to avoid always privileging Windows/PowerShell.
Explicitly state that Azure CLI commands work cross-platform and, where relevant, show example commands in both Windows (PowerShell) and Linux (Bash) syntax.
Add a note or section for Linux/macOS users, clarifying any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell scripts and examples, referencing Windows-specific issues (such as the Windows path length limit), and highlighting tools and workflows (like PowerShell and Azure Storage Explorer) that are more familiar to Windows users. There are no explicit Linux shell (bash) or cross-platform CLI examples, and Linux-specific considerations are absent.

Recommendations:

Add explicit bash/Azure CLI examples for all steps where PowerShell is referenced, including SAS generation and file upload.
Provide sample scripts or command lines for Linux/macOS users, not just PowerShell scripts.
Mention Linux/macOS file system considerations where Windows-specific issues (like path length limits) are discussed.
Ensure that references to tools like Azure Storage Explorer are accompanied by notes on their cross-platform availability, or suggest alternative CLI methods.
Where PowerShell scripts are linked, provide equivalent bash or Python scripts for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell examples alongside Azure CLI, but omits explicit Linux/bash examples. PowerShell is used for both deployment and cleanup, and the CLI example references a Bicep file rather than the ARM template file described earlier. There are no bash shell or Linux-specific instructions, and PowerShell is presented as the default scripting language for resource cleanup.

Recommendations:

Add explicit bash/Linux shell examples for deploying and cleaning up resources, using az CLI with ARM template files (e.g., az deployment group create --resource-group exampleRG --template-file azuredeploy.json).
Ensure that CLI examples reference the ARM template file (azuredeploy.json) as described in the instructions, not just Bicep files.
Provide parity in cleanup instructions by including az CLI commands for deleting resource groups (e.g., az group delete --name <resourceGroupName> --yes --no-wait).
Where scripting is shown, offer both PowerShell and bash equivalents, and avoid presenting PowerShell as the default unless the context is Windows-specific.
Consider a tabbed or side-by-side format for all command-line examples, with clear labels for PowerShell, Azure CLI (bash), and, if relevant, Cloud Shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more detailed (including retrieval and removal commands). The documentation refers to 'scripts' and 'commands' in a way that assumes familiarity with PowerShell, and the Azure portal UI instructions use terminology and screenshots that are more familiar to Windows users. There are no explicit Linux-specific instructions or examples, and the CLI examples are not highlighted as the primary or preferred method.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples to avoid implying PowerShell is the default or preferred method.
Ensure parity in the depth and breadth of examples for both PowerShell and Azure CLI, including retrieval and removal operations.
Add explicit notes that both Azure CLI and PowerShell are cross-platform, and clarify that CLI commands work natively on Linux/macOS.
Where possible, include Linux/macOS-specific tips or troubleshooting notes (e.g., shell syntax differences, environment variable usage).
Consider providing Bash script equivalents for multi-step operations, and clarify that the Azure portal is accessible from any OS.
Avoid using Windows-centric terminology or UI references unless necessary, or provide equivalent guidance for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and PowerShell examples for configuring active geo-replication, but it lists PowerShell as a primary automation method alongside CLI, and does not mention or provide any Linux-specific shell (e.g., Bash) examples. There is no explicit mention of Linux or cross-platform scripting, and PowerShell is traditionally associated with Windows environments, which may give the impression of Windows preference. Additionally, there are no examples or guidance for Linux-native tools or scripting environments.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash or other shells.
Provide example commands using Bash (or generic shell) where appropriate, especially for automation scenarios.
Clarify that PowerShell Core is available cross-platform, but also mention that users on Linux can use Bash and Azure CLI for all operations.
Consider including a section or note for Linux/macOS users, highlighting any differences or confirming parity.
Avoid presenting PowerShell as the only or primary scripting/automation option; ensure CLI/Bash examples are equally prominent.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell as the first and primary scripting example, mentioning Azure PowerShell before Azure CLI in both the introduction and the step-by-step instructions. The only explicit scripting example outside the Azure CLI is for PowerShell, with no mention of Bash, Linux shell, or cross-platform scripting environments. The Azure CLI examples are present, but PowerShell is consistently given prominence, and there are no Linux-specific considerations or examples.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used in Linux environments.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash shell usage where appropriate.
Add a section or note for Linux users, highlighting any platform-specific considerations (such as authentication, environment variables, or prerequisites).
Where PowerShell is referenced, clarify that it is available cross-platform, but also provide equivalent Bash or shell script examples for Linux users.
Ensure that documentation metadata and custom tags do not prioritize PowerShell over CLI (e.g., avoid 'devx-track-azurepowershell' without 'devx-track-bash' or similar).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing PowerShell and Windows-centric tools (such as the Azure PowerShell module) before or instead of Linux equivalents. In the section on configuring module parameters, only PowerShell, Azure CLI, and REST API are mentioned, but the PowerShell link is called out explicitly, and there are no Linux-specific shell or scripting examples. There are no bash, shell, or Linux command-line examples or references, and no mention of Linux tools or patterns. This may make Linux users feel less supported or require extra effort to adapt instructions.

Recommendations:

Include explicit bash/shell examples alongside PowerShell for all command-line instructions.
When referencing management tools, mention cross-platform tools (like Azure CLI) first, and clarify their compatibility with Linux/macOS.
Provide links to Linux-specific documentation or examples where available.
Avoid listing PowerShell or Windows tools before cross-platform or Linux-native alternatives.
Add a note clarifying that Azure CLI and REST API are fully supported on Linux, and provide example usage in a Linux shell context.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a connectivity test example using PSPING in PowerShell without offering an equivalent Linux command or tool. The use of PSPING and PowerShell is Windows-specific, and there is no mention of Linux alternatives (such as nc, telnet, or nmap). Additionally, the Windows example appears before any Linux-specific troubleshooting steps, and Linux guidance is limited to a single note about TCP settings, lacking actionable troubleshooting commands.

Recommendations:

Provide Linux equivalents for connectivity testing, such as using 'nc', 'telnet', or 'nmap' to check port connectivity to the Redis instance.
When introducing tools like PSPING, mention both Windows and Linux options together, or present Linux examples first if the majority of Azure workloads are Linux-based.
Expand the 'Linux-based client application' section to include actionable troubleshooting steps and commands, not just a reference to a GitHub issue.
Where possible, use cross-platform tools (like redis-cli) as primary examples, and clearly indicate platform-specific instructions in separate subsections.
Review the order of examples to ensure Linux and Windows are given equal prominence, or alternate which platform appears first in each section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows development, specifically targeting Visual Studio, Windows SDK, and UWP. All instructions, tools, and code samples are tailored exclusively for Windows, with no mention of Linux or cross-platform alternatives. There are no Linux equivalents or guidance for non-Windows environments.

Recommendations:

Add a section or parallel tutorial for Linux users, outlining how to set up a similar development environment using cross-platform tools (e.g., CMake, GCC/Clang, VS Code).
Provide code samples and project setup instructions for Linux, including how to link dependencies and manage project files outside of Visual Studio.
Mention and, where possible, support cross-platform graphics APIs or abstractions (e.g., OpenGL, Vulkan) alongside DirectX11.
Reference cross-platform package managers (e.g., vcpkg, Conan) for dependency management instead of only NuGet.
Clarify early in the documentation that the tutorial is Windows-specific, and provide links or guidance for users on other platforms.
If Remote Rendering is not supported on Linux, explicitly state this and provide any available workarounds or roadmap information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows and Microsoft-specific technologies. All code samples and API references assume the use of Direct3D 11 (D3D11), Windows Mixed Reality, and HoloLens 2, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for using OpenGL, Vulkan, or Linux-based systems, nor any mention of how to set up or use Azure Remote Rendering on non-Windows platforms. The documentation also assumes the use of Windows-specific APIs and tools (e.g., NuGet, ID3D11Device, ISpatialCoordinateSystem), and does not provide parity for Linux users.

Recommendations:

Add explicit information about platform support, including whether Linux is supported and, if not, state this clearly.
If Linux or cross-platform support is available, provide equivalent examples using OpenGL, Vulkan, or other non-Windows graphics APIs.
Include setup and usage instructions for Linux environments, including any required dependencies or differences in workflow.
Mention Linux tools or package managers (e.g., apt, yum) where NuGet is referenced for Windows.
If only Windows is supported, clarify this at the beginning of the documentation to set user expectations.
Consider providing a roadmap or guidance for users interested in non-Windows support, or link to relevant community resources.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing PowerShell as a deployment method without mentioning equivalent Linux/CLI options, and by omitting Linux-specific or cross-platform command examples. The guidance assumes use of PowerShell or the Azure Portal, with no explicit mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS platforms.

Recommendations:

Include Azure CLI (az) command examples alongside or before PowerShell examples for all deployment and migration steps.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI, not just PowerShell or the Portal.
Add Bash scripting examples where automation is discussed, to ensure Linux users have parity.
Where the Portal is referenced, clarify that it is platform-agnostic, and provide CLI alternatives for users who prefer command-line interfaces.
Review the documentation for any implicit assumptions about the user's operating system and update language to be inclusive of all platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias. For example, in the table, the only explicit tool-based deployment example is 'Deploy an Azure Firewall with Availability Zones using Azure PowerShell', with no mention of Linux CLI equivalents (e.g., Azure CLI or Bash). There is a general preference for Windows-centric tools (PowerShell) and terminology, and no Linux-specific or cross-platform command-line examples are provided. The ordering and selection of examples suggest a Windows-first approach, and Linux parity is lacking.

Recommendations:

For every PowerShell-based guide or example, provide equivalent Azure CLI (az) or Bash examples to ensure Linux and cross-platform users are supported.
Where possible, use neutral, cross-platform tools (such as Azure CLI) in examples and documentation, or present both Windows and Linux approaches side-by-side.
Review all linked reliability guides to ensure that Linux and macOS users are not excluded by tool choice or instructions.
Explicitly mention cross-platform compatibility in introductory sections and link to platform-specific instructions where relevant.
Avoid using Windows-specific terminology or tools as the default unless there is no cross-platform alternative.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing PowerShell scripts as the only code sample in the 'Next steps' section and not providing equivalent Linux/bash examples. There are no explicit Linux or cross-platform command-line examples, and the only script-based guidance is Windows-centric. Additionally, there is no mention of Linux tools or instructions for non-Windows environments.

Recommendations:

Add equivalent bash or shell script examples alongside PowerShell scripts in the 'Next steps' and sample sections.
Explicitly mention that authentication steps and REST calls can be performed from any OS, and provide curl or wget examples for token retrieval.
Include references to cross-platform tools (e.g., Azure CLI, curl) and ensure that instructions are not limited to Windows environments.
Where PowerShell is referenced, add a note or link to Linux/macOS alternatives to ensure parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally avoids platform-specific instructions, but in the Azure Storage section (especially for Azure Files), it references Windows-centric tools and patterns such as Azure PowerShell and Azure File Sync (which is Windows-only), and provides a sample script that is likely Windows-oriented. There are no explicit Linux/CLI examples or mentions of Linux-compatible tools for file sync or scripting, and Windows tools are listed before cross-platform alternatives.

Recommendations:

Where Azure PowerShell is mentioned, also provide equivalent Azure CLI commands and examples for Linux/macOS users.
When referencing Azure File Sync (which is Windows-only), clearly state its platform limitation and suggest alternative cross-region sync methods for Linux environments (e.g., rsync, AzCopy, or third-party tools).
For sample scripts (such as syncing between file shares), provide both PowerShell and Bash (or Python) examples to ensure Linux parity.
In lists of tools, avoid always listing Windows tools first; alternate or group by platform, and clarify which tools are cross-platform.
Explicitly mention when a feature or tool is only available on Windows, and provide guidance for Linux users where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a PowerShell-only example for updating job definitions, with no equivalent CLI or Linux-native example. It references Azure PowerShell and Hybrid Compute (typically Windows-centric) resources, but does not mention or provide parity for Linux users or tools such as Azure CLI or bash scripts. This creates a bias toward Windows and PowerShell users, making it less accessible for Linux administrators.

Recommendations:

Provide equivalent Azure CLI (az) examples alongside PowerShell for all resource management tasks, especially for updating job definitions.
Explicitly mention that the agent and management operations can be performed from Linux environments, and provide bash or shell script examples where appropriate.
Clarify whether Hybrid Compute resources are required to be Windows-based, and if not, provide Linux deployment guidance.
Ensure that all instructions referencing the Azure portal or PowerShell also include steps for Azure CLI and REST API usage.
Add a section or note highlighting cross-platform support and linking to Linux-specific agent deployment or management documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias: Windows tools and paths are often mentioned first or exclusively, and some operational examples are missing for Linux. For example, the PowerShell cmdlet Register-AzResourceProvider is referenced before the equivalent Azure CLI command, and the command to check the status of sapstartsrv is only given for Windows, not Linux. File paths for both OSes are listed, but operational commands are more detailed for Windows.

Recommendations:

Provide Linux equivalents for all operational commands, such as checking the status of sapstartsrv, not just for Windows.
When referencing tools or commands (e.g., Register-AzResourceProvider), present the Azure CLI version first or alongside PowerShell to avoid Windows-first bias.
Ensure that all examples and instructions are given for both Linux and Windows, especially since SAP systems are commonly deployed on Linux.
Where file paths or commands differ by OS, always present both together and with equal detail.
Consider adding a table or section that summarizes OS-specific steps for clarity and parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows development environments. All prerequisites and instructions assume Windows, including the use of the Windows SDK, Visual Studio (Windows-only), and Windows-specific tools for Mixed Reality. The command-line instructions reference Windows command prompt and PowerShell scripts, with no mention of Linux or macOS equivalents. There are no examples or guidance for users on Linux or macOS platforms.

Recommendations:

Provide a section or callout for Linux/macOS users, clarifying platform support for Azure Remote Rendering with Unity.
If supported, include Linux/macOS equivalents for all command-line instructions (e.g., bash/zsh commands instead of cmd/PowerShell).
List cross-platform tools where possible (e.g., VS Code instead of Visual Studio, or mention Rider/MonoDevelop for Unity development).
Clarify whether the Windows SDK and Mixed Reality tools are strictly required, or if alternatives exist for other platforms.
Explicitly state platform limitations early in the prerequisites if only Windows is supported, to set user expectations.
If PowerShell scripts are required, provide alternative scripts or manual steps for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively references Windows-specific tools and scenarios, such as HoloLens 2 and Windows Mixed Reality (WMR) VR headsets, without mentioning Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or equivalent tooling discussed, and Windows tools are presented as the default or only option.

Recommendations:

Add information about whether Holographic Remoting and Azure Remote Rendering are supported on Linux, and if not, clarify this explicitly.
If Linux or cross-platform workflows exist (e.g., Unity Editor on Linux), provide equivalent instructions or note any limitations.
Mention alternative VR headsets or remoting solutions that are compatible with Linux, if available.
Rephrase sections to avoid assuming the user is on Windows, or clearly state platform requirements at the beginning.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell scripts for interacting with the REST API, mentioning only Windows-centric tools and scripting languages (PowerShell, .NET), and omitting equivalent Linux or cross-platform examples (such as Bash, curl, or Python). There is no mention of Linux command-line tools or scripts, nor are there links to Linux-specific guidance or parity in SDK coverage.

Recommendations:

Provide equivalent Bash or shell script examples for Linux users, demonstrating how to interact with the REST API using curl or httpie.
Include references to cross-platform tools and scripting languages, such as Python, with sample scripts.
Mention Linux and macOS compatibility explicitly where relevant, and ensure that SDKs and tools are described in a platform-neutral manner.
Add links to Linux-specific documentation or samples, or clarify if the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS.
Reorder examples and tool mentions to avoid always listing Windows-first (e.g., mention both PowerShell and Bash, or .NET and Java, in parallel).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric, listing only Windows as a supported desktop platform, referencing only Windows tools (Visual Studio, Windows SDK, Microsoft Store, HEVC Video Extensions), and providing no mention of Linux or macOS support or alternatives. All instructions, requirements, and troubleshooting steps assume a Windows environment, with no Linux equivalents or cross-platform guidance.

Recommendations:

Clearly state whether Linux and macOS are unsupported, or provide information on their support status.
If Linux/macOS are supported or planned, add equivalent instructions for installing dependencies (e.g., Unity, Git, codecs) on those platforms.
Mention cross-platform alternatives to Windows-only tools (e.g., Visual Studio Code instead of Visual Studio, open-source codecs instead of Microsoft Store HEVC extensions).
Provide troubleshooting steps and requirements for Linux/macOS if applicable.
If only Windows is supported, add a prominent note at the top of the page clarifying this to set user expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page provides detailed instructions and examples for removing resources from a move collection in Azure Resource Mover, but all command-line examples use PowerShell cmdlets, which are primarily associated with Windows environments. There are no examples using Azure CLI, Bash, or other cross-platform tools, and no mention of Linux or macOS workflows. The exclusive use of PowerShell and lack of alternative examples creates a Windows-centric bias.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the operations can be performed on any OS using Azure CLI or REST API, not just via PowerShell.
Include Bash shell examples where relevant, especially for bulk or scripting operations.
Reorganize sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.
Add a note clarifying that PowerShell is available on Linux and macOS, but provide guidance for users who prefer native Linux tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias, particularly in the Diagnostics section, where only Windows-specific tools such as Event Tracing for Windows (ETW), Event Trace Logging (ETL), and the Windows Device Portal are mentioned for tracing and diagnostics. There are no equivalent Linux or cross-platform diagnostic tools referenced, nor are Linux-specific instructions or examples provided. Additionally, OneDrive integration is highlighted, which is more closely associated with Windows environments, and there is a general absence of Linux or cross-platform perspectives throughout the document.

Recommendations:

Include Linux and cross-platform equivalents for diagnostics, such as referencing syslog, strace, perf, or open-source tracing tools (e.g., LTTng, SystemTap) for Linux users.
When mentioning Windows tools (e.g., ETW, Windows Device Portal), also provide guidance or links for achieving similar diagnostics on Linux and macOS.
Add examples or references for Linux-based workflows, such as using Azure CLI or PowerShell Core on Linux for session management, analytics, and troubleshooting.
Avoid assuming OneDrive is the default or only file storage option; mention alternatives like Dropbox, Google Drive, or generic SFTP/SMB/NFS solutions that are platform-agnostic.
Where possible, use neutral language and ordering (e.g., 'Windows, Linux, and macOS' instead of 'Windows and others') to avoid the impression of Windows-first thinking.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and providing a quickstart link for PowerShell, while not mentioning or linking to any Linux or cross-platform CLI alternatives. There are no Linux-specific instructions or examples, and the use of PowerShell is highlighted before any other automation or scripting options.

Recommendations:

Include equivalent quickstart links and instructions for the Azure CLI, which is cross-platform and commonly used on Linux.
Avoid referencing PowerShell as the only scripting/automation option; mention Azure CLI and Bash where appropriate.
Provide examples or notes for Linux users, especially for steps that may differ (such as certificate management or connectivity checks).
Ensure that any screenshots or diagrams do not assume a Windows environment unless necessary.
Review all prerequisite and setup steps to ensure parity for Linux and Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows tools (Visual Studio, Windows SDK, UWP), and provides only Windows command-line and PowerShell references. There are no Linux or cross-platform alternatives mentioned for building, deploying, or managing sessions. All instructions and prerequisites assume a Windows development environment.

Recommendations:

Add a section or note clarifying whether Linux or macOS development is supported or not. If not, state this explicitly.
If cross-platform development is possible, provide equivalent instructions for Linux (e.g., using CMake, VS Code, or other IDEs) and mention any required dependencies.
Include Linux/macOS command-line examples for cloning the repository and managing files (e.g., bash equivalents for mkdir/cd/git).
If session management can be done via REST API or cross-platform scripts, provide examples using curl or Python instead of only referencing PowerShell scripts.
Mention any platform limitations or alternatives for developers not using Windows, and provide guidance or links to relevant resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most closely associated with Windows workflows), providing only .NET/C# code samples (which are most common on Windows), and omitting Linux-specific examples or command-line authentication flows. While Azure CLI is mentioned in the 'Next steps', the main authentication and role assignment instructions focus on portal and .NET SDK usage, with no parity for Linux-native tools, languages, or shell environments.

Recommendations:

Add equivalent authentication code samples using cross-platform languages such as Python (with azure-identity and azure-servicebus), Java, or Node.js.
Include examples of using Azure CLI (az login, az ad sp create-for-rbac, etc.) for authentication and role assignment, showing commands runnable on Linux/macOS.
Provide guidance for authenticating from Linux-based environments, such as using managed identities on Linux VMs, containers, or Azure Functions running on Linux.
Reference Linux-friendly editors and environments (e.g., VS Code, bash) alongside or instead of Windows-centric tools.
Ensure that all screenshots and step-by-step instructions are not specific to the Windows Azure portal experience, or clarify that the portal is cross-platform.
Where .NET is used, add parallel samples for other languages/platforms that are popular on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (Windows Device Portal), using Windows-style file paths (User Folders\LocalAppData\...), and omitting any mention of Linux or macOS equivalents for accessing files or running the ArrInspector. There are no instructions for users running the application on Linux or macOS, nor are there alternative file path formats or tools mentioned.

Recommendations:

Include instructions for accessing the StartArrInspector.html file on Linux and macOS, specifying typical file locations and methods for retrieval.
Provide cross-platform file path examples (using forward slashes and environment variables where appropriate).
Mention and link to any Linux/macOS equivalents to the Windows Device Portal, or clarify if such functionality is unavailable.
Explicitly state platform limitations if the tool is only supported on Windows, or otherwise ensure parity in documentation for all supported platforms.
Add a section or note addressing how non-Windows users can launch and use ArrInspector, or clarify if only Windows is supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is explicitly and exclusively focused on Windows-based SQL Server deployments for SAP workloads on Azure. It repeatedly states that SAP does not support SQL Server on Linux for SAP software, and all configuration, operational, and example sections assume Windows Server as the guest OS. All instructions, tooling, file system references (NTFS, D:\ drive), and high-availability patterns (Always On, clustering) are Windows-centric. There are no Linux equivalents, examples, or even mentions of Linux-based deployment patterns, tools, or file systems. The only mention of Linux is to state it is unsupported for this scenario.

Recommendations:

If SAP support for SQL Server on Linux becomes available, update the documentation to include Linux-based deployment guidance, examples, and parity for all configuration and operational steps.
Where possible, clarify which recommendations are Windows-specific and which are general best practices for SQL Server on Azure, to help users understand what is OS-dependent.
Include a section or callout for customers interested in Linux-based SQL Server deployments, even if only to direct them to current support status or alternative documentation.
For parity, provide Linux equivalents for file system, disk formatting, and high-availability patterns (e.g., XFS/ext4, mdadm/LVM, Linux clustering/HA options) if/when supported.
Avoid assuming Windows-only patterns (such as D:\ drive, NTFS, Windows command line) without noting their OS specificity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally focuses on Oracle on Linux as the primary and recommended platform for SAP on Azure, with detailed configuration, tuning, and deployment guidance for Oracle Linux. However, there is some evidence of Windows bias in the structure and presentation: Windows-specific sections and tools (e.g., Windows Storage Spaces) are presented in dedicated sections, and Windows recommendations are summarized separately, sometimes after Linux. There are also references to Windows tools and patterns (e.g., NTFS, Windows Storage Spaces, Windows Tuning guides), and some configuration tables and examples are provided for Windows. However, Linux is clearly the preferred and more deeply documented platform, with more extensive examples and recommendations. There are few, if any, PowerShell or Windows command-line examples, but the Windows configuration is described in detail. In some cases, Windows considerations are mentioned after Linux, but the parity of detail is not always maintained.

Recommendations:

Ensure that Linux and Windows configuration sections are equally detailed, with parallel structure and equivalent examples for both platforms.
Where Windows-specific tools or patterns are mentioned (e.g., Storage Spaces, NTFS), provide Linux equivalents (e.g., LVM, ext4/XFS) in the same context.
If providing configuration tables for Windows, ensure Linux tables are presented with the same level of detail and vice versa.
Include example commands for both Linux (bash, systemctl, etc.) and Windows (PowerShell, cmd) where relevant, or clarify when a step is platform-specific.
Review the order of presentation: if Linux is the primary supported platform, clarify this early and consistently, but avoid relegating Windows to an afterthought—ensure both are treated as first-class options where supported.
Where features are not supported on Windows (e.g., ASM), explicitly state this and provide alternative best practices for Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (Mixed Reality Feature Tool), providing only PowerShell scripts for automation, and omitting Linux/macOS equivalents or instructions. All example commands and scripts are either Windows-native or assume a Windows environment, with no mention of cross-platform alternatives or guidance for non-Windows users.

Recommendations:

Provide explicit instructions for Linux and macOS users, including equivalent shell commands (e.g., bash) for downloading packages.
If the Mixed Reality Feature Tool is Windows-only, clarify this and suggest manual installation steps for other platforms.
Offer cross-platform scripts or note how to adapt the PowerShell script for other environments (e.g., bash or Python).
List both Windows and Linux/macOS approaches side-by-side where possible, or at least acknowledge platform differences.
Avoid assuming PowerShell is available; provide npm-based workflows as the primary or parallel method, since npm is cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows, introducing Windows tools (ETW, WPR, WPA) first and in detail, with step-by-step instructions and screenshots. Linux and Android equivalents (Perfetto) are only briefly mentioned, with no Linux desktop examples or instructions. The only non-Windows command-line example uses PowerShell, and there is no mention of Linux profiling tools or workflows for non-Quest Linux clients. The documentation assumes Windows as the default environment for profiling and analysis.

Recommendations:

Provide equivalent Linux desktop profiling instructions, e.g., using Perfetto or other Linux tracing tools, for users running ARR clients on Linux.
Include Linux shell (bash) command-line examples for recording and analyzing traces, not just PowerShell.
Present Windows and Linux/Android tools in parallel, rather than introducing Windows tools first and in more detail.
Add screenshots and step-by-step guides for Linux workflows, similar to the Windows sections.
Clarify which tools and workflows are available or recommended for each supported client OS (Windows, Linux, Android, etc.).
If Linux is not supported for client-side tracing, explicitly state this and provide alternatives or workarounds.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC). All operational examples, scripts, and tooling references are for Windows and PowerShell. There is no mention of Linux equivalents, nor are any Linux-based high-availability clustering solutions (such as Pacemaker/Corosync) or Linux command-line examples provided. The documentation assumes a Windows-only context throughout, from infrastructure setup to SAP installation and failover testing.

Recommendations:

Add a parallel section or separate article for Linux-based SAP ASCS/SCS HA with Azure shared disk, using Pacemaker/Corosync or other supported Linux clustering solutions.
Provide Linux command-line examples (e.g., using Azure CLI, shell scripts) for disk creation, attachment, and formatting.
Include instructions for configuring load balancers and health probes in Linux environments, referencing relevant Linux tools and configuration files.
Describe how to set up DNS entries and cluster resources using Linux-native tools (e.g., `crm`, `pcs`, or systemd-resolved).
Reference SAP installation procedures for Linux, including any OS-specific SAP profile or kernel parameter adjustments.
Clearly state at the beginning of the article that it is Windows-specific, and provide a link to Linux documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric: all installation instructions, error messages, and workarounds reference Windows-specific tools and patterns (e.g., ClickOnce, Windows Menu shortcuts). Only Windows is listed as a supported OS, with no mention of Linux or cross-platform alternatives. There are no Linux examples, troubleshooting steps, or parity in system requirements.

Recommendations:

Explicitly state if Linux is unsupported, or provide information on Linux compatibility/workarounds if possible.
If feasible, offer Linux installation instructions or alternatives (e.g., via Mono, Wine, or a native Linux version).
Include troubleshooting steps and error messages relevant to Linux users, or clarify that the tool is Windows-only.
Avoid assuming the presence of Windows-specific features (like the Windows Menu) without noting their absence on other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on Windows Mixed Reality (WMR), Windows-specific APIs, and Direct3D (D3D11) graphics bindings. All examples and configuration steps reference Windows tools and patterns, with no mention of Linux or cross-platform equivalents. There are no Linux-specific instructions, examples, or references to Linux-compatible graphics APIs (such as Vulkan or OpenGL), and the documentation assumes a Windows development environment.

Recommendations:

Add equivalent instructions and examples for Linux platforms, including how to configure LSR modes in Unity and native applications using Linux-supported graphics APIs (e.g., Vulkan, OpenGL).
Reference cross-platform or Linux-compatible XR runtimes and SDKs, such as Monado or SteamVR, where applicable.
Provide code samples and configuration steps that work on Linux, or explicitly state platform limitations if certain features are Windows-only.
Avoid using Windows-specific terminology (e.g., WMR, D3D11) as the default; instead, present cross-platform options first or in parallel.
Include a section outlining platform support and any differences in feature availability or setup between Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a clear Windows bias. The only provided script-based workflow uses PowerShell, with no mention of Linux or cross-platform alternatives. All scripting instructions, configuration paths, and prerequisite tooling are Windows-centric (e.g., backslash paths, PowerShell, Azure PowerShell module). There are no Bash, CLI, or Linux-native instructions or examples. The documentation assumes the user is on Windows, both in terminology and in the tools referenced.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for Linux/macOS users, alongside PowerShell examples.
Use platform-agnostic path examples or show both Windows and Unix-style paths in configuration samples.
Explicitly mention cross-platform support and note any platform-specific limitations or requirements.
Include instructions for installing and using the Azure CLI (which is cross-platform) as an alternative to Azure PowerShell.
Add a section or callout for Linux/macOS users, outlining any differences in setup or usage.
Ensure screenshots and UI instructions clarify when steps are platform-independent (e.g., Azure Portal) versus platform-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed prerequisites for Azure PowerShell (a Windows-centric tool) before Azure CLI, and by listing multiple specific PowerShell modules and versions. The PowerShell section is more prominent and detailed than the Azure CLI section, which is brief. There is no mention of Linux-specific considerations, nor are there examples or notes about using these tools on Linux or macOS. The documentation implicitly assumes a Windows environment by focusing on PowerShell and omitting cross-platform guidance.

Recommendations:

Provide equal detail for Azure CLI as for PowerShell, including any required extensions or modules for CLI.
Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform and can be used on Windows, Linux, and macOS.
Include notes or examples for using these tools on Linux/macOS, such as installation instructions or environment-specific caveats.
Avoid listing PowerShell prerequisites before CLI unless there is a technical reason; consider presenting both options in parallel or in a neutral order.
If there are differences in behavior or prerequisites between platforms, document them explicitly.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed PowerShell-based instructions for modifying destination settings when moving Azure VMs, but does not include equivalent examples for Linux users (e.g., Azure CLI, Bash scripting). The only command-line automation example is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux-native tools or cross-platform alternatives.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell-based instructions, demonstrating how to perform the same tasks using az commands.
Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide guidance for users on Linux/macOS.
Where possible, provide Bash scripting examples or note any differences in workflow for Linux users.
Ensure screenshots and output examples are not PowerShell-specific, or provide parallel examples for CLI.
Consider restructuring the 'Modify settings in PowerShell' section to a more general 'Modify settings using command-line tools', with subsections for PowerShell and Azure CLI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Windows as the supported operating system, with no mention of Linux or cross-platform compatibility. All system requirements and download instructions are Windows-specific, and there are no examples or guidance for Linux users. The tool appears to be Windows-only, and this is reflected throughout the documentation.

Recommendations:

Explicitly state if the tool is Windows-only, and if so, provide rationale or roadmap for Linux/macOS support.
If Linux support is possible (e.g., via Mono or Wine), include installation and usage instructions for Linux.
If the tool is not available on Linux, suggest alternative threat modeling tools that are cross-platform.
Ensure future documentation includes parity in examples, instructions, and troubleshooting for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows environments, both in system requirements and in usage instructions (e.g., using Windows Menu shortcuts, ClickOnce installer). There are no mentions of Linux or cross-platform support, nor are alternative installation or usage instructions provided for non-Windows users.

Recommendations:

Explicitly state if the tool is Windows-only, or provide information about Linux/macOS support or lack thereof.
If possible, offer Linux/macOS installation instructions or workarounds (e.g., via Wine, virtualization, or alternative tools).
Include notes on cross-platform compatibility in the system requirements section.
If the tool is not available on Linux, suggest comparable open-source or Microsoft-supported threat modeling tools for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. The Azure portal (a web UI, but often associated with Windows-centric workflows) is presented first and in greatest detail. PowerShell is given its own dedicated tab with explicit examples, while Linux-native shell or Bash examples are not provided. Although Azure CLI is included (which is cross-platform), there are no explicit Linux/Bash-specific instructions or screenshots, and the PowerShell tab precedes the CLI tab. No mention is made of Linux terminal conventions, and all command-line examples are either PowerShell or Azure CLI (with CLI examples not tailored for Linux users).

Recommendations:

Add explicit Bash/Linux shell examples for all Azure CLI commands, including any necessary environment variable usage or authentication steps common on Linux.
Include notes or sections on running Azure CLI commands in Linux environments, addressing differences in quoting, authentication, and file redirection.
Reorder tabs or sections so that Azure CLI (the most cross-platform tool) appears before PowerShell, or at least give them equal prominence.
Add screenshots or terminal output examples from Linux environments where relevant.
Where the Azure portal is referenced, clarify that it is web-based and not Windows-specific, and consider including browser-agnostic language.
If possible, mention that PowerShell Core is available on Linux, or provide Bash equivalents for PowerShell commands.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows environments, both in system requirements and in usage instructions (e.g., 'Windows Menu', ClickOnce installer, Windows file paths). There are no mentions of Linux or cross-platform support, nor are there alternative instructions or examples for non-Windows users.

Recommendations:

Explicitly state if the tool is Windows-only, or clarify platform support.
If Linux or macOS support is possible or planned, provide installation and usage instructions for those platforms.
If the tool is not supported on Linux, suggest alternatives or workarounds for Linux users (such as running via Wine or using similar open-source tools).
Avoid referencing Windows-specific UI elements (e.g., 'Windows Menu') without noting the absence of equivalents on other platforms.
Include a section on platform compatibility and address common questions from non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a significant Windows bias. Troubleshooting steps and examples are almost exclusively presented for Windows environments, especially in codec installation and file system troubleshooting. PowerShell and Windows Explorer are referenced without Linux or cross-platform alternatives. File system limitations and tools are described only in the context of Windows, and there are no Linux-specific instructions or parity in examples.

Recommendations:

Provide Linux (and macOS, if applicable) equivalents for all command-line instructions, such as using bash or terminal commands instead of only PowerShell.
When referencing file system limitations, include notes about Linux file system behaviors and path length limits.
If certain features or troubleshooting steps are Windows-only, explicitly state this and, where possible, suggest workarounds or alternatives for Linux users.
Include examples or troubleshooting steps for installing codecs and managing permissions on Linux systems.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them under OS-specific headings.
Reference cross-platform tools (e.g., Azure CLI, VS Code) where possible, rather than only Windows-native tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a significant Windows bias by providing only PowerShell-based CLI examples for scripting and automation tasks, with no mention of Azure CLI (cross-platform) or Bash/Linux equivalents. All command-line automation is shown using PowerShell cmdlets, which are native to Windows and less commonly used on Linux or macOS. There is no guidance or parity for users on Linux or macOS platforms, and the documentation implicitly assumes a Windows-centric workflow.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell scripts and tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell examples are provided and offer Bash or shell script alternatives where appropriate.
Reorder sections or provide parallel examples so that both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) users are equally supported.
Include notes or links to documentation on how to install and use Azure CLI on non-Windows platforms.
Consider referencing automation options available in Cloud Shell, which supports both Bash and PowerShell, to highlight cross-platform capabilities.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references Windows operating systems, Windows-specific installation mechanisms (ClickOnce), and Windows UI elements (Windows Menu). There is no mention of Linux or macOS support, nor are any cross-platform installation instructions or troubleshooting steps provided.

Recommendations:

Clearly state platform support, including whether Linux or macOS are supported or not.
If the tool is Windows-only, explicitly mention this early in the documentation to set user expectations.
If cross-platform support is planned or available, provide installation and troubleshooting steps for Linux/macOS, including equivalent commands and UI references.
Where possible, use platform-neutral language or provide parallel instructions for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively targets Windows users, specifying only Windows as a supported operating system and requiring .NET 4.7.1 or later. There is no mention of Linux or macOS support, nor are there any instructions or examples for running the tool on non-Windows platforms. The download and installation instructions are Windows-specific, and the tool itself appears to be a Windows application.

Recommendations:

Clearly state in the documentation whether Linux and macOS are unsupported, and if possible, provide information about alternative tools or workarounds for those platforms.
If there are unofficial or community-supported ways to run the tool on Linux (e.g., via Wine or Mono), document these options with appropriate caveats.
Consider developing and documenting a cross-platform version of the tool or providing equivalent functionality for Linux users.
Add a section addressing frequently asked questions about non-Windows support to improve transparency and user experience for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows Server Failover Clustering (WSFC), Windows tools (such as DNS Manager and Windows Firewall), and PowerShell scripts for Azure resource configuration. There are no references or examples for Linux-based SAP high availability solutions, nor are Linux equivalents or alternative approaches mentioned.

Recommendations:

Add a parallel section or separate documentation for SAP ASCS/SCS multi-SID HA on Linux, using Pacemaker/Corosync and native Linux clustering tools.
Provide equivalent command-line examples for Linux (e.g., using Azure CLI or shell scripts instead of PowerShell).
Mention Linux-supported shared disk and replication solutions (such as STONITH, DRBD, or native Azure shared disks with Pacemaker).
Reference SAP and Azure documentation for Linux-based high availability setups.
Clearly state in the introduction that this guide is Windows-specific, and link to Linux-focused guides if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell examples as the primary (and only) command-line scripting option for querying and managing Azure RBAC resources. References to PowerShell cmdlets (e.g., Get-AzRoleAssignment, Get-MgUser) are given before or instead of Azure CLI equivalents. There is no explicit mention or example of using Bash, Linux shell, or cross-platform scripting, and the only command-line snippets are in PowerShell syntax. Additionally, the documentation refers to 'Azure PowerShell commands' and 'PowerShell' as the default automation tool, which may alienate Linux/macOS users who prefer Bash or Azure CLI.

Recommendations:

Provide Azure CLI (az) command examples alongside PowerShell for all scripting and automation steps, especially for querying and managing role assignments and users.
When referencing command-line tools, mention both PowerShell and Azure CLI, and avoid presenting PowerShell as the default or only option.
Include Bash/Linux shell scripting examples where relevant, or clarify that Azure CLI commands are cross-platform.
In lists or instructions, do not always mention PowerShell before Azure CLI; alternate or present both equally.
Explicitly state that all steps can be performed on Linux/macOS as well as Windows, and link to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell deployment scripts as the mechanism for custom deployment options, without mentioning or providing alternatives for Linux environments (such as Bash or cross-platform scripting). There are no Linux-specific examples or guidance, and the only scripting tool referenced is PowerShell, which is traditionally associated with Windows. No mention is made of running these workflows or scripts in a Linux environment, nor are any Linux-native tools or shell examples provided.

Recommendations:

Explicitly state whether the PowerShell deployment script is cross-platform (e.g., works with PowerShell Core on Linux/macOS) or provide equivalent Bash scripts/examples for Linux users.
Include Linux-specific instructions or examples for customizing deployments, such as using Bash or other common Linux automation tools.
Clarify any platform requirements or limitations for running deployment scripts, and provide guidance for Linux users where necessary.
Where possible, use neutral, cross-platform terminology (e.g., 'script' instead of 'PowerShell script') and provide both Windows and Linux command-line examples.
Add a section or note addressing Linux/macOS users, outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and instructions for deploying and cleaning up resources. There are no examples or instructions for using Azure CLI, Bash, or other cross-platform tools commonly used on Linux/macOS. The workflow assumes the use of Azure Cloud Shell in PowerShell mode, and all scripts and command references are PowerShell-specific. There is no mention of Linux-specific tools or alternative command-line approaches, and the only linked tutorial is also PowerShell-focused.

Recommendations:

Add equivalent Azure CLI (az) command examples for all deployment and cleanup steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
Include Bash script examples for users who prefer scripting in Bash.
Ensure that references to commands and tools are not PowerShell-exclusive; provide links to both PowerShell and CLI documentation where appropriate.
Consider restructuring sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page for Azure Route Server FAQ demonstrates subtle Windows bias. The 'Next steps' section links only to a PowerShell-based quickstart, which is Windows-centric, and there are no Linux or cross-platform CLI examples or references. The documentation does not mention or provide parity for Linux tools or workflows, nor does it reference the Azure CLI, which is cross-platform. This may make it less accessible or welcoming for Linux users.

Recommendations:

Add links to cross-platform Azure CLI (az) quickstart and configuration guides alongside or before PowerShell guides.
Ensure that all example commands and scripts are provided in both PowerShell and Azure CLI/bash formats.
Explicitly mention that Azure Route Server can be managed from Linux/macOS using the Azure CLI, and provide relevant documentation links.
Review all 'Next steps' and instructional links to ensure Linux users are not excluded or made to feel secondary.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows-centric technologies, specifically Azure Stack HCI and System Center Virtual Machine Manager (ScVmm), which are exclusive to Windows environments. There are no Linux-specific examples, roles, or tools mentioned, and the documentation does not address Linux or cross-platform scenarios, despite the 'Hybrid + multicloud' context. The structure and terminology assume a Windows-first audience and omit Linux equivalents or guidance.

Recommendations:

Explicitly state the Windows-only nature of Azure Stack HCI and ScVmm roles at the top of the page, clarifying the lack of Linux support.
If Linux or cross-platform management is possible via Azure Arc or other tools, provide dedicated sections or links to Linux-specific documentation.
Include examples or references for managing hybrid/multicloud environments that include Linux servers, such as using Azure Arc-enabled servers for Linux.
Add a comparison table or guidance for users managing both Windows and Linux resources, highlighting differences and available role-based access controls.
Ensure that future documentation in the 'Hybrid + multicloud' category covers both Windows and Linux scenarios, or clearly scopes content to Windows if Linux is not supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for deploying and cleaning up resources, referencing PowerShell cmdlets and output screenshots, and not including equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots are tailored to a Windows/PowerShell workflow, with no Linux-specific or cross-platform guidance.

Recommendations:

Add Azure CLI examples (using Bash or Cloud Shell) alongside PowerShell for all deployment and cleanup steps.
Include screenshots and instructions that are not specific to PowerShell or Windows environments.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both.
Ensure that references to tools and commands are balanced between Windows and Linux/cross-platform options.
Where possible, provide a tabbed interface or clear separation for PowerShell and CLI/Bash instructions, so users can follow the workflow appropriate for their environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references the use of a PowerShell cmdlet (Unlock-SPOSensitivityLabelEncryptedFile) as the only example of a command-line tool for managing sensitivity labels, with no mention of Linux or cross-platform alternatives. No Linux-specific tools, commands, or usage patterns are provided, and the documentation implicitly assumes a Windows/PowerShell environment for administrative tasks.

Recommendations:

Include equivalent command-line examples for Linux environments, such as using Microsoft Graph API via curl or other cross-platform tools.
Explicitly state whether the administrative tasks (e.g., unlocking sensitivity label encrypted files) can be performed on Linux, and provide guidance or alternatives if available.
Where PowerShell cmdlets are mentioned, add notes or links to REST API documentation or CLI tools that can be used on non-Windows platforms.
Review all examples and references to ensure Linux and macOS users are not excluded from administrative guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, with extensive Linux-specific instructions and examples. However, there is a notable Windows/Azure bias in several areas: (1) The only provided example for creating and attaching Azure shared disks uses PowerShell, with Azure CLI and Portal relegated to a brief mention and no example; (2) Azure-native tooling and patterns (PowerShell, Azure portal, Azure CLI) are referenced throughout, with no Linux-native alternatives for Azure resource management; (3) In some cross-references and links, Windows is mentioned before Linux (e.g., maintenance documentation links), which can subtly reinforce a Windows-first perspective.

Recommendations:

Provide full Azure CLI examples for all resource creation and management steps, especially for creating and attaching shared disks, to ensure Linux users can follow along without needing PowerShell.
Include explicit instructions or links for performing Azure resource management tasks via the Azure Portal and Azure CLI, not just PowerShell.
Where both Linux and Windows are referenced (e.g., maintenance documentation), list Linux first or equally to avoid reinforcing a Windows-first ordering.
Where possible, highlight or link to Linux-native automation tools (such as bash scripts using az CLI) for Azure resource management.
Clarify that PowerShell is cross-platform, but provide guidance for Linux users on installing and using it if it remains the only example.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing file path examples in Windows format (e.g., C:\Users\...), referencing Windows-specific file locations, and omitting equivalent Linux/macOS instructions for saving SSH keys or file paths. The workflow assumes a Windows environment for Visual Studio Code usage and does not provide parallel guidance for Linux users.

Recommendations:

Include Linux/macOS file path examples alongside Windows paths when instructing users where to save SSH keys (e.g., ~/.ssh/weeu_deployer.ssh).
Explicitly mention steps for Linux/macOS users, such as using the terminal to save the SSH key with appropriate permissions (e.g., chmod 600).
When referencing Visual Studio Code commands or shortcuts, note any differences for Linux/macOS platforms.
Provide screenshots or descriptions that are platform-agnostic or include both Windows and Linux/macOS variants where relevant.
Review all instructions to ensure parity for users on non-Windows platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references PowerShell and CLI as the primary interfaces for deploying and managing SAP systems with Azure Center for SAP Solutions, but does not provide explicit Linux/bash examples or mention Linux-native tools. PowerShell is a Windows-centric tool, and its mention without Linux parity can create a perception of Windows bias. There are no screenshots, code snippets, or step-by-step instructions for Linux users, and the documentation does not clarify if all steps are equally supported on Linux platforms.

Recommendations:

Explicitly provide bash/Azure CLI examples alongside or before PowerShell examples for all deployment and registration steps.
Clarify that all CLI commands are cross-platform and provide sample commands in bash syntax.
If PowerShell is required, mention PowerShell Core's cross-platform support and provide installation instructions for Linux.
Include screenshots or terminal output from Linux environments where applicable.
Add a section or note confirming Linux support and parity for all documented procedures.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, and there are no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and prerequisites focus on Azure PowerShell and Cloud Shell, which defaults to PowerShell, and there is no mention of Linux-specific workflows or tools. The documentation does not provide parity for Linux users or those preferring Bash/Azure CLI.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operations.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
Include Linux/Bash-specific instructions for preparing the environment, such as installing Azure CLI on Linux.
Ensure that sample payload file editing instructions are platform-agnostic or include Linux-friendly editors (e.g., nano, vim).
Review all prerequisites and steps to ensure they are not exclusively tailored to Windows/PowerShell users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell and Windows file paths) are mentioned prominently and sometimes before their Linux equivalents. Some instructions and troubleshooting steps provide detailed guidance for Windows (e.g., PowerShell scripts, Windows VM Agent troubleshooting) but lack equivalent detail or parity for Linux users. In some cases, Linux commands are mentioned, but Windows commands are more explicit or prioritized.

Recommendations:

Ensure all examples and instructions are provided for both Windows and Linux environments, with equal detail and prominence.
When referencing PowerShell or Windows tools, always provide the equivalent Bash or Linux-native command, and vice versa.
Avoid listing Windows-specific instructions before Linux equivalents; instead, group them together or alternate their order.
Expand troubleshooting sections to include step-by-step guidance for both Windows and Linux VM agents, not just links for one and details for the other.
Where file paths or commands are given, always show both Windows and Linux syntax side by side.
Review all notes and prerequisites to ensure Linux users are not left with less actionable or less detailed information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments, focusing exclusively on Windows Server Failover Clustering (WSFC), Windows VMs, and Microsoft-specific tools such as PowerShell and Scale-Out File Server. All examples, instructions, and code samples are Windows-centric, with no mention of Linux equivalents, SAP HA on Linux, or cross-platform considerations.

Recommendations:

Add equivalent guidance for deploying SAP ASCS/SCS HA on Linux, including supported clustering technologies (e.g., Pacemaker, Corosync).
Provide Linux-based examples and scripts (e.g., shell commands, Ansible playbooks) alongside PowerShell examples.
Mention and link to documentation for Linux-based SAP HA deployments in Azure, ensuring parity in prerequisites and deployment steps.
Clarify in the introduction that the guide is Windows-specific, and direct users to Linux documentation if available.
Include a comparison table or section outlining differences and similarities between Windows and Linux SAP HA deployments on Azure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides Azure PowerShell examples for command-line automation, with no equivalent examples using cross-platform tools such as Azure CLI or REST API. This creates a bias toward Windows and PowerShell users, potentially excluding Linux/macOS users or those who prefer non-PowerShell automation. The documentation assumes familiarity with PowerShell and does not mention or demonstrate alternative, platform-agnostic methods.

Recommendations:

Add equivalent Azure CLI examples for each scenario alongside the PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include REST API (HTTP request) examples for advanced users and automation scenarios, ensuring parity for all platforms.
Explicitly state that the examples are not limited to Windows and provide guidance or links for installing and using Azure CLI on Linux/macOS.
Consider reordering or grouping examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside PowerShell to avoid the perception of Windows-first bias.
Review and update any references to tools or workflows that are exclusive to Windows or PowerShell, ensuring documentation is inclusive of all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell in the 'Next steps' section and not providing equivalent Linux/CLI examples throughout the guide. The instructions and examples are oriented around the Azure portal and PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. There are no explicit Linux command-line examples or references, and the PowerShell quickstart is mentioned before any Linux alternative.

Recommendations:

Add Azure CLI (az) command examples alongside or before PowerShell instructions for all relevant steps.
Include Linux/Bash-specific guidance or screenshots where applicable, especially for network configuration and DNS settings.
In the 'Next steps' section, provide a quickstart for Linux/Azure CLI users and ensure it is listed before or alongside the PowerShell quickstart.
Explicitly mention that all steps can be performed on Linux using Azure CLI, and provide links to relevant documentation.
Where screenshots are shown, include versions from both Windows and Linux environments if UI differences exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples first, followed by CLI and REST API, without providing any native Linux shell or bash examples. There is an implicit assumption that users are familiar with PowerShell, and no explicit Linux command-line (bash) or native SAP/Linux system commands are shown. The documentation also references PowerShell-specific cmdlets and does not mention Linux-specific tools or patterns.

Recommendations:

Provide bash or shell script examples for Linux users, especially for invoking Azure CLI commands.
Alternate the order of examples, sometimes presenting CLI (cross-platform) before PowerShell to avoid implying Windows primacy.
Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide sample shell environments.
Where possible, include native SAP/Linux commands for soft stopping instances/databases, or at least reference how to do this outside of Azure tooling.
Clarify that PowerShell is available cross-platform, but that many Linux users may prefer bash or zsh, and tailor examples accordingly.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows environments, particularly in the sections referencing Microsoft SQL Server (MSSQL) log tables. All examples and references for database monitoring are focused on SQL Server, which is traditionally a Windows-centric technology, and the referenced system views (such as sys.dm_os_windows_info) are specific to Windows. There are no equivalent examples or references for Linux-based database systems (e.g., PostgreSQL, MySQL) or for running SQL Server on Linux. Additionally, there is a lack of Linux-specific monitoring tools or patterns, and Windows-related tools/views are mentioned exclusively.

Recommendations:

Include examples and references for Linux-based database systems commonly used with SAP, such as PostgreSQL or MySQL, if supported.
If Azure Monitor for SAP solutions supports SQL Server on Linux, clarify this and provide examples or notes on any differences in monitoring/logging.
Where possible, balance references to Windows-specific system views (e.g., sys.dm_os_windows_info) with Linux equivalents or note their absence.
Highlight or provide guidance on using Linux-native monitoring tools (such as sysstat, sar, or journalctl) where relevant.
Explicitly state platform limitations or support to help users on Linux understand what is or isn't available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell as the only command-line deployment option, omitting equivalent instructions for Linux-native tools (such as Azure CLI or ARM templates). The mention of PowerShell appears before any cross-platform alternatives, and there are no explicit Linux command-line examples or references for deployment or management, despite the product's relevance to Linux-based SAP landscapes.

Recommendations:

Add Azure CLI examples alongside or before Azure PowerShell for deployment and configuration steps, ensuring Linux users have clear, native instructions.
Explicitly mention cross-platform tools (e.g., Azure CLI, ARM templates, Bicep) wherever PowerShell is referenced.
Where possible, provide bash or shell script examples for common tasks, especially in sections relevant to Linux-based SAP deployments.
Review and update quickstart and configuration links to ensure parity between Windows and Linux workflows.
Clarify in the documentation that all features are accessible from both Windows and Linux environments, and provide links to platform-specific guidance where necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as Windows Server Failover Cluster and SMB/UNC backup paths) are described in more detail and often appear before their Linux equivalents. There are more specific instructions and examples for Windows (e.g., UNC path for backup), while Linux sections lack equivalent command-line or configuration examples. The documentation references Windows-specific tools and deployment guides more prominently, and the Windows deployment section precedes the Linux section in both structure and detail.

Recommendations:

Provide Linux-first or parallel examples for all procedures, especially for backup/restore commands (e.g., show NFS path usage for Linux backups as is done for Windows UNC paths).
Include Linux-native clustering tools (e.g., Pacemaker) with equal detail and example configurations as given for Windows Server Failover Cluster.
Ensure that Linux deployment and high-availability solutions are described with the same depth and clarity as Windows, including links to relevant Linux documentation and guides.
When listing storage options, avoid presenting Windows options first or in more detail; instead, present both OS options side by side.
Add Linux-specific troubleshooting tips and automation scripts where Windows PowerShell or tools are mentioned.
Balance the order of sections so that Linux and Windows are treated equally, or use a truly parallel tabbed structure for all OS-specific content.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a significant Windows bias. Most automation and setup scripts are provided exclusively in PowerShell, with instructions to use PowerShell ISE and Windows-specific command patterns. Linux equivalents are either missing or only appear in a few sections, often after the Windows instructions. The use of Windows tools and terminology (e.g., PowerShell ISE, .ps1 scripts, Windows file paths) is prevalent, and Linux users are only occasionally accommodated, sometimes with minimal or incomplete guidance.

Recommendations:

Provide all automation and setup scripts in both PowerShell and Bash (or other common Linux shells), ensuring parity in functionality and clarity.
Avoid referencing Windows-specific tools (such as PowerShell ISE) as the default or only option; suggest cross-platform editors (e.g., VS Code) or terminal usage.
When presenting code blocks, use tabbed or side-by-side examples for Windows and Linux, and ensure both are equally detailed and tested.
Ensure all steps (such as downloading, unblocking, and executing scripts) have clear Linux equivalents, not just conditional PowerShell code for Unix.
Review all instructions for terminology and paths, replacing Windows-centric language with cross-platform alternatives where possible.
Where Azure CLI or other tools are used, provide explicit Linux command-line examples, not just PowerShell wrappers.
Audit the documentation for any missing Linux-specific troubleshooting or caveats, and add them as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by frequently mentioning Windows and Azure SQL Database before Linux and MySQL equivalents, especially in architecture and sizing sections. Windows-specific tools and services (e.g., Azure SQL Database, which is only supported for SAP BOBI on Windows) are highlighted, while Linux-specific guidance is less detailed or deferred to external links. There is a lack of Linux-specific examples or step-by-step instructions within the main document, with Linux deployment guidance relegated to a separate page.

Recommendations:

Provide parallel Linux examples and guidance alongside Windows instructions within the main document, rather than referring users to a separate Linux page.
When listing supported operating systems, alternate the order or present Windows and Linux options together to avoid implicit prioritization.
Include Linux-specific tools, commands, and configuration steps (e.g., for file sharing, database setup, and high availability) directly in the main guide.
Ensure that all Azure services and features discussed (such as storage and database options) clearly indicate Linux compatibility and any differences in implementation.
Add explicit Linux architecture diagrams or callouts where implementation details diverge from Windows.
Where Windows-only services are mentioned (e.g., Azure SQL Database for SAP BOBI), provide equivalent Linux alternatives and note any limitations or required workarounds.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. PowerShell is mentioned as the only method for configuring disaster recovery for VMs in scale sets, with no equivalent Linux CLI or Bash example provided. Windows-specific tools like RoboCopy are recommended for SMB file replication, while the Linux alternative (rsync) is only mentioned for NFS scenarios. There is a section specifically referencing 'SAP system running on Windows with Azure shared disk', but no parallel guidance for Linux-based SAP systems. Overall, Windows tools and patterns are mentioned first or exclusively in several places, and Linux-native approaches are underrepresented.

Recommendations:

Provide equivalent Azure CLI and/or Bash script examples for all PowerShell-only instructions, especially for configuring disaster recovery for VMs in scale sets.
When recommending file replication tools, mention both Windows (RoboCopy) and Linux (rsync) options for all relevant storage types (e.g., SMB as well as NFS).
Include explicit guidance and examples for SAP systems running on Linux, especially in sections that currently reference only Windows scenarios (e.g., Azure shared disk).
Ensure that Linux-native tools and patterns are presented alongside or before Windows equivalents to avoid the appearance of Windows-first bias.
Add a table or section summarizing DR strategies for both Windows and Linux SAP workloads, highlighting any differences and providing parity in documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All deployment, configuration, and backup/restore guidance is exclusively for Windows environments, with repeated references to Windows-specific tools and features (e.g., Windows Storage Pools, Windows Storage Spaces, VSS integration, Microsoft IIS). There are no Linux examples, nor any mention of Linux support, tools, or best practices for SAP MaxDB, liveCache, or Content Server on Azure VMs. The structure and content assume Windows as the default and only platform.

Recommendations:

Add equivalent sections for Linux deployments, including supported distributions, VM types, and SAP MaxDB/liveCache/Content Server configuration on Linux.
Provide Linux-specific storage configuration guidance (e.g., using LVM, mdadm, or other Linux-native tools for disk striping and logical volumes).
Include backup/restore instructions and recommendations for Linux, referencing Linux-compatible tools and SAP MaxDB utilities.
Mention Linux best practices for performance, security, and monitoring in Azure.
Ensure that all platform-specific advice is clearly labeled and that Linux is presented as a first-class option alongside Windows.
Where Windows tools (e.g., VSS, IIS, Storage Spaces) are mentioned, provide Linux equivalents or alternatives (e.g., Apache/Nginx for IIS, LVM/mdadm for Storage Spaces, native Linux backup strategies).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally strives for parity between Windows and Linux, but there are several instances of Windows bias. Windows tools and patterns (e.g., Windows Storage Spaces, drive D:) are often mentioned before or in more detail than their Linux equivalents. In some cases, Windows-specific guidance is more prominent, and Linux alternatives are referenced but not always explained as thoroughly. Some example links and explanations are Windows-centric, and the use of PowerShell or Windows-specific terminology is more prevalent. Linux examples are present but sometimes less detailed or referenced after Windows.

Recommendations:

Ensure that Linux tools (e.g., LVM, MDADM) are described with equal detail and prominence as Windows tools like Storage Spaces.
When presenting examples or recommendations, alternate the order or present both Windows and Linux in parallel, rather than always listing Windows first.
Provide direct Linux command-line examples (not just links) where Windows PowerShell or GUI steps are described.
Expand Linux-specific notes and best practices to match the depth given to Windows, especially for storage, disk striping, and nonpersistent disk usage.
Where Windows-specific terminology is used (e.g., drive letters), provide the Linux equivalent (e.g., mount points) in the same context.
Review all referenced articles and ensure Linux parity in linked content as well.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing all command-line examples exclusively in PowerShell, referencing PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Set-AzureRmKeyVaultAccessPolicy) without Bash or Linux shell equivalents. There are no explicit Linux/Unix shell examples, and the use of PowerShell is presented as the default method for scripting and automation. While Azure CLI is mentioned for some vault creation steps, all automation and scripting for deployment and identity management is shown only with PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for deployment and access policy steps.
Explicitly mention that all PowerShell commands can be run cross-platform (if true), or clarify any Windows-specific requirements.
For each PowerShell example, add a corresponding Azure CLI or Bash example, and consider presenting CLI first or side-by-side.
Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
Add a section or note for Linux/macOS users, highlighting any differences or prerequisites.
Ensure that automation and scripting guidance is not limited to Windows/PowerShell, to support users on all platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally provides parity between Windows and Linux in terms of configuration tables and recommendations, but there are several areas where a Windows bias is evident. Windows is often mentioned first in lists and configuration tables, and Windows-specific tools (e.g., Storage Spaces, NTFS, Windows Firewall) are referenced explicitly, sometimes with more detail than their Linux equivalents. Some operational instructions (such as firewall configuration) are only given for Windows, and the section on installing SAP ASE provides a direct link to the Windows installation guide but not to the Linux equivalent. There are also areas where Linux-specific operational guidance is less detailed or missing.

Recommendations:

Alternate the order of Windows and Linux in configuration tables and lists, or list Linux first in some sections to avoid implicit prioritization.
Provide equivalent detail for Linux tools (e.g., LVM2, XFS, firewalld/iptables) as is given for Windows tools like Storage Spaces and NTFS.
Add explicit instructions or links for Linux firewall configuration (e.g., firewalld, iptables) where Windows Firewall is mentioned.
Include a direct link to the SAP ASE Installation Guide for Linux, as is done for Windows.
Ensure operational examples (such as commands, tuning, or troubleshooting) are provided for both platforms where relevant.
Where possible, provide sample shell commands for Linux alongside PowerShell or Windows command examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Windows as the supported operating system, with no mention of Linux or macOS compatibility or alternatives. System requirements specify only Windows 10 and .NET Framework, both of which are Windows-centric. There are no examples, instructions, or notes for Linux users, nor any mention of cross-platform support or workarounds.

Recommendations:

Clearly state if the tool is Windows-only, and if so, suggest alternatives or workarounds for Linux users (e.g., running via Wine, using a VM, or recommending open-source cross-platform threat modeling tools).
If Linux support is planned or possible, include installation and usage instructions for Linux.
Add a section addressing platform support explicitly, so non-Windows users are not left uncertain.
If the tool is not cross-platform, consider providing links to comparable Linux-compatible tools in the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows as the supported operating system and requires the .NET Framework (not .NET Core), which is primarily Windows-centric. There are no mentions of Linux or cross-platform support, nor are there any Linux installation or usage instructions. All examples, requirements, and download links assume a Windows environment.

Recommendations:

Clearly state if the tool is Windows-only, or provide information about Linux/macOS support if available.
If cross-platform support is planned or possible (e.g., via .NET Core or Mono), include installation and usage instructions for Linux.
Add troubleshooting or compatibility notes for non-Windows users.
If the tool is not supported on Linux, suggest alternative tools or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is largely cross-platform in its use of Azure CLI and Bash examples, which are suitable for both Windows and Linux users. However, there are some instances of Windows bias: (1) PowerShell is mentioned as a method for listing ACLs without providing a Linux alternative, (2) some linked quickstarts for managed identities reference Windows-specific guides (e.g., configuring managed identities on Windows VMs), and (3) there are no explicit Linux or cross-platform examples for tasks like listing ACLs for Azure Files/Data Lake Storage. These omissions may make it less clear for Linux users how to perform certain steps.

Recommendations:

For sections mentioning PowerShell (e.g., listing ACLs), provide equivalent Bash/Azure CLI commands or explicitly mention Linux-compatible alternatives.
When linking to quickstarts or guides for managed identities, ensure both Windows and Linux VM scenarios are referenced, or clarify that the steps are similar for Linux.
Wherever possible, add explicit Linux/Bash examples alongside Windows/PowerShell ones, especially for resource management tasks like ACL listing or manipulation.
Review all external links to ensure Linux parity in referenced documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: Windows tools and clustering frameworks are often mentioned first or in greater detail, with Windows-specific technologies (e.g., Windows Failover Cluster, Windows Scale-Out File Services, SIOS Datakeeper) described before their Linux equivalents. Some sections provide detailed guidance or links for Windows but only brief or less prominent coverage for Linux (e.g., Oracle Linux high availability is not supported, and users are referred to third-party solutions). There are also more explicit recommendations and configuration details for Windows-based scenarios, while Linux alternatives are sometimes less emphasized or require external documentation. Powershell or Windows-centric patterns are implied as defaults in some areas. In a few cases, Linux examples or tools are missing or less detailed.

Recommendations:

Ensure Linux and Windows solutions are presented with equal prominence and detail, ideally alternating which OS is described first in each section.
Provide equivalent step-by-step examples, diagrams, and links for Linux (SUSE, Red Hat, Oracle Linux) as are given for Windows, especially for high availability and disaster recovery scenarios.
Include explicit Linux command-line examples (e.g., using shell scripts or systemd) where Windows/Powershell commands or tools are referenced.
Clarify support status and recommended patterns for Linux distributions, including Oracle Linux, and provide direct links to official documentation for Linux-based clustering and HA solutions.
Where third-party solutions are required for Linux (e.g., SIOS for Oracle Linux), provide more guidance or references to help users achieve parity with Windows-based solutions.
Review the order of presentation to avoid always listing Windows first, which can reinforce a perception of Windows as the default or preferred platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is largely platform-neutral in its main content, as it focuses on listing Azure RBAC built-in roles and their permissions. However, there is evidence of Windows bias in the external links and references. For example, the 'Attestation Contributor' role's 'Learn more' link points to a PowerShell-specific quickstart, which is typically associated with Windows environments. There are no Linux/CLI/Bash equivalents or cross-platform instructions referenced alongside or instead of PowerShell. No Linux tools, shell commands, or cross-platform Azure CLI examples are provided, and where a platform-specific example is referenced, it is Windows/PowerShell.

Recommendations:

Wherever a 'Learn more' or quickstart link is provided (e.g., for Attestation Contributor), ensure that both PowerShell (Windows) and Azure CLI (cross-platform) or Bash examples are linked, or provide a platform-neutral landing page.
Audit all external documentation links to ensure Linux and cross-platform users are equally supported, not just Windows/PowerShell users.
If role usage examples or automation scripts are added in the future, always provide both PowerShell and Azure CLI/Bash equivalents, and avoid assuming Windows as the default environment.
Consider adding a 'Platform support' note or table where relevant, clarifying that all roles and permissions are accessible via Azure CLI, Azure Portal, and PowerShell, with links to relevant guides for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation, while covering both Windows and Linux scenarios, frequently presents Windows tools, requirements, and workflows before their Linux equivalents. PowerShell and Windows-specific tools are often referenced as primary management methods, with Linux alternatives mentioned secondarily or as exceptions. Some sections (e.g., domain join, prerequisites) are Windows-centric or lack Linux parity in detail. There are also more explicit and detailed instructions for Windows tasks (e.g., VM Agent installation, domain join), while Linux instructions are sometimes less detailed or presented as secondary.

Recommendations:

Present Linux and Windows options in parallel, rather than listing Windows first or as the default.
Where PowerShell is referenced, ensure equivalent Azure CLI or Linux-native commands are provided with equal prominence and detail.
Avoid language that assumes a Windows management workstation by default; clarify that both Windows and Linux can be used for management tasks.
For every Windows-specific example or tool, provide a Linux equivalent (e.g., for joining domains, managing VMs, configuring proxies).
Expand Linux sections to match the detail and clarity of Windows instructions, especially for tasks like agent installation, proxy configuration, and post-deployment steps.
Where a feature is 'Windows only', clarify if there is a Linux alternative or explicitly state the limitation.
Review and update prerequisites to reflect that Linux workstations are fully supported for management and deployment, not just as an exception.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows-specific tools (e.g., Microsoft Management Console, PowerShell scripts) before or more prominently than Linux equivalents. PowerShell is used for validation examples, and links/scripts are provided specifically for Windows. Linux instructions are present but sometimes less detailed or secondary. Some automation (e.g., unprotecting web methods) is only referenced for Windows, and troubleshooting steps often lead with Windows approaches.

Recommendations:

Provide Linux shell script equivalents for all PowerShell scripts and automation steps (e.g., unprotecting web methods).
When describing service restarts or management, present Linux and Windows instructions in parallel or in a neutral order.
Include references and links to Linux-specific resources and scripts where Windows ones are given.
Ensure troubleshooting and validation examples (such as querying SAP Control web methods) are shown for both Windows (PowerShell) and Linux (bash/curl/python).
Avoid using Windows tools (MMC, Windows Defender Firewall) as the primary example; instead, offer cross-platform or OS-agnostic instructions.
Explicitly state when a step is OS-specific and provide parity in detail and automation for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it covers both Windows and Linux high availability scenarios in referenced documents, the main text and examples often mention Windows-specific tools and procedures first or exclusively. For instance, the only automation script for network latency measurement is provided as a PowerShell script, with no mention of a Linux/bash alternative. The 'Next steps' section lists only Windows failover cluster guides, omitting Linux Pacemaker equivalents. Some cluster solution explanations refer to Windows Server Failover Clustering before Linux Pacemaker. This can give the impression that Windows is the primary or preferred platform, and Linux is secondary.

Recommendations:

Provide Linux/bash equivalents for all automation scripts and procedures (e.g., a bash script for network latency measurement alongside the PowerShell script).
Ensure that references to high availability solutions mention Linux Pacemaker and Windows Server Failover Clustering equally and in parallel, rather than listing Windows first.
In the 'Next steps' section, add links to Linux high availability guides (e.g., clustering SAP ASCS/SCS with Pacemaker on SUSE/Red Hat).
Where possible, use cross-platform terminology (e.g., 'cluster solution' instead of 'Windows failover cluster') and clarify when instructions apply to both Windows and Linux.
When mentioning tools or scripts, specify their compatibility (e.g., 'This script is available in both PowerShell for Windows and bash for Linux').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally covers both Windows and Linux scenarios, but there are subtle biases. Windows tools and patterns (such as Storage Spaces) are mentioned before Linux equivalents (LVM). Some example references and high-availability guides list Windows before Linux, and Windows-specific technologies (e.g., SMB for Windows) are sometimes highlighted first. There are no explicit command-line examples, but where tooling is mentioned, Windows is often foregrounded. Linux-specific details are sometimes less prominent or only mentioned as an afterthought.

Recommendations:

Ensure Linux and Windows are given equal prominence in all lists and examples, alternating order or grouping by OS where appropriate.
When referencing tools for striping or storage management, mention Linux LVM and Windows Storage Spaces together, with equal detail and priority.
Where high-availability guides or scenario links are provided, list Linux and Windows guides in parallel, not with Windows first.
Add explicit Linux command-line examples (e.g., LVM setup, NFS mounting) alongside any Windows or PowerShell examples.
In capability matrices and feature tables, clarify which features apply to Linux, Windows, or both, and avoid defaulting to Windows terminology.
For shared storage, ensure NFS (Linux) and SMB (Windows) are described with equal depth and clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is exclusively focused on Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability in Azure, with all examples, architectures, and tooling (e.g., SIOS DataKeeper, Windows Scale-Out File Server, WSFC) being Windows-specific. There are no references to Linux-based clustering solutions, nor any examples or guidance for Linux environments, despite SAP being widely deployed on Linux. The document assumes a Windows-only context throughout.

Recommendations:

Include a parallel section or separate documentation for clustering SAP ASCS/SCS on Linux in Azure, covering Pacemaker/Corosync or SUSE HAE/Red Hat HA solutions.
Provide Linux-specific examples for shared disk configuration, fencing, and load balancer integration in Azure.
Mention Linux support and alternatives wherever Windows tools or patterns (e.g., WSFC, SIOS DataKeeper, Windows Scale-Out File Server) are discussed.
Add a comparison table or guidance on choosing between Windows and Linux clustering approaches for SAP on Azure.
Ensure that prerequisites and supported OS versions mention Linux distributions and their requirements for SAP clustering.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively lists Windows 10 as the supported operating system, with no mention of Linux or macOS support or alternatives. All requirements and download instructions are Windows-centric, and there are no examples or guidance for Linux users.

Recommendations:

Clearly state if the tool is Windows-only, and if so, mention any workarounds (e.g., running via Wine or in a VM) for Linux users.
If cross-platform support is planned or available, provide installation and usage instructions for Linux (and macOS) alongside Windows.
Include a section addressing Linux users, even if only to acknowledge the lack of native support and suggest alternatives or similar tools available on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Windows ACLs, WCF/.NET configuration) without providing Linux or cross-platform equivalents. Examples and guidance are oriented toward Windows environments, and there is a lack of Linux-specific instructions or examples for common tasks like log file permissions or log rotation. The only detailed configuration examples are for Windows technologies (WCF), and Windows terminology (ACL) is used exclusively when discussing file access control.

Recommendations:

For sections discussing file permissions (e.g., 'Ensure that Audit and Log Files have Restricted Access'), include Linux/Unix equivalents such as chmod, chown, and setfacl, and provide example commands.
When referencing log rotation, mention and provide examples for Linux tools such as logrotate, and describe how to configure them.
For logging and auditing in web applications, provide examples using popular cross-platform frameworks (e.g., Node.js, Python, Java) and mention logging best practices for both Windows and Linux deployments.
Where WCF/.NET examples are given, consider adding parallel examples for cross-platform frameworks (e.g., gRPC, REST APIs implemented in other languages) and how to configure logging/auditing in those environments.
Replace or supplement Windows-specific terminology (e.g., 'Windows ACL') with platform-neutral language or include Linux equivalents (e.g., 'file permissions and access control lists (ACLs) on Linux using chmod/setfacl').
Explicitly state when a mitigation or recommendation is platform-specific, and provide alternative guidance for other platforms where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation frequently lists Windows before Linux when discussing supported operating systems, and in some cases (such as Oracle DBMS support and SAP Hybris Commerce Platform), Windows is emphasized or described in more detail than Linux. There are also sections where only Windows or Oracle Linux are mentioned as supported OSes, with less clarity or detail for other Linux distributions. No Linux-specific tools, commands, or examples are provided, and the document lacks parity in examples or guidance for Linux users.

Recommendations:

List Linux distributions before or alongside Windows when enumerating supported operating systems to avoid the impression of Windows primacy.
Provide equal detail for all supported Linux distributions, including explicit mention of supported versions and any special considerations, not just for Oracle Linux.
Where examples or scenarios are given (e.g., for Oracle DBMS or SAP Hybris Commerce Platform), ensure Linux scenarios are described with the same depth as Windows scenarios.
Include Linux-specific guidance, tools, or troubleshooting tips where relevant, not just general or Windows-focused information.
Clarify any restrictions or differences for Linux platforms in all relevant sections, ensuring Linux users have clear, actionable information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools and patterns (such as Visual Studio for code reviews, Microsoft Antimalware, and Microsoft Defender Antivirus in Windows) without mentioning Linux alternatives. The only example of browser cache location is for Internet Explorer. There are no Linux-specific examples or tool recommendations, and the documentation does not provide parity in instructions or tool suggestions for Linux environments.

Recommendations:

When mentioning Visual Studio for code reviews, also reference cross-platform or Linux-friendly alternatives such as VS Code, GitHub pull requests, or GitLab merge requests.
For static code analysis, include examples of popular open-source tools that are commonly used on Linux, such as SonarQube, ESLint, or Clang Static Analyzer.
When discussing antimalware solutions, mention Linux-compatible endpoint protection tools and clarify which Microsoft solutions are available for Linux (e.g., Microsoft Defender for Endpoint on Linux).
In the section about removing standard server headers, provide links or instructions for both Windows/IIS and Linux/Apache/Nginx environments.
When describing browser cache folders, avoid referencing only Windows/Internet Explorer; mention cache locations for other browsers and operating systems.
For attack surface analysis, include Linux-compatible tools (e.g., Lynis, OpenVAS) alongside Microsoft Attack Surface Analyzer.
Ensure that all tool recommendations and examples have Linux equivalents or clarify platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in several ways. Windows-specific tools and patterns (such as Windows Server Failover Clustering, WSFC) are mentioned first and in greater detail, while Linux equivalents (such as Pacemaker) are only briefly referenced and with limited scope (only for SUSE Linux Enterprise Server 12+). The document references many figures and guides related to Windows clustering (WSFC), with no equivalent Linux diagrams or walkthroughs. There are no Linux-specific examples, commands, or step-by-step instructions, and the overall structure and linked resources are heavily skewed toward Windows environments.

Recommendations:

Provide equivalent Linux examples and walkthroughs, including commands and configuration steps for Pacemaker and other Linux HA solutions.
Include diagrams and architecture figures for Linux-based SAP high availability scenarios, not just Windows/WSFC.
Mention Linux tools and patterns (such as Pacemaker, Corosync, systemd) alongside Windows tools, and not only as an afterthought or with limited support.
Ensure that references, links, and figures are balanced between Windows and Linux, or clearly indicate when a feature is Windows-only.
Expand the discussion of Linux support beyond SUSE Linux Enterprise Server, if possible, or clarify the support matrix for other distributions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows and PowerShell tools are frequently mentioned first, and in some sections, Windows-specific instructions or links are provided before Linux equivalents. The manual configuration section links only to Windows VM identity guides for Azure portal, CLI, PowerShell, and templates, omitting direct links to Linux VM identity configuration. While most command examples do include both Windows and Linux variants, the ordering and linking patterns prioritize Windows. There is also a heavier emphasis on PowerShell, with more detailed steps and references compared to Linux/CLI.

Recommendations:

Ensure that all identity configuration links in the manual configuration section include both Windows and Linux VM guides for Azure portal, CLI, PowerShell, and templates.
Wherever examples are given for both Windows and Linux, alternate the order or present them in parallel tabs to avoid always listing Windows first.
Add explicit Linux-focused instructions and links where only Windows examples or references are currently provided.
Review the balance of PowerShell and CLI coverage to ensure Linux users have equally detailed guidance.
In summary tables or lists, avoid using 'Windows' as the default or first option; instead, clarify applicability to both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for deployment tasks, without any equivalent Azure CLI (cross-platform/Linux-friendly) examples. The PowerShell examples are presented as the default and only method for resource creation and management, and there is no mention or illustration of Linux-native tools or workflows. Although the page links to both Linux (Azure CLI) and Windows (PowerShell) guides at the end, the in-page walkthroughs and code samples exclusively use PowerShell, potentially disadvantaging Linux users.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI example, especially for resource creation and management tasks (e.g., New-AzVm, New-AzAvailabilitySet).
When introducing command-line examples, present Azure CLI (cross-platform) examples first or in parallel with PowerShell to avoid implicit prioritization of Windows tooling.
Explicitly mention that all operations can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation inline.
Consider including a section or callout that highlights cross-platform deployment options and best practices for Linux users.
Audit the documentation for other instances where Windows-specific tools or workflows are assumed, and ensure Linux parity throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (such as azperflib.exe and Windows services) are introduced and explained before their Linux or cross-platform equivalents. The PowerShell workflow is described in greater detail and with more context than the corresponding Azure CLI/Linux instructions. Some troubleshooting and error resolution steps refer to Windows tools or directories first, and the overall structure often presents Windows approaches before Linux ones.

Recommendations:

Ensure Linux and Windows instructions are presented in parallel or in a consistent order (e.g., always Linux first if the service is Linux-focused, or alternate).
Provide equal depth and detail for both PowerShell (Windows) and Azure CLI (Linux/cross-platform) workflows, including troubleshooting steps.
Where possible, use cross-platform tools (like Azure CLI) as the primary example, with OS-specific notes as needed.
Avoid referencing Windows-specific tools (e.g., azperflib.exe, Windows service directories) without providing equivalent Linux details (e.g., Linux daemons, log locations) in the same section.
When describing error codes and solutions, ensure both Windows and Linux log file locations and commands are mentioned together.
Review the order of sections and examples to avoid always listing Windows/PowerShell first, especially when the service is available on both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) and Scale-Out File Server (SOFS). All configuration steps, code samples, and screenshots are Windows-specific, using PowerShell scripts and Windows administrative tools. There are no Linux equivalents, examples, or even references to Linux-based clustering or file sharing solutions. The documentation assumes a Windows-only approach and does not provide guidance for users operating SAP on Linux or mixed environments.

Recommendations:

Add a section or parallel documentation for Linux-based SAP high availability, using Pacemaker/Corosync clusters and NFS or other Linux file sharing solutions.
Provide Linux shell script examples for file system preparation, permissions, and cluster resource management.
Reference Linux-native tools and patterns (e.g., systemd, crmsh, pcs) alongside Windows tools.
Clearly state in the introduction if the guide is Windows-only, and link to Linux-specific guides if available.
Include comparative diagrams and workflows for both Windows and Linux high availability architectures.
Ensure that all major steps (cluster setup, file share configuration, permissions) have Linux equivalents or cross-references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation presents Windows troubleshooting steps and directory paths before Linux equivalents, and references Windows-specific tools and log file locations. While Linux troubleshooting is included, Windows is consistently prioritized in order and detail, and there is a lack of parity in example commands or scripts for both platforms.

Recommendations:

Alternate the order of Windows and Linux sections, or present them in parallel tables to avoid implicit prioritization.
Provide equivalent example commands or scripts for both Windows (e.g., PowerShell) and Linux (e.g., Bash) where relevant.
Reference both Windows and Linux log file paths and tools together when describing troubleshooting steps.
Ensure that any mention of support components or log files always lists both Windows and Linux options together, or in alphabetical order.
If setup scripts or automation are mentioned, clarify if they are cross-platform or provide separate instructions for each OS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes the Microsoft Threat Modeling Tool, which is a Windows-only application. All instructions, screenshots, and workflows assume the use of a Windows environment, with references to Windows-centric features like OneDrive and Active Directory. There are no mentions of Linux or cross-platform alternatives, nor are there any examples or guidance for users on non-Windows systems.

Recommendations:

Clearly state the platform requirements (e.g., Windows-only) at the beginning of the documentation.
If possible, provide information about running the tool on Linux (e.g., via Wine or virtualization), or mention any available cross-platform alternatives.
Include guidance for Linux users on how to collaborate with Windows users (e.g., file formats, sharing reports).
Reference non-Windows equivalents for features like OneDrive (e.g., SharePoint, Dropbox, or generic file sharing) where appropriate.
If the tool is not available for Linux, suggest open-source or cross-platform threat modeling tools as alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/Microsoft-centric bias by referencing Windows-specific security models (SDL), Microsoft tools (Entra ID, Key Vault, Azure DevOps), and providing links and examples that are tailored to Microsoft technologies. There is a lack of Linux-specific tools, patterns, or examples, and no mention of Linux-native security practices or open-source alternatives. The documentation assumes the reader is using the Microsoft ecosystem and does not provide parity guidance for Linux or cross-platform development.

Recommendations:

Include Linux-native security practices and tools (e.g., SELinux, AppArmor, Linux auditd, iptables/nftables, fail2ban) alongside Microsoft solutions.
Provide examples and links for both Windows and Linux environments when discussing authentication, logging, key management, and error handling.
Reference cross-platform or open-source alternatives to Microsoft tools (e.g., HashiCorp Vault for secrets management, OpenLDAP for identity, Jenkins/GitLab CI for DevOps).
Explicitly mention how Azure services integrate with Linux-based applications and provide links to relevant Linux documentation.
Balance the order of presentation so that Linux and open-source options are mentioned alongside or before Windows/Microsoft-specific solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. It consistently references Windows-specific cryptographic APIs (CNG, CAPI, Win32/64, .NET), Windows-only features (BitLocker, Group Policy, SSIS, SQL Server EKM, Always Encrypted), and Windows IoT Core. Examples and recommendations are almost exclusively for Windows environments, with only brief mentions of Apple and Java/Android APIs, and no Linux-specific tools, APIs, or examples. Linux cryptographic practices, tools (e.g., OpenSSL, GnuPG), and equivalents to Windows features are not discussed or referenced.

Recommendations:

Add Linux-specific cryptographic API and tool recommendations (e.g., OpenSSL, /dev/urandom, GnuPG, dm-crypt/LUKS for disk encryption).
Provide code examples for Linux environments (e.g., using OpenSSL CLI or libraries in C/Python).
Reference Linux equivalents for Windows features (e.g., LUKS for BitLocker, systemd-cryptsetup for encrypted volumes, Linux TPM stack).
Include guidance for cross-platform .NET Core/5+ cryptography APIs that work on Linux and macOS, not just Windows.
Mention Linux/Unix device management and encryption policies where relevant (e.g., mobile device management, disk encryption).
Balance the order of presentation so that Windows and Linux/Unix approaches are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Microsoft Windows as the supported operating system and does not mention Linux or macOS compatibility, installation, or usage. All system requirements and instructions are Windows-centric, with no examples or alternatives for Linux users.

Recommendations:

Clearly state if the tool is Windows-only, and if so, mention the lack of Linux/macOS support explicitly.
If possible, provide information about running the tool on Linux (e.g., via Wine or virtualization), or mention any planned cross-platform support.
Include a section addressing Linux/macOS users, even if only to acknowledge the limitation and suggest alternatives or workarounds.
If there are command-line or scripting examples, provide Linux/bash equivalents alongside Windows/PowerShell examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, providing only Windows Server Failover Cluster (WSFC) instructions, PowerShell scripts, and references to Windows-specific tools (DNS Manager, Windows Firewall, Failover Cluster Manager). There are no Linux or cross-platform examples, and Linux high-availability patterns (such as Pacemaker/Corosync or SUSE HA) are not mentioned or linked, despite SAP NetWeaver being supported on Linux in Azure. All configuration and troubleshooting steps assume a Windows environment.

Recommendations:

Add equivalent Linux high-availability installation and configuration steps, referencing Pacemaker/Corosync and SUSE/RHEL HA clusters.
Provide Linux shell (bash) command examples alongside PowerShell for tasks such as firewall configuration, cluster management, and DNS updates.
Include links to Linux-specific SAP HA documentation (e.g., SAP high-availability guide for SUSE, Red Hat).
Clearly indicate in the introduction that this guide is Windows-specific, and cross-reference a Linux-focused guide if available.
Where possible, use Azure-native tooling or cross-platform scripts (e.g., Azure CLI) in examples, or provide both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide any Linux-specific instructions or alternatives. All examples and requirements are Windows-centric, with no indication of cross-platform support or guidance.

Recommendations:

Clarify explicitly if the Threat Modeling Tool is Windows-only; if so, state this clearly at the top of the documentation.
If Linux or cross-platform support is planned or available, provide equivalent installation instructions and troubleshooting steps for Linux users.
Mention alternative installation methods or compatibility notes for non-Windows environments, even if only to state that they are not supported.
Avoid assuming the presence of Windows-specific features (e.g., Windows Menu shortcuts, ClickOnce) without noting their absence on other platforms.
Include a section in 'System requirements' that addresses Linux and macOS, even if only to state they are not supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by focusing on Windows-centric technologies (e.g., ASP.NET, WCF, SQL Server, SMB 3.x for Windows), providing configuration and code examples only for Windows/.NET environments, and referencing Windows tools and patterns (e.g., web.config, URL Rewrite, ServicePointManager, Windows-specific SMB clients) without offering Linux or cross-platform alternatives. There are no Linux command-line, configuration, or code examples, and Linux tools or deployment scenarios are not discussed.

Recommendations:

Provide equivalent Linux examples for enforcing HTTPS (e.g., using Nginx or Apache configuration snippets for HSTS and HTTPS redirects).
Include code samples in cross-platform languages (e.g., Python, Java, Node.js) for certificate pinning and HTTPS enforcement, not just C#/.NET.
Mention and link to Linux-compatible tools and clients (e.g., smbclient for SMB 3.x, OpenSSL for certificate validation, sqlcmd for SQL Server on Linux).
When describing configuration (e.g., web.config, URL Rewrite), also describe how to achieve the same on Linux-based web servers.
Avoid assuming Windows as the default environment; explicitly state when guidance is Windows-specific and provide Linux alternatives where possible.
Reference documentation for Linux deployments of Azure services (e.g., connecting to Azure SQL from Linux, securing Redis from Linux clients).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows operating systems and Windows-specific installation patterns (e.g., ClickOnce, Windows Menu shortcuts). There are no mentions of Linux or cross-platform support, nor are there alternative instructions or requirements for non-Windows environments.

Recommendations:

Clearly state in the system requirements section whether Linux (or macOS) is supported or not. If not, explicitly mention Windows-only support.
If Linux is or will be supported, provide equivalent installation and troubleshooting instructions for Linux users.
Include information about any cross-platform alternatives or workarounds, such as running the tool via Wine or using similar open-source tools on Linux.
Avoid Windows-specific terminology (like 'Windows Menu') without clarifying that these instructions are for Windows users only.
If the tool is Windows-only, suggest alternative threat modeling tools available for Linux in the documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All deployment, configuration, and removal instructions are specific to Windows Server operating systems, with no support or examples for Linux. All code samples and automation are provided exclusively via PowerShell cmdlets, and the documentation repeatedly references Windows tools (Azure portal, Visual Studio, Windows event logs) without mentioning or providing parity for Linux users. Linux is explicitly called out as unsupported, but the lack of any alternative guidance or comparable tooling for Linux users further reinforces the Windows-centric nature of the documentation.

Recommendations:

Clearly state early in the documentation that Microsoft Antimalware for Azure does not support Linux, and suggest alternative antimalware solutions for Linux VMs in Azure.
If possible, provide links or references to recommended antimalware solutions for Linux on Azure, such as third-party extensions or Microsoft Defender for Endpoint (Linux).
Where PowerShell is used for automation, suggest or provide equivalent Azure CLI or REST API examples, which are cross-platform and usable from Linux.
Add a section comparing antimalware options for both Windows and Linux in Azure, with guidance on how to achieve similar protection and monitoring on Linux VMs.
Ensure that all tooling and configuration guidance is inclusive of both Windows and Linux users, or clearly indicate when a feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows environments, including installation patterns (ClickOnce), error paths, and system requirements. Only Windows is mentioned as a supported OS, and all troubleshooting and usage instructions assume a Windows context. There are no Linux or cross-platform examples, nor any mention of Linux support or alternatives.

Recommendations:

Explicitly state if the tool is Windows-only, or provide information about Linux/macOS support if available.
If Linux is not supported, suggest possible workarounds (e.g., using Wine or virtualization) or alternative tools for Linux users.
Include a section addressing cross-platform compatibility and clarify installation and usage instructions for non-Windows environments if applicable.
If future versions may support Linux, mention this in the documentation to inform users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows tools and technologies (such as Microsoft Antimalware, BitLocker, and Microsoft Defender for Endpoint) are mentioned first or exclusively in several sections. While Linux is acknowledged as supported, Linux-specific examples, tools, or guidance are often missing or less detailed. For instance, antimalware and endpoint protection sections focus almost entirely on Microsoft/Windows solutions, and links to Linux-specific security solutions are absent. In the disk encryption section, BitLocker (Windows) is mentioned before dm-crypt (Linux), and the majority of linked resources and examples are Windows-centric.

Recommendations:

Provide Linux-specific examples and guidance alongside Windows examples, especially in antimalware and endpoint protection sections.
List Linux and Windows tools in parallel, rather than mentioning Windows tools first or exclusively.
Include links to popular Linux antimalware and endpoint protection solutions available in the Azure Marketplace.
Ensure that all security features (e.g., Microsoft Defender for Endpoint) clarify Linux support and provide relevant Linux documentation links.
Where possible, add Linux command-line or configuration examples (e.g., for deploying antimalware, configuring disk encryption, or using backup tools).
Balance the order of presentation so that Linux and Windows are treated equally throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows technologies and tools, such as WCF, ASP.NET, IIS, and Windows-specific configuration files (web.config, machine.config). All code and configuration examples are for .NET/ASP.NET and Windows server environments, with no mention of Linux, cross-platform .NET Core, or alternative web servers (e.g., Apache, Nginx). Linux equivalents, if any, are not discussed or referenced.

Recommendations:

Add examples and mitigation steps for cross-platform .NET (e.g., ASP.NET Core) running on Linux, including configuration differences.
Include guidance for deploying and configuring exception management on Linux-based web servers (e.g., Apache, Nginx, Kestrel) alongside IIS.
Reference Linux file paths, permissions, and deployment practices where relevant.
Mention and provide examples for non-Windows environments, such as containerized deployments (Docker), and cloud-native Linux scenarios.
Clarify which recommendations are Windows-specific and which are applicable to cross-platform or Linux environments.
Provide parity in code/configuration samples for both Windows and Linux hosting scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily through the use of Windows-centric technologies (e.g., WCF, ASP.NET, UseWindowsGroups), configuration examples referencing Windows roles and groups, and a lack of Linux/Unix-specific examples or tools. While some recommendations are generic, the only concrete implementation details and code samples are for Windows/.NET environments, with no equivalent Linux or cross-platform examples provided.

Recommendations:

Provide equivalent Linux/Unix examples for access control (e.g., using chmod, chown, setfacl for ACLs, and Linux user/group management).
Include cross-platform or Linux-specific code/configuration samples alongside Windows/.NET examples, especially for authorization and role management.
Mention Linux/Unix tools and patterns (e.g., sudoers, PAM, systemd service permissions) where relevant, not just Windows tools like UseWindowsGroups.
For sections referencing user-profile directories, clarify the Linux equivalent (e.g., /home/username) and provide examples for both platforms.
When discussing web application and database security, include references to open-source stacks (e.g., Node.js, Django, PostgreSQL) and their authorization mechanisms.
Balance the order of presentation so that Linux/Unix approaches are mentioned alongside or before Windows-specific ones, where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides PowerShell code samples and references to Windows-centric tools and file paths (e.g., C:\ paths, .exe processes). There are no examples or guidance for Linux VMs or cross-platform alternatives, and all extension configuration is shown using Windows/PowerShell paradigms. Linux support or parity is not mentioned, and the documentation implicitly assumes a Windows environment.

Recommendations:

Add equivalent examples for deploying and configuring antimalware on Linux VMs, using Azure CLI, ARM templates, or REST API.
Clarify whether Microsoft Antimalware is available for Linux VMs, and if not, explicitly state this limitation.
If Linux support exists, provide sample configuration files and command-line instructions relevant to Linux environments.
Avoid using only Windows file paths and process names in configuration samples; include Linux-style paths and process examples where applicable.
Present cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and Azure Storage Explorer (a GUI tool with a strong Windows association) for obtaining SAS tokens, without mentioning or providing examples for Linux-native or CLI-based workflows. The API example relies on Azure CLI authentication but does not clarify cross-platform compatibility or provide Linux-specific guidance. There are no command-line examples (e.g., using az CLI or Bash scripts) for Linux users, and no mention of Linux tools or patterns.

Recommendations:

Add explicit examples for obtaining SAS tokens using the Azure CLI (az storage container generate-sas) with command-line instructions suitable for Linux/macOS environments.
Clarify that Azure CLI and the Python SDK are cross-platform, and provide any necessary setup steps for Linux users (e.g., package installation, authentication).
Mention and provide examples for using Bash or shell scripting to automate SAS token generation and ingestion source creation.
If referencing Azure Storage Explorer, note its cross-platform availability and provide installation instructions for Linux.
Ensure screenshots and UI instructions are supplemented with equivalent CLI or code-based workflows for users who do not use Windows or GUIs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and concepts (e.g., BitLocker, privileged access workstation, contributor roles) are mentioned first or exclusively in several sections. While Linux is referenced (e.g., Azure Disk Encryption for Linux VMs), examples and tool explanations are often Windows-centric or lack Linux parity. There are no Linux-specific command-line or management examples, and secure workstation recommendations are based on Microsoft/Windows models without Linux alternatives.

Recommendations:

Provide Linux-specific examples and command-line instructions (e.g., using Azure CLI/Bash instead of only referencing Windows/PowerShell or BitLocker).
When discussing secure workstations, include guidance or references for securing Linux-based admin workstations, not just Microsoft PAW.
Present Linux and Windows options together, or alternate which is mentioned first, to avoid the perception of Windows as the default.
Where Windows tools (e.g., BitLocker, privileged access workstation) are mentioned, add equivalent Linux tools (e.g., dm-crypt, LUKS, Linux hardening guides) and link to relevant documentation.
Include Linux-focused security best practices and reference open-source security tools where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific protocols (TDS), linking to Windows Server documentation for TLS, and omitting Linux or cross-platform tooling and examples. There are no mentions of Linux-based client tools, nor are there instructions or references for managing Azure SQL security from non-Windows environments.

Recommendations:

Include examples and links for configuring secure connections from Linux-based clients (e.g., using sqlcmd, Azure CLI, or ODBC on Linux).
Reference cross-platform tools and protocols, not just Windows-specific ones (e.g., mention that TDS is supported by various clients on different OSes).
Provide parity in documentation links, such as linking to TLS documentation relevant for Linux and macOS users.
Explicitly mention that management and security features are accessible from non-Windows environments, and provide guidance or examples for those scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows tools and terminology are often mentioned first or exclusively (e.g., SMB 3.0, RDP, PowerShell), and Windows-specific libraries (e.g., .NET NuGet package for client-side encryption) are highlighted before or instead of Linux or cross-platform alternatives. PowerShell is given as a primary automation/configuration method, with less emphasis or detail on Linux CLI or scripting. Some sections lack Linux-specific examples or parity in instructions, especially for storage and VPN configuration.

Recommendations:

Provide Linux and cross-platform examples alongside Windows/PowerShell instructions, especially for configuration tasks (e.g., VPN, storage encryption).
Mention Linux tools and protocols (e.g., Samba for SMB, OpenSSH, Linux CLI) with equal prominence and detail.
Include references to Linux SDKs and libraries (e.g., Azure Storage SDK for Python, Java, or Node.js) for client-side encryption, not just .NET/Windows libraries.
When listing protocols or tools (e.g., SMB, RDP, PowerShell), clarify Linux equivalents and provide links to relevant documentation.
Ensure that automation and scripting examples are provided for both PowerShell and Bash/Azure CLI, and that Linux configuration steps are as detailed as Windows ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as Windows Server Active Directory, Privileged Access Workstations, and Windows Hello for Business) and patterns (like Microsoft Entra Connect for on-premises integration) without mentioning or providing Linux or cross-platform equivalents. There are no examples or guidance for Linux-based identity management, admin workstations, or password protection, and Windows terminology is used exclusively when discussing on-premises scenarios.

Recommendations:

Include examples and guidance for integrating Linux-based identity providers (such as OpenLDAP or FreeIPA) with Azure/Microsoft Entra ID.
Mention and provide parity for Linux admin workstation security models, such as using hardened Linux desktops for privileged access, alongside Windows PAWs.
Discuss password protection and synchronization for Linux-based systems, or reference third-party tools that can provide similar functionality.
When referencing tools like Microsoft Entra Connect, clarify if and how Linux environments can participate or what alternatives exist.
Avoid using Windows-specific terminology exclusively; provide cross-platform terminology and examples where possible.
Add explicit notes or links for Linux administrators on how to achieve similar security postures using non-Windows infrastructure.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows Hyper-V as the hypervisor technology, without mentioning or providing examples for Linux-based hypervisors or management tools. The terminology and security mechanisms described are specific to Windows environments, and there are no Linux or cross-platform perspectives or examples provided.

Recommendations:

Include references to Linux-based hypervisors (such as KVM or Xen) where relevant, and clarify how Azure supports or interacts with Linux guests and their security models.
Provide examples or explanations of how hypervisor security concepts apply to Linux VMs on Azure, including any differences in implementation or management.
Mention Linux-specific tools or commands (e.g., virsh, qemu, or Linux security modules) where appropriate, or at least acknowledge their existence and role in the Azure ecosystem.
Balance the discussion by explicitly stating Azure's support for both Windows and Linux guests, and how security boundaries and mitigations are enforced for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows and .NET bias. All code examples are in C# and target .NET/ASP.NET technologies, with configuration examples referencing IIS and web.config. References and steps often mention Windows-specific technologies (MSXML, http.sys, IIS, Win32 APIs) and Microsoft-centric frameworks (WCF, MVC, Web Forms). There are no Linux, cross-platform, or open-source web server examples (e.g., Apache, Nginx), nor are there any code samples in languages common on Linux (e.g., Python, Java, Node.js). Even generic security concepts are illustrated exclusively with Microsoft tooling and patterns.

Recommendations:

Provide equivalent examples for Linux-based environments, such as configuring headers in Apache (using .htaccess) or Nginx.
Include code samples in other popular web languages (Python/Flask, Node.js/Express, Java/Spring) to demonstrate input validation and security controls.
Reference cross-platform XML libraries and demonstrate disabling entity resolution in Java (SAX/DOM), Python (lxml), and Node.js.
When discussing HTTP headers, show how to set them in non-IIS environments (e.g., with Nginx, Apache, or via application code in various languages).
Avoid assuming .NET or Windows as the default; structure sections to present cross-platform or language-agnostic guidance first, then provide platform-specific details.
Mention open-source alternatives to Microsoft-specific libraries (e.g., OWASP Java Encoder, Python's html.escape for output encoding).
Balance references and links to include non-Microsoft documentation and best practices from the broader security community.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias by referencing Windows-specific technologies (such as Windows Fabric and Windows administrator accounts) and omitting equivalent Linux tools or scenarios. There are no examples or mentions of Linux-based environments, tools, or patterns, and Windows terminology is used exclusively when discussing platform management and security controls.

Recommendations:

Include references to both Windows and Linux environments where applicable, especially in sections discussing OS images, administrator accounts, and platform management endpoints.
Mention Linux equivalents for technologies like Windows Fabric or clarify if such features are Windows-only.
Describe how virus scans and endpoint protection are handled for Linux-based components or guest VMs.
Provide examples or notes on how ACLs, firewalls, and monitoring agents operate in Linux-based clusters.
Avoid using Windows terminology exclusively; use neutral or cross-platform terms where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias in several areas. Windows tools and patterns, such as the Windows Event Log service, are mentioned before their Linux equivalents (e.g., Syslog). There is a lack of concrete Linux-specific examples or guidance, and Windows diagnostic tools are referenced by name, while Linux logging is only briefly mentioned. This may make the documentation less accessible or actionable for Linux users.

Recommendations:

Provide Linux-specific examples and guidance alongside Windows examples, such as detailed steps for configuring Syslog collection and forwarding in Azure.
When listing log types or tools, present Windows and Linux options with equal prominence, or alternate their order to avoid implicit prioritization.
Reference Linux-native tools (e.g., rsyslog, journald) and their integration with Azure Monitor or other Azure services.
Include example commands or configuration snippets for both Windows (e.g., PowerShell, Event Viewer) and Linux (e.g., shell commands, log file paths).
Clarify in tables and text that both Windows and Linux are supported, and provide links to Linux-specific documentation where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific technologies (e.g., 'Microsoft Monitoring Agent', 'Azure SQL Database Windows Fabric platform', 'Active Directory Federation Services') without mentioning Linux or cross-platform equivalents. There are no examples or references to Linux-based monitoring agents, authentication methods, or operational tooling, and the term 'Windows' is explicitly used in the context of the Fabric platform. The documentation assumes a Windows-centric environment for management and monitoring, omitting Linux or open-source alternatives.

Recommendations:

Include references to Linux-based monitoring agents (e.g., OMS Agent for Linux, Azure Monitor Agent) and describe how monitoring/logging is handled on Linux hosts.
Mention cross-platform or Linux-native authentication and access control methods (such as integration with PAM, SSH, or SSSD) where relevant.
If the Azure SQL Database Fabric platform is Windows-only, clarify this and provide information on equivalent Linux-based services or note the lack thereof.
Provide examples or descriptions of operational tooling and workflows for both Windows and Linux environments to ensure parity.
Avoid using 'Windows' in platform names or descriptions unless it is strictly Windows-only, and clarify platform support where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing a specific security configuration example (Dynamic IP Security via web.config) only for App Service on Windows, without mentioning equivalent methods for Linux-based App Service. It references Windows-specific tooling (web.config, IIS) and omits Linux-native approaches or configuration files, leading to an incomplete experience for Linux users.

Recommendations:

Include equivalent instructions or references for restricting IP addresses on App Service for Linux, such as using app-level configuration, .htaccess (for Apache), or nginx configuration files.
When mentioning Windows-specific features (like web.config or IIS), immediately follow with Linux alternatives or note if a feature is unavailable.
Add explicit examples or links for Linux-based App Service security configurations to ensure parity.
Review other sections for similar patterns and ensure cross-platform coverage throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and technologies (such as BitLocker, Windows Firewall, Active Directory Federation Services, and Group Policy) without equivalent emphasis or examples for Linux. Windows terminology and tools are often mentioned first or exclusively, and there is a lack of Linux-specific operational guidance or examples, especially in areas like VM administration, disk encryption, and identity management.

Recommendations:

Provide Linux-specific operational examples and guidance alongside Windows examples, especially for VM administration, disk encryption, and identity management.
When mentioning Windows tools (e.g., BitLocker, Group Policy, Windows Firewall), also mention and briefly describe the Linux equivalents (e.g., dm-crypt, iptables/firewalld, PAM/SSSD for identity).
Avoid using Windows terminology as the default; instead, use cross-platform or neutral terms where possible, or explicitly mention both Windows and Linux.
Include Linux command-line examples (e.g., Bash, CLI) where PowerShell or Windows GUI steps are referenced.
Ensure that references to documentation or quickstarts include both Windows and Linux versions, especially in 'Next Steps' and operational sections.
Highlight Azure features or services that are platform-agnostic or provide parity between Windows and Linux, and call out any differences or limitations for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias throughout. It consistently references Windows-specific tools (such as AppLocker, Hyper-V, Group Policy, BitLocker, Windows Firewall, and PowerShell) as the primary or only examples for hardening, management, and security. There are no equivalent Linux tools or workflows mentioned, nor are there any Linux-specific examples or guidance for securing non-Windows management endpoints. The language assumes Windows as the default management environment, with no discussion of Linux-based administrative workstations or tools.

Recommendations:

Add parallel Linux examples and recommendations throughout, such as using iptables/nftables for firewalling, AppArmor/SELinux for application control, and open-source VPN solutions.
Include Linux-based management workstation hardening guidance (e.g., minimal install, sudoers configuration, SSH key management, Linux patching best practices).
Reference cross-platform Azure management tools (e.g., Azure CLI, which is available on Linux/macOS/Windows) and provide usage examples for both PowerShell and Bash.
Mention Linux equivalents for Windows security features (e.g., dm-crypt/LUKS for disk encryption, auditd for auditing, systemd services for restricting execution).
Discuss Linux domain integration options (e.g., using SSSD/realmd for joining Linux systems to Active Directory or Azure AD).
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or at least acknowledge Linux as a first-class management platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing all shell/command-line examples in PowerShell syntax (e.g., using 'cd' and 'git clone' in PowerShell code blocks), and does not show Linux/macOS-specific shell commands or mention platform differences. The instructions and code blocks assume a Windows environment, with no explicit guidance for Linux or macOS users. There is also a lack of explicit mention or examples for Linux tools or terminal usage, and no alternative instructions for non-Windows environments.

Recommendations:

Provide parallel shell command examples for Linux/macOS (e.g., use bash/zsh syntax and code blocks alongside PowerShell).
Use generic 'shell' or 'bash' code blocks for cross-platform commands, unless a command is truly Windows-specific.
Explicitly mention that the commands work on all platforms, or note any platform-specific differences.
Include installation and usage notes for Linux and macOS for prerequisites like Azure CLI, Git, and Visual Studio Code.
Add a section or callout for Linux/macOS users, clarifying any differences in environment variable setup, file paths, or authentication steps.
Avoid using PowerShell-specific code blocks unless necessary; prefer 'bash' or 'shell' for cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific protocols (e.g., SMB 3.0) and tools without equivalent Linux examples or alternatives. In the 'Data Protection & Storage' section, SMB (a Windows-native protocol) is mentioned for Azure File Shares, but there is no mention of NFS or Linux mounting instructions. Additionally, the order and phrasing often present Windows approaches or terminology first, and some links (e.g., Azure Disk Encryption for Windows VMs) are duplicated or misdirected, while Linux-specific guidance is less visible or missing.

Recommendations:

Include Linux-specific protocols and tools (e.g., NFS for Azure File Shares) alongside or before Windows examples.
Provide explicit Linux command-line or configuration examples where Windows tools or protocols are referenced.
Ensure parity in documentation links: for every Windows-specific link (e.g., Azure Disk Encryption for Windows VMs), provide and correctly link to the Linux equivalent.
Avoid referencing Windows protocols (such as SMB) exclusively; mention cross-platform or Linux-native options where available.
Review the checklist for opportunities to add Linux administration and security best practices, not just those that align with Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Remote management protocols are listed as SSH, RDP, and PowerShell remoting, with RDP and PowerShell (both Windows-centric) mentioned alongside SSH but without Linux-specific management tools or examples. The use of PowerShell for Azure management is referenced multiple times, and there are no Linux command-line or management tool examples. The documentation also refers to Microsoft Entra and other Microsoft-specific technologies without mentioning cross-platform or open-source alternatives, and does not provide parity for Linux users in terms of security tooling or operational patterns.

Recommendations:

When listing remote management protocols, provide Linux-first or at least equal examples (e.g., SSH, SCP, SFTP, and mention Linux-native management tools such as Ansible or Bash scripting for automation).
Include Linux command-line examples for Azure management, such as using the Azure CLI (az) in Bash, and reference cross-platform tools.
When referencing PowerShell, clarify that Azure PowerShell is cross-platform, or provide parallel Bash/Azure CLI examples.
Mention open-source identity and authentication solutions (e.g., integration with LDAP, SSSD, or other federated identity providers) where appropriate.
Ensure that security best practices and tooling recommendations are not limited to Microsoft or Windows-specific solutions, but also include guidance relevant to Linux-based deployments.
Add explicit notes or sections for Linux administrators, highlighting any differences or additional considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft and Windows-centric tools (e.g., Microsoft Defender for Cloud, Defender for Endpoint, PowerShell logs), and by omitting Linux-specific guidance, tools, or examples. There are no references to Linux event logs, Linux endpoint protection, or incident response workflows for non-Windows systems. The examples and recommendations assume a Windows environment and do not address Linux or cross-platform scenarios.

Recommendations:

Include equivalent Linux guidance for detection and response, such as monitoring Linux audit logs, syslog, or journald for ransomware indicators.
Mention Linux-compatible security solutions (e.g., Microsoft Defender for Endpoint on Linux, or third-party EDR/XDR tools) alongside Windows tools.
Provide examples of how to isolate or remediate compromised Linux systems, including relevant commands or procedures.
Reference Linux-specific attack vectors (e.g., SSH brute force) and mitigation strategies.
Ensure that any mention of PowerShell or Windows Event Logs is paired with Linux equivalents (e.g., Bash history, auditd logs).
Clarify that the recommendations apply to both Windows and Linux environments, or provide separate sections/examples for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it mentions Linux support in some areas (e.g., Azure Disk Encryption for Linux VMs, Azure Backup for Linux), Windows tools, technologies, and patterns (such as IIS, BitLocker, and PowerShell) are often referenced first or exclusively. Several diagnostic and configuration examples reference Windows-specific features (e.g., IIS trace logs, BitLocker, PowerShell cmdlets) without providing equivalent Linux guidance or examples. Linux tools and workflows are mentioned less frequently and sometimes only in passing.

Recommendations:

Provide Linux-specific examples and workflows alongside Windows ones, especially for configuration, diagnostics, and security operations.
When referencing Windows tools (e.g., PowerShell, IIS, BitLocker), include equivalent Linux tools (e.g., Bash/CLI, Apache/Nginx logs, dm-crypt/LUKS) and instructions.
Avoid presenting Windows technologies or tools first by default; instead, present both Windows and Linux options in parallel where possible.
Expand sections that mention Linux only in passing (e.g., 'Azure Disk Encryption for Linux VMs') with concrete usage examples and links to relevant Linux documentation.
Ensure that all code snippets, command-line instructions, and troubleshooting steps are available for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows and Azure-centric bias by exclusively referencing Microsoft and Windows-based tools (e.g., Microsoft Defender, Azure Backup, MARS agent, Active Directory) and omitting Linux-specific examples or tools. Backup and recovery guidance is focused on Azure and Windows Server, with no mention of Linux backup strategies or tools. There are no Linux command-line or open-source tool examples, and the guidance assumes a Microsoft ecosystem, which may not be representative of mixed or Linux-heavy environments.

Recommendations:

Include examples and guidance for Linux systems, such as using rsync, tar, or open-source backup solutions (e.g., Bacula, Duplicity, Restic) for backup and recovery.
Mention Linux-native security tools (e.g., auditd, SELinux, AppArmor, ClamAV) alongside Microsoft Defender and Azure tools.
Provide parity in incident response and malware analysis sections by referencing Linux log sources (e.g., syslog, journald), authentication systems (e.g., PAM, LDAP), and forensics tools (e.g., Sleuth Kit, Volatility).
When listing backup options, include Linux on-premises and cloud backup strategies, not just Windows Servers and Azure-native solutions.
Balance references to Active Directory with mentions of common Linux directory/authentication solutions.
Explicitly state that the guidance applies to multi-platform environments and provide links or references to Linux and open-source documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias. In the 'InstallAgent' section, Windows-related link types ('InstallAgentOnWindowsVirtualMachine', 'InstallAgentOnWindowsNonAzure') are listed before their Linux equivalents, and the only detailed example link provided is to a Windows DNS connector. There is also a lack of Linux-specific examples or references, and the only connector example referenced is for Windows. No PowerShell or Windows command-line examples are present, but the overall pattern and example selection favor Windows environments.

Recommendations:

Add Linux-focused examples and references, such as linking to a Linux data connector template (e.g., Syslog or Linux agent).
When listing options (such as link types), alternate or randomize the order, or list Linux and Windows together to avoid 'Windows first' ordering.
Provide at least one detailed example or screenshot for a Linux-based connector alongside the Windows DNS connector.
Explicitly mention parity and support for both Windows and Linux environments in the introduction and relevant sections.
If referencing external documentation or templates, ensure Linux connectors are equally represented.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and authentication methods (e.g., Windows Hello) before or instead of Linux equivalents, and by omitting concrete Linux-focused examples or tools. While the text mentions that Microsoft Defender for Cloud protects both Linux and Windows, practical examples, screenshots, and tool references are either Windows-centric or generic, with no Linux-specific guidance or parity in authentication or system management features.

Recommendations:

Provide explicit Linux-focused examples and screenshots alongside Windows ones, especially when demonstrating threat detection, backup, or remediation steps.
When listing authentication options, mention Linux-compatible passwordless and multifactor authentication solutions (e.g., FIDO2, PAM modules, Linux desktop integrations) alongside Windows Hello.
Include references to Linux-native tools and patterns (such as SSH key management, Linux firewall configuration, or integration with Linux SIEM agents) where Windows tools are mentioned.
Ensure that all actionable recommendations and feature descriptions clarify support for both Linux and Windows, and provide links to Linux-specific documentation where available.
Balance the order of presentation so that Linux and Windows are given equal prominence, rather than defaulting to Windows-first language or examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments, particularly through the use of PowerShell and .NET/NUnit examples, and by referencing Windows-centric tools and patterns before or instead of Linux equivalents. The 'nunit-test-runner' pivot assumes a Windows/.NET environment, and there are no explicit Linux or cross-platform shell examples for .NET users. Azure CLI usage is platform-neutral, but the overall structure and examples prioritize Windows workflows, especially for .NET users.

Recommendations:

Provide explicit Linux/macOS shell examples alongside PowerShell/.NET commands, especially for .NET/NUnit workflows (e.g., show 'dotnet' commands in bash/zsh context).
Clarify that .NET and NUnit can be used cross-platform, and provide guidance for Linux/macOS users (e.g., using Mono or .NET Core on Linux).
Wherever PowerShell is used, offer equivalent bash/zsh commands for Linux/macOS users.
Mention and link to Linux/macOS installation instructions for dependencies like Azure CLI and .NET SDK.
Add troubleshooting notes or tips for common Linux/macOS issues (e.g., file permissions, environment variable syntax differences).
Ensure that all code snippets and configuration steps are validated for cross-platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/PowerShell bias by exclusively providing PowerShell-based tooling and scripts (e.g., Get-DanglingDnsRecords.ps1), referencing PowerShell in the 'Next steps', and omitting any Linux-native or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or Linux-specific instructions, which may hinder Linux users or those preferring non-Windows environments.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
Include Bash script examples or instructions for running the detection and remediation steps on Linux systems.
Clarify whether the provided PowerShell scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide installation guidance if so.
Reference or link to any available open-source or third-party tools that can be run natively on Linux for detecting dangling DNS records.
Ensure that all prerequisite and setup instructions include both Windows and Linux environments (e.g., how to authenticate to Azure, install required modules, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias, with nearly all configuration and code examples tailored to Windows-centric technologies (ASP.NET, IIS, web.config, BitLocker, Windows Firewall, WCF, etc.). There are no Linux or cross-platform equivalents provided for key security practices, and Windows tools and patterns are mentioned exclusively or before any alternatives. Linux/Unix-based approaches, tools, or configuration examples are entirely absent, even for generic security recommendations.

Recommendations:

For every configuration or code example using Windows-specific tools (e.g., web.config, IIS, BitLocker, Windows Firewall), provide equivalent instructions for Linux environments (e.g., Apache/Nginx configuration, iptables/firewalld, LUKS/dm-crypt for disk encryption).
Include cross-platform or Linux-specific code/configuration snippets alongside Windows examples, especially for HTTP headers (CSP, X-Frame-Options, X-Content-Type-Options) and CORS setup.
Reference Linux/Unix security tools and best practices (e.g., SELinux, AppArmor, fail2ban, systemd service hardening) where relevant.
Mention open-source and cross-platform frameworks (e.g., Node.js, Django, Flask, Spring) in addition to ASP.NET and WCF, and provide examples for those stacks.
When discussing Azure-specific features, clarify which recommendations are applicable to Linux-based Azure services and provide relevant guidance.
Explicitly state when a recommendation is Windows-only, and offer alternative approaches for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows and Microsoft-centric tools and workflows. All playbook examples and templates focus on Microsoft products (e.g., Microsoft Teams, Outlook, Defender for Endpoint, Entra ID, Azure Firewall) with no mention of Linux-native tools, open-source alternatives, or Linux-specific workflows. There are no examples of integrating with Linux firewalls (like iptables or nftables), Linux user management, or Linux-based notification/email systems. The documentation assumes a Microsoft ecosystem and does not provide parity for Linux environments.

Recommendations:

Include examples of playbooks that interact with Linux-based firewalls (e.g., iptables, nftables) for blocking IP addresses.
Provide templates or guidance for disabling Linux user accounts (e.g., using usermod or passwd commands) as part of incident response.
Add notification examples using Linux-native tools (e.g., sendmail, mailx, or integration with open-source chat platforms like Mattermost or Rocket.Chat).
Mention and demonstrate integration with open-source ticketing systems (e.g., OTRS, RT) alongside ServiceNow.
Balance the order of examples so that Linux/open-source options are presented alongside or before Microsoft/Windows-specific tools where applicable.
Explicitly state that playbooks can be extended to Linux environments and provide links or references to relevant connectors or scripts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing migration steps and examples on Windows systems, such as referencing the 'Windows Security Events' solution, 'Windows Security Event connector', and 'Windows agent-based connections' without providing equivalent Linux examples or guidance. Linux-specific features are only briefly mentioned (e.g., Linux multi-homing) and not elaborated upon. There are no step-by-step instructions or connectors highlighted for Linux systems, and the documentation does not mention Linux tools or patterns for migration.

Recommendations:

Add parallel Linux-focused migration steps, including references to Linux-specific connectors and solutions (e.g., 'Linux Security Events via AMA').
Provide examples and screenshots for Linux agent installation, configuration, and validation, similar to the Windows examples.
Include guidance on uninstalling the legacy agent from Linux systems, referencing relevant commands and documentation.
Mention Linux tools and patterns (such as syslog, auditd, or Linux-specific data connectors) alongside Windows tools.
Ensure that Linux and Windows instructions are presented with equal prominence, or provide a clear structure separating guidance for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Use data collection rules for your Windows Security Events' section, which exclusively discusses Windows Server and the Windows Security Events connector. There are no equivalent examples or guidance for collecting security events from Linux systems, nor are Linux-specific connectors or data collection rules mentioned. The focus on Windows tools and lack of Linux parity may leave Linux administrators without clear guidance for cost optimization.

Recommendations:

Add a section or examples for collecting and optimizing security event ingestion from Linux servers, including relevant connectors (e.g., Syslog, CEF) and data collection rules.
Mention Linux data sources and how to use data collection rules or agents (such as the Azure Monitor Agent on Linux) to filter and optimize log ingestion.
Ensure that references to connectors and data collection are platform-neutral where possible, or provide parallel guidance for both Windows and Linux environments.
Review the documentation for other areas where only Windows-centric tools or workflows are described, and add Linux equivalents or cross-platform instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell and Windows-centric deployment methods. The manual deployment section provides detailed PowerShell instructions before Python, and the PowerShell example assumes use of the Azure portal and PowerShell Core, both of which are more familiar to Windows users. There is no mention of Linux shell (e.g., Bash) or CLI-based deployment options, and no explicit Linux or cross-platform examples are provided. The Python deployment requires Visual Studio Code, which, while cross-platform, is not the default editor on Linux systems. There are no examples using Azure CLI, Bash, or Linux-native tools.

Recommendations:

Add explicit Linux/Bash shell deployment instructions, including examples using Azure CLI and Bash scripts.
Present deployment options in a neutral order (e.g., ARM template, Python, PowerShell) or clarify that all are equally supported.
Include notes or examples for Linux users, such as using the Azure CLI in Bash to deploy and configure Function Apps.
Highlight cross-platform tooling (e.g., Azure CLI, VS Code) and provide alternatives for users who may not use PowerShell or Windows.
Ensure that references to workspace keys and configuration steps are not Windows-specific (e.g., avoid linking only to Windows agent documentation).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by recommending Windows-centric tools and environments (Azure Machine Learning VM, Visual Studio Code) as primary options, and by relying on the Azure CLI for authentication without mentioning cross-platform or Linux-specific alternatives. There are no explicit Linux or macOS setup instructions, and no mention of Linux-native authentication methods or terminal usage, despite the tutorial being Jupyter/Python-based and thus inherently cross-platform.

Recommendations:

Explicitly mention that the tutorial works on Linux and macOS, not just Windows.
Provide example instructions for installing and using Azure CLI on Linux and macOS.
Include alternative authentication options (such as Azure Identity's DefaultAzureCredential, device code login, or environment variables) that work well on all platforms.
Suggest Linux-friendly environments (e.g., JupyterLab on Ubuntu, Anaconda, or cloud-based Jupyter services) alongside Windows tools.
Clarify that Visual Studio Code and Jupyter Notebooks are available on Linux and macOS, and provide links or setup steps for those platforms.
Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_terms

⚠️ windows_examples

Summary:

The documentation shows a mild Windows bias. Windows-specific terms (such as 'NTDomain', 'DeviceNtDomain', 'DestinationNTDomain', 'SourceNTDomain') are present as field names and descriptions. In several field descriptions, Windows is mentioned explicitly (e.g., 'The Windows domain of the device address'). File path examples consistently list the Windows path first (e.g., 'C:\ProgramFiles\WindowsNT\Accessories\wordpad.exe' before '/usr/bin/zip'). There are no PowerShell-specific examples or exclusive use of Windows tools, but Windows terminology and examples are more prominent or appear before Linux equivalents.

Recommendations:

Alternate the order of Windows and Linux/Unix examples in file paths, or list Linux examples first in some cases.
Where possible, generalize field descriptions to avoid Windows-centric language (e.g., say 'domain name' instead of 'Windows domain name'), or provide both Windows and Linux/Unix context.
Add clarifying notes for fields that are Windows-specific, and provide equivalent Linux/Unix fields or note when not applicable.
Ensure that examples and terminology are balanced between Windows and Linux/Unix systems throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias: file path examples consistently show Windows paths (e.g., c:\temp) before Linux equivalents (e.g., /tmp), and in some cases, only the Windows path is shown in code snippets. In configuration examples, the sample_file_path is set to a Windows path by default. There are no PowerShell-specific commands or Windows-only tools, but the ordering and emphasis of examples favor Windows. Linux-specific troubleshooting is only briefly mentioned in the Docker/Ubuntu section, and Linux file path conventions are not given equal prominence throughout.

Recommendations:

Present Linux and Windows file path examples side-by-side or alternate their order to avoid always listing Windows first.
In code snippets, use placeholder paths (e.g., <path-to-temp-dir>) and provide both Windows and Linux examples in comments.
Ensure that all instructions and examples are equally applicable to both Linux and Windows environments.
Add explicit Linux shell command examples where relevant (e.g., for file creation, permissions, or service management).
Highlight any OS-specific considerations (such as file permissions or service management) in dedicated callout sections.
Review all code and configuration blocks to ensure Linux parity and avoid defaulting to Windows-centric paths or conventions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows-centric technologies and patterns, such as ASP.NET, ADFS, web.config, and PowerShell commands. All code/configuration examples are for Windows/.NET environments, with no mention of Linux, cross-platform, or open-source alternatives. There are no examples for Linux-based web servers, identity providers, or session management tools, and Windows tools and patterns are presented exclusively and first.

Recommendations:

Include equivalent examples for Linux-based web servers (e.g., Apache, Nginx) and frameworks (e.g., Node.js/Express, Django, Flask) for session and cookie management.
Provide configuration and code samples for cross-platform identity providers (e.g., Keycloak, Auth0) and logout/session management in non-Windows environments.
When referencing tools like PowerShell or web.config, also mention and provide examples for Linux/Unix equivalents (e.g., Bash scripts, environment variables, config files in YAML/JSON).
Add guidance for securing cookies and sessions in non-.NET stacks (e.g., using Set-Cookie headers in Nginx/Apache, middleware in Express/Django).
Present cross-platform or Linux-first examples alongside or before Windows-specific ones to ensure parity and inclusiveness.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, specifically Windows DNS servers, and does not mention or provide guidance for Linux-based DNS servers or cross-platform scenarios. All examples, prerequisites, and instructions are tailored exclusively for Windows Server, with no Linux equivalents or alternatives discussed. The tools and terminology (e.g., Windows DNS Events, Windows Server DNS, Windows event logs) are Windows-specific, and there is no indication of parity or support for Linux DNS logging or ingestion.

Recommendations:

Add a section clarifying whether Linux-based DNS servers (such as BIND or dnsmasq) are supported, and if not, explicitly state this limitation.
If Linux DNS log ingestion is possible, provide equivalent instructions, prerequisites, and examples for popular Linux DNS servers.
Include Linux-specific tools, log file paths, and configuration steps where relevant.
Use more inclusive language in titles and throughout the documentation (e.g., 'Stream and filter DNS logs with the AMA connector' instead of 'Windows DNS logs').
If the connector is Windows-only, suggest alternative solutions or connectors for Linux DNS log ingestion, or link to relevant documentation.
Ensure that any API examples or schemas are annotated to indicate whether they are Windows-specific or cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias primarily by referencing Windows-centric tools and automation methods (notably PowerShell), mentioning them before or instead of cross-platform or Linux-native alternatives. The only automation scripting example given is PowerShell, and there is no mention of Linux command-line tools or scripting options. The documentation also references the Azure and Defender portals, which are web-based and cross-platform, but when it comes to automation and exporting, only Windows/PowerShell options are highlighted, with no Linux or CLI parity.

Recommendations:

Include examples of automating rule management using Azure CLI (az) or Bash scripts, not just PowerShell.
Explicitly mention that API and PowerShell automation can be performed from Linux/macOS as well, and provide cross-platform instructions.
Reference and provide examples for using REST API via curl or other Linux-native tools for rule management.
Where PowerShell is mentioned, also provide equivalent commands or scripts using Azure CLI or generic REST API calls.
Clarify that exporting/importing ARM templates can be done from any OS, and provide sample commands for Linux environments.
If possible, add a section or callout for Linux users, summarizing the parity and any differences in workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and technologies (such as PowerShell, Windows events, and Windows malware families) without providing equivalent Linux examples or mentioning Linux-specific attack patterns. PowerShell is highlighted in multiple detection scenarios, and Windows alerts are used as illustrative examples. There is no mention of Linux-based threats, tools, or detection patterns, nor are Linux command-line or log sources referenced.

Recommendations:

Include detection scenarios and examples that reference Linux-based attacks, such as suspicious Bash or shell activity, Linux-specific malware, or Linux log sources (e.g., syslog, auditd).
Provide examples of multistage attacks that involve Linux endpoints or mixed-OS environments.
Balance the use of Windows-specific tools (like PowerShell and Windows Event Logs) with Linux equivalents (such as Bash, systemd, or Linux audit logs).
Add references to Linux security solutions (e.g., Microsoft Defender for Endpoint on Linux, or integration with Linux EDR tools) where appropriate.
Ensure that tables and illustrative examples include both Windows and Linux alerts/incidents to demonstrate parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-based data connectors and tooling. Windows-specific agents and event types (e.g., Windows agent, SecurityEvent, W3CIISLog) are mentioned explicitly, while Linux equivalents are only referenced in a single entry (Syslog via Legacy Agent) and not in parity with the Windows coverage. The documentation for Microsoft Exchange and Security Events focuses solely on Windows machines and agents, with no comparable Linux event collection examples or guidance. Additionally, links and instructions for agent installation reference Windows-centric tabs and tools, and Linux agent scenarios are not equally detailed.

Recommendations:

Provide Linux-based examples and instructions alongside Windows ones for all relevant connectors, especially for event and log collection.
Ensure that agent installation documentation references both Windows and Linux agents equally, with clear parity in detail and guidance.
Include Linux event types (such as auditd, auth.log, etc.) and their mapping to Log Analytics tables where applicable.
Where Windows-specific tools or logs are mentioned (e.g., W3CIISLog, SecurityEvent), add Linux equivalents (e.g., Apache/Nginx logs, Syslog, audit logs) and describe their ingestion.
Review all prerequisite and setup sections to ensure Linux users are not omitted and have clear, actionable steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing the PowerShell New-GUID cmdlet as an example for generating GUIDs, without mentioning Linux or cross-platform alternatives. No Linux or macOS command-line tools are suggested for this task, and the only explicit tooling example is Windows-specific. This may hinder Linux or cross-platform users from following the guidance seamlessly.

Recommendations:

When suggesting how to generate a GUID, include cross-platform and Linux-native options, such as 'uuidgen' (available on most Linux/macOS systems) or Python's uuid module.
Rephrase the sentence to mention multiple platforms, e.g., 'Generate it by using any development tool, an online generator, the PowerShell New-GUID cmdlet (Windows), or the uuidgen command (Linux/macOS)'.
Wherever command-line examples are given, provide both Windows (PowerShell/CMD) and Linux/macOS (bash/sh) equivalents.
Audit the documentation for other places where Windows tools or patterns are referenced first or exclusively, and ensure Linux parity in examples and tool recommendations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a PowerShell script for automating the rotation of BTP client secrets, relying on Azure PowerShell modules and cmdlets. No equivalent Bash, Azure CLI, or cross-platform scripting example is provided. The automation guidance is thus Windows-centric, and Linux users are not given parity in automation instructions.

Recommendations:

Provide equivalent automation examples using Azure CLI and Bash scripts for Linux/macOS environments.
Explicitly mention that the PowerShell script is intended for Windows users, and link to or include Linux-compatible alternatives.
Where possible, use cross-platform tools (e.g., Azure CLI) in examples, or offer both PowerShell and Bash/CLI versions side by side.
Review other automation or scripting sections for similar bias and ensure Linux users have clear, actionable guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates Windows bias by recommending and documenting tools (such as LightIngest) that are Windows-only, without providing Linux alternatives or guidance for non-Windows environments. There are no Linux-specific examples or instructions, and the documentation does not clarify cross-platform compatibility for other tools (such as AzCopy or the Custom Log Ingestion script). The order of presentation and lack of parity in tooling further reinforce a Windows-centric approach.

Recommendations:

Provide explicit instructions and examples for Linux environments, including installation and usage of ingestion tools on Linux.
If a tool is Windows-only (e.g., LightIngest), recommend and document alternative ingestion methods for Linux (such as using Azure Data Explorer's ingestion REST API, Python SDK, or other cross-platform tools).
Clarify the cross-platform compatibility of tools like AzCopy and the Custom Log Ingestion script, and include Linux/macOS installation and usage steps where applicable.
Present platform-agnostic or Linux-first options alongside Windows instructions to ensure parity and inclusivity.
Add a table or section summarizing supported platforms for each tool, with links to relevant documentation for each OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: file paths and process examples use Windows conventions (e.g., C:\Windows\explorer.exe, C:\Windows\System32\notepad.exe), registry fields reference Windows Registry exclusively, and user identity examples use Windows formats (e.g., Contoso\JSmith, SID). There are no Linux or cross-platform examples for file paths, process names, or user identities, and no mention of Linux equivalents for registry or process fields. No Linux-specific tools or patterns are referenced.

Recommendations:

Provide Linux/Unix examples alongside Windows examples for file paths (e.g., /usr/bin/bash), process names, and command lines.
Include Linux user identity formats (e.g., UID, user@domain) in user field examples.
Clarify that registry fields are Windows-specific and, if applicable, describe how similar data might be represented on Linux (e.g., configuration files, /etc).
Add examples of alerts and schema usage from Linux-based systems to ensure parity.
Where possible, use neutral or cross-platform examples (e.g., generic process names, file paths) to avoid platform-specific bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a clear Windows bias in the sections describing how to generate and sanitize ARM templates for playbooks. The only automation script provided is a PowerShell script, and instructions reference running it in Visual Studio Code, Windows PowerShell, or PowerShell Core. There are no examples or guidance for performing these tasks on Linux or macOS, nor are alternative tools or shell commands mentioned. The documentation assumes the user is on a Windows environment, both in tool recommendations and in the order of presentation.

Recommendations:

Provide equivalent instructions for Linux and macOS users, including how to run the PowerShell script using PowerShell Core on those platforms.
Explicitly state that PowerShell Core is cross-platform and provide installation links for Linux/macOS.
Offer alternative methods for extracting and sanitizing ARM templates using Azure CLI, Bash, or other cross-platform tools.
Include example commands and screenshots from Linux/macOS terminals where appropriate.
Avoid assuming Visual Studio Code or Windows PowerShell as the default environment; mention cross-platform editors and shells.
Add a section or note clarifying platform compatibility for all scripts and tools referenced.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by focusing heavily on Windows-specific tools, commands, and attack techniques (such as rundll32.exe, PowerShell, Certutil, Exchange PowerShell Snapin, and Windows System Shutdown/Reboot). Many hunting queries and analytic rules reference Windows-centric binaries and behaviors, with little to no mention of Linux or cross-platform equivalents. There are no explicit Linux examples or references to Linux-specific threats, tools, or command-line patterns. This may leave Linux users without clear guidance or parity in threat detection and hunting.

Recommendations:

Add Linux-specific examples and hunting queries, such as detections for common Linux persistence or privilege escalation techniques (e.g., cron jobs, systemd service abuse, SSH key misuse).
Include analytic rules and hunting queries that reference Linux-native tools and binaries (e.g., bash, systemctl, sudo, /etc/passwd modifications).
Balance the documentation by providing both Windows and Linux perspectives for each content area (process, file, registry, network, etc.), or explicitly state if a given rule is Windows-only.
Highlight cross-platform detection strategies where possible, and clarify which rules are applicable to Linux, macOS, or other operating systems.
Consider adding a section or table summarizing OS coverage for each analytic rule and hunting query.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_heavy_examples

Summary:

The documentation exhibits a moderate Windows bias. Windows-specific identifiers (e.g., SID, Windows domain\username format) are consistently listed before Linux equivalents (e.g., UID, simple username). Examples and field priorities often use Windows-centric formats, and Windows terminology (such as SIDs, domain\username, and C:\Windows\System32\svchost.exe) is more prominent and detailed than Linux references. Linux is mentioned, but usually after Windows, and with less detail or fewer examples.

Recommendations:

Alternate the order of Windows and Linux examples throughout the documentation, or present them side-by-side to ensure parity.
Provide Linux-specific examples (e.g., UID, /usr/bin/processname) wherever Windows examples are given (such as for ActorUserId, GroupId, ActingAppName).
Expand on Linux username and group formats (e.g., user@host, /etc/passwd entries) in the same detail as Windows formats.
Include Linux-specific terminology and normalization recommendations (e.g., mention GID for groups, typical Linux username conventions, and process paths).
Ensure that field type recommendations and normalization guidelines are equally detailed for both Windows and Linux systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_examples

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias through the exclusive use of Windows-style file paths (e.g., C:\Windows\explorer.exe), Windows-specific concepts (such as integrity levels and UAC), and examples referencing Windows tools and formats. While some fields mention Linux, there are no Linux-specific examples, terminology, or parity in explanations. Windows terminology and references are consistently presented first or exclusively, with little to no Linux context.

Recommendations:

Provide Linux-specific examples alongside Windows examples, such as using /usr/bin/bash or /usr/bin/sshd in process name/path fields.
When describing fields like integrity levels or session IDs, include Linux equivalents or clarify how these concepts map (or do not map) to Linux systems.
Balance the use of Windows and Linux terminology in field descriptions and examples, ensuring both platforms are represented.
Add explicit notes or tables indicating differences in field population or semantics between Windows and Linux sources.
Where Windows tools or concepts are referenced (e.g., UAC, Win32 integrity levels), provide Linux analogs or state when no direct equivalent exists.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

While the documentation is focused on setting up Pacemaker on RHEL in Azure and is generally Linux-centric, there are notable instances of Windows bias. The only example for creating and attaching Azure shared disks is provided using PowerShell, with Azure CLI and portal options relegated to a brief mention. The documentation references PowerShell and Windows-centric tools before Linux-native equivalents, and some links for managed identity configuration point to Windows VM instructions. This may create friction for Linux administrators who expect parity in CLI or portal-based examples.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples for creating and attaching Azure shared disks, as CLI is more commonly used in Linux environments.
Include explicit step-by-step instructions for performing key Azure resource management tasks (e.g., disk creation, managed identity assignment) using the Azure CLI and Azure portal, not just PowerShell.
Ensure that all referenced links for identity and resource configuration include Linux VM-specific instructions or clarify when steps are OS-agnostic.
Review all sections for ordering bias, ensuring that Linux-native tools and workflows are presented first or at least equally with Windows/PowerShell alternatives.
Where possible, avoid referencing Windows-specific documentation or tools unless strictly necessary, and always provide the Linux equivalent.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While most instructions are cross-platform (using Node.js, npm, and Azure CLI), there are several references that prioritize or exclusively mention Windows tools or patterns. Notably, the instructions refer to 'command prompt' (a Windows term) instead of 'terminal' or 'shell', and a key link for deploying Node.js apps points to a Windows PowerShell-based tutorial, with no equivalent Linux/Mac instructions or links. There are no explicit Linux shell or macOS Terminal examples, and the language used assumes a Windows environment.

Recommendations:

Replace or supplement 'command prompt' with 'terminal' or 'shell' to be inclusive of Linux and macOS users.
Where links are provided for deploying Node.js applications (e.g., 'Node.js Cloud Service using Windows PowerShell'), add equivalent links or instructions for Linux and macOS environments.
Explicitly mention that all npm and Node.js commands work on Linux, macOS, and Windows, and provide example shell commands where appropriate.
If referencing editors, note that Visual Studio Code is cross-platform, or suggest alternatives available on Linux/macOS.
Review included snippets and referenced tutorials to ensure they do not contain Windows-specific commands or paths, or provide alternatives if they do.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Windows and Linux instructions for setting environment variables, but Windows instructions are presented first, and Windows-specific tools (such as the System Properties dialog) are described in more detail. The Linux section is less detailed and assumes more user familiarity with the command line. There are also references to Windows environment variable syntax (e.g., %userprofile%) before Linux equivalents (~), and the Windows workflow is described in a more step-by-step, GUI-oriented manner, while Linux instructions are more condensed and terminal-focused. There are no PowerShell-specific commands, but the overall pattern prioritizes Windows tools and workflows.

Recommendations:

Present Linux and Windows instructions in parallel or in the same level of detail, rather than always listing Windows first.
Provide equally detailed, step-by-step instructions for Linux users, including screenshots or explicit command examples for common tasks (e.g., editing .bashrc with nano or vim).
When referencing environment variable paths, list both Windows (%userprofile%) and Linux (~) syntaxes together, or default to platform-agnostic language.
Ensure that all examples and workflows are provided for both platforms, with clear parity in explanation and troubleshooting steps.
Consider including PowerShell and Bash equivalents for any command-line instructions, and avoid assuming GUI access for Windows users only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific event sources (e.g., 'Microsoft-Windows-Sysmon'), using Windows-centric terminology and examples (such as EventID, ProcessName, and the Event table), and prioritizing Windows/PowerShell tools for deployment and management (e.g., recommending PowerShell scripts for deleting functions, and referencing Azure portal and PowerShell for ARM template deployment). There is a lack of explicit Linux or cross-platform deployment/testing instructions, and examples focus on Windows event sources or generic KQL, without showing Linux-specific log sources or command-line tools.

Recommendations:

Include Linux-specific examples, such as parsing logs from common Linux sources (e.g., auth.log, messages, or Linux audit logs) and show how to map these to ASIM schemas.
Provide deployment and management instructions using cross-platform tools such as Azure CLI and/or REST API, not just PowerShell and Azure Portal.
When referencing event sources or tables, include both Windows and Linux examples (e.g., show Syslog and Windows Event Log side by side).
Explicitly mention and provide examples for Linux-based environments in sections discussing log collection, parser development, and testing.
If recommending scripts or tools, ensure that Linux-compatible alternatives (e.g., Bash scripts, Azure CLI) are documented alongside PowerShell.
Review terminology to ensure it is inclusive of both Windows and Linux environments, avoiding Windows-centric language where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for enabling duplicate message detection in Azure Service Bus. However, there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool, and the PowerShell section is given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of sections places Azure CLI before PowerShell, which is positive, but the heavy inclusion of PowerShell commands and lack of Linux-native shell examples may make the documentation feel Windows-biased.

Recommendations:

Add bash (Linux shell) script examples alongside Azure CLI, demonstrating how to use the CLI in a Linux environment.
Clarify in the PowerShell section that Azure PowerShell is available cross-platform, but also provide equivalent bash or shell scripting examples for Linux users.
Consider including a table or summary comparing the different approaches (Azure portal, CLI, PowerShell, ARM templates) and their platform compatibility.
If possible, add notes or links to Linux-specific guidance for installing and using the Azure CLI and PowerShell on Linux.
Ensure that future documentation includes Linux-native command-line examples where applicable, not just PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by explicitly providing a dedicated 'Azure PowerShell' section with command references, while the 'Azure CLI' section is minimal and lacks concrete command examples. The PowerShell section is more detailed and appears after the CLI, but the CLI section is underdeveloped. There are no Linux-specific instructions or examples, and the only deployment link for Resource Manager templates points to a PowerShell-based deployment guide. No Bash or Linux shell examples are provided, and the documentation assumes familiarity with Windows-centric tools.

Recommendations:

Provide explicit Azure CLI command examples for managing IP firewall rules, similar to the PowerShell section.
Include Bash/Linux shell examples for deploying ARM templates (e.g., using 'az deployment group create').
Ensure that deployment links reference both PowerShell and CLI (Bash) guides, or provide a cross-platform deployment section.
Balance the order and depth of CLI and PowerShell sections, ensuring Linux users are equally supported.
Add notes or examples for common Linux environments, such as using the Azure CLI in Bash or Cloud Shell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. The PowerShell examples use Windows-style syntax (backticks for line continuation), and there is no mention of Linux-specific considerations or alternative tools. The ordering of sections (CLI before PowerShell) is good, but the presence of PowerShell as a primary method and the lack of bash or Linux-native scripting tips indicate a mild Windows bias.

Recommendations:

Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
Add bash/zsh shell examples or notes for Linux users, especially for scripting or automation.
Mention that PowerShell Core is available cross-platform, or clarify that the examples use Windows PowerShell syntax.
Consider adding a note about line continuation differences (backtick vs. backslash) between PowerShell and bash.
Ensure that all examples and instructions are tested and presented in a way that is accessible to both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by specifically mentioning the handling of VMware tools for Windows VMs during failover/failback, without referencing Linux VMs or their equivalent tooling. There are no examples or notes about Linux VMs, their requirements, or any differences in the failback process. The only OS-specific guidance is for Windows, and Linux scenarios are omitted.

Recommendations:

Add equivalent notes or guidance for Linux VMs, such as how VMware tools or open-vm-tools are handled during failover/failback.
Explicitly mention if the process is the same or different for Linux VMs, and highlight any OS-specific considerations.
Include troubleshooting tips or common issues for Linux VMs, similar to the note provided for Windows.
Ensure parity in examples and notes by providing both Windows and Linux perspectives wherever OS-specific behavior is relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows (e.g., Command Prompt, PowerShell, Visual Studio) exclusively or before any Linux alternatives. There are no explicit instructions or examples for Linux users, such as using Bash, VS Code, or .NET CLI on Linux. The prerequisites and step-by-step instructions assume a Windows environment, and no mention is made of cross-platform considerations.

Recommendations:

Add explicit instructions and examples for Linux users, such as using Bash or terminal commands instead of Command Prompt/PowerShell.
Mention and provide steps for installing and using .NET SDK and running the sample code on Linux/macOS, including any differences in file paths or command syntax.
Include VS Code as an alternative to Visual Studio in the prerequisites, and provide guidance for Linux/macOS users.
When referencing command-line actions, use cross-platform .NET CLI commands and clarify that they work on Windows, Linux, and macOS.
Add screenshots or terminal output examples from Linux environments where appropriate.
Avoid assuming the use of Notepad or other Windows-only tools for copying/storing connection strings; suggest cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based integration, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation section explicitly instructs users to create a Windows VM and does not mention Linux VMs or provide Linux-specific instructions, reinforcing a Windows-first approach.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside or instead of PowerShell scripts for creating and managing private endpoints.
In the validation section, provide instructions for both Windows and Linux VMs, including how to run nslookup or dig on Linux.
When referencing VM creation, link to both Windows and Linux VM quickstart guides.
Ensure screenshots and UI instructions are platform-neutral or clarify when steps differ between OSes.
Consider including Bash script examples for automation, especially for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides detailed instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is prominent and uses Windows-centric tooling. PowerShell is a Windows-first tool, and its inclusion as a primary automation method can be seen as a Windows bias, especially since there are no equivalent Bash or Linux shell script examples. The CLI examples are cross-platform, but the ordering (CLI before PowerShell) is good; however, the presence of PowerShell without any Linux shell scripting alternatives (e.g., Bash) or explicit mention of cross-platform PowerShell Core may disadvantage Linux users. There are no explicit Linux-only tools or patterns, and the documentation does not mention or show Linux-specific considerations.

Recommendations:

Add Bash shell script examples alongside PowerShell, especially for automation scenarios.
Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
If including PowerShell, clarify whether the examples work with PowerShell Core on Linux/macOS or are Windows-only.
Consider providing parity in scripting examples: for every PowerShell example, provide a Bash or shell equivalent.
Highlight any OS-specific considerations (if any) for using these tools on Linux.
If possible, add a section or note for Linux users, e.g., how to install and use Azure CLI/PowerShell on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally provides both Windows and Linux examples for most applications, but there are several instances of Windows bias. In many cases, Windows file paths are listed before Linux equivalents ('windows_first'). Some applications (e.g., Apache Tomcat, NGINX, SecurityBridge) only provide Linux examples, omitting Windows instructions ('missing_linux_example'). There is a tendency to mention Windows tools and file paths, and the documentation refers to Windows-specific configuration files and patterns ('windows_tools'). While PowerShell commands are not explicitly shown, the overall structure and ordering favor Windows environments.

Recommendations:

For all application sections, ensure both Windows and Linux examples are provided, or explicitly state if a platform is not supported.
When listing file paths or configuration steps, alternate the order (sometimes Linux first), or present both together to avoid 'windows_first' bias.
Where only Linux examples are given (e.g., Apache Tomcat, NGINX, SecurityBridge), clarify if Windows is unsupported or provide equivalent Windows instructions if possible.
If referencing Windows tools or configuration files, provide Linux equivalents or note platform-specific differences.
Review general instructions and introductory sections to ensure parity in mentioning both platforms and avoid implicit prioritization of Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page provides only Azure PowerShell examples for deploying and managing a Service Bus namespace, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and code blocks are PowerShell-specific, and the workflow assumes familiarity with PowerShell and Windows-centric patterns (e.g., Write-Host, Read-Host). While there is a brief mention of Azure CLI as an alternative, no CLI or Linux-native examples are provided, and PowerShell is presented as the default and primary method.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell scripts, using Bash syntax where appropriate.
Present both PowerShell and CLI/Bash examples side-by-side, or allow users to toggle between them.
Avoid assuming the use of Windows tools or PowerShell-specific commands in instructions and explanations.
Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for both environments.
Ensure that Linux/macOS users can follow the quickstart without needing to adapt PowerShell scripts themselves.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias, especially in the 'Prepare on-premises to connect after failover' section, where Windows instructions are more detailed and appear before Linux instructions. Windows-specific tools and settings (e.g., Windows Firewall, WinHTTP proxy, SAN policy) are mentioned, while Linux guidance is minimal and lacks equivalent detail. There are also missing Linux examples for some troubleshooting and configuration steps.

Recommendations:

Provide Linux instructions with equal detail and prominence as Windows, including firewall configuration (e.g., iptables, firewalld, ufw), SSH service management, and handling of persistent routes or proxies.
List Linux and Windows procedures side-by-side or in parallel sections, rather than always listing Windows first.
Include Linux-specific troubleshooting resources and links, similar to the Windows RDP troubleshooting tips provided.
Mention Linux equivalents for Windows-specific settings (e.g., SAN policy, pending updates) or clarify if not applicable.
Ensure all automation and scripting examples (if any) are cross-platform or provide both PowerShell and Bash/Shell script samples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first and primary example for deploying the ARM template, with the Azure CLI example following. The 'Next steps' section prioritizes PowerShell-based management and does not mention Linux-specific tools or workflows. There is no explicit mention of Linux or cross-platform considerations in the deployment or management sections, and the use of PowerShell and Service Bus Explorer (a Windows desktop tool) further reinforces a Windows-centric approach.

Recommendations:

Present Azure CLI deployment commands before or alongside PowerShell, emphasizing its cross-platform compatibility.
Include explicit references to Linux and macOS compatibility, especially in deployment and management sections.
Add examples for deploying ARM templates using Bash scripts or from Linux/macOS terminals.
Highlight cross-platform tools for managing Service Bus resources, such as Azure CLI, REST API, or SDKs, rather than focusing on Windows-only tools like PowerShell and Service Bus Explorer.
In the 'Next steps' section, provide links to CLI-based management guides and mention Service Bus management via the Azure Portal, which is OS-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions and references for preparing Windows machines, including PowerShell usage and Windows Firewall configuration, while Linux preparation is covered only briefly. Windows tools and patterns (e.g., RDP, Windows Firewall, PowerShell) are mentioned exclusively or before their Linux equivalents, and there are no Linux-specific examples or command references.

Recommendations:

Provide equally detailed steps for preparing Linux machines, including example commands for configuring SSH, managing firewall rules (e.g., using ufw, firewalld, or iptables), and checking required services.
Include references or links to official Linux documentation for preparing VMs for Azure, similar to the Windows links provided.
Mention Linux tools and access patterns (e.g., SSH, Linux firewalls) alongside Windows tools, not just as a secondary note.
Add example scripts or automation runbooks for Linux environments, not just PowerShell/Windows.
Ensure that all sections referencing RDP or Windows Firewall also mention SSH and Linux firewall configuration where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear Windows bias: troubleshooting steps, examples, and tool references are predominantly Windows-centric, with detailed instructions and command-line examples for Windows, while Linux guidance is often less detailed, grouped at the end, or missing entirely for some scenarios. Windows tools and patterns (e.g., registry edits, net commands, Control Panel, Task Manager, Group Policy, WMI, VSS, DCOM) are described in depth, while Linux equivalents are either briefly mentioned or omitted. Linux troubleshooting is often summarized in a few steps, with less context and fewer examples.

Recommendations:

For every Windows-specific troubleshooting step, provide an equivalent Linux example or procedure, including command-line instructions and file locations.
Where Windows tools (e.g., registry editor, net, Control Panel, Task Manager, Group Policy, WMI, VSS) are referenced, include Linux tools and commands (e.g., systemctl, journalctl, SSH configuration, system logs, package management, systemd services).
Avoid presenting Windows steps or tools first by default; instead, structure sections to address both platforms equally, or clearly separate Windows and Linux subsections.
Add Linux-specific troubleshooting for agent installation failures, privilege issues, login failures, connectivity checks (e.g., using ssh, sftp, systemctl status), and disk/driver issues.
Include screenshots or terminal output examples for Linux where Windows screenshots are provided.
Reference Linux documentation or official resources for advanced troubleshooting (e.g., SSH hardening, system logs, SELinux/AppArmor, package installation).
Ensure parity in detail and clarity between Windows and Linux troubleshooting instructions throughout the document.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong bias toward Windows development environments. All instructions for creating and running the .NET applications are centered around Visual Studio, a Windows-centric IDE, with no mention of cross-platform alternatives like Visual Studio Code or JetBrains Rider. Package installation is shown exclusively using the NuGet Package Manager Console (PowerShell), with no examples for .NET CLI (dotnet) commands, which are platform-agnostic. There are no instructions or screenshots for Linux or macOS users, and the workflow assumes the user is operating within a Windows GUI environment.

Recommendations:

Add instructions for using Visual Studio Code and/or JetBrains Rider, including how to create and run .NET console applications on Linux and macOS.
Provide .NET CLI (dotnet add package ...) commands as an alternative to the NuGet Package Manager Console for installing packages.
Include notes or screenshots for Linux/macOS environments where relevant, especially for authentication (e.g., DefaultAzureCredential) and running the sample code.
Clarify that Visual Studio is not required, and that the sample can be built and run on any platform supported by .NET 6+.
Add troubleshooting notes for common Linux/macOS issues (e.g., port/firewall settings, credential management).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments. All examples, prerequisites, and operational steps assume the use of Windows Server (2012 R2/2016), PowerShell, and Windows-specific tools and frameworks (.NET Framework, Visual C++ Redistributable). There are no Linux equivalents or cross-platform instructions, and the tool appears to be designed exclusively for Windows, with no mention of Linux support or alternative workflows.

Recommendations:

Clearly state in the introduction that the Deployment Planner tool is Windows-only, if that is the case. If not, provide explicit instructions for Linux environments.
If possible, develop and document a cross-platform version of the Deployment Planner tool that can run on Linux or macOS, or provide a containerized version.
Provide equivalent command-line examples for Linux (e.g., using SSH, OpenSSL, or other cross-platform tools) where possible.
If PowerShell is required, mention PowerShell Core (pwsh) and its cross-platform capabilities, and provide instructions for installing and running the tool on Linux.
List any limitations or lack of support for non-Windows environments explicitly in the prerequisites section.
For report generation, suggest open-source alternatives to Microsoft Excel (such as LibreOffice Calc) or provide CSV/JSON output options.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists Azure PowerShell and Visual Studio (a Windows-centric IDE) as primary client tools for Service Connector, and mentions them before cross-platform or Linux-native alternatives. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), and the examples and tool recommendations lean toward Windows-first workflows.

Recommendations:

Include explicit mention and examples for Linux environments, such as Bash shell usage with Azure CLI.
Highlight cross-platform editors and tools (e.g., VS Code) alongside or before Windows-only tools like Visual Studio.
Provide parity in examples and instructions for both Windows and Linux users, ensuring that PowerShell is not the only shell referenced.
Clarify that Azure CLI and Terraform are fully cross-platform, and consider providing links or notes for Linux installation and usage.
If possible, add a section or callout for Linux/macOS users to ensure inclusivity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided, there are several areas where Windows-specific tools and patterns are prioritized or Linux alternatives are missing. For example, the section on checking the minimum TLS version uses ARMClient.exe (a Windows executable) and PowerShell commands, with no mention of Linux-compatible alternatives. PowerShell examples are given equal prominence to Azure CLI, and the documentation refers to tools and workflows (like ARMClient.exe) that are not natively available on Linux or macOS. There are no Bash/cURL or Linux-native instructions for querying the ARM API or obtaining tokens.

Recommendations:

Provide Linux/macOS-compatible alternatives for ARMClient.exe, such as using Azure CLI (az account get-access-token) and curl for querying the ARM API.
Include Bash/cURL examples alongside or before PowerShell examples when demonstrating API queries.
Clearly indicate which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows users.
Consider reordering examples to present cross-platform or Linux-native tools first, or at least in parallel with Windows tools.
Add explicit notes or links for Linux/macOS users where a tool or workflow is Windows-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas. Windows instructions and tools (such as registry edits and Windows Firewall) are described in greater detail and appear before Linux equivalents. The Windows RDP section is more comprehensive, mentioning specific firewall settings and SAN policy, while the Linux SSH section is brief and lacks comparable troubleshooting or configuration depth. There are also references to Windows-specific tools and patterns (e.g., registry, Windows Firewall) without Linux analogs or detailed Linux examples.

Recommendations:

Provide Linux instructions with equivalent detail to Windows, such as specifying how to configure SSH, firewall (e.g., iptables, firewalld, ufw), and SELinux/AppArmor settings.
Include troubleshooting steps for Linux VMs after failover, similar to the Windows RDP troubleshooting section.
When listing steps for both OS types, alternate the order or present them in parallel sections to avoid always listing Windows first.
Where Windows-specific tools (e.g., registry, Windows Firewall) are mentioned, provide Linux equivalents (e.g., editing /etc/ssh/sshd_config, using systemctl to enable SSH, configuring firewall rules).
Add links to Linux-specific documentation for further reading, as is done for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows and Visual Studio workflows. All instructions for creating projects, managing dependencies, and authenticating are based on Visual Studio UI and PowerShell commands. There are no instructions or examples for Linux or cross-platform .NET development (e.g., using VS Code, JetBrains Rider, or the .NET CLI). The NuGet installation steps use PowerShell exclusively, and there is no mention of how to perform equivalent steps on Linux or macOS. The use of Visual Studio sign-in for authentication assumes a Windows environment.

Recommendations:

Add parallel instructions for Linux/macOS users, including how to use the .NET CLI (e.g., 'dotnet new console', 'dotnet add package') for project creation and package management.
Include examples for installing NuGet packages via the CLI (e.g., 'dotnet add package Azure.Messaging.ServiceBus') instead of only PowerShell.
Describe authentication options that work cross-platform, such as using Azure CLI or environment variables for DefaultAzureCredential, not just Visual Studio sign-in.
Mention and provide examples for alternative editors like VS Code or JetBrains Rider, and clarify that the code samples work on any OS supported by .NET.
Where UI steps are described (e.g., creating projects), provide equivalent CLI commands for non-Windows users.
Explicitly state that the tutorial is cross-platform and highlight any OS-specific steps or requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows and PowerShell instructions before Linux/macOS equivalents, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and sometimes only mentioned in passing. Some file path examples and configuration notes are Windows-centric, and Linux-specific nuances (such as file permissions or shell differences) are not addressed.

Recommendations:

Present Linux/macOS instructions before or alongside Windows instructions to ensure parity.
Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands and navigation.
Avoid assuming use of PowerShell or WSL; provide native Linux/macOS shell commands and workflows.
Include Linux/macOS file path examples (using forward slashes) alongside Windows examples.
Explicitly mention any Linux/macOS prerequisites or dependencies (such as bash, chmod, or Docker Compose installation methods).
Ensure that all scripts and configuration steps are validated and described for Linux/macOS environments, not just Windows.
Add troubleshooting tips or notes specific to Linux/macOS where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by consistently presenting Windows instructions and tools before Linux equivalents. Windows-specific tools and folder paths (e.g., Control Panel, C:\WindowsAzure\Packages) are mentioned in detail, while Linux instructions are less detailed and sometimes less prominent. The validation steps for Windows are more GUI-oriented, while Linux steps are more generic. There is also a lack of parity in troubleshooting and validation detail between platforms.

Recommendations:

Alternate the order of Windows and Linux instructions, or present them in parallel sections to avoid always listing Windows first.
Provide equivalent detail and validation steps for Linux as for Windows, including specific file paths, log locations, and version checks.
Include Linux-specific troubleshooting links and resources, similar to those provided for Windows.
Where possible, use cross-platform language and avoid assuming a Windows-centric workflow (e.g., mention both Control Panel and Linux package managers in the same prominence).
Ensure that command-line examples are provided for both platforms, and avoid GUI-only instructions for Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on Windows environments, specifically Hyper-V, and provides only Windows-based instructions and tooling (e.g., .exe installers, CMD commands, Windows file paths). There are no examples or references for Linux environments, tools, or equivalent processes, and all command-line instructions are Windows-centric. The documentation assumes the user is operating in a Windows ecosystem, with no mention of Linux-based Hypervisors or cross-platform considerations.

Recommendations:

Explicitly state that the tutorial is only applicable to Windows/Hyper-V environments, and provide links to equivalent Linux/KVM/VMware documentation if available.
Where possible, mention whether Azure Site Recovery supports Linux-based hypervisors, and if so, provide parallel instructions or links.
If cross-platform support is not available, clarify this early in the prerequisites or introduction to set user expectations.
If any steps can be performed from a Linux environment (e.g., using Azure CLI or REST APIs), provide Linux shell examples alongside Windows examples.
Consider adding a comparison table or section outlining support and steps for different hypervisor platforms (Windows/Hyper-V, Linux/KVM, VMware, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed registry and CLI instructions specifically for Windows (including registry key changes and REG ADD command), referencing Windows-specific tools and patterns (such as the Windows registry and Local Administrator), and linking to Windows Time Server documentation. Linux is only briefly mentioned (e.g., 'the account should be root'), with no equivalent step-by-step instructions or CLI examples for Linux systems. No Linux-specific troubleshooting, commands, or configuration guidance is provided, and Windows procedures are presented first and in more detail.

Recommendations:

Provide equivalent step-by-step instructions and CLI commands for Linux systems, such as how to prepare the Linux environment for Mobility service installation (e.g., required packages, firewall configuration, SELinux/AppArmor considerations).
Include Linux-specific troubleshooting steps, such as checking system time synchronization (e.g., using timedatectl or ntpd/chrony), and reference relevant Linux documentation instead of only Windows Time Server.
When describing account preparation, give explicit Linux commands or configuration file changes (e.g., ensuring root SSH access, sudoers configuration) alongside the Windows registry steps.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or clearly separate them into distinct subsections.
Reference Linux tools and patterns (e.g., systemd, journalctl, SSH configuration) where appropriate, not just Windows tools and registry.
Add examples of common issues and solutions for Linux VMs during the migration process, similar to the detail given for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All detailed examples focus exclusively on Windows VMs, with disk layouts, drive letters (C:, D:, etc.), and screenshots from Windows interfaces. Instructions reference Windows-specific tools (diskmgmt.msc, service console, command prompt, Net start/stop). SQL Server examples assume Windows as the guest OS. There are no Linux VM examples, nor are Linux-specific tools, filesystems, or commands mentioned. Even when Linux is referenced (e.g., in failback behavior), it is only in passing, not as a worked example.

Recommendations:

Add parallel Linux VM examples for disk exclusion, failover, and failback, including typical Linux disk layouts (e.g., /, /var, /tmp, /mnt/data) and relevant files (e.g., swap, tempdb for SQL Server on Linux, etc.).
Include Linux-specific instructions for adding and formatting disks (e.g., using fdisk, mkfs, mount, and updating /etc/fstab).
Show how to manage SQL Server tempdb on Linux (e.g., using systemctl for service management, Linux file paths, and sqlcmd usage on Linux).
Reference Linux tools and commands (e.g., lsblk, parted, systemctl) alongside Windows tools.
Provide screenshots or terminal output from Linux environments where appropriate.
Clarify any differences in behavior or limitations for Linux VMs, not just Windows.
Ensure that all tables and scenarios include both Windows and Linux perspectives where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits several forms of Windows bias. Windows-specific features, tools, and examples (such as PowerShell and Volume Shadow Copy Service) are mentioned prominently, often without equivalent Linux guidance or examples. In some sections, Linux support is only briefly referenced or explicitly excluded (e.g., shared disks), and Windows terminology or tools are used as the default or only example. PowerShell is frequently suggested for advanced tasks, with no mention of Bash, CLI, or Linux-native alternatives.

Recommendations:

Provide Linux-specific examples and guidance alongside Windows examples, especially for scripting and automation (e.g., show Azure CLI or Bash scripts in addition to PowerShell).
When referencing Windows tools or features (such as VSS), include Linux equivalents or explain how similar functionality can be achieved on Linux (e.g., using pre/post scripts for app-consistency).
Avoid presenting Windows options or tools first by default; instead, present both Windows and Linux options in parallel or clarify applicability.
Where features are unsupported for Linux (e.g., shared disks), clearly state this early and provide links to feature requests or workarounds if available.
Expand documentation for Linux-specific scenarios, such as encrypted disk replication, app-consistent snapshots, and automation using non-Windows tools.
Include troubleshooting and best practices sections for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All command-line examples, administrative tasks, and tool references are Windows-centric, relying heavily on PowerShell, Windows paths, and Windows-specific executables. There are no Linux-specific instructions, examples, or tool alternatives provided, despite mentioning support for Linux physical servers. The use of Windows tools and patterns is pervasive, and Linux parity is not addressed.

Recommendations:

Provide equivalent Linux command-line instructions for tasks such as certificate renewal, passphrase generation, and server registration/unregistration.
Include examples using Bash or shell commands where appropriate, especially for Linux-based configuration servers or physical servers.
Document the location of relevant files and executables for Linux systems (e.g., paths, required permissions, dependencies).
Clarify whether tools like cspsconfigtool.exe or genpassphrase.exe are available or have alternatives on Linux, and provide installation or usage guidance.
When referencing PowerShell or Windows tools, always follow with Linux alternatives or note if a feature is Windows-only.
Explicitly state any limitations or differences in managing configuration servers on Linux versus Windows.
Add screenshots or walkthroughs for Linux environments where GUI or CLI actions are described.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows-specific tools and instructions (such as Internet Explorer settings and psexec usage) before Linux equivalents. It provides detailed steps for Windows (including tool usage) but omits comparable Linux command-line examples or tools. The Linux section is less detailed and lacks parity in guidance, particularly for configuring environment variables or editing the ProxyInfo.conf file.

Recommendations:

Provide Linux configuration steps with the same level of detail as Windows, including example commands for editing /etc/profile or /etc/environment (e.g., using nano or vi).
Include Linux-specific tools or methods for setting environment variables for system services, such as using 'export' or editing systemd service files.
Present Windows and Linux instructions in parallel, rather than listing Windows first, to avoid the perception of prioritizing one platform.
Offer example commands for creating and editing ProxyInfo.conf on Linux, similar to the Windows file path instructions.
Avoid referencing Windows-only tools (like psexec and Internet Explorer) without Linux equivalents or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: it provides registry key and PowerShell cmdlet instructions specific to Windows, references Windows-specific tools (MMC snap-in, registry, Windows Azure Backup), and gives detailed step-by-step instructions for Windows-based master target server installation, while Linux instructions are limited to a single link. There are no Linux command-line examples or parity in configuration guidance, and Windows tools and patterns are mentioned first and in greater detail.

Recommendations:

Provide equivalent Linux command-line examples for bandwidth throttling and process server configuration (e.g., using sysctl, tc, or other Linux-native tools).
Include Linux-specific instructions for altering replication settings, not just a link to a separate article.
Mention Linux tools and configuration patterns alongside Windows ones, not only as an afterthought or in a separate section.
Ensure that all registry or PowerShell-based instructions have clear Linux alternatives (such as configuration files or commands).
Balance the depth of guidance for Linux and Windows, including screenshots and step-by-step instructions for both platforms.
Where Windows tools (MMC, registry, PowerShell) are referenced, clarify their Linux equivalents or state if a feature is not available on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows environments, specifically referencing Windows Failover Clustering and Storage Spaces Direct (S2D), which are Windows-only technologies. All examples, terminology, and linked resources are Windows-centric, with no mention of Linux-based clustering, storage, or disaster recovery solutions. There are no Linux equivalents or guidance for users running Linux VMs or open-source clustering/storage stacks.

Recommendations:

Explicitly state that the guide is only applicable to Windows-based clusters and provide a reference or link to equivalent guidance for Linux-based clusters if available.
Add a section or note addressing disaster recovery for Linux VMs, including supported clustering and storage technologies (e.g., Pacemaker, DRBD, LVM, etc.), or clarify current limitations if Linux clustering is not supported.
Where possible, provide parallel examples or documentation links for Linux environments to ensure parity and inclusivity.
Avoid assuming the use of Windows-specific tools and patterns (e.g., Failover Cluster, Storage Spaces Direct) without mentioning alternatives or the scope of applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. It exclusively provides instructions and screenshots for installing and configuring the Windows agent, with no mention of Linux agents or instructions for Linux-based Process Servers. The 'Connected Sources' setup, agent download, and performance counter configuration are all Windows-specific, and there are no Linux equivalents or guidance for Linux-based environments.

Recommendations:

Add equivalent instructions for installing and configuring the Microsoft monitoring agent on Linux-based Process Servers, including download links, configuration steps, and screenshots.
Include guidance on setting up Linux performance counters or their equivalents, and how to collect churn/upload rate metrics from Linux Process Servers.
Wherever agent installation is discussed, mention both Windows and Linux options, or clarify if Linux is not supported.
Ensure that all steps and screenshots are provided for both platforms, or explicitly state platform limitations.
Review all examples and instructions to ensure Linux parity, and add Linux-specific troubleshooting or notes where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing PowerShell-based setup instructions as the only command-line/manual alternative to the OVF template, referencing Windows registry and group policy settings, and omitting Linux-based setup or troubleshooting examples. Windows-specific tools and configuration patterns are mentioned exclusively, and Linux is only referenced in the context of VM credentials, not as a platform for the appliance or for management tasks.

Recommendations:

Provide equivalent Linux-based setup instructions for deploying and configuring the replication appliance, including command-line examples using Bash or shell scripts.
Include Linux-specific troubleshooting steps and configuration checks (e.g., for connectivity, permissions, or required packages) alongside Windows registry and group policy checks.
Clarify whether the replication appliance can be deployed on Linux-based VMs, and if so, provide guidance for those scenarios.
When referencing PowerShell, also mention or link to Linux-compatible alternatives (such as Azure CLI or shell scripts) where possible.
Ensure that examples and screenshots are balanced between Windows and Linux environments, or explicitly state platform limitations if Windows is the only supported OS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on Windows environments, specifically Hyper-V and related Microsoft tools (e.g., System Center VMM, Recovery Services agent, Hyper-V Replica). There are no examples, references, or guidance for Linux-based hypervisors or management tools. All technical details, commands, and processes are described in terms of Windows technologies, with no mention of Linux equivalents or cross-platform considerations.

Recommendations:

Clearly state at the beginning that the guide is specific to Hyper-V (a Windows-only hypervisor) and does not apply to Linux-based virtualization platforms.
Provide links or references to equivalent Azure Site Recovery documentation for Linux-based environments (e.g., VMware, physical Linux servers, or Linux KVM).
If possible, add a comparison table or section outlining how disaster recovery architecture and processes differ for Linux-based hypervisors or workloads.
Ensure that related documentation for Azure Site Recovery covers Linux scenarios with equal depth and visibility, and cross-link these resources.
If any Linux guest VM considerations exist (e.g., agent installation, supported distributions), mention them explicitly.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-specific tools, paths, and troubleshooting steps. PowerShell and Windows file paths are provided explicitly, while Linux equivalents are either missing or only briefly mentioned. Troubleshooting steps and error log locations are described in detail for Windows, with Linux guidance often relegated to a single line or omitted. Windows services and commands are listed first and in greater detail, and Windows tools (like VSS) are discussed extensively without Linux alternatives.

Recommendations:

Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, including equivalent commands and log file locations.
Include Linux command-line examples (e.g., bash, systemctl) where PowerShell or Windows CMD commands are given.
When referencing file paths or configuration files, always provide both Windows and Linux locations and formats.
Discuss Linux-specific tools or mechanisms (e.g., LVM snapshots, systemd services) where Windows tools like VSS are mentioned.
Ensure that Linux error messages, service names, and restart procedures are as detailed as their Windows counterparts.
Avoid listing Windows steps or tools first by default; present both platforms with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows environments, specifically focusing on Hyper-V and System Center VMM, both of which are Windows-only technologies. All setup and installation instructions, including command-line examples, use Windows tools and PowerShell commands. There are no Linux equivalents or alternative instructions for non-Windows environments, and the documentation assumes the use of Windows throughout.

Recommendations:

Clearly state early in the documentation that this guide is specific to Windows/Hyper-V environments, and provide links to equivalent guides for Linux/KVM or VMware environments if available.
Where possible, mention if similar disaster recovery workflows exist for Linux-based hypervisors (e.g., KVM, Xen) and link to relevant documentation.
If Azure Site Recovery supports Linux-based hosts or VMs, include parallel instructions or at least reference documentation for those scenarios.
Avoid using only PowerShell or Windows command-line examples; if cross-platform tools or REST APIs are available, provide examples for Linux/bash as well.
Add a comparison table or section outlining supported platforms and any differences in setup between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows and PowerShell environments. All code examples are in PowerShell, with no mention or examples for Linux, Bash, or Python. The required modules and scripting patterns are specific to PowerShell and the AzureRM/Az modules, which are primarily used in Windows-centric automation. There is no guidance for users managing Linux VMs or those who prefer cross-platform scripting languages. The documentation assumes a Windows-first approach, both in tooling and in the order of presentation.

Recommendations:

Add equivalent examples using Azure CLI (bash) and/or Python SDK for runbook automation, especially for Linux-based recovery scenarios.
Explicitly mention support for Linux VMs and provide guidance or links for automating recovery steps on Linux workloads.
Include sample runbooks written in Python or Bash, and show how to use them in Azure Automation.
Clarify which features or modules are cross-platform and which are Windows/PowerShell-specific.
Provide a comparison table or section outlining scripting options for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Hyper-V, a Windows-centric virtualization technology, and exclusively discusses concepts, tools, and workflows relevant to Windows environments. There are no references to Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples, commands, or considerations for Linux users. All terminology, examples, and requirements are tailored to Windows/Hyper-V administrators, with no Linux parity.

Recommendations:

Add a section clarifying the scope of the tool and documentation, explicitly stating if it is only for Hyper-V (Windows) environments, and provide links to equivalent tools or documentation for Linux/KVM/VMware environments if available.
If Azure Site Recovery supports Linux-based hypervisors or Linux VMs, include examples, requirements, and report analysis guidance for those scenarios.
Where possible, generalize terminology (e.g., 'on-premises hypervisor' instead of 'Hyper-V server') and provide parallel Linux/KVM/VMware instructions or notes.
Include a comparison table or FAQ addressing differences in deployment planner usage and report analysis between Windows/Hyper-V and Linux-based environments.
If the tool is Windows-only, suggest alternative planning/reporting tools for Linux users, or provide guidance on how Linux VMs can be assessed for Azure Site Recovery readiness.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is focused exclusively on Hyper-V, a Windows-based virtualization platform, and does not mention or provide examples for Linux-based hypervisors (such as KVM or VMware on Linux). All instructions, terminology, and scenarios are tailored to Windows environments, with no Linux equivalents or cross-platform considerations discussed.

Recommendations:

Include guidance or references for excluding disks from replication for Linux-based hypervisors (e.g., KVM, VMware on Linux) if supported by Azure Site Recovery.
Add examples or notes for administrators managing non-Windows environments, clarifying whether similar functionality is available and how to achieve it.
Explicitly state if the feature is only available for Hyper-V (Windows) and provide links to equivalent documentation for Linux platforms if applicable.
Consider a section comparing the process for Windows (Hyper-V) and Linux-based virtualization platforms to improve cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows-specific tools (Resource Monitor, Performance Monitor) in greater detail and before Linux equivalents. The Windows section includes step-by-step instructions and screenshots, while the Linux section only briefly mentions iotop and iostat without detailed usage, examples, or visuals. No Linux-native graphical tools or monitoring workflows are described, and the Linux section lacks parity in depth and guidance.

Recommendations:

Provide step-by-step instructions for using iotop and iostat, including example command outputs and explanations.
Include screenshots or sample outputs for Linux tools, similar to the Windows section.
Mention additional Linux monitoring tools (e.g., dstat, atop, glances, GNOME System Monitor) to match the breadth of Windows tool coverage.
Present Windows and Linux sections in parallel structure, ensuring equal depth and clarity for both.
Consider introducing the Linux section before or alongside the Windows section to avoid a Windows-first impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exclusively provides troubleshooting steps and examples for Windows environments, referencing Windows-specific tools (Command Prompt, Registry Editor, Task Manager), file paths (C:\), and executable formats (.exe). There are no Linux equivalents, commands, or guidance, indicating a strong Windows bias.

Recommendations:

Add parallel troubleshooting steps for Linux environments, if supported by the product.
Include Linux shell command examples (e.g., using bash, tar, or unzip for extraction).
Reference Linux file paths and conventions alongside Windows examples.
Mention Linux equivalents for tools like Registry Editor (e.g., editing configuration files), and Task Manager (e.g., using top, htop, or ps).
Clarify in the introduction if the product or troubleshooting steps are only applicable to Windows, or explicitly state Linux is not supported if that is the case.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. Troubleshooting steps, log locations, and example commands are almost exclusively Windows-centric, with PowerShell and Windows GUI tools (Event Viewer, Task Manager, Resource Monitor, Disk Management) being referenced throughout. Linux is only briefly mentioned in a single bullet point, with no concrete troubleshooting steps or examples provided for Linux-based VMs or environments.

Recommendations:

Provide parallel troubleshooting steps and log locations for Linux-based guest VMs, especially for scenarios where Linux VMs are protected or replicated via Hyper-V.
Include Linux command-line equivalents for checking service status, disk configuration, and VSS/app-consistent snapshot status (e.g., systemctl, journalctl, lsblk, etc.).
When referencing PowerShell or Windows GUI tools, also mention or link to Linux tools and commands where applicable.
Add explicit Linux examples for common troubleshooting tasks, such as checking integration services, verifying app-consistency, and collecting logs.
Clarify which steps are Windows-only and which apply to Linux guests, and ensure Linux parity in troubleshooting guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and consistently references Windows-centric tools and workflows (e.g., VMM, PowerShell) without providing Linux equivalents or examples. There are no Linux-specific instructions, examples, or considerations, and all automation and scripting references are to PowerShell. The documentation assumes the reader is operating in a Windows ecosystem, with no mention of Linux-based Hypervisors or management tools.

Recommendations:

Add explicit statements clarifying that Azure Site Recovery for Hyper-V is only supported on Windows, and provide links to equivalent documentation for Linux-based disaster recovery scenarios (e.g., for KVM, VMware on Linux, or physical Linux servers).
Where PowerShell is referenced for automation, provide equivalent Azure CLI or REST API examples that are cross-platform and can be run from Linux or macOS.
If possible, mention or link to tools and workflows for managing disaster recovery for Linux VMs or workloads, including how to replicate and failover Linux VMs to Azure.
Include a section addressing common questions or considerations for Linux administrators, such as supported guest OSes, agent installation on Linux VMs, and any differences in failover/failback processes.
Ensure that any references to management tools (e.g., VMM, Hyper-V Manager) are accompanied by notes on their platform specificity and alternatives for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically IIS on Windows Server. All examples, scripts, and recovery scenarios are centered around Windows tools and patterns (e.g., IIS, PowerShell scripts, web.config, ARR, SQL Server). There are no Linux equivalents or mentions of cross-platform scenarios, and Linux-based web servers (such as Apache or Nginx) are not addressed at all.

Recommendations:

Include parallel guidance for Linux-based web applications (e.g., Apache, Nginx) and their disaster recovery using Azure Site Recovery.
Provide Linux-specific examples for updating DNS, connection strings, site bindings, and certificate management (e.g., using Bash scripts, systemd, or relevant Linux tools).
Reference Linux-based scripting (Bash, Python) alongside PowerShell for automation steps.
Mention and link to Azure Site Recovery support for Linux VMs, including any prerequisites or limitations.
Clarify in the introduction that the article is specific to Windows/IIS, and provide links or references to Linux documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation predominantly provides Windows-centric instructions and examples, especially in the antivirus exclusions section, where Windows paths and registry keys are listed extensively before Linux equivalents. Linux-specific guidance is minimal and appears only after several Windows-focused sections. There are also references to Windows licensing and tools without mentioning Linux alternatives or parity.

Recommendations:

Present Linux and Windows instructions in parallel sections or tables, ensuring equal prominence.
Include Linux-specific examples and paths wherever Windows examples are provided, not just as an afterthought.
If registry exclusions are mentioned for Windows, clarify whether similar steps are needed or possible on Linux, or explicitly state if not applicable.
When discussing licensing or activation (e.g., Windows evaluation license), mention any Linux-specific considerations or clarify if not relevant.
Review all steps to ensure that Linux administrators have clear, actionable instructions, not just Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically Active Directory and DNS as implemented on Windows Server. All examples, tools, and troubleshooting steps reference Windows-specific utilities (e.g., dcdiag, nltest, dnscmd, registry edits), and there is no mention of Linux-based domain controllers (such as Samba AD DC) or DNS servers. The guidance assumes the use of Windows Server roles and tools, with no Linux equivalents or cross-platform considerations provided.

Recommendations:

Add explicit notes about support (or lack thereof) for Linux-based Active Directory alternatives (e.g., Samba AD DC) and DNS servers.
Provide parallel instructions and examples for Linux-based domain controllers and DNS servers, if supported by Azure Site Recovery.
Include Linux command-line equivalents for diagnostic and recovery steps (e.g., using samba-tool, systemctl, or BIND utilities).
Clarify early in the documentation that the instructions are specific to Windows Server environments if Linux is not supported, or provide a section on cross-platform considerations.
Mention Linux tools and patterns (e.g., systemd, /etc/krb5.conf, /etc/bind) where relevant, and provide links to Linux documentation for AD/DNS disaster recovery.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation and provided script are entirely focused on Windows environments, specifically using PowerShell, Windows registry paths, Windows services, and Windows clustering tools. There are no examples, instructions, or references for performing similar tasks on Linux-based systems or with cross-platform tools. The documentation assumes the user is operating in a Windows environment from the outset.

Recommendations:

Provide equivalent instructions or scripts for Linux environments, if VMM or similar functionality is supported on Linux.
If the operation is inherently Windows-only (e.g., due to VMM being a Windows-only product), clearly state this limitation at the beginning of the documentation.
Where possible, mention cross-platform alternatives or tools, or provide guidance for users managing hybrid environments.
Include a section that addresses Linux administrators, even if only to clarify that the script and procedure are not applicable to Linux.
If any cleanup or unregister operations are possible via REST APIs or other cross-platform interfaces, provide examples for those as well.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by frequently mentioning Windows technologies (such as Windows Server Failover Clusters, SQL Server Always On, and Windows physical servers) before or more prominently than Linux equivalents. There are no Linux-specific examples, tools, or scenarios described, and the only explicit mention of Linux is in a parenthetical note. Windows tools and patterns (e.g., shared disk for WSFC, SQL FCI) are discussed in detail, while Linux disaster recovery scenarios are not addressed.

Recommendations:

Include explicit Linux-based disaster recovery scenarios and examples, such as replicating Linux VMs or physical servers, and protecting Linux-based clustered applications (e.g., Pacemaker, Corosync).
Provide parity in workload examples by mentioning common Linux workloads (e.g., MySQL, PostgreSQL, Apache, NGINX) alongside Windows workloads like SQL Server.
Add Linux-specific guidance or links for scripting, automation, and failover testing (e.g., using Bash scripts, Ansible, or Linux-native tools) in recovery plans.
Balance the discussion of Windows and Linux tools and patterns, ensuring that Linux equivalents are introduced wherever Windows-specific technologies are described.
Where shared disk or clustering is discussed, mention Linux clustering solutions and how Site Recovery supports them, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Windows-based Dynamics AX components. There are no Linux examples or mentions of Linux-based equivalents for any of the steps, tools, or patterns. All technical guidance, screenshots, and recommendations assume a Windows-centric deployment.

Recommendations:

Include explicit statements about Linux support or lack thereof for Dynamics AX and Azure Site Recovery in this context.
If Linux-based deployments are possible (e.g., for SQL Server or other components), provide parallel instructions and examples for Linux environments.
Mention Linux-compatible tools or approaches for disaster recovery, such as using Linux-based domain controllers (e.g., Samba) if supported, or alternative database engines.
Clarify in prerequisites and throughout the document whether the guidance is Windows-only or if there are cross-platform considerations.
Provide at least one end-to-end example or scenario for a mixed or Linux-based environment, if supported by the product.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on SAP NetWeaver deployments on Windows, referencing Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper, and omitting Linux-based deployment guidance or examples. No Linux clustering or high availability solutions (such as Pacemaker or NFS) are mentioned, and all technical recommendations and examples assume a Windows environment.

Recommendations:

Add explicit guidance and examples for SAP NetWeaver deployments on Linux, including supported Linux distributions on Azure.
Include Linux-based high availability and clustering solutions (e.g., Pacemaker, Corosync, NFS, GlusterFS) as alternatives to Windows Server Failover Cluster and Storage Spaces Direct.
Provide parity in disaster recovery steps, scripts, and automation for Linux-based SAP environments, including references to relevant Azure Automation scripts or runbooks.
Mention and link to SAP and Azure documentation for Linux-based SAP deployments and disaster recovery best practices.
Ensure diagrams and architectural references include both Windows and Linux deployment patterns where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas. Troubleshooting steps for hydration failures provide detailed, step-by-step PowerShell scripts and registry instructions for Windows Guest OS, but do not offer equivalent Linux guidance. Windows tools like PsExec and Internet Explorer are referenced for proxy troubleshooting, with no Linux alternatives. In some sections, Windows-specific errors and solutions are described in detail before Linux is mentioned, and Linux troubleshooting is often limited or absent. Only one Linux-specific command is provided (for serial console issues), and even there, the context is minimal compared to the Windows sections.

Recommendations:

For every Windows-specific troubleshooting script or step (e.g., hydration, registry changes), provide equivalent Linux commands or scripts (e.g., systemd service checks, driver/module configuration).
When referencing Windows tools like PsExec and Internet Explorer, also describe how to achieve the same outcome on Linux (e.g., using curl, wget, or editing environment variables directly).
Ensure Linux troubleshooting examples are as detailed as Windows ones, including command-line steps, expected outputs, and error interpretation.
When listing troubleshooting steps, avoid always presenting Windows first; alternate or group by OS, or clearly label sections for each OS.
Expand Linux coverage in sections where only Windows is discussed (e.g., hydration, proxy settings, unexpected shutdowns), or explicitly state if an issue is Windows-only.
Provide links to relevant Linux documentation and tools alongside Windows references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. All examples, references, and linked resources are focused on Windows-based SQL Server deployments. There are no instructions, examples, or considerations for Linux-based SQL Server, despite its support. Windows-specific tools (e.g., Task Manager, PowerShell scripts) are referenced exclusively, and all high availability/disaster recovery patterns are described in the context of Windows. Linux equivalents are not mentioned or provided.

Recommendations:

Include explicit guidance and examples for SQL Server running on Linux, including supported BCDR technologies and any Azure Site Recovery considerations.
Provide Linux-specific instructions for monitoring (e.g., using iostat, vmstat, or other Linux tools instead of Task Manager).
Offer PowerShell alternatives or equivalent Bash/shell scripts for automation steps, or clarify if only Windows is supported.
Reference and link to documentation for SQL Server on Linux high availability and disaster recovery options.
Clearly state any limitations or lack of support for Linux scenarios, if applicable, to avoid confusion.
Balance the order of presentation so that Linux and Windows are treated equally where both are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows workloads (Active Directory, SQL Server, SharePoint, Exchange, IIS, Dynamics AX, RDS) in both structure and detail. Windows tools and technologies are mentioned exclusively or in greater depth, while Linux and open-source equivalents are only briefly referenced or grouped generically. There are no Linux-specific examples, tools, or application scenarios, and the documentation lacks parity in describing Linux disaster recovery workflows.

Recommendations:

Add Linux-first sections or examples, such as protecting common Linux workloads (e.g., Apache, NGINX, MySQL/PostgreSQL, Samba, LDAP).
Include Linux-specific disaster recovery workflows, tools, and best practices, such as integration with systemd, cron, rsync, or native Linux clustering solutions.
Provide example scripts or automation for Linux environments (e.g., bash scripts) alongside or before Windows/PowerShell examples.
Highlight open-source and cross-platform applications (e.g., PostgreSQL, MariaDB, Tomcat) with the same level of detail as Windows workloads.
Ensure parity in technical depth and guidance for both Windows and Linux scenarios, including references to relevant Linux documentation and community best practices.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows tools, paths, and PowerShell are mentioned more frequently and often before Linux equivalents. Some instructions and examples (e.g., installation paths, manual installation, MySQL placement) are Windows-centric or only mention Windows locations. PowerShell is highlighted as a primary automation method, with less emphasis on Linux scripting or CLI alternatives. In a few cases, Linux equivalents are provided, but often as a secondary note or with less detail.

Recommendations:

Provide Linux examples and paths alongside Windows ones in all relevant sections (e.g., installer locations, MySQL placement).
When mentioning PowerShell, also reference Bash/CLI or scripting options for Linux users.
Ensure that automation and scripting guidance includes examples for Linux environments (e.g., Azure CLI, shell scripts).
List Linux instructions before or alongside Windows instructions to avoid 'Windows-first' ordering.
Where Windows tools or patterns are referenced (e.g., Configuration Manager), mention Linux alternatives (e.g., Ansible, shell scripts) if applicable.
Review all sections for implicit Windows assumptions and clarify cross-platform applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas: Windows paths, tools, and examples are consistently presented before their Linux equivalents, and some sections (such as UI-based installation) focus almost exclusively on Windows. Windows-specific tools, directories, and patterns (e.g., C:\Program Files, command prompt, .exe installers) are referenced throughout, sometimes with Linux instructions only appended or less detailed. In some cases, Linux instructions are present but less prominent, and the overall structure and examples assume a Windows-centric environment.

Recommendations:

Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
Include Linux-specific screenshots and UI walkthroughs where applicable, not just Windows UI images.
Use neutral language and file paths in general guidance (e.g., 'installation directory' instead of 'C:\Program Files...').
Where Windows-specific tools or services (e.g., VSS) are mentioned, provide equivalent Linux information or clarify if not applicable.
Ensure Linux command examples are as detailed and prominent as Windows examples, including troubleshooting and advanced options.
Highlight any differences in agent behavior or requirements between Windows and Linux explicitly, rather than assuming Windows as the default.
Where possible, provide a summary table or matrix showing parity and differences between Windows and Linux installation and configuration steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the primary automation tool, mentioning Windows-specific features (such as Azure Hybrid Benefit for Windows Server), and omitting Linux-specific instructions or examples. Windows terminology and tools are introduced before or instead of Linux equivalents, and there are no explicit Linux automation or troubleshooting examples.

Recommendations:

Provide equivalent CLI (az CLI) and/or Bash scripting examples alongside PowerShell for automation and management tasks.
Include Linux-specific considerations, such as supported Linux distributions, requirements for Linux VMs, and troubleshooting steps for common Linux issues.
Mention Linux licensing and cost-saving options (if any) in parity with the Azure Hybrid Benefit section for Windows.
Ensure that all references to tools (e.g., PowerShell, Windows Server) are balanced with Linux alternatives or clarifications where applicable.
Add explicit examples or links for automating replication and failover for Linux VMs, not just Windows.
Clarify any steps or requirements that differ for Linux VMs, especially regarding agent installation, disk requirements, and failover behavior.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments, specifically focusing on Hyper-V, System Center VMM, and PowerShell scripts. All command-line and scripting examples are provided exclusively in PowerShell, with no mention of Linux-based tools, shell commands, or procedures for unregistering or disabling protection on Linux servers. Windows tools and patterns (e.g., registry edits, Windows services, VMM/Hyper-V management) are referenced throughout, and there is no guidance for Linux-based disaster recovery scenarios.

Recommendations:

Add parallel instructions and examples for unregistering and disabling protection on Linux-based servers, including shell (bash) commands where applicable.
Include guidance for managing replication and cleanup on Linux VMs, such as how to uninstall the Mobility Service on Linux, or how to clean up configuration files and services.
Where PowerShell scripts are provided, offer equivalent bash or Python scripts for Linux environments, or explicitly state if certain actions are not required/applicable for Linux.
Clarify in each section whether the steps are Windows-specific, and provide links or references to Linux-specific documentation if available.
Ensure that Linux tools and procedures are mentioned alongside Windows tools, not only in separate sections but also in summary tables or comparison charts for parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, Windows command prompt, Windows service names), providing only Windows-based procedures and command examples, and omitting any Linux equivalents or guidance for non-Windows environments. There is no mention of how to perform these troubleshooting steps on Linux-based configuration servers, nor are cross-platform alternatives suggested.

Recommendations:

Provide equivalent troubleshooting steps for Linux-based configuration servers, including relevant commands and tools (e.g., using sudo, systemctl, Linux browsers, or CLI-based proxy configuration).
Mention and document how to configure proxy settings and service restarts on Linux systems.
Avoid referencing Windows-only tools (such as PsExec and Internet Explorer) without offering alternatives for other platforms.
Structure the documentation to address both Windows and Linux environments, or clearly state if only Windows is supported and why.
Include examples and screenshots for both Windows and Linux where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/Azure-centric bias by exclusively referencing Azure portal UI workflows, Azure CLI commands, and Azure Fileshare for storage operations, all of which are primarily oriented toward Windows or Azure environments. There are no examples or guidance for Linux-native workflows (e.g., using SCP, rsync, or Linux shell commands for uploading files), nor are there any mentions of Linux-specific tools or patterns for deploying or managing the agent. The documentation assumes the user is operating within the Azure ecosystem, which is more closely aligned with Windows environments.

Recommendations:

Provide Linux-native command-line examples for uploading the Elastic APM Java Agent to persistent storage (e.g., using azcopy, scp, or rsync from a Linux shell).
Include alternative instructions for users managing deployments from Linux or macOS environments, such as using Bash scripts or Linux CLI tools.
Mention cross-platform considerations explicitly, clarifying that the Azure CLI and related commands work on Linux, macOS, and Windows, and provide any OS-specific caveats.
Add screenshots or text-based examples that show how to perform key steps (such as uploading files) using Linux command-line tools, not just the Azure portal UI.
Where possible, provide parity in automation examples (e.g., show how to automate with shell scripts or Linux-native CI/CD tools in addition to Azure-native templates).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by presenting PowerShell instructions alongside Azure CLI, but omits explicit Linux shell (bash) examples. The PowerShell example is given equal prominence to Azure CLI, and there is no mention of Linux-specific considerations or tools. The instructions for deleting resources use PowerShell and Azure CLI, but the CLI example is written generically and does not clarify that it is intended for bash or Linux users. No Linux-specific screenshots, commands, or troubleshooting notes are provided.

Recommendations:

Explicitly label the Azure CLI example as 'Bash/Linux/macOS' to clarify its cross-platform applicability.
Add a note that Azure CLI commands can be run on Windows, Linux, or macOS, and provide links to installation instructions for each OS.
If possible, provide bash-specific examples or troubleshooting notes for common Linux environments.
Ensure that any references to PowerShell are balanced with bash shell equivalents, especially for scripting or automation tasks.
Consider including a table or section that summarizes command-line options for Windows (PowerShell), Linux (bash), and macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation examples for interacting with Palo Alto REST APIs and for Azure CLI usage. There are no equivalent Bash/shell or Linux-native scripting examples. The instructions assume the user is running commands in a PowerShell environment, which is native to Windows and only optionally available on Linux/macOS. This may create barriers for Linux users and does not reflect cross-platform parity.

Recommendations:

Provide equivalent Bash/shell script examples for all PowerShell automation steps, especially for interacting with Palo Alto REST APIs and processing CSV files.
Explicitly mention that PowerShell examples are cross-platform only if tested on Linux/macOS, or clarify any Windows-specific requirements.
For Azure CLI commands, provide both PowerShell (with backticks for line continuation) and Bash (with backslashes) variants.
Add a section or callout for Linux/macOS users, outlining any differences or prerequisites (e.g., installing PowerShell Core, using curl/jq instead of Invoke-RestMethod, etc.).
Where possible, use platform-agnostic tools (e.g., curl, jq, Python scripts) for REST API interactions and CSV processing.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits mild Windows bias. The only specific client configuration example provided is for WinSCP, a Windows-centric SFTP client, and no Linux or cross-platform client (such as OpenSSH, FileZilla, or lftp) is mentioned or given as an example. The troubleshooting and client settings sections do not reference Linux tools or provide parity in examples, which may leave Linux users without clear guidance.

Recommendations:

Add configuration examples for popular Linux and cross-platform SFTP clients (e.g., OpenSSH's sftp, FileZilla, lftp) alongside or before WinSCP.
When listing unsupported clients, clarify whether these are Windows-only or cross-platform, and consider including Linux-specific clients if relevant.
In the 'Client settings' section, provide equivalent settings or notes for Linux clients (e.g., how to disable resume/temporary filename in OpenSSH sftp or FileZilla, if applicable).
Ensure troubleshooting steps reference both Windows and Linux command-line tools and error messages where appropriate.
Consider a dedicated section or table comparing client compatibility and configuration steps for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by specifying Windows as the OS type when creating the Function app, omitting Linux alternatives. It also lacks explicit Linux examples or guidance for deploying Function apps on Linux, and the only OS-specific flag shown is '--os-type windows'. No PowerShell-specific commands are present, but the pattern of mentioning Windows first and not providing Linux parity is evident.

Recommendations:

Provide examples for both Windows and Linux when creating the Function app, e.g., show '--os-type Linux' usage.
Explicitly mention that Azure Functions supports both Windows and Linux, and discuss any differences or considerations.
Include a note or section on how to adapt the steps for Linux users, especially for the Function app creation and deployment.
Ensure that all CLI commands and instructions are OS-agnostic or provide alternatives where behavior differs.
Review screenshots and portal instructions to ensure they are not Windows-specific and clarify any OS-dependent UI differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for database management, with PgAdmin only mentioned as an alternative. In all code examples (git, npm, environment variable setting), both Bash and PowerShell are shown, but PowerShell is always presented second, not first. However, the documentation does not provide Linux-specific troubleshooting or mention Linux-native tools (like psql CLI) for PostgreSQL management. The focus on Azure Data Studio and the lack of Linux-first or CLI-native workflows indicate a Windows-centric approach.

Recommendations:

Provide equal prominence to Linux-native tools such as psql CLI and PgAdmin, including step-by-step instructions for these tools.
When listing tools for database management, mention cross-platform and Linux-native tools first or equally (e.g., 'You may use Azure Data Studio, PgAdmin, or the psql command-line tool').
Include Linux-specific troubleshooting tips or notes where relevant (e.g., firewall configuration, environment variable syntax).
For all command examples, consider using a tabbed interface with Bash (Linux/macOS) as the default or first tab, or explicitly state that both shells are supported equally.
Add a section or callout for users developing on Linux, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias by exclusively using Visual Studio (Windows-only) for development, instructing users to set the Function App OS to Windows, and providing no guidance or examples for Linux or cross-platform development environments. There are no instructions for using VS Code, CLI, or other tools commonly used on Linux/macOS, nor any mention of deploying or running on Linux-based Function Apps.

Recommendations:

Provide parallel instructions for developing Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
Include steps for creating and deploying Function Apps with the OS set to Linux, and highlight any differences or considerations.
Offer examples for installing dependencies and running/debugging the function on Linux/macOS (e.g., using dotnet CLI, bash, or zsh).
Mention that Azure Functions can be hosted on both Windows and Linux, and explain how to select the appropriate OS during Function App creation.
Avoid assuming Visual Studio is the only or primary development environment; reference alternatives early and equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows tools and patterns first or exclusively. It mentions that a secure FTP client is installed on most typical Windows instances, and recommends WinRAR (a Windows tool) for extracting Zstandard archives, without mentioning Linux equivalents. There are no explicit Linux command examples or tool recommendations, and the documentation assumes a Windows-centric environment for host operations.

Recommendations:

Explicitly mention and provide examples for both Windows and Linux environments when discussing prerequisites and tools (e.g., recommend FileZilla or lftp for Linux as secure FTP clients).
Suggest Linux-native tools for extracting Zstandard archives, such as 'tar' with 'zstd' or the 'unzstd' command, alongside WinRAR.
Include example commands for retrieving and extracting the support bundle on Linux hosts, not just Windows.
Avoid language that assumes the user is on Windows (e.g., 'A secure FTP client is installed on most typical Windows instances') and instead provide parity for both platforms.
Where screenshots or command snippets are shown, provide both Windows and Linux variants if the process differs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench) for database management, omitting explicit Linux-native alternatives (such as the MySQL CLI). While both Bash and PowerShell examples are provided for CLI commands, the database tooling and portal navigation instructions assume a GUI workflow more common on Windows. There are no explicit Linux-specific instructions or screenshots, and the documentation does not mention Linux package managers or command-line tools for MySQL database management.

Recommendations:

Include explicit instructions and examples for using the MySQL CLI (mysql, mysqladmin) for database creation, querying, and data manipulation, especially for Linux users.
Mention Linux-native tools (e.g., DBeaver, command-line MySQL clients) alongside Azure Data Studio and MySQL Workbench.
Provide package manager installation commands for Azure Data Studio, MySQL CLI, or other recommended tools on Linux (e.g., apt, yum, snap).
Add screenshots or terminal output examples from Linux environments where appropriate.
Clarify that all steps can be performed on Linux, and highlight any differences or prerequisites for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing Azure PowerShell before Azure CLI in the deployment methods, and by providing both Azure CLI and PowerShell commands for resource cleanup, but omitting explicit Linux shell (bash) or cross-platform examples. There are no Linux-specific instructions or examples, and the PowerShell method is mentioned alongside CLI without clarifying cross-platform compatibility.

Recommendations:

Present Azure CLI (which is cross-platform) examples before PowerShell, or clarify that Azure CLI works on all platforms including Linux and macOS.
Add explicit bash/shell examples for Linux users, especially for common tasks like resource group deletion.
When referencing deployment methods, include links or notes for Linux/macOS users (e.g., 'See how to deploy with Azure CLI on Linux').
Avoid implying PowerShell is the primary or default method; treat CLI and PowerShell equally, or lead with CLI for broader platform coverage.
Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. It references PowerShell cmdlets and APIs for manual RBAC assignment, but does not mention or provide equivalent instructions for Linux users (such as Azure CLI or Bash). No Linux-specific tools or examples are provided, and the troubleshooting steps assume familiarity with Windows-centric patterns. There are no explicit Linux instructions or parity in command-line tooling.

Recommendations:

Include Azure CLI (az) command examples alongside or before PowerShell cmdlets for RBAC assignment and troubleshooting.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide Bash/CLI equivalents where possible.
Add troubleshooting guidance for common Linux/NFS scenarios, not just SMB/Windows.
Where APIs or SDKs are referenced, clarify that these are cross-platform and provide links or examples for both PowerShell and CLI.
Review all troubleshooting steps to ensure they are not Windows-centric and are accessible to users on all platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides extensive PowerShell examples and references, including file paths and commands that are specific to Windows environments (e.g., C:\temp\json.txt), and often lists PowerShell before Azure CLI. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or considerations. This may make the documentation less approachable for Linux users and those who do not use PowerShell.

Recommendations:

Add Bash shell equivalents for all PowerShell examples, especially for tasks like file manipulation (e.g., using cat, jq, or similar tools for JSON processing).
Use platform-neutral file paths in examples (e.g., /tmp/json.txt or ./json.txt) or provide both Windows and Linux/Mac paths.
When listing command-line options, alternate the order or explicitly state that both PowerShell and Azure CLI are cross-platform, and highlight CLI as suitable for Linux/macOS.
Include a note that Azure CLI commands work natively on Linux/macOS and can be run in Bash or other shells.
Where PowerShell is used for scripting, provide equivalent Bash scripts or commands for Linux users.
Review screenshots and UI references to ensure they are not Windows-specific, or provide clarifying notes if UI differs on other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ visual_studio_code_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by emphasizing Visual Studio Code (a Microsoft product popular on Windows) for debugging, and by not providing any Linux- or macOS-specific instructions, terminal commands, or troubleshooting notes. All examples are generic but implicitly assume a Windows-centric workflow, especially in the debugging section. There are no explicit references to Windows-only tools or PowerShell, but the absence of Linux/macOS parity in examples and tool recommendations is notable.

Recommendations:

Include explicit instructions or notes for Linux and macOS users, such as alternative editors (e.g., VS Code, Vim, or JetBrains IDEs) and terminal usage.
Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, environment variables, or port conflicts).
Provide example commands or screenshots from Linux/macOS terminals to demonstrate cross-platform compatibility.
Mention that Visual Studio Code is cross-platform, and suggest alternatives for users who may not use it.
Clarify that all CLI commands are platform-agnostic, and note any platform-specific differences if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. In tool and workflow tables, Azure PowerShell is consistently listed before Azure CLI, and PowerShell is mentioned as a primary method for tasks such as ingesting and downloading data. There is a lack of explicit Linux command-line examples or references to Linux-native tools, and the documentation does not provide parity in example order or depth between Windows and Linux environments. Azure Storage Explorer and AzCopy are cross-platform, but the documentation does not highlight their use on Linux or provide Linux-specific guidance.

Recommendations:

Ensure that Azure CLI examples and references are given equal prominence to PowerShell, and consider listing CLI before or alongside PowerShell to avoid a 'Windows-first' impression.
Add explicit Linux command-line examples and workflows, such as bash scripts or Linux shell commands, especially for common tasks like data ingestion, download, and monitoring.
Highlight the cross-platform nature of tools like AzCopy and Azure Storage Explorer, and provide instructions or screenshots for Linux environments.
Include references to Linux-native tools or integration patterns (e.g., using curl, wget, or Linux automation tools) where appropriate.
Where PowerShell is mentioned, clarify that it is available on Linux as well, or provide alternative Linux-native command examples.
Review the order of tool listings in tables and prose to ensure that Windows-specific tools are not always listed first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by consistently mentioning PowerShell before Azure CLI, grouping them together as primary command-line interfaces, and not providing explicit Linux- or macOS-specific examples or guidance. The focus on PowerShell, a Windows-centric tool, and the lack of parity in example depth or order for cross-platform tools like Azure CLI may make Linux users feel secondary. There are no explicit Linux shell (bash) or macOS instructions, and the documentation does not clarify cross-platform differences or considerations.

Recommendations:

Ensure that Azure CLI examples are presented before or alongside PowerShell, emphasizing its cross-platform nature.
Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide example commands in bash syntax where appropriate.
Add a section or callout for Linux/macOS users, highlighting any differences or prerequisites.
Where PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent bash commands.
Review linked articles (e.g., 'authorize-data-operations-cli.md' and 'authorize-data-operations-powershell.md') to ensure Linux parity in examples and instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides management instructions for Azure Storage Mover projects using the Azure Portal and PowerShell exclusively. All command-line examples use PowerShell cmdlets, with no mention of cross-platform CLI tools (such as Azure CLI) or Linux shell equivalents. Installation instructions and prerequisites are PowerShell-specific, and there are no Bash or Linux-native command examples. This creates a bias towards Windows users and environments.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell script examples alongside PowerShell, especially for variable assignment and command execution.
Explicitly mention that PowerShell Core is available on Linux and macOS, but clarify that Azure CLI is often preferred on those platforms.
Reorder sections or provide tabs so that Azure CLI and Bash examples are presented alongside or before PowerShell, ensuring parity.
Review installation instructions to include Azure CLI installation steps for Linux/macOS users.
Avoid language or tool recommendations that assume a Windows environment unless absolutely necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing PowerShell and Azure Storage Explorer (a GUI tool more common on Windows) before Azure CLI in the 'How to set ACLs' section. PowerShell is given its own row, and Storage Explorer is listed first, while Linux-native tools or shell examples are not provided. The only command-line example for obtaining a service principal's object ID uses Azure CLI, which is cross-platform, but no explicit Linux shell (e.g., bash) or Linux file system command analogies are given. There are no Linux-specific examples or references to Linux command-line tools for managing ACLs, despite the POSIX context.

Recommendations:

Provide Linux shell (bash) examples for managing ACLs using Azure CLI, including sample commands for common tasks.
Include references to Linux-native tools (e.g., setfacl, getfacl) for users familiar with POSIX ACLs, and draw explicit parallels between Azure Data Lake Storage ACLs and Linux file system ACL management.
Reorder the 'How to set ACLs' table to list Azure CLI before PowerShell and Storage Explorer, or group CLI tools together to avoid a Windows-first impression.
Add a section or examples specifically targeting Linux users, such as scripting with bash or integrating with Linux-based automation.
Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation links or tips for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and explanations before Azure CLI equivalents, and by referencing PowerShell-specific cmdlets and workflows. The PowerShell section is more comprehensive, with step-by-step command breakdowns, while the Azure CLI section is less detailed. There is no mention of Linux-specific tools, shells, or workflows, and the use of PowerShell as a primary scripting example assumes a Windows-centric audience.

Recommendations:

Provide equally detailed Azure CLI examples, including step-by-step breakdowns of commands and their parameters, to match the depth of the PowerShell section.
Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, to encourage non-Windows users.
Add Bash shell script examples for common lifecycle policy tasks, demonstrating usage in a typical Linux environment.
Avoid presenting PowerShell examples before CLI or Bash examples; consider presenting CLI first or in parallel, as it is more universally available.
Reference Linux and macOS environments in prerequisites or introductory sections, clarifying that all operations can be performed from those platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerShell instructions (a Windows-centric tool) before Azure CLI examples, and does not mention or provide Linux-specific command-line environments or examples. There is a lack of parity in guidance for Linux users, as the PowerShell section is more detailed and appears before the Azure CLI, which is cross-platform. No explicit Linux shell (bash) or scripting examples are given, and the template section assumes use of the Azure Portal, which is platform-agnostic but not CLI-based.

Recommendations:

Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash shell usage where appropriate.
Balance the level of detail between PowerShell and Azure CLI sections to ensure Linux users have equally comprehensive instructions.
Consider adding a section or note for Linux users, highlighting any platform-specific considerations or tips.
If possible, provide examples using Azure SDKs or REST API calls that are platform-neutral.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently referencing Windows-specific tools and patterns. PowerShell is given a dedicated section, and instructions for the Azure CLI repeatedly suggest using Windows PowerShell as the example terminal, with file paths in Windows format (e.g., C:\demo-file.txt). There are no explicit Linux or macOS examples, nor are cross-platform considerations (such as file path differences or alternative shells) addressed. The documentation does not mention or show Linux command-line environments, and the use of Windows-centric terminology and tools is prevalent throughout.

Recommendations:

Provide explicit Linux/macOS examples alongside Windows ones, especially for CLI commands (e.g., show file paths like /home/user/demo-file.txt).
When referencing a command console, mention cross-platform options such as Bash, Terminal, or zsh, not just Windows PowerShell.
Balance PowerShell examples with Bash or generic shell script examples where possible.
Clarify that Azure CLI and AzCopy are cross-platform, and show usage in both Windows and Linux/macOS environments.
Avoid using only Windows-style file paths in examples; provide both Windows and Unix-style paths.
Add notes or callouts about any differences in behavior or prerequisites on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. In the 'Uploading content' section, Windows-centric tools and workflows (Azure PowerShell, Visual Studio Code extension, Azure Storage Explorer) are listed alongside cross-platform tools, but PowerShell is given equal prominence to the Azure CLI, and Windows tools are mentioned before Linux-native equivalents. There are no explicit Linux-specific examples or mentions of Linux-native tools or workflows. The documentation does not provide Linux shell (bash) or scripting examples, and it assumes familiarity with tools more common in Windows environments.

Recommendations:

Provide explicit Linux/bash command-line examples for common tasks (e.g., using Azure CLI in bash, AzCopy in Linux).
Include Linux-native tools or workflows (e.g., mention using rclone, curl, or bash scripting for uploads).
Balance the order of tool listings: list Azure CLI before PowerShell, and clarify that both are cross-platform.
Add screenshots or instructions for Linux environments (e.g., terminal screenshots, file path conventions).
Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide links to Linux installation guides.
Consider a 'Platform differences' section to highlight any OS-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning cross-platform or Linux-native options, and by not providing explicit Linux or Bash/CLI examples. The mention of PowerShell and the Azure classic CLI (which is Windows-focused) without equal emphasis on Azure CLI (which is cross-platform and more commonly used on Linux) further highlights this bias. There are no Linux-specific instructions, and no Bash or shell command examples are provided.

Recommendations:

Include explicit Azure CLI examples, as it is cross-platform and widely used on Linux and macOS.
When listing tools for assigning roles, mention Azure CLI before PowerShell and Azure classic CLI, or present them together with equal prominence.
Provide Bash or shell command examples alongside PowerShell examples, or use Azure CLI as the primary example since it works across all platforms.
Clarify that all management operations can be performed from Linux, macOS, and Windows, and provide links to relevant cross-platform documentation.
Avoid referencing deprecated or Windows-only tools (such as Azure classic CLI) unless necessary, and always provide modern, cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (e.g., WireShark, NetMon) for network diagnostics, and by not providing Linux equivalents or cross-platform alternatives. Additionally, some sections (such as .NET configuration) are Windows-centric, and there is a lack of explicit Linux or cross-platform command-line examples (e.g., AzCopy usage, PowerShell vs. Bash/CLI). The order of mention for tools and examples tends to favor Microsoft/Windows technologies, with Linux or cross-platform considerations only briefly acknowledged or omitted.

Recommendations:

When mentioning diagnostic tools like WireShark and NetMon, include Linux alternatives such as tcpdump or Wireshark (noting its cross-platform nature).
Provide explicit Linux/Bash command-line examples for tools like AzCopy, and clarify that AzCopy is cross-platform.
Where .NET configuration is discussed, add references to equivalent settings or considerations for other languages and platforms (e.g., Java, Python, Node.js), and include links to relevant documentation.
When listing client libraries and tools, mention Azure CLI and its cross-platform nature before or alongside PowerShell.
Review the order of tool and example presentation to ensure Linux and cross-platform options are not consistently secondary to Windows/PowerShell.
Add a section or call-out summarizing cross-platform support and best practices for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates some Windows bias, particularly in the registration instructions for preview features, where PowerShell is presented before Azure CLI. There are also references to PowerShell and Windows tools (e.g., PowerShell screenshots and cmdlets), even though the main focus of the guide is on Linux clients. However, the core technical instructions and examples for encrypting NFS data in transit are Linux-centric, with detailed steps for multiple Linux distributions and no actual Windows mounting instructions (since NFS Azure Files with EiT is Linux-only).

Recommendations:

Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more relevant for Linux users.
Replace or supplement PowerShell screenshots with Linux terminal screenshots where appropriate.
Avoid using the term 'cmdlet' when referring to Linux commands; use 'command' or 'CLI command' instead.
Clarify early in the document that the feature is only supported on Linux, and remove any unnecessary references to Windows tools or PowerShell unless specifically relevant to management tasks that can only be done from Windows.
Ensure all troubleshooting and verification screenshots are from Linux environments.
If management tasks (such as registration) must be performed from Windows/PowerShell, provide equivalent Bash/CLI instructions and note any platform limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exclusively provides a PowerShell script example for batch creation of Azure Elastic SAN volumes, referencing a Windows-style file path and omitting any Linux or cross-platform alternatives. There is no mention of Bash, Azure CLI, or Linux-compatible scripting, and the use of PowerShell and Windows file paths is presented as the default approach.

Recommendations:

Include a Bash or Azure CLI script example for Linux/macOS users performing the same batch operation.
Show file path examples in both Windows (e.g., D:\ElasticSan\TestCsv3.csv) and Linux (e.g., /home/user/ElasticSan/TestCsv3.csv) formats.
Mention that the operation can be performed from any OS and provide guidance or links for installing and using Azure PowerShell on Linux/macOS, or suggest Azure CLI as an alternative.
If PowerShell is required, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
Consider reordering or presenting both Windows and Linux options side-by-side to avoid the impression that Windows is the primary or only supported environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a moderate Windows bias. PowerShell is presented as a primary scripting interface alongside the Azure Portal and Azure CLI, with explicit PowerShell command examples and references. In several sections, PowerShell is listed before Azure CLI, and the CLI tab itself incorrectly instructs users to 'Run the following PowerShell command' instead of 'Azure CLI command.' No Linux-specific shell or scripting examples (such as Bash) are provided, and there is no mention of Linux tools or environments. The documentation assumes familiarity with PowerShell and Windows-centric tooling, which may disadvantage Linux users.

Recommendations:

Correct the Azure CLI sections to refer to 'Azure CLI command' instead of 'PowerShell command.'
Add Bash shell examples for Azure CLI commands, demonstrating usage in a typical Linux or macOS terminal.
Clarify that Azure CLI commands can be run on Windows, Linux, and macOS, and provide any OS-specific notes if needed (e.g., line continuation differences).
Where PowerShell is mentioned, consider adding a note or tab for Bash or sh equivalents, especially for scripting scenarios.
Review the order of tabs and examples; consider listing Azure CLI (cross-platform) before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
Audit for any other Windows-centric terminology or assumptions, and ensure parity in guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform, focusing on Azure CLI, which works on all major OSes. However, there are subtle Windows biases: the AzCopy example uses a Windows file path ('C:\myDirectory\myFile.txt') without a Linux/macOS equivalent, and no Linux/macOS example is provided for AzCopy. The only explicit file creation example uses 'vi', which is cross-platform but more common on Linux/macOS. Overall, the documentation could better demonstrate parity by including Linux/macOS-specific examples where Windows-specific patterns are shown.

Recommendations:

For every example using a Windows file path (e.g., 'C:\myDirectory\myFile.txt'), provide a Linux/macOS equivalent (e.g., '~/myDirectory/myFile.txt').
In the AzCopy section, show both Windows and Linux/macOS command examples side by side.
Explicitly state that AzCopy is available on all major platforms and provide installation links for each.
Where file creation is demonstrated (e.g., using 'vi'), briefly mention alternatives for Windows users (e.g., 'notepad').
Review all examples to ensure that neither OS is implicitly prioritized, and that users on any platform can follow along without confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All deployment, management, and troubleshooting instructions assume or require Windows Server. Only Windows Server is supported for Azure File Sync agents, and all examples (such as PowerShell cmdlets) are Windows-specific. There are no Linux or cross-platform examples or guidance, and Linux is only mentioned in the context of direct SMB mounting, not as a sync agent or management platform.

Recommendations:

Clearly state early in the documentation that Azure File Sync is only supported on Windows Server, and explain the rationale.
Provide a comparison table or section outlining what is and is not possible on Linux/macOS versus Windows, especially for hybrid and migration scenarios.
Where possible, include Linux/macOS examples for direct SMB mounting and management, or link to relevant documentation.
If Linux support is not planned, offer alternative solutions or migration paths for organizations with Linux-based file servers.
Avoid presenting PowerShell/Windows tools as the only management interface; if REST APIs or CLI tools are available, provide cross-platform examples.
Explicitly mention the lack of Linux agent support in the prerequisites and planning sections to set expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, using PowerShell-specific cmdlets, and referencing Windows-centric tooling and patterns. While Azure CLI is included, the PowerShell section is more detailed and appears before the CLI, which is more cross-platform. There are no Linux- or Bash-specific examples, and the documentation does not mention or show screenshots from Linux environments.

Recommendations:

Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more accessible to Linux users.
Include Bash shell examples and clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
Add notes or screenshots showing the process in Linux terminal environments where relevant.
Where PowerShell is mentioned, also mention that Azure CLI is available and preferred for Linux/macOS users.
Avoid using Windows-specific terminology or screenshots exclusively; include Linux equivalents or clarify cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation for Azure File Sync is heavily biased toward Windows environments. All instructions, requirements, and examples are exclusively for Windows Server, with repeated references to Windows-specific tools (e.g., PowerShell cmdlets, Robocopy, NTFS, FSRM, .NET Framework). There is no mention of Linux support, alternatives, or parity, and no Linux or cross-platform examples are provided. The documentation assumes the reader is operating in a Windows-only context.

Recommendations:

Clearly state early in the documentation whether Azure File Sync is supported only on Windows Server, and if so, explain why and whether Linux support is planned.
If partial Linux support exists (e.g., for Azure Files itself), provide guidance or links for Linux users on how to interact with Azure Files, even if sync agent parity is not available.
Where PowerShell cmdlets are referenced, offer equivalent CLI or REST API commands if available, and clarify their platform compatibility.
Avoid using only Windows-specific tools (e.g., Robocopy, FSRM) in examples; if alternatives exist for Linux, mention them.
Add a section explicitly addressing cross-platform considerations, including limitations and possible workarounds for non-Windows environments.
If Azure File Sync is fundamentally a Windows-only solution, make this limitation prominent and suggest alternative architectures for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. Windows-specific tools (Schtasks) are mentioned before their Linux equivalents (crontab), and Windows paths/examples are often listed first. There is a tendency to explain Windows concepts and commands in more detail, and some sections (such as authentication and script creation) provide more explicit guidance for Windows users. Linux examples are present but sometimes less detailed or appear after Windows content.

Recommendations:

Alternate the order in which Windows and Linux examples are presented, or present them side-by-side to avoid always listing Windows first.
Ensure that all explanations and command breakdowns are equally detailed for both Windows and Linux users.
Where possible, provide parity in example scripts and command-line usage, including full Linux shell script examples (not just commands).
Expand on Linux-specific instructions, such as setting environment variables for authentication in cron jobs, and provide troubleshooting tips for both platforms.
Use neutral language when introducing cross-platform tools, and avoid implying Windows as the default or primary environment.
Include macOS examples where relevant, especially for script creation and scheduling.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation assumes the use of Windows Server exclusively, with all steps, tools, and examples (such as Robocopy and DFS-N) being Windows-specific. There are no Linux equivalents or cross-platform guidance, and the documentation does not acknowledge the possibility of non-Windows environments.

Recommendations:

Clarify early in the documentation whether Azure File Sync supports only Windows Server, or provide guidance for Linux or cross-platform scenarios if available.
If Linux support is possible, include equivalent Linux commands and tools (e.g., rsync instead of Robocopy) for file copying.
Mention Linux-compatible alternatives to DFS-N for namespace redirection, or explicitly state if such functionality is unavailable.
Structure instructions to acknowledge both Windows and Linux environments, or explain the Windows-only limitation up front.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways. PowerShell examples are given in full detail before the Azure CLI/Linux equivalent, and the PowerShell section is more verbose and prominent. Windows-specific tools and scenarios (such as Azure File Sync with Windows file servers) are described in detail, while Linux/NFS scenarios are less emphasized or omitted. There are no Linux/NFS-specific redundancy or failover examples, and the documentation does not provide parity in guidance or troubleshooting for Linux clients.

Recommendations:

Provide Linux/NFS-specific examples and scenarios, especially for redundancy, failover, and disaster recovery.
Ensure that Azure CLI/bash examples are given equal prominence and detail as PowerShell examples, possibly presenting CLI first or side-by-side.
Include troubleshooting and operational guidance for Linux/NFS clients, not just SMB/Windows clients.
Mention and link to Linux tools (e.g., rsync, cron, Linux mount options) where relevant, especially in sections discussing custom scripts or sync solutions.
Clarify any differences in redundancy support or behavior for NFS/Linux clients versus SMB/Windows clients.
Balance the documentation so that Windows and Linux users can both find relevant, actionable information for their platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated example section before the Azure CLI, and Azure PowerShell is referenced as a primary tool for managing storage accounts. The Azure Storage Explorer documentation link defaults to Windows tabs, and the Azure portal (which is often used on Windows) is emphasized. There are no explicit Linux shell (bash) or cross-platform scripting examples, and no mention of Linux-specific tools or workflows. While Azure CLI is included, it is presented after PowerShell, and there is no explicit parity guidance for Linux users.

Recommendations:

Provide bash or shell script examples alongside PowerShell, especially for common tasks such as updating storage account properties.
Ensure that Azure CLI examples are presented before or alongside PowerShell to emphasize cross-platform compatibility.
When referencing Azure Storage Explorer or other tools, include instructions or links for Linux and macOS versions, not just Windows.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
Where screenshots or UI walkthroughs are given, clarify if the experience differs on non-Windows platforms.
Consider including a table or section summarizing tool availability and usage across different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting Windows/Powershell instructions and scripts before Linux/CLI equivalents, using Powershell as the primary example for deletion commands, and referencing Windows-specific tools and patterns. Linux instructions are present but are consistently positioned after Windows ones, and the scripting approach for Linux is less integrated (Python script vs. native shell).

Recommendations:

Alternate the order of Windows and Linux sections, or present them side-by-side to avoid privileging one platform.
Provide native Bash/shell script examples for Linux users, not just Python scripts.
Ensure that Azure CLI examples are given equal prominence to PowerShell, possibly by combining them in unified tabs or sections.
Explicitly state that both Windows and Linux are fully supported and provide parity in instructions and tooling.
Review terminology to avoid Windows-centric language (e.g., refer to 'command-line' or 'shell' rather than 'PowerShell' when discussing general concepts).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_reference

Summary:

The documentation page exhibits mild Windows bias. In the encryption section, BitLocker (a Windows-specific tool) is referenced as an analogy for storage service encryption, and the only deep-dive link for cryptographic modules is to a Windows-specific API (Cryptography API: Next Generation). In the networking section, mounting instructions mention AKS, Linux, and Windows, but Windows is listed last, which is not biased. However, there are no command-line examples or tooling references for either platform, so there is no overt PowerShell or CLI bias. Overall, the documentation leans on Windows concepts and references for explanations and further reading, which may not be as relatable for Linux users.

Recommendations:

When using analogies for encryption, include Linux equivalents (e.g., 'similar to BitLocker on Windows or LUKS on Linux').
Provide links to cross-platform or Linux-specific cryptographic documentation (e.g., dm-crypt, LUKS, or general AES/FIPS documentation) alongside Windows references.
Ensure that any tooling or API references are balanced, or at least mention Linux alternatives if Windows-specific tools are cited.
If examples or scripts are added in the future, ensure parity between Windows (PowerShell, etc.) and Linux (bash, etc.) examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric. All examples use Windows-only tools (Robocopy), reference Windows services (Storage Sync Agent Service), and assume the use of Windows Server. There are no Linux equivalents or instructions, and no mention of how to perform these tasks on Linux systems or with cross-platform tools.

Recommendations:

Add equivalent instructions for Linux servers, including supported distributions and any prerequisites.
Provide examples using cross-platform tools (e.g., rsync for file copying) alongside Robocopy.
Clarify whether Azure File Sync is supported on Linux, and if not, explicitly state this early in the documentation.
If only Windows is supported, add a prominent note to avoid confusion for Linux administrators.
Where possible, use neutral terminology (e.g., 'copy files using your platform's preferred tool') and provide both Windows and Linux command examples.
Document how to manage SMB access and sync agent services on Linux, if supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways: PowerShell is the only scripting example provided for interacting with logs, and no equivalent Azure CLI, Bash, or Linux-native example is given. The sample log entries and user agent strings repeatedly reference Windows-specific tools and platforms (e.g., 'win32', 'Windows_NT'), and Windows tools are mentioned before or instead of cross-platform alternatives. There is no guidance or example for Linux or macOS users for common tasks such as filtering blobs or viewing metadata.

Recommendations:

Provide equivalent Azure CLI and/or Bash examples alongside PowerShell snippets for tasks such as filtering blobs and reading metadata.
Include references to cross-platform tools (e.g., Azure Storage Explorer for Linux/macOS, AzCopy on Linux) and show their usage.
When mentioning tools or user agents, clarify their cross-platform availability and provide examples relevant to Linux/macOS environments.
Ensure that instructions and code samples are not Windows-centric by default; present cross-platform or Linux-first examples where appropriate.
Explicitly state that all features and operations are available on Linux/macOS, and link to relevant documentation for those platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for scripting and automation, explicitly instructing users to open a Windows PowerShell command window. There are no equivalent examples for Linux users (e.g., Bash, Azure CLI), and file paths in AzCopy examples use Windows-style paths. The documentation refers to Windows tools and patterns before or instead of cross-platform or Linux-native alternatives.

Recommendations:

Provide equivalent Azure CLI (az) examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
Avoid instructions that explicitly reference 'Windows PowerShell command window'; instead, use neutral language like 'open a terminal window'.
When showing file paths (e.g., in AzCopy examples), include both Windows and Linux/macOS path formats, or use placeholders and explain both.
Mention and demonstrate the use of cross-platform tools (e.g., Azure CLI, AzCopy) equally alongside PowerShell.
If referencing Microsoft Azure Storage Explorer, clarify its cross-platform availability.
Add Bash or shell script examples where appropriate, especially for common administrative tasks.
Ensure that any .NET code samples are supplemented with samples for other languages commonly used on Linux, where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides instructions and examples for installing the Azure File Sync agent on Windows, using Windows-specific tools (msiexec), Windows file paths, and Windows environment variables. There are no references to Linux, Linux tools, or cross-platform installation methods, indicating a strong Windows bias.

Recommendations:

Explicitly state if Azure File Sync agent is only supported on Windows. If so, clarify this early in the documentation to set user expectations.
If Linux support is planned or available, provide equivalent Linux installation instructions, including command-line examples (e.g., using dpkg, rpm, or shell scripts).
Include Linux file path examples and environment variable formats where relevant.
If the agent is Windows-only, consider linking to alternative Azure file synchronization solutions for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation for Azure File Sync demonstrates a strong Windows bias. All examples, scenarios, and deployment instructions exclusively reference Windows Server, with no mention of Linux or cross-platform alternatives. The language assumes the use of Windows Server for local caching, management, and recovery, and only Windows-specific tools and protocols are discussed in detail.

Recommendations:

Explicitly state whether Azure File Sync supports only Windows Server, or clarify any Linux or cross-platform limitations.
If Linux support exists or is planned, provide equivalent Linux examples and instructions for deployment, management, and recovery.
Mention Linux-compatible protocols (such as NFS) in parity with SMB, and clarify how non-Windows clients can interact with Azure File Sync.
If only Windows Server is supported, add a note early in the documentation to set expectations for non-Windows users.
Consider including a comparison table outlining feature availability and limitations for Windows vs. Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-specific tools (Visual Studio, .exe paths), using Windows-style paths (c:\azurite) in all CLI examples, and omitting explicit Linux/macOS command examples for running Azurite or specifying data directories. Installation and usage instructions for Visual Studio are Windows-centric, and there are no Linux/macOS-specific instructions or screenshots. While the introduction claims cross-platform support, practical guidance is overwhelmingly Windows-focused.

Recommendations:

For every CLI example using Windows paths (e.g., c:\azurite), provide equivalent Linux/macOS examples (e.g., /home/user/azurite or ~/azurite).
Explicitly document the location of the Azurite executable for Visual Studio Code and npm/Docker installs on Linux/macOS.
Add Linux/macOS-specific instructions and screenshots where appropriate, especially for file paths, environment variables (e.g., export vs set), and Docker volume mounts (e.g., -v ~/azurite:/data).
Where Visual Studio is referenced, clarify that it is Windows-only and provide alternative workflows for Linux/macOS users (e.g., using VS Code, npm, or Docker).
Ensure that all environment variable examples include both Windows (set) and Linux/macOS (export) syntax.
Add a section or tab for 'Linux/macOS' in all relevant install/run instructions to ensure parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows tools (icacls, Windows File Explorer, net use), require a Windows client, and reference PowerShell cmdlets. There are no Linux or cross-platform examples, nor any mention of how to manage permissions from non-Windows systems. The documentation also assumes Active Directory integration in a Windows context and does not address Linux SMB clients or NFS scenarios.

Recommendations:

Add instructions and examples for configuring file share permissions from Linux clients, including mounting Azure Files over SMB using Linux tools (e.g., mount.cifs) and managing permissions with setfacl or equivalent.
Clarify whether Windows ACLs can be managed from non-Windows clients, and if not, explicitly state this limitation.
If Azure Files does not support Linux ACLs or NFS permissions, mention this clearly and provide guidance for Linux/NFS users.
Include parity in documentation structure: present Linux (and macOS, if supported) options alongside Windows, not just as an afterthought.
Reference cross-platform tools or APIs (such as Azure CLI, REST API, or AzCopy) where possible for managing permissions, and provide examples for their use on Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by providing configuration examples only for PowerShell and .NET (both Windows-centric), referencing Fiddler (a Windows tool) for verification, and omitting any Linux or cross-platform command-line examples. There is no mention of Linux shell commands, OpenSSL, or Linux-native tools for TLS configuration or verification.

Recommendations:

Add equivalent examples for configuring TLS version in common Linux environments, such as using curl or Python scripts.
Include instructions or code samples for verifying TLS version on Linux, e.g., using tcpdump, Wireshark, or OpenSSL.
Mention and demonstrate cross-platform tools for network traffic inspection, such as Wireshark or tcpdump, alongside or instead of Fiddler.
Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel Windows and Linux/macOS instructions.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is exclusively focused on Windows environments, both in prerequisites and all example commands. It explicitly states that Azure File Sync is only supported on Windows, and all instructions, settings, and validation steps are tailored for Windows servers. There are no Linux equivalents, examples, or even mentions of Linux support or alternatives. All tooling and patterns (e.g., PowerShell, Windows file paths, Windows services) are Windows-centric, and Linux is only mentioned to clarify lack of support.

Recommendations:

If Azure File Sync is not supported on Linux, clearly state this at the top and consider providing links to alternative solutions for Linux file sync scenarios (e.g., Azure File NFS, rsync, third-party tools).
If Linux support is planned or possible in the future, add a section outlining current limitations and a roadmap or workaround for Linux users.
Where possible, generalize Azure CLI examples to clarify which steps are cross-platform, and explicitly note which commands or features are Windows-only.
Provide a comparison table or FAQ addressing common Linux administrator questions (e.g., 'What should I use if I have Linux servers?').
Avoid using Windows-specific terminology (like C:\ paths, Programs and Features, FileSyncSvc) in generalized sections, or clearly scope them as Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as Visual Studio and PowerShell, and by presenting Windows-specific instructions before Linux equivalents. PowerShell and Windows command-line examples are given prominence, while Linux alternatives are sometimes less detailed or appear after Windows instructions. There is also a focus on Windows development environments, with Visual Studio as the primary editor, and some steps (like package installation) include PowerShell-specific tabs but lack equivalent coverage for Linux-native tools (e.g., apt, yum, or .NET CLI on Linux).

Recommendations:

Present Linux and Windows instructions in parallel or give equal prominence to both, avoiding 'Windows first' ordering.
Include Linux-native tooling and workflows (e.g., .NET CLI on Linux, common editors like Vim or nano, and package managers like apt or yum where relevant).
Provide Bash and PowerShell examples side by side for all command-line operations.
Reference cross-platform editors (such as VS Code) before or alongside Windows-only editors like Visual Studio.
Ensure that all steps (such as setting environment variables, installing packages, and assigning roles) have clear, tested Linux equivalents.
Avoid assuming the use of Windows-specific tools (like PowerShell) as the default for scripting or automation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias: Windows and PowerShell examples are consistently presented first, and Windows-specific tools and environment variable syntax (PowerShell, cmd.exe) are described in greater detail or before Linux/macOS equivalents. Linux and macOS are included, but often as secondary considerations.

Recommendations:

Alternate the order in which Windows and Linux/macOS examples are presented, or present them side-by-side to avoid prioritizing one platform.
Provide equal detail for Linux/macOS shell usage (e.g., mention Bash or zsh explicitly, not just 'Linux').
When discussing quoting or environment variables, clarify the shell context for each OS (e.g., Bash for Linux/macOS, PowerShell and cmd.exe for Windows) and provide parallel examples.
Include a general, platform-agnostic example first, followed by OS-specific notes if needed.
Avoid using Windows-specific terminology (like %USERPROFILE%) without immediately providing the Linux/macOS equivalent in the same sentence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All mounting instructions, code samples, and troubleshooting steps are exclusively for Windows environments, using Windows-specific tools (PowerShell, net use, setspn, Active Directory DNS Manager). There are no examples, commands, or guidance for mounting Azure SMB file shares from Linux or macOS clients, nor is there mention of Linux authentication patterns or tools.

Recommendations:

Add a dedicated section for mounting Azure SMB file shares from Linux clients, including examples using the 'mount.cifs' command and relevant authentication options.
Provide Linux-specific prerequisites, such as required packages (e.g., cifs-utils), and guidance on Kerberos configuration for identity-based access.
Include troubleshooting steps and links relevant to Linux environments.
Mention macOS support or limitations, if applicable.
Ensure that examples for both Windows and Linux are presented in parallel or with equal prominence, rather than Windows-first.
Reference cross-platform tools and patterns where possible, and clarify any Windows-only limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. Windows examples and tools (such as PowerShell and Registry Editor) are often presented first or in more detail, and Windows-specific tools (e.g., iSCSI Initiator app, PowerShell cmdlets) are referenced directly. Linux examples are present and reasonably detailed, but Windows workflows and screenshots are prioritized or described before Linux equivalents.

Recommendations:

Alternate the order of Windows and Linux sections/examples throughout the document to avoid always listing Windows first.
Where possible, provide equal detail and step-by-step instructions for both Windows and Linux, including screenshots for both platforms.
Reference Linux-native tools (e.g., iscsiadm, multipath-tools) as prominently as Windows tools, and provide links to their documentation.
When mentioning PowerShell or Windows-specific tools, also mention the equivalent Linux commands or configuration files in the same context.
Ensure that any Azure CLI instructions are cross-platform and not only PowerShell-focused.
Consider adding a summary table or section at the start that outlines parity and differences between Windows and Linux workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and patterns. PowerShell is given a dedicated section before the cross-platform Azure CLI, and there is a notable emphasis on the Azure portal (which is platform-agnostic but often associated with Windows workflows). Additionally, the documentation references Windows-specific implementation details (such as Azure Storage relying on the Windows SSL stack) and links to Application Gateway configuration via PowerShell. There are no explicit Linux-specific examples or mentions of Linux command-line tools, and the documentation does not address any platform-specific considerations for Linux users.

Recommendations:

Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Include explicit Linux shell (bash) usage examples where relevant, especially for scripting or automation tasks.
When referencing tools or configuration steps (such as Application Gateway SSL policy), provide both PowerShell and Azure CLI (or ARM template) instructions.
Clarify that the Azure portal and Azure CLI are fully supported on Linux, and mention any platform-specific caveats if they exist.
Avoid language that implies Windows is the default or preferred platform (e.g., by stating 'Azure Storage relies on Windows implementation of SSL...') without balancing with Linux/OpenSSL context.
Add a section or note for Linux users, highlighting any differences or confirming parity in functionality and tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets (e.g., Add-DnsServerConditionalForwarderZone, Resolve-DnsName, Test-NetConnection), and prerequisites specifically mention the Azure PowerShell module. The instructions assume the use of Windows Server DNS, and there are no examples or guidance for configuring DNS forwarding using Linux-based DNS servers (such as BIND or dnsmasq). Linux tools and workflows are not mentioned, and no Linux command-line equivalents are provided.

Recommendations:

Add equivalent Linux-based DNS server configuration steps (e.g., using BIND or dnsmasq) for conditional forwarding.
Provide Linux command-line examples for DNS testing (e.g., dig, nslookup) alongside PowerShell examples.
Mention Linux DNS server options explicitly in the prerequisites and guidance, not just Windows Server DNS.
Where possible, present cross-platform instructions or clearly separate Windows and Linux sections.
Reference relevant Linux documentation or external resources for configuring DNS forwarding on popular distributions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, focusing on .NET (C#) SDK code, and omitting explicit Linux/bash or cross-platform scripting examples. There are no Linux-specific command-line examples (e.g., Bash, shell scripts), and the tools and workflows highlighted (PowerShell, .NET) are more familiar to Windows users.

Recommendations:

Provide Bash or shell script examples alongside PowerShell and Azure CLI, especially for common monitoring tasks.
Include code samples using cross-platform SDKs (e.g., Python, JavaScript) in addition to .NET/C#.
Alternate the order of examples so that Azure CLI or Bash appears before or alongside PowerShell to avoid a 'Windows-first' impression.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., quoting, authentication).
Where screenshots or portal instructions are given, clarify that the Azure portal is accessible from any OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI examples, and uses PowerShell variable syntax in CLI examples. There is a notable emphasis on PowerShell scripts and terminology, which may be less familiar or accessible to Linux users. No native Linux shell (bash) or cross-platform scripting examples are provided, and there is no mention of Linux-specific tools or workflows. The documentation assumes familiarity with Windows/PowerShell patterns, which can create friction for Linux users.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) examples first.
Use bash-style variable syntax in Azure CLI examples (e.g., RgName="<ResourceGroupName>") instead of PowerShell-style ($RgName).
Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Where possible, provide bash script examples for Linux users, especially in sections that involve scripting or automation.
Avoid exclusive references to Windows tools or patterns; ensure parity in instructions and terminology for both Windows and Linux environments.
Add a brief section or note on how to install and use Azure CLI and PowerShell on Linux, highlighting cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All examples, terminology, and supported scenarios are centered around Windows Server and NTFS. Only Windows-specific tools (such as File Server Resource Manager and Robocopy) are mentioned. There is no mention of Linux, Linux file systems, or cross-platform considerations, and all technical explanations assume a Windows environment.

Recommendations:

Explicitly state that Azure File Sync cloud tiering is only supported on Windows Server and NTFS, if that is the case. If Linux support is planned or available, provide equivalent guidance for Linux environments.
If Linux is not supported, add a clear note at the top of the documentation indicating the platform limitation to avoid confusion for non-Windows users.
If Linux or other platforms are supported, include examples and explanations for those platforms, such as supported file systems (e.g., ext4, XFS), equivalent quota management tools, and migration utilities.
When referencing tools like Robocopy and FSRM, offer Linux equivalents (e.g., rsync, setquota) or clarify that these are Windows-only tools.
Use more neutral language where possible, and avoid assuming the reader is only using Windows Server.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments. All examples use Windows-specific tools (PowerShell, reg.exe, fsutil, Windows Explorer), and all instructions reference Windows registry paths and services. There are no Linux or cross-platform examples, and the documentation assumes the use of Windows Server throughout. Linux equivalents or guidance are entirely absent.

Recommendations:

Clearly state at the beginning if Azure File Sync is Windows-only, or clarify platform support.
If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments (e.g., using Linux file attribute commands, systemd/service management, and configuration file locations).
Where possible, use cross-platform Azure CLI or REST API examples for management tasks.
If features are Windows-exclusive, explicitly mention this in each relevant section to set user expectations.
Consider providing a comparison table of feature availability and management steps for Windows vs. Linux, if partial support exists.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias. All migration instructions and examples assume the use of Windows Server, Windows VMs, and Windows-native tools such as PowerShell cmdlets (Invoke-StorageSyncFileRecall) and Robocopy. There are no examples or guidance for performing these migrations from Linux clients or using cross-platform tools. The documentation also recommends deploying Windows Server VMs in Azure and references Windows-specific services (Storage Migration Service) without mentioning Linux alternatives or parity.

Recommendations:

Provide equivalent Linux-based migration instructions, including how to mount Azure File Shares on Linux and perform file copies using tools like rsync or azcopy.
Include examples for invoking Azure File Sync operations from Linux environments, or clarify if such operations are not supported.
Mention cross-platform tools (e.g., azcopy) alongside or before Windows-specific tools like Robocopy, and provide command examples.
Clarify any platform limitations (e.g., if Azure File Sync server endpoints must be Windows-based) early in the documentation.
Where PowerShell cmdlets are referenced, note whether there are REST API or CLI equivalents usable from Linux.
If Storage Migration Service is only available on Windows, suggest alternative approaches for Linux users, or explicitly state the limitation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows-centric bias by referencing Windows-specific tools (such as Volume Shadow Copy Service and the Previous Versions tab), requiring PowerShell for certain configurations, and omitting Linux equivalents or examples. There are no instructions or examples for Linux servers, and the guidance assumes the use of Windows-based environments throughout.

Recommendations:

Include explicit guidance for Linux-based file servers, if supported by Azure File Sync, or clarify platform limitations.
Provide examples for configuring disaster recovery, backup, and restores using Linux-native tools (e.g., rsync, LVM snapshots, cron jobs) where applicable.
If PowerShell is required, mention and provide alternatives for Linux (such as Azure CLI, Bash scripts, or cross-platform PowerShell Core).
Reference cross-platform backup and restore strategies, not just Windows-specific features like VSS and Previous Versions.
Clearly state platform support at the beginning of the document, and if Azure File Sync is Windows-only, make this explicit to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally provides good Linux coverage, especially in installation instructions, but there is a subtle Windows bias in several areas. Windows and PowerShell examples are often listed first or given more detailed attention, and Windows-specific tools and patterns (such as PowerShell and .cmd batch file escaping) are discussed in more depth than their Linux equivalents. Some command examples use Windows-style paths, and Windows-specific scripting nuances are highlighted, while Linux scripting considerations are less emphasized.

Recommendations:

Alternate the order of Windows and Linux examples or present them side-by-side to avoid always listing Windows first.
Provide equivalent Linux/Bash scripting advice where Windows batch file or PowerShell scripting is discussed (e.g., escaping characters in SAS tokens for Bash).
Include Linux path examples (e.g., /home/user/path) alongside Windows path examples (e.g., C:\local\path) in command usage sections.
When discussing how to run AzCopy, explicitly mention Linux shell usage (e.g., ./azcopy) and not just Windows PowerShell.
Where PowerShell-specific commands are shown, provide Bash equivalents for Linux users.
Expand troubleshooting and scripting sections to include Linux-specific tips, not just Windows/PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All examples, instructions, and tooling references are specific to Windows Server, PowerShell, and Windows configuration files. There are no Linux equivalents or cross-platform guidance, and the documentation assumes the use of Windows-only tools and paths throughout.

Recommendations:

Clearly state at the beginning of the documentation that Azure File Sync is only supported on Windows Server, if that is the case. If Linux support is planned or available, add equivalent Linux instructions.
If any features (such as proxy/firewall configuration or connectivity testing) are available or relevant for Linux, provide Linux-specific examples using Bash, curl, iptables, or other common Linux tools.
Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform scenarios, or explicitly mention that only PowerShell is supported if that is a product limitation.
For configuration file edits (such as .NET machine.config), clarify if these steps are only for Windows or provide Linux/Mono equivalents if applicable.
When referencing Windows tools (e.g., netsh, WinHTTP, ServerRegistration.exe), indicate their platform specificity and suggest Linux alternatives or note the lack thereof.
Add a section that addresses platform support and limitations, making it clear to Linux users what is or isn't possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: it consistently refers to Windows file servers as the only supported on-premises sync targets, provides PowerShell examples and output before or instead of cross-platform alternatives, and uses Windows-centric terminology and tools (such as PowerShell and Windows DNS output). While Azure CLI and Bash examples are present for many tasks, some critical operations (such as disabling the Storage Sync Service public endpoint) are only possible via PowerShell, with the documentation explicitly stating that Azure CLI does not support the operation. There is also an absence of Linux-specific guidance or examples for managing on-premises endpoints, reflecting the Windows-only support of Azure File Sync agents.

Recommendations:

Clearly state early in the documentation that Azure File Sync currently only supports Windows file servers as sync agents, and provide a link to feature requests or roadmap for Linux support if available.
Where PowerShell is the only supported method (e.g., for Storage Sync Service public endpoint configuration), explicitly note the limitation and suggest workarounds or alternatives for Linux users, such as using Azure Portal or REST API if possible.
For all command-line examples, ensure that Azure CLI/Bash examples are given equal prominence and are not presented after PowerShell by default.
Where output examples are shown, provide both Windows (PowerShell) and Linux (Bash/CLI) output formats to help users on all platforms recognize expected results.
If certain features are not available for Linux, explicitly state this in the relevant sections to set user expectations.
Consider including a summary table at the top of the article indicating which operations are supported on which platforms/tools (PowerShell, Azure CLI, Portal, REST API) for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. Azure File Sync is described as a solution that transforms Windows Server into a cache for Azure Files, and all on-premises monitoring instructions are exclusively for Windows Server. Only Windows-specific tools (Event Viewer, Performance Monitor) and Windows event IDs are referenced, with no mention of Linux equivalents or cross-platform monitoring approaches. There are no Linux or PowerShell Core examples, nor any discussion of monitoring from non-Windows systems.

Recommendations:

Clarify early in the documentation whether Azure File Sync is supported only on Windows Server, and if so, state this explicitly to set expectations.
If Linux or cross-platform monitoring is possible (e.g., via Azure Monitor APIs, CLI, or REST), provide equivalent instructions and examples for Linux environments.
Include guidance on how to access relevant metrics and logs from non-Windows systems, such as using Azure CLI, azcopy, or REST APIs.
If only Windows Server is supported, add a clear note or section explaining the platform limitation and suggest alternative Azure Files monitoring approaches for Linux users.
Where possible, provide PowerShell Core (cross-platform) or Azure CLI examples in addition to GUI-based instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides detailed examples for configuring Azure role assignment conditions for Blob Storage, with a strong emphasis on Azure PowerShell for all command-line and scripting examples. There are no examples using cross-platform or Linux-native tools (such as Azure CLI, Bash, or REST API via curl), and all scripting guidance is provided exclusively in PowerShell syntax. This creates a Windows-centric bias, as PowerShell is primarily associated with Windows environments, even though it is available cross-platform. The lack of Linux/Unix-native examples may hinder adoption or ease-of-use for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Where scripting is shown (e.g., for testing conditions), provide Bash or shell script examples alongside PowerShell.
For REST-based operations, include curl or HTTP request examples to demonstrate how to interact with the API from any platform.
Explicitly mention that PowerShell examples are cross-platform, but clarify how to install and use PowerShell Core on Linux/macOS if retaining PowerShell as a primary example.
Consider reordering or presenting Azure CLI and Bash examples before or alongside PowerShell to avoid the perception of Windows-first bias.
Audit all sections to ensure Linux users can follow the documentation without needing to translate PowerShell commands themselves.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides instructions and examples using Windows-centric tools (PowerShell, AzFilesHybrid, Active Directory PowerShell), with no mention of Linux or cross-platform alternatives. All code samples are PowerShell, and the prerequisites and environment requirements assume a Windows domain-joined client. There is no guidance for administrators using Linux or non-Windows platforms.

Recommendations:

Provide equivalent instructions for Linux environments, if possible, such as using cross-platform tools (e.g., Azure CLI, LDAP utilities, or Samba tools) to interact with AD DS.
Explicitly state platform requirements and clarify if the operation is only supported on Windows, or provide workarounds for Linux users.
Include Linux shell (bash) examples or note if there are no supported Linux alternatives.
Mention any cross-platform modules or APIs that could be used from non-Windows systems, or provide references to relevant documentation.
If the operation is fundamentally Windows-only due to AD DS or Kerberos integration, clearly state this limitation at the beginning of the document.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page for Azure Files and Azure File Sync exhibits a Windows-centric bias. Many examples and troubleshooting steps reference Windows-specific tools (PowerShell, File Explorer, icacls, cmdkey, net use), and several workflows are described only for Windows environments. Linux and macOS are mentioned as supported platforms, but practical examples, command-line instructions, or troubleshooting steps for these platforms are largely absent. The documentation assumes familiarity with Windows patterns and tools, and Linux equivalents are not provided or are relegated to NFS-specific sections.

Recommendations:

For every PowerShell or Windows command (e.g., Get-ChildItem, icacls, cmdkey, net use), provide equivalent Linux/macOS commands (e.g., ls, getfacl/setfacl, mount.cifs, smbclient, etc.).
When describing troubleshooting or configuration steps, include Linux and macOS workflows alongside Windows instructions.
In sections discussing tools (e.g., file copy tools, auditing, credential management), explicitly mention and give examples for Linux tools (e.g., rsync, smbclient, mount, journalctl for logs).
Avoid assuming File Explorer or Windows Server as the default management interface; mention alternatives such as Nautilus, Finder, or command-line tools for Linux/macOS.
Where Windows-specific behaviors are discussed (e.g., offline attribute, thumbnail cache), clarify the equivalent or differing behavior on Linux/macOS.
Add a parity table or quick-reference guide showing how common tasks are performed on Windows, Linux, and macOS.
Review all example code blocks and ensure at least one Linux/macOS example is present for each Windows example.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples and referencing Windows-centric tools (e.g., Azure File Sync agent, PowerShell modules). There are no Linux or cross-platform CLI (such as Azure CLI) instructions or examples, and the documentation assumes the use of Windows servers or Azure Arc-enabled servers without addressing Linux-based registered servers or management workflows.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
Explicitly state whether Azure File Sync supports Linux-based registered servers, and if so, provide setup and configuration instructions for Linux environments.
Include troubleshooting and verification steps using Linux tools or scripts where applicable.
Clarify any platform limitations (e.g., if Azure File Sync agent is Windows-only) early in the prerequisites section.
Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell window') and provide both Windows and Linux shell instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All migration steps assume the use of Windows Server as the on-premises sync target, with no mention of Linux or cross-platform alternatives. Only Windows-native tools (Robocopy, Event Viewer) are referenced for file transfer and monitoring, and there are no Linux command examples or guidance for non-Windows environments. The workflow is designed around Windows Server and Azure File Sync, excluding Linux-based servers from the process.

Recommendations:

Add guidance for scenarios where the on-premises sync server is Linux-based, or clarify that Azure File Sync does not support Linux, and suggest alternative migration paths for Linux users.
Provide equivalent Linux file copy commands (e.g., rsync, cp, or robocopy alternatives) for copying data to Data Box SMB shares.
Mention and document how Linux administrators can interact with Data Box SMB shares, including mounting instructions and best practices.
If Azure File Sync is Windows-only, explicitly state this limitation early in the documentation and link to Linux-compatible Azure migration solutions (such as AzCopy, Azure Storage Mover, or third-party tools).
Include troubleshooting steps and monitoring guidance for Linux environments, if supported, or provide links to relevant Linux migration documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments. All operational steps, tools, and examples (such as Task Scheduler, Event Viewer, and PowerShell cmdlets/scripts) are specific to Windows Server. There is no mention of Linux support, alternatives, or equivalent commands, and the workflow assumes the use of Windows-native tools and interfaces throughout.

Recommendations:

Clearly state at the beginning whether Azure File Sync is supported only on Windows, or provide guidance for Linux users if support exists.
If Linux is supported, provide equivalent steps and examples for Linux environments, including how to perform sync status checks, initiate syncs, and handle errors using Linux tools or Azure CLI.
If only Windows is supported, explicitly mention this limitation to set user expectations and avoid confusion.
Where possible, use cross-platform Azure CLI examples instead of (or in addition to) PowerShell.
Reference or link to any Linux-compatible tools or scripts, or provide guidance for alternative workflows for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by prioritizing Windows-centric tools and workflows. Azure PowerShell is given a dedicated section before Azure CLI, and Azure File Sync (a Windows-only solution) is presented as the primary hybrid backup method. There is no mention of Linux-native tools or workflows for hybrid backup, and the SMB protocol (Windows-native) is emphasized over NFS (Linux/UNIX-native) in feature tables and examples.

Recommendations:

Add explicit Linux/NFS backup and restore workflows, including examples for on-premises Linux servers using NFS and rsync.
Include parity in hybrid backup guidance by referencing third-party or native Linux tools for synchronizing and backing up data to Azure Files.
Balance the order of examples and tool references: present Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
Highlight NFS support and provide equivalent data protection and disaster recovery scenarios for Linux environments.
If Azure File Sync is Windows-only, clearly state this and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All configuration and verification steps for SMB Multichannel are described exclusively for Windows clients, using PowerShell commands and Windows-specific tools (e.g., robocopy, diskspd.exe). References to SMB Multichannel support are limited to Windows, with no mention of Linux client support, configuration, or verification. Even in sections that mention both Windows and Linux (e.g., metadata caching), only Windows-centric registration and usage examples are provided. There are no Linux command-line examples, nor are Linux tools or workflows discussed.

Recommendations:

Add explicit information about SMB Multichannel support on Linux clients, including supported distributions and kernel versions.
Provide equivalent Linux command-line examples for verifying SMB Multichannel (e.g., using smbstatus, smbclient, or reviewing /proc/fs/cifs/Stats).
Include Linux alternatives to Windows tools such as robocopy and diskspd.exe (e.g., rsync, fio, or dd) for generating load and performance testing.
Document how to mount Azure SMB shares on Linux, including relevant mount options for performance.
Ensure that all configuration, verification, and troubleshooting steps are presented for both Windows and Linux clients, or clearly state if a feature is not supported on Linux.
Reference Linux documentation for SMB Multichannel and Azure Files where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows Server DFS Namespaces, Windows-based DNS management, and PowerShell/Windows GUI tools. There are no Linux or cross-platform examples, nor is there mention of Linux-based SMB clients, alternative DFS-like solutions for Linux, or how non-Windows environments might interact with DFS-N or Azure Files. All setup, configuration, and management instructions assume a Windows Server environment.

Recommendations:

Explicitly state that DFS Namespaces is a Windows Server feature and clarify any limitations or alternatives for Linux or cross-platform environments.
Add a section discussing how Linux or macOS clients can access DFS-N namespaces, including any caveats or configuration steps (e.g., using smbclient, cifs-utils, or mount.cifs).
If possible, provide guidance or references for Linux-based SMB namespace solutions (such as autofs, symlinks, or third-party DFS implementations), and how they might be used with Azure Files.
Include examples of mounting Azure Files SMB shares from Linux, and clarify how (or if) DFS-N referrals are handled by Linux SMB clients.
Mention that all management tooling (DFS Management console, PowerShell cmdlets, Windows DNS tools) is Windows-only, and suggest any available cross-platform or CLI alternatives if they exist.
Consider adding a table or callout summarizing platform support and management options for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently mentioning PowerShell alongside or before Azure CLI, and by not providing explicit Linux or cross-platform command-line examples. The focus on PowerShell, a Windows-centric tool, and the absence of Linux-specific guidance or parity in examples may make it less accessible to Linux users.

Recommendations:

Ensure that Azure CLI examples are provided before or alongside PowerShell, as Azure CLI is cross-platform.
Explicitly mention Linux and macOS compatibility when discussing Azure CLI usage.
Add example commands for both Windows (PowerShell) and Linux/macOS (Bash) environments where relevant.
Avoid grouping PowerShell and Azure CLI together without clarifying their platform support.
Include a section or note addressing Linux/macOS users and any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by consistently presenting Windows requirements, tools, and examples before their Linux counterparts. Windows-specific tools (Robocopy, PowerShell cmdlets) are emphasized, and some steps (such as mounting with NTLMv2 and using PowerShell to retrieve storage keys) are detailed for Windows but not equivalently for Linux. Linux examples are present but sometimes less detailed or referenced after Windows. The troubleshooting and verification steps also lead with Windows commands.

Recommendations:

Alternate the order of Windows and Linux sections throughout the guide, or present both in parallel where possible.
Provide Linux command-line equivalents for all PowerShell or Windows-specific instructions (e.g., retrieving storage account keys via Azure CLI or REST API).
Expand Linux examples to match the detail level of Windows examples, especially for mounting, authentication, and troubleshooting.
Include Linux-first or cross-platform tooling recommendations where appropriate (e.g., mention AzCopy or Azure CLI for both platforms).
Ensure that all references to documentation and external tools are balanced between Windows and Linux.
In the 'Verify migration' section, provide equally detailed Linux commands for file counting and validation, not just a single example.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias by consistently referencing Windows authentication technologies (Active Directory Domain Services, Kerberos, DACLs) and patterns first, with only brief mention of Linux support. Windows tools and terminology are used throughout, and there are no Linux-specific examples or guidance. The only reference to Linux is a parenthetical link, with no parity in explanation or workflow details.

Recommendations:

Add explicit Linux client examples and workflows for identity-based authentication with Azure Files over SMB, including step-by-step instructions and troubleshooting tips.
Include Linux tools and commands (e.g., mount.cifs, Kerberos configuration on Linux, relevant package requirements) alongside or before Windows equivalents where appropriate.
Balance terminology and explanations by referencing both Windows and Linux authentication mechanisms, and clarify any differences or limitations.
Provide links to Linux-focused documentation in the main body, not just as a parenthetical note.
Where diagrams or workflows are shown, include Linux client scenarios and architecture.
Ensure glossary entries and references are not exclusively Windows-focused (e.g., mention Linux Kerberos implementations, Samba, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (File Explorer, icacls, Set-ACL, robocopy) for configuring and preserving ACLs, and by only discussing Windows ACLs. There are no Linux or cross-platform examples, nor are Linux tools or patterns mentioned for managing permissions or accessing Azure Files.

Recommendations:

Include equivalent Linux instructions and examples for configuring directory and file-level permissions, such as using the 'smbclient', 'mount.cifs', or 'setfacl' commands where applicable.
Mention and explain how Linux clients can interact with Azure Files, including any limitations or differences in ACL support.
Provide parity in tool references by listing both Windows and Linux options for copying data and preserving ACLs (e.g., 'rsync' with SMB mounts, or 'cp --preserve=mode' where relevant).
Clarify whether Windows ACLs are enforced or mapped when accessed from Linux, and provide guidance for mixed-environment scenarios.
Add a section or note specifically addressing Linux administrators and their workflows for Azure Files authorization and access control.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. It explicitly recommends Windows Server RRAS as an on-premises VPN appliance, mentioning it before any Linux alternatives and without suggesting Linux-based VPN appliances. PowerShell examples are provided throughout, and in some cases, PowerShell is mentioned before CLI. There is a lack of explicit Linux-focused guidance for on-premises VPN configuration, and the only direct reference to Linux is in the context of mounting Azure Files, not in VPN setup.

Recommendations:

Mention Linux-based VPN appliances (e.g., strongSwan, OpenVPN, Libreswan) alongside Windows RRAS as supported options for on-premises VPN gateways.
Provide links or references to official guidance for configuring site-to-site VPNs using popular Linux VPN solutions.
Balance the order of examples and tool mentions (e.g., alternate between PowerShell and CLI, or present them together) to avoid Windows-first perception.
Include a short section or callout for Linux administrators, summarizing the steps or considerations for configuring a Linux-based VPN appliance.
Where PowerShell is used to retrieve information (e.g., public IP address), provide equivalent Linux/CLI commands.
Ensure that all OSes are equally represented in 'See also' and cross-reference sections, especially for core VPN setup steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by providing detailed PowerShell examples and referencing Windows-centric tools and patterns. While Azure CLI examples are included (which are cross-platform), there are no explicit Linux shell (bash) examples, nor are there references to Linux-specific tools or usage patterns. The order of presentation also places PowerShell before Azure CLI, subtly prioritizing Windows workflows. There are no explicit Linux screenshots or troubleshooting links (the only troubleshooting link shown uses a Windows tab).

Recommendations:

Add explicit Linux/Bash shell examples for metric queries using Azure CLI, including sample commands and expected outputs.
Ensure that Azure CLI examples are presented before or alongside PowerShell examples to emphasize cross-platform parity.
Include troubleshooting links and examples that reference both Windows and Linux clients, especially in sections discussing latency and performance.
Add screenshots or walkthroughs that show the experience from a Linux client (e.g., mounting Azure Files via NFS or SMB on Linux, monitoring from a Linux VM).
Where relevant, mention Linux-native tools (such as curl, jq, or shell scripting) for interacting with Azure Monitor APIs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All examples and instructions use Windows PowerShell (specifically PowerShell 5.1), Windows-specific modules (AzFilesHybrid, Active Directory PowerShell), and Windows command-line tools (Setspn). There are no examples or guidance for performing these tasks from Linux or cross-platform environments, nor is there mention of Linux clients or tools. The documentation assumes the administrator is working from a Windows domain-joined machine and does not address Linux-based management or access scenarios.

Recommendations:

Provide equivalent instructions and examples for Linux environments, including how to join storage accounts to AD DS using cross-platform tools or Azure CLI.
Mention and document any limitations or requirements for Linux administrators, such as whether certain steps must be performed from Windows, and what alternatives exist.
Include examples for mounting Azure file shares from Linux clients using AD DS credentials, if supported.
Reference or link to documentation on managing Azure Files and AD DS integration from non-Windows platforms.
Clarify in prerequisites and throughout the guide which steps are Windows-only and offer Linux-compatible alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation is generally cross-platform, using mostly Bash-style environment variable examples, but there are several signs of Windows bias. Windows tools (such as PowerShell and Export-PfxCertificate) are referenced explicitly, and PowerShell is used for secure variable input without equivalent Linux shell examples. When discussing certificate export, only Windows certificate store and PowerShell guidance are provided. In some sections, Windows-specific patterns are mentioned before or instead of Linux/macOS equivalents.

Recommendations:

Provide Linux/macOS equivalents for all PowerShell examples, especially for secure environment variable input (e.g., using 'read -s' in Bash).
When referencing certificate export, include instructions or links for exporting certificates on Linux/macOS (e.g., using OpenSSL).
Avoid referencing Windows tools (like Export-PfxCertificate) exclusively; always mention cross-platform or platform-specific alternatives.
When discussing environment variables, clarify the syntax for both Bash (Linux/macOS) and PowerShell (Windows), and present them side by side.
Review the order of platform-specific instructions to ensure Linux/macOS are not always secondary or omitted.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows terminology, tools, and workflows. Windows is mentioned first in client OS requirements, and all domain join and permissions management instructions reference Windows tools and concepts (such as Windows ACLs and DACLs), with no equivalent Linux examples or guidance. Troubleshooting links and mounting instructions are Windows-specific, and there is no mention of Linux command-line tools or procedures for mounting or managing Azure file shares with AD DS authentication.

Recommendations:

Provide Linux-specific examples for mounting Azure file shares with AD DS authentication, including recommended distributions and SMB client configurations.
Include instructions or references for managing file/directory-level permissions from Linux clients, such as using setfacl or other Linux ACL tools, and clarify any limitations.
Add troubleshooting guidance for Linux mounting errors, similar to the Windows troubleshooting link provided.
When listing client OS requirements, present Windows and Linux options with equal prominence, or alternate their order.
Reference both Windows and Linux domain-join procedures, or clarify how Linux clients can authenticate to AD DS if domain joining is not applicable.
Where possible, use cross-platform terminology (e.g., 'file permissions' instead of 'Windows ACLs') and clarify which features are Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All client and server requirements, examples, and tooling are Windows-centric. Only Windows operating systems are mentioned as supported clients, and all configuration steps rely on Windows tools such as PowerShell, Active Directory cmdlets, Windows File Explorer, Group Policy, and icacls. There are no Linux or cross-platform instructions, nor any mention of Linux support or alternatives.

Recommendations:

Clearly state whether Linux clients are supported for this scenario. If not, explicitly mention the limitation.
If Linux is supported, provide equivalent instructions for Linux clients, including required OS versions, configuration steps, and tools (e.g., using kinit, smbclient, or Kerberos utilities on Linux).
Include Linux command-line examples (bash, shell scripts) alongside PowerShell examples where possible.
Reference Linux tools (such as setfacl, getfacl, or Samba utilities) for managing file and directory permissions, if applicable.
If certain features (like Group Policy or Windows File Explorer) are not available on Linux, suggest alternative approaches or clarify the limitations.
Add a parity table or section summarizing which steps/tools are Windows-only and which are cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways: Windows and PowerShell tools are referenced and exemplified more frequently and in greater detail than Linux equivalents, especially for client-side configuration. Windows-specific instructions (e.g., registry edits, PowerShell commands) are provided for enabling SMB Multichannel and configuring encryption, with no comparable Linux guidance. Windows terminology and features are referenced first or exclusively in scenarios, security, and limitations sections. Linux client configuration, troubleshooting, and advanced usage are notably absent or deferred to separate documentation.

Recommendations:

Add Linux-specific examples for configuring SMB Multichannel and advanced SMB security settings, including relevant mount options and client configuration steps.
Where PowerShell or Windows registry edits are shown, provide equivalent Linux commands (e.g., using smb.conf, mount.cifs options, or relevant Linux tools) or explicitly state if a feature is not configurable on Linux.
Balance scenario descriptions to include Linux-based applications and workloads, not just Windows-based ones.
When referencing client configuration (such as enabling specific encryption ciphers), include Linux (and macOS) instructions alongside Windows/PowerShell.
In limitations and feature support sections, clarify which features or settings have different behaviors or requirements on Linux clients.
Ensure that cross-platform parity is maintained in all code tabs and example sections, not just in the 'Next steps' links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a moderate Windows bias. Windows tools and patterns (such as Azure File Sync, PowerShell, and Active Directory) are mentioned more frequently and are often introduced before their Linux equivalents. The 'Next steps' section lists Windows mounting instructions before Linux and macOS. PowerShell is highlighted as a primary scripting tool, while Linux-specific tools or scripting examples are not mentioned. There are also references to Windows-centric features (e.g., Azure File Sync, FSLogix, AD DS integration) without equivalent Linux-focused alternatives or guidance.

Recommendations:

Ensure Linux and macOS instructions/examples are presented alongside or before Windows examples, especially in introductory and 'Next steps' sections.
Include Linux-native tooling (e.g., shell scripts, mount.cifs, mount.nfs) and scripting examples in the 'Scripting and tooling' section, not just PowerShell and Azure CLI.
Highlight Linux-compatible features and workflows (such as NFS support, Linux authentication options) with equal detail as Windows features like Azure File Sync and AD DS.
Provide Linux-focused use cases and video resources, similar to those provided for Windows (e.g., FSLogix).
Mention cross-platform management tools and clarify when a feature is Windows-only or has Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently referencing Windows concepts (such as Windows ACLs), recommending Windows-based patterns (Active Directory, Windows ACLs), and providing PowerShell examples. There is no mention of Linux/Unix equivalents for file-level permissions, nor guidance for users managing Azure Files from Linux clients. The documentation assumes a Windows-centric environment for both identity and access management.

Recommendations:

Include explicit guidance for Linux clients, such as how to mount and access Azure Files from Linux using SMB or NFS (where supported), and how permissions are handled in those scenarios.
Discuss the limitations or differences in file-level permission enforcement when accessing Azure Files from Linux systems, and provide best practices for Linux administrators.
Provide CLI and scripting examples that are platform-agnostic or include bash/shell scripts where possible, not just PowerShell.
Clarify whether and how Linux-based identity providers (such as LDAP or Kerberos on Linux) can integrate with Azure Files, or explicitly state if such scenarios are unsupported.
Balance references to Windows ACLs with explanations of how access control works (or does not work) for non-Windows clients.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias. Migration tools and examples are predominantly Windows-centric, with extensive mention of Windows Server, RoboCopy, Azure File Sync, and NTFS/ACLs. Linux is only briefly mentioned, with no detailed migration guides or examples provided for Linux users. The recommended tools and migration paths are almost exclusively tailored for Windows environments, and Windows terminology (e.g., NTFS permissions, SIDs, DACLs) is used throughout without Linux equivalents.

Recommendations:

Provide equivalent Linux migration examples and guides, especially for common scenarios such as migrating from Linux SMB servers or NAS devices using Linux.
Include Linux-native tools (e.g., rsync, cifs-utils, smbclient) in the migration toolbox, and discuss their capabilities and limitations with respect to Azure file shares.
Balance the order of presentation so that Linux and Windows options are given equal prominence in tables and tool recommendations.
Explain file permission and metadata mapping for Linux (e.g., POSIX ACLs, ownership, timestamps) and how they are preserved or mapped in Azure file shares.
Add detailed step-by-step migration guides for Linux environments, similar to those provided for Windows (e.g., mounting Azure file shares on Linux, copying data, preserving metadata).
Clarify limitations or special considerations for Linux users, such as differences in metadata support or authentication methods.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias throughout the migration process. All file transfer examples and instructions rely exclusively on Windows Server and the RoboCopy tool, with no mention of Linux-based alternatives or guidance for environments where Windows is not available. Windows-specific tools, patterns, and terminology (e.g., mounting shares on Windows, using DFS-N, Windows Server QoS, and RoboCopy switches) are used exclusively or introduced before any Linux equivalents (which are absent). There are no examples or instructions for performing the migration from Linux systems, nor are Linux tools (such as rsync or smbclient) discussed.

Recommendations:

Add parallel Linux-based migration instructions, including examples using rsync, smbclient, or other common Linux tools for copying data to DataBox SMB shares and Azure file shares.
Include guidance on mounting Azure file shares from Linux (e.g., using cifs-utils or NFS where supported), with step-by-step commands.
Provide sample scripts or command lines for Linux environments to perform both the initial bulk copy and the incremental/catch-up copy phases.
Discuss authentication and authorization considerations for Linux clients, including integration with Kerberos, AD, or local credentials.
Reference troubleshooting steps and performance tuning tips relevant to Linux-based file copy tools.
Ensure that all phases (planning, copying, cut-over, troubleshooting) include Linux parity, not just Windows-centric approaches.
Where Windows-specific features (like DFS-N or NTFS ACLs) are discussed, note Linux equivalents or workarounds, or clearly state any limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric concepts and tools (e.g., SMB/CIFS, Azure Files, DFS, DNS server reconfiguration), referencing Windows-oriented network monitoring tools, and omitting explicit Linux/NFS examples or Linux command-line instructions. There is little to no mention of Linux-specific migration scenarios, tools, or best practices, and the documentation assumes familiarity with Windows patterns.

Recommendations:

Add explicit Linux/NFS migration examples, including how to add NFS shares as sources and destinations, and any protocol-specific considerations.
Include Linux command-line examples for mounting Azure Files or Blob Storage (e.g., using cifs-utils, blobfuse, or azcopy on Linux).
Mention Linux/Unix equivalents for network and performance monitoring (e.g., iperf, nload, iftop, netstat, atop) alongside Windows/third-party tools.
Describe how to update Linux mount points (e.g., /etc/fstab) and NFS exports for cutover, not just DNS/DFS changes.
Clarify any differences in permissions, ACLs, or symbolic link handling between Windows (SMB) and Linux (NFS) environments.
Ensure screenshots and workflow steps are platform-agnostic or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. It exclusively uses RoboCopy, a Windows-only tool, for migration and provides only Windows-based instructions and examples. Linux is mentioned as a possible source, but no Linux-native migration tools or examples are provided. The process assumes the use of a Windows machine as an intermediary, and all mounting and authentication guidance is Windows-centric. There are no Linux or cross-platform alternatives or parity in the migration workflow.

Recommendations:

Provide equivalent Linux-based migration instructions using tools such as rsync, smbclient, or AzCopy (which is cross-platform).
Include Linux command-line examples for mounting SMB shares and performing file transfers.
Explicitly describe migration routes that use Linux servers as the intermediary, not just Windows.
Mention and compare Linux-native tools for SMB file copying, and discuss their pros/cons relative to RoboCopy.
Ensure that all troubleshooting and optimization advice includes Linux scenarios and tools.
Add a section or callout for cross-platform or Linux-only environments, outlining supported migration patterns.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a moderate Windows bias. Windows operating systems and tools are mentioned first or exclusively in several sections, such as the recommended OS list, authentication methods, and networking strategies. Azure File Sync, a Windows Server-only solution, is highlighted as the primary caching option. PowerShell and Windows-centric management patterns are referenced, while Linux-specific examples and tools are either missing or mentioned secondarily. There is a lack of parity in practical Linux guidance, especially regarding mounting, authentication, and backup/restore workflows.

Recommendations:

Ensure Linux and macOS are mentioned alongside Windows in all relevant sections, especially in OS recommendations and protocol support.
Provide explicit Linux (and macOS, if applicable) examples for mounting, authentication, and backup/restore workflows, not just references to Windows tools or PowerShell.
When discussing Azure File Sync or other Windows-only features, clearly state the lack of Linux support and suggest alternative approaches for Linux environments.
Balance the order of presentation so that Linux and Windows are given equal prominence (e.g., alternate which OS is listed first, or use alphabetical order).
Include references to Linux-native tools (such as mount.cifs, mount.nfs, or relevant CLI commands) and provide links to Linux-specific documentation where available.
Where possible, add practical Linux-focused scenarios or case studies to demonstrate parity and applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on Windows-based migration scenarios, particularly using SMB/CIFS shares from Windows file servers as the source. There are no examples or guidance for Linux-based file servers (e.g., NFS shares), nor are Linux tools or workflows mentioned. Additionally, when discussing network monitoring tools, only Windows-centric or commercial solutions are listed, with no mention of common Linux/open-source alternatives.

Recommendations:

Add parallel examples for migrating from Linux file servers, such as using NFS shares as the source storage.
Include instructions and screenshots for configuring Miria to connect to Linux/NFS sources.
List open-source and Linux-friendly network monitoring tools (e.g., iftop, nload, vnStat, Netdata) alongside the commercial/Windows options.
Use neutral language and ordering (e.g., 'Windows or Linux file servers') rather than defaulting to Windows-first.
Clarify platform support and provide links or references to documentation for Linux deployments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows Server as the source system, explicitly requiring Windows Server 2012 R2 or newer for Azure File Sync installation and migration. All migration steps, examples, and tooling (notably Robocopy) are Windows-specific, with no mention of Linux-based servers, Linux tools, or cross-platform alternatives. There are no examples or guidance for Linux users, and the documentation assumes a Windows-centric environment throughout.

Recommendations:

Add a section or callout clarifying support (or lack thereof) for Linux-based file servers and migration scenarios.
If Azure File Sync does not support Linux, provide clear guidance and alternative migration paths for Linux/NAS users, linking to relevant documentation.
Where file copy tools are discussed (e.g., Robocopy), mention Linux equivalents (such as rsync or scp) and explain their applicability or limitations in this context.
Include a migration matrix or overview table at the start, indicating which OS/platforms are supported for each migration path.
If possible, provide Linux-based examples or scripts for scenarios where Linux servers are involved, or explicitly state that this guide is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias, particularly in the Azure File Sync sections. It exclusively references Windows Server as the supported platform for the Azure File Sync agent, with no mention of Linux support or alternatives. Performance guidance and metrics are framed entirely around Windows Server environments, and there are no Linux-based examples or considerations for Linux file servers. Additionally, the documentation refers to Windows-specific tools and patterns (e.g., Windows Server, Windows disk configuration) without providing Linux equivalents or guidance for cross-platform scenarios.

Recommendations:

Explicitly state platform support for Azure File Sync, including whether Linux is supported or not. If not, provide a rationale or roadmap.
If Azure File Sync is Windows-only, consider mentioning alternative synchronization or backup solutions for Linux clients.
Include performance considerations and configuration guidance for Linux SMB/NFS clients where relevant, especially in sections discussing client behavior and network performance.
Provide parity in examples and recommendations for both Windows and Linux environments throughout the documentation.
Reference Linux tools and best practices for managing Azure Files (e.g., using mount.cifs, NFS utilities, or rsync for sync scenarios) alongside Windows tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. All examples, tools, and instructions are centered around Windows environments, such as using Active Directory Domains and Trusts console, PowerShell commands, icacls, net use, and klist from a Windows command prompt. There are no examples or guidance for Linux clients or administrators, nor are Linux-compatible tools or workflows mentioned. The documentation assumes a Windows-centric approach throughout.

Recommendations:

Include equivalent instructions and examples for Linux clients, such as how to mount Azure Files SMB shares from Linux using cifs-utils and how to handle Kerberos authentication from Linux.
Mention and provide examples for Linux tools (e.g., smbclient, mount.cifs, setfacl) where applicable, alongside Windows tools like icacls and net use.
Add PowerShell and non-PowerShell alternatives for administrative tasks, and clarify which steps are Windows-only.
Explicitly state platform limitations (e.g., if certain features are only available on Windows) and provide guidance or workarounds for Linux environments.
Reorganize sections to present both Windows and Linux approaches in parallel, or clearly label Windows-specific instructions.
Provide troubleshooting steps and validation commands for Linux clients (e.g., using klist, smbclient, or Kerberos tools on Linux).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: PowerShell is the primary tool shown for DNS validation, with only a brief mention of nslookup as an alternative; Windows-specific technologies (e.g., SMB over QUIC, Azure File Sync on Windows Server) are discussed in detail, while Linux equivalents or alternatives are not covered or are only briefly referenced. Example commands and configuration guidance are Windows-centric, and Linux guidance is either missing or less prominent.

Recommendations:

Provide Linux-specific command examples alongside PowerShell, such as using dig or nslookup for DNS validation.
Include Linux mounting and configuration instructions for both SMB and NFS scenarios, with equal detail as Windows.
Discuss Linux-compatible tools or methods for caching Azure Files (e.g., third-party sync tools or NFS-based solutions) if Azure File Sync is Windows-only.
When referencing features like SMB over QUIC, clarify Linux support status and suggest alternatives for Linux environments.
Ensure that links to configuration guides for both Windows and Linux are equally prominent and included wherever relevant.
Avoid assuming Windows as the default client environment; use neutral language and structure examples for both platforms in parallel.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ windows_heavy_examples

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways: it repeatedly references Windows-specific technologies (such as VSS and Azure File Sync for Windows file servers), describes features in terms of Windows behaviors (e.g., 'Windows properties dialog'), and provides analogies or explanations primarily from a Windows perspective. There are no Linux-specific examples, tools, or workflows mentioned, and Linux/NFS support is only referenced in passing within tables. The documentation assumes familiarity with Windows concepts and omits equivalent Linux/NFS guidance, especially in sections about snapshots, file sync, and mounting shares.

Recommendations:

Add Linux/NFS examples and explanations alongside Windows ones, especially in sections discussing mounting, snapshots, and file sync.
When referencing Windows-specific tools (e.g., VSS, Windows properties dialog), provide Linux equivalents (e.g., LVM snapshots, du/ls commands, or Linux file property dialogs).
Include information about Azure File Sync alternatives or guidance for Linux file servers, or explicitly state if such features are unavailable.
Balance the narrative by describing behaviors and terminology from both Windows and Linux perspectives (e.g., how logical/physical size is reported in Linux tools).
Ensure that tables and feature lists highlight Linux/NFS support with equal prominence and detail as Windows/SMB.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-centric bias by focusing exclusively on Windows-based virtual desktop workloads, tools, and patterns (such as FSLogix, roaming user profiles, folder redirection, and App Attach). There are no examples, guidance, or references for Linux virtual desktop environments, Linux authentication mechanisms, or Linux-compatible tools. All terminology, scenarios, and recommendations assume a Windows ecosystem.

Recommendations:

Include explicit guidance and examples for Linux-based virtual desktop workloads, such as using Azure Files with Linux VDI solutions (e.g., Citrix/VMWare Horizon with Linux session hosts).
Provide authentication and authorization instructions relevant to Linux clients (e.g., using SMB with Kerberos from Linux, or integration with Linux identity providers).
Add examples of mounting Azure Files shares from Linux (e.g., using mount.cifs or SMB clients on Linux), including sample commands and troubleshooting tips.
Mention Linux profile/container management solutions if applicable, or clarify the Windows-only scope early in the document.
If the guidance is intentionally Windows-only, clearly state this at the beginning to set expectations for cross-platform readers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias, particularly in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all reference tabs or instructions that prioritize Windows-specific environments (e.g., 'environment-variable-windows') and, in the Java example, explicitly mention 'powershell' as a tab. There is no mention of Linux or macOS equivalents, nor are there examples or instructions tailored for non-Windows platforms.

Recommendations:

Add Linux and macOS-specific tabs or instructions alongside Windows in all quickstart links.
Ensure that environment variable setup and CLI instructions are provided for bash/zsh (Linux/macOS) as well as PowerShell (Windows).
Avoid defaulting to Windows or PowerShell examples; present cross-platform options equally or default to platform-agnostic instructions where possible.
Explicitly mention that Azure Queue Storage is accessible from all major operating systems, and provide parity in tooling and setup guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example, and output samples are shown in Windows format first. Windows-specific tools and terminology (e.g., PowerShell, Windows output) are emphasized, while Linux/macOS equivalents are less prominent or absent. There is a lack of explicit Linux/macOS command output examples, and the documentation assumes familiarity with Windows-centric patterns.

Recommendations:

Provide explicit Linux and macOS command output examples alongside Windows output, especially for commands like nslookup.
Include Bash or shell scripting examples where PowerShell is used, or at least reference equivalent Linux/macOS commands.
Avoid presenting Windows tools or outputs first; instead, present cross-platform examples in parallel or alternate order.
Clarify when instructions or outputs are platform-specific, and provide guidance for users on other operating systems.
Where possible, use neutral language and tools (e.g., Azure CLI, which is cross-platform) as the primary example, and supplement with platform-specific instructions as needed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (e.g., Network Monitor), omits Linux equivalents, and in the '.NET configuration' section, focuses on .NET Framework (historically Windows-centric) before mentioning other languages. There are no explicit Linux or cross-platform command-line examples, and PowerShell/Azure CLI are only mentioned in passing without parity in example usage.

Recommendations:

When mentioning diagnostic tools like Network Monitor, also mention cross-platform or Linux alternatives such as tcpdump or Wireshark (which is cross-platform).
Provide example commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) when discussing client libraries and tools.
In sections focused on .NET Framework, clarify that .NET Core/.NET 5+ are cross-platform and provide configuration guidance for Linux environments where applicable.
Wherever possible, avoid assuming the reader is on Windows; use neutral or cross-platform language and examples.
Explicitly mention and link to documentation for Linux/macOS users when discussing setup, troubleshooting, or performance tuning.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. While it claims cross-platform compatibility and recommends Visual Studio Code and .NET Core SDK (both cross-platform), all command-line examples and output use Windows-style paths (e.g., C:\Tutorials), and references to console windows mention 'cmd' and 'PowerShell' before 'Azure CLI'. There are no explicit Linux or macOS terminal examples, and no mention of Linux-specific shell environments (e.g., bash, zsh). The output samples and instructions assume a Windows file system and command prompt experience.

Recommendations:

Include Linux/macOS terminal examples alongside Windows ones, using POSIX-style paths (e.g., ~/Tutorials) and bash/zsh syntax where appropriate.
When referencing console windows, mention Linux/macOS terminals (e.g., 'Terminal', 'bash', 'zsh') equally or before Windows-specific shells.
Provide example output using Linux/macOS file paths and prompt styles (e.g., user@host:~/Tutorials$) in addition to Windows output.
Avoid using only Windows-style paths in code/output snippets; use environment-agnostic or dual examples.
Explicitly state that all commands work on Windows, Linux, and macOS, and provide troubleshooting tips for common cross-platform issues (e.g., case sensitivity, path separators).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed step-by-step examples for using the Azure portal and Azure PowerShell to add and test role assignment conditions for Azure Queue Storage. However, it does not include any examples or guidance for Linux users, such as using Azure CLI (which is cross-platform) or shell scripting. All command-line examples are exclusively in PowerShell, a tool most commonly associated with Windows environments, and there is no mention of Bash, Azure CLI, or other Linux-native tools.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the steps can be performed on Linux and macOS using Azure CLI, and provide guidance or links for those platforms.
Where possible, provide Bash or shell script examples alongside PowerShell, especially for testing and automation tasks.
Avoid assuming PowerShell as the default scripting environment; present PowerShell and Azure CLI examples side-by-side or in separate tabs.
Include a note in the prerequisites or introduction clarifying tool support across operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows/Azure portal-centric bias. All configuration and operational steps are described exclusively via the Azure portal GUI, with no mention of command-line approaches (such as Azure CLI, PowerShell, or Bash) or Linux-specific workflows. The tools and monitoring solutions referenced (e.g., SolarWinds, Cisco Network Assistant, WhatsUp Gold) are traditionally Windows-focused, and there are no examples or guidance for Linux administrators or environments. There are no Linux command-line examples, scripts, or references to Linux-native tools for bandwidth measurement, storage configuration, or automation.

Recommendations:

Add parallel instructions for performing all Azure Storage configuration steps using the Azure CLI and/or Azure PowerShell, and explicitly include Bash examples suitable for Linux environments.
Include Linux-native network monitoring and bandwidth assessment tools (such as iftop, nload, vnstat, or iperf) alongside or before Windows-centric tools.
Provide sample scripts or command-line snippets for DobiSync integration and automation in Linux environments.
Explicitly mention Linux support and provide links to Linux documentation or guides where relevant.
Balance the order of tool and example presentation so that Linux and cross-platform options are not secondary to Windows/portal-based workflows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by explicitly referencing 'Windows Proxies' as the primary data mover for SMB/CIFS data, without mentioning Linux-based alternatives or providing parity for Linux/NFS environments. There are no examples or instructions specific to Linux, and the only platform-specific component described is Windows-based, suggesting a Windows-first approach. The lack of Linux/NFS-specific setup guidance or examples further reinforces this bias.

Recommendations:

Include equivalent Linux-based data mover options (e.g., Linux proxies or agents) and describe their deployment and configuration alongside Windows Proxies.
Provide explicit instructions or examples for tiering from NFS shares on Linux servers, not just SMB/CIFS via Windows.
Ensure that any platform-specific terminology (like 'Windows Proxies') is balanced with Linux alternatives, or clarify if such alternatives are not available.
Add screenshots or walkthroughs that show the process from a Linux/NFS environment to Azure Blob, not just generic or Windows-centric flows.
Mention and document any Linux command-line or automation options for managing Komprise tiering, if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently using 'Windows Azure Platform' terminology, referencing 'Windows' in provider selection, and providing only Azure Portal (GUI) instructions with screenshots from a Windows environment. There are no examples or instructions for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST APIs, nor are there references to Linux tools or command-line workflows. The documentation assumes a GUI/Windows-centric workflow throughout.

Recommendations:

Provide equivalent step-by-step instructions for Linux users, including how to create and manage Azure Storage accounts using the Azure CLI (az), Bash scripts, or REST API.
Include command-line examples for credential management and storage configuration that work on both Linux and Windows.
Use neutral terminology such as 'Azure Platform' instead of 'Windows Azure Platform' when referring to cloud provider options.
Add screenshots or terminal outputs from Linux environments where applicable.
Explicitly mention that the procedures are platform-agnostic where possible, or provide separate sections for Windows (GUI/PowerShell) and Linux (CLI/Bash) workflows.
Reference cross-platform tools (e.g., Azure CLI, PowerShell Core) rather than only Windows-specific tools or interfaces.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias, primarily through the mention of Windows-specific tools and environments (e.g., Windows Server, Windows file servers, Windows Shell integration) and by highlighting Windows-centric features (such as NTFS tiering and Windows clustering) without equivalent Linux examples or parity. Some ISV solutions are described as operating specifically on Windows Server, and features like Windows Shell integration are called out, while Linux environments, tools, or integration points are not mentioned or are less visible. There are no explicit Linux command-line or management examples, and Linux-based deployment or management patterns are not discussed.

Recommendations:

For each ISV solution that highlights Windows Server or Windows-specific features, add equivalent information for Linux environments if supported (e.g., Linux-based file servers, Linux clustering, Linux shell integration).
Where features like 'Windows Shell integration' are mentioned, clarify if there are Linux desktop or CLI equivalents, or explicitly state if such features are unavailable on Linux.
If a solution is Windows-only, clearly state this; if Linux is supported, provide parity in feature descriptions and management tooling.
Include Linux-focused deployment, management, and failover patterns/examples where relevant, such as using Linux VMs, Linux clustering, or Linux-native file systems.
Add explicit Linux compatibility notes or examples in tables, especially in the 'Operating Environment' and 'Automatic failover' sections.
Where NTFS or Windows file server is referenced, mention Linux file systems (e.g., ext4, XFS) or NFS server options if supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. It assumes deployment on Windows Server, references NTFS/ReFS file systems, and requires a Windows file server for installation. All setup and configuration steps, screenshots, and features (such as the Windows Explorer shell extension) are Windows-centric. There are no Linux-specific instructions, examples, or screenshots, and no mention of Linux-native deployment, tools, or command-line equivalents.

Recommendations:

Add explicit instructions and examples for deploying Tiger Bridge on Linux-based systems, if supported, including supported file systems (e.g., ext4, XFS) and integration with NFS/SMB exports.
Provide Linux command-line examples (e.g., bash, shell scripts) for installation, configuration, and management, alongside or instead of Windows GUI and PowerShell instructions.
Include screenshots or terminal output from Linux environments to illustrate cross-platform parity.
Clarify in the introduction and prerequisites whether Tiger Bridge can be installed natively on Linux, or only as a gateway to NAS devices, and provide guidance for Linux users accordingly.
Mention Linux-native tools for bandwidth and network monitoring (e.g., iftop, nload, vnStat, Netdata) alongside the Windows/third-party tools listed.
If Linux is not supported for direct Tiger Bridge installation, explicitly state this limitation early in the documentation and provide alternative architectures or partner solutions for Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias: all code examples use PowerShell syntax, Windows-specific tools (such as Connect-AzAccount and New-AzResourceGroupDeployment) are used exclusively, and there are no Bash or Linux shell equivalents provided. The only mention of platform differences is a note that JavaScript UDFs only work on Windows, but no guidance or alternatives are offered for Linux users. This could make it difficult for Linux or macOS users to follow the instructions or adapt them to their environments.

Recommendations:

Provide all command-line examples in both PowerShell and Bash (or generic shell) syntax, especially for npm commands and directory navigation.
Include Azure CLI equivalents for deployment steps (e.g., az login, az deployment group create) alongside PowerShell cmdlets.
Explicitly state platform requirements or limitations at the beginning of the article, and offer alternatives or workarounds for non-Windows users where possible.
Add notes or sections for Linux/macOS users, including any differences in file paths, environment setup, or tool installation.
Where features are Windows-only (e.g., JavaScript UDFs), suggest alternative approaches or clarify the impact for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt, and commands) for all CLI examples, including npm installation and Azure CLI deployment. There are no Linux/macOS shell equivalents, and Windows path separators are used throughout, which may confuse or exclude Linux/macOS users.

Recommendations:

Provide equivalent Bash examples alongside PowerShell, using appropriate path separators (e.g., ./ instead of .\).
Explicitly mention that the commands work cross-platform and clarify any OS-specific differences.
Use platform-agnostic syntax in documentation when possible, or provide tabs/switches for Windows and Linux/macOS instructions.
Add a note about prerequisites or shell environments for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by focusing on Windows-centric deployment and operational patterns. It assumes the use of Active Directory, Windows file servers, and Windows-based tools (e.g., portqryui), and provides detailed steps and screenshots for Windows environments. There is a lack of equivalent Linux/NFS-focused examples, commands, or guidance, and Linux-native tools or patterns are not mentioned or are only referenced in passing.

Recommendations:

Provide parallel Linux/NFS deployment instructions, including how to deploy and configure StorageX on Linux-based systems if supported.
Include examples and screenshots for NFS migrations, not just SMB/Windows/Active Directory scenarios.
Mention and provide usage examples for Linux-native tools (e.g., netcat, ss, iperf, or nmap) for port and bandwidth testing, alongside or instead of Windows tools like portqryui.
Clarify whether StorageX requires Windows for deployment, or if Linux-based deployments are possible, and document any differences.
Ensure that instructions for creating service accounts and setting permissions include Linux/NFS equivalents (e.g., export rules, root squash, POSIX permissions), not just Active Directory/Windows group memberships.
Balance the order of presentation so that NFS/Linux scenarios are given equal prominence to SMB/Windows ones, rather than always following or being secondary.
Add troubleshooting and support guidance for Linux/NFS environments, not just Windows/Active Directory.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes how to configure managed identities and permissions using the Azure portal, which is a graphical tool most commonly used on Windows. There are no examples or instructions for performing these tasks using cross-platform command-line tools such as Azure CLI, PowerShell, or REST APIs. No Linux-specific or CLI-based workflows are mentioned, and the documentation assumes the user is interacting with the Azure portal UI, which may not be the preferred or available method for Linux users or those automating deployments.

Recommendations:

Add equivalent instructions for configuring managed identities and role assignments using the Azure CLI, which is cross-platform and widely used on Linux.
Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are given equal or higher prominence.
Provide REST API examples or references for users who need to automate these tasks in a platform-agnostic way.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows using the CLI or API, not just the Azure portal.
Where screenshots are used, consider including CLI output or code snippets as alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows/Powershell bias. All command-line examples, including installation, project build, autoscale configuration, Azure login, and deployment, are shown exclusively using Powershell syntax and cmdlets (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment). There are no Bash, Linux shell, or cross-platform CLI equivalents provided, despite the fact that the Stream Analytics CI/CD tool is installed via npm and could be used on Linux/macOS. The documentation assumes a Windows environment for Azure authentication and deployment, omitting az CLI or Bash alternatives.

Recommendations:

Provide equivalent Bash/Linux/macOS shell commands for all steps, especially for npm installation, project build, and running the CI/CD tool.
Include Azure CLI (az) commands for authentication and deployment, as these are cross-platform and commonly used on Linux/macOS.
Explicitly state that the CI/CD tool and deployment steps can be performed on Linux/macOS, and highlight any platform-specific considerations.
Reorder or parallelize examples so that Linux/Bash and Windows/Powershell instructions are given equal prominence.
Add a section or callout for Linux/macOS users, clarifying any differences in file paths, environment setup, or command syntax.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools (e.g., WireShark, NetMon), focusing on .NET Framework (primarily used on Windows), and mentioning PowerShell before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and configuration/code snippets are .NET/C#-centric, with no parity for Linux or non-Windows environments.

Recommendations:

When mentioning diagnostic tools, include popular Linux alternatives (e.g., tcpdump, Wireshark for Linux, or iperf) alongside Windows tools like NetMon.
Provide code/configuration examples for other languages and platforms (e.g., Python, Java, Node.js) and reference their connection/thread pool management.
When referencing Azure CLI and PowerShell, mention Azure CLI first or equally, as it is cross-platform, and provide example commands for both.
Explicitly state that the guidance applies to both Windows and Linux clients where relevant, and highlight any OS-specific considerations.
Where .NET Framework is discussed, also mention .NET Core/.NET 5+ and clarify cross-platform support.
Add a section or callouts for Linux/macOS users, especially in areas discussing client-side configuration or troubleshooting.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing PowerShell for command-line instructions, linking only to Windows-specific Azure CLI installation guides, and omitting any mention or examples for Linux or macOS environments. All screenshots and terminal instructions assume a Windows/PowerShell context, with no alternatives or parity for other platforms.

Recommendations:

Provide equivalent command-line instructions for Linux and macOS users, using Bash or sh syntax where appropriate.
Include links to Azure CLI installation guides for Linux and macOS alongside the Windows link.
Add screenshots or notes indicating how to open the terminal and run commands in VS Code on Linux/macOS.
Use platform-agnostic language (e.g., 'open a terminal' instead of 'open PowerShell') and clarify that the Azure CLI works across operating systems.
Where referencing PowerShell, also show the Bash equivalent, especially for commands that may differ in syntax or environment.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page is generally cross-platform as it focuses on Visual Studio Code, which is available on both Windows and Linux. However, there is a notable Windows bias in the 'Limitations' section, where it states that running jobs locally with JavaScript functions is only supported on Windows. No Linux-specific instructions, troubleshooting, or parity notes are provided elsewhere. There are no Linux or macOS examples, nor are there alternative workflows or caveats for non-Windows users.

Recommendations:

Explicitly state which features are supported on Linux and macOS, not just Windows.
Provide alternative instructions or workarounds for Linux/macOS users where features are Windows-only.
Add Linux/macOS-specific troubleshooting tips or known issues if certain features are unavailable.
Include parity tables or notes to clarify which features are cross-platform and which are not.
If possible, prioritize cross-platform support for local JavaScript function execution or provide a roadmap for Linux/macOS support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, with no equivalent Azure CLI or REST API examples. It explicitly states that role assignment must be done via Azure PowerShell, which is primarily a Windows-centric tool, and does not mention or provide guidance for Linux or cross-platform users. There are no Bash or Linux shell examples, and the documentation assumes access to PowerShell.

Recommendations:

Provide equivalent Azure CLI (az) commands for role assignment, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include REST API or ARM template examples for users who may want to automate the process in a platform-agnostic way.
Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, if PowerShell is truly required, and provide installation instructions or links.
Add a note or section addressing Linux/macOS users, ensuring parity in instructions and tooling.
Where possible, avoid language that implies PowerShell is the only supported method, unless it is a technical limitation, and clarify if so.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on using Visual Studio for local debugging of Azure Stream Analytics queries, which is a Windows-centric tool. There are no examples or instructions for Linux users, nor are any cross-platform alternatives (such as Visual Studio Code or CLI-based workflows) mentioned. All steps, screenshots, and references assume the use of Visual Studio on Windows, and there is no guidance for achieving similar functionality on Linux or macOS.

Recommendations:

Provide equivalent instructions for Linux users, such as using Visual Studio Code with relevant extensions or Azure CLI for local testing and debugging.
Explicitly mention platform requirements and, if the feature is Windows-only, suggest alternative workflows for non-Windows users.
Include cross-platform examples and screenshots, or clarify which steps are not available on Linux/macOS.
Reference any available tools or SDKs that support local debugging on Linux, or provide a roadmap for such support if it does not exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references PowerShell specifically in the 'Next steps' section, suggesting it as the primary tool for monitoring and managing Azure Stream Analytics jobs. There are no examples or mentions of Linux-native tools, Bash, or cross-platform alternatives, which may make Linux users feel unsupported.

Recommendations:

Include equivalent Bash or Azure CLI examples and links alongside PowerShell references.
Explicitly mention that Azure Stream Analytics management can be performed from Linux, macOS, and Windows, and provide cross-platform instructions.
Balance the 'Next steps' section by linking to documentation for both PowerShell and Azure CLI/Bash management.
Where possible, use neutral language (e.g., 'use your preferred shell or scripting environment') and provide code snippets for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Visual Studio (a Windows-only tool) is mentioned in the commented-out sections and in the 'Next steps' links, sometimes before Visual Studio Code (which is cross-platform). The feature table for JavaScript UDF and UDA explicitly states 'Windows only' for Visual Studio Code, without further explanation or Linux alternatives. There are no Linux-specific examples, troubleshooting, or parity notes, and the documentation does not highlight or address limitations/workarounds for non-Windows users.

Recommendations:

Ensure all feature tables and descriptions clarify platform limitations, and provide workarounds or alternatives for Linux/macOS users where possible.
In 'Next steps' and throughout the documentation, list cross-platform tools (like Visual Studio Code) before Windows-only tools (like Visual Studio) to avoid Windows-first bias.
Where features are Windows-only (e.g., JavaScript UDF/UDA), explicitly state the limitation and, if possible, provide a roadmap or alternatives for Linux/macOS users.
Add Linux/macOS-specific examples, troubleshooting tips, or notes to improve parity and inclusivity.
Consider a dedicated section summarizing platform support and limitations for all major features.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell examples for Azure CLI commands, referencing Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem), and instructing users to configure Azure CLI locally with PowerShell. There are no equivalent Linux/macOS command-line examples, nor are Linux file path conventions or shell environments mentioned.

Recommendations:

Provide Azure CLI command examples using Bash (or generic shell) syntax alongside PowerShell, including Linux/macOS file path examples (e.g., /home/user/certificatefile.pem).
Clarify that Azure CLI can be used on Windows, Linux, and macOS, and provide links or instructions for installing and using Azure CLI on non-Windows platforms.
Avoid language that assumes PowerShell as the default shell; instead, offer both PowerShell and Bash command blocks where appropriate.
Include notes or callouts for any platform-specific considerations, such as file path formats or shell differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally presents Windows-specific concepts (such as Windows Registry and environment variables) before Linux equivalents, and Windows examples (e.g., file paths, use of %winDir%) are described in more detail. Windows terminology and tools (like the Registry) are mentioned without Linux parallels, and Windows file tracking is described before Linux file tracking. However, Linux is included in most sections, and Linux-specific instructions are present.

Recommendations:

Alternate the order of Windows and Linux examples/tabs so that Linux is sometimes presented first.
When referencing Windows-specific tools (like the Registry), provide Linux equivalents or explicitly state when a feature is Windows-only.
Ensure that Linux examples (such as file paths or environment variables) are as detailed as Windows examples.
Where possible, provide parity in screenshots and step-by-step instructions for both Windows and Linux.
Review terminology to ensure that Windows concepts are not assumed as the default (e.g., avoid referencing environment variables only in Windows context).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking to the Windows-specific Azure CLI installation instructions in both the pre-requisites and configuration steps, without mentioning or linking to Linux or macOS equivalents. There are no Linux-specific examples or guidance, and the documentation does not acknowledge cross-platform usage for the Azure CLI.

Recommendations:

Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link, or use a generic cross-platform link.
Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS.
Include a note or section about verifying Azure CLI installation on Linux/macOS.
Ensure screenshots and instructions are not Windows-specific, or provide Linux/macOS alternatives where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias in the prerequisites section, where the Node.js installation is suggested via the MSI installer (a Windows-specific method), and the link to creating a Communication Services resource uses a 'platform-azp' pivot with a 'windows' tab by default. However, the rest of the guide uses cross-platform tools (Node.js, npm, Azure CLI) and generic terminal commands, making it largely platform-agnostic.

Recommendations:

In the prerequisites, mention cross-platform installation methods for Node.js (e.g., using package managers like apt, yum, brew, or direct downloads for macOS/Linux) alongside the MSI installer.
Ensure that links to Azure portal/resource creation do not default to Windows-specific pivots or tabs; provide clear parity for Linux and macOS users.
Explicitly state that all terminal/console commands work on Windows, Linux, and macOS, and clarify any platform-specific differences if they exist.
Wherever a tool or pattern is mentioned (such as 'command window'), use neutral terms like 'terminal' or 'command-line interface'.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on configuration steps through the Azure CycleCloud web portal, which is a GUI-based workflow commonly associated with Windows environments. There are no command-line examples or instructions for Linux users, nor are Linux-native tools or patterns (such as editing configuration files via SSH or using Linux shell commands) mentioned. This may disadvantage users who prefer or require Linux-based workflows.

Recommendations:

Add equivalent Linux command-line instructions for configuring Open OnDemand with CycleCloud, such as using SSH to access the VM and editing configuration files directly.
Include examples of how to perform the same configuration steps using Linux shell commands or scripts.
Mention Linux-native tools and workflows alongside the web portal method, ensuring parity for users who operate primarily in Linux environments.
Explicitly state that the web portal is cross-platform, if applicable, and clarify any OS-specific requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial demonstrates a Windows bias by exclusively deploying and testing with Windows Server virtual machines and using Remote Desktop Protocol (RDP) and Internet Explorer for validation. There are no examples or instructions for deploying Linux servers, using SSH, or testing with Linux-native tools. All server deployment and connectivity testing steps assume a Windows environment.

Recommendations:

Include parallel instructions for deploying Linux virtual machines (e.g., Ubuntu Server) alongside Windows Server.
Provide examples for connecting to Linux VMs using SSH, and for testing firewall rules with Linux-native tools (e.g., curl, wget, or a Linux browser).
Demonstrate how to test application and network rules from a Linux VM, such as using SSH to connect between VMs or using command-line tools to access allowed/blocked FQDNs.
Mention both RDP (for Windows) and SSH (for Linux) in firewall rule creation and testing sections.
Use neutral language when referring to operating systems, and avoid assuming the user will always deploy Windows workloads.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation claims support for both Windows and Linux, but all examples, instructions, and referenced scripts are generic or implicitly Windows-focused. There are no explicit Linux-specific instructions, examples, or troubleshooting notes. The prerequisites and installation steps do not mention Linux-specific commands, package managers, or differences, and the only mention of OS support is in the context of deprecation, with Windows listed before Linux.

Recommendations:

Add explicit Linux installation instructions, including package manager commands (e.g., apt, yum, zypper) for installing the Azure Monitor Agent and Dependency Agent.
Provide Linux-specific examples for running scripts, managing services, and troubleshooting common issues.
Include a section or notes highlighting any differences in migration steps or agent behavior between Windows and Linux.
Ensure that all references to OSes alternate or list Linux first in some cases to avoid 'windows_first' ordering.
Reference Linux tools (e.g., systemctl, journalctl, log file locations) where relevant, alongside or before Windows tools.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively provides .NET (C#) code examples, which are most commonly used on Windows and with Windows-centric tooling. There are no examples or references for Linux users, such as using Azure CLI, REST API, or SDKs commonly used on Linux (e.g., Python, Node.js). The use of Console.WriteLine and .NET SDKs further reinforces a Windows-first approach.

Recommendations:

Add equivalent examples using Azure CLI commands to update Notification Hub FCMv1 credentials.
Provide code samples in cross-platform languages such as Python or Node.js, which are widely used on Linux.
Include REST API example requests for updating FCMv1 credentials, which can be executed from any platform.
Explicitly mention that the .NET SDK can be used on Linux and provide instructions for setting up the environment on Linux, if applicable.
Ensure that any tooling or setup steps are not exclusive to Windows (e.g., avoid referencing only Visual Studio or Windows-specific authentication flows).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides Azure CLI examples and does not mention or provide examples for Linux or macOS environments, nor does it address platform-specific considerations. There is an implicit Windows bias in the troubleshooting workflow (e.g., opening a Microsoft support ticket, referencing Azure CLI without clarifying cross-platform compatibility), and no mention of Linux-native tools or shell environments. The documentation assumes the user is familiar with Azure CLI, which is available cross-platform, but does not explicitly demonstrate or acknowledge usage on Linux or macOS, nor does it provide Bash or shell script examples.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example commands in both Windows (cmd/PowerShell) and Linux/macOS (Bash/zsh) shell formats where relevant.
Include notes or sections on installing and using Azure CLI on Linux and macOS, with links to official installation guides.
If any output handling (such as downloading blobs or parsing JSON) is required, provide examples using Linux-native tools (e.g., curl, jq, wget) in addition to any Windows tools.
Clarify that the troubleshooting steps and commands are platform-agnostic, or call out any platform-specific differences if they exist.
Add troubleshooting tips or common issues for Linux/macOS users, such as permissions, environment variables, or shell syntax differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy_examples

Summary:

The documentation page demonstrates a bias toward Windows platforms by consistently presenting Windows/Windows Phone notification examples first and in greater detail. The initial 'Get started tutorial' link and most code samples focus on Windows (WNS, MPNS) payloads, with screenshots and explanations centered around Windows notification headers and outcomes. Linux or cross-platform command-line usage, tools, or deployment scenarios are not discussed, and there is no mention of Linux-specific considerations or parity in the workflow.

Recommendations:

Reorder examples to alternate or rotate the platform order, sometimes showing iOS or Android first.
Include explicit instructions or notes for running the Python code on Linux and macOS, such as environment setup, dependencies, and any OS-specific caveats.
Add screenshots or logs from non-Windows platforms to illustrate parity in debugging and outcomes.
Provide links to platform-agnostic or Linux/macOS-specific tutorials, not just Windows-centric ones.
Ensure that all references to 'Get started' or other tutorials are available for multiple platforms, not only Windows.
Mention any differences (or confirm the lack thereof) in using Notification Hubs from Linux-based servers or CI/CD pipelines.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides Azure CLI examples, which are cross-platform, but it lacks any mention of Linux-specific considerations or examples. There is no explicit Windows bias in terms of PowerShell or Windows-only tools, but the absence of any Linux shell (bash) examples or notes about Linux environments may implicitly favor Windows users, especially since Azure documentation often defaults to Windows-first perspectives.

Recommendations:

Explicitly state that the Azure CLI commands work on both Windows and Linux, and provide example shell environments (e.g., Bash for Linux, Command Prompt/PowerShell for Windows) where appropriate.
Include notes or troubleshooting tips relevant to Linux users, such as file permission considerations or environment variable handling.
If there are any platform-specific differences in command usage or output, document them clearly.
Consider providing example commands in both Bash and PowerShell syntax if relevant, or clarify that the commands are identical across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Azure and Microsoft Entra ID integration, with all examples and references centered on Azure tools, modules, and patterns. There are no explicit examples or instructions for Linux environments or non-Windows tooling, and the documentation does not mention or provide parity for Linux-specific workflows or considerations.

Recommendations:

Include explicit examples and instructions for Linux environments, such as command-line usage on Bash or Linux terminals.
Mention cross-platform compatibility of tools like Terraform, OCI CLI, and Azure CLI, and provide installation or usage notes for Linux.
Add references or links to Linux-specific documentation for installing and configuring dependencies.
Ensure that any scripts or code snippets are shown in both Windows (PowerShell/Command Prompt) and Linux (Bash) formats where applicable.
Highlight any differences or considerations when using the modules or templates on Linux versus Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal, a Microsoft-centric (and thus Windows-associated) tool, without mentioning or providing alternatives for Linux users or command-line options. There are no examples or instructions for Linux environments or cross-platform command-line tools.

Recommendations:

Include instructions for using cross-platform tools such as Azure CLI or PowerShell Core (which runs on Linux) to accomplish the same task.
Provide examples or references for Linux users, such as how to perform the operation from a Linux environment.
Clarify whether the Azure portal steps are platform-agnostic (i.e., accessible from any web browser), and if so, explicitly state this to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by exclusively referencing Visual Studio and Visual Studio Code workflows, using Windows-centric UI instructions (e.g., right-click, F5), and omitting explicit Linux/macOS terminal or editor alternatives. There are no Linux-specific examples or mentions of common Linux editors or command-line workflows, and troubleshooting steps assume Azure Portal or CLI usage without addressing platform-specific differences.

Recommendations:

Include explicit instructions for Linux and macOS users, such as using VS Code on Linux, or alternative editors like Vim or Nano for editing JSON files.
Provide terminal-based workflows for adding bindings and running/debugging the function, rather than relying solely on VS Code UI actions.
Mention keyboard shortcuts and UI actions for all supported platforms (Windows, Linux, macOS), not just Windows (e.g., clarify F5 vs. Cmd+F5, right-click vs. Ctrl+click).
Add troubleshooting steps that address common Linux/macOS issues, such as file permissions or environment variable setup.
Reference cross-platform tools and avoid suggesting Visual Studio (full IDE) for deployment unless a Linux/macOS equivalent is provided.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation refers to the driver as the 'Windows Azure Storage Blob driver' (WASB) and discusses it as the prior capability before ABFS. The term 'Windows' is used in the context of Azure Storage Blob, which may suggest a Windows-centric origin or association. However, the technical content, examples, and configuration instructions are platform-neutral and use standard Hadoop tools and configuration files, with no exclusive focus on Windows or PowerShell. Linux/Unix examples are present (e.g., bash commands), and there is no omission of Linux equivalents.

Recommendations:

Clarify that the 'Windows Azure Storage Blob driver' (WASB) is not Windows-specific, or consider using the acronym 'WASB' primarily to avoid confusion.
Add a note early in the documentation to emphasize that ABFS and WASB are cross-platform and supported on both Linux and Windows Hadoop distributions.
Ensure that all examples and configuration instructions remain platform-neutral, and explicitly mention cross-platform compatibility where relevant.
If mentioning management tools like Ambari, clarify their cross-platform nature or provide Linux-specific alternatives if any exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell command examples for environment variable setup, npm usage, and CLI commands, but consistently lists Bash first. There is no exclusive use of Windows tools, and Linux (Bash) is always represented. However, the presence of PowerShell tabs and examples throughout, and the order in which Bash is always presented before PowerShell, may indicate a slight bias towards Windows users by ensuring PowerShell parity, even though the commands are cross-platform. There are no missing Linux examples, and no exclusive mention of Windows-only tools or patterns.

Recommendations:

Continue to provide both Bash and PowerShell examples to ensure parity.
Consider explicitly mentioning that Bash commands work on Linux and macOS, and PowerShell commands are for Windows, to clarify platform applicability.
If possible, add a short section at the start of the tutorial explaining how to choose between Bash and PowerShell based on the user's OS.
Ensure that any screenshots or UI references are not Windows-specific, or provide Linux/macOS equivalents if UI differences exist.
Maintain the current practice of not favoring Windows-specific tools or patterns, and avoid implying that PowerShell is the default unless it truly is.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page exhibits some Windows bias, primarily by presenting PowerShell code for SSH access as the only explicit example, even though the context is a Linux-based HDInsight cluster. The SSH example is labeled as 'sample PowerShell code,' which may confuse Linux users, and no native Linux shell example is provided. However, the rest of the HDFS CLI commands are platform-agnostic and do not show further Windows bias.

Recommendations:

Provide Linux shell (bash) examples for SSH access alongside or instead of PowerShell, since HDInsight clusters are Linux-based.
Clarify that SSH commands are the same on Linux/macOS terminals and Windows (when using WSL or OpenSSH), or provide separate tabs/examples for each platform.
Avoid labeling SSH command blocks as 'PowerShell' when the commands are cross-platform.
Review other sections for similar platform-specific language or examples and ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation heavily emphasizes Visual Studio Code and Azure Portal workflows, which are cross-platform, but all step-by-step UI instructions and screenshots are tailored to GUI tools rather than command-line environments. There are no explicit Windows-only tools (like PowerShell or Command Prompt), but the absence of Linux-specific command-line or file management examples (e.g., using Bash, Linux file explorers, or Linux-native editors) means Linux users are left to adapt instructions themselves. The CLI examples are platform-neutral (Azure CLI), but the primary guidance and troubleshooting focus on GUI workflows, which may be more familiar to Windows users.

Recommendations:

Add explicit Linux (and macOS) command-line examples for uploading files to Blob Storage, such as using 'az storage blob upload' or 'curl' with SAS tokens.
Include instructions for managing files and environment variables using Bash or other Linux-native tools.
Where UI screenshots are shown, clarify that the steps are identical on all platforms, or provide alternative screenshots for Linux/macOS if there are differences.
Mention that Visual Studio Code is cross-platform, but also suggest alternative editors or workflows for users who prefer terminal-based development.
Add troubleshooting tips for common Linux/macOS issues, such as file permissions or environment variable configuration.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is focused exclusively on .NET usage for creating a user delegation SAS, with all code samples in C#. There are no references to platform-specific tools, but the .NET ecosystem and C# code examples are typically associated with Windows development. There are no Linux or cross-platform command-line examples (such as Bash, Azure CLI, or PowerShell), nor is there any mention of Linux-specific considerations or parity.

Recommendations:

Include equivalent examples using Azure CLI and/or PowerShell, which are cross-platform and can be run on both Windows and Linux.
Add a section or note clarifying that the .NET SDK and code samples are cross-platform and can be run on Linux, macOS, and Windows, possibly with links to .NET installation instructions for Linux.
Provide sample scripts or instructions for creating a user delegation SAS using REST API calls via curl or similar Linux-native tools.
Explicitly mention any platform-specific requirements or differences, if any, to help Linux users understand how to adapt the instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page exhibits mild Windows bias, primarily by listing PowerShell as the first example under 'Get started with SAS' for user delegation SAS, and by including a PowerShell-specific guide that is not matched by a Bash or Linux shell equivalent. While Azure CLI is mentioned (which is cross-platform), the explicit highlighting of PowerShell and its placement before other language examples suggests a preference for Windows tooling. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or workflows.

Recommendations:

Add Bash or Linux shell examples for creating SAS tokens, especially for common scenarios.
Ensure that Azure CLI examples are clearly marked as cross-platform and, where possible, provide explicit Linux usage notes.
Balance the order of example links so that PowerShell is not always listed first; consider rotating or grouping by platform-neutral and platform-specific tools.
If PowerShell is included, also include equivalent Bash or shell scripts for parity.
Explicitly mention that Azure CLI and SDKs are available on Linux and macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-centric tools such as Azure PowerShell and AzCopy for data copying and backup operations, but does not provide explicit Linux or cross-platform command-line examples or mention Linux-native alternatives. There are no CLI (az), Bash, or Linux shell script examples, and PowerShell is referenced without clarifying its cross-platform availability or providing parity with Linux usage patterns.

Recommendations:

Include Azure CLI (az) examples alongside or before PowerShell examples for all operations, as Azure CLI is cross-platform and widely used on Linux.
When referencing AzCopy, clarify that it is available for Windows, Linux, and macOS, and provide example commands for both Windows (CMD/PowerShell) and Linux (Bash).
Avoid referencing 'Azure PowerShell' as the only scripting interface; always mention Azure CLI as an alternative.
Where scripting or automation is discussed, provide both PowerShell and Bash script snippets.
Explicitly state the cross-platform nature of tools where applicable, and avoid implying that Windows tools are the default or only option.
Add a section or callout for Linux users, summarizing recommended tools and patterns for disaster recovery operations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory') in all examples and does not provide any Linux or macOS path examples. While there are notes about quoting differences between shells, the actual command examples and syntax always show Windows paths, and Linux/Unix-style paths are never demonstrated. This may make the documentation less approachable for Linux/macOS users.

Recommendations:

For each example using a Windows path (e.g., 'C:\myDirectory'), provide a parallel example using a Linux/macOS path (e.g., '/home/user/myDirectory').
In the syntax sections, show both Windows and Linux/macOS variants, or use a placeholder like '<local-directory-path>' in the example and clarify with both path styles below.
Consider alternating which platform is shown first, or present both at the same time, to avoid the appearance of Windows-first bias.
Explicitly mention that AzCopy is cross-platform and provide links or notes about shell-specific behaviors for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides parity between Azure Portal, PowerShell, and Azure CLI for all major operations (enable/disable/restore soft delete). However, PowerShell examples are always presented before Azure CLI, and there are no explicit Linux shell (bash) or scripting examples outside of Azure CLI. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not mention or link to Linux-specific tools or workflows (e.g., Bash scripting, Cloud Shell usage on Linux).

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and more familiar to Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash).
Add a short section or note for Linux users, highlighting that all Azure CLI commands can be run from Bash or other Linux shells, and provide links to Azure CLI installation instructions for Linux.
Where possible, provide Bash script snippets or usage patterns (e.g., using environment variables, piping output) to demonstrate Linux-native workflows.
Consider referencing Azure Cloud Shell, which provides a cross-platform, browser-based CLI experience, and is accessible from both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by exclusively providing instructions and screenshots for the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no examples or guidance for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST APIs to accomplish the same tasks. The documentation also omits any mention of Linux-specific considerations or tools for integrating Commvault with Azure, and does not provide command-line alternatives that would be relevant for Linux administrators.

Recommendations:

Add parallel instructions and examples for Linux users, such as using the Azure CLI (az commands) to create storage accounts, containers, and manage access keys.
Include sample scripts or command-line steps for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
Mention and link to REST API documentation for users who may wish to automate tasks in a platform-agnostic way.
Explicitly state that the Azure Portal is accessible from any OS, but provide alternatives for users who prefer or require CLI-based workflows.
Highlight any Linux-specific considerations for Commvault MediaAgent deployment or integration with Azure Storage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation presents PowerShell examples before Azure CLI, and the PowerShell tab is more detailed and prominent. There is no explicit mention of Linux or cross-platform considerations, and the use of PowerShell as the first and primary example may signal a Windows-centric approach. However, Azure CLI (which is cross-platform) is also covered, and no Windows-only tools or patterns are exclusively required.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
Add a note clarifying that PowerShell Core is available cross-platform, if relevant, or recommend Azure CLI for Linux/macOS users.
Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
Consider adding Bash shell examples or clarifying that Azure CLI commands can be run in Bash on Linux/macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides instructions and examples exclusively for Windows environments. It references a Windows executable (.exe), uses Windows command prompt syntax, and does not mention or provide guidance for Linux or cross-platform usage. There are no Linux-specific instructions or alternative commands, and the event generator application appears to be Windows-only.

Recommendations:

Provide instructions for running the event generator application on Linux, such as offering a cross-platform version (e.g., .NET Core, Java, or Python) or a Docker container.
Include Linux shell command examples (e.g., bash) alongside Windows command prompt examples.
Clarify OS requirements for the event generator and suggest alternatives or workarounds for Linux/Mac users.
If the application is Windows-only, explicitly state this and provide a comparable method for Linux users to generate and send events (e.g., using Azure CLI, Python scripts, or open-source tools).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on .NET (C#) samples and references Visual Studio, which is traditionally a Windows-centric development environment. There are no examples or references for Linux-specific tools, environments, or workflows. The prerequisite and sample instructions assume a Windows/.NET context, with no mention of Linux or cross-platform alternatives.

Recommendations:

Include explicit instructions or notes on how to use the .NET SDK and samples on Linux (e.g., using .NET Core/SDK on Linux, VS Code, or JetBrains Rider).
Mention and provide examples for running the samples on Linux, including any required dependencies or setup steps.
Reference cross-platform development tools (such as VS Code) alongside Visual Studio.
Clarify that the .NET SDK and samples are cross-platform if applicable, and provide troubleshooting or environment setup guidance for Linux users.
Ensure parity in documentation structure and depth between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides configuration examples for multiple origin types, including App Service, Application Gateway, Application Gateway for Containers, IIS, and AKS NGINX controller. However, it includes a dedicated example for Microsoft IIS (a Windows-specific web server) and omits equivalent examples for common Linux web servers such as Apache HTTP Server or NGINX (outside of Kubernetes). The IIS example is the only origin-specific example that is platform-specific, and it appears before the AKS NGINX controller example, which is more Linux-centric. There are no PowerShell-specific commands or explicit Windows command-line instructions, but the inclusion of IIS and omission of standalone Linux web server examples indicates a subtle Windows bias.

Recommendations:

Add example configurations for popular Linux web servers such as Apache HTTP Server and standalone NGINX (outside of Kubernetes), showing how to filter the X-Azure-FDID header.
Ensure that Linux-origin examples appear alongside or before Windows-specific examples like IIS to provide parity and avoid the perception of Windows-first ordering.
If possible, provide shell command snippets (e.g., iptables, firewalld) for configuring IP address filtering on Linux servers, in addition to network security group rules.
Review the documentation for other subtle Windows-centric language or assumptions and ensure cross-platform inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell-specific command (`Get-AzLocation | Where-Object Providers -like 'Microsoft.OperationalInsights' | Select DisplayName`) as the only example for listing available Log Analytics workspace regions. No equivalent CLI or Bash/Linux example is given, and there is no mention of cross-platform tools or instructions. The rest of the documentation is GUI-focused and does not reference platform-specific tools, but the only command-line example is Windows-centric.

Recommendations:

Provide equivalent Azure CLI (az) commands for tasks such as listing available Log Analytics workspace regions, e.g., `az account list-locations --query "[?metadata.resourceType=='Microsoft.OperationalInsights/workspaces'].displayName"`.
When giving command-line examples, always include both PowerShell and Bash/Azure CLI versions, or clearly indicate cross-platform options.
Review documentation for any other PowerShell-specific guidance and ensure Linux/macOS users are equally supported.
Consider adding a note that all tasks can be performed using Azure CLI or Cloud Shell, which are cross-platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows/Azure-centric tooling by exclusively referencing Azure SQL Database as the external metastore solution, without mentioning or providing examples for commonly used open-source alternatives (such as MySQL or PostgreSQL) that are often preferred in Linux-based Hadoop deployments. There are no command-line examples (PowerShell or Bash), but the only database technology discussed is a Microsoft product, and all configuration steps assume use of Azure Portal or Ambari UI, with no Linux-native or cross-platform CLI guidance.

Recommendations:

Include guidance and examples for using open-source databases (e.g., MySQL, PostgreSQL) as external metastores, which are supported by Hive and Oozie and commonly used in Linux environments.
Provide CLI-based instructions (using Bash/SSH) for configuring external metastores, in addition to portal and UI-based steps.
Mention and link to documentation for setting up and connecting to non-Azure SQL databases, especially for users running HDInsight clusters in Linux environments or hybrid clouds.
Clarify that while Azure SQL Database is recommended for Azure-native deployments, other RDBMS options are available and supported for Hive/Oozie/Ambari metastores.
Add examples or references for managing firewall rules and connectivity for non-Azure SQL databases, which may be hosted on Linux servers.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references PowerShell-specific recovery steps (e.g., using Undo-AzKeyVaultKeyRemoval) and links to PowerShell modules without providing equivalent CLI or Linux-native command examples. There are no explicit Linux or cross-platform command-line instructions, and the documentation assumes the use of PowerShell for recovery operations.

Recommendations:

Provide Azure CLI equivalents for all PowerShell commands, especially for key vault recovery operations.
Include Linux/macOS-specific instructions or examples where command-line actions are required.
When referencing command-line tools or scripts, present both PowerShell and Bash/Azure CLI options, or clarify when steps are platform-agnostic.
Review all linked resources to ensure they include cross-platform guidance, not just Windows/PowerShell instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for most network management tasks, but PowerShell commands are consistently listed before CLI commands. This ordering, along with the use of PowerShell-specific scripting in some examples, subtly prioritizes Windows-centric tooling and patterns, even though Azure CLI is cross-platform and more native to Linux environments. There are no explicit Linux shell (bash) examples, and the documentation does not mention Linux-specific tools or workflows.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature and popularity among Linux users.
Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, and provide bash shell examples where appropriate.
Where PowerShell scripting is used (e.g., looping over NICs), provide equivalent bash/CLI scripts for Linux users.
Add a note clarifying that all management tasks can be performed from Linux environments using Azure CLI, and link to relevant Linux setup guides.
Consider including screenshots or walkthroughs using Linux terminals to further demonstrate parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates mild Windows bias by referencing Visual Studio Hadoop tools in the 'Next steps' section, which are primarily Windows-based. Additionally, the workflow for accessing and deleting clusters is described in terms of the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. There are no explicit Linux command-line examples or mentions of Linux-specific tools, and no PowerShell or CMD examples are present. However, the cluster creation link refers to 'linux-clusters', and the main Grafana access method is via web browser, which is cross-platform.

Recommendations:

Include references to cross-platform or Linux-native tools for managing HDInsight clusters, such as Azure CLI or Azure Cloud Shell, alongside or instead of Visual Studio tools.
Provide command-line examples (using Bash/Azure CLI) for common tasks like accessing Grafana or deleting clusters, to ensure Linux users have parity.
Balance 'Next steps' resources by including links to Linux-friendly development environments or tools, not just Visual Studio.
Explicitly state that the Azure Portal and Grafana web UI are accessible from any OS, to reinforce cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits a mild Windows bias. While it covers both Windows and Linux in the artifact parameters table, Windows terminology and concepts (such as 'Windows VM Administrators group', 'Microsoft IaaSAntimalware extension', and password policies typical of Windows environments) are mentioned explicitly and in detail. There are no Linux-specific administrative group examples or equivalent Linux user/group management parameters. Additionally, the documentation references Windows VM settings before or more frequently than Linux equivalents in several places, and the only user/group management examples are for Windows. However, there are parameters for both Windows and Linux Log Analytics agents, and Linux is not entirely omitted.

Recommendations:

Add Linux-specific examples for user/group management, such as parameters for configuring sudoers or root access exclusions/inclusions on Linux VMs.
Where user/group management is discussed for Windows (e.g., Administrators group), provide equivalent Linux examples (e.g., sudo or wheel group).
Ensure that for every Windows-specific extension or policy (like IaaSAntimalware), the Linux equivalent (such as the OMS agent or Linux security extensions) is also mentioned and described.
Review the order of presentation in the artifact parameters table and documentation text to ensure Linux and Windows are given equal prominence, alternating or grouping them together where possible.
Where password policies are described, clarify which apply to Windows, Linux, or both, and provide Linux-specific guidance if relevant.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Windows PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning or providing Linux/CLI alternatives. No Linux-specific tools or authentication workflows are described, and there is no parity in example commands for Linux users.

Recommendations:

Include instructions and examples for obtaining an Azure access token using the Azure CLI (az account get-access-token) on Linux/macOS.
Mention cross-platform alternatives to PowerShell, such as Bash scripts or REST client tools available on Linux.
Provide equivalent authentication and request examples using Linux-native tools and workflows.
Ensure that all referenced tools and commands are available and documented for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by presenting Azure PowerShell examples before Azure CLI examples in key sections, and by providing detailed PowerShell scripts for network security group configuration. While Azure CLI (cross-platform) examples are included, there are no native Linux shell (bash) or scripting examples for Azure resource management. However, the DNS configuration sections do focus on Linux (Bind) and the network validator tool is recommended for use on Azure Linux VMs, which helps balance the overall bias.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples to avoid the perception of Windows-first bias.
Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
Consider providing bash script examples for common tasks, especially for Linux-focused audiences.
Where PowerShell is used, clarify that PowerShell Core is available on Linux and macOS, or provide equivalent bash/CLI commands.
Add a brief section or note highlighting the parity between PowerShell and CLI, and guide users on choosing the best tool for their OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation instructs users to open the cloned repository in Visual Studio Code using the menu path 'File > Open Folder', which reflects the Windows UI and does not mention Linux or macOS equivalents. There are no alternative instructions or screenshots for Linux users, nor is there mention of command-line alternatives for opening the folder in VS Code.

Recommendations:

Include instructions for opening the folder in VS Code on Linux and macOS, such as using the 'code .' command in the terminal.
Mention that the menu path may differ on other operating systems and provide the equivalent steps or screenshots for Linux/macOS.
Use cross-platform language (e.g., 'Open the folder in Visual Studio Code using the menu or by running code . in your terminal') to ensure inclusivity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page contains a reference to a Windows-specific tool (Get-AzResourceProvider from PowerShell) when describing how to determine valid strongType resource types. There are no equivalent Linux/CLI commands or examples provided, and no mention of cross-platform alternatives. No explicit Windows-first ordering is present, but the only tool mentioned is Windows-centric.

Recommendations:

Add Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside or in place of PowerShell commands to ensure Linux and macOS users are supported.
Wherever a PowerShell cmdlet is referenced, provide the corresponding Azure CLI command and example output.
Consider a short note or table summarizing cross-platform methods for discovering resource types, making it clear that both Windows and Linux/macOS users are supported.
Review other documentation sections for similar tool references and ensure parity in examples and instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation describes how to configure automatic topic creation in Apache Kafka on Azure HDInsight, mentioning PowerShell and Resource Manager templates for configuration during cluster creation. However, it does not provide any Linux/Unix CLI or Bash examples, nor does it mention Linux-native tools or workflows for cluster creation or configuration. The only automation tool mentioned is PowerShell, which is Windows-centric, and there is no parity for Linux users.

Recommendations:

Include equivalent Bash or Azure CLI examples for configuring Kafka during cluster creation, alongside or instead of PowerShell.
Mention and provide examples for using Linux-native tools (such as Bash scripts or the Azure CLI) for cluster configuration.
Ensure that automation instructions are cross-platform by referencing both Windows and Linux tools equally.
Explicitly state that the steps can be performed from any OS, and clarify when a tool is Windows-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by consistently presenting PowerShell examples before Azure CLI examples in all code sections. The PowerShell sections are more detailed, with richer example scripts and explanations, while Azure CLI sections are more succinct and sometimes refer to external documentation for examples. There is no mention of Linux-specific tools, shells, or workflows, and the documentation implicitly assumes familiarity with PowerShell, which is more common on Windows.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first in some sections to avoid reinforcing a Windows-first perspective.
Ensure that Azure CLI examples are as detailed and comprehensive as the PowerShell examples, including full command sequences and explanations.
Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, to encourage non-Windows users.
Where appropriate, add Bash shell examples or notes for Linux/macOS users (e.g., variable syntax differences, login methods).
Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported equally.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only C# code examples, which are most commonly associated with Windows development environments. There are no examples using Linux-native tools, shell scripts, or cross-platform command-line utilities (such as Azure CLI or REST API via curl). This may make it less accessible or immediately useful for Linux users or those working outside of the Windows/.NET ecosystem.

Recommendations:

Add equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux.
Include REST API examples using curl or similar tools to demonstrate how to interact with Azure Resource Graph from any platform.
If PowerShell is relevant, provide both Windows PowerShell and cross-platform PowerShell Core examples, and clarify their compatibility.
Explicitly mention that the SDK and APIs are usable from Linux and provide links or notes on how to set up the environment on Linux.
Consider including bash or Python SDK examples, which are popular in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell is mentioned before or alongside CLI without clarifying cross-platform usage. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux tools or environments, which may disadvantage Linux users or suggest a Windows-first approach.

Recommendations:

Clearly indicate that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
Consider providing Bash shell examples or explicitly referencing Bash for Linux/macOS users, especially in sections where command-line usage is demonstrated.
If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide separate tabs for Windows PowerShell and Bash.
Where possible, lead with Azure CLI/Bash examples, as these are more universally applicable, and mention PowerShell as an alternative.
Add notes or links for Linux/macOS users about installing and using Azure CLI in their environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence to the cross-platform CLI, and there is no explicit mention of Linux-specific usage or shell environments. The PowerShell tab may imply a Windows-centric approach, especially since no Bash or Linux shell examples are provided or discussed.

Recommendations:

Explicitly mention that the Azure CLI example works cross-platform, including on Linux and macOS.
Add a Bash shell example or clarify that the Azure CLI command can be run in Bash, zsh, or other Linux shells.
Consider reordering tabs to present the Azure CLI (cross-platform) example before PowerShell, or clarify that PowerShell Core is available on Linux.
Add a note about any differences or prerequisites for running these commands on Linux versus Windows, if applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references the Windows-style environment variable (%HADOOP_HOME%) when describing the location of the core-site.xml file, and does not provide the Linux equivalent ($HADOOP_HOME). This suggests a subtle Windows-first bias. No explicit PowerShell or Windows command-line examples are present, but the use of Windows path notation and environment variable syntax may confuse Linux users. There are no Linux-specific examples or clarifications.

Recommendations:

When referencing environment variables or file paths, provide both Windows (%HADOOP_HOME%) and Linux ($HADOOP_HOME) syntax.
Clarify that the location of configuration files applies to both Windows and Linux clusters, and show both path formats if they differ.
Review for any other implicit Windows assumptions and ensure Linux parity in terminology and examples.
If command-line examples are added in the future, ensure both Windows (cmd/PowerShell) and Linux (bash) examples are provided.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now cross-platform) in every example, and the explicit labeling of 'Azure PowerShell' as a primary tab, demonstrates a Windows-centric approach. Additionally, PowerShell examples are always presented alongside or immediately after CLI examples, reinforcing a 'Windows-first' mindset. There are no Linux-specific shell (e.g., Bash) or scripting examples, nor are there references to Linux-native tools or patterns.

Recommendations:

Add explicit Bash or shell script examples where applicable, especially for users on Linux or macOS.
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if differences exist.
Consider reordering tabs to present Azure CLI (the most cross-platform tool) first, or provide a note about cross-platform compatibility.
If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide installation or usage notes for those platforms.
Where possible, include references to Linux-native scripting or automation approaches, such as using jq or other common Unix tools in conjunction with Azure CLI output.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits mild Windows bias, particularly in the 'Next steps' section, where a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' is given before any mention of Linux equivalents. Additionally, there is a reference to Windows-specific tooling, but no parallel guidance or examples for Linux users are provided. The main body of the documentation does not include command-line examples, but the resource links and structure suggest a Windows-centric approach.

Recommendations:

Add equivalent guidance and links for Linux users in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux PC' or similar documentation.
Ensure that any references to Windows tools or workflows are paired with Linux alternatives, or provide cross-platform instructions where possible.
Review linked pages (e.g., 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity and consider linking to Linux-specific tools or instructions.
Consider reordering links or examples so that Linux and Windows are presented with equal prominence, or in alphabetical order to avoid perceived prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation consistently presents Azure CLI and Azure PowerShell examples side by side, but always lists Azure PowerShell (a Windows-centric tool) as a primary method alongside CLI. There are no explicit Linux shell or scripting examples, and PowerShell is given equal prominence to the cross-platform CLI, which may suggest a Windows-centric bias.

Recommendations:

Add explicit Bash or Linux shell examples where relevant, especially for scripting scenarios.
Clarify that Azure CLI is fully cross-platform and highlight its use on Linux/macOS.
Consider listing Azure CLI examples before PowerShell, or note that PowerShell Core is cross-platform if that is intended.
Include notes or links for Linux/macOS users about installing and using the Azure CLI.
If PowerShell examples are included, specify whether they are compatible with PowerShell Core on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Linux and Windows instructions for editing the hosts file, but the Linux example is more detailed and comes first. The Windows-specific instructions are brief and appear after the Linux steps. There is a screenshot for Windows, but no command-line example (e.g., using PowerShell or Notepad). The document mentions the Windows hosts file location but does not provide a step-by-step example for Windows users, nor does it mention Linux tools before Windows equivalents. Overall, there is a slight Windows bias in that Windows is treated as a secondary platform, with less detailed guidance.

Recommendations:

Provide step-by-step instructions for editing the hosts file on Windows, including example commands (e.g., using Notepad or PowerShell) similar to the Linux example.
Include a command-line example for testing connectivity from Windows (e.g., using curl for Windows or PowerShell's Invoke-WebRequest), not just a screenshot.
Ensure that both Linux and Windows examples are equally detailed and appear in parallel, rather than Linux first and Windows as an afterthought.
Explicitly mention that the instructions apply to both Linux and Windows VMs, and provide parity in troubleshooting and verification steps for both platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates log analysis using a custom Python library for IIS (Internet Information Services) logs, which are specific to Windows servers. The sample data, parser, and log schema are all tailored to Microsoft IIS, with no mention of Apache, Nginx, or other common Linux-based web servers. There are no examples or guidance for analyzing non-Windows log formats, nor suggestions for adapting the workflow to Linux environments.

Recommendations:

Include examples using log formats from popular Linux web servers such as Apache (access.log) or Nginx.
Provide or reference a generic log parser or libraries for non-IIS logs, and demonstrate how to use them in Spark.
Clarify that the sample data and parser are specific to IIS/Windows, and suggest equivalent workflows for Linux-based logs.
Offer guidance on how to upload and analyze custom log files from Linux servers.
Balance the documentation by mentioning both Windows and Linux scenarios, or provide links to Linux-focused log analysis tutorials.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash/cURL and PowerShell/Invoke-WebRequest examples for all major steps, but there is a subtle Windows bias: PowerShell is mentioned first in the prerequisites, and Windows/PowerShell is often referenced before Bash/Linux. The use of Windows-specific terminology (e.g., 'on Windows PowerShell') and the explicit mention of credential pop-ups (a Windows UX pattern) further reinforce this bias, even though Linux/Bash examples are present and complete.

Recommendations:

List Bash/cURL examples before PowerShell/Windows examples to avoid the perception of Windows-first bias.
In the prerequisites, mention Bash/cURL before PowerShell/Invoke-WebRequest, or present them in parallel.
Use neutral language such as 'On Bash' and 'On PowerShell' instead of 'on Windows PowerShell', to avoid platform-preference signaling.
Where possible, provide parity in explanation detail for both Bash and PowerShell examples (e.g., credential handling).
Consider a tabbed or side-by-side layout for Bash and PowerShell examples to emphasize equal support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally focuses on Linux/Bash workflows, but in the prerequisites section, it presents Windows (specifically Windows Subsystem for Linux and PowerShell) as the primary environment. Bash on Windows is mentioned before native Linux/Unix shells, and PowerShell alternatives are described in detail, suggesting a Windows-first approach. There are no explicit Linux-only gaps, but the ordering and emphasis may subtly favor Windows users.

Recommendations:

Present native Linux/Unix instructions first, followed by Windows-specific notes as alternatives.
Avoid suggesting Windows Subsystem for Linux as the default Bash environment; instead, treat it as one of several options.
When referencing PowerShell cmdlets, provide equivalent Linux/Unix commands side-by-side.
Clarify that all examples work natively on Linux and macOS, and only require WSL or PowerShell on Windows.
Ensure that all tooling and command-line examples are cross-platform or have clear, parallel instructions for each OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page assumes Windows as the default environment, only providing detailed setup steps for non-Windows (Linux/macOS) users as a special case. There are no explicit Linux command-line examples for common tasks (such as launching VS Code or running Spark commands), and the guidance for Linux users is limited to troubleshooting package installation. Windows tools and workflows are implicitly prioritized.

Recommendations:

Provide parallel setup instructions for both Windows and Linux/macOS users, not just for non-Windows as an exception.
Include Linux/macOS-specific command-line examples for launching VS Code, running Spark commands, and managing Python environments.
List Linux and Windows instructions side-by-side or in clearly separated sections to ensure parity.
Mention Linux package managers and tools (e.g., apt, yum, brew) where relevant, not just in troubleshooting.
Explicitly state when steps differ between platforms, and ensure Linux/macOS users are not treated as an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page exhibits mild Windows bias by listing PowerShell and Visual Studio connectivity options before CLI and Python SDK options, and by specifically highlighting 'Connect with PowerShell' as a quickstart. There is no explicit Linux example or mention of Linux-specific tools, and the ordering of examples may suggest a Windows-first approach.

Recommendations:

Ensure that Linux/CLI examples are given equal prominence by listing 'Connect with CLI' before or alongside 'Connect with PowerShell' in quickstarts.
Include explicit references to Linux development environments and workflows, such as Bash, VS Code on Linux, or Linux-based automation.
Add quickstart links or sections for Linux users, such as 'Connect with Bash' or 'Develop on Linux', to demonstrate parity.
Where PowerShell is mentioned, also mention Bash or other cross-platform shells to avoid implying PowerShell is the default or only option.
Review other linked documentation (e.g., the PowerShell and CLI guides) to ensure Linux examples are present and up-to-date.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page lists a 'Next steps' link specifically for working with HDInsight from a Windows PC, highlighting Windows tools. There is no equivalent mention or link for Linux or cross-platform tools, and the Windows-specific guidance appears before any Linux-specific guidance. No Linux or cross-platform command-line examples or tools are mentioned.

Recommendations:

Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, parallel to the Windows PC link.
Ensure that any platform-specific tooling or setup guides are provided for both Windows and Linux users.
Consider reordering or grouping platform-specific links together to avoid the appearance of prioritizing Windows.
If possible, provide cross-platform examples or note when instructions are applicable to both Windows and Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions solely for the Azure web portal, without mentioning command-line alternatives. There are no examples for Linux users (e.g., using Azure CLI), nor are PowerShell or Windows-specific tools mentioned, but the absence of CLI guidance can disadvantage Linux users who may prefer or require non-GUI methods.

Recommendations:

Add instructions for finding the subscription ID using the Azure CLI, which is cross-platform and commonly used on Linux.
If mentioning PowerShell, ensure Azure CLI examples are given equal prominence and appear before or alongside any Windows-specific tools.
Clarify that the Azure portal is accessible from any OS, but provide alternative methods for users who prefer or require command-line access.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page is largely neutral and focused on HDInsight versioning, but in the 'Next steps' section, the only platform-specific workflow highlighted is 'Work in Apache Hadoop on HDInsight from a Windows PC', which appears before any Linux-specific guidance. There is also a reference to Windows tools, but no equivalent mention of Linux or cross-platform tooling, which may suggest a subtle Windows bias.

Recommendations:

Add a parallel 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, or a cross-platform guide.
Ensure that references to platform-specific tools or workflows are balanced, with Linux and macOS options given equal prominence to Windows.
Review other linked documentation (such as the Windows tools page) to ensure Linux alternatives are mentioned and linked.
Consider reordering or grouping platform-specific links together, or prefacing with a cross-platform option.

Create pull request

Bias Types:

⚠️ wsl_heavy

⚠️ windows_first

Summary:

The documentation is generally cross-platform in its usage examples, with all command-line instructions provided in bash syntax suitable for Linux or macOS. However, the 'Install Beeline client' section is heavily oriented towards Windows users by focusing on installation via Windows Subsystem for Linux (WSL), mentioning Windows file paths, and not providing native Linux or macOS installation instructions. This creates a bias towards Windows environments, especially for users seeking to install Beeline on non-Windows systems.

Recommendations:

Add a dedicated subsection for installing Beeline natively on Linux distributions (e.g., Ubuntu, CentOS) and macOS, with appropriate package manager commands and environment variable setup.
Clarify that the WSL-based instructions are specific to Windows users and provide parallel instructions for other operating systems.
Avoid referencing Windows-specific paths (e.g., /mnt/c/Users/user/) as the default; instead, use generic Unix-style paths and note Windows-specific paths only in a dedicated section.
Explicitly state OS prerequisites or differences at the start of the installation section to guide users to the most relevant instructions for their platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references SQL Server Integration Services (SSIS) and the Azure Feature Pack for SSIS as a method for running Pig jobs, which are Windows-centric tools. There are no examples or walkthroughs for running Pig jobs from Linux environments, nor are Linux-native tools or command-line examples provided. The documentation omits Linux/Unix command-line usage, which is common for Hadoop/Pig workflows.

Recommendations:

Add examples of running Pig jobs using SSH and the Linux command line, such as using the pig command in Bash.
Include references to cross-platform tools (e.g., PuTTY for Windows, OpenSSH for Linux/macOS) for connecting to HDInsight clusters.
Provide walkthroughs for submitting Pig jobs from both Windows and Linux environments to ensure parity.
Mention and link to documentation for running Pig scripts directly from the cluster's head node using standard Hadoop/Pig commands.
Balance the mention of Windows-specific tools (like SSIS) with Linux-native or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias, primarily by referencing Windows paths and tools first, and by providing more detailed instructions for Windows-specific features (such as the Kudu UI, which is not available for Linux). Windows paths are often mentioned before Linux equivalents, and the Kudu UI workflow is only supported on Windows, with Linux users directed to alternative methods. However, most command-line examples (Azure CLI, cURL) are cross-platform, and Linux paths are included where relevant.

Recommendations:

When mentioning default deployment paths, list Linux and Windows paths together or mention Linux first if the majority of users are on Linux.
Clarify the availability of features (such as the Kudu UI) for both Windows and Linux early in the relevant sections, and provide direct Linux alternatives in the same flow rather than as afterthoughts.
Where a feature is Windows-only (e.g., Kudu UI), provide a step-by-step Linux alternative (such as using the ZIP deploy API or FTP) in parallel, not just as a note.
Ensure that all examples and instructions are explicitly cross-platform where possible, and avoid assuming the user is on Windows unless the feature is truly exclusive.
Consider adding a summary table or section at the top that clearly outlines which deployment methods are available for Windows and Linux App Service plans.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary client-side interfaces for WebHCat, without mentioning Linux or cross-platform alternatives. No Linux-specific tools or command-line examples are provided, and there is no guidance for users working from Linux environments.

Recommendations:

Mention cross-platform or Linux-native tools (such as curl, wget, or the Linux command line) for interacting with the WebHCat REST API.
Provide example commands for submitting jobs or querying status using Linux shell tools.
Reference Hadoop command-line utilities (e.g., hadoop, hive, or beeline) where appropriate.
Include guidance for Linux users on how to modify configurations or troubleshoot issues, possibly via SSH or Ambari CLI.
Ensure that any mention of Windows-specific tools is balanced with Linux equivalents, and avoid implying that Windows tools are the primary or only supported method.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by providing an Azure PowerShell example for checking feature registration status before mentioning the Azure CLI alternative. No Linux-specific examples or tools are shown, and the PowerShell example is given more prominence. However, the page does reference Linux performance benchmarks and does not include Windows-only tools or patterns elsewhere.

Recommendations:

Present Azure CLI and PowerShell examples side-by-side or with equal prominence, ideally showing CLI first as it is cross-platform.
Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS.
Where possible, provide Linux-specific operational examples (e.g., mounting NFS volumes from Linux clients) in relevant sections.
Avoid using PowerShell-specific code blocks as the only example; always include CLI or REST API alternatives.
If referencing performance benchmarks for Linux, consider also linking to any available Windows benchmarks for parity, or clarify if Linux is the primary supported/tested platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates bias by providing more complete metric support and examples for Windows-based Azure Functions hosting plans, while repeatedly noting missing or unsupported features for Linux plans. There are no Linux-specific examples or guidance, and Windows support is implicitly prioritized.

Recommendations:

Add Linux-specific examples and guidance for monitoring Azure Functions, including any available metrics or workarounds.
Clearly indicate feature parity status and provide timelines or alternatives for Linux users where metrics are not supported.
Where features are unsupported on Linux, suggest equivalent monitoring strategies (e.g., using Application Insights logs or custom metrics).
Ensure that documentation sections and tables are inclusive of both Windows and Linux, or provide separate, parallel sections for each platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform, as HDInsight Spark clusters are Linux-based and IntelliJ IDEA is available on both Windows and Linux. However, there is a notable Windows bias in the Spark Local Console section, where the prerequisite for WINUTILS.EXE is mentioned without any Linux equivalent or guidance for Linux users. No Linux-specific instructions or troubleshooting are provided, and the documentation does not clarify that WINUTILS.EXE is only required on Windows. This omission may confuse Linux users and suggests an implicit Windows-first assumption for local development.

Recommendations:

Clearly state that WINUTILS.EXE is only required on Windows, and that Linux/macOS users do not need this prerequisite.
Add a section or note for Linux/macOS users explaining any differences or confirming that no extra steps are needed for local Spark console usage.
Where platform-specific configuration is required (e.g., environment variables like HADOOP_HOME), provide examples for both Windows and Linux/macOS (e.g., using export in bash for Linux).
Review the documentation for other subtle Windows assumptions (such as file paths or keyboard shortcuts) and provide Linux/macOS equivalents where relevant.
Consider adding a troubleshooting section for common platform-specific issues encountered on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and Azure PowerShell commands for deployment and resource management, but consistently lists PowerShell as the second option, which is a subtle 'windows_first' ordering. There is a notable presence of PowerShell examples throughout, which may be unnecessary for Linux-focused users. However, the SSH and Kafka management sections are Linux/Unix-centric, with all examples using Bash commands and Linux tools. There are no exclusive Windows tools or missing Linux examples, but the dual presentation of PowerShell and CLI, with CLI first, may still suggest a slight Windows bias due to the inclusion of PowerShell in all steps.

Recommendations:

Consider clearly labeling which command sets are for Windows and which are for Linux/macOS, especially for Azure CLI and PowerShell, to help users quickly find relevant instructions.
If PowerShell is not required for Linux/macOS users, clarify this in the documentation and possibly move PowerShell sections to an appendix or a separate tab for Windows users.
Ensure parity by providing Bash equivalents for any PowerShell commands if new steps are added in the future.
Explicitly state that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, to encourage non-Windows users.
If possible, provide a summary table at the top indicating which tools are recommended for each OS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references Azure Storage Explorer (a GUI tool most commonly used on Windows) for obtaining the ETag, but does not provide alternative methods (such as CLI or cross-platform tools) for Linux users. No command-line examples (e.g., using Azure CLI, PowerShell, or Bash) are provided for either Windows or Linux, but the only tool mentioned is typically associated with Windows environments.

Recommendations:

Provide cross-platform command-line examples for obtaining the ETag, such as using Azure CLI (az storage blob show ...) or REST API calls, which work on both Windows and Linux.
Explicitly mention and link to Azure Storage Explorer downloads for all supported platforms (Windows, macOS, Linux) to clarify its availability.
Include examples of how to perform the export operation using both PowerShell and Bash/Azure CLI to ensure parity.
Where GUI tools are referenced, always provide equivalent CLI instructions for automation and Linux compatibility.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation does not provide any OS-specific command-line examples, but it references the Azure CLI for obtaining tokens, which is cross-platform. However, there is a subtle bias in that no Linux- or Unix-specific tools or workflows are mentioned, and there are no explicit examples or guidance for Linux users. The only tool mentioned for token inspection is a Microsoft web tool (jwt.ms), with no mention of common Linux command-line utilities (e.g., jq, curl, openssl) that could be used for similar purposes.

Recommendations:

Provide explicit command-line examples for obtaining and inspecting tokens using cross-platform tools (e.g., Azure CLI, curl, jq) and clarify that Azure CLI works on Linux, macOS, and Windows.
Include Linux/Unix command-line snippets for decoding JWTs (e.g., using base64, jq, or openssl) alongside the mention of jwt.ms.
If referencing tools or shortcuts, ensure parity by mentioning both GUI/web and command-line options, and clarify platform compatibility.
Explicitly state that the workflows and tools described are cross-platform where applicable, to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes the registration process using the Azure portal GUI, which is platform-agnostic, but does not provide any command-line examples (such as Azure CLI or PowerShell). There is no mention of Linux-specific tools or workflows, nor are there any CLI examples that would support cross-platform automation. The absence of CLI instructions can be seen as a subtle Windows bias, as GUI workflows are more commonly associated with Windows environments, while Linux users often prefer or require CLI-based instructions.

Recommendations:

Add Azure CLI examples for registering a service client application, obtaining secrets, and configuring permissions. Ensure these examples are tested on both Windows and Linux.
If PowerShell examples are added, provide equivalent Bash/Azure CLI commands for Linux/macOS users.
Explicitly mention that the Azure portal is accessible from any OS, but provide links or sections for command-line alternatives.
Include a note or section on automating these steps using scripts, with examples for both Windows (PowerShell) and Linux (Bash/Azure CLI).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes using the Azure portal UI for application registration and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI), nor are there any Linux-specific instructions or screenshots. While the portal is technically cross-platform via browser, the lack of CLI or script-based examples (which are especially valued in Linux environments) and the absence of any mention of Linux or non-Windows workflows suggests a subtle Windows-first bias.

Recommendations:

Add Azure CLI examples for registering public client applications, as Azure CLI is cross-platform and widely used on Linux.
Include PowerShell and Bash script examples side by side where scripting is relevant.
Explicitly mention that the Azure portal can be accessed from any OS, and provide links or notes for users who prefer CLI or automation.
Add a section or callout for Linux/macOS users, highlighting any differences or tips for those environments.
Where screenshots are used, consider including examples from non-Windows browsers or generic browser windows to avoid implicit Windows bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation consistently uses PowerShell syntax (e.g., 'npm install ...' and 'npm run build' in PowerShell code blocks) for all command-line examples, which may imply a Windows-first or Windows-only development environment. There are no explicit Linux or macOS shell examples, and no mention of cross-platform command-line usage or differences.

Recommendations:

Use generic shell (sh, bash) code blocks for npm and CLI commands instead of PowerShell, unless a Windows-specific command is required.
Add a note clarifying that all npm commands work on Windows, Linux, and macOS, and that the examples are cross-platform.
If platform-specific differences exist (e.g., file paths, environment variables), provide both Windows and Linux/macOS examples.
Avoid using PowerShell-specific code block annotations unless demonstrating PowerShell-specific functionality.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only Windows-specific command-line instructions (e.g., using 'netstat' in a Windows command prompt) for troubleshooting, without offering equivalent Linux commands or examples. This creates a bias toward Windows environments and may hinder users operating Linux-based Azure VMs.

Recommendations:

Include Linux equivalents for all command-line examples. For instance, alongside 'netstat -an' in Windows, provide 'ss -ltn' or 'netstat -ltn' for Linux.
When referencing command prompts or shells, mention both Windows (Command Prompt/PowerShell) and Linux (Bash/shell) environments.
Ensure that troubleshooting steps and validation commands are platform-agnostic or provide parallel instructions for both Windows and Linux.
Explicitly state that the guidance applies to both Windows and Linux VMs, and clarify any platform-specific differences in behavior or commands.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples in each section, which may suggest a preference for Windows-centric tools. While Azure CLI is cross-platform and included, the PowerShell-first ordering and explicit mention of PowerShell may make Linux/macOS users feel secondary. No Linux-specific shell examples or guidance are provided.

Recommendations:

Alternate the order of examples so that Azure CLI (which is cross-platform) appears before PowerShell in some sections, or present both simultaneously without implied priority.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider adding bash/zsh shell context where appropriate.
Add a brief note at the start clarifying that both PowerShell and Azure CLI are supported on all major platforms, and users can choose whichever is most convenient.
Where possible, provide examples in native Linux shell syntax (e.g., bash) for common tasks, especially if there are differences in output handling or environment setup.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page is largely platform-neutral, focusing on Bicep language features and Azure resource management. However, in the section describing how to discover available 'list' operations for resources, the PowerShell example (Get-AzProviderOperation) is presented before the Azure CLI example. This ordering may suggest a slight Windows/PowerShell bias, as PowerShell is more commonly used on Windows. No Linux-specific tools or shell examples are provided, and there are no Bash or cross-platform scripting examples. The rest of the documentation does not reference Windows-specific tools, paths, or patterns.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is fully cross-platform and more familiar to Linux/macOS users.
Include Bash or shell script examples where appropriate, especially when demonstrating command-line usage.
Explicitly mention that both PowerShell and Azure CLI are available on all major platforms, and provide links to installation guides for each.
Consider adding a note or section on how to perform equivalent operations in Bash or other popular Linux shells, if relevant.
Review other documentation pages for similar ordering or tool selection to ensure consistent cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing Windows-based tools (Fiddler 4) for testing templates and not providing equivalent Linux alternatives or examples. There are no command-line or scripting examples (e.g., PowerShell, Bash), but the only explicit tool guidance is for a Windows application. No Linux or cross-platform alternatives are mentioned for the debugging/testing step.

Recommendations:

Include Linux-friendly or cross-platform alternatives to Fiddler, such as mitmproxy or Charles Proxy, in the 'Test your template' section.
Provide example instructions for using these alternative tools on Linux/macOS.
When referencing third-party tools, clarify their platform compatibility and suggest options for all major operating systems.
If possible, add a note or table listing recommended web debugging tools for Windows, Linux, and macOS.
Review other sections for opportunities to add Linux/macOS parity, such as mentioning Azure CLI usage or showing screenshots from non-Windows environments where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform, using cURL for all API examples, which is available on both Windows and Linux. However, there is a subtle Windows bias in the way file paths are described: the only explicit example for {path-to-dicoms} uses a Windows-style path (C:/dicom-server/docs/dcms), and there is no Linux/Unix-style path example provided. No PowerShell or Windows-specific tools are used, but the absence of Linux path examples may cause confusion for Linux users.

Recommendations:

Provide both Windows and Linux/Unix-style path examples for {path-to-dicoms}, e.g., 'C:/dicom-server/docs/dcms' and '/home/user/dicoms'.
Explicitly state that cURL commands work on both Windows and Linux, and mention any OS-specific considerations (such as path separators or quoting).
If referencing file paths or environment variables, show both Windows and Linux/Unix conventions side by side.
Consider adding a short section or note for Linux/macOS users, clarifying any differences in usage or syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides deployment examples for multiple platforms and languages. However, for the ASP.NET (classic) tab, the example exclusively uses a Windows runner (runs-on: windows-latest) and Windows-specific tools (NuGet, MSBuild with Windows path syntax), without offering a Linux-based alternative. In contrast, all other language tabs (including ASP.NET Core) use Ubuntu runners and cross-platform tooling. The ASP.NET example is also presented before the Java, Node.js, and Python examples, reinforcing a 'windows_first' bias for .NET technologies.

Recommendations:

Provide a Linux-based example for ASP.NET (classic) using Mono or .NET Core-compatible tooling if possible, or clarify that Windows is required and explain why.
If Windows is required for ASP.NET (classic), explicitly state this in the documentation to avoid confusion.
Consider reordering or grouping examples so that Windows-specific instructions do not appear to be the default or primary approach.
Where possible, mention cross-platform alternatives to Windows tools (e.g., dotnet CLI instead of MSBuild/NuGet) or explain the platform limitations.
Ensure parity in detail and clarity across all language/platform tabs, so Linux users do not feel secondary.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions using GUI navigation in the Azure portal, which is platform-neutral in appearance, but does not mention or provide examples for command-line alternatives. This omission can disadvantage Linux users who may prefer or require CLI-based workflows (e.g., Azure CLI, Bash scripting), especially since Windows users are often more accustomed to GUI-based instructions.

Recommendations:

Add equivalent instructions using the Azure CLI (az webapp config appsettings set ...) with Bash examples.
Explicitly mention that the steps can be performed via CLI or PowerShell, and link to relevant documentation for both.
Ensure that future documentation includes both GUI and command-line instructions to serve users on all platforms equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of the Azure CLI for authentication and instructs users to 'sign in to Azure from the CLI' without specifying the platform. However, the Azure CLI is cross-platform, but there is no mention of Linux or macOS environments, nor are there any examples or troubleshooting steps specific to those platforms. There are no explicit Windows-only commands or PowerShell scripts, but the lack of Linux/macOS context or examples may cause confusion for non-Windows users.

Recommendations:

Explicitly state that the Azure CLI is cross-platform and provide installation links for Windows, Linux, and macOS.
Add a note or section describing how to authenticate using the Azure CLI on Linux and macOS, including any differences in environment variables or shell usage.
Provide troubleshooting tips for common authentication issues on Linux/macOS (e.g., PATH issues, login persistence).
Where file paths are referenced (e.g., {path to the folder that includes green-square.dcm}), clarify path conventions for both Windows (C:\path\to\folder) and Linux/macOS (/home/user/path/to/folder).
If referencing the Azure CLI, clarify that commands are to be run in a terminal or shell, and that both Windows Command Prompt, PowerShell, and Unix shells (bash, zsh) are supported.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions that are platform-neutral in wording but implicitly assumes a graphical user interface (GUI) workflow typical of Windows environments. There are no explicit Linux or command-line alternatives mentioned, and the steps may not be as clear for Linux users who might prefer or require CLI-based instructions.

Recommendations:

Add explicit instructions or notes for Linux users, such as how to perform the same actions using the Azure CLI.
Include screenshots or examples from both Windows and Linux environments if the GUI differs.
Clarify whether the steps are identical across platforms, and if not, provide platform-specific guidance.
Mention any prerequisites or differences in setup for Linux users (e.g., installation of VS Code and Azure Tools on Linux).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias by using PowerShell syntax (>) in npm install commands and presenting these commands in a way that is most familiar to Windows users. There are no explicit Linux shell (bash) examples, and the use of the PowerShell prompt may confuse Linux/macOS users. However, the overall content is largely cross-platform, as it focuses on JavaScript, HTML, and npm, which are platform-agnostic.

Recommendations:

Replace PowerShell-specific prompts (>) in npm install commands with a generic shell prompt ($) or no prompt at all to avoid implying a Windows-only environment.
Add explicit Linux/macOS shell examples where command-line instructions are given, or use a neutral format (e.g., 'npm install azure-maps-indoor') without any prompt.
Include a note clarifying that all npm and JavaScript commands work on Windows, Linux, and macOS, and that the instructions are platform-independent.
If referencing tools or workflows that differ between platforms (such as file paths or environment variables), provide both Windows and Linux/macOS examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows instructions (using 7-Zip) before macOS/Linux (using the zip utility) in the section on creating a ZIP file, and specifically recommends a third-party Windows tool (7-Zip) rather than built-in options. However, the rest of the documentation is largely cross-platform, with Azure CLI and cURL examples that work on all OSes.

Recommendations:

Present macOS/Linux and Windows instructions in parallel tabs or alternate the order to avoid always listing Windows first.
For Windows, mention built-in zip support (e.g., via File Explorer's 'Send to > Compressed (zipped) folder') before recommending third-party tools like 7-Zip.
Ensure all screenshots and examples have Linux/macOS equivalents where possible.
Explicitly state that Azure CLI and cURL commands are cross-platform, and provide any OS-specific notes if needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation only describes enabling streaming logs via the Azure Tools for VS Code extension, which is a GUI tool commonly used on Windows. There are no instructions or examples for enabling streaming logs using command-line tools or methods commonly used on Linux systems.

Recommendations:

Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and commonly used on Linux.
Provide examples for enabling streaming logs via the Azure Portal, which is platform-agnostic.
Explicitly mention that the VS Code extension is available on all platforms, if relevant, or provide alternative steps for Linux users who may not use VS Code.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides deployment examples for multiple platforms. However, the ASP.NET (not Core) example is Windows-specific: it uses 'runs-on: windows-latest', relies on Windows-only tools (NuGet, MSBuild), and uses Windows path syntax. This is the only example that is Windows-exclusive; all other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use 'runs-on: ubuntu-latest' and cross-platform tooling. The ASP.NET section appears first among .NET examples, potentially reinforcing a Windows-first impression for .NET users.

Recommendations:

Add a Linux-based example for ASP.NET (if possible, e.g., using Mono or .NET Core for legacy apps), or clarify that ASP.NET (not Core) is Windows-only and explain why.
Reorder sections so that cross-platform or Linux-first examples (such as ASP.NET Core) appear before Windows-only examples.
Explicitly state in the ASP.NET section that it is Windows-only, and provide guidance for users who want to target Linux.
Where Windows-specific tools are used (NuGet, MSBuild), mention Linux alternatives or note their absence.
Ensure parity in detail and clarity between Windows and Linux examples across all stacks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is generally cross-platform, using Azure CLI and bash-style variable syntax, which is compatible with Linux and macOS. However, there is a subtle Windows bias: the only editor mentioned is Visual Studio Code, and there is a note about running scripts in PowerShell and needing to adjust variable syntax, which is presented as an afterthought. There are no explicit Linux or macOS instructions, nor are common Linux editors or shells mentioned. The documentation assumes familiarity with bash but does not clarify cross-platform compatibility or provide Linux/macOS-specific guidance.

Recommendations:

Explicitly mention that the CLI and scripts work on Linux, macOS, and Windows, and clarify which shell is assumed (e.g., bash, zsh, PowerShell).
Provide examples or notes for running the scripts in Linux/macOS shells, including any differences in variable syntax or command usage.
Mention common Linux/macOS editors (e.g., nano, vim) alongside Visual Studio Code, or refer to 'your preferred editor'.
If referencing PowerShell, provide equivalent bash/zsh syntax or note any differences.
Add a section or note confirming that all commands are cross-platform unless otherwise specified.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses UI navigation instructions that are tailored to the Azure portal, which is platform-agnostic, but it does not provide any command-line examples. There are no Linux-specific instructions, CLI commands, or references to cross-platform tools. The absence of CLI or Linux examples can disadvantage users who prefer or require non-GUI, scriptable, or Linux-based workflows.

Recommendations:

Add Azure CLI examples for creating or updating application settings, which work across Windows, Linux, and macOS.
Include PowerShell and Bash script examples for automation.
Explicitly mention that the Azure portal is accessible from any OS, and provide parity between GUI and CLI instructions.
Consider linking to documentation that covers both Windows and Linux workflows for managing app settings.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides instructions that reference the 'File System' logging option, which is primarily associated with Windows-based App Service plans. There is no mention of Linux-based App Service plans or their equivalent logging configuration, leading to a lack of parity for Linux users.

Recommendations:

Include instructions for configuring application logging on Linux-based App Service plans.
Clarify whether the 'File System' option is available or behaves differently on Linux versus Windows.
Provide alternative logging options or tools for Linux users, such as using Azure Blob Storage or Application Insights.
Add a note or table comparing logging features and configuration steps between Windows and Linux App Service environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page lists Windows-related pivots (Visual Studio, PowerShell, CLI, Azure Portal) before Linux equivalents, and includes a dedicated PowerShell section (a Windows-centric tool) without an equivalent for Linux shells. This ordering and tooling emphasis may signal a Windows-first bias and a heavier focus on Windows-native tools.

Recommendations:

Alternate the order of Windows and Linux pivots or group them together to avoid the perception of prioritizing Windows.
Add Linux shell (e.g., Bash) or cross-platform CLI examples where PowerShell is used, or provide a Linux shell equivalent pivot.
Ensure that Linux tools and workflows are given equal prominence and detail as Windows tools.
Consider a neutral, platform-agnostic introduction before splitting into OS-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both PowerShell and Azure CLI examples for scripting tasks, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform and more common on Linux/macOS). There are no Linux shell-specific examples or explicit mention of Linux environments, and PowerShell is given equal or greater prominence than Azure CLI, which may signal a Windows-first bias.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) where appropriate.
Add a short section or note for Linux/macOS users, clarifying that all Azure CLI steps are fully supported and providing any OS-specific tips if needed.
Consider including bash script examples or references for common Linux workflows, especially for tasks like environment variable assignment.
Reduce reliance on PowerShell-specific instructions or clarify that PowerShell Core is available cross-platform if its use is required.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently references Microsoft SQL Server and its client libraries (e.g., Microsoft.Data.SqlClient, mssql-jdbc, ODBC Driver 18 for SQL Server), which are Windows-centric or Microsoft-specific. The Python example assumes the presence of 'ODBC Driver 18 for SQL Server', which is not always available or straightforward to install on Linux. There are no explicit Linux-specific instructions, troubleshooting, or alternative driver suggestions. No PowerShell or cmd.exe examples are present, but the documentation implicitly assumes a Windows/Microsoft ecosystem.

Recommendations:

Add explicit instructions for installing ODBC Driver 18 for SQL Server on Linux and macOS, or mention compatible open-source alternatives (e.g., FreeTDS).
Include troubleshooting notes for common Linux issues (e.g., driver installation, environment variable differences).
Provide example connection strings or code snippets that work on Linux, including any required driver or authentication configuration differences.
Clarify cross-platform compatibility of all client libraries and tools mentioned.
Where possible, mention or link to documentation for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows a subtle Windows bias, primarily by referencing Windows first in quickstart links and not providing explicit Linux-specific instructions or examples for environment setup, deployment, or tooling. While the content is mostly cross-platform (Python/Flask), the quickstart and setup links default to Windows tabs, and there are no Linux shell or deployment examples, nor any mention of Linux-specific considerations.

Recommendations:

Ensure that quickstart and setup links default to neutral or Linux tabs, or provide both Windows and Linux options equally.
Add explicit Linux (bash) command-line examples for environment variable setup, deployment, and local development.
Mention Linux-specific tools or patterns (e.g., systemd for service management, Linux file paths) where appropriate.
Clarify that all steps are cross-platform, and call out any differences for Linux users.
Include screenshots or portal instructions that are not Windows-centric.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking to Windows-specific App Service pricing details and omitting any mention of Linux-specific scaling workflows, tools, or differences. There are no examples or guidance tailored for Linux-based App Service plans, nor are Linux-specific considerations or links provided.

Recommendations:

Include explicit guidance or notes for scaling Linux-based App Service plans, highlighting any differences or considerations.
Provide links to both Windows and Linux App Service pricing details and feature matrices.
Add examples or screenshots that show the experience for Linux-based App Service plans, if different.
Clarify in the documentation when instructions apply equally to both Windows and Linux, or call out platform-specific steps where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not explicitly mention or provide examples for Linux or cross-platform environments. All command-line instructions use Azure Developer CLI (azd), which is cross-platform, but there is no mention of Linux-specific considerations, nor are there any screenshots or guidance for Linux users. The use of .NET Blazor and App Service is not inherently Windows-specific, but the absence of Linux parity guidance or explicit cross-platform notes may leave Linux users underserved.

Recommendations:

Explicitly state that all CLI commands (azd, Azure CLI) work on Linux, macOS, and Windows, and provide any prerequisites or installation links for Linux users.
Include a note or section confirming that the sample app and deployment steps are fully supported on Linux and macOS, not just Windows.
Add Linux/macOS-specific troubleshooting tips or environment setup notes if there are any known differences (e.g., file permissions, path formats, shell differences).
If screenshots are shown, consider including at least one from a Linux desktop or terminal to reinforce cross-platform support.
Mention that Codespaces is a cloud-based, OS-agnostic environment, but also provide instructions for running the sample locally on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only Windows-based examples for the App Service plan and web apps (using azurerm_service_plan with os_type set to 'Windows' and azurerm_windows_web_app resources). There are no Linux equivalents or guidance for deploying Linux web apps, which may lead users to believe that only Windows is supported or recommended for this scenario.

Recommendations:

Include parallel examples using azurerm_linux_web_app and an App Service plan with os_type set to 'Linux'.
Add a section or note clarifying that the same architecture is supported for Linux web apps, with links to relevant documentation.
Provide guidance or code snippets for both Windows and Linux scenarios, or use variables to allow easy switching between OS types.
Ensure that any OS-specific configuration (such as app settings or site_config) is explained for both Windows and Linux web apps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to create integration environments using the Azure Portal GUI, with no mention of command-line options or automation via CLI tools. There are no examples or instructions for using cross-platform tools such as Azure CLI or Azure PowerShell, nor are there any references to Linux or macOS workflows. This implicitly prioritizes Windows/GUI usage patterns and omits guidance for users on Linux or those preferring automation.

Recommendations:

Add step-by-step instructions for creating integration environments using the Azure CLI, which is cross-platform and widely used on Linux.
Include equivalent Azure PowerShell commands, and clarify that Azure PowerShell is available on Linux and macOS as well as Windows.
Explicitly mention that all steps can be performed from any supported OS using the Azure CLI or PowerShell, not just via the Azure Portal.
Provide sample scripts or command snippets for both CLI and PowerShell to register the resource provider and create the integration environment.
Consider adding a section or callout for Linux/macOS users, ensuring parity in documentation and making it clear that the process is not Windows-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page uses Remote Desktop Protocol (RDP) as the sole example of interacting with a virtual machine via the data plane, which is a Windows-centric protocol. There are no Linux-specific examples (such as SSH), nor is there mention of Linux tools or patterns for interacting with Azure resources.

Recommendations:

Include Linux-specific examples alongside Windows ones, such as mentioning SSH for virtual machine access in addition to RDP.
When describing data plane operations, provide both Windows and Linux usage scenarios to ensure parity.
Avoid listing Windows-centric protocols or tools first or exclusively; instead, present both Windows and Linux options together.
Consider adding examples or references to command-line tools commonly used on Linux (e.g., curl, scp, SSH) when discussing data plane operations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent CLI or Linux-native examples (such as Azure CLI or ARM template snippets). There are no references to Windows-specific tools, but the exclusive use of PowerShell for code snippets and lack of Linux/CLI parity may disadvantage users on non-Windows platforms.

Recommendations:

Provide Azure CLI examples alongside PowerShell snippets for all configuration tasks, especially for enabling HTTP/2 support.
Include ARM template or Bicep examples where applicable to ensure cross-platform automation parity.
Explicitly mention that all configuration steps can be performed from any OS using the Azure CLI, and provide links to relevant CLI documentation.
Review the documentation for other sections where only PowerShell is used and add Linux-friendly alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides code examples and configuration guidance primarily for C# (.NET) and JavaScript, but when discussing configuration files and application settings, it references patterns and files (such as 'ConnectionStrings' in configuration files and 'local.settings.json') that are more familiar to Windows/.NET developers. There are no explicit Linux-specific examples, nor are there mentions of Linux-native tools or configuration patterns. The order of presentation also places .NET/C# examples before JavaScript, which may reinforce a Windows-first perspective.

Recommendations:

Include explicit Linux-oriented examples, such as referencing environment variables for connection strings, and demonstrate how to set these in Linux environments (e.g., using bash or export statements).
When discussing configuration files, clarify cross-platform applicability and provide Linux-specific guidance (e.g., how to set application settings via Azure CLI or environment variables in Linux containers).
Alternate the order of code examples or provide a neutral introduction to avoid reinforcing a Windows-first perspective.
Mention Linux-native tools or patterns where relevant, such as using environment variables or configuration management approaches common in Linux deployments.
Add a section or note on how to manage connections and configuration in Linux-based Azure Functions environments, including Docker/container scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page references associating Peer ASN to an Azure Subscription with a link to a PowerShell-specific guide (howto-subscription-association-powershell.md), but does not mention or provide equivalent instructions for Linux users (e.g., using Azure CLI or Bash). There is an implicit bias towards Windows/PowerShell tooling, and Linux-native methods are omitted.

Recommendations:

Add explicit instructions or links for associating Peer ASN using Azure CLI, which is cross-platform and commonly used on Linux.
Wherever PowerShell is referenced, ensure that equivalent steps for Bash/Azure CLI are provided and linked.
In the 'Related content' section, include links to guides that use Azure CLI or REST API, not just Azure Portal or PowerShell.
Review all prerequisite steps to ensure that no step assumes a Windows environment or tool by default.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page primarily uses Azure PowerShell commands for feature registration, with PowerShell examples shown first and in detail. The mention of Azure CLI (which is cross-platform and more common on Linux) is brief and lacks example commands, creating a Windows-first impression and making it harder for Linux users to follow along.

Recommendations:

Provide Azure CLI command examples alongside PowerShell examples for all feature registration and status-checking steps.
Present Azure CLI and PowerShell examples in parallel or with equal prominence, rather than prioritizing PowerShell.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Consider including bash shell script snippets or Linux terminal screenshots where appropriate to demonstrate parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references the use of a PowerShell cmdlet for deleting exchange peering, but does not provide equivalent instructions or examples for Linux users (e.g., using Azure CLI or REST API). No Linux-specific tools or cross-platform command-line examples are mentioned, and the only command-line reference is Windows-centric.

Recommendations:

Provide equivalent Azure CLI commands for managing exchange peering, including deletion, alongside PowerShell instructions.
Explicitly mention cross-platform tools (such as Azure CLI and REST API) in all procedural steps where PowerShell is referenced.
Add examples or notes for Linux/macOS users to ensure parity and inclusivity.
Where possible, present cross-platform (CLI/REST) examples before or alongside Windows/PowerShell examples to avoid Windows-first bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing a Linux equivalent. There are no Linux-specific instructions or examples, and the documentation implicitly assumes a Windows VM context.

Recommendations:

Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
Clarify that the instructions apply to both Windows and Linux VMs, or specify any differences if applicable.
Provide examples or notes relevant to Linux virtual machines, especially if there are any platform-specific considerations.
Use neutral language when referring to virtual machines, avoiding implicit assumptions that the user is working with Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking exclusively to Windows-specific documentation for the Azure Instance Metadata Service (IMDS), such as /azure/virtual-machines/windows/instance-metadata-service, and by referencing documentation tabs with '?tabs=windows'. There are no Linux or cross-platform examples, nor are Linux-specific links or guidance provided. This may make it harder for Linux users to find relevant information or feel equally supported.

Recommendations:

Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation, such as /azure/virtual-machines/linux/instance-metadata-service.
When referencing documentation with tabbed content (e.g., '?tabs=windows'), either use the default tab or explicitly mention both Windows and Linux tabs.
Add Linux-specific examples or notes where appropriate, especially if there are differences in usage or troubleshooting steps.
Ensure that all guidance and mitigation steps are applicable to both Windows and Linux users, or clearly indicate any platform-specific differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides generic ARM template instructions without explicit OS-specific steps, but it implicitly prioritizes Windows by omitting Linux-specific deployment examples or considerations. The only direct mention of Linux is relegated to the 'Next steps' section, while no Linux-specific guidance or examples are present in the main onboarding workflow.

Recommendations:

Add explicit Linux onboarding examples or notes within the main deployment instructions, not just as a link in 'Next steps'.
Include any Linux-specific considerations, such as supported distributions, required extensions, or troubleshooting tips, alongside Windows information.
Present both Linux and Windows guidance in parallel where relevant, ensuring parity in detail and visibility.
If there are differences in ARM template parameters or deployment steps for Linux VMs, document these clearly with examples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references Microsoft-centric workflow tools (Power Automate and Azure Logic Apps) and provides step-by-step instructions only for these platforms. There are no examples or mentions of Linux-native automation tools, CLI-based alternatives, or cross-platform scripting approaches. The documentation assumes use of graphical interfaces typical of Windows environments and does not address Linux users or their preferred tools.

Recommendations:

Include examples or references for integrating with Azure IoT Central using cross-platform tools such as Azure CLI, REST API (with curl or httpie), or open-source workflow engines (e.g., Apache Airflow, Node-RED).
Provide sample automation scripts or workflows that can be executed from Linux environments, such as Bash scripts or Python code using the Azure SDK.
Mention that Power Automate and Logic Apps are web-based and accessible from any OS, but clarify any OS-specific limitations or requirements.
Add a section or links for Linux users who may want to automate IoT Central integration without relying on Microsoft-specific workflow tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell example for consuming exported environment variables but does not include equivalent examples for Linux shells (e.g., Bash). There are no explicit references to Windows-only tools or patterns, but the lack of Linux/Unix shell examples may create a perception of Windows bias.

Recommendations:

Add equivalent Bash (and/or other popular Linux shell) examples alongside the PowerShell example for accessing environment variables in pipeline tasks.
Explicitly mention that the exported variables are accessible in all supported agent operating systems and provide cross-platform usage guidance.
Review screenshots and UI instructions to ensure they are not specific to Windows environments, or clarify when instructions are OS-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows-first bias by only referencing the Azure portal and .NET (a Microsoft-centric technology) for implementation, without providing examples or instructions for Linux users or alternative platforms. There are no CLI, Bash, or cross-platform code samples, and no mention of Linux-specific tools or workflows.

Recommendations:

Include Azure CLI and Bash examples for creating and managing chat completion configurations, ensuring Linux and macOS users are supported.
Provide code samples and implementation guides for additional languages and platforms, such as Python, Java, or Node.js, which are popular in Linux environments.
Explicitly mention cross-platform compatibility and note any OS-specific considerations.
Add links or references to documentation for using Azure App Configuration from Linux-based systems.
Balance .NET examples with equivalent open-source or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary alternative throughout. There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux environments or tools, which may lead to a subtle Windows bias, especially for users unfamiliar with PowerShell.

Recommendations:

Clarify that Azure CLI commands work cross-platform (Windows, macOS, Linux), and recommend CLI as the default for Linux/macOS users.
Consider listing Azure CLI examples before PowerShell, or labeling CLI as the preferred method for non-Windows users.
Add explicit notes or callouts for Linux/macOS users, reassuring them that PowerShell is optional and not required.
Optionally, provide Bash script examples or usage notes for Linux users, especially for common automation scenarios.
In the prerequisites, mention that Azure CLI is available on all major platforms, while PowerShell is primarily used on Windows (though cross-platform versions exist).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the Linux/macOS equivalent, and gives more detailed instructions for Windows users. While Linux/macOS is included, the ordering and emphasis favor Windows environments.

Recommendations:

Present environment variable setup instructions for all platforms together, or start with a neutral (cross-platform) example such as bash, then provide Windows-specific instructions.
Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
Consider using tabbed or side-by-side formatting for platform-specific commands to avoid implicit prioritization.
Review other sections for subtle Windows-first language or assumptions, and strive for parity in all platform-specific guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias by only linking to Python installation instructions for Windows in the prerequisites and not mentioning Linux or macOS setup. No Linux-specific examples or instructions are provided, and the only OS-specific resource is for Windows.

Recommendations:

In the prerequisites, add links to official Python installation/setup documentation for Linux and macOS alongside the Windows link.
Explicitly mention that the instructions and code samples are cross-platform and can be run on Linux, macOS, and Windows.
If there are any OS-specific considerations (such as environment variable syntax or CLI usage), provide examples for both Windows and Linux/macOS shells.
Consider adding a note or section confirming compatibility and any differences in running the samples on Linux/macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a bias toward Windows environments by focusing exclusively on ASP.NET Core (a Microsoft technology), referencing Docker Desktop (which is primarily a Windows/Mac tool), and omitting any Linux-specific instructions or examples. There are no PowerShell-specific commands, but the absence of Linux shell (bash) examples and the lack of mention of Linux-native Docker workflows or tools (such as Podman or native Docker on Linux) indicate a Windows-first approach. Additionally, the documentation does not address potential differences in environment variable syntax or file system paths between Windows and Linux containers.

Recommendations:

Include explicit instructions and examples for Linux users, such as using native Docker on Linux (not just Docker Desktop).
Mention and, where appropriate, provide bash shell command equivalents for all CLI instructions.
Clarify that the Dockerfile and deployment steps are cross-platform, and note any differences in file paths or environment variable syntax between Windows and Linux.
Add a section or callout for Linux users, highlighting any OS-specific considerations (e.g., file permissions, case sensitivity).
Consider including a sample using a non-Microsoft stack (e.g., a Python or Node.js app) to broaden applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, review, and cleanup steps. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific shell environments (such as Bash) or explicit Linux tooling. The use of PowerShell, which is traditionally associated with Windows, and the lack of Linux/Bash-specific context or examples, indicates a mild Windows bias. Additionally, the ordering of examples sometimes places PowerShell before or equally with CLI, rather than prioritizing cross-platform-first tools.

Recommendations:

Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and provide Bash-specific context where appropriate.
Consider providing Bash script examples or notes for Linux/macOS users, especially for steps like saving files or setting parameters.
If PowerShell is included, clarify that it is available cross-platform, but note that Bash is the default shell on most Linux distributions.
Where possible, lead with Azure CLI (which is cross-platform) and present PowerShell as an alternative, rather than as an equal or primary option.
Add a note in the prerequisites or deployment sections about shell compatibility and how to run the examples on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by listing Windows command prompt and PowerShell instructions before Linux/macOS equivalents in the environment variable setup sections. It also provides explicit PowerShell commands, which may not be as relevant for Linux/macOS users. However, Linux/macOS instructions are present and correct, and the rest of the documentation is generally cross-platform.

Recommendations:

Present environment variable instructions in a neutral or rotating order (e.g., Linux/macOS first in some sections, or group all OSes together).
Avoid giving Windows command prompt and PowerShell instructions precedence over Linux/macOS unless there is a clear user base justification.
Consider using tabbed or collapsible sections for each OS to give them equal prominence.
Where possible, provide cross-platform commands (e.g., using cross-env for npm scripts) or mention tools that work on all platforms.
Clarify that all examples work equally on Windows, Linux, and macOS, and link to OS-specific setup guides only as needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not provide any OS-specific examples, but it references .NET APIs and tools (such as ServicePointManager) that are traditionally associated with Windows environments. There are no Linux-specific troubleshooting steps, examples, or mentions of Linux tools or patterns. The guidance assumes a .NET/Windows-centric development environment, which may not be directly applicable to Linux users or those using other languages/platforms.

Recommendations:

Include troubleshooting steps and examples for Linux environments, such as checking ulimit settings, systemd service logs, or relevant Linux network configuration.
Mention cross-platform SDKs and tools (e.g., Azure CLI, Node.js SDK) and provide equivalent guidance for those environments.
Clarify when advice is specific to .NET/Windows and offer alternative steps for non-Windows users.
Add examples or notes for common Linux firewall configurations and how they might affect Azure Relay connections.
Reference platform-agnostic documentation or provide links to language-specific guides for non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Visual Studio (a primarily Windows-based IDE) for all development steps and does not mention or provide instructions for Linux users or alternative development environments. There are no examples or guidance for running or developing the .NET applications on Linux, nor are cross-platform .NET CLI instructions provided.

Recommendations:

Include instructions for setting up and running the .NET applications using the .NET CLI (dotnet new, dotnet run, etc.), which works on Linux, macOS, and Windows.
Mention and provide examples for using cross-platform editors such as Visual Studio Code.
Explicitly state that the tutorial can be followed on Linux and macOS, not just Windows.
Add notes or sections for any platform-specific considerations (e.g., how to open/close console windows, install .NET SDK on Linux).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias in the way environment variable instructions are presented. Windows Command Prompt and PowerShell commands are listed before Linux/macOS equivalents, and there is a dedicated prerequisite link for setting up Python on Windows but not for Linux. However, Linux/macOS commands are present and correct, and the code samples themselves are cross-platform.

Recommendations:

Present environment variable instructions for Linux/macOS before or alongside Windows instructions, or use tabs to separate platforms equally.
Add a link or note for setting up Python on Linux/macOS in the prerequisites, not just Windows.
Ensure parity in all setup and troubleshooting steps for both Windows and Linux/macOS users.
Consider using platform-agnostic language or grouping instructions by OS in a way that does not prioritize Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line instructions and setup steps that are platform-neutral in syntax (e.g., 'git clone', 'npm install', 'npm start'), but it does not specify or show any Linux/macOS-specific instructions, nor does it mention potential differences or prerequisites for Linux users. The use of 'cmd/sh' in code blocks is ambiguous and could confuse users about which shell to use. There are no explicit Windows-only tools or PowerShell commands, but the lack of Linux-specific guidance or troubleshooting constitutes a subtle 'windows_first' and 'missing_linux_example' bias.

Recommendations:

Explicitly state that the migrator tool and all commands work on Windows, Linux, and macOS, and mention any platform-specific prerequisites (e.g., how to install Node.js on Linux).
Use separate code blocks for Windows (cmd/PowerShell) and Linux/macOS (bash/sh) where commands or environment setup differ, or clarify that the commands are cross-platform.
Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable syntax, npm/node installation).
Clarify in the 'cmd/sh' code blocks which shell is expected, or provide both Windows and Linux/macOS variants if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed guidance for Linux TCP settings in one section, but the majority of code and client library examples focus on .NET/ASP.NET and the StackExchange.Redis library, which are primarily associated with Windows development. There are no explicit Linux or cross-platform code samples, and the only client library-specific recommendations are for Microsoft-centric technologies. There are no PowerShell or Windows tool references, but the guidance implicitly assumes a Windows/.NET environment by default.

Recommendations:

Include equivalent examples and recommendations for popular Linux/Unix Redis client libraries (e.g., redis-py for Python, Jedis for Java, node-redis for Node.js) alongside StackExchange.Redis.
Provide cross-platform code samples or explicitly mention how the patterns apply to non-.NET environments.
When discussing configuration or code patterns, avoid focusing solely on ASP.NET or Microsoft.Extensions packages; mention alternatives for other platforms.
If referencing platform-specific settings (like Linux TCP settings), consider also mentioning any relevant Windows settings or explicitly state if none are needed.
Add a table or section summarizing best practices for different operating systems and client libraries to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by presenting Windows Command Prompt and PowerShell instructions before macOS and Linux equivalents when setting environment variables. The Windows command is described as the default, with extra validation steps, and PowerShell is given a dedicated section. While Linux and macOS commands are present, they appear after the Windows instructions, and there is no explicit parity in validation or troubleshooting steps for non-Windows platforms.

Recommendations:

Present all OS instructions in parallel tabbed sections (Windows CMD, PowerShell, macOS, Linux) without ordering Windows first by default.
Ensure validation and troubleshooting steps are equally detailed for all platforms, not just Windows.
Avoid language that implies Windows is the default or primary development environment.
Where possible, provide cross-platform commands or highlight differences only where necessary.
Consider including a table summarizing environment variable commands for all platforms at once for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes both Windows command prompt and PowerShell commands, which may suggest a Windows-first and PowerShell-heavy approach. However, Linux/macOS instructions are present and complete. There are no exclusive references to Windows-only tools or missing Linux examples, but the ordering and emphasis may subtly favor Windows users.

Recommendations:

Present environment variable setup instructions in a neutral order, such as listing Linux/macOS (bash) first or grouping all OS instructions together without preference.
Avoid giving the impression of Windows primacy by using headings like 'On Windows', 'On macOS', 'On Linux' rather than listing Windows first.
Ensure that all command-line examples are equally detailed for all platforms, and consider providing cross-platform scripts or notes where possible.
Explicitly state that all steps are cross-platform unless a step is truly OS-specific.
Where possible, use platform-agnostic tooling or highlight alternatives (e.g., cross-platform editors, deployment tools) to reinforce parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation lists PowerShell (a Windows-centric tool) before Azure CLI (cross-platform) in both the quickstart table and 'Next steps' section, suggesting a subtle Windows-first bias. There are no explicit Linux-only examples or tools, but the ordering and inclusion of PowerShell may imply a preference for Windows environments.

Recommendations:

List Azure CLI before PowerShell in tables and 'Next steps' sections, as Azure CLI is cross-platform and more inclusive for Linux users.
Explicitly mention that Azure CLI works on Linux, macOS, and Windows to encourage non-Windows users.
Consider adding a Linux-specific example or note, such as using Bash or curl for event handling, to further improve Linux parity.
If PowerShell is included, clarify that PowerShell Core is available cross-platform, or link to instructions for installing it on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In the prerequisites section, the only tutorial linked for creating a user-assigned managed identity is specifically for Windows VMs, with no equivalent Linux guidance provided. There are no command-line examples (e.g., PowerShell, CLI, Bash), but the only deep-link for a step is Windows-specific, and Linux is not mentioned as an option.

Recommendations:

Add links to both Windows and Linux tutorials for creating user-assigned managed identities.
Wherever possible, provide cross-platform Azure CLI examples instead of or in addition to platform-specific guides.
Explicitly mention that the steps apply to both Windows and Linux, or clarify any platform-specific differences.
Review all prerequisite links and ensure Linux parity for all referenced setup guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses on using the Azure portal UI for configuration, which is platform-agnostic but visually and procedurally most familiar to Windows users. There are no command-line examples (PowerShell or otherwise), but the only CLI reference is a link to Azure CLI documentation, without any direct Linux or cross-platform command examples. There is no mention of Linux-specific workflows or screenshots, and the UI-centric approach may implicitly favor Windows users.

Recommendations:

Add explicit Azure CLI command examples for enabling and configuring Microsoft Entra ID authentication, demonstrating usage on both Windows and Linux terminals.
Include screenshots or terminal output from Linux environments to ensure parity.
If PowerShell or Windows-specific tools are referenced in other sections, ensure equivalent Bash or Linux-native instructions are provided.
Clarify that the Azure portal is accessible from any OS, and provide guidance for users who prefer CLI or automation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the instructions for setting environment variables. Windows command prompt and PowerShell commands are consistently listed before Linux/macOS equivalents, and explicit references to Windows tools (setx, PowerShell) are made. However, Linux/macOS commands are present and correct, and the main code samples are cross-platform JavaScript.

Recommendations:

Present Linux/macOS and Windows instructions in parallel or randomize the order to avoid always listing Windows first.
Use tabbed or side-by-side formatting for OS-specific instructions, so no platform is prioritized.
Where possible, use neutral language (e.g., 'On Windows, use... On Linux/macOS, use...') rather than always listing Windows first.
Consider referencing cross-platform tools (e.g., cross-env for setting environment variables in npm scripts) if appropriate.
Ensure all platform-specific instructions are equally detailed and visible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates mild Windows bias by referencing Windows-specific documentation first (e.g., password requirements link points to the Windows VM FAQ), and by mentioning password authentication (common for Windows) before SSH keys (common for Linux). However, both Windows and Linux images are mentioned as options, and SSH key guidance is provided for Linux users.

Recommendations:

Provide parallel links to both Windows and Linux documentation for password and username requirements.
Mention SSH public key authentication before password authentication, or present both options equally, to reflect Linux best practices.
Ensure that any referenced documentation or examples (such as password requirements) are OS-neutral or have both Windows and Linux variants.
Explicitly include example steps or screenshots for both Windows and Linux image deployments, if applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by recommending Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, without mentioning command-line or cross-platform alternatives. The Storage Explorer link specifically references a Windows tab. No Linux-specific or cross-platform CLI examples are provided for these steps, and there is no mention of Linux file upload or SAS generation workflows. However, the main configuration and encryption steps use Azure CLI, which is cross-platform.

Recommendations:

Provide Azure CLI or PowerShell (cross-platform) commands for uploading files to Azure Storage and generating SAS tokens, in addition to or instead of relying on Azure Storage Explorer.
Explicitly mention that Azure Storage Explorer is available for Linux and macOS, or provide links to platform-specific instructions.
Include Linux/macOS-specific instructions or examples for all steps involving file operations, such as uploading deployment packages.
Avoid linking only to Windows-specific tabs or instructions; ensure parity in documentation for all supported platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for creating and managing Azure Functions, but does not explicitly mention or provide Linux/macOS-specific shell commands or considerations. PowerShell is highlighted as an alternative to Azure CLI, which may be less familiar or relevant to Linux users. The order of presentation (CLI first, then PowerShell) is reasonable, but the presence of PowerShell throughout and lack of explicit Linux/macOS guidance or troubleshooting may create a subtle Windows bias.

Recommendations:

Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary shell-specific notes (e.g., quoting, environment variables).
Add a brief section or callout for Linux/macOS users, clarifying that PowerShell steps are optional and not required on those platforms.
Where PowerShell is mentioned, clarify its cross-platform availability, or provide bash/zsh equivalents if relevant.
Include troubleshooting tips or common issues for Linux/macOS environments (e.g., permissions, path issues) if applicable.
Consider adding a table or tabbed examples for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make parity explicit.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows by exclusively using Visual Studio Code and its Azure extension for deployment steps, without mentioning or providing alternatives for Linux users (such as CLI-based deployment or cross-platform tooling). There are no command-line examples, and all instructions assume the use of a GUI tool that is most commonly used on Windows. No mention is made of Linux-specific workflows or considerations.

Recommendations:

Include CLI-based deployment instructions using Azure CLI or GitHub Actions that work across Windows, Linux, and macOS.
Explicitly mention that Visual Studio Code and its extensions are cross-platform, or provide alternative instructions for users who may prefer terminal-based workflows.
Add examples or notes for deploying from Linux environments, such as using Bash scripts or terminal commands.
Ensure screenshots and step-by-step guides are not exclusively tied to Windows UI conventions.
Provide parity in documentation by showing both GUI and CLI approaches for all major steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and provides explicit PowerShell examples. While Linux/macOS commands are included, Windows tools and patterns are consistently mentioned first, which may subtly prioritize Windows users.

Recommendations:

Alternate the order of OS instructions (e.g., show Linux/macOS first in some sections, or group by OS rather than always leading with Windows).
Provide all OS instructions in parallel tabbed sections, so no OS is prioritized visually.
Avoid giving extra detail or emphasis to Windows-specific tools (e.g., 'setx', PowerShell) unless necessary; ensure parity in explanation for Linux/macOS equivalents.
Consider adding a summary table or section that lists all environment variable commands for each OS together for quick reference.
Where possible, use cross-platform commands or tools (such as Azure CLI) as the primary example, with OS-specific alternatives as secondary notes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by explicitly stating that the tutorial uses Windows and C#, and by instructing users to select Windows as the operating system in the setup steps. While it mentions that Linux is also supported, there are no Linux-specific instructions, examples, or screenshots. All configuration and deployment steps are described using the Azure Portal UI, with no command-line examples (such as Azure CLI, Bash, or PowerShell), but the default assumption is a Windows environment. There are no Linux-specific troubleshooting notes or guidance, and the runtime stack and deployment examples are focused on .NET/C# on Windows.

Recommendations:

Provide parallel instructions and screenshots for Linux users, including selecting Linux as the OS during Function App creation.
Include examples for other supported runtime stacks (e.g., Node.js, Python) and clarify any differences in networking or deployment for Linux-based Function Apps.
Add Azure CLI and/or Bash script examples for resource creation, configuration, and deployment, to support cross-platform and automation scenarios.
Explicitly call out any differences or considerations when using Linux, such as file system paths, supported features, or troubleshooting steps.
Ensure that language in the documentation does not default to Windows (e.g., 'This tutorial uses Windows but also works for Linux' could be reworded to be more neutral or to offer a choice at the start).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on signing into Azure via Visual Studio Code, a tool often associated with Windows workflows. There is no mention of alternative sign-in methods (such as CLI-based sign-in) that are commonly used on Linux, nor are there any Linux-specific instructions or screenshots. This may disadvantage Linux users who do not use Visual Studio Code or prefer command-line tools.

Recommendations:

Include instructions for signing into Azure using the Azure CLI (az login), which is cross-platform and commonly used on Linux.
Add screenshots or examples that show the process on Linux systems, or clarify that the process is the same across platforms if applicable.
Mention alternative editors or tools that Linux users may use, or provide parity in guidance for non-VS Code environments.
Explicitly state that Visual Studio Code is available on Linux, if relevant, and provide installation links or notes for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation consistently lists Windows PowerShell cmdlets before cross-platform Azure CLI commands in every example, and includes PowerShell-specific tooling throughout. This ordering and emphasis may signal a preference for Windows environments, potentially disadvantaging Linux or macOS users.

Recommendations:

Alternate the order of examples so that Azure CLI commands appear before or alongside PowerShell cmdlets.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Consider providing bash or shell script snippets for common tasks, especially in sections likely to be used by Linux users.
Add a brief note clarifying the platform compatibility of each tool (e.g., 'Azure CLI works on Windows, Linux, and macOS; PowerShell examples are primarily for Windows users').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for creating Azure resources, but PowerShell is mentioned alongside CLI as a primary tool, and the PowerShell example is given equal prominence. There are no explicit Linux-specific instructions or examples, and the use of PowerShell (which is traditionally associated with Windows, though now cross-platform) may suggest a Windows-centric approach. There are no examples of Linux-specific shells or tools, and no mention of platform-specific differences or considerations.

Recommendations:

Clearly indicate that both Azure CLI and PowerShell are cross-platform, but highlight that Azure CLI is often pre-installed or more common on Linux/macOS.
Provide explicit bash/zsh shell examples or notes for Linux/macOS users, especially for common tasks like environment variable setting or file navigation.
If PowerShell is shown, clarify that it is available on Linux/macOS, or provide alternative bash commands where appropriate.
Add a section or callout for Linux/macOS users, mentioning any platform-specific considerations (such as file paths, permissions, or installation steps).
Ensure that CLI examples are shown before PowerShell, as CLI is more universal across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias in the authentication examples for managed identities. Specifically, links and instructions for enabling and assigning managed identities on AKS clusters refer to Azure documentation sections that are explicitly for Windows Virtual Machine Scale Sets (VMSS), even though AKS clusters are typically Linux-based. There are no explicit Linux or cross-platform instructions or references for these steps, and the linked guides use Windows terminology and navigation. However, the rest of the documentation, including all YAML and CLI examples, is platform-neutral and uses standard Kubernetes and Azure CLI tools.

Recommendations:

Replace or supplement links to Windows VMSS documentation with links to platform-neutral or Linux-focused AKS managed identity guides, as most AKS clusters run on Linux nodes.
Explicitly clarify in the authentication sections that the instructions apply to both Linux and Windows node pools, or provide separate guidance for each if there are differences.
Where possible, reference Azure documentation that is not specific to Windows (e.g., use AKS managed identity docs rather than Windows VMSS docs).
Review all external documentation links to ensure they are not Windows-specific unless necessary, and provide Linux or cross-platform alternatives.
Consider adding a note at the beginning of the authentication section to clarify that the provider works with both Linux and Windows AKS clusters, and that the instructions are platform-agnostic unless otherwise stated.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing the Kudu console (which is Windows-centric in its UI and terminology) for package installation and file management. The instructions for running commands and uploading files are tailored to the Kudu interface, which is more familiar to Windows users. There are no alternative instructions for Linux-based workflows, such as using SSH, SCP, or Bash in the Azure Cloud Shell. Additionally, the use of 'CMD' in the Kudu console and the absence of Linux-native command-line examples or guidance further reinforce a Windows-first approach.

Recommendations:

Provide alternative instructions for Linux users, such as using Azure Cloud Shell (Bash) or SSH to interact with the function app's file system.
Include examples of using SCP or SFTP to upload files like package.json, in addition to the Kudu drag-and-drop method.
Clarify that Kudu is accessible from any OS, but explain the differences in command-line environments (CMD vs Bash) and provide Bash equivalents where appropriate.
Mention cross-platform tools and workflows explicitly, ensuring parity for both Windows and Linux users throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page discusses a Linux-specific error but suggests 'running on Windows' as the only alternative for timezone support, without providing Linux workarounds or parity. No Linux-specific solutions or examples are offered.

Recommendations:

Provide Linux-compatible alternatives or workarounds for timezone configuration, if available.
Offer examples or references for handling timezones on Linux hosting plans (e.g., using UTC or application-level timezone handling).
Avoid suggesting Windows as the primary or only solution; instead, present both Windows and Linux options equally.
Clarify any platform limitations and guide users to cross-platform best practices.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions that are generic but implicitly assume a GUI workflow typical of Windows environments, without mentioning or providing examples for Linux command-line alternatives or workflows. There is no reference to Linux tools or CLI-based deployment methods, which may be more familiar to Linux users.

Recommendations:

Include equivalent instructions for Linux users, such as how to perform the same actions using the Azure CLI or other command-line tools.
Explicitly mention that the steps apply to both Windows and Linux environments, or provide separate sections/examples for each.
Add screenshots or examples from Linux desktops or terminal sessions to ensure parity.
Reference Linux-friendly deployment patterns, such as using Git from the terminal, alongside GUI instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides instructions that are tailored to a graphical user interface (GUI) commonly associated with Windows environments, without mentioning equivalent steps for Linux users or command-line alternatives. There is no reference to Linux tools or terminal-based workflows.

Recommendations:

Include instructions for restarting the web app using the command line (e.g., Azure CLI, Bash) for Linux users.
Explicitly mention if the steps apply to both Windows and Linux, or provide separate sections for each platform.
Add screenshots or descriptions for Linux environments if the GUI differs, or clarify that the web portal is platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation describes using a right-click context menu to delete a resource group, which is a pattern typical of Windows GUI applications. There is no mention of equivalent actions for Linux users, such as command-line instructions or alternative interfaces.

Recommendations:

Include instructions for deleting a resource group using the command line (e.g., Azure CLI or Bash), which is platform-agnostic and accessible to Linux users.
If a GUI is required, clarify whether the instructions apply to cross-platform tools (such as VS Code) or are specific to Windows-only tools.
Provide Linux-specific or neutral examples alongside Windows GUI instructions to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently refers to 'Command Prompt', uses Windows-style paths (e.g., C:\My Fluid Projects, \src\App.js), and does not provide Linux/macOS equivalents for commands or file paths. There are no explicit Linux or macOS instructions or terminal examples, and all navigation and command-line instructions are written with a Windows-first perspective.

Recommendations:

Provide parallel instructions for Linux/macOS users, including using 'Terminal' instead of only 'Command Prompt'.
Use cross-platform path examples or show both Windows (C:\My Fluid Projects) and Unix-style (~/fluid-projects) paths.
Mention that all commands (npx, npm) work in any terminal (Command Prompt, PowerShell, Terminal, etc.) and are not Windows-specific.
Use forward slashes in file paths (src/App.js) or clarify that backslashes are for Windows and forward slashes for Unix-based systems.
Add notes or callouts where behavior might differ on Linux/macOS (e.g., environment variables, permissions, or port usage).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes use of the Azure portal's GUI, which is more commonly associated with Windows workflows. There are no examples or instructions for enabling streaming logs using command-line tools like Azure CLI or PowerShell, nor is there any mention of Linux-specific approaches or parity.

Recommendations:

Add instructions for enabling streaming logs using Azure CLI, which is cross-platform and commonly used on Linux.
Include PowerShell examples if relevant, but ensure they are presented alongside CLI/bash examples.
Explicitly mention that the steps apply to both Windows and Linux App Service plans, or clarify any differences.
Provide guidance for users who prefer command-line or automated approaches, not just portal-based workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation references copying the 'Git Clone Uri' for later use but does not provide any platform-specific instructions or examples. There is an implicit bias as there are no Linux/macOS-specific instructions or examples, and the lack of cross-platform guidance may lead users to assume a Windows-centric workflow.

Recommendations:

Add explicit instructions or examples for setting up a Git remote on both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash).
Include screenshots or command snippets for both platforms to ensure parity.
Clarify that the instructions apply to all platforms, or provide separate sections for Windows and Linux/macOS users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation instructs users to copy a connection string and paste it into a text file, implicitly assuming the use of a GUI and a text editor, which are more common in Windows environments. There are no examples or instructions for Linux users (e.g., using terminal commands or Linux-native editors), and no mention of cross-platform alternatives.

Recommendations:

Provide explicit instructions for both Windows and Linux users, such as how to copy and save the connection string using terminal commands (e.g., echo or cat) on Linux.
Mention cross-platform text editors (e.g., VS Code, nano, vim) instead of generically referring to a 'text file'.
Include screenshots or command-line examples for both Windows and Linux environments to ensure parity.
Avoid assuming a GUI workflow; offer CLI alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page describes a UI element that supports both Windows and Linux user names, but the only schema example provided specifies 'osPlatform': 'Windows'. There are no Linux-specific examples or validation patterns, and Windows is mentioned first in several places.

Recommendations:

Add a schema example that specifies 'osPlatform': 'Linux', including any Linux-specific constraints or validation patterns.
Provide sample output and validation messages for both Windows and Linux scenarios.
Ensure that descriptions and examples treat Windows and Linux equally, for example by alternating which platform is mentioned first or by presenting both together.
Clarify any differences in built-in validation logic between Windows and Linux user names.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation does not provide any explicit examples or guidance for Linux users. All references to uploading executables or scripts are generic, but the sample file names (e.g., ConsoleApp.zip, ConsoleApp1.zip) and terminology (e.g., 'executable') are strongly associated with Windows development. There is no mention of Linux shell scripts, Python, or other cross-platform script types, nor are there examples or notes about running WebJobs authored on Linux or using Linux tools.

Recommendations:

Include explicit examples for Linux users, such as uploading a .sh (shell script) or Python script, alongside .exe or .bat examples.
List supported file types with both Windows and Linux script formats (e.g., .exe, .bat, .cmd, .ps1, .sh, .py).
Provide sample file names and walkthroughs that use Linux-friendly naming and formats (e.g., myscript.sh, myjob.py).
Add notes or sections clarifying any differences or considerations when deploying WebJobs from Linux environments.
Ensure screenshots and instructions are not Windows-centric, or provide parallel Linux examples where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias, particularly in the sections discussing cryptography and authentication. Windows and Windows-specific tools (e.g., Windows FIPS validation, Windows Hello for Business) are mentioned explicitly and often before or instead of Linux equivalents. There are references to Azure being built with both Linux and Windows, but technical details and validation links focus on Windows modules. No Linux-specific examples, tools, or validation references are provided.

Recommendations:

Include explicit references to Linux cryptographic modules and their FIPS 140 validation status in Azure, alongside Windows.
When discussing authentication (e.g., Windows Hello for Business), mention Linux-compatible alternatives or clarify cross-platform support for FIDO2 and smartcards.
Provide links to documentation or guidance for configuring security and compliance features on Linux-based Azure VMs and services.
Ensure that examples and technical details are balanced between Windows and Linux, or are presented in a platform-neutral way where possible.
If certain features are only available or validated on Windows, clearly state this and provide guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page uses zone pivots to separate instructions for different Java stacks. However, for 'java-javase' and 'java-jboss', only Windows-based quickstart includes are referenced, while only 'java-tomcat' uses a Linux-based quickstart. This results in missing Linux examples for Java SE and JBoss, and Windows instructions are prioritized for these stacks.

Recommendations:

Provide equivalent Linux quickstart instructions for Java SE and JBoss stacks, not just Tomcat.
Ensure that for each Java stack (Tomcat, Java SE, JBoss), both Windows and Linux deployment examples are available and equally discoverable.
Review the included markdown files to confirm that Linux instructions are present and up-to-date for all supported Java stacks.
Consider restructuring the pivots or documentation flow so that Linux and Windows parity is clear and users can easily find instructions for their preferred OS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation focuses exclusively on deleting Azure Automation Run As accounts using PowerShell (a Windows-centric tool) and the Azure portal, without providing equivalent CLI or scripting examples for Linux users. There are no references to Bash, Azure CLI, or Linux-native tools, and the only command-line method mentioned is PowerShell.

Recommendations:

Add examples using Azure CLI (az) commands for deleting Run As accounts, which are cross-platform and commonly used on Linux.
Include Bash script examples where appropriate, or clarify that the steps are platform-agnostic if using the Azure portal.
Explicitly mention that PowerShell Core is cross-platform if PowerShell examples are retained, and provide installation guidance for Linux users.
Ensure that all command-line instructions are available for both Windows and Linux environments to improve accessibility and parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively focuses on creating a Windows web app, with no mention of Linux web apps or examples for Linux. All references, resource names, and verification steps are specific to Windows, and there is no guidance or parity for users interested in Linux-based web apps.

Recommendations:

Add a parallel section or quickstart for creating an Azure Linux web app with a backup using Terraform.
Where possible, generalize instructions and highlight differences between Windows and Linux web apps.
Provide verification steps and CLI commands for both Windows and Linux web apps.
Include notes or links to Linux-specific documentation for users who may want to deploy on Linux instead of Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references a procedure link that prioritizes CLI, PowerShell, and ARM template usage, but does not provide explicit Linux or cross-platform command-line examples. The 'Deploy to Azure' button leads to the Azure Portal, which is platform-agnostic, but the only procedural link mentions PowerShell before CLI and does not clarify Linux compatibility. There are no Linux-specific instructions or examples, and no mention of Bash or cross-platform scripting.

Recommendations:

Explicitly provide both Azure CLI (bash) and PowerShell examples for creating and managing alert rules, ensuring Linux users have clear, native instructions.
In procedural links and references, mention Azure CLI (bash) before or alongside PowerShell to avoid the appearance of Windows-first bias.
Add a section or note clarifying that all ARM template deployments and Azure CLI commands are fully supported on Linux, macOS, and Windows.
Where possible, include screenshots or walkthroughs using the Azure CLI in a Linux terminal environment.
Audit linked documentation to ensure Linux parity in all referenced procedures.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a preference for Windows tooling. No Linux-specific examples or tools are highlighted, and PowerShell is mentioned before the more cross-platform Azure CLI.

Recommendations:

List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, to avoid implying a Windows-only workflow.
Where possible, provide example commands for both PowerShell and Azure CLI in relevant sections, or link to both sets of instructions equally.
Consider adding a note or section highlighting Linux compatibility and common Linux tools for managing Azure resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively instructing users to create a Windows Server virtual machine and providing only Windows-based setup and screenshots. There are no instructions or examples for creating or using a Linux-based VM, nor are there any Linux-specific considerations or command-line examples. The documentation assumes a Windows environment for the VM used to access the Azure Function, which may not reflect the needs or preferences of all users.

Recommendations:

Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
Explicitly mention that either Windows or Linux VMs can be used for this scenario, and highlight any differences in setup or access.
Include examples of connecting to the VM using SSH (for Linux) as well as RDP (for Windows), and clarify how Azure Bastion supports both.
Where relevant, show command-line examples (e.g., using curl or wget on Linux) for invoking the Azure Function from within the VM.
Ensure that all steps, especially those involving the VM, are platform-agnostic or provide clear alternatives for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists a client setup example specifically for Windows 10, with no equivalent Linux or cross-platform client setup example. This suggests a Windows-first approach and omits guidance for Linux users, despite the cross-platform nature of many Azure and HPC environments.

Recommendations:

Add a Linux client setup example, demonstrating how to mount and use Avere vFXT from a Linux workstation.
Ensure that future documentation includes both Windows and Linux client instructions where relevant.
Consider providing cross-platform or platform-agnostic instructions where possible, or clearly indicate parity between platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific instructions or examples, which may lead Linux users to feel unsupported or unclear about the process.

Recommendations:

Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
Clarify that the instructions apply to both Windows and Linux VMs, or specify any differences if they exist.
Add a note or example demonstrating the process with a Linux VM, if there are any distinctions.
Ensure parity in documentation references and examples for both major operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references both Linux and Windows in a single section, but does not provide any concrete examples or details for either platform within the main content. However, the link to 'Automanage for Linux' is listed after 'Automanage for Windows Server', suggesting a subtle 'windows_first' ordering. There are no command-line examples, but the absence of any Linux-specific examples or tools in the main text constitutes a 'missing_linux_example' bias.

Recommendations:

Provide explicit examples for both Windows and Linux platforms within the main documentation, such as how to enable or customize Automanage profiles using platform-specific tools (e.g., PowerShell for Windows, Bash/CLI for Linux).
When listing platform-specific documentation or links, alternate the order or list Linux first in some cases to avoid implicit prioritization.
Include a table or section summarizing differences and supported features for both Windows and Linux, ensuring parity and clarity.
Reference Linux tools and patterns (such as cloud-init, shell scripts, or Linux security solutions) alongside Windows tools where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by explicitly recommending Windows as the operating system for the function app and not providing equivalent guidance or examples for Linux. There are no Linux-specific instructions, notes, or parity checks, and the only runtime stack mentioned is .NET, which is often associated with Windows. No PowerShell or Windows command-line tools are used, but the absence of Linux parity is notable.

Recommendations:

Provide explicit instructions and notes for both Windows and Linux hosting options, including any differences in configuration or limitations.
Include examples for creating and configuring the function app on Linux, and clarify if any steps differ.
Mention runtime stack options that are cross-platform (e.g., Node.js, Python) and provide sample code or notes for those.
If there are platform-specific recommendations (such as for best experience), explain the rationale and provide alternatives for Linux users.
Ensure screenshots and UI instructions are not Windows-specific, or clarify if the experience is identical on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific instructions or examples, and the only VM creation link is for Windows.

Recommendations:

Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
Explicitly state that the instructions apply to both Windows and Linux VMs, if applicable.
Provide examples or notes for any steps that may differ between Windows and Linux environments.
Ensure parity in documentation references and examples for both operating systems to avoid user confusion and improve inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows command prompt and PowerShell examples, which can be seen as a Windows-first and PowerShell-heavy approach. However, Linux/macOS instructions are present and not omitted.

Recommendations:

Present Linux/macOS instructions before or alongside Windows instructions, rather than always after.
Group all OS instructions together in a table or tabbed format to avoid implicit prioritization.
Ensure parity in tool recommendations; for example, mention cross-platform editors or CLI tools where relevant.
Where possible, use cross-platform language (e.g., 'terminal' instead of 'command prompt') and clarify that all platforms are equally supported.
Consider adding explicit notes that all steps are supported on Linux/macOS, and provide troubleshooting tips for those platforms if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates mild Windows bias by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# and HTTP test tools sections. Visual Studio (Windows-only) is presented as the primary environment for C#, with cross-platform options mentioned later. PowerShell is listed as an HTTP test tool before curl, which is more native to Linux. However, the page does provide parity in mentioning Linux and macOS support for Visual Studio Code and Core Tools, and does not omit Linux examples entirely.

Recommendations:

In C# sections, list Visual Studio Code and command-line/terminal options before Visual Studio, or group them together to avoid implying Windows-first development.
In HTTP test tools, list curl before PowerShell, as curl is more universal and native to Linux/macOS.
Wherever possible, provide explicit Linux/macOS command-line examples or screenshots alongside Windows ones.
Highlight cross-platform tools and workflows first, or equally, to reinforce Linux parity.
Explicitly mention Linux package managers (e.g., apt, yum, brew) for installing Core Tools and Azurite, not just npm or Windows installers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents or clarifying Linux support. There are no explicit Linux examples or references to Linux-specific best practices, tools, or configuration profiles. The only detailed configuration example (Guest configuration) is Windows-centric, and the documentation does not clarify how or if these best practices apply to Linux VMs.

Recommendations:

Explicitly state which services and best practices apply to Linux VMs and provide links to Linux-specific documentation where available.
For each service (e.g., Guest configuration, Antimalware), mention both Windows and Linux support, including any differences in onboarding, configuration, or available features.
Include examples or references for configuring and managing Linux VMs, such as using Linux security baselines or supported Linux antimalware solutions.
Where Windows-specific links are provided (e.g., Windows security baselines), provide parallel Linux resources (e.g., CIS benchmarks for Linux).
Clarify in tables and descriptions whether each feature or profile is available for Linux, Windows, or both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias, particularly in the local development instructions. Windows PowerShell is mentioned first, and Windows-specific commands (such as 'py -m venv .venv' and '.venv\Scripts\Activate.ps1') are listed before their Linux equivalents. The file path separator in the memory profiler output example also uses Windows-style backslashes. However, Linux alternatives are present, and there are no exclusive Windows-only tools or missing Linux examples.

Recommendations:

Present Linux and Windows instructions in parallel (side-by-side tabs or clearly separated steps) rather than listing Windows first.
Use neutral or platform-agnostic language, e.g., 'Open a terminal' instead of 'Open a Windows PowerShell or any Linux shell as you prefer.'
When showing commands, either provide both Windows and Linux/Mac commands together, or use tabs for each OS.
In code or output examples, use platform-neutral paths (e.g., <ProjectRoot>/HttpTriggerAsync/__init__.py) or show both Windows and Linux path formats.
Ensure that all steps and tooling are equally accessible and clear for Linux users, not just as an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the ordering and example presentation. In the X.509 self-signed authentication section, the openssl command is shown for Windows (PowerShell) before Linux (Bash), and the Windows command is not clearly marked as PowerShell-specific. There are no Linux-specific tools or patterns highlighted, and the documentation does not provide explicit Linux GUI or CLI examples outside of Azure CLI, which is cross-platform. The certificate generation and transfer steps mention Azure Key Vault and SCP, which are cross-platform, but no Linux-specific certificate management tools or workflows are highlighted.

Recommendations:

Present Linux and Windows command examples in parallel or alternate the order to avoid always listing Windows first.
Clearly label command blocks as 'Windows (PowerShell)' and 'Linux (Bash)' for clarity.
Include Linux-specific certificate management tips or references (e.g., using certbot, update-ca-certificates, or Linux file paths).
Where GUI steps are shown (e.g., Azure Portal screenshots), consider also providing CLI-only workflows for headless Linux environments.
Highlight that Azure CLI and IoT CLI extension are cross-platform, and provide example shell commands for both Bash and PowerShell where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Visual Studio (a primarily Windows-based tool) for C# class library functions and omitting any mention of Linux-specific tools, workflows, or command-line examples. All instructions are given via the Azure Portal UI, with no CLI or cross-platform automation examples. There are no Linux or macOS-specific instructions, nor are there alternatives to Visual Studio for non-Windows users.

Recommendations:

Include examples using Azure CLI and/or Azure PowerShell for all major steps (creating API Management instance, importing functions, downloading OpenAPI definitions) to provide parity for Linux and macOS users.
Mention cross-platform IDEs or editors (such as VS Code) alongside Visual Studio, and provide links or instructions for using them with Azure Functions and API Management.
Explicitly state that the portal-based workflow is platform-agnostic, but offer command-line alternatives for users who prefer or require non-GUI workflows.
If referencing Visual Studio, also reference equivalent workflows for Linux/macOS users (e.g., using VS Code or CLI tools).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally platform-neutral but exhibits subtle Windows bias in the cryptography/FIPS 140 section, where Windows and Windows-specific validation programs are mentioned before Linux. There is also a reference to 'Azure-specific version of Windows' and the 'Windows FIPS validation program' without equivalent detail for Linux. No command-line examples (PowerShell, Bash, etc.) are present, so there is no overt example bias, but the underlying platform references favor Windows.

Recommendations:

When discussing FIPS 140 validation, provide equal detail about Linux cryptographic modules and their validation status in Azure, not just Windows.
Reference both Windows and Linux as supported Azure operating systems in parallel, avoiding phrasing that puts Windows first or gives it more prominence.
If mentioning validation programs or modules, include links or references to Linux equivalents (e.g., OpenSSL FIPS validation in Azure Linux VMs).
Explicitly state that Azure supports both Linux and Windows for compliance scenarios, and provide parity in technical detail where applicable.
If future updates add command-line or configuration examples, ensure both PowerShell/Windows and Bash/Linux examples are included.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by defaulting the Azure Functions runtime OS to 'windows' in the Gradle configuration example, without mentioning Linux as an alternative or providing guidance for Linux users. Additionally, the documentation refers to the Azure portal and Azure CLI, which are cross-platform, but the explicit configuration for 'windows' as the runtime OS may lead Linux users to believe Windows is preferred or required.

Recommendations:

In the Gradle configuration example, explicitly mention that 'os' can be set to 'linux' as well as 'windows', and provide an example or note for Linux users.
Add a short section or note explaining the implications of choosing 'windows' vs 'linux' for the runtime, especially since Java 21 is supported on Linux only.
Ensure parity in instructions and examples for both Windows and Linux environments, particularly in configuration files and deployment steps.
If there are any OS-specific steps (such as setting JAVA_HOME), provide both Windows and Linux/macOS command examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is given equal prominence and is referenced in the 'Next steps' section. The final recommended tutorial specifically focuses on creating a PowerShell runbook, reinforcing a Windows-centric workflow. There are no explicit Linux shell examples or mentions of Linux-specific tools, but the CLI examples are cross-platform. However, the emphasis on PowerShell in both verification and next steps introduces a subtle Windows bias.

Recommendations:

Include explicit Bash/Linux shell examples where appropriate, especially in verification steps.
In the 'Next steps' section, provide a parallel tutorial for creating a Python or Bash runbook, not just PowerShell.
Clarify that Azure CLI commands work cross-platform and highlight this fact for Linux/macOS users.
If referencing PowerShell, also mention that PowerShell Core is cross-platform, or provide guidance for Linux users.
Consider adding a section or note on how to use the Automation account with non-Windows runbooks (e.g., Python, Bash).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally presents Windows and Linux options in parallel, but there are subtle biases: Windows is often mentioned first in tables and explanations, and some links (such as App Service plan rates) point to Windows-specific resources. There is also a lack of Linux-specific troubleshooting or deployment examples, and some App Service pricing links default to Windows. However, the page does acknowledge Linux container support and Linux-only features where relevant.

Recommendations:

Alternate the order of Windows and Linux mentions in tables and explanations to avoid always listing Windows first.
Ensure pricing and feature links reference both Windows and Linux resources, or provide a clear choice.
Add Linux-specific troubleshooting and deployment examples or links, especially where behaviors differ.
Where Windows-only features or limitations are mentioned, provide equivalent Linux information or explicitly state the Linux alternative.
Review all references to App Service plans and ensure Linux options are equally visible and accessible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-style file paths (e.g., C:/Users/john/Downloads/data.json, D:/abc.json) in all Azure CLI examples, and does not provide any Linux/macOS path examples. There are no explicit Linux or cross-platform command examples, and no mention of Linux-specific considerations. This may lead Linux/macOS users to feel the documentation is Windows-centric and less approachable.

Recommendations:

Provide both Windows and Linux/macOS path examples in CLI commands (e.g., use ~/Downloads/data.json or /home/user/data.json alongside C:/... examples).
Add a note clarifying that file paths should be adapted to the user's operating system.
Where relevant, mention any OS-specific considerations for Azure CLI usage (such as path separators or shell differences).
Consider including screenshots or terminal snippets from both Windows and Linux environments, or use neutral, cross-platform examples.
Explicitly state that Azure CLI is cross-platform and works on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples for running the Spring Boot app and testing with curl, but the curl example is given with a Windows command prompt (cmd) code block and no explicit Linux or cross-platform shell example. There are no PowerShell-specific commands or Windows-only tools, but the use of 'cmd' for curl and the lack of explicit Linux/macOS instructions or terminal screenshots suggest a subtle Windows-first bias. All Azure Portal instructions are platform-agnostic.

Recommendations:

Provide curl examples in both Windows (cmd) and Linux/macOS (bash/sh) formats, or use a generic 'shell' code block.
Explicitly mention that the Maven and curl commands work on Linux/macOS as well as Windows.
If showing command-line output or screenshots, include both Windows and Linux/macOS terminals.
Consider using platform-neutral code blocks (e.g., 'shell' instead of 'cmd') for commands that are cross-platform.
Add a note clarifying that all command-line steps are applicable to both Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is largely cross-platform and provides examples for multiple programming languages, but there are subtle signs of Windows bias. In several places, Windows command line (cmd) examples are provided alongside Bash, and references to 'command prompt' or 'cmd' often precede 'terminal' or 'Bash'. The use of 'func.exe' and references to MSI installers for upgrades are Windows-specific. The documentation also mentions Azure PowerShell and Azure CLI as required tools for publishing, listing PowerShell (a Windows-first tool) before CLI. However, Linux and macOS users are not excluded, and Bash/cURL examples are present.

Recommendations:

When providing command examples, always present Bash (Linux/macOS) and Windows (cmd/PowerShell) examples in parallel, and avoid listing Windows examples first by default.
Use neutral terminology such as 'terminal' instead of 'command prompt' or 'cmd', or mention both equally.
Where 'func.exe' is referenced, clarify that on Linux/macOS the executable is 'func'.
When discussing required tools, list Azure CLI before Azure PowerShell, or mention both together without preference.
Explicitly note platform differences in installation and usage steps, and provide links or instructions for Linux/macOS where appropriate.
Ensure that all cross-platform tools (like cURL) are introduced with equal weight for Linux/macOS and Windows, and avoid implying Windows is the default environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally cross-platform and Linux-friendly, with explicit statements that Python Functions run on Linux in Azure. However, there is a subtle Windows bias in the order and phrasing of some development and publishing guidance. Specifically, 'command prompt' is used as a synonym for 'terminal', and remote build is recommended 'when developing Python apps on Windows', with local build discouraged for Windows users. Visual Studio Code is emphasized, but that is cross-platform. There are no PowerShell-specific examples, and Linux is well-represented in hosting and deployment sections.

Recommendations:

Replace 'command prompt' with 'terminal' or 'shell' to avoid Windows-centric terminology. If both are meant, clarify with 'terminal (Linux/macOS) or command prompt (Windows)'.
When discussing remote vs. local build, explain the technical reasons for the recommendation, and provide equivalent Linux/macOS guidance, not just Windows.
Where possible, add explicit Linux/macOS CLI examples (e.g., bash/zsh) alongside any Windows-specific instructions.
Review all tool references (e.g., Visual Studio Code, Azure Functions Core Tools) to ensure installation and usage instructions are clear for both Windows and Linux users.
Consider adding a section or callout summarizing any platform-specific caveats for local development, so Linux users are equally informed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally aims for cross-platform neutrality, mentioning both Linux and Windows for tools like FIO and providing links to both Windows and Linux VM sizing. However, there is subtle Windows bias: the VM sizing section lists the Windows VM sizes link before the Linux equivalent, and there are no explicit Linux command-line examples (e.g., FIO usage on Linux), nor are there any Linux-specific screenshots or walkthroughs. The only API example uses curl, which is cross-platform but more common on Linux, yet there are no PowerShell or Windows CLI examples either. The 'Performance benchmarks for Linux' is relegated to a 'Next steps' link rather than being integrated into the main content.

Recommendations:

Provide explicit Linux and Windows command-line examples for running FIO or SSB, showing both platforms equally.
Alternate the order of Windows and Linux references (e.g., sometimes list Linux first).
Include Linux-specific screenshots or terminal output where appropriate.
Integrate Linux benchmarking guidance directly into the main content, not just as a 'Next steps' link.
If API examples are shown with curl, consider also showing PowerShell/Windows CLI equivalents for parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring customer-managed keys, but there is a notable emphasis on PowerShell, which is primarily a Windows tool. The PowerShell section is given equal prominence to the Azure CLI, despite CLI being cross-platform, and there are no explicit Linux shell (bash) or scripting examples. The documentation does not mention or demonstrate Linux-specific workflows or tools, and PowerShell is presented as a primary automation method alongside the CLI.

Recommendations:

Clearly state that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
Add explicit bash shell examples (where relevant) to show Linux-native scripting, especially for variable assignment and command chaining.
De-emphasize PowerShell as a primary automation method, or clarify that PowerShell Core is available cross-platform, but provide bash alternatives for Linux users.
Include a section or note for Linux users, highlighting any OS-specific considerations or confirming that all steps are supported on Linux.
Where screenshots or UI references are shown, clarify that the Azure Portal is OS-agnostic and accessible from any browser.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows client instructions (Windows Explorer and dir command) before Linux client instructions, and references Windows-specific concepts (Security Identifiers/SIDs) before UNIX equivalents (UIDs/GIDs). Windows tools and patterns are mentioned first in several places, and the 'Next steps' section links to Windows-specific documentation. However, both Windows and Linux examples are present, and Linux parity is generally maintained in technical content.

Recommendations:

Alternate the order of Windows and Linux client instructions in relevant sections, or present them in parallel to avoid implicit prioritization.
When introducing user/group identification, mention UNIX (UID/GID) and Windows (SID) concepts together, or start with UNIX when discussing NFS.
In 'Next steps', provide links to both Windows and Linux documentation for related concepts (e.g., link to Linux user/group management alongside Windows Security Identifiers).
Ensure that all example scenarios and screenshots are balanced between Windows and Linux clients.
Explicitly state that both Windows and Linux clients are supported and that instructions apply equally, where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a bias toward Windows by using Windows-specific device IDs (e.g., 'Windows109') in all JSON examples and does not provide any Linux-based examples or mention Linux-specific considerations. There are no explicit Linux or cross-platform command-line examples, and the only programming example uses .NET, which is more common on Windows. No PowerShell or Windows-only tools are mentioned, but the overall context and examples are Windows-centric.

Recommendations:

Include JSON examples with Linux-based device IDs (e.g., 'raspberrypi', 'ubuntu-edge') to demonstrate cross-platform applicability.
Add explicit notes or examples for Linux users, such as differences in file paths, environment variables, or troubleshooting steps.
Provide code samples in additional languages commonly used on Linux (e.g., Python, Node.js) alongside .NET.
Ensure that all instructions and screenshots are platform-neutral or provide both Windows and Linux variants where relevant.
Clarify that the Azure CLI and Visual Studio Code instructions apply equally to Linux, macOS, and Windows, and mention any platform-specific prerequisites if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes a Windows development environment by instructing users to create the project in Visual Studio and referencing .NET Framework, which is primarily Windows-only. There are no instructions or examples for creating the application on Linux or using cross-platform tools like .NET Core/SDK CLI. The NuGet package installation steps are also Visual Studio-specific, with no mention of command-line alternatives suitable for Linux.

Recommendations:

Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') for cross-platform compatibility.
Mention and provide steps for installing the NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay'), which works on Linux, macOS, and Windows.
Clarify whether the code is compatible with .NET Core/.NET 5+ and, if so, recommend using those frameworks for cross-platform support.
Include a note or section specifically for Linux/macOS users, outlining any differences or additional steps required.
Avoid assuming Visual Studio as the only development environment; reference VS Code or other editors where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references SQLPackage.exe and SQL Client Tools, which are traditionally Windows-based tools, without mentioning cross-platform or Linux-native alternatives. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify how to perform equivalent actions on Linux systems.

Recommendations:

Explicitly mention that sqlpackage is available as a cross-platform tool and provide installation instructions for Linux and macOS.
Include command-line examples for deploying DACPAC/BACPAC using sqlpackage on Linux (e.g., bash commands).
Avoid referencing only Windows-specific tools like SQLPackage.exe; instead, use 'sqlpackage' and clarify platform support.
If GUI tools are referenced (like Azure Data Studio), clarify their cross-platform availability.
Add troubleshooting steps and manual deployment instructions for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by referencing Windows shells (PowerShell and cmd) alongside Bash, and by providing specific instructions for PowerShell/cmd users after Bash examples. However, all code samples and primary instructions are written for Bash, and Linux is referenced positively (e.g., cloud-init for Linux VMs). There are no exclusive Windows tools or patterns, but the repeated need to clarify PowerShell/cmd differences and the order in which they are mentioned (Bash first, then Windows shells) indicates a subtle 'windows_first' and 'powershell_heavy' bias.

Recommendations:

Provide explicit Linux and macOS instructions/examples where relevant, not just Bash (e.g., clarify file path differences or shell-specific syntax).
Group shell-specific instructions together in a table or section, rather than always listing Bash first and then PowerShell/cmd as an afterthought.
Where differences exist, show parallel examples for Bash, PowerShell, and cmd, rather than focusing on Bash and adding Windows notes.
Highlight cross-platform compatibility and note any platform-specific limitations or behaviors.
Consider adding a section at the top clarifying that all examples are cross-platform unless otherwise noted, and link to platform-specific guidance if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page shows mild Windows bias by mentioning Azure PowerShell before Linux-friendly tools (such as Azure CLI) in the 'Required access' section, and by highlighting PowerShell as a primary automation interface. While the 'Next steps' section does list Azure CLI and Python, PowerShell is still given prominence in earlier sections. There are no explicit Linux shell examples or references to Linux-specific workflows, and the only command-line example in the limitations section uses Azure CLI, which is cross-platform.

Recommendations:

When referencing automation or scripting tools, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform and more familiar to Linux users.
Provide explicit Linux shell (bash) examples or note that Azure CLI commands work in both Windows and Linux environments.
Balance references to PowerShell and CLI throughout the documentation, not just in the 'Next steps' section.
Consider adding a brief note on cross-platform compatibility for each tool mentioned, especially in sections discussing automation or scripting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deployment commands and role assignment, but PowerShell (a Windows-centric tool) is often presented first or equally, and is highlighted in code snippets. There is no explicit mention of Linux or Bash, nor are there any Linux-specific considerations or examples. The documentation assumes familiarity with PowerShell, which may disadvantage Linux users.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
Present Azure CLI examples before PowerShell examples to avoid implicit Windows-first bias.
Add a brief note or section about running these commands in Bash or other Linux shells, especially for role assignment and deployment.
Where PowerShell is shown, clarify that it is primarily for Windows users, and provide equivalent Bash/Linux shell commands if any OS-specific steps exist.
Consider including screenshots or terminal prompts that reflect both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any OS-specific command-line examples, but when mentioning Infrastructure as Code (IAC) tools, it lists 'Azure CLI' and 'PowerShell' together, with PowerShell mentioned after Azure CLI. However, there are no explicit Linux-specific instructions, screenshots, or examples. All instructions reference the Azure Portal or generic Azure tools, but the lack of Linux/Unix shell examples or explicit mention of cross-platform command-line usage may make the documentation less approachable for Linux users.

Recommendations:

Include explicit examples using both Azure CLI (which is cross-platform) and Azure PowerShell, clarifying which commands work in Bash/Linux and which in PowerShell/Windows.
Add screenshots or instructions for performing tasks using the Azure CLI in a Linux shell environment.
Clarify that all steps can be performed on both Windows and Linux, and provide notes or links for Linux users where appropriate.
Where templates or scripts are referenced, provide sample commands for both Bash (Linux/macOS) and PowerShell (Windows), or indicate their cross-platform compatibility.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes using the Azure Portal (a web GUI) for all actions and does not provide any command-line examples. There is no mention of cross-platform CLI tools such as Azure CLI or Azure PowerShell. While the portal is cross-platform in theory, the lack of CLI examples means users on Linux (or those who prefer automation/scripting) are not served. Furthermore, there is no mention of Linux-specific workflows or parity with Windows tools, and the documentation implicitly assumes a GUI-first (and thus, often Windows-centric) workflow.

Recommendations:

Add Azure CLI examples for enabling, customizing, and approving JIT access, as Azure CLI is cross-platform and widely used on Linux.
If relevant, include Azure PowerShell examples and clarify that PowerShell Core is available on Linux, but prioritize CLI examples for parity.
Explicitly mention that all actions can be performed from any OS via the Azure Portal, but highlight automation options for Linux users.
Provide links to CLI reference documentation for managing JIT access in Azure Managed Applications.
Consider a dedicated section or callout for Linux/macOS users, emphasizing cross-platform tooling and scripting options.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively uses examples with 'adminUsername' values such as 'administrator' and 'adminUsername', which are strongly associated with Windows virtual machines. There is no mention of Linux equivalents (e.g., 'adminUser', 'root'), nor is there any example or guidance for Linux VM scenarios. The resource type used ('Microsoft.Compute/virtualMachines') can be for both Windows and Linux, but the admin username patterns and terminology are Windows-centric.

Recommendations:

Include examples that use Linux-typical admin usernames (e.g., 'adminUser', 'root', 'azureuser') to demonstrate parity.
Explicitly mention that the rule applies to both Windows and Linux VMs, and provide guidance for both.
Where adminUsername is referenced, clarify that the value and conventions differ between Windows and Linux.
Consider adding a table or section listing common admin usernames for both platforms and how to avoid literals in each case.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias, particularly in the PowerShell deployment examples and file path conventions. Azure PowerShell is featured as a primary deployment method, and all PowerShell examples use Windows-style (C:\) paths without Linux equivalents. Visual Studio Code is referenced as the main editor, but no mention is made of Linux-native editors or shells. There are no explicit Linux shell (bash) or cross-platform PowerShell Core examples, and file paths are not shown in a platform-neutral way.

Recommendations:

Provide Linux/bash equivalents for all PowerShell deployment examples, using bash syntax and Linux file paths (e.g., /home/user/templates/storage.bicep).
When showing file paths, use both Windows (C:\...) and Linux (/home/...) examples, or use platform-neutral notation.
Mention that Azure PowerShell and Azure CLI are both cross-platform, and clarify that PowerShell Core can be used on Linux/macOS.
Include examples using Linux-native editors (e.g., vim, nano) or at least acknowledge their use alongside Visual Studio Code.
Where Visual Studio Code features are described, note that they are available on all supported platforms.
Explicitly state that all commands and tools shown are available on Linux, and provide installation links or notes for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agent—all Windows-based backup solutions. There are no mentions of Linux-based backup agents, tools, or workflows, nor are there any examples or considerations for Linux environments. This creates a bias toward Windows and omits guidance for Linux users.

Recommendations:

Explicitly state whether Linux-based backup agents or tools are supported or not for offline backup workflows.
If Linux support exists, provide equivalent instructions, examples, and workflows for Linux environments (e.g., using Azure CLI, azcopy, or other cross-platform tools).
Include a comparison table row for OS/platform support, clarifying which options are available for Windows and Linux.
If only Windows tools are supported, note this limitation clearly and provide guidance or alternatives for Linux users.
Reference cross-platform utilities (such as AzCopy or Azure CLI) where possible, and provide sample commands for both Windows and Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure portal UI for all operational steps, which is more familiar to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-native tools or workflows. The guidance assumes use of graphical tools and omits parity for users who prefer or require command-line or automation approaches, which are common in Linux environments.

Recommendations:

Add step-by-step examples using Azure CLI for all major operations described (moving resources, finding original resource group, handling certificates).
Include PowerShell examples, but ensure Azure CLI (cross-platform) is presented first or equally.
Reference Bash scripting or automation scenarios for Linux users.
Explicitly state that all operations can be performed via CLI and provide links or inline examples.
Where screenshots are provided for the portal, consider also providing terminal output or code snippets for CLI equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure PowerShell and Azure CLI examples for managing resource locks, but it lists Azure PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform and more common on Linux). There is a slight Windows-first bias in the ordering of command-line examples. However, both PowerShell and CLI are covered in detail, and the CLI examples use Bash syntax, which is Linux-friendly. No exclusive use of Windows tools or missing Linux examples were found.

Recommendations:

Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is available cross-platform but is more familiar to Windows users.
Where possible, provide Bash and PowerShell command variants side by side, or clarify which shell the example is intended for.
Ensure that any references to tools or workflows are not Windows-specific unless necessary, and mention Linux/macOS compatibility where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally maintains cross-platform neutrality by focusing on Visual Studio Code and Azure CLI. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and in all such cases, PowerShell is always listed after Azure CLI (never exclusively or first). There are no explicit Windows-only tools or patterns, but the presence of PowerShell examples and references may be perceived as Windows-centric, especially since Linux-native shell examples (e.g., Bash) are not provided. All keyboard shortcuts are given in a cross-platform way (Ctrl/Cmd), and no Windows-only tools are promoted. There are no missing Linux examples, but the parity could be improved by explicitly mentioning Linux/macOS environments and shell usage.

Recommendations:

Where Azure CLI and PowerShell are both mentioned, consider explicitly stating that Azure CLI works natively on Linux/macOS/Windows, and PowerShell Core is cross-platform, to avoid the impression of Windows bias.
Add explicit references to Linux/macOS environments where relevant, such as mentioning that all commands work in Bash or zsh.
Provide example commands in Bash or zsh where appropriate, especially for common developer workflows.
In sections that mention keyboard shortcuts, clarify any differences for macOS users (e.g., Cmd vs Ctrl) if not already done.
Consider including a brief note or link about using the Azure CLI in Linux/macOS terminals to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page is largely a reference table listing Azure resource types and their support for move operations, with minimal platform-specific guidance. However, there are a few instances of Windows bias: (1) The only script explicitly referenced is a PowerShell script for Azure Automation account region moves; (2) The SQL VM move instructions link only to Windows-specific SQL IaaS Agent extension documentation, not mentioning Linux VMs or their process; (3) There are no CLI (az), Bash, or Linux-specific examples or links, and PowerShell is the only automation tool directly referenced.

Recommendations:

Where scripts or automation are referenced (e.g., for Azure Automation or SQL VM moves), provide both PowerShell and Azure CLI (az) examples, and clarify if the process is different for Linux.
For SQL VM move instructions, include guidance or links for both Windows and Linux SQL Server VMs, or clarify if the process is identical.
Wherever automation is referenced, mention cross-platform tools (such as Azure CLI or REST API) alongside PowerShell.
Add a general note in the 'Next steps' or introduction about cross-platform support, and link to platform-agnostic tools and documentation.
Audit referenced links to ensure they are not Windows-specific unless the feature is truly Windows-only, and clarify platform applicability where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and Azure CLI examples for all command-line operations, but PowerShell examples are consistently presented first. PowerShell is a Windows-centric tool, and its prioritization may suggest a Windows-first bias. However, Azure CLI examples (which are cross-platform and Linux-friendly) are present and equally detailed. There are no missing Linux examples, and no exclusive mention of Windows-only tools or patterns.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to better reflect cross-platform usage.
Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused (though available cross-platform).
Where possible, provide Bash script examples or clarify shell compatibility for CLI commands.
Consider adding a short section or note about cross-platform tool availability and usage to guide users on different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation consistently lists Azure PowerShell as a primary management option alongside the Azure portal and Azure CLI, and in several places, PowerShell is mentioned before the CLI. There are no explicit Linux-specific examples or references, and the documentation does not provide parity for Linux-native tools or workflows. While the Azure CLI is cross-platform, the ordering and emphasis on PowerShell may suggest a Windows-first perspective.

Recommendations:

Ensure that Azure CLI examples are always presented before or alongside PowerShell, as the CLI is cross-platform and more familiar to Linux users.
Add explicit Linux shell (bash) command examples where relevant, especially for common migration or management tasks.
Where PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent bash/CLI commands.
Include a note or section highlighting Linux support and any Linux-specific considerations or tools.
Review the ordering of management tool mentions to avoid consistently placing Windows-centric tools first.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web-based GUI) and not providing any command-line examples, such as Azure CLI or PowerShell. There are no Linux-specific instructions or examples, and no mention of how to perform these tasks from a Linux environment. The lack of CLI examples particularly impacts Linux users, who often prefer or require command-line interfaces over GUIs.

Recommendations:

Add Azure CLI examples for all major tasks (adding managed identities, configuring upstream settings, enabling authentication, etc.), as the CLI is cross-platform and widely used on Linux.
Explicitly mention that the Azure portal is accessible from any OS, but provide alternative instructions for users who prefer or require command-line tools.
If PowerShell is referenced in other related documentation, ensure that equivalent Azure CLI (bash-friendly) examples are always provided.
Include a section or callout noting that all features are available via CLI/automation, with links to relevant scripts or documentation.
Where screenshots are used, consider including CLI output or code blocks to supplement GUI steps.

Create pull request

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. There are no explicit Linux shell or Bash examples, and the focus is on tools and workflows (such as PowerShell and VS Code) that are more familiar to Windows users. However, Azure CLI is also mentioned, which is cross-platform, and there are no exclusive Windows-only commands or tools.

Recommendations:

Include explicit Bash or Linux shell command examples for exporting and deploying ARM/Bicep templates, not just Azure CLI and PowerShell.
When listing deployment methods, alternate the order or explicitly mention that Azure CLI and Bash are fully supported on Linux/macOS.
Provide examples or links for using the Azure Cloud Shell in Bash mode, not just PowerShell.
Mention cross-platform editors (such as Visual Studio Code) in a way that highlights their availability on Linux/macOS.
Ensure that all referenced tools and scripts are available and tested on Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-style file paths (e.g., 'c:\Templates\azuredeploy.json') in all code examples, including Azure CLI sections, without providing Linux/macOS alternatives. There are no explicit Linux/macOS examples or notes about path differences, which may confuse or hinder non-Windows users. While the CLI examples themselves are cross-platform, the path usage and lack of Linux-specific guidance create a Windows-centric bias.

Recommendations:

Provide both Windows and Linux/macOS file path examples in all code snippets, especially for Azure CLI commands (e.g., use 'c:\Templates\azuredeploy.json' and '~/Templates/azuredeploy.json').
Add a note early in the documentation clarifying that file paths should be adjusted for the user's operating system.
Wherever file paths are referenced in text or code, use OS-agnostic language or show both formats.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide shell-specific guidance if needed.
Review screenshots and instructions for any other Windows-specific assumptions (e.g., file explorer references) and provide Linux/macOS equivalents or clarifications.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by referencing 'Windows Azure Service Management API' in the registration section and mentioning the addition of apps to the 'Microsoft Entra tenant' by this API. Additionally, the PowerShell section appears before the Azure CLI section, which may suggest a prioritization of Windows-centric tooling over cross-platform or Linux-native tools. However, the page does provide Azure CLI and Python examples, which are cross-platform, and does not exclusively use Windows or PowerShell examples.

Recommendations:

Remove or clarify references to 'Windows Azure Service Management API' if not strictly necessary, or provide equivalent information for Linux/macOS users.
Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
Explicitly state that Azure CLI and Python examples are cross-platform and can be run on Windows, Linux, or macOS.
If mentioning tools or APIs with 'Windows' in the name, clarify their relevance (or irrelevance) to non-Windows users.
Consider adding a short section or note for Linux/macOS users if there are any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to configure service tags using the Azure Portal UI, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux-specific tools or workflows. This approach implicitly favors Windows users and omits guidance for users who prefer or require Linux-based or cross-platform automation.

Recommendations:

Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
If PowerShell examples are provided in other documentation, ensure Bash or Azure CLI equivalents are also included.
Explicitly mention that all steps can be performed from any OS using the Azure Portal, but provide links or examples for command-line automation.
Include a section or callout for Linux users, highlighting any differences or additional considerations.
Ensure screenshots and UI references are supplemented with command-line instructions for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias in the section on connecting to the VM, where it explicitly references RDP and links to Windows-specific connection instructions. The only example for connecting to the VM is via RDP, with no mention of SSH or Linux/macOS alternatives. Additionally, the link provided for connecting to a VM points to Windows instructions, reinforcing the Windows-centric approach.

Recommendations:

Provide parallel instructions for connecting to the VM using SSH, which is common for Linux and macOS users, alongside the RDP/Windows instructions.
Include a link to documentation on connecting to Linux VMs or using SSH clients on different platforms (Windows, Linux, macOS).
When referencing remote access, avoid assuming the user is on Windows; instead, present both RDP and SSH as options, or clarify which is appropriate for different guest OS types.
Ensure that all steps referencing tools or connection methods are platform-agnostic or offer alternatives for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by emphasizing ASP.NET Core and ASP.NET (both traditionally associated with Windows development) as the primary server-side frameworks for Azure SignalR Service. There is no mention of Linux-based server frameworks, nor are there examples or references to non-Windows development environments. The documentation also lacks explicit Linux or cross-platform setup or usage examples, which may leave Linux users underserved.

Recommendations:

Include explicit references to Linux and cross-platform server environments (e.g., running ASP.NET Core on Linux, using Docker, or deploying on Linux-based Azure App Services).
Provide examples or links for setting up and using Azure SignalR Service from Linux environments, including command-line instructions for both Windows (PowerShell/CMD) and Linux (Bash).
Highlight cross-platform compatibility of ASP.NET Core and SignalR, and clarify that development and hosting are supported on Linux, macOS, and Windows.
Mention and provide examples for non-.NET server-side frameworks or languages (such as Node.js, Java, or Python) where possible, to broaden the appeal and utility for non-Windows developers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks, but consistently lists PowerShell (a Windows-centric tool) alongside CLI, and sometimes before or equally with CLI. There are no Linux- or macOS-specific shell examples (e.g., Bash), and no mention of Linux-native editors or troubleshooting tools. The prerequisite section lists Visual Studio Code (cross-platform) but does not mention any Linux-specific alternatives or considerations.

Recommendations:

Explicitly state that Azure CLI commands work identically on Linux, macOS, and Windows, and consider showing CLI examples first to emphasize cross-platform parity.
Add Bash shell examples or notes for Linux/macOS users, especially for common deployment and troubleshooting workflows.
Mention Linux-native editors (such as Vim, Emacs, or Gedit) as alternatives to Visual Studio Code, or clarify that VS Code is cross-platform.
Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide Bash equivalents.
Ensure that troubleshooting steps and screenshots are not Windows-centric (e.g., avoid only showing Windows UI or file paths).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both PowerShell and Azure CLI deployment examples, but the PowerShell (commonly associated with Windows) example is given first, and the tab label is 'PowerShell' rather than 'Windows PowerShell', which may reinforce a Windows-first perspective. There are no explicit Linux-specific instructions, nor are there references to Linux tools or shell environments. The CLI example is cross-platform, but there is no mention of running it in Bash or Linux terminals, and the prerequisites section does not explicitly mention Linux support or alternatives.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform and widely used on Linux.
Explicitly mention that Azure CLI commands can be run in Bash or other Linux shells.
In the prerequisites, clarify that Visual Studio Code and Azure CLI are available on Linux, and provide links or notes for Linux installation.
Where PowerShell is mentioned, clarify that PowerShell Core is also available on Linux, or provide Bash equivalents for common tasks.
Consider adding a 'Linux' or 'Bash' tab for deployment examples, especially for users who may not use PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation references both Azure PowerShell and Azure CLI for troubleshooting, but consistently lists Azure PowerShell commands before Azure CLI equivalents. There is a slight emphasis on Windows-centric tools and patterns, such as Visual Studio Code and PowerShell, without explicit mention of Linux-specific workflows or editors. No Linux-specific examples or tools are provided.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid implicit prioritization.
Include explicit references to Linux environments, such as mentioning that Visual Studio Code and the Azure CLI are cross-platform.
Provide example commands for both PowerShell and Bash shells, especially for CLI usage.
Mention alternative editors or tools popular in Linux environments, such as Vim or Emacs, if relevant.
Clarify that all tools and commands are available on Linux, macOS, and Windows, and provide links to installation guides for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references Microsoft IIS Servers as backend VMs and demonstrates verification steps using Windows-centric tools (IIS, vSphere Client, Azure portal). There are no examples or mentions of Linux-based backend servers (such as Apache or Nginx), nor are there any Linux command-line or management tool instructions. This creates a Windows-first impression and omits guidance for users deploying Linux workloads.

Recommendations:

Include examples of configuring Linux-based backend servers (e.g., Apache, Nginx) as pool members in the Application Gateway.
Provide verification steps using Linux tools (such as SSH, curl, or Linux VM screenshots) alongside or instead of IIS/Windows examples.
Explicitly mention that both Windows and Linux VMs are supported as backend pool members, and link to relevant Linux setup documentation.
Balance screenshots and walkthroughs to show both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses the Azure portal UI for all configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows/Powershell bias, it also omits parity for Linux users who may prefer or require CLI-based instructions. Additionally, there is an implicit bias toward GUI-based workflows, which are more familiar to Windows users, and no mention of Linux tools or scripting approaches.

Recommendations:

Add Azure CLI examples for all major steps (creating virtual networks, gateways, ExpressRoute connections), as Azure CLI is cross-platform and widely used on Linux.
If PowerShell examples are added in the future, ensure equivalent Azure CLI/Bash examples are provided alongside.
Explicitly mention that all tasks can be performed using Azure CLI or ARM templates, and link to relevant documentation.
Include a section or callout for Linux/macOS users, highlighting cross-platform tools and approaches.
Consider providing downloadable sample scripts (in Bash/Azure CLI) for automating the configuration steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily presents platform-agnostic guidance but exhibits subtle Windows bias by referencing SQL Server documentation and best practices that are historically Windows-centric, and by not providing explicit Linux or cross-platform examples for configuration steps. Only at the end is Linux mentioned, and even then, only as a link out rather than as integrated guidance. There are no Linux-specific command-line examples or configuration snippets, and no mention of Linux tools or patterns for managing SQL Edge.

Recommendations:

Integrate Linux-specific configuration examples (e.g., editing mssql.conf using nano/vi, using systemd for service management).
Provide both Windows and Linux command-line examples for common tasks (such as setting memory limits, managing tempdb files, or configuring recovery models).
Reference Linux tools and patterns (such as using bash scripts, system resource monitoring with top/vmstat, or Docker commands on Linux).
Ensure that links to further reading include both Windows and Linux-focused documentation, or provide parity in the depth of guidance for both platforms.
Consider reordering sections so that Linux guidance is not relegated to the end, but is presented alongside or before Windows-centric information, reflecting the cross-platform nature of Azure SQL Edge.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing a security rule example that specifically targets Windows server sign-in failures, without offering a comparable example for Linux systems. The language and examples focus on Windows event IDs and scenarios, and there are no Linux-specific queries, event types, or operational guidance. While the documentation mentions 'operating system' in a generic sense, practical steps and detection logic are Windows-centric.

Recommendations:

Include parallel examples for Linux VMs, such as a KQL query for failed SSH logins (e.g., using Syslog data).
When demonstrating security rules, provide both Windows and Linux scenarios to ensure parity.
Explicitly mention that Microsoft Defender for Cloud and Sentinel support both Windows and Linux, and link to documentation for Linux event monitoring.
Add screenshots or walkthroughs that show Linux VM onboarding and monitoring, not just Windows.
In the 'Create rules to identify security threats' section, add a Linux-focused example (e.g., detecting repeated failed sudo attempts or SSH brute force attacks).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses generic terms like 'command prompt' and provides no explicit examples or instructions for Linux users. The navigation path uses backslashes (\), which is a Windows convention, and there are no mentions of Linux shells, terminals, or file path formats. There is also no mention of Linux-specific setup steps or troubleshooting, despite Azure SQL Edge being a cross-platform product.

Recommendations:

Explicitly mention both Windows and Linux environments in setup instructions.
Provide parallel examples for opening a terminal/command prompt on both Windows (Command Prompt/PowerShell) and Linux (Terminal/Bash).
Use platform-agnostic path separators (or show both Windows and Linux path formats).
Include Linux-specific notes for installing Git and navigating directories.
Add troubleshooting tips or environment notes for common Linux distributions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation repeatedly references Windows environments and workloads (e.g., AD domain controllers, Windows desktops, RDS), and does not provide Linux-specific deployment examples or guidance. While Linux is mentioned as a supported guest OS, there are no Linux-focused instructions, examples, or parity in the deployment, sizing, or architecture sections. The documentation assumes a Windows-centric environment and omits Linux-specific considerations, tools, or best practices.

Recommendations:

Include explicit Linux deployment examples for Horizon on Azure VMware Solution, such as provisioning Linux desktops or application servers.
Add guidance on integrating Linux authentication (e.g., LDAP, Kerberos) alongside or instead of Active Directory.
Provide Linux-specific sizing recommendations and performance considerations, referencing the linked 'System Requirements For Horizon Agent for Linux' within the main text.
Mention and link to Linux management tools or scripts where appropriate, not just Windows/AD-centric tools.
Ensure that any references to domain controllers, user profiles, or application delivery include both Windows and Linux scenarios.
Add a section or callout for Linux administrators highlighting any differences, limitations, or best practices when deploying Horizon for Linux workloads.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides configuration steps and examples only for the Azure Portal (a web UI) and Azure CLI, with no mention of Linux-specific command-line environments or tools. While Azure CLI is cross-platform, the documentation does not clarify this or provide any Linux-specific guidance, troubleshooting, or considerations. Additionally, the structure and language (e.g., references to the Azure Portal and UI navigation) may be more familiar to Windows users, and there is no explicit assurance of parity or instructions for Linux users.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary prerequisites or installation steps for Linux users.
Include example commands or troubleshooting notes relevant to common Linux shells (e.g., bash, zsh), such as variable syntax or command differences if any.
Add a section or note addressing Linux users, confirming that all steps are applicable and highlighting any OS-specific considerations (such as file paths, environment variables, or authentication methods).
Where UI navigation is described, clarify that the Azure Portal is web-based and platform-agnostic, to avoid the impression of a Windows-only workflow.
If any step has different behavior or requirements on Linux (e.g., handling of environment variables, use of tr or other utilities), provide explicit Linux examples or caveats.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Windows-based tools and drivers (such as ODBC Driver 17 for SQL Server and Azure Data Studio) and does not provide any Linux-specific instructions or alternatives. There is no mention of Linux-compatible drivers, nor are there installation or troubleshooting notes for Linux users. All connection strings and tool recommendations are Windows-centric, and there are no examples or guidance for Linux environments.

Recommendations:

Add explicit instructions for installing and configuring ODBC Driver 17 for SQL Server on Linux, including package manager commands for popular distributions (e.g., apt, yum).
Mention and provide links to Linux-compatible versions of Azure Data Studio, and clarify any differences in installation or usage.
Include troubleshooting notes for common Linux issues (e.g., driver library paths, permissions).
Provide example connection strings and code snippets that work on Linux, including any required environment variables or driver names.
Clearly state cross-platform compatibility and highlight any steps that differ between Windows and Linux.
If any steps are Windows-only, provide equivalent Linux alternatives or explicitly note the limitation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page shows subtle Windows bias by linking to PowerShell-based instructions before or alongside CLI and REST API options, and by referencing a PowerShell-specific guide for creating a Backup vault. There is no explicit Linux exclusion, but the presence and order of PowerShell links suggest a Windows-first approach.

Recommendations:

Provide direct links to both PowerShell and Azure CLI/Linux shell instructions for creating a Backup vault, ensuring CLI examples are not secondary.
When listing restore options, avoid listing PowerShell before CLI or alternate between them to avoid perceived priority.
Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) to reinforce parity.
If possible, include bash or shell script examples alongside CLI commands to demonstrate Linux compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to gather information and file a support request using the Azure portal's graphical interface, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, PowerShell, or REST APIs, nor is there mention of Linux or macOS workflows. This may disadvantage users who prefer or require command-line or non-Windows approaches.

Recommendations:

Add equivalent instructions and examples for gathering correlation IDs, error messages, and ExpressRoute IDs using Azure CLI and/or REST API, which are cross-platform and work on Linux, macOS, and Windows.
Explicitly mention that the Azure portal can be accessed from any modern browser on any OS, to clarify platform neutrality.
If PowerShell examples are provided in the future, ensure Azure CLI or REST API equivalents are also included.
Include a section or note for users who may be automating support data collection from Linux or macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally maintains cross-platform language and includes a Linux-based pool template example. However, in the section on file transfer, all CLI examples use Windows-style paths (e.g., c:\source_videos\*.mp4), with no Linux/macOS equivalents provided. This implicitly prioritizes Windows users and may confuse or exclude Linux/macOS users.

Recommendations:

For every CLI example using a Windows file path, provide a Linux/macOS equivalent (e.g., /home/user/source_videos/*.mp4).
When referencing file paths, use platform-neutral language or clarify that the syntax differs by OS.
Consider alternating the order of examples or presenting both Windows and Linux/macOS commands side by side.
Explicitly state that the Azure CLI and Batch CLI extension are cross-platform and provide links to OS-specific installation instructions if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page, while mentioning Linux in the title and description, focuses almost exclusively on Windows Server and SQL Server scenarios. All detailed examples, licensing explanations, and next steps are centered on Microsoft technologies, with no concrete examples, migration paths, or configuration guidance for Linux subscriptions. Linux is only referenced in passing, with no actionable content or parity in guidance.

Recommendations:

Add concrete examples and step-by-step instructions for applying Azure Hybrid Benefit to Linux subscriptions, including supported Linux distributions and scenarios.
Include Linux-specific migration guides and next steps, similar to the SQL Server and Windows Server sections.
Provide parity in technical depth for Linux, such as licensing requirements, supported workloads, and configuration steps.
Ensure that Linux tools and patterns are mentioned alongside Windows tools, not just in the introduction or as an afterthought.
Consider restructuring the documentation to give equal prominence to Linux use cases, rather than focusing almost exclusively on Windows/SQL Server.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates mild Windows bias by referencing PowerShell-specific syntax and issues before or more prominently than Linux equivalents. While the primary examples use Bash/Azure Cloud Shell, there are multiple notes and tips about PowerShell-specific line continuation and escaping, without providing equivalent Linux/Bash troubleshooting or tips. No Linux examples are missing, but the documentation assumes familiarity with Windows/PowerShell environments.

Recommendations:

Balance PowerShell-specific notes with equivalent Bash/Linux tips (e.g., mention common Bash pitfalls or escaping requirements).
If providing PowerShell-specific syntax advice, also provide explicit Bash/Linux advice where relevant.
Consider including a PowerShell example block if PowerShell is supported, or clarify that Bash is the recommended shell for these commands.
Review the order of tips and notes to ensure Linux/Bash is not always presented as secondary to Windows/PowerShell.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes installation and management using the Azure portal, VMware vSphere client, and 'Run command' features, all of which are GUI-based or Windows-centric enterprise tools. There are no CLI examples, scripts, or instructions for Linux environments, nor is there mention of Linux-based automation or management approaches. The documentation assumes use of Windows-style workflows and tools, omitting Linux-native alternatives.

Recommendations:

Provide equivalent CLI instructions for Linux users, such as using Azure CLI or PowerShell Core (cross-platform) for automation.
Include examples or references for managing the backup solution via SSH, shell scripts, or REST APIs that can be run from Linux systems.
Clarify whether the 'Run command' and vSphere client steps can be performed from non-Windows platforms, and if so, provide explicit instructions.
Add a section or callout for Linux administrators, highlighting any differences or additional steps required when operating from Linux environments.
If possible, provide sample automation scripts (Bash, Python, etc.) for installation, upgrade, and backup tasks.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is largely neutral and cross-platform, focusing on ARM template best practices with JSON examples. However, there is a subtle Windows bias in the references to the test toolkit's implementation and test cases. Specifically, the only direct link to a test case points to a .ps1 (PowerShell) script, and the toolkit cache and test case references are hosted in a Windows-centric (PowerShell) repository. There are also references to Windows and Linux in the context of VM images, but both are treated equally in those examples.

Recommendations:

Provide explicit instructions or examples for running the ARM template test toolkit on Linux/macOS, including any CLI commands (e.g., Bash, Azure CLI) in addition to or instead of PowerShell.
When linking to test cases or toolkit resources, ensure that cross-platform scripts or instructions are available and referenced (e.g., Bash scripts, or platform-agnostic instructions).
If the toolkit is only available as PowerShell scripts, mention any cross-platform compatibility (such as PowerShell Core on Linux/macOS) and provide installation/running instructions for those environments.
Where possible, avoid linking directly to .ps1 files as the only reference for test logic; provide documentation or markdown summaries of test logic that are platform-neutral.
Continue to ensure that all examples and explanations are not specific to Windows environments and that Linux/macOS users are not excluded or left to infer compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation mentions both Linux and Windows VMs as prerequisites and references both SMB (Windows) and NFS (Linux) protocols. However, when describing how to mount shares, it provides more detail and context for SMB/Windows (e.g., Active Directory setup) and only briefly mentions that NFS can be mounted on Linux using command lines or /etc/fstab, without providing explicit Linux command examples. There are no concrete Linux (mount) or Windows (map network drive) command examples, but the SMB/Windows workflow is described in more detail and appears first in the share mapping section.

Recommendations:

Add explicit Linux command-line examples for mounting NFS shares (e.g., mount -t nfs ... or /etc/fstab entry).
Provide parity by including Windows command-line or GUI steps for mapping SMB shares, if not already present.
Present Linux and Windows instructions side-by-side or in parallel sections, rather than listing Windows/SMB first.
Ensure both Linux and Windows tools, commands, and workflows are described with equal detail and prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing Windows VM creation in the introductory section and providing a detailed, step-by-step Windows agent installation process before mentioning Linux. Linux instructions are less detailed and lack direct package commands or examples. Throughout the guide, there is a lack of parity in practical Linux examples, and the initial VM creation link points only to Windows VMs.

Recommendations:

Provide parallel links and references for both Windows and Linux VM creation in the introduction (e.g., link to both /azure/virtual-machines/windows/quick-create-portal and /azure/virtual-machines/linux/quick-create-portal).
Ensure that all instructions and examples (such as agent installation) are equally detailed for Linux, including explicit package manager commands (e.g., 'sudo apt install walinuxagent' or 'sudo yum install WALinuxAgent').
Where screenshots or UI steps are shown, clarify that the process is identical for both Windows and Linux VMs, or note any differences.
Include troubleshooting or verification steps for Linux agent installation, similar to the Windows example (e.g., checking the agent version with 'waagent --version').
Review the documentation for any other implicit prioritization of Windows and ensure Linux users are equally supported throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by referencing PowerShell-specific syntax and considerations before Linux/Bash equivalents, and by providing tips for PowerShell users while assuming Bash as the default. However, it does provide Bash-first CLI examples and does not omit Linux-specific instructions, but the presence of PowerShell notes and the order of browser support listings suggest a subtle prioritization of Windows environments.

Recommendations:

Provide explicit Linux and macOS instructions and examples alongside Windows/PowerShell, not just as notes.
List browser and tool support in a neutral or alphabetical order rather than putting Microsoft/Windows options first.
Where line continuation or command syntax differs between shells, show both Bash and PowerShell examples side by side.
Include references to common Linux tools (e.g., curl, jq) where relevant, not just Azure CLI.
Explicitly mention Linux and macOS compatibility in prerequisites and environment setup sections.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation contains a subtle Windows bias, notably by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the baseline for backup scheduling and retention. There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned as the default tool, which may not be familiar or available to Linux users. However, the main focus of the documentation is on REST API usage, which is platform-agnostic. No shell-specific (cmd, PowerShell, bash) command-line examples are provided, but the only tool mentioned by name is PowerShell.

Recommendations:

Remove or rephrase references to 'default PowerShell object' to avoid implying PowerShell is the primary or only supported tool.
If referencing default objects or tools, clarify their cross-platform availability or provide equivalent examples for Linux (e.g., Azure CLI, Bash, or SDK usage).
Add a section or note highlighting that the REST API can be used from any platform, and provide example invocations using curl (Linux/macOS) and PowerShell (Windows), ensuring parity.
Where possible, provide sample scripts or commands for both Windows (PowerShell) and Linux (bash/curl) to demonstrate REST API usage in a cross-platform manner.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for configuration steps and does not provide any command-line examples. While the Azure CLI is mentioned as a next step for restore operations, there are no CLI, PowerShell, or shell-based instructions for the backup configuration process itself. This approach implicitly favors Windows users, as the Azure Portal is often the default for Windows-centric workflows, and omits parity for Linux users who may prefer or require CLI-based automation.

Recommendations:

Add step-by-step instructions for configuring AKS backup using the Azure CLI, including all relevant commands.
If PowerShell examples are provided elsewhere, ensure equivalent Bash/shell examples are included.
Explicitly mention that the Azure CLI is cross-platform and provide links or code blocks for both Windows and Linux environments.
Include a table or section comparing portal, CLI, and (if applicable) PowerShell methods for configuring AKS backup.
Ensure screenshots and examples are not exclusively from Windows environments; include CLI output from Linux terminals where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page generally maintains cross-platform language and highlights Linux and MCU support, but it references the 'proven reliability of the Windows Update platform' as a foundational technology without mentioning Linux update mechanisms. There are no explicit Windows/Powershell examples or exclusive Windows tools, but the only platform-specific technology mentioned in the context of reliability and scale is Windows Update, which may imply a Windows-first perspective.

Recommendations:

Acknowledge the reliability and prevalence of Linux update mechanisms (such as APT, RPM, or Yocto-based OTA solutions) alongside Windows Update when discussing the foundational technologies behind Device Update.
Include references or examples of how Device Update leverages or integrates with common Linux update workflows, not just Windows.
Ensure that any mention of platform reliability or scale includes both Windows and Linux to avoid implying that Device Update is primarily based on Windows technologies.
If referencing Windows Update as a model, provide a parallel statement about Linux update systems to reinforce cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists several Azure Resource Manager and Bicep templates for backup scenarios, but it demonstrates a Windows bias by explicitly providing a template for deploying a Windows Server VM with backup enabled, while not offering an equivalent example for Linux VMs. There are no Linux-specific backup scenarios or templates mentioned, and the only OS-specific example is for Windows.

Recommendations:

Add examples and templates for deploying and backing up Linux VMs, ensuring parity with the Windows Server VM example.
Explicitly mention support for both Windows and Linux VMs in relevant templates, or clarify any OS-specific limitations.
Where OS-specific templates are provided (e.g., for Windows Server), provide a corresponding Linux example immediately after or alongside.
Review descriptions to ensure they are OS-neutral unless a feature is genuinely Windows-only, and clearly state such limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias, particularly in the 'Copy and paste' section, which explicitly references only Windows VMs and links to a Windows-specific guide. There is no mention of Linux VMs or examples for Linux users in this context. Other sections are more neutral, but the lack of Linux parity in key feature explanations is notable.

Recommendations:

Include equivalent documentation and examples for Linux VMs, especially for features like copy/paste and file transfer.
Update references and links to cover both Windows and Linux scenarios, or clarify if a feature is not supported on Linux.
Where features differ between platforms, provide side-by-side instructions or a comparison table.
Ensure that introductory text and feature descriptions do not assume a Windows environment by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

Summary:

The documentation demonstrates a Windows-first bias by referencing Windows OS families and configurations in detail, providing explicit mapping to Windows Server versions, and including a dedicated section for Windows-specific configuration (windowsConfiguration). Linux-specific configuration is only mentioned indirectly (e.g., by exclusion), and there is no equivalent Linux configuration section or detailed mapping for Linux OS images. Additionally, the deprecated 'cloudServiceConfiguration' is exclusively Windows-based.

Recommendations:

Add a 'linuxConfiguration' section parallel to 'windowsConfiguration', describing available Linux-specific settings for virtual machines.
Include explicit examples and documentation for Linux OS images, such as common publishers/offers/SKUs for popular Linux distributions.
Where OS families or versions are discussed, provide equivalent Linux information (e.g., mapping of common Linux image references, links to Linux release notes).
When referencing documentation for VM sizes, ensure Linux and Windows links are presented together or Linux-first, not Windows-first.
Clarify in notes and tables when a property is Windows-only, and provide Linux alternatives or state explicitly when Linux does not require a setting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and Azure PowerShell examples for all CLI operations, but PowerShell is consistently presented as an equal alternative rather than a secondary or optional one. In the prerequisites, both Bash and PowerShell are listed, but it is noted that Python, JavaScript, and Java samples require Bash. However, PowerShell examples are still provided for all CLI steps, which may suggest a slight Windows bias by giving PowerShell parity with Bash even when Bash is required for the main language samples. Additionally, PowerShell is mentioned before Bash in the prerequisites, and PowerShell-specific variable syntax and command formatting are used throughout.

Recommendations:

Clarify that Bash is the primary supported shell for non-.NET SDKs and that PowerShell examples are optional or secondary.
Present Bash examples first in all code tabs and sections, especially since most SDK samples require Bash.
Explicitly note any limitations of PowerShell usage with the SDKs (e.g., if certain language samples cannot be run in PowerShell).
Consider reducing the prominence of PowerShell examples or moving them to an appendix or 'Windows-specific' section to avoid implying equal support.
Ensure that all instructions and environment variable usage are cross-platform and avoid Windows-centric patterns unless necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates mild Windows bias by referencing Windows command shells and tools before or in preference to Linux equivalents. For example, it mentions using Windows cmd.exe as an alternative to Bash, and in several places, it provides Windows-specific instructions (such as using 'set' instead of 'export') before or alongside Linux commands. Additionally, the Java quickstart uses a Windows-style 'cmd' code block for directory creation, even though the rest of the instructions are cross-platform.

Recommendations:

Present Linux and Windows command instructions in parallel, using tabbed or side-by-side formatting, rather than mentioning Windows as an alternative to Bash.
When referencing environment variable setting (e.g., 'export' vs 'set'), provide both commands explicitly in a tabbed or clearly separated format, rather than as a parenthetical note.
For directory creation and navigation, use cross-platform commands (e.g., 'mkdir', 'cd') in a neutral shell format, or provide both Bash and cmd/PowerShell equivalents.
Avoid using Windows-specific code block annotations (e.g., 'cmd') unless absolutely necessary; prefer 'bash' or a neutral format.
Ensure that any references to tools or shells do not assume Windows as the default or primary environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_reference

Summary:

The documentation is largely cross-platform and focused on Azure CLI, which is available on both Windows and Linux. However, there is a subtle Windows bias in the form of referencing PowerShell documentation before Linux alternatives, and linking to Windows-specific VM documentation in some places. No Linux-specific examples or tools are missing, but the only alternative to CLI mentioned is PowerShell, and the link to zone-pinned VMs references a Windows VM creation page.

Recommendations:

When referencing alternative automation tools, mention both PowerShell and Bash (or shell scripting) guides if available, or clarify that CLI commands are cross-platform.
When linking to VM documentation (e.g., for zone-pinned VMs), provide links to both Windows and Linux VM creation guides.
Explicitly state that all CLI examples work on both Windows and Linux, and consider including a note or section for Linux users if there are any OS-specific considerations.
If referencing PowerShell for automation, also mention Bash scripting or provide a link to a Linux automation guide if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page discusses backing up SAP ASE (Sybase) databases on Azure VMs but implicitly assumes a Windows-centric environment in several places. For example, when referencing VM creation, it links specifically to the Windows VM creation guide and does not mention or link to Linux VM equivalents. There are no explicit examples or instructions tailored for Linux-based ASE deployments, despite Linux being a common platform for SAP ASE. There is also no mention of Linux-specific tools, commands, or considerations, and no PowerShell or Windows-specific commands are shown, but the omission of Linux content is notable.

Recommendations:

Provide parallel instructions and links for both Windows and Linux VM creation and management, especially when referencing Azure VM documentation.
Explicitly mention supported operating systems for SAP ASE on Azure VMs, and clarify any differences in backup procedures or prerequisites between Windows and Linux.
Include Linux-specific examples, such as using Bash or Linux shell commands for running the preregistration script, and note any OS-specific requirements (e.g., permissions, package dependencies).
When referencing Azure documentation, provide both Windows and Linux links where relevant (e.g., quick-create guides for VMs).
If the solution is OS-agnostic, state this clearly to reassure Linux users that the instructions apply equally to their environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by only providing next steps and connection instructions for Windows virtual machines. There are no examples or links for deploying or connecting to Linux VMs via Azure Bastion, and the 'Next steps' section exclusively references Windows workflows.

Recommendations:

Add parallel 'Next steps' links for Linux virtual machines, such as 'Quickstart: Create a Linux virtual machine in the Azure portal' and 'Create an SSH connection to a Linux VM using Azure Bastion'.
Include example values or screenshots for Linux VM deployments where relevant.
Ensure that instructions and examples throughout the page are platform-neutral or provide both Windows and Linux options where applicable.
Review related documentation to ensure Linux users have clear, accessible guidance for using Azure Bastion with their workloads.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides generic instructions for connecting to a VM scale set using Azure Bastion, but implicitly assumes a Windows-centric workflow by referencing RDP (a Windows protocol) and omitting any mention of Linux connection methods (such as SSH). There are no examples or guidance for connecting to Linux-based VM instances, nor are Linux tools or workflows mentioned.

Recommendations:

Include explicit instructions and examples for connecting to Linux VM instances using SSH via Azure Bastion.
Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux), and provide guidance for both scenarios.
Add screenshots or step-by-step guidance that demonstrates the SSH connection workflow for Linux users.
Ensure that terminology and steps are platform-neutral or that both Windows and Linux workflows are presented in parallel.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking only to the Windows VM creation guide and the Windows RDP connection guide, without mentioning or providing equivalent Linux VM or SSH connection documentation. There are no Linux-specific examples or references, which may make Linux users feel unsupported or overlooked.

Recommendations:

Include links to both Windows and Linux VM creation guides in the deployment overview step.
Provide guidance or links for connecting to Linux VMs via SSH using Azure Bastion, alongside the existing RDP/Windows instructions.
Ensure that all examples and references cover both Windows and Linux scenarios equally, or explicitly state when instructions are applicable to both.
Consider adding a section or FAQ entry addressing Linux VM connectivity and any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is exclusively focused on Windows virtual machines, with all instructions, prerequisites, and examples tailored to Windows. There is no mention of Linux VMs, nor are there any Linux-specific instructions or considerations. This creates a strong Windows-first bias and omits Linux parity.

Recommendations:

Add a parallel section or a separate article for Linux VMs, detailing how copy and paste works with Azure Bastion when connecting to Linux virtual machines.
Include Linux-specific prerequisites (e.g., supported distributions, required desktop environments, or RDP/SSH client considerations).
Provide examples and screenshots demonstrating the copy and paste process on Linux VMs, including any differences in keyboard shortcuts or clipboard behavior.
Clarify any limitations or differences in feature support between Windows and Linux VMs when using Azure Bastion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally avoids platform-specific instructions or examples, but the only explicit OS-specific mention is for Windows pools in the 'Node OS updates' section. There are no Linux-specific instructions, examples, or parity notes. No shell or PowerShell commands are shown, but the only OS-specific configuration (automatic updates) is described for Windows, with no mention of Linux equivalents or differences.

Recommendations:

Add a section or note describing how OS updates are handled for Linux pools, including default behaviors and configuration options.
Wherever Windows-specific behaviors or properties are mentioned (such as 'enableAutomaticUpdates'), include equivalent information for Linux pools, or explicitly state if not applicable.
If there are differences in troubleshooting steps, log file locations, or node management between Windows and Linux pools, provide parallel guidance or examples.
Consider including at least one example error or scenario that is specific to Linux pools to demonstrate parity and awareness of cross-platform usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell section is presented immediately after the Azure CLI section and uses Windows PowerShell syntax. There are no explicit Linux-specific instructions or mentions of Linux tools, shells, or patterns. The use of PowerShell, which is primarily associated with Windows, and the absence of explicit Linux/Bash parity (such as mentioning Bash or zsh shells, or providing Linux-specific troubleshooting or environment notes), indicates a mild Windows bias.

Recommendations:

Explicitly mention that the Azure CLI examples are cross-platform and can be run on Linux, macOS, and Windows.
Add a note or section clarifying that all Terraform and Azure CLI steps are fully supported on Linux and macOS, and provide any Linux-specific prerequisites if needed.
Consider including example shell commands using Bash syntax (e.g., export instead of $var=...) for Linux/macOS users.
If troubleshooting or environment setup differs on Linux, add a dedicated section or callout for Linux users.
Ensure that PowerShell is not presented as the default or primary method; if possible, present CLI/Bash examples first or in parallel.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for Azure Backup service release notes exhibits a mild Windows bias. Several features and updates reference or focus on Windows-centric tools (such as MARS agent and Microsoft Azure Backup Server), and Windows Server support is highlighted in the context of on-premises backup. However, the majority of the content is platform-neutral or references cross-platform workloads (Linux, PostgreSQL, MySQL, SAP HANA, AKS, etc.), and there are no explicit PowerShell-heavy or Windows-only example sections. Linux-specific tools or parity are not missing, but Windows tools are mentioned more frequently and sometimes before their Linux or cross-platform equivalents.

Recommendations:

When referencing backup agents or servers (e.g., MARS, MABS), clarify their platform support and provide equivalent Linux options or links where available.
Where Windows tools are mentioned (such as MARS or MABS), include a brief note or link about Linux backup approaches (e.g., Azure Backup for Linux VMs, native Linux backup tooling integration).
Ensure that any feature or tool that is Windows-specific is clearly labeled as such, and that Linux or cross-platform alternatives are referenced in the same context.
Add explicit examples or references for Linux workloads and management tools (e.g., Azure CLI, REST API) alongside any mention of PowerShell or Windows GUIs.
Consider a summary table or section listing supported platforms for each backup feature/tool, making Linux parity and support more visible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a 'windows_first' bias by listing Windows native client scenarios and links before Linux equivalents in both the main connection table and the 'Next steps' section. There is also a lack of explicit Linux command-line examples or screenshots in the main configuration steps, and the walkthroughs for enabling the feature do not mention Linux-specific tools or workflows.

Recommendations:

Reorder examples and tables to alternate or lead with Linux scenarios where appropriate, or present both Windows and Linux in parallel.
Include explicit Linux command-line examples (e.g., using SSH from a Linux terminal) in the main configuration and connection sections.
Add screenshots or walkthroughs from a Linux environment (e.g., GNOME Terminal, Konsole) alongside Windows screenshots.
Ensure that the 'Next steps' section lists Linux and Windows guides with equal prominence, or groups them together to avoid prioritizing one platform.
Mention Linux-native tools (e.g., OpenSSH, GNOME RDP clients) where Windows tools are referenced.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents PowerShell examples before Azure CLI examples, which may suggest a Windows-first perspective. The PowerShell section is detailed and appears before the cross-platform Azure CLI section, potentially prioritizing Windows users. However, both PowerShell and CLI examples are provided, and the CLI examples use POSIX shell syntax, supporting Linux/macOS users.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
Explicitly mention that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
Consider adding a short note or table at the top summarizing tool parity and platform support.
Ensure that any screenshots or UI references are not Windows-specific (the current portal section is neutral).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page shows mild Windows bias by listing Azure PowerShell as a configuration option alongside Azure CLI and Azure Portal, and by mentioning PowerShell after CLI (which is cross-platform) but before any Linux-specific tools. There are no explicit Linux shell or command-line examples, and no mention of Linux-specific tools or patterns. However, the programming language examples themselves are not shown, so further bias in code samples cannot be assessed from the provided content.

Recommendations:

Ensure that all command-line instructions are provided for both Azure CLI and Azure PowerShell, with clear indications of platform compatibility (e.g., note that Azure CLI is cross-platform, while PowerShell is available on both Windows and Linux).
When listing configuration options, avoid listing PowerShell immediately after CLI, or clarify that both are available on all platforms.
Add explicit Linux shell (bash) examples or references where relevant, especially for device-side operations.
If any code samples or instructions use Windows-specific paths, commands, or conventions, provide equivalent Linux/macOS examples.
Consider adding a section or note on platform compatibility for all tools and SDKs mentioned.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page describes the Azure Batch workflow and resources in a platform-neutral way, but there are subtle signs of Windows bias. The workflow and examples do not mention Linux-specific considerations, tools, or patterns, and the 'Next steps' section highlights the .NET client library (commonly associated with Windows) before Python. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or shell scripting mentioned.

Recommendations:

Include explicit references to both Windows and Linux when discussing compute node OS selection, with examples for each.
Provide sample workflows or links to quickstarts for both Windows (PowerShell, .NET) and Linux (Bash, Python, etc.) environments.
Mention Linux-friendly tools and scripting options (e.g., Bash scripts) alongside Windows tools.
Ensure parity in the order of presenting SDKs and tools (e.g., list Python and .NET together or alternate their order).
Add a note or section highlighting cross-platform support and any OS-specific considerations for Batch tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily demonstrates deployment using the Azure Portal, and when mentioning alternative methods, it lists Azure PowerShell before Azure CLI and REST API. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI or Bash), and the only linked deployment method is to a PowerShell-focused page, which may suggest a Windows-first or Windows-centric approach.

Recommendations:

Provide explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
When listing alternative deployment methods, mention Azure CLI before or alongside Azure PowerShell to avoid the impression of Windows-first bias.
Include Bash shell or Linux terminal screenshots or instructions where relevant, to demonstrate parity.
Link to both PowerShell and CLI deployment documentation, or provide direct step-by-step instructions for both.
Explicitly state that all deployment methods are supported on Windows, Linux, and macOS where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation shows a mild Windows bias, primarily through the consistent mention of Azure PowerShell alongside Azure CLI in every release note, and by referencing PowerShell-specific tools and links. Additionally, some documentation links and tabs default to PowerShell, and Windows/PowerShell tools are often listed before Linux-native or cross-platform alternatives. However, the document does acknowledge Linux (e.g., Azure Linux base image, Linux tools like Inspektor Gadget), and there are no outright missing Linux examples or exclusive use of Windows tools.

Recommendations:

Ensure that documentation links and tab defaults include both Bash and PowerShell options, or default to a neutral/cross-platform view.
When listing tool updates, alternate the order of Azure CLI and Azure PowerShell, or group them as 'cross-platform' and 'PowerShell' to clarify parity.
Provide explicit mention of Bash/Linux shell support and examples where relevant, especially in installation or usage instructions.
Highlight Linux-native tools and changes with equal prominence as Windows/PowerShell tools.
Audit all reference links to ensure they are not PowerShell-specific unless necessary, and provide equivalent Bash/Linux references when available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI (Bash) and Azure PowerShell examples, but there is a subtle Windows bias: PowerShell is consistently mentioned alongside Bash, and sometimes appears first in lists and next steps. The 'Next steps' section lists PowerShell before CLI, and there is a notable focus on PowerShell-specific navigation (e.g., 'Azure drive', 'cd Azure:/...'), which is not paralleled with Bash/Linux equivalents. There are no explicit Linux-only examples or tools, and the documentation does not highlight Linux-native patterns or features.

Recommendations:

Alternate the order of Azure CLI (Bash) and PowerShell examples throughout the documentation to avoid always listing PowerShell first.
In the 'Next steps' section, list Azure CLI before Azure PowerShell, or present them in parallel.
Provide Bash/Linux-native navigation examples where PowerShell-specific navigation is shown (e.g., show how to list or navigate resources using Bash/CLI).
Explicitly mention that Bash in Cloud Shell is a Linux environment and highlight any Linux-specific features or tips.
Ensure screenshots and instructions are balanced between Bash and PowerShell, and avoid PowerShell-specific terminology unless also providing Bash equivalents.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral and focused on Android, but there is a notable Windows bias in the mitigation steps for the 'noMicrophoneDevicesAvailable' diagnostic, which references enabling a microphone from the 'device manager'—a Windows-specific tool. There are no Linux-specific tools, commands, or mitigation steps mentioned, and no Linux examples are provided for device troubleshooting.

Recommendations:

When referencing device troubleshooting steps, provide Linux equivalents alongside Windows instructions. For example, suggest checking microphone availability using 'arecord -l' or verifying permissions in ALSA/PulseAudio on Linux.
Avoid referencing Windows-specific tools (like 'device manager') without mentioning alternatives for other platforms.
Include links or brief instructions for common Linux desktop environments (e.g., GNOME, KDE) on how to enable or troubleshoot audio devices.
Where possible, use platform-agnostic language or provide parallel steps for Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page describes Teams Phone extensibility provisioning and authorization but implicitly assumes a Windows-centric environment. It references 'cmdlet' usage for provisioning, which is typically associated with PowerShell on Windows, and does not provide equivalent Linux or cross-platform command-line examples. There are no explicit Linux or macOS instructions, nor are cross-platform tools or patterns mentioned.

Recommendations:

Provide cross-platform command-line examples, such as using Azure CLI or Microsoft Graph API via curl or other REST tools, alongside any PowerShell/cmdlet instructions.
Clarify whether the provisioning steps (e.g., cmdlet usage) can be performed on Linux/macOS, and if so, provide the necessary commands or scripts.
Explicitly mention any platform dependencies or prerequisites, and offer alternatives for non-Windows environments.
Include notes or links to documentation for cross-platform tools (e.g., Azure CLI, Microsoft Graph API) where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally aims for cross-platform parity and uses cURL, Bash, and Python, which are available on both Linux and Windows. However, there is a subtle Windows bias in the way platform-specific instructions are ordered and in the explicit recommendation of Git Bash for Windows users, while Linux/WSL users are simply told to use Bash. Windows is mentioned first in several places, and the only Windows-specific tool mentioned is Git Bash, with no mention of native Windows command prompts or PowerShell. There are no PowerShell-specific examples, and Linux is not omitted, but the documentation assumes Windows users need extra tooling (Git Bash) to follow along, which may not be necessary for all users.

Recommendations:

Alternate the order of platform mentions (sometimes Linux/WSL first, sometimes Windows) to avoid always putting Windows first.
Explicitly mention that Bash is available natively on Linux and WSL, and that Windows users can use Git Bash, WSL, or other Bash environments (such as Cygwin or Windows Terminal with WSL).
Consider providing a brief note for Windows users who may prefer PowerShell or Command Prompt, clarifying that the examples use Bash syntax and recommending Bash-compatible environments for all platforms.
Where possible, avoid assuming Windows users require extra tooling; clarify that Bash is the required shell environment, and list options for obtaining it on Windows.
Ensure that any references to tools or environments are balanced; if Git Bash is mentioned for Windows, mention native Bash for Linux/WSL with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation refers specifically to 'Windows' in the introductory sentence for using the capabilities call feature, but all code examples are in Swift (suggesting iOS/macOS context), and there are no Linux-specific instructions or examples. There is no mention of Linux or its equivalents, nor any cross-platform guidance.

Recommendations:

Remove or clarify the 'for Windows' phrasing if the feature is not Windows-specific, or provide equivalent instructions/examples for Linux.
Add explicit Linux (and macOS, if relevant) usage notes or examples, especially if the SDK is cross-platform.
Ensure introductory and instructional text is platform-neutral unless a feature is truly platform-specific.
If the feature is not available on Linux, state this explicitly to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a subtle Windows bias by referencing Windows-specific resources and presenting Windows as the default environment. For example, the link to creating an Azure Communication Services resource includes a '?tabs=windows' parameter, and the documentation for WebSockets refers to a Windows Azure Web Sites blog post. There are no explicit Linux or cross-platform instructions or examples, and Windows is implied as the primary platform.

Recommendations:

Provide explicit Linux and macOS instructions or links alongside Windows-specific ones, especially in setup and resource creation steps.
Replace or supplement Windows-specific documentation links (such as the WebSockets on Windows Azure Web Sites blog) with cross-platform or Linux-focused resources.
Ensure that all code samples and setup instructions are clearly cross-platform, and mention any platform-specific considerations if they exist.
Use neutral language and tabs or pivots to allow users to select their operating system, rather than defaulting to Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking to resource creation instructions with a Windows-specific tab and parameter (e.g., '?tabs=windows'), and does not provide any explicit Linux or cross-platform examples for setup or usage. While the .NET SDK is cross-platform, the documentation does not clarify or illustrate usage on Linux or macOS, nor does it mention or show Linux-specific commands, tools, or environment considerations.

Recommendations:

Ensure all links to Azure resource creation or setup guides default to a neutral or cross-platform tab, or explicitly mention both Windows and Linux options.
Add explicit instructions or notes for Linux users, such as confirming that the dotnet CLI commands work identically on Linux/macOS and providing any relevant prerequisites (e.g., installing .NET on Ubuntu).
Where possible, include example terminal commands or environment setup steps for Linux (e.g., using bash instead of PowerShell, if relevant).
Clarify in the prerequisites and setup sections that the SDK and instructions are cross-platform, and provide links to platform-specific installation guides for .NET.
Audit all quickstart and reference links to ensure Linux parity and avoid defaulting to Windows-specific documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias, particularly in the prerequisites section where links and instructions default to Windows (e.g., resource creation link with '?tabs=windows'). There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific considerations, despite the Java/Maven workflow being inherently cross-platform. This may leave Linux users uncertain about parity or specific steps.

Recommendations:

Update prerequisite links to use neutral or cross-platform tabs, or provide both Windows and Linux (and macOS, if relevant) options.
Explicitly state that all Java/Maven commands are cross-platform and can be run on Linux, macOS, or Windows.
If any platform-specific steps exist (e.g., file paths, environment variables), provide Linux/macOS equivalents alongside Windows instructions.
Include a note or section confirming Linux support and mentioning any known differences or additional requirements for Linux users.
Avoid using Windows-specific query parameters (like '?tabs=windows') in documentation links unless also providing Linux/macOS alternatives.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by only listing 'Windows' as a supported platform in the SDKs table, without mentioning Linux or macOS. There are no code examples, but the absence of Linux (or cross-platform) support information and the explicit mention of Windows may give the impression that Linux is unsupported or less important.

Recommendations:

Explicitly mention Linux and macOS support (or lack thereof) in the SDKs/platforms table to clarify parity.
If Linux is supported, add Linux-specific instructions, examples, or notes alongside Windows.
If Linux is not supported, state this clearly to avoid ambiguity.
Ensure future documentation includes cross-platform considerations and does not default to Windows-only references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias. In the prerequisites, links and instructions reference Windows first (e.g., resource creation link includes '?tabs=windows'), and there is no mention of Linux-specific instructions or examples. All command-line and code examples are platform-neutral, but there are no explicit Linux or cross-platform instructions, and no mention of Linux package managers or shell environments.

Recommendations:

Provide Linux-specific instructions or ensure parity in quickstart/resource creation links (e.g., include tabs for Linux/macOS).
Explicitly mention that the dotnet CLI and SDK are cross-platform, and provide example commands for Linux/macOS if any differences exist.
If there are platform-specific steps (such as setting environment variables, file paths, or installing dependencies), include Linux/macOS equivalents alongside Windows.
Avoid using Windows-specific query parameters (like '?tabs=windows') in documentation links unless also providing Linux/macOS options.
Consider adding a section or note clarifying cross-platform compatibility and any known differences in behavior or setup.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows development environments and tools. All code examples and setup instructions are focused exclusively on .NET and C#, with no mention of Linux-specific instructions, shell commands, or alternative SDKs (such as Python, Java, or Node.js). The 'Run the code' section provides build/run instructions for .NET CLI, Visual Studio, and Visual Studio Code, but omits any Linux-specific guidance or examples (e.g., bash shell, Linux package dependencies, or cross-platform considerations). Visual Studio, a Windows-centric IDE, is mentioned before Visual Studio Code, which is more cross-platform.

Recommendations:

Add explicit instructions and examples for Linux users, such as installing .NET SDK on Linux, using bash/zsh shell commands, and troubleshooting common Linux-specific issues.
Include alternative code samples or references for other supported SDKs (e.g., Python, Java, Node.js) to broaden platform inclusivity.
When listing development tools, mention cross-platform editors (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio), and clarify which instructions apply to which OS.
Provide guidance on running the code in Linux terminal environments, including any required dependencies or environment variables.
Where screenshots or UI references are shown (e.g., Azure Portal), clarify if the experience is the same across OSes or note any differences.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references enabling Teams Phone features via PowerShell, a Windows-centric tool, and does not provide Linux/macOS alternatives or mention cross-platform management options. No explicit Linux or cross-platform command-line examples are given for Teams user enablement.

Recommendations:

When referencing enabling Teams Phone or Enterprise Voice, provide cross-platform alternatives (e.g., Teams Admin Center web UI) or note if PowerShell is available on Linux/macOS.
If PowerShell is required, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
Add a note or link to documentation for managing Teams users from non-Windows environments.
Ensure all prerequisite steps are accessible from Linux/macOS, or clearly state any platform limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking only to the Windows installation instructions for Azure CLI in the prerequisites section. There are no Linux or macOS installation links or examples, and no mention of cross-platform usage, even though the Azure CLI is cross-platform. All command-line examples use the Azure CLI, which is platform-agnostic, but the installation guidance is Windows-specific.

Recommendations:

Provide installation links for Azure CLI on Linux and macOS alongside the Windows link, or use a generic Azure CLI installation page that covers all platforms.
Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS.
Consider adding a note or section confirming cross-platform compatibility for all commands shown.
If platform-specific instructions are necessary, present them in parallel (e.g., tabs for Windows, Linux, macOS) rather than only for Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows by exclusively referencing the Teams Admin Center (a web-based tool but often associated with Windows-centric workflows) and omitting any mention of Linux or cross-platform alternatives for Teams administration. There are no examples or instructions for managing Teams Auto Attendants or resource accounts using command-line tools (such as PowerShell or CLI) that could be run on Linux. All setup and configuration steps are described using GUI tools or web portals, which may not be ideal or accessible for Linux users.

Recommendations:

Include instructions for managing Teams Auto Attendants and resource accounts using cross-platform tools, such as Microsoft Graph API or Azure CLI, which can be used on Linux.
Provide PowerShell and CLI script examples for relevant steps, and clarify which steps can be performed from any OS.
Explicitly state when a step requires a web portal and confirm its accessibility from all major browsers and platforms.
Add notes or links to Linux-friendly tools or documentation for Teams administration tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. In the 'Clean up resources' section, the link provided includes a 'tabs=windows' parameter, suggesting that Windows instructions are prioritized or shown by default. There is no explicit mention or example for Linux or macOS in this section, and the documentation references Windows tools/patterns without ensuring Linux parity.

Recommendations:

Ensure that all referenced links and tabs provide clear options for Linux and macOS, not just Windows.
Avoid defaulting to Windows-specific instructions or tabs; use a neutral or platform-agnostic default where possible.
Explicitly mention and provide examples for Linux (and macOS) in cleanup and resource management sections.
Review included content (e.g., video-calling-javascript.md) to ensure cross-platform parity in all code and command-line examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias by referencing the Microsoft Installer (MSI) for Node.js installation as the only installation method, without mentioning Linux alternatives. No explicit Linux or cross-platform installation instructions or examples are provided. However, the rest of the instructions (npm, webpack, JavaScript code) are platform-agnostic.

Recommendations:

Provide Linux installation instructions for Node.js, such as using package managers like apt, yum, or snap.
Mention that Node.js can be installed on macOS and Linux, and provide links or commands for those platforms.
Avoid referencing only Windows-specific installers (like MSI) when discussing prerequisites; instead, offer cross-platform guidance.
Explicitly state that the sample and commands work on Windows, Linux, and macOS, and note any platform-specific caveats if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias by referencing Windows-centric console environments (cmd, PowerShell) before Bash, and by not providing any Linux- or macOS-specific instructions or examples. All terminal commands are generic and cross-platform, but there is no explicit mention or demonstration of Linux-specific steps, such as environment variable setup or file path conventions. There are no PowerShell-specific commands, but the overall framing assumes familiarity with Windows tools and patterns.

Recommendations:

Explicitly mention Linux and macOS as supported platforms wherever terminal or console instructions are given.
When listing console environments, use neutral or rotated orderings (e.g., 'such as Bash, cmd, or PowerShell') or mention all three equally.
Provide Linux/macOS-specific notes for setting environment variables (e.g., 'export VAR=VALUE' for Bash) alongside Windows examples ('set VAR=VALUE' for cmd, '$env:VAR="VALUE"' for PowerShell).
Include screenshots or references to Linux/macOS terminal usage where appropriate.
Ensure that any file path or editor instructions are platform-neutral or provide alternatives for different OSes.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on .NET and C# usage, which is most commonly associated with Windows development environments. There are no explicit Linux or cross-platform command-line examples, nor are there any references to Linux-specific tooling or shell usage. The installation and authentication steps assume a Windows-centric workflow (e.g., NuGet and dotnet CLI), and there is no mention of Linux or macOS environments, package managers, or shell commands. All code samples are in C#, and there is no guidance for users on Linux or alternative platforms.

Recommendations:

Explicitly mention that the .NET SDK and tools are cross-platform and provide installation instructions for Linux and macOS, including links to official documentation for those platforms.
Include example shell commands for Linux/macOS (e.g., using bash/zsh) alongside Windows/PowerShell equivalents where relevant.
Reference Linux package managers (such as apt, yum, or Homebrew for macOS) for installing prerequisites where appropriate.
Clarify that the dotnet CLI and NuGet are available on all major platforms, and provide troubleshooting tips for common Linux/macOS issues.
Consider including code samples or notes for other supported languages/platforms (such as Python, Java, or JavaScript) if the SDK is available, or at least acknowledge their existence and link to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows mild Windows bias by listing Windows-specific instructions and links before Linux/macOS equivalents. The Azure CLI installation link points only to the Windows installation page, and the environment variable section lists Windows instructions first, with Linux and macOS following. There is no direct Linux-specific Azure CLI installation link, and the Linux environment variable instructions assume the use of .bash_profile, which is not universal.

Recommendations:

Provide platform-agnostic or parallel links for Azure CLI installation (e.g., include links for Windows, Linux, and macOS).
Present environment variable instructions in a more balanced order, such as using tabs or listing Linux/macOS first in some cases.
Clarify that .bash_profile may not exist on all Linux distributions and suggest alternatives (e.g., .bashrc, .profile).
Ensure all examples and instructions are equally detailed for all platforms.
Consider using a platform selection tab for all setup steps, not just for environment variables.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias by describing user enablement for Teams exclusively through the Microsoft 365 admin center UI, which is a web-based tool but often associated with Windows-centric workflows. It also references the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance) as a method to retrieve the Resource Account ObjectId, without mentioning equivalent CLI or scripting options for Linux or cross-platform environments. No Linux-specific tools, shell commands, or alternative workflows are provided, and the only administrative tool mentioned is PowerShell.

Recommendations:

Provide equivalent instructions for enabling Teams users using cross-platform tools such as Azure CLI or Microsoft Graph API, which can be run on Linux, macOS, and Windows.
When referencing PowerShell cmdlets, also include REST API or CLI alternatives for retrieving necessary identifiers (such as the Resource Account ObjectId) to ensure Linux users are not excluded.
Explicitly state that all API calls can be made using any REST client (e.g., curl, Postman) and provide example commands for these tools.
Where possible, avoid assuming the use of Windows-specific administrative tools, or at least present them alongside cross-platform options.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows-specific tools and patterns, such as requiring Teams users to be 'Enterprise Voice enabled' via a PowerShell-based process, and linking to Microsoft documentation that is primarily Windows-focused. No Linux or cross-platform alternatives are mentioned for these administrative steps.

Recommendations:

Provide Linux/macOS alternatives or clarify if the administrative steps (such as enabling Enterprise Voice) can be performed using cross-platform tools or web interfaces.
Include links to platform-agnostic documentation or explicitly state if certain steps are Windows-only.
If PowerShell is required, mention if PowerShell Core (which is cross-platform) can be used, and provide example commands for Linux/macOS environments where possible.
Ensure that all prerequisite steps are accessible to users on non-Windows platforms, or provide guidance/workarounds if not.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing the Teams Admin Center (a web-based tool but often associated with Windows environments) and providing resource creation links that default to Windows pivots. There are no explicit Linux-specific instructions or examples, and no mention of Linux terminal or shell environments. All setup and run instructions are generic but lack Linux parity checks or clarifications.

Recommendations:

Ensure that resource creation links and instructions are not Windows-specific; provide Linux and macOS pivots or clarify that the steps are cross-platform.
Explicitly mention that all terminal commands (e.g., mkdir, npm install, npx webpack serve) work on Linux, macOS, and Windows, and note any OS-specific differences if applicable.
Add a section or notes for Linux/macOS users, including any prerequisites (e.g., package managers, permissions) and troubleshooting tips.
Avoid defaulting to Windows pivots in links; provide a neutral or multi-platform default.
If screenshots or UI references are included, clarify if they look different on non-Windows platforms or in different browsers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Visual Studio Code and Azure Functions tooling without specifying or demonstrating Linux-specific workflows. All instructions and links are oriented around Visual Studio Code, which, while cross-platform, is often associated with Windows, and there is no mention of Linux terminal usage, alternative editors, or command-line deployment methods. There are no explicit Linux or macOS examples, and the documentation assumes the use of GUI tools and workflows that may be less common on Linux.

Recommendations:

Include explicit instructions for Linux users, such as using the Azure Functions Core Tools CLI for function creation, local testing, and deployment.
Provide terminal-based examples for common tasks (e.g., running, deploying, and testing the function) using bash or zsh.
Mention and link to Linux-specific prerequisites, such as package installation commands for Node.js and Azure Functions Core Tools on Ubuntu or other distributions.
Clarify that Visual Studio Code is cross-platform, and provide any Linux-specific caveats or setup steps.
Offer alternative instructions for users who prefer not to use Visual Studio Code, such as using vim, nano, or other editors common on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash/OpenSSL and PowerShell examples for certificate creation and verification, but in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned first, followed by Bash and OpenSSL. This ordering subtly prioritizes Windows tooling. Additionally, the explicit mention of a 'PowerShell script supplied by Microsoft' as the first option, with Bash and OpenSSL as alternatives, reflects a mild Windows-first and PowerShell-heavy bias. However, Linux tooling (Bash/OpenSSL) is well represented and not omitted.

Recommendations:

Present Bash/OpenSSL and PowerShell examples in parallel or randomize their order to avoid implying a default platform.
Explicitly state that all methods are equally supported and that users should choose the one that fits their environment.
Where possible, provide cross-platform scripts or note any platform-specific limitations.
Ensure that Linux-first or neutral ordering is used in at least some sections, especially in cross-platform documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tabs in prerequisite links (e.g., '?tabs=windows'), and does not provide explicit Linux/macOS instructions or examples for setup and execution. All instructions are generic but implicitly assume a Windows environment, especially given the .NET/C# sample and lack of cross-platform notes.

Recommendations:

Provide explicit Linux/macOS instructions or notes where setup or tooling may differ (e.g., for .NET, DevTunnels CLI).
Ensure prerequisite links include Linux/macOS tabs or clarify cross-platform compatibility.
Mention that the sample can be run on Linux/macOS if applicable, and provide any additional steps required.
Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, port binding).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a mild Windows bias. The prerequisites link to a resource creation guide with a 'tabs=windows' parameter, suggesting a Windows-first approach. There are no explicit Linux-specific instructions or examples, and the sample project is .NET-based, which is cross-platform but often associated with Windows. No PowerShell or Windows-only command-line tools are shown, but there is also a lack of explicit Linux/macOS parity in instructions or troubleshooting.

Recommendations:

Update prerequisite links to use platform-neutral or multi-tab URLs (e.g., remove '?tabs=windows' or add Linux/macOS tabs).
Explicitly mention that the sample can be run on Linux/macOS as well as Windows, and provide any necessary platform-specific notes.
If there are any platform-specific steps (e.g., for dotnet or DevTunnels), provide Linux/macOS command-line examples or troubleshooting notes.
Ensure all referenced quickstarts and guides have Linux/macOS parity and are linked appropriately.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias, particularly in the quickstart and example links, which predominantly use 'windows' or 'uwp' tabs and pivots. There are no explicit Linux or cross-platform command-line examples, nor are Linux tools or environments mentioned. This could make it harder for Linux developers to follow or feel included.

Recommendations:

Provide Linux-specific examples and instructions alongside Windows ones, especially in quickstart links and code samples.
Use neutral, cross-platform language and tabs (such as 'web', 'nodejs', or 'dotnet') instead of defaulting to 'windows' or 'uwp'.
Explicitly mention Linux compatibility and any required steps for Linux environments.
Where platform-specific instructions are necessary, present Windows and Linux instructions in parallel.
Audit linked quickstarts and tutorials to ensure Linux users are not excluded or forced to adapt Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias in the prerequisites section, where instructions for installing the Azure CLI are provided only for Windows, with no mention of Linux or macOS alternatives. The link to create a Communication Services Resource also uses a 'tabs=windows' parameter, further reinforcing the Windows-centric approach. No Linux-specific instructions or parity are provided, especially in the setup and tooling sections.

Recommendations:

Provide installation instructions and links for Azure CLI on Linux and macOS alongside Windows, or use a tabbed interface to allow users to select their OS.
Remove or supplement 'tabs=windows' in resource creation links with Linux/macOS equivalents or a generic/default tab.
Explicitly mention cross-platform compatibility in the prerequisites and setup sections.
Wherever CLI or tooling is referenced, ensure that examples and links are not Windows-specific unless there is a technical reason.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides platform-specific instructions for Android (Java), iOS (Swift), and Windows (C#), but omits any mention of Linux or cross-platform desktop environments. The Windows example is included as the only desktop OS, with no Linux equivalent or guidance for Linux users.

Recommendations:

Add a Linux-specific section or example for log file retrieval, especially for scenarios where the SDK or application may be run on Linux desktops.
If the SDK does not support Linux, explicitly state this limitation to avoid confusion.
Consider including cross-platform .NET Core examples if applicable, and clarify OS compatibility.
Ensure parity in documentation by providing equivalent instructions for all major desktop operating systems (Windows, macOS, Linux) where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward .NET and Azure Functions in C#, which are cross-platform, but the workflow and examples assume development in Visual Studio Code and do not mention Linux-specific tools or workflows. There are no explicit PowerShell or Windows-only commands, but the guidance and examples are implicitly Windows-centric (e.g., referencing pressing F5 in VS Code, using .NET, and not mentioning Linux shell equivalents or alternative editors). There are no Linux-specific instructions, troubleshooting, or environment setup details.

Recommendations:

Include explicit instructions for running and testing the Azure Function on Linux (e.g., using the Azure Functions Core Tools in a bash shell, or running in a Docker container).
Provide alternative examples for installing dependencies (e.g., using apt-get or yum for required tools, or dotnet CLI commands in a Linux terminal).
Mention and show how to use editors commonly used on Linux (such as Vim, Emacs, or JetBrains Rider) or clarify that Visual Studio Code is cross-platform.
Add notes on environment variable configuration for Linux shells (e.g., export commands, .env files) instead of only referencing Windows environment variable patterns.
Clarify that all steps can be performed on Linux and provide troubleshooting tips for common Linux-specific issues.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI (Bash) and PowerShell examples for all commands, but does not include explicit Linux shell (e.g., Bash) examples outside of the Azure CLI tab. PowerShell is given equal prominence to Azure CLI, which is more commonly used on Windows. There are no Linux-specific instructions, troubleshooting, or environment notes, and PowerShell is not natively available on most Linux distributions. The structure (CLI first, then PowerShell) is better than Windows-first, but the parity is not complete for Linux users.

Recommendations:

Clarify in the prerequisites or setup sections that Azure CLI commands are intended for Bash or compatible Linux shells, and provide explicit Bash examples where environment variable syntax or command usage differs from PowerShell.
Remove or de-emphasize PowerShell examples unless there is a specific Windows-only step, or add a dedicated Bash/Linux tab for clarity.
Add troubleshooting notes or environment setup tips for Linux users, such as installing required tools (e.g., base64 with -w0 flag, which differs on macOS), and note any differences in command output or file paths (e.g., ~/.kube/config).
Where environment variables are set, ensure the Bash syntax is always shown and explained, as PowerShell variable assignment is not portable to Linux.
If PowerShell is to be retained, clarify that it is cross-platform but less common on Linux, and provide guidance for users who may not have it installed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in the prerequisites section by linking only to Windows installation instructions for the Azure CLI and referencing resource creation steps with a Windows-specific tab. There are no Linux or macOS equivalents or links provided for these steps, which may hinder users on non-Windows platforms. However, the rest of the documentation is platform-neutral and focused on iOS development.

Recommendations:

Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
Ensure that resource creation quickstarts and links use platform-neutral or multi-platform tabs, or explicitly mention Linux/macOS options.
Review all prerequisite steps to ensure parity for Linux and macOS users, especially for command-line and setup instructions.
Consider adding a note that the CLI and SDK steps are cross-platform, and provide troubleshooting tips or references for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for all Azure CLI and Docker commands, ensuring cross-platform coverage. However, in several key sections, the PowerShell workflow is more verbose and detailed, especially for deploying the frontend application, where the PowerShell path uses multiple custom objects and cmdlets, while the Bash path uses a single CLI command. Additionally, in the deployment section, the Bash example is presented first, followed by the PowerShell example, which may subtly prioritize Bash/Linux users, but the PowerShell path is more elaborate and may imply a Windows-centric workflow.

Recommendations:

Ensure that both Bash and PowerShell examples are equally detailed and cover the same workflow steps, especially for complex operations like deploying container apps.
Where possible, provide simplified PowerShell examples that match the simplicity of the Bash/CLI approach, or explain why the PowerShell workflow is more complex.
Consider explicitly mentioning that both Bash and PowerShell can be used on Windows, macOS, and Linux, to avoid the perception that PowerShell is only for Windows users.
If advanced PowerShell workflows are included, consider providing advanced Bash equivalents (e.g., using jq for JSON parsing) to maintain parity.
Review the ordering of examples to ensure neither platform is consistently prioritized over the other.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented around Microsoft-specific tools and portals (Azure portal, Microsoft Admin Center, Power BI, Microsoft 365 admin center) and does not provide any platform-specific command-line examples or automation instructions. There are no references to Windows-only scripting (e.g., PowerShell), but the documentation assumes use of web-based Microsoft portals and tools, which are most commonly associated with Windows environments. There are no Linux-specific instructions, CLI examples, or cross-platform automation guidance, and all video and tutorial links focus on the GUI experience.

Recommendations:

Add examples and guidance for using the Azure CLI and Azure REST APIs for onboarding and managing MCA, including sample commands that work on Linux, macOS, and Windows.
Include automation examples using cross-platform tools such as Azure CLI, Bash scripts, or Python, not just references to the Azure portal or Microsoft Admin Center.
Explicitly mention that the Azure portal and Admin Center are accessible from any modern browser on any OS, to clarify cross-platform compatibility.
Provide links to documentation or tutorials that cover command-line and programmatic approaches to MCA management, not just GUI/video resources.
If possible, include sample workflows for onboarding and billing management that can be performed from Linux or macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but consistently lists PowerShell examples before curl. This ordering implicitly prioritizes Windows users. There are no Linux- or bash-specific instructions or notes, and PowerShell is not as commonly used on Linux. However, all Azure CLI commands are cross-platform, and curl is included, so Linux users are not blocked, but the presentation order and example emphasis show a subtle Windows bias.

Recommendations:

Present curl (bash/Linux) examples before PowerShell examples, or at least alternate the order in different sections.
Explicitly mention that all Azure CLI and curl commands work on Linux, macOS, and Windows.
Consider adding bash script examples or notes for Linux users where appropriate.
If PowerShell is shown, clarify that it is available cross-platform, or provide equivalent bash one-liners for Linux/macOS users.
Add a short section in prerequisites or introduction noting that all steps are cross-platform unless otherwise specified.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI or PowerShell). While this avoids explicit Windows-only tools, the lack of CLI examples means Linux users (who often prefer or require CLI workflows) are not served. Additionally, when exceptions are mentioned, the workaround references 'Azure CLI' but does not provide actual CLI steps, and the linked documentation defaults to the Azure Portal, which is more familiar to Windows users.

Recommendations:

Add Azure CLI examples for all major steps, including enabling managed identity, assigning roles, and importing certificates, to ensure parity for Linux and cross-platform users.
Where exceptions require CLI usage, provide explicit CLI commands and not just references.
When linking to further documentation, ensure that both Portal and CLI tabs/examples are present and clearly indicated.
Consider including a section that summarizes both Portal and CLI workflows, allowing users to choose their preferred method.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Hyper-V (a Windows-specific virtualization technology) as the foundation for session isolation, without mentioning or acknowledging Linux-based alternatives or underlying technologies. There are no Linux-specific tools, patterns, or examples provided, and the documentation implicitly assumes a Windows-centric approach to sandboxing and isolation.

Recommendations:

Acknowledge that Hyper-V is a Windows technology and clarify whether Linux-based container hosts use different isolation mechanisms (such as gVisor, Kata Containers, or other Linux container isolation technologies).
If Azure Container Apps uses different underlying technologies for Linux-based environments, document these explicitly to provide transparency and parity.
Include references or links to documentation about container isolation on Linux, and explain how session isolation is achieved on non-Windows hosts.
Avoid assuming Hyper-V is universally applicable; clarify platform-specific details where relevant.
If possible, provide examples or explanations relevant to both Windows and Linux users, or note any differences in behavior or implementation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Windows VM software costs and related meters, without mentioning Linux or other operating systems. There are no examples or explanations for Linux VM scenarios, nor is there any discussion of software costs or meters that might apply to non-Windows environments. This creates a Windows-first perspective and omits information relevant to Linux users.

Recommendations:

Add a section explicitly addressing software costs for Linux VMs, even if to state that there are no additional software meters for standard Linux distributions.
Include a comparative table or statement clarifying how savings plans apply to both Windows and Linux VMs.
If there are software costs for Linux (e.g., for premium distributions or third-party software), list those meters as well.
Use inclusive language throughout, such as 'Windows and Linux VMs', rather than only referencing Windows.
Provide links to documentation about licensing and costs for Linux and other non-Windows OSes in Azure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell is given equal or greater prominence, and all scripting alternatives are either Bash or PowerShell. There is a strong focus on PowerShell, which is primarily a Windows tool, and no explicit mention or examples for native Linux shell environments beyond Bash. In some sections, PowerShell examples are presented before or alongside Bash, which can be perceived as a Windows-first approach. No Linux-specific tools or patterns (such as native Linux networking tools or automation approaches) are mentioned.

Recommendations:

Ensure Bash (Azure CLI) examples are always presented before PowerShell, as Bash is more universally available across platforms.
Clarify that Bash examples are suitable for Linux and macOS users, and PowerShell is primarily for Windows users (unless using PowerShell Core on Linux).
Consider including explicit Linux shell environment notes or troubleshooting tips for common Linux distributions.
If possible, add a short section or callout for Linux users, confirming that all Azure CLI commands work natively on Linux and macOS.
Avoid assuming PowerShell is the default scripting environment; make it clear that it is an alternative for those who prefer it.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows subtle Windows bias by mentioning Microsoft Excel as the example spreadsheet application for opening CSV files, without naming any Linux alternatives. There are no command-line examples or automation scripts, but when tools are mentioned, they are Windows-centric or Microsoft-branded. No Linux-specific tools, workflows, or examples are provided, and the documentation does not address cross-platform considerations for data ingestion or analysis.

Recommendations:

When mentioning spreadsheet applications, include cross-platform options such as LibreOffice Calc or Google Sheets alongside Microsoft Excel.
If providing examples for downloading or processing CSV files, include both Windows (PowerShell, Excel) and Linux (bash, awk, LibreOffice) workflows.
Explicitly state that the APIs and exported CSV files can be used on any platform, and provide sample scripts or command-line instructions for both Windows and Linux environments.
Reference open-source or platform-agnostic tools where possible, and avoid implying that Microsoft tools are required.
Add a section or note about cross-platform compatibility for cost data analysis and ingestion.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to apply billing tags using the Azure portal, which is a web-based interface accessible from any OS. However, there are no examples or references to command-line or automation methods (such as Azure CLI, PowerShell, or REST API), which are often used in cross-platform or Linux environments. If automation were discussed, there is a risk that only Windows/PowerShell examples would be provided first or exclusively, but in this case, the omission itself is a form of bias as it does not address Linux users' needs for automation or scripting.

Recommendations:

Add examples for applying billing tags using Azure CLI, which is cross-platform and widely used on Linux.
If PowerShell examples are added, ensure Azure CLI or REST API examples are also provided and presented first or alongside PowerShell.
Explicitly mention that all operations can be performed from any OS via the portal, but also provide automation options for Linux users.
Include links to relevant Azure CLI and REST API documentation for managing billing tags.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific troubleshooting content first (e.g., linking only to Windows VM CPU troubleshooting) and providing a Windows command prompt example before the Linux equivalent. There are no Linux-specific troubleshooting links or parity in example depth.

Recommendations:

Include links to both Windows and Linux troubleshooting guides (e.g., for high CPU usage) to ensure platform parity.
When providing command-line examples, present both Windows and Linux commands side by side, or in a neutral order (alternating which comes first).
Add Linux-specific troubleshooting steps or references where appropriate, especially in sections that currently only mention Windows resources.
Review all external links and ensure Linux equivalents are present wherever Windows-specific documentation is referenced.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references deletion of resource groups and resources with a link that includes an 'azure-powershell' tab, suggesting a preference for Windows tooling. There are no explicit Linux or cross-platform CLI examples or references, and the documentation does not mention or provide parity for Linux users or tools such as Azure CLI or Bash scripts.

Recommendations:

Include examples and references for cross-platform tools such as Azure CLI and Bash scripts alongside or instead of PowerShell.
Ensure that linked articles and code samples provide both PowerShell and Azure CLI (or REST API) instructions, and make this explicit in the main documentation.
Avoid defaulting to Windows-centric tooling in links or examples; if PowerShell is mentioned, provide equivalent Linux-friendly alternatives.
Add a section or note clarifying that all actions can be performed from any OS using cross-platform tools, and provide links to relevant documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on the Azure portal (a web interface) and does not provide any command-line examples or automation guidance. There is no mention of PowerShell, Windows-specific tools, or scripts, but there is also a complete absence of Linux CLI tools (such as Azure CLI) or cross-platform automation methods. All instructions and examples assume use of the Azure portal, which is accessible from any OS, but the lack of parity in mentioning or demonstrating CLI-based management (which is common for Linux users) creates a subtle bias by omission.

Recommendations:

Add examples for managing EA roles using Azure CLI commands, which are cross-platform and widely used by Linux users.
Include references to REST API usage with curl or other Linux-native tools for automation.
Where possible, provide both portal-based and CLI/API-based instructions for all administrative tasks.
Explicitly mention that all tasks can be performed from any OS via the portal, but highlight automation options for Linux users.
Ensure that links to further documentation include both PowerShell and Azure CLI where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but the PowerShell example is presented second. However, the presence of PowerShell (a Windows-centric tool) as a primary scripting example, and the absence of any explicit Linux shell or Bash-specific guidance (beyond the Azure CLI, which is cross-platform), indicates a slight Windows bias. There are no Linux- or Bash-specific examples, and PowerShell is highlighted as an alternative, which may not be as familiar or readily available to Linux users.

Recommendations:

Ensure that all command-line examples are provided in both Azure CLI (which is cross-platform) and Bash shell script formats where appropriate.
If PowerShell examples are included, clarify that Azure CLI commands work natively on Linux/macOS and Windows, and consider providing Bash script equivalents for automation scenarios.
Avoid assuming the use of PowerShell as the default scripting environment; instead, present Azure CLI or REST API examples first, as these are more universally accessible.
Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide troubleshooting notes for non-Windows environments if needed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page primarily references Windows-centric tools such as PowerShell and Power BI, without providing equivalent examples or explicit guidance for Linux users. There are no command-line examples for Linux shells, and the focus on Power BI and PowerShell may implicitly favor Windows environments.

Recommendations:

Include Azure CLI examples for retrieving reservation utilization, with sample commands that work cross-platform (Linux, macOS, Windows).
Mention and provide examples for using Bash or other Linux shells where appropriate.
Clarify that Power BI Desktop is only available on Windows, and suggest alternative reporting tools or methods for Linux users (such as using the API with Python or other cross-platform tools).
Ensure that references to PowerShell are accompanied by Azure CLI or REST API examples, to provide parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using Excel for data preparation and calculation steps, with no mention of Linux-compatible spreadsheet tools (such as LibreOffice Calc or Google Sheets) or command-line alternatives. All screenshots and instructions are tailored to Excel, which is primarily a Windows (and Mac) application, and there are no examples or guidance for users on Linux or those preferring open-source tools.

Recommendations:

Explicitly mention and provide parallel instructions for Linux-compatible spreadsheet applications such as LibreOffice Calc and Google Sheets.
Include screenshots and step-by-step examples using LibreOffice Calc or Google Sheets alongside Excel.
Offer a brief section or appendix on how to perform the calculations using command-line tools (e.g., csvkit, awk, pandas in Python) for advanced or Linux-native users.
Use more generic terminology (e.g., 'spreadsheet application' instead of 'Excel') throughout the documentation, except where Excel-specific features are referenced.
Where possible, provide downloadable example files in open formats and ensure formulas are compatible with non-Excel spreadsheet software.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively references the Azure portal (a web interface) for all reservation management tasks and does not provide any command-line examples, such as using Azure CLI, PowerShell, or REST APIs. While this avoids explicit Windows/Powershell bias, it implicitly favors GUI-based workflows, which are more familiar to Windows users. There are no examples or guidance for Linux users who may prefer or require command-line or automation-friendly approaches (e.g., Azure CLI on Linux).

Recommendations:

Add step-by-step examples for purchasing and managing reservations using the Azure CLI, which is cross-platform and widely used on Linux.
Include REST API references or examples for advanced automation scenarios, which are platform-agnostic.
If PowerShell examples are added, ensure equivalent Azure CLI examples are provided and presented first or side-by-side.
Explicitly mention that all tasks can be performed from Linux, macOS, or Windows using the Azure CLI or REST API, not just the Azure portal.
Provide links to Azure CLI and REST API documentation for reservation management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references Excel for data preparation and calculation, with all instructions and screenshots based on the Excel interface. There are no examples or guidance for Linux users or those using non-Microsoft spreadsheet tools (such as LibreOffice Calc, Google Sheets, or command-line tools like awk/csvkit). The workflow assumes a Windows-centric environment, implicitly prioritizing Windows tools and patterns.

Recommendations:

Include parallel instructions and screenshots for at least one popular Linux-compatible spreadsheet application, such as LibreOffice Calc or Google Sheets.
Mention and provide examples for command-line CSV processing tools (e.g., csvkit, awk, pandas) for users who may not use GUI spreadsheet software.
Rephrase references to 'Excel' as 'spreadsheet application' throughout, and clarify that the process is applicable to any tool capable of handling CSV files.
Where possible, provide downloadable sample data and formulas in formats compatible with both Excel and LibreOffice Calc.
Add a note or section specifically addressing Linux/macOS users, outlining alternative tools and any differences in steps or formulas.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on user management via the CycleCloud web portal, a Microsoft-centric tool, without mentioning or providing examples for Linux-native user management methods (e.g., command-line tools like useradd or adduser). There are no Linux command-line instructions or references, and the workflow assumes the use of Microsoft Entra ID and CycleCloud, both of which are more common in Windows-centric environments.

Recommendations:

Include alternative instructions for adding users using standard Linux command-line tools (e.g., useradd, adduser) for environments where CycleCloud is not used or for administrators who prefer CLI.
Provide examples or references for managing users directly on Linux clusters, including how to synchronize with Microsoft Entra ID if applicable.
Clarify whether the described process is required or optimal for Linux-based clusters, or if there are Linux-native alternatives.
Add a section comparing CycleCloud-based user management with traditional Linux user management to help users choose the best approach for their environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes management of Azure savings plans using the Azure Portal GUI, with no mention of command-line tools or automation options. There are no examples using Azure CLI, Bash, or Linux-native workflows, nor are there any references to PowerShell or Windows-specific tools. However, the lack of Linux/CLI examples and the focus on GUI navigation (which is more common in Windows-centric documentation) results in a subtle Windows-first and missing Linux example bias.

Recommendations:

Add equivalent instructions for managing savings plans using the Azure CLI, with example commands for common tasks (e.g., changing scope, viewing details, modifying auto-renewal).
Include Bash shell examples for Linux users, especially for automation or scripting scenarios.
Explicitly mention cross-platform tools (Azure CLI, REST API) and provide links to their documentation.
Clarify that all management actions can be performed from any OS using the Azure Portal, but highlight automation options for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally provides cross-platform instructions, but there is a subtle Windows bias in the Python section where Windows command examples are presented before Linux ones, and in some places, Linux-specific instructions are less prominent or missing. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the ordering and occasional lack of explicit Linux parity can create a perception of Windows-first orientation.

Recommendations:

Present Linux and Windows examples side-by-side or in a consistent order (e.g., Linux first, then Windows, or vice versa, but be consistent across all language pivots).
Where platform-specific commands are needed, ensure both Windows and Linux/macOS variants are always shown, not just for Python but for all languages.
Consider using platform-agnostic commands (e.g., 'python3' instead of 'python' where possible) or provide a note explaining differences.
Explicitly mention that all CLI commands (e.g., Dapr, azd, git) work on both Windows and Linux/macOS, and link to cross-platform installation guides.
Audit other language pivots (Node.js, C#) to ensure that if there are any platform-specific nuances, they are equally documented for both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides browser troubleshooting steps that reference Edge and Chrome in detail, with Edge (a Microsoft product) consistently listed first and described in greater detail. There are no Linux-specific instructions or references to Linux browsers or environments. The guidance assumes the use of browsers and settings most common on Windows or macOS, omitting mention of Linux distributions, Firefox (a popular Linux browser), or command-line alternatives for clearing cache/cookies.

Recommendations:

Include instructions for Firefox, which is widely used on Linux systems, for private browsing and clearing cache/cookies.
Add a note or section addressing Linux users, specifying where browser settings may differ or how to access them on common Linux desktop environments.
Consider providing command-line alternatives for clearing browser data on Linux (e.g., using rm to delete browser cache directories).
Avoid always listing Edge first; rotate browser order or group instructions by operating system.
Explicitly mention that the steps apply to all platforms, and highlight any platform-specific differences where relevant.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists several cluster template types, and the only project with a Microsoft-specific/Windows-specific tool is 'HPC Pack', which is a Windows-only job scheduler. Additionally, the link for HPC Pack points to a PowerShell documentation page, and it is listed before several Linux-native schedulers (HTCondor, LSF, OpenPBS, Slurm). However, the CLI example given is cross-platform and there are examples for Linux-native schedulers as well. There are no explicit PowerShell commands or Windows-only instructions, but the presence and placement of HPC Pack and its PowerShell link indicate a mild Windows bias.

Recommendations:

Ensure that Linux-native schedulers (e.g., Slurm, OpenPBS) are given equal prominence in the table, possibly by ordering them alphabetically or by usage popularity.
Provide links to Linux documentation or usage guides for each scheduler, not just for the Windows-specific HPC Pack.
If referencing Windows tools (like HPC Pack), also provide equivalent Linux tool references or clarify platform support for each template.
Avoid linking directly to PowerShell documentation unless a Linux equivalent is also provided.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Azure portal GUI (a web interface commonly used by Windows users) for checking settings, and does not provide any command-line examples (such as Azure CLI or PowerShell) for Linux users. There are no Linux-specific instructions or parity in tooling guidance.

Recommendations:

Include Azure CLI commands to check if Hierarchical namespace is enabled (e.g., using 'az storage account show').
Provide both PowerShell and Bash/Azure CLI examples for managing permissions and checking storage account settings.
Mention that the Azure portal is cross-platform, but explicitly offer command-line alternatives for users who prefer or require non-GUI workflows.
Add troubleshooting steps or examples relevant to Linux environments, such as checking permissions or environment variables from a Linux shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing only the creation of a Windows VM in the prerequisites and omitting any mention or example of Linux virtual machines. There are no Linux-specific instructions, links, or parity in the examples, which may lead Linux users to feel unsupported or uncertain about the process.

Recommendations:

Include references and links to both Windows and Linux VM creation guides in the prerequisites section (e.g., add a link to 'Create a Linux VM in the Azure portal').
Explicitly state that the instructions apply to both Windows and Linux VMs, unless there are platform-specific differences.
Where examples refer to a VM (e.g., 'myVM1'), clarify that it can be either a Windows or Linux VM.
If there are any platform-specific steps (such as verifying network settings inside the VM), provide both Windows and Linux command examples.
Review all sections for implicit Windows assumptions and ensure Linux users are equally guided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation shows mild Windows bias by mentioning Windows prerequisites and installation steps before Linux equivalents in some sections, and by providing more detailed instructions for Windows-specific tools (e.g., PowerShell, Windows Explorer). However, Linux installation steps are present and reasonably detailed.

Recommendations:

Present Linux and Windows instructions in parallel or in a consistent order (e.g., Linux first, then Windows, or vice versa, but consistently).
Provide equivalent detail for both platforms, including command-line examples for both Linux and Windows (e.g., show PowerShell commands alongside bash commands).
Avoid assuming the user is on Windows in prerequisite sections; instead, provide platform-neutral guidance or clearly separate platform-specific steps.
Where possible, mention cross-platform tools and patterns, and avoid Windows-specific terminology unless necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest', 'Windows 2022 DataCenter') and omitting equivalent Linux-based examples. While the table of available images includes both Linux and Windows options, the configuration examples exclusively reference Windows, which may mislead users into thinking Windows is the primary or preferred platform.

Recommendations:

Add parallel Linux-based examples (e.g., using 'cycle.image.ubuntu22' or 'almalinux-8') alongside Windows examples in all configuration code blocks.
Alternate the order of examples or provide both Windows and Linux examples together to demonstrate parity.
Explicitly state that all example patterns apply equally to Linux images, and show this with sample URNs or labels for Linux distributions.
Consider including a short section or note highlighting Linux image usage, especially for common distributions like Ubuntu or CentOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references Windows support explicitly for the self-hosted integration runtime and links to Windows prerequisites, but does not mention Linux support or provide Linux-specific instructions or examples. No Linux or cross-platform guidance is present for self-hosted runtime setup or compatibility.

Recommendations:

Explicitly state whether Linux is supported for the self-hosted integration runtime in this connector scenario.
If Linux is supported, provide a link to Linux installation/prerequisite documentation alongside the Windows link.
Include Linux-specific instructions or examples for setting up the self-hosted integration runtime, if applicable.
If Linux is not supported, clearly state this limitation to avoid ambiguity.
Ensure parity in documentation structure and examples for both Windows and Linux environments where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes a Windows development environment by default, provides only Windows (cmd) commands for setting environment variables and running commands, and does not include equivalent Linux/bash examples. While it mentions that steps can be performed on Linux, it does not provide explicit Linux instructions or command syntax, which may hinder Linux users.

Recommendations:

Provide Linux/bash equivalents for all command-line instructions, especially for setting environment variables (e.g., export VAR=value).
When showing command-line examples, present both Windows (cmd) and Linux (bash) commands side by side or in tabs.
Avoid language such as 'the steps in this article assume a Windows development machine' unless absolutely necessary; instead, state that instructions are cross-platform and provide both sets of commands.
Explicitly mention any OS-specific differences in steps, tools, or behaviors.
Include screenshots or references to popular Linux editors or terminals where relevant, not just Visual Studio Code.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation lists Azure PowerShell as a primary tool for performing the Copy activity, but does not mention Linux-specific tools or provide Bash/CLI examples. PowerShell, which is traditionally associated with Windows, is highlighted, and there is no explicit mention of cross-platform command-line tools like Azure CLI or Linux shell scripting.

Recommendations:

Include Azure CLI as a recommended tool alongside PowerShell, with a corresponding quickstart link.
Provide explicit examples or links for performing the Copy activity using Bash or Linux shell environments.
Ensure that PowerShell is not listed before more cross-platform tools like Azure CLI to avoid the appearance of Windows-first bias.
Add a note clarifying the cross-platform availability of tools where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by recommending the use of XrmToolBox, a Windows-only tool, for troubleshooting Dynamics 365 connectors. No equivalent Linux tools or cross-platform alternatives are mentioned, and there are no command-line or script examples for Linux environments. The documentation assumes access to Windows-based utilities, which may exclude Linux or macOS users.

Recommendations:

Provide cross-platform alternatives to XrmToolBox, such as open-source FetchXML testers or REST API usage examples that work on Linux and macOS.
Include troubleshooting steps or examples using command-line tools available on Linux (e.g., curl, wget, PowerShell Core, or REST API calls).
Explicitly state when a recommended tool is Windows-only and suggest equivalent approaches for non-Windows users.
Where possible, link to documentation or community tools that support Linux/macOS for Dynamics 365 troubleshooting.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references 'network monitor (netmon) trace' for troubleshooting SSL/TLS issues, which is a Windows-specific tool, and does not provide equivalent instructions or tool suggestions for Linux environments. No command-line examples (e.g., PowerShell, Bash) are given, but the only explicit tool mentioned is Windows-centric. There are no Linux-specific troubleshooting steps or parity in tooling guidance.

Recommendations:

When suggesting network monitoring, mention cross-platform tools such as Wireshark or tcpdump, and provide brief instructions or links for both Windows and Linux users.
If referencing a Windows tool (like netmon), also list equivalent Linux tools and how to use them for the same troubleshooting task.
Wherever possible, provide troubleshooting steps or examples that are platform-agnostic, or explicitly include both Windows and Linux variants.
Audit the documentation for other implicit assumptions of a Windows environment and ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., %windir%\system32) for library placement and troubleshooting, and does not provide equivalent instructions or examples for Linux environments. There are no Linux-specific installation paths, troubleshooting tips, or examples, which may hinder users deploying Self-hosted Integration Runtime on Linux.

Recommendations:

Include Linux-specific instructions for installing the SAP NetWeaver library and its dependencies, such as typical library paths (e.g., /usr/lib or /opt/sap), and how to set environment variables (e.g., LD_LIBRARY_PATH).
Provide troubleshooting tips for Linux environments, such as checking shared library dependencies with ldd, and ensuring correct permissions.
Mention any differences or additional requirements when running Self-hosted Integration Runtime on Linux, if supported.
Where Windows environment variables or paths are referenced, add Linux equivalents in parallel.
Explicitly state if Linux is not supported for Self-hosted Integration Runtime, or provide a link to platform compatibility documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page is generally cross-platform and does not provide command-line examples specific to Windows or Linux. However, there is a subtle Windows bias in the 'Staged copy' section, where firewall configuration is discussed only in the context of the Windows firewall, and port requirements are described with reference to Windows and corporate firewalls. No mention is made of Linux firewall equivalents (e.g., iptables, firewalld, ufw), nor are Linux-specific considerations or examples provided. This may lead Linux users to feel their scenarios are not fully addressed.

Recommendations:

When discussing firewall configuration, mention both Windows (Windows Firewall) and Linux (e.g., iptables, firewalld, ufw) firewalls to ensure Linux users are included.
Where platform-specific configuration is referenced, provide parallel guidance or links for both Windows and Linux environments.
Explicitly state that the guidance applies to both Windows and Linux self-hosted integration runtime nodes, and note any differences if they exist.
Consider adding a short section or note acknowledging cross-platform support and linking to platform-specific setup/configuration guides where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally presents a cross-platform workflow using the Azure CLI and Cloud Shell, which are available on both Windows and Linux. However, there are subtle indications of Windows bias: Windows tools (Windows Terminal) are mentioned before Linux equivalents, and PowerShell is given equal or slightly more prominence than Bash in some sections. Additionally, PowerShell-specific command syntax is included, but there is no mention of Linux-specific shells or issues. There are no Linux-specific examples or troubleshooting notes, and the guidance for local CLI use references Windows tools first.

Recommendations:

When mentioning local CLI usage, list both Windows Terminal and common Linux terminals (e.g., GNOME Terminal, Konsole) to avoid Windows-first bias.
Include troubleshooting notes or tips for common Linux shell issues (e.g., line endings, permissions) alongside PowerShell notes.
When presenting command syntax differences, ensure Bash (or other Unix shells) are given equal or first prominence, and clarify that PowerShell is just one of several options.
Explicitly state that all commands work on both Windows and Linux, and provide links to platform-specific installation or usage guides where relevant.
Consider adding a brief section or callout for Linux/macOS users, especially when discussing local CLI installation or environment setup.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only Windows-centric examples for Hadoop Streaming activities, specifically referencing '.exe' files (e.g., MyMapper.exe, MyReducer.exe) as mapper and reducer executables. There are no examples or mentions of Linux/Unix-style scripts (e.g., Python, Bash, or shell scripts), which are more common in Hadoop environments. This may mislead users into thinking only Windows executables are supported or recommended.

Recommendations:

Add Linux/Unix-based examples for mapper and reducer scripts, such as Python (.py), Bash (.sh), or other common script types used in Hadoop Streaming.
Clarify in the documentation that both Windows executables and Linux/Unix scripts are supported, if applicable.
Provide at least one example using a non-Windows executable (e.g., 'MyMapper.py', 'MyReducer.sh') in the JSON sample and file paths.
Explicitly mention any platform requirements or limitations for the mapper/reducer programs.
Consider reordering or balancing examples to reflect the prevalence of Linux in Hadoop environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation focuses exclusively on configuring Azure-SSIS IR via the Azure portal and ADF UI, which are web-based and cross-platform, but does not provide any command-line examples or automation options for Linux users. The only alternative automation method referenced is via Azure PowerShell, a tool primarily associated with Windows environments. There are no mentions of Azure CLI or Bash-based workflows, and no Linux-specific guidance or parity is provided.

Recommendations:

Add equivalent instructions for configuring Azure-SSIS IR and joining a virtual network using Azure CLI, which is cross-platform and widely used on Linux.
Include Bash shell command examples for automation, where applicable.
Reference both Azure PowerShell and Azure CLI options in the 'Related content' section, ensuring Linux users are aware of non-Windows tooling.
Explicitly state that the Azure portal and ADF UI are accessible from any OS with a supported browser, to reassure Linux and macOS users.
If certain features are only available via PowerShell, clarify this and provide a roadmap or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and update mechanisms, such as the Microsoft Update Catalog and .exe update packages. There are no examples or instructions for Linux users, nor is there any mention of Linux-compatible update workflows or file formats.

Recommendations:

Provide guidance for Linux administrators, including how to download and apply updates from non-Windows systems.
Offer alternative update package formats (e.g., .tar.gz, .sh) or clarify if updates can only be applied from Windows environments.
Include explicit statements about platform requirements or limitations, so Linux users are aware of any constraints.
If the device or update process is platform-agnostic (e.g., web UI accessible from any OS), clarify this and provide screenshots or instructions using browsers on Linux.
If PowerShell or Windows-only tools are required, suggest equivalent Linux command-line approaches or note the lack of parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure SQL Database and T-SQL/SQL Server stored procedures for control tables and workflow orchestration, which are Windows-centric technologies. There are no examples or mentions of Linux-native alternatives (such as PostgreSQL, MySQL, or open-source orchestration tools), nor any guidance for users who may wish to use non-Windows database engines or scripting environments. No PowerShell or Windows command-line examples are present, but the overall workflow assumes a Windows/Azure SQL Server environment.

Recommendations:

Provide equivalent examples using open-source databases such as PostgreSQL or MySQL, including DDL and stored procedure syntax.
Mention that the control table could be implemented in other database engines, and provide guidance or links for Linux users.
Clarify whether Azure Data Factory supports non-SQL Server control tables and, if so, how to configure them.
If possible, include a section or appendix with Linux-friendly alternatives for the control table and orchestration logic.
Explicitly state the platform requirements and suggest cross-platform options where available.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only Azure Portal (web UI) instructions for erasing data and downloading the Secure Erase Certificate, with no mention of command-line or automation options. There are no examples or references to using Linux tools, scripts, or CLI commands. If there are equivalent PowerShell or Windows CLI methods, they are not shown, but the absence of Linux/CLI parity is notable.

Recommendations:

Add instructions for performing device reset and certificate download using Azure CLI, including examples that work on Linux and macOS.
If PowerShell or Windows CLI methods exist, ensure Linux shell equivalents are provided and shown side-by-side.
Mention any REST API or automation options that can be used from non-Windows environments.
Explicitly state platform requirements or parity if some features are only available via the Azure Portal.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed reference architectures and links specifically for Windows virtual machines and Windows N-tier applications, while Linux is only mentioned in passing. There are no equivalent Linux-specific examples, diagrams, or reference links, despite the mention of 'Windows/Linux' workloads. The focus on Windows architectures without Linux parity may leave Linux users underserved.

Recommendations:

Add explicit Linux-based reference architectures, including diagrams and detailed explanations, similar to those provided for Windows.
Include links to Linux-specific Azure architecture guides (e.g., 'Linux N-tier application on Azure').
Where 'Windows/Linux' is mentioned, ensure both platforms are equally represented with examples and guidance.
Review all sections to ensure Linux is not just mentioned but actively supported with actionable content.
If certain features or architectures are Windows-only, clearly state this and provide alternative recommendations for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, which is a Windows-only tool. There are no instructions or examples for users running the self-hosted integration runtime on Linux, nor is there any mention of Linux command-line alternatives or parity.

Recommendations:

Add instructions for collecting and sending logs when the self-hosted integration runtime is running on Linux.
Specify whether the Integration Runtime Configuration Manager is available on platforms other than Windows, and provide alternatives if not.
Include command-line or script-based methods (e.g., using shell commands) for Linux users to gather and send logs.
Clearly indicate platform-specific steps and provide equivalent guidance for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for key CLI operations, but PowerShell is given equal prominence to Bash, which can indicate a Windows-centric approach. There are no explicit Linux-only or Windows-only tools, but the inclusion of PowerShell tabs and examples throughout, rather than focusing on Bash (which is more universal across platforms), suggests a slight Windows bias. However, Linux-specific instructions (e.g., editing k3s config with nano, using systemctl) are present, and no steps are missing for Linux users.

Recommendations:

List Bash examples before PowerShell, as Bash is available on both Linux and Windows (via WSL or Git Bash), while PowerShell is less common on Linux.
Clarify that Bash examples are cross-platform and can be used on Windows via WSL or Git Bash.
Consider providing a single Bash example by default, with PowerShell as an optional/secondary tab for Windows users.
Explicitly mention that all CLI commands work on Linux, macOS, and Windows (with Bash or PowerShell), to reinforce cross-platform parity.
If possible, provide guidance for macOS users as well, or clarify that instructions are valid for both Linux and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only SQL Server/Azure SQL Database examples for the control table, with no equivalent examples or instructions for Linux-based database systems (e.g., PostgreSQL, MySQL) or command-line environments. The workflow and examples are centered on Microsoft technologies, and there is no mention of Linux tools, shell commands, or cross-platform database creation steps.

Recommendations:

Add equivalent examples for creating the control table in popular Linux-supported databases such as PostgreSQL and MySQL.
Include instructions or code snippets using Linux command-line tools (e.g., psql, mysql) for creating and populating the control table.
Clarify that the template is database-agnostic and provide guidance for users working on non-Windows platforms.
If screenshots are shown for connection creation, ensure at least one example uses a non-SQL Server source (e.g., Oracle, PostgreSQL) to demonstrate cross-platform applicability.
Explicitly mention that the steps are applicable regardless of the operating system, and provide any OS-specific notes if necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias. While it mentions that both Windows and Linux images are supported (e.g., in the OS type selection), all procedural steps, screenshots, and linked resources (such as uploading a VHD) are presented in a generic or Windows-centric manner. There are no explicit Linux-specific examples, screenshots, or command-line instructions (e.g., using Linux tools to prepare/upload images). The only reference to Linux is in a dropdown selection, with no further guidance or parity in examples.

Recommendations:

Include explicit Linux examples, such as preparing and uploading a Linux VHD using Linux tools (e.g., Azure CLI, azcopy on Linux, or shell commands).
Provide screenshots that show Linux image selection and deployment, not just generic or Windows-centric images.
Add a section or callout for Linux users, highlighting any differences or best practices when creating and uploading Linux VM images.
Ensure that linked resources (such as 'Upload a VHD image in your Azure Storage account') include Linux instructions and not just Windows/PowerShell steps.
When referencing OS types, alternate the order or provide equal prominence to Linux and Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references and demonstrates the use of SSIS (SQL Server Integration Services) activities, which are Windows-centric tools, and highlights them alongside cross-platform activities (Copy, Data Flow). There are no explicit Linux or cross-platform command-line examples, and the only specific tool mentioned beyond the Data Factory UI is SSIS, which is traditionally Windows-based. No Linux-specific tools, patterns, or examples are provided.

Recommendations:

Include explicit mention of cross-platform compatibility for all activities, clarifying which features are available on Linux-based integration runtimes.
Add examples or notes for users running Data Factory pipelines on Linux-based integration runtimes, especially for Data Flow and Copy activities.
If SSIS is Windows-only, clearly state this and suggest Linux alternatives or workarounds where possible.
Provide parity in documentation by referencing Linux tools or environments where relevant, or by stating when a feature is not available on Linux.
Consider adding a table or section summarizing feature support and instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page is generally cross-platform, focusing on Python and the Azure Python SDK, which are available on both Windows and Linux. However, in the 'Next steps' section, it highlights Azure PowerShell and Az.LabServices cmdlets as further learning resources, both of which are traditionally associated with Windows environments. There is no mention of Linux-native tools (such as Azure CLI) or explicit Linux shell examples, which may give the impression of a Windows-first or Windows-tools bias.

Recommendations:

In the 'Next steps' section, add references to Azure CLI and its equivalent commands for managing Lab Services, ensuring Linux users see parity in tooling.
Where PowerShell is mentioned, clarify that Azure CLI is also fully supported and provide links to relevant CLI documentation.
Consider including a brief note in the prerequisites or introduction that the Python SDK and examples work identically on Linux, macOS, and Windows.
If possible, provide example commands or scripts using bash or Azure CLI alongside PowerShell references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for generating an access token, but the PowerShell example is more detailed and appears after the Bash example, which is a positive sign. However, throughout the document, all instructions for portal-based actions (such as app registration, role assignment, and resource creation) are described in a way that assumes use of the Azure Portal GUI, which is more familiar to Windows users. There are no CLI-based (e.g., Azure CLI) instructions for Linux users for these steps. The only command-line examples are for token generation, and while Bash is included, there is a heavier focus on PowerShell with more detailed scripting. There are no references to Linux-specific tools or patterns, and no mention of how to perform the same tasks using the Azure CLI or other cross-platform tools.

Recommendations:

Add Azure CLI examples for all steps that can be performed via CLI, such as resource provider registration, app registration, role assignment, and token generation.
Ensure that for every PowerShell example, there is a corresponding Bash/Azure CLI example with equal detail and explanation.
Include explicit instructions or links for Linux/macOS users, especially for steps that are currently only described using the Azure Portal GUI.
Avoid assuming the use of the Azure Portal for all actions; provide parity for users who prefer or require command-line tools.
Where screenshots are used, consider including CLI output examples or terminal screenshots to balance the visual focus.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to create and assign custom RBAC roles using the Azure Portal, which is a graphical interface accessible from any OS, but does not mention or provide any command-line examples. There are no references to PowerShell, Windows tools, or CLI commands, but the lack of Azure CLI (cross-platform) or Bash examples means Linux users do not see parity in automation or scripting guidance. The documentation implicitly assumes a GUI-first workflow, which is more common among Windows users.

Recommendations:

Add Azure CLI examples for creating and assigning custom roles, as the CLI is cross-platform and widely used on Linux.
Include Bash shell command examples for downloading and editing JSON files, to complement the GUI instructions.
Explicitly mention that all steps can be performed from any OS using the Azure CLI, and link to relevant CLI documentation.
If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Hyper-V (a Windows virtualization platform) first and in detail, while VMware ESXi (a cross-platform solution) is mentioned second. There is no mention of Linux-native virtualization platforms (such as KVM or Xen), nor are there any Linux-specific instructions, tools, or examples. The documentation does not provide parity for Linux administrators or environments.

Recommendations:

Add support information and examples for Linux-native virtualization platforms (e.g., KVM, Xen) if supported, or explicitly state if they are not supported.
Include Linux-specific instructions or considerations for deploying and managing the Data Box Gateway, such as recommended distributions, package dependencies, or configuration steps.
Provide parity in examples and tooling references, ensuring that both Windows and Linux administrators can follow the documentation without ambiguity.
If only Hyper-V and VMware are supported, clarify the lack of Linux-native hypervisor support and provide guidance for Linux users on how to proceed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by specifically mentioning Windows (e.g., launching from the Start menu) when describing how to run Azure IoT explorer, while not providing equivalent details or examples for Linux users. There are no Linux-specific instructions or examples, and the only platform-specific launch method mentioned is for Windows.

Recommendations:

Add explicit instructions for launching Azure IoT explorer on Linux (e.g., using AppImage, .deb, or .tar.gz, and how to run from terminal or create desktop shortcuts).
Mention Linux alongside Windows when describing installation and launch procedures, ensuring parity in the level of detail.
Include troubleshooting tips or known issues relevant to Linux users if applicable.
Where platform-specific behavior is described, provide parallel guidance for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes management of Azure Key Vault and Azure Stack Edge resources through the Azure Portal UI, with no mention of command-line tools or automation. There are no examples or instructions for using CLI tools such as Azure CLI, PowerShell, or Bash scripts. While this avoids explicit Windows-only tools, the lack of any Linux-oriented or cross-platform command-line examples (e.g., Azure CLI usage) implicitly favors Windows/GUI workflows, which are more common in Windows environments. There are also no references to Linux tools or patterns.

Recommendations:

Add Azure CLI examples for all key vault and resource management tasks, as Azure CLI is cross-platform and widely used on Linux.
Where relevant, provide Bash script snippets for automating common tasks (e.g., activation key generation, secret retrieval, key vault recovery).
Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI, and provide equivalent command-line instructions alongside portal steps.
If PowerShell examples are added, ensure Azure CLI or Bash equivalents are always provided and appear before or alongside PowerShell.
Reference documentation for CLI-based management (e.g., links to Azure CLI Key Vault docs) for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it mentions both Windows and Linux support, it provides explicit guidance and links for preparing a Windows VHD but omits equivalent instructions or links for preparing a Linux VHD. The reference to password complexity requirements links to Windows-specific documentation. In the 'Add a VM image' section, the only preparation link is for Windows, and Linux is only mentioned as an OS type in a dropdown. The connection instructions for Linux and Windows VMs are separated, but the actual connection steps are included via external includes, so parity there cannot be assessed from this page alone.

Recommendations:

Add a dedicated section or link for preparing a generalized image from a Linux VHD, similar to the Windows VHD preparation link.
When mentioning password requirements, provide a link to Linux VM password requirements or a cross-platform reference, not just the Windows-specific FAQ.
Ensure that all steps and examples (such as VHD preparation, troubleshooting, and connection instructions) are provided for both Windows and Linux, either inline or via clear links.
If using includes for connection instructions, verify that both Linux and Windows connection guides are equally detailed and accessible.
Consider presenting Windows and Linux options in parallel throughout the documentation, rather than referencing Windows first or exclusively.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides explicit, step-by-step instructions for importing certificates on Windows clients only, with no mention of how to perform equivalent actions on Linux or macOS systems. All client-side examples and screenshots are Windows-specific, and there is no guidance for non-Windows users.

Recommendations:

Add a section detailing how to import certificates on Linux clients, including common desktop environments (e.g., GNOME, KDE) and command-line methods (such as using update-ca-certificates or trust commands).
Include instructions or references for macOS users on how to add certificates to the System or User keychain.
Where possible, present cross-platform instructions together, or clearly label platform-specific steps, to ensure parity and inclusivity.
Add a note at the beginning of the 'Import certificates to client' section indicating that instructions are available for multiple operating systems, and provide links or tabs for each.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page for Azure Stack Edge Pro with GPU exhibits mild Windows bias. It references BitLocker for encryption, which is a Windows-specific technology, and does not mention Linux-native alternatives. There are no explicit examples or instructions for either Windows or Linux, but the mention of BitLocker without Linux equivalents or cross-platform alternatives suggests a preference for Windows tooling. Additionally, there are no command-line or usage examples provided for either platform, but the absence of Linux-specific references (e.g., LUKS for encryption) is notable.

Recommendations:

When referencing encryption, mention both BitLocker (for Windows) and LUKS or dm-crypt (for Linux) as supported or possible options, or clarify platform support.
If providing examples or instructions in future documentation, ensure both Windows (PowerShell, Command Prompt) and Linux (bash, shell) workflows are included.
Explicitly state platform compatibility and management options for both Windows and Linux administrators.
Include references to Linux-native tools and patterns where relevant, especially in sections discussing device management, diagnostics, or encryption.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by consistently mentioning SMB (a Windows-centric protocol) before NFS (a Linux/UNIX-centric protocol) when discussing storage backends. The examples and explanations focus on SMB shares, with NFS only mentioned as an alternative, and there are no explicit Linux command-line or tooling examples. There is also a lack of parity in discussing Linux-native storage tools or patterns, and no Linux shell or CLI examples are provided.

Recommendations:

Alternate the order of SMB and NFS mentions, or lead with NFS in some sections to avoid the impression of Windows-first bias.
Provide explicit examples for both SMB and NFS, including sample YAMLs or CLI commands for each.
Include Linux-native command-line examples (e.g., using Linux shell or kubectl from a Linux terminal) where appropriate.
Discuss Linux/UNIX storage patterns or tools (such as mounting NFS shares via Linux commands) alongside or before Windows-centric approaches.
Clarify that both SMB and NFS are supported equally, and provide guidance for Linux users on best practices for NFS-backed storage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents SMB (the Windows protocol) as the default and standard, mentioning it before NFS (the Linux protocol) in all relevant sections. While NFS is acknowledged as the Linux option, there are no concrete examples or instructions for Linux users (e.g., no Linux mount commands or guidance for accessing shares from Linux clients). Additionally, user management and permission modification references are Windows-centric (e.g., 'use File Explorer to modify these permissions'), with no Linux equivalents provided.

Recommendations:

Provide explicit Linux/NFS examples, such as sample mount commands for NFS shares (e.g., 'mount -t nfs ...').
Balance the order of protocol presentation: alternate or clarify that SMB is for Windows and NFS is for Linux, rather than always listing SMB first.
Include instructions or references for managing permissions from Linux clients (e.g., using chmod/chown or NFS export options).
Where File Explorer or other Windows tools are mentioned, add equivalent Linux tools (e.g., Nautilus, command-line instructions) or note their absence.
Add screenshots or walkthroughs for Linux client scenarios, not just Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents Azure CLI and Azure portal instructions, but when referencing command-line usage, it does not provide any OS-specific guidance or examples. There are no explicit Windows-only tools (like PowerShell), but the lack of Linux/macOS-specific notes or examples (such as shell differences, package managers, or environment setup) means Linux users may not have full parity or clarity. The documentation implicitly assumes a Windows or generic environment, with no mention of Linux-specific considerations.

Recommendations:

Explicitly mention that Azure CLI commands are cross-platform and provide any OS-specific installation or usage notes, especially for Linux/macOS users.
Include examples or notes for common Linux/macOS shell environments (e.g., bash, zsh) where command syntax or environment variables might differ.
Add troubleshooting tips or prerequisites for Linux (such as required dependencies or permissions).
Reference Linux package managers (apt, yum, etc.) in the Azure CLI installation section.
If screenshots or file paths are shown, provide both Windows and Linux/macOS variants where relevant.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by referencing BitLocker (a Windows-specific encryption technology) as the only example for encryption-at-rest, without mentioning Linux alternatives or providing guidance for Linux users. There are no command-line examples or tooling references for Linux or cross-platform certificate management, and no mention of Linux-compatible certificate formats or tools.

Recommendations:

Include references to Linux-compatible encryption-at-rest solutions (e.g., dm-crypt/LUKS) or clarify if BitLocker is the only supported method.
Provide guidance or examples for certificate management using cross-platform or Linux-native tools (such as OpenSSL) alongside any Windows-specific instructions.
Mention supported certificate formats and how to generate them on both Windows and Linux.
If the device or portal is platform-agnostic, explicitly state so and provide parity in instructions for both Windows and Linux users.
If BitLocker is a hard requirement, clarify this early and suggest workarounds or alternatives for Linux environments if possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively referencing BitLocker (a Windows disk encryption technology) for device encryption and recovery. There are no mentions of Linux-based encryption tools or instructions for Linux users, nor are there any Linux command-line examples or guidance for handling the key file on non-Windows systems.

Recommendations:

Include references to Linux-compatible disk encryption and recovery tools, or clarify if the device is only compatible with BitLocker.
Provide guidance or examples for Linux users on how to handle, store, and use the downloaded key file (e.g., using Linux command-line tools to inspect or manage the JSON file).
If the device is managed exclusively through a web UI and is OS-agnostic, explicitly state this to reassure non-Windows users.
If BitLocker is mandatory due to device design, add a note explaining this requirement and suggest best practices for Linux/Mac users in managing BitLocker keys.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation mentions PowerShell as an alternative to the Azure CLI and REST API for management tasks, listing it before REST API and alongside Azure CLI. This subtly prioritizes Windows tooling by explicitly naming PowerShell, which is primarily a Windows-centric tool, and by listing it before REST API. There are no explicit Linux examples or Linux-specific tools mentioned, and no indication of parity in examples or instructions for Linux users.

Recommendations:

Explicitly mention Bash or shell scripting as an alternative alongside PowerShell and Azure CLI, to acknowledge Linux users.
Ensure that any referenced guides (such as those for Azure CLI or PowerShell) provide both Windows and Linux usage examples.
Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and provide links or notes for Linux/macOS usage.
Consider listing Azure CLI before PowerShell, as it is the more cross-platform tool.
Add a note or section highlighting cross-platform compatibility and where to find Linux/macOS-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by linking to the Windows-specific Azure Instance Metadata Service documentation in the 'Next steps' section, without referencing the Linux equivalent. There are no operating system-specific examples or commands, but the only direct link for further learning is for Windows, and there is no mention of Linux or cross-platform guidance.

Recommendations:

Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation in the 'Next steps' section.
Explicitly state that the IMDS REST API is OS-agnostic and can be accessed from both Windows and Linux VMs.
Provide example commands for retrieving metadata using common Linux tools (e.g., curl or wget) alongside any Windows/Powershell examples.
Ensure that troubleshooting and support guidance is not Windows-centric and covers common issues for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal (a web-based GUI) for managing Microsoft Dev Box dev centers and does not provide any command-line examples. There is an implicit Windows bias as the Azure portal is most commonly used and documented in Windows-centric environments, and there are no CLI, PowerShell, or Azure CLI/Bash examples. There is also no mention of Linux tools, workflows, or parity for users who may prefer or require non-Windows environments.

Recommendations:

Add equivalent instructions for managing dev centers using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include Bash shell examples for common tasks such as creating, deleting, and assigning permissions to dev centers.
Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide links or steps for CLI-based management for users who prefer or require non-GUI workflows.
Ensure that any screenshots or step-by-step instructions do not assume a Windows-only environment (e.g., avoid referencing Windows-specific UI elements or terminology).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses Windows-style backslashes in folder paths (e.g., 'digital-twins-samples-main\AdtSampleApp\SampleClientApp') and does not provide equivalent Linux/macOS path examples. There are no Linux-specific instructions or examples, which may confuse or exclude users on non-Windows platforms.

Recommendations:

Provide folder navigation examples using both Windows (backslash) and Linux/macOS (forward slash) path separators.
Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where differences exist.
Include a note or section for Linux/macOS users to clarify any differences in file paths or commands.
Review referenced includes (e.g., 'digital-twins-local-credentials-outer.md') to ensure they also offer cross-platform guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a note specifically for Mac users to adapt a date command, but does not mention Linux at all. This omission implies a Windows (or at least non-Linux) default, as Linux users are left without guidance, despite the high similarity between Mac and Linux shells. There is also no explicit Linux example or command adaptation.

Recommendations:

Explicitly mention Linux alongside Mac in the note, as the command adaptation is likely the same.
Provide a Linux-specific example or clarify that the Mac instructions also apply to Linux.
Consider rephrasing the note to: 'When executing the commands on Mac or Linux, replace `date -Is` with `date +%FT%T%z`.'
Audit other documentation pages for similar omissions to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides an ARM template example that exclusively references Windows Server images and OS versions, with no mention of Linux options or examples. The parameters and variables are all tailored to Windows (e.g., 'MicrosoftWindowsServer', 'WindowsServer', and specific Windows Server versions), and there is no guidance or parity for deploying Linux-based environments.

Recommendations:

Include Linux image options in the ARM template, such as Ubuntu, CentOS, or other popular distributions.
Add a parallel example or section demonstrating how to connect a Linux VM to the lab's VNet, including relevant parameters and variables.
Mention both Windows and Linux scenarios in the introductory and instructional text to ensure cross-platform applicability.
Provide guidance or links for customizing the template for Linux environments, including admin username conventions and SSH key authentication.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Microsoft Sentinel and Defender for IoT, both of which are Microsoft cloud-based tools. There are no explicit examples or instructions that are specific to Windows or PowerShell, but the documentation exclusively references Microsoft tools and workflows, with no mention of Linux-based alternatives, command-line examples, or cross-platform considerations. There are no Linux-specific instructions, nor is there any guidance for users who may be operating in non-Windows environments.

Recommendations:

Include examples or references for integrating Defender for IoT and SIEM/SOAR workflows in Linux environments, such as using Linux-based log shippers or open-source SIEM tools.
Provide command-line examples that are cross-platform, or specify how to perform relevant tasks using Bash or Linux CLI tools where applicable.
Mention any platform requirements or compatibility notes, especially if certain features are only available or best supported on Windows.
If possible, highlight how Linux-based SOC teams can interact with Microsoft Sentinel (e.g., via REST APIs, CLI tools, or SDKs available for Linux).
Add documentation or links for users who may want to use non-Microsoft tools or hybrid environments, ensuring broader applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally platform-neutral in its main instructions, focusing on CSV file manipulation and web UI actions. However, in the 'Next steps' section, it specifically references 'Detect Windows workstations and servers with a local script' as a follow-up, without mentioning Linux or cross-platform alternatives. Additionally, downloadable example files are in Excel (.xlsx) format, which is more closely associated with Windows environments, though CSV is also supported. There are no explicit Linux examples or references to Linux tools or workflows.

Recommendations:

Include references to Linux or cross-platform device detection scripts in the 'Next steps' section, or clarify if such scripts are not available.
Provide example workflows or notes for editing CSV files using Linux-native tools (e.g., nano, vim, LibreOffice Calc) in addition to Excel.
If possible, offer downloadable example files in open formats (CSV only) and avoid referencing Excel-specific formats unless necessary.
Ensure parity in documentation by mentioning both Windows and Linux environments where relevant, especially in follow-up resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a 'windows_first' and 'windows_tools' bias by exclusively referencing the Azure portal (a web UI optimized for Windows/Edge), Azure Key Vault, and Azure DevOps tools throughout all workflows. There are no Linux-specific instructions, CLI/bash examples, or references to cross-platform command-line tools. All screenshots and navigation steps assume a GUI workflow typical of Windows-centric environments, and there is no mention of Linux-native tooling or alternative approaches for Linux users.

Recommendations:

Provide equivalent instructions using the Azure CLI and/or Azure PowerShell for all major workflows (e.g., adding catalogs, configuring managed identities, managing Key Vault secrets).
Include bash shell command examples for Linux users, especially for tasks like cloning repositories, managing secrets, and interacting with Azure resources.
Explicitly state that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific prerequisites.
Add screenshots or terminal output examples from Linux environments where relevant.
Reference cross-platform tools (such as az CLI) before or alongside GUI-based instructions.
Where GUI navigation is described, offer parallel CLI or REST API instructions for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by exclusively referencing RDP (Remote Desktop Protocol) sessions as the trigger for the auto-stop feature, with no mention of Linux remote desktop protocols (such as SSH or VNC) or scenarios. All examples and explanations assume Windows usage patterns, and there are no Linux-specific instructions or considerations.

Recommendations:

Clarify whether the auto-stop feature supports non-RDP (e.g., SSH, VNC) disconnects, especially for Linux-based dev boxes.
If Linux dev boxes are supported, provide equivalent examples and explanations for Linux remote access protocols.
Explicitly state any platform limitations (e.g., 'This feature currently only applies to Windows dev boxes using RDP').
Include guidance for administrators managing Linux dev boxes, or link to relevant documentation if supported elsewhere.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page refers to 'passwords for your Windows VMs' and 'public SSH keys for your Linux VMs', but all subsequent examples and screenshots are generic and do not provide platform-specific guidance. However, the initial mention of Windows passwords before Linux SSH keys suggests a subtle 'windows_first' bias. There are no Linux-specific examples or screenshots, and no mention of Linux command-line tools or workflows, indicating a lack of Linux parity.

Recommendations:

Provide explicit Linux-focused examples, such as how to use secrets for Linux VM provisioning (e.g., using secrets for SSH keys or environment variables).
Include screenshots or command-line instructions relevant to Linux users, such as using the Azure CLI or bash scripts.
Ensure that Linux use cases (e.g., storing and retrieving SSH keys) are described with equal prominence and detail as Windows password scenarios.
Where possible, alternate the order of Windows and Linux references, or present them together, to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses on redeploying VMs in Azure DevTest Labs with a clear emphasis on Windows-based VMs, mentioning remote desktop connection and troubleshooting for Windows VMs. There are no references to Linux VMs, SSH connectivity, or Linux-specific troubleshooting, and all examples and terminology are Windows-centric.

Recommendations:

Include references to Linux-based VMs and scenarios where redeployment may help (e.g., SSH connection issues).
Mention both RDP (for Windows) and SSH (for Linux) as common remote access methods that may require redeployment troubleshooting.
Add examples or notes for Linux users, such as what to do if SSH access fails and how redeployment affects Linux VMs.
Ensure that language is inclusive of both Windows and Linux VM users throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows as the default operating system in examples (App Service plans and web apps), with no mention of Linux or cross-platform options. There are no Linux-specific instructions or parity in the walkthrough, and the runtime stack is limited to .NET Core, which is cross-platform, but the hosting environment is Windows-only in all examples.

Recommendations:

Include examples for both Windows and Linux App Service plans in the configuration tables.
Explicitly mention that App Service plans and web apps can be created on Linux, and provide step-by-step instructions or notes for Linux users.
Show at least one example using a Linux runtime stack (e.g., Node.js, Python, or .NET Core on Linux) to demonstrate cross-platform support.
Clarify in the prerequisites or relevant sections that the process is applicable to both Windows and Linux environments.
Where UI steps are given, note any differences for Linux-based App Services if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally presents Windows tools and workflows (such as Hyper-V and Microsoft Configuration Manager) as the default or only options for creating and managing custom images, with Linux alternatives mentioned but not equally detailed. In several places, Windows is mentioned before Linux, and the tooling focus is on Microsoft/Windows-specific solutions.

Recommendations:

When listing steps or options, alternate the order in which Windows and Linux are mentioned, or present them together (e.g., 'Windows or Linux') to avoid implicit prioritization.
Include Linux-native tools and workflows (such as KVM, qemu-img, or virt-manager) alongside Windows tools like Hyper-V for creating VHDs, and provide links to relevant Linux documentation.
Where Microsoft Configuration Manager is mentioned, suggest open-source or Linux-native alternatives for image creation and management (e.g., Packer, Clonezilla, or Ansible).
Ensure that all example workflows and tool recommendations are equally detailed for both Windows and Linux, including step-by-step guides and troubleshooting tips.
Add explicit notes or sections for Linux users where Windows-specific instructions or tools are referenced.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing the Windows App for resuming a dev box and troubleshooting connectivity issues specifically via the RDP (Remote Desktop Protocol) app, which is primarily a Windows technology. There are no explicit Linux or cross-platform client examples or troubleshooting steps, and the only CLI shown is Azure CLI, which is cross-platform but not accompanied by Linux-specific context or alternative remote access methods.

Recommendations:

Include instructions or notes for resuming a dev box using Linux or macOS clients, such as through cross-platform remote desktop clients (e.g., Remmina, FreeRDP, or Microsoft Remote Desktop for Mac).
In troubleshooting, mention Linux/macOS remote desktop clients and provide guidance for users who are not using the Windows RDP app.
Avoid phrasing that assumes the user is on Windows (e.g., 'the Windows App'); instead, clarify if there are equivalent apps or steps for other platforms.
If there are platform-specific limitations or differences, explicitly document them and provide workarounds or alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides code examples and instructions primarily using the .NET SDK (C#) and references Visual Studio Code for model authoring, but does not offer any Linux- or cross-platform-specific command-line examples (e.g., Bash, curl, or Python). There is no mention of Linux-specific tools or shell environments, and no explicit parity for Linux users in the examples or tooling guidance. REST API and Azure CLI are mentioned but not exemplified. The documentation implicitly assumes a Windows/.NET development environment.

Recommendations:

Add explicit Linux-friendly examples, such as using curl or HTTPie for REST API calls, and Bash scripts for model management.
Provide Azure CLI command examples for all major operations (upload, retrieve, update, delete models), and ensure these are shown alongside or before SDK-specific examples.
Include Python SDK examples, which are cross-platform and popular in Linux environments.
Clarify that Visual Studio Code is cross-platform, and suggest alternative editors or tools commonly used on Linux if relevant.
Where possible, avoid assuming a .NET/C# development environment as the default; present REST API and CLI as primary options for cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses 'nslookup' as the sole example for DNS validation, with screenshots and references that appear to be from Windows Command Prompt. There are no examples or mentions of equivalent Linux/macOS tools (such as 'dig' or 'host'), nor are there instructions or screenshots for validating DNS from non-Windows environments. This presents a subtle Windows-first bias and omits guidance for Linux users.

Recommendations:

Include equivalent DNS validation commands for Linux/macOS, such as 'dig <domain>' and 'host <domain>', alongside 'nslookup'.
Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
Explicitly mention that DNS validation can be performed from any OS, and provide cross-platform instructions.
Where possible, use neutral language (e.g., 'run a DNS query using your preferred tool, such as nslookup, dig, or host') rather than referencing only Windows tools.
Consider a table or note summarizing common DNS query tools across platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page lists PowerShell samples before CLI samples in the 'Next steps' section, suggesting a Windows-first approach. There is also a specific callout to PowerShell, which is traditionally associated with Windows, without equal prominence given to Linux-native tools or Bash examples.

Recommendations:

List CLI (az CLI) or Bash samples before or alongside PowerShell samples to avoid implying Windows is the primary platform.
Explicitly mention that CLI samples are cross-platform and suitable for Linux, macOS, and Windows.
Add Bash or shell script examples where appropriate, or link to them if available.
Include a note clarifying that all templates can be deployed from any OS using the Azure CLI, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by highlighting the Az PowerShell module as the primary SDK integration and mentioning Windows and Linux auto-shutdown settings with Windows listed first. There are no Linux-specific command-line examples, and the only SDK/tooling example given is PowerShell, which is more commonly associated with Windows environments.

Recommendations:

Include CLI examples using Azure CLI (az), which is cross-platform and widely used on Linux.
When listing OS support (e.g., auto-shutdown), alternate or balance the order (e.g., 'Linux and Windows operating systems') or mention both equally.
Highlight or provide examples for Linux administrators, such as using bash scripts or Linux-native tools to interact with Azure Lab Services.
Mention or link to documentation for managing Azure Lab Services from Linux environments, ensuring parity with Windows tooling.
If referencing SDKs, provide example usage in both PowerShell and bash (Azure CLI), and clarify that all features are accessible from both environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only C#/.NET (NuGet) code samples and references to Windows-centric tooling (NuGet, AzureEventSourceListener), with no mention of Linux, cross-platform, or non-Windows development environments. There are no examples or guidance for Linux users, such as using Python, Node.js, or command-line tools commonly available on Linux.

Recommendations:

Add code samples in additional languages that are popular on Linux (e.g., Python, Node.js, Java).
Reference cross-platform SDKs and tools, not just .NET/NuGet.
Explicitly mention that the APIs and tools are cross-platform if applicable, and provide Linux-specific installation or usage notes where relevant.
Include instructions or examples for retrieving models using curl, wget, or other command-line tools available on Linux.
Provide guidance for setting up the development environment on Linux, including package installation and dependencies.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ visual_studio_heavy

Summary:

The documentation consistently lists Visual Studio (a Windows-centric IDE) before Visual Studio Code and Azure CLI in instructions for creating and publishing Azure Functions. While cross-platform tools like Azure CLI and VS Code are mentioned, the ordering and emphasis on Visual Studio may suggest a Windows-first approach. There are no explicit PowerShell-only commands or Windows-only tools, but the documentation could better highlight Linux parity.

Recommendations:

When listing development environments, alternate the order or explicitly state that all methods are cross-platform, with VS Code and Azure CLI being fully supported on Linux.
Add explicit notes or sections for Linux/macOS users, especially for common development and deployment workflows.
Provide example commands and screenshots from Linux terminals (e.g., bash) in addition to or instead of Windows-centric tools.
Clarify that Visual Studio Code and Azure CLI are recommended for Linux users, and link to Linux-specific setup guides where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but the PowerShell example is given equal prominence as the CLI example, which can be seen as a Windows bias since PowerShell is primarily a Windows tool (despite cross-platform support). There are no Linux-specific shell examples (such as Bash), and the validation steps focus on the Azure Portal UI, which is platform-agnostic but often associated with Windows workflows. The order of examples (CLI first, then PowerShell) is good, but the lack of explicit Linux/Bash guidance may disadvantage Linux users.

Recommendations:

Add explicit Bash shell examples for Linux users, highlighting any differences in environment variable syntax or command usage.
Clarify that Azure CLI commands work identically on Windows, macOS, and Linux, and provide notes on installing the CLI on Linux.
If PowerShell is included, mention that it is available cross-platform, but also provide Bash alternatives to ensure Linux parity.
Consider including a table or section summarizing deployment options for different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on creating Windows virtual machines, with no mention or example of Linux VMs. All VM-related steps and outputs are Windows-specific, and there are no Linux alternatives or parity in the walkthrough. While both Azure CLI and PowerShell are provided for verification, the core scenario is Windows-centric.

Recommendations:

Include parallel instructions and Terraform code samples for creating Linux virtual machines alongside Windows VMs.
Update the checklist and scenario description to mention both Windows and Linux VM creation, or provide a choice.
Add outputs and verification steps relevant to Linux VMs (such as SSH credentials, Linux admin username, etc.).
Ensure that the sample code repository referenced contains both Windows and Linux VM examples.
Consider providing a toggle or tabbed interface for users to choose between Windows and Linux scenarios throughout the guide.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial exclusively demonstrates creating and configuring a Windows Server virtual machine, including detailed steps for installing IIS via the Windows GUI and using RDP. There are no examples or instructions for deploying a Linux-based web server or using Linux-native tools. The documentation assumes a Windows environment throughout, omitting Linux alternatives.

Recommendations:

Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu or CentOS) and installing a web server such as Apache or Nginx.
Include Linux command-line examples for connecting to the VM (e.g., using SSH) and installing web server packages.
Provide screenshots or terminal output relevant to Linux environments.
Explicitly mention that either Windows or Linux VMs can be used, and link to relevant Azure documentation for both platforms.
Consider alternating or balancing the order of Windows and Linux examples to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes integration and log analysis using Azure Portal UI and Azure-native tools (Log Analytics Workspace, KQL), with no mention of command-line or scripting options for Linux users (such as Azure CLI, Bash, or REST API). There are no PowerShell or Windows-specific commands, but the absence of Linux-friendly examples or cross-platform CLI instructions creates an implicit bias toward Windows/GUI workflows.

Recommendations:

Add Azure CLI examples for enabling diagnostic settings and querying logs, which work cross-platform (Windows, Linux, macOS).
Include sample Bash scripts or REST API calls for automating log export and analysis.
Mention that all Azure Portal features are accessible from any OS with a browser, but provide parity for users who prefer or require CLI/scripted workflows.
If screenshots are used, consider including at least one from a Linux environment or clarify that the UI is OS-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation presents deployment options for AKS (Azure Kubernetes Service) and Windows, but does not mention or provide instructions for deploying the GCZ service on Linux (outside of AKS). The 'Windows' deployment option is specifically called out for development/testing, but there is no equivalent guidance for Linux environments, which are common for development and testing. This creates a Windows-first impression and omits Linux parity.

Recommendations:

Add a section or pivot for deploying the GCZ service on Linux (e.g., Ubuntu) for development and testing, similar to the Windows option.
If the service can run on Linux, provide step-by-step instructions or reference scripts for Linux-based deployment.
Ensure that any scripts, commands, or tooling mentioned for Windows (such as PowerShell or Windows-specific paths) have Linux equivalents (e.g., Bash scripts, Linux file paths).
Explicitly mention Linux as a supported platform for development/testing if applicable, or clarify if there are technical limitations.
Review included files (e.g., deploy-gcz-on-windows.md) to ensure Linux users are not excluded from development/test scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes deploying ARM templates and interacting with Azure services through the Azure Portal, with a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative deployment methods. However, the only explicit link for further deployment instructions points to a PowerShell-specific page, and there are no direct Linux or cross-platform CLI examples provided. This may lead Linux users to feel secondary or unsupported.

Recommendations:

Provide explicit Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Link to both Azure CLI and PowerShell deployment documentation in the 'Deploy the template' section, not just the PowerShell page.
Include a short example of deploying the ARM template using Azure CLI (e.g., az deployment group create ...) directly in the quickstart.
Mention that all steps can be performed from Linux, macOS, or Windows, and clarify that the Azure Portal and Azure CLI are fully supported on all platforms.
If scripting is shown, ensure both Bash (for Linux/macOS) and PowerShell (for Windows) examples are present.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows environments by exclusively referencing the Azure Portal (a web GUI) and Visual Studio Code for all steps, without mentioning or providing examples for command-line tools commonly used on Linux (such as Azure CLI or deployment via terminal). There are no Linux-specific instructions or alternatives for creating, configuring, or deploying Azure Functions, nor are there any references to Bash or shell commands. The instructions assume GUI-based workflows, which are more common in Windows-centric documentation.

Recommendations:

Provide equivalent instructions using Azure CLI for all major steps, including function creation, configuration, and deployment.
Include examples for deploying and managing Azure Functions from a Linux terminal (Bash), not just via Visual Studio Code.
Mention and link to documentation for cross-platform tools (e.g., Azure CLI, azcopy) alongside Azure Portal instructions.
Add a note clarifying that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant platform-specific guides.
Where screenshots are used, consider including terminal output or command snippets as alternatives for users not using the Azure Portal GUI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias by focusing exclusively on Postman (a GUI tool most commonly used on Windows) for API interactions, and by not providing explicit Linux command-line examples for key steps such as file uploads or API calls. While the use of bash scripts and Python-based sdutil suggests some cross-platform intent, there are no Linux-specific instructions or examples, and the initial setup and workflow are described primarily through GUI-based tools rather than CLI alternatives that are more common in Linux environments.

Recommendations:

Provide explicit Linux command-line examples for all API interactions, especially for uploading files and making API calls (e.g., using curl or httpie).
Include instructions for installing and using Postman on Linux, or suggest alternative CLI tools for Linux users.
When referencing scripts (such as prepare-records.sh), clarify any OS-specific dependencies or steps, and provide troubleshooting tips for Linux environments.
Ensure that all steps that can be performed via CLI (such as sdutil commands or curl requests) are documented with equivalent Linux shell commands and not just GUI screenshots.
Add a section or callouts highlighting any differences or considerations for Linux users, such as file path conventions or required dependencies.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to enable managed identity for an Azure Event Grid partner topic using the Azure portal, which is a graphical interface accessible from any OS, but does not provide any command-line examples (such as Azure CLI or PowerShell). There is no mention of Linux-specific tools or workflows, nor are there any CLI instructions that would be platform-neutral. The absence of CLI examples may implicitly favor Windows users, who are more likely to use the portal or PowerShell, while Linux users often prefer Azure CLI.

Recommendations:

Add Azure CLI examples for assigning system-assigned and user-assigned identities to Event Grid partner topics.
Include explicit instructions or links for performing these tasks using command-line tools on Linux, macOS, and Windows.
Ensure that any referenced scripts or commands are cross-platform, and clarify which tools are available on each OS.
Consider adding a section titled 'Using Azure CLI' or 'Command-line instructions' to provide parity for users who do not use the Azure portal.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any platform-specific examples, but the only code sample link in 'Next steps' points to a .NET (Windows-centric) sample. There are no explicit Linux or cross-platform code samples or command-line instructions, and the documentation does not mention Linux tools or patterns. This subtly prioritizes Windows by omission and by linking to a Windows-first technology.

Recommendations:

Include links to cross-platform or Linux-specific code samples (e.g., Python, Java, or Node.js examples) in the 'Next steps' section.
Add explicit mention of cross-platform compatibility for the authentication and authorization flows.
Provide sample commands or scripts for both Windows (PowerShell) and Linux (Bash/CLI) environments where relevant.
Ensure that the documentation references tools and patterns that are available on both Windows and Linux, or provides alternatives for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by exclusively describing role assignment and management steps using the Azure Portal UI, which is most commonly accessed via Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no Linux-specific instructions or parity for role assignment or authentication workflows. The absence of CLI or cross-platform automation examples may disadvantage Linux users or those who prefer scripting.

Recommendations:

Add Azure CLI examples for role assignment and authentication, which work across Windows, Linux, and macOS.
Include Bash shell command examples for obtaining JWT tokens and interacting with Azure resources.
Explicitly mention that the Azure Portal is accessible from any OS, and provide parity for users who prefer command-line or automated approaches.
If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided alongside.
Highlight any OS-agnostic tools or SDKs (such as the Azure Identity client library) with examples in multiple languages where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page shows a subtle Windows bias by prioritizing .NET (a Microsoft/Windows-centric technology) at the top of all SDK tables and providing a dedicated section for .NET packages, including legacy Windows-specific libraries. There is also mention of 'WindowsAzure.Messaging' and 'Windows.Azure.ServiceBus', reinforcing Windows-centric naming and history. However, there are no explicit PowerShell examples or exclusive Windows command-line tools, and Linux/Unix equivalents are not omitted but are not given equal prominence.

Recommendations:

Reorder SDK tables or rotate the first-listed language/platform to avoid always leading with .NET/Windows-centric technologies.
Add equivalent dedicated sections for other major platforms (e.g., Java, Python) to match the detailed .NET section.
Clarify cross-platform compatibility for all SDKs, especially .NET Standard, and explicitly mention Linux/macOS support where applicable.
Avoid Windows-centric naming in new documentation and highlight any platform-specific differences or requirements.
Where legacy Windows-only libraries are mentioned, provide context for Linux users and suggest modern, cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by using Windows-style path separators (backslashes) in the Maven command and by referencing Eclipse GUI steps without mentioning Linux alternatives or command-line options. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility or provide parity for Linux users.

Recommendations:

Provide both Windows and Linux/macOS command examples, especially for Maven commands (e.g., use forward slashes for Linux/macOS).
Mention that Eclipse is available on multiple platforms, and consider including command-line alternatives for project creation (e.g., using 'mvn archetype:generate').
Explicitly state that the instructions are cross-platform, or call out any platform-specific steps.
Add notes or sections for common Linux development environments and tools (e.g., IntelliJ IDEA, VS Code, or command-line workflows).
Ensure all file paths and configuration examples use platform-neutral syntax or provide both variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking only to instructions for configuring DSCP markings on Windows 10 clients and referencing Skype for Business/Teams workloads in a Windows-centric context. There are no examples or guidance for Linux or cross-platform environments, and no mention of Linux tools or methods for setting QoS/DSCP values.

Recommendations:

Include references or links to documentation for configuring DSCP markings and QoS policies on Linux systems (e.g., using iptables, tc, or systemd-networkd).
Provide cross-platform examples or a table summarizing how to set DSCP markings on both Windows and Linux clients.
Avoid linking exclusively to Windows-specific guides; instead, offer parallel guidance for Linux or note the absence of such guidance.
Explicitly mention whether the recommendations and requirements apply to non-Windows clients and, if so, how to implement them.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Azure DNS (which is tightly integrated with Azure and often managed via Windows-centric tooling) and by providing code and configuration examples that assume .NET and C# (which are historically more common on Windows). There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, dig for DNS), nor are Linux-native tools or patterns mentioned. The only DNS client library referenced is DnsClient.NET, with no mention of Linux tools like dig or nslookup. No PowerShell is present, but the absence of Linux/Unix equivalents and the focus on .NET/C# patterns suggest a Windows-oriented perspective.

Recommendations:

Include Linux-native command-line examples for DNS operations, such as using 'dig' or 'nslookup' to query CNAME and SRV records.
Mention cross-platform or Linux-friendly DNS client libraries (e.g., Python's dnspython, Node.js dns module) alongside DnsClient.NET.
Provide code samples in additional languages popular on Linux (e.g., Python, JavaScript, Java) in addition to C#.
Explicitly state that the patterns and techniques are platform-agnostic where possible, and highlight any platform-specific considerations.
Reference Linux-based infrastructure options (e.g., hosting the failover file on an NGINX/Apache server) in the file-share failover section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively deploys Windows Server virtual machines in its example scenario, with no mention of Linux VM options or parity. All VM-related steps and resources reference only Windows, and there are no examples or guidance for deploying or managing Linux VMs in the same context.

Recommendations:

Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside Windows VM examples.
Update the scenario description to mention both Windows and Linux VM deployment options, or provide a rationale for the Windows-only focus.
Add a section or note explaining how to adapt the Terraform configuration for Linux VMs, including any differences in variables or resources.
Ensure that any scripts, troubleshooting, or verification steps are not Windows-specific, or provide Linux equivalents where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation primarily describes the auto-shutdown feature in a general way but includes a prominent note that Linux support is limited and varies by distribution. There are no Linux-specific instructions, screenshots, or examples, and the limitations for Linux are only mentioned in a side note. The main flow assumes parity but does not provide Linux-focused guidance or alternatives.

Recommendations:

Provide explicit Linux-specific instructions or examples, including any UI differences or additional configuration steps required for supported distributions.
Include screenshots or illustrations showing the experience for Linux-based labs, if different.
List supported and unsupported Linux distributions more clearly, possibly in a table.
Mention Linux limitations earlier in the workflow, not just in a note, to set expectations.
Offer troubleshooting or workaround guidance for Linux users, especially for unsupported images like Data Science Virtual Machine - Ubuntu.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples, but the PowerShell (Windows-centric) example appears first and is more detailed, with step-by-step variable assignments and explanations. The CLI (cross-platform) example is shorter and less detailed. There are no Linux-specific tools or shell examples, and the structure implicitly prioritizes Windows/PowerShell usage.

Recommendations:

Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux users.
Ensure that both PowerShell and CLI sections have equivalent detail and explanation, so Linux users are not disadvantaged.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux shell context (e.g., bash variable usage if needed).
Consider adding bash or shell script examples where appropriate, especially for steps involving multiple commands or variables.
If referencing tools or commands that are Windows-specific (like PowerShell cmdlets), always provide a CLI or bash alternative.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses the Azure portal GUI for all instructions and does not provide any command-line examples. There are no references to PowerShell, Windows tools, or CLI commands, but the lack of Azure CLI or Linux-based instructions means Linux users do not have parity. The documentation implicitly assumes a GUI-first (and thus, often Windows-first) workflow, which may disadvantage users who prefer or require command-line or Linux-native approaches.

Recommendations:

Add equivalent Azure CLI instructions for each step, ensuring they work on Linux, macOS, and Windows.
Explicitly mention that all steps can be performed using the Azure CLI or Azure PowerShell, and provide links to relevant documentation.
Where verification steps are described (e.g., viewing ARP tables or route tables), include CLI commands (such as az network express-route or az network vnet-gateway) alongside portal instructions.
Ensure that any references to tools or workflows are cross-platform, or provide alternatives for Linux/macOS users.
Consider including a table or section comparing portal, Azure CLI, and PowerShell workflows for each major step.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias by referencing Azure portal UI patterns and domain names that are Windows-centric (e.g., *.servicebus.windows.net) without mentioning Linux tools or command-line alternatives. There are no examples or instructions for Linux users (e.g., using Azure CLI, shell commands, or Linux-based verification methods), and all post-migration verification is described via the Azure portal, which is platform-agnostic but often more familiar to Windows users. No PowerShell or explicit Windows-only tools are mentioned, but the absence of Linux-specific guidance or parity is notable.

Recommendations:

Add Linux command-line examples for creating namespaces and event hubs using Azure CLI.
Include instructions for retrieving the connection string and FQDN using Azure CLI or az commands.
Provide alternative post-migration verification steps using Azure CLI or REST API, not just the Azure portal.
Explicitly mention that the instructions apply equally to Linux and macOS users, and provide shell command snippets where appropriate.
If referencing domain names, clarify that these are not Windows-specific and apply to all platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking to instructions for enabling managed identity specifically on Windows VMs, without mentioning or providing equivalent Linux VM instructions. Additionally, the sample application and walkthrough focus exclusively on .NET (ASP.NET Core) and do not provide Linux-oriented or cross-platform examples, nor do they reference Linux command-line tools or deployment scenarios.

Recommendations:

Include links and instructions for enabling managed identities on both Windows and Linux VMs, or reference a platform-agnostic guide.
Provide sample applications or walkthroughs for Linux-based environments (e.g., using Python or Java on Linux App Service or VMs).
Add examples or references for deploying and authenticating from Linux containers or command-line tools (such as Azure CLI on Linux).
Ensure that sample code and deployment steps are not limited to Windows/.NET, but also cover other common stacks used on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by referencing the Azure portal and .NET samples first, and by not providing explicit Linux or cross-platform command-line examples for authentication or role assignment. While it does mention Azure CLI in the related content, the main instructions and code samples focus on .NET (a Windows-centric technology) and the Azure portal, with no explicit Linux shell or cross-platform scripting examples. There are no PowerShell-heavy sections, but the absence of Linux-specific or cross-platform examples is notable.

Recommendations:

Include explicit Linux and cross-platform command-line examples (e.g., using Azure CLI in Bash) for key tasks such as application registration, role assignment, and token acquisition.
Balance .NET code samples with equivalent samples in Python or JavaScript, which are widely used on Linux.
When referencing the Azure portal, also provide CLI alternatives for users who prefer or require non-GUI workflows.
Ensure that sample links and walkthroughs include Linux-friendly instructions and note any OS-specific requirements or differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not provide any platform-specific configuration examples, but the only 'Next steps' link refers to using the Azure portal, which is a graphical tool most commonly used on Windows. There are no CLI, PowerShell, or Linux-based instructions or references, and no mention of cross-platform tools or automation approaches. This may implicitly bias the documentation towards Windows users and those using the Azure portal, while omitting parity for Linux or CLI-based workflows.

Recommendations:

Add explicit instructions and examples for configuring BGP communities using cross-platform tools such as Azure CLI and Azure PowerShell, ensuring both Windows and Linux users are supported.
Include sample command-line snippets for both PowerShell and Bash (Azure CLI) to demonstrate configuration steps.
Mention automation options (e.g., ARM templates, Terraform) that are platform-agnostic.
Ensure that references to the Azure portal are complemented by equivalent CLI or scripting instructions, and clarify that the portal is accessible from any OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing the Azure portal and .NET SDK examples, which are more commonly associated with Windows environments. There are no Linux-specific instructions, command-line examples, or cross-platform SDK references (such as Python, Java, or CLI usage). No mention is made of Linux tools or workflows, and all example links and references are oriented toward Windows-centric development.

Recommendations:

Include examples and references for cross-platform SDKs, such as Python, Java, or Node.js, in addition to .NET.
Provide instructions for configuring Event Hubs using the Azure CLI or Azure PowerShell, and clarify which commands work on Linux, macOS, and Windows.
Add explicit guidance for Linux users, such as how to use the Azure portal or CLI from Linux systems.
Balance references to .NET with equivalent links for other languages and platforms.
Mention any platform-specific considerations (such as client configuration or environment setup) for Linux and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to create, view, and delete lab plans using the Azure portal, which is a graphical interface most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), nor are there references to Linux tools or workflows. This may implicitly favor Windows users and workflows, and does not provide parity for Linux users who may prefer or require command-line instructions.

Recommendations:

Add equivalent instructions for managing lab plans using the Azure CLI, which is cross-platform and widely used on Linux.
Provide examples for common tasks (create, view, delete lab plans) using both Azure CLI and PowerShell, and present them in parallel.
Explicitly mention that the Azure portal can be accessed from any modern browser on Windows, Linux, or macOS to clarify platform neutrality.
Include screenshots or terminal output from Linux environments where relevant.
Consider adding a section on automating lab plan management using scripts, with examples in Bash and PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line instructions exclusively using Windows tools (nslookup from 'command prompt'), without mentioning or providing equivalent Linux/macOS commands or context. There are no PowerShell-specific commands, but the guidance assumes a Windows environment and omits Linux/Unix alternatives.

Recommendations:

For all command-line instructions (such as nslookup), explicitly mention that these commands are available on both Windows and Linux/macOS, or provide Linux/macOS shell equivalents (e.g., 'Run nslookup <namespace> from your terminal or command prompt').
Where 'command prompt' is mentioned, clarify that this could be Windows Command Prompt, PowerShell, or a Unix shell (bash/zsh), and that the command works cross-platform.
If there are any differences in output format or command usage between platforms, note them or provide example outputs for both Windows and Linux.
Consider including a table or note listing common tools (e.g., nslookup, dig) and their availability on different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently refers to Windows-specific drive letters (C: and D:) when describing OS and temporary disks, without mentioning Linux equivalents (such as / or /mnt). No Linux-specific examples or terminology are provided, and the documentation does not clarify how these instructions or disk mappings apply to Linux VMs. This may cause confusion for users working with Linux-based lab VMs.

Recommendations:

Include references to Linux disk conventions (e.g., root filesystem '/', '/mnt', or '/tmp') alongside Windows drive letters when discussing OS and temporary disks.
Explicitly state that the instructions apply to both Windows and Linux VMs, or provide separate notes/examples for each platform where behavior differs.
Add Linux command-line or tool references where PowerShell is mentioned, or clarify if PowerShell is required/supported on Linux VMs.
Review screenshots and UI text to ensure they are not Windows-centric, or provide Linux-relevant visuals if the experience differs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing 'Command Prompt' and showing a Windows-style command prompt path in example output, while not explicitly mentioning or illustrating Linux/macOS terminal usage. There are no Linux-specific instructions or screenshots, and the initial instruction to 'open a Command Prompt window' may confuse non-Windows users. However, the actual commands (npm, node) are cross-platform.

Recommendations:

Replace 'open a Command Prompt window' with 'open a terminal window' or mention both Command Prompt (Windows) and Terminal (Linux/macOS).
Provide example terminal commands and output for both Windows and Linux/macOS (e.g., show both C:\... and ~/... paths).
Include a note clarifying that all commands work on Windows, Linux, and macOS, and adjust screenshots or code blocks to reflect this parity.
When referencing editors or tools, mention cross-platform options (e.g., 'such as Visual Studio Code, which is available on Windows, Linux, and macOS').

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates bias by using Windows-style file paths (e.g., 'c:/certs/member0_cert.pem') in CLI examples without providing equivalent Linux-style paths. While it mentions that OpenSSL is required on Windows or Linux, all concrete examples use Windows conventions, and there are no Linux-specific instructions or examples.

Recommendations:

Provide parallel CLI examples using Linux-style file paths (e.g., '/home/user/certs/member0_cert.pem') alongside Windows examples.
Explicitly mention that file paths should be adapted to the user's operating system.
Where relevant, include notes or callouts for Linux users regarding file system differences or command syntax.
Ensure that any referenced scripts or commands are cross-platform or provide alternatives for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page primarily describes configuration using the Azure portal, which is platform-agnostic, but it specifically mentions Azure PowerShell as the only CLI tool in the prerequisites, with no mention of Azure CLI or Bash alternatives. This suggests a Windows-first and PowerShell-heavy bias, as Linux users are more likely to use Azure CLI or Bash scripting. No Linux-specific tools or instructions are provided.

Recommendations:

In the 'Before you begin' section, mention both Azure PowerShell and Azure CLI as supported tools for local scripting, and provide installation links for both.
Wherever PowerShell is referenced, add equivalent Azure CLI (az) commands or guidance, especially for users on Linux or macOS.
Explicitly state that all portal-based steps are cross-platform, but provide links to CLI-based documentation for both PowerShell and Azure CLI.
Consider adding a 'Command-line configuration' section with both PowerShell and Azure CLI examples for users who prefer scripting or automation.
Review all notes and prerequisites to ensure they do not assume a Windows environment or PowerShell as the default.

Create pull request

Bias Types:

⚠️ windows_reference

⚠️ windows_services_first

Summary:

The documentation is generally platform-neutral and focuses on network routing concepts, but there are minor instances of Windows bias. Specifically, there is a reference to Windows VM license activation in the context of default route advertisement, and the list of Microsoft 365 services highlights Windows-centric products (Exchange, SharePoint, Skype for Business, Teams) before mentioning others. There are no PowerShell-heavy sections, Windows-only tools, or missing Linux examples, but the only explicit OS reference is to Windows.

Recommendations:

When mentioning issues like VM license activation, clarify that similar issues may affect Linux VMs (e.g., Azure Linux VM activation or cloud-init scenarios) if applicable, or explicitly state if the issue is Windows-only.
If referencing troubleshooting or configuration for VM activation, provide links or notes for both Windows and Linux VM scenarios.
When listing Microsoft 365 services, consider a more neutral phrasing or include a broader range of services to avoid the appearance of Windows-first bias.
Continue to avoid OS-specific tooling (such as PowerShell or Windows command-line) unless parity examples for Linux (Bash, CLI) are also provided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.

Recommendations:

Include Linux and macOS equivalents when referencing file paths or system modifications (e.g., mention /etc/hosts for Linux/macOS alongside the Windows path).
Provide cross-platform instructions or clarify that the steps apply to all major operating systems.
When giving examples, either show both Windows and Linux/macOS commands or use neutral, platform-agnostic language where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references Windows Server 2019 virtual machines for testing the firewall and does not mention or provide examples for Linux-based virtual machines. There are no instructions or guidance for deploying or testing with Linux VMs, nor are Linux tools or patterns discussed.

Recommendations:

Include parallel instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
Describe how to test firewall rules from a Linux VM, including example commands (e.g., using curl or wget to access www.microsoft.com).
Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
Ensure that troubleshooting and cleanup steps are applicable to both Windows and Linux environments, or note any differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes password setting/resetting in a way that assumes Windows VMs as the default, with screenshots and UI text referencing Windows terminology. There is only a brief mention of Ubuntu, and no detailed Linux-specific instructions or examples are provided.

Recommendations:

Include explicit instructions and screenshots for setting and resetting passwords on Linux-based VMs (e.g., Ubuntu), highlighting any differences in workflow or UI.
Clarify any limitations or differences for Linux VMs (such as the inability to use the same password for all VMs) with more detail and guidance.
Ensure that terminology and screenshots are balanced between Windows and Linux, or provide parallel sections/examples for each platform.
Add troubleshooting tips or notes specific to Linux VM password management where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates subtle Windows bias by listing Azure PowerShell (a Windows-centric tool) before CLI in several places and referencing PowerShell explicitly as a supported deployment mechanism. There is no explicit Linux example or mention of Linux-specific tools, and the migration example only references the portal and Azure PowerShell, omitting CLI or Linux-native approaches.

Recommendations:

Ensure that Azure CLI is always mentioned alongside or before Azure PowerShell, as CLI is cross-platform and widely used on Linux.
When referencing deployment mechanisms, clarify that both Azure CLI and PowerShell are supported, and provide parity in examples and migration paths.
Add explicit examples or references for Linux users, such as using Azure CLI for policy creation, management, and migration.
Avoid listing Windows tools (like PowerShell) before cross-platform tools (like CLI) to prevent the perception of Windows-first bias.
Consider including a table or section that highlights tool parity and usage across different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell is presented immediately after CLI without clarification that PowerShell is primarily a Windows tool. There are no explicit Linux-specific instructions or mentions of Linux shell environments, and no guidance for users on macOS or Linux regarding PowerShell Core compatibility.

Recommendations:

Clarify that Azure CLI is cross-platform and works natively on Windows, Linux, and macOS, while PowerShell examples are for users who prefer or require PowerShell (and mention PowerShell Core for cross-platform use).
Consider presenting Azure CLI examples first, as it is the most universally applicable across platforms.
Add a note or section for Linux/macOS users, confirming that all CLI commands work in Bash and other Unix shells.
If PowerShell is included, specify that it is available cross-platform as PowerShell Core, and provide installation links or references for non-Windows users.
Explicitly state that no Windows-only tools or steps are required, and that the process is fully supported on Linux and macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not provide any OS-specific examples, but it references protocols and tools (such as RDP) that are strongly associated with Windows environments. There are no Linux-specific examples or tools mentioned, and the documentation does not demonstrate parity in terms of cross-platform usage or guidance.

Recommendations:

Include examples or references to Linux-relevant protocols and tools (e.g., SSH, SCP, SFTP) alongside or before Windows-centric ones like RDP.
Explicitly mention that FQDN filtering applies equally to Linux and Windows environments.
Provide example scenarios or command-line snippets for both Windows (PowerShell) and Linux (Bash/CLI) where relevant.
Balance protocol mentions so that Linux use cases are as visible as Windows ones.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively using the azurerm_windows_web_app resource for the App Service example, without mentioning or providing examples for Linux-based App Service resources. There are no explicit PowerShell or Windows command-line instructions, but the resource selection implicitly favors Windows environments. No Linux equivalents or guidance are offered.

Recommendations:

Include an example using azurerm_linux_web_app alongside azurerm_windows_web_app to provide parity for Linux users.
Add a note or section explaining how to adapt the Terraform configuration for Linux-based App Service deployments.
Ensure that any referenced sample code or GitHub repositories contain both Windows and Linux App Service examples.
Review the documentation for other implicit Windows-first patterns, such as screenshots or troubleshooting steps, and provide Linux alternatives where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine for the workload example and only describing remote desktop (RDP) access and Microsoft Edge browser for testing. There are no Linux VM deployment instructions, nor are there SSH or Linux-based testing steps. The documentation assumes a Windows environment for both deployment and validation, omitting Linux alternatives.

Recommendations:

Provide parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including sample configuration values.
Include steps for connecting to the Linux VM using SSH, and for testing outbound access using Linux command-line tools (e.g., curl or wget) instead of only Microsoft Edge.
Demonstrate how to configure DNS settings on a Linux VM (e.g., by editing /etc/resolv.conf or using netplan), not just via the Azure portal.
When describing firewall rules (such as DNAT), include examples for both RDP (Windows) and SSH (Linux) to show parity.
In the testing section, provide both Windows and Linux validation steps, ensuring users on either platform can follow along.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image in the creation steps and referencing Microsoft Edge for connectivity tests. There are no examples or instructions for deploying or testing with Linux-based virtual machines, nor are Linux tools or browsers mentioned. This may lead Linux users to feel unsupported or unsure if the process is applicable to their environments.

Recommendations:

Provide parallel instructions for creating a Linux-based VM (e.g., Ubuntu or CentOS) alongside the Windows example.
Include Linux-specific details for connecting to the VM (e.g., using SSH via Bastion, or using a Linux desktop environment and browser).
When testing outbound connectivity, mention using a browser available on Linux (e.g., Firefox) or using command-line tools like curl or wget to verify external IP.
Clarify that the process is OS-agnostic unless there are steps that are truly Windows-specific, and highlight any differences for Linux users.
Where possible, use neutral language and examples (e.g., 'open a web browser' instead of 'open Microsoft Edge').

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides three pivots: Portal, PowerShell, and CLI. The PowerShell section is detailed and appears before the CLI section, which may indicate a slight Windows-first and PowerShell-heavy bias. However, the CLI section is present and complete, supporting Linux and macOS users. There are no missing Linux examples, but the ordering and emphasis on PowerShell could be improved for parity.

Recommendations:

Consider listing the CLI pivot before the PowerShell pivot to give equal or greater prominence to cross-platform tooling.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Where possible, provide Bash script examples or notes for Linux users in the CLI section.
Ensure that all features and steps described in PowerShell are also available and equally detailed in the CLI section.
Add a short note in the prerequisites for each pivot clarifying the OS compatibility (e.g., 'Azure CLI runs on Windows, Linux, and macOS').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the workload VM, and by instructing users to connect via Remote Desktop and use Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned.

Recommendations:

Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) in the workload subnet, including example settings.
Include Linux-specific testing steps, such as connecting via SSH and using curl, wget, or a Linux browser to test outbound connectivity.
When describing remote access, mention both RDP (for Windows) and SSH (for Linux) as options, and show how to configure DNAT rules for SSH (port 22) as well as RDP (port 3389).
Avoid assuming the use of Internet Explorer or Windows-specific tools for testing; instead, offer cross-platform alternatives.
Explicitly state that the procedure applies to both Windows and Linux workloads, and provide example commands or screenshots for both where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Linux (Ubuntu/k3s) and Windows (AKS/PowerShell) examples for configuring kubectl access, but the Windows/PowerShell example is presented after the Linux example and is clearly labeled for AKS. The PowerShell example is more complex and uses Windows-specific scripting, which could be seen as a bias if Linux/Bash alternatives for AKS are not provided. However, the rest of the documentation uses cross-platform tools and Bash/console commands, with no exclusive reliance on Windows tools or patterns.

Recommendations:

For the AKS section, provide both PowerShell and Bash (or Azure Cloud Shell) command examples, as AKS can be managed from Linux/macOS as well as Windows.
Clearly indicate that both Linux and Windows clients can be used for AKS, and provide parity in scripting examples.
Where possible, use cross-platform commands first (e.g., Azure CLI, Bash), and include PowerShell as an alternative, not the default.
Review other sections for any implicit assumptions about the user's OS, and ensure that instructions are inclusive of both Linux and Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for all major workflows, but consistently presents Bash (Linux/macOS) instructions before PowerShell (Windows). There are no exclusive Windows tools or patterns, and no steps are missing for Linux users. However, the PowerShell examples are present throughout, which may be seen as a mild Windows bias, though not at the expense of Linux parity. No Windows-only tools or instructions are given, and Linux command-line tools (e.g., wget, base64, kubectl, az CLI) are used throughout.

Recommendations:

Maintain the current structure of providing both Bash and PowerShell examples for all workflows.
Consider clarifying in the introduction that both Linux/macOS and Windows are fully supported, and that users should select the tab that matches their environment.
Ensure that any troubleshooting or advanced scenarios also include both Bash and PowerShell examples, if applicable.
If possible, add explicit notes about cross-platform compatibility for tools like az CLI and kubectl, to reassure users on both platforms.
Continue to avoid Windows-only tools or patterns unless a Linux equivalent is also provided.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation presents both Azure PowerShell and Azure CLI examples, but the PowerShell section is listed first and is more detailed, with step-by-step explanations and variable usage. The CLI section is less detailed and lacks some of the explanatory context provided in the PowerShell section. There are no Linux-specific shell examples or explicit mention of Linux environments, and the documentation implicitly assumes familiarity with PowerShell, which is more common on Windows.

Recommendations:

Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
Ensure both PowerShell and CLI sections have equivalent detail and explanation, including variable usage and step-by-step breakdowns.
Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide bash/zsh syntax where appropriate.
Consider adding a short section or note for Linux users, clarifying that all CLI commands are cross-platform and providing any Linux-specific tips if relevant.
If possible, provide examples using Azure REST API or ARM templates, which are platform-agnostic, to further enhance cross-platform parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Windows Server as the example OS for the test virtual machine and only describes connecting via Remote Desktop (RDP) and using Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned. The only OS-specific instructions are for Windows, and these appear before any mention of alternatives (which are absent).

Recommendations:

Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the 'Create a virtual machine' section, including example settings and commands.
Include Linux-specific testing instructions, such as using SSH to connect to the VM and using curl, wget, or a browser like Firefox for testing outbound connectivity.
When describing DNS configuration, provide guidance for setting DNS servers on a Linux VM (e.g., editing /etc/resolv.conf or using netplan).
In the 'Test the firewall' section, include Linux-based examples for verifying connectivity and DNS resolution.
Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives to ensure cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally avoids platform-specific instructions, but there is evidence of subtle Windows bias. For example, the link for creating a dual stack application points specifically to a PowerShell-based guide (which is Windows-centric) and does not mention or link to Linux/CLI equivalents. No explicit Linux examples or parity are provided, and PowerShell is implicitly prioritized.

Recommendations:

Provide links to both PowerShell (Windows) and Azure CLI (cross-platform) or Bash (Linux) guides for all procedural documentation, especially for tasks like creating dual stack applications.
Wherever a PowerShell example or link is given, ensure an equivalent Azure CLI/Bash example or link is also present and given equal prominence.
Review all linked articles (e.g., 'virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md') to ensure Linux users are not excluded and update them to include Linux/CLI instructions if missing.
Explicitly mention that Azure CLI is available cross-platform and provide guidance for both Windows and Linux users in all relevant sections.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on Visual Studio Code as the export tool, but all instructions, screenshots, and workflow descriptions implicitly assume a Windows environment. There are no explicit Linux or macOS instructions, no mention of cross-platform differences, and no terminal/CLI alternatives. Keyboard shortcuts (Shift + Alt + A) and UI references are Windows-centric. There is no guidance for Linux users regarding possible differences in UI, file paths, or required dependencies.

Recommendations:

Explicitly state that Visual Studio Code and the Azure Logic Apps (Standard) extension are cross-platform and supported on Windows, Linux, and macOS.
Include Linux/macOS-specific instructions or notes where UI, keyboard shortcuts, or file paths may differ.
Provide at least one example or screenshot from a Linux (and/or macOS) environment to demonstrate parity.
Mention any required dependencies or troubleshooting steps that may be unique to Linux (e.g., installing .NET runtime, handling permissions).
If possible, offer CLI-based alternatives (e.g., using Azure CLI or PowerShell Core, which is cross-platform) for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation mentions prerequisites for both Windows and Linux, but does not provide any Linux-specific instructions or examples. The inclusion of a '[Mac instructions]' section without a corresponding Linux section, and the absence of explicit Linux command-line examples or guidance, suggests a bias towards non-Linux platforms. Additionally, Windows is listed before Linux in the prerequisites.

Recommendations:

Add a dedicated section or include instructions for Linux users, similar to the '[Mac instructions]' section.
Provide Linux-specific command-line examples where relevant.
Ensure that all steps and tooling references are explicitly cross-platform, or provide alternatives for Linux users.
List Linux before or alongside Windows in prerequisites to avoid 'windows_first' ordering bias.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ macos_first

Summary:

The documentation provides explicit instructions for macOS but does not include equivalent instructions for Linux or Windows. There is no evidence of Windows-specific bias (such as PowerShell commands or Windows tools), but Linux is notably absent, which may hinder Linux users.

Recommendations:

Add a dedicated section or include file with Linux-specific instructions for updating the application.
Ensure that all command-line examples are cross-platform or provide variants for macOS, Linux, and Windows.
Review included files (e.g., 'deploy-update-application.md') to confirm Linux parity and add Linux examples where missing.
Consider a platform-neutral approach where possible, or explicitly state when instructions are applicable to multiple platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Microsoft Rules Composer, a Windows-only GUI tool, and provides instructions specific to its interface. There are no examples or guidance for Linux users, command-line alternatives, or cross-platform workflows. No mention is made of using the Rules Engine or composing rules outside of the Windows environment.

Recommendations:

Provide information on whether the Microsoft Rules Composer is available or supported on Linux (e.g., via Wine, or if a cross-platform version exists).
If the Rules Composer is Windows-only, suggest alternative methods for Linux users, such as editing ruleset XML files directly with cross-platform editors.
Include command-line or API-based workflows for rule creation and editing that work on Linux.
Explicitly state platform limitations and offer guidance for Linux users to achieve parity in rule authoring and management.
Where possible, provide screenshots or step-by-step instructions for both Windows and Linux environments, or clarify when features are Windows-specific.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Microsoft Rules Composer, a GUI tool that is only available for Windows. There are no instructions, examples, or alternatives provided for Linux users, nor is there any mention of command-line or cross-platform approaches. All steps assume the use of a Windows environment and Windows-style UI interactions.

Recommendations:

Clearly state platform requirements and limitations at the beginning of the documentation, specifying that Microsoft Rules Composer is Windows-only.
If possible, provide or reference any available Linux-compatible tools or command-line alternatives for managing vocabularies and rulesets.
Include guidance for Linux users, such as using Azure Portal, REST APIs, or other cross-platform interfaces if available.
If no Linux alternatives exist, suggest workarounds (e.g., using a Windows VM or container) and encourage feedback to help prioritize cross-platform support.
Ensure future documentation includes parity in examples and tool references for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is largely cross-platform in intent, focusing on Azure CLI and Visual Studio Code, both of which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: (1) The documentation refers to 'command window' and 'terminal' interchangeably, but does not provide explicit Linux/macOS shell examples or mention Bash, Zsh, or other common Linux shells. (2) There are no explicit Linux/macOS-specific instructions, troubleshooting tips, or environment setup notes, and no screenshots or examples that show Linux terminals. (3) The installation instructions for Azure CLI are linked generically, but no Linux-specific package manager commands (e.g., apt, yum, brew) are shown. (4) The documentation does not mention or demonstrate using Linux-native tools or patterns (such as Bash scripting, environment variables, or file paths in Linux format), nor does it address potential differences in file permissions, case sensitivity, or CLI usage on Linux.

Recommendations:

Explicitly mention both Windows and Linux/macOS environments when referring to 'terminal' or 'command window', and provide examples for both (e.g., 'Open a terminal (Command Prompt on Windows, Terminal on Linux/macOS)').
Include Linux/macOS-specific installation commands for Azure CLI (e.g., apt-get, yum, brew) alongside the generic installation guide link.
Add example commands and screenshots from Linux/macOS terminals to demonstrate parity.
When referencing file paths, show both Windows (C:\path\to\file) and Linux (/home/user/path/to/file) formats where relevant.
Mention any known platform-specific issues, such as file permissions or case sensitivity, that may affect Linux users.
If scripting or automation is discussed, provide Bash script examples in addition to any PowerShell or batch examples.
Ensure that all tool references (such as Visual Studio Code) clarify that they are cross-platform and provide links or instructions for Linux/macOS installation if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a 'windows_first' bias by exclusively referencing Azure Portal and Azure CLI for role assignment, both of which are cross-platform but are often associated with Windows-centric workflows. There are no explicit PowerShell-only examples or Windows-specific tools, but there is also a lack of Linux/Unix-specific instructions or examples (e.g., Bash scripts, Linux command-line nuances, or references to Linux-native tools). The documentation does not mention or demonstrate how to manage permissions using Linux-native tools or workflows, nor does it clarify cross-platform compatibility for the CLI commands.

Recommendations:

Explicitly state that the Azure CLI commands work on Linux, macOS, and Windows, and provide installation or usage notes for Linux users.
Include example commands or screenshots from a Linux terminal (e.g., Bash shell) to demonstrate parity.
Mention any Linux-specific considerations, such as environment variable usage, file path differences, or shell quoting nuances.
If possible, provide alternative instructions or references for managing permissions using Linux-native tools or automation scripts.
Clarify that the Azure Portal is web-based and platform-agnostic, to avoid the impression of a Windows-only workflow.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward the Azure portal and Microsoft Entra (formerly Azure AD) ecosystem, which are primarily accessed via web UI or Microsoft-centric tools. There are no references to Linux command-line tools, CLI-based workflows, or cross-platform automation (e.g., Azure CLI, REST API, or Terraform). All examples and screenshots are from the Azure portal UI, with no mention of how to perform these tasks outside the Microsoft ecosystem or from Linux environments.

Recommendations:

Include Azure CLI and/or REST API examples for all major steps (e.g., assigning roles, creating teams, linking Entra groups), as these are cross-platform and usable from Linux, macOS, and Windows.
Mention and provide examples for managing Grafana Team Sync via Grafana's own API or configuration files, which are accessible from any OS.
Add a note clarifying that all portal-based steps can also be performed via CLI or API, and link to relevant documentation.
If possible, provide Terraform or other infrastructure-as-code examples for automating these tasks in a platform-agnostic way.
Explicitly state that the instructions are not limited to Windows and that Linux users can accomplish the same tasks using CLI or API tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-centric workloads and migration scenarios, such as ASP.NET web apps running on IIS and SQL Server, without mentioning or providing examples for Linux-based workloads or open-source databases/web servers. There are no Linux-specific migration scenarios, tools, or examples, and the only application migration scenario described is for IIS/ASP.NET, with no mention of Linux web servers (e.g., Apache, Nginx) or databases (e.g., MySQL, PostgreSQL).

Recommendations:

Include examples and guidance for migrating Linux-based workloads, such as web apps running on Apache or Nginx, and open-source databases like MySQL or PostgreSQL.
Add explicit mention of Linux server discovery, assessment, and migration processes, including any differences or considerations compared to Windows.
Provide parity in application migration scenarios by describing how to assess and migrate common Linux workloads to Azure (e.g., LAMP/LEMP stacks, Tomcat, Java apps).
Reference Linux-compatible migration tools and patterns where relevant, and clarify any limitations or special steps for Linux environments.
Ensure that all examples and best practices are inclusive of both Windows and Linux platforms, or clearly state if a feature is Windows-only.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide explicit examples or guidance for Linux environments or tools. It mentions discovery of SQL Server and ASP.NET (typically Windows workloads) before MySQL, and does not clarify Linux-specific discovery steps or considerations. No Linux command-line or tooling examples are provided, and the guidance for physical/public cloud servers is generic, lacking Linux context.

Recommendations:

Add explicit examples and guidance for discovering Linux workloads (e.g., Linux VMs, Apache, NGINX, PostgreSQL).
Include Linux-specific prerequisites or considerations for appliance deployment and import-based discovery.
Provide parity in workload examples, such as mentioning Linux web servers and databases alongside Windows ones.
If command-line or scripting is referenced, include Bash/Linux shell examples in addition to any PowerShell or Windows examples.
Clarify support for Linux operating systems in each discovery method section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on C# examples and references Windows-centric tutorials (WNS, Windows Store, ASP.NET backend), with no mention of Linux, cross-platform, or non-Windows development environments. There are no examples or guidance for Linux users or alternative SDKs/languages.

Recommendations:

Provide equivalent examples using cross-platform SDKs (e.g., Node.js, Python) that run natively on Linux.
Include instructions or notes for scheduling notifications from Linux environments, such as using REST APIs or CLI tools.
Add links to tutorials or documentation that cover non-Windows platforms and mobile backends.
Balance the 'Next steps' section with guides for Android, iOS, or generic cross-platform scenarios, not just Windows/ASP.NET.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses on Azure Migrate support for VMware and Hyper-V VMs, which are predominantly associated with Windows environments. There is no mention of Linux-specific migration scenarios, tools, or examples, nor are Linux-native patterns or permissions discussed. The content implicitly assumes a Windows-centric infrastructure by prioritizing VMware and Hyper-V, with no parity for Linux-based or open-source virtualization platforms (e.g., KVM, Xen).

Recommendations:

Include explicit references to Linux-based workloads and migration scenarios, such as support for KVM, Xen, or other open-source hypervisors.
Provide examples or documentation links for migrating Linux servers (both physical and virtual) to Azure, including any Linux-specific considerations or limitations.
Mention Linux-native tools or command-line patterns where relevant, and ensure that instructions are not solely tailored to Windows administrators.
Clarify support for Linux guest operating systems in the assessment and migration process, including any differences in agent installation or data collection.
Balance the order of presentation so that Linux and Windows scenarios are given equal prominence, or at least mention Linux scenarios alongside Windows/VMware/Hyper-V.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page describes the process of migrating servers to Azure using Private Link with agent-based replication. While it mentions migrating various types of servers (including VMware, Hyper-V, physical, AWS, and GCP VMs), it does not provide any explicit examples, commands, or instructions specific to Linux systems. The only OS-specific reference is to the Azure Hybrid Benefit, which is only applicable to Windows Server. There are no Linux-specific migration considerations, commands, or troubleshooting steps, and no mention of Linux authentication, service installation, or OS nuances. The documentation implicitly assumes a Windows-centric environment.

Recommendations:

Include explicit Linux migration examples, such as how to install and configure the Mobility Service on Linux servers.
Provide Linux-specific troubleshooting steps (e.g., DNS resolution using dig/nslookup, editing /etc/hosts, systemd service management for the Mobility Service).
Clarify any differences in agent installation, permissions, or prerequisites between Windows and Linux servers.
Mention Linux-specific Azure Hybrid Benefit or licensing considerations, if any, or clarify that it is Windows-only.
Add sample commands or scripts for both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) environments where relevant.
Ensure that references to OS-specific features (such as Windows Server licensing) are clearly marked as such, and provide equivalent Linux guidance where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any OS-specific examples or commands, but it references Windows Server and Azure Hybrid Benefit for Windows Server specifically, without mentioning Linux equivalents or considerations. There are no explicit Linux or cross-platform instructions, nor are there examples for Linux-based replication appliances or agent installation. The only OS-specific benefit (Azure Hybrid Benefit) is described for Windows Server, and no mention is made of Linux licensing or migration nuances. The documentation implicitly assumes a Windows-centric environment.

Recommendations:

Add explicit instructions or notes for Linux-based replication appliances, including any differences in setup or agent installation.
Include examples or references for migrating Linux servers, such as handling Linux-specific OS disk selection, agent installation, or post-migration steps.
Mention Azure Hybrid Benefit alternatives or considerations for Linux (e.g., bring-your-own-subscription, support for RHEL/SUSE, or other licensing models).
Ensure that any OS-specific features or benefits are described for both Windows and Linux, or clarify when a feature is Windows-only.
Provide links to Linux migration documentation or best practices alongside Windows references.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for reviewing deployed resources, but PowerShell is presented first and is used exclusively in the 'Clean up resources' section. There is no explicit Linux shell (bash) example for resource cleanup, and PowerShell is implicitly prioritized, which may be less familiar or accessible to Linux users.

Recommendations:

Provide Azure CLI (bash) examples alongside or before PowerShell examples, especially in the 'Clean up resources' section.
Alternate the order of PowerShell and CLI tabs to avoid always presenting Windows-centric tools first.
Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux) and are often preferred for Linux users.
Consider including bash scripting examples for resource cleanup to improve accessibility for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides comprehensive examples for Azure Portal, Azure PowerShell, Azure CLI, and Bicep. However, there is a notable emphasis on Azure PowerShell, which is most commonly used on Windows, and PowerShell examples are often presented before Azure CLI. The PowerShell sections are more verbose and detailed, and prerequisites for PowerShell include specific instructions for Windows environments. While Azure CLI is cross-platform and suitable for Linux, it is consistently listed after PowerShell, and there are no explicit Linux shell (bash) or scripting examples. There is no mention of Linux-specific tools, nor is there guidance for Linux users beyond Azure CLI.

Recommendations:

Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell environments (e.g., bash) where appropriate.
Add a short section or note for Linux users, clarifying that Azure CLI is the recommended tool for Linux and macOS, and that PowerShell is optional.
Where PowerShell is referenced, clarify that it is available cross-platform, but that Azure CLI may be more familiar to Linux users.
Consider including bash script snippets or references to Linux shell usage, especially in the prerequisites and setup sections.
Ensure parity in detail and explanation between PowerShell and CLI sections, so Linux users are not disadvantaged.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation subtly prioritizes Windows and macOS users by mentioning them explicitly in the note about running Azure CLI in Docker, while Linux users are not directly addressed. There are no Linux-specific instructions or examples, and the guidance assumes familiarity with Windows/macOS environments. No Linux command-line or package manager examples are provided for installing tools like Docker or Helm.

Recommendations:

Explicitly mention Linux as a supported platform alongside Windows and macOS in all relevant sections.
Provide Linux-specific installation instructions or command examples for Docker and Helm (e.g., using apt, yum, or snap).
Include a note or section on running Azure CLI in Docker on Linux, not just for Windows/macOS.
Ensure parity in troubleshooting tips or environment setup for Linux users.
Add example commands for common Linux distributions where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward the Azure Portal GUI and does not provide any command-line examples for provisioning Exadata infrastructure. While it does not explicitly reference Windows tools or PowerShell, it implicitly assumes use of the Azure Portal, which is most commonly accessed from Windows environments. There are no CLI (az), Bash, or Linux-specific instructions or examples, nor are there references to automation or scripting approaches that would be common in Linux-centric workflows.

Recommendations:

Add equivalent instructions for provisioning Exadata infrastructure using the Azure CLI (az), including full command-line examples.
Include Bash shell scripting examples for automating the provisioning process.
Explicitly mention that the Azure Portal can be accessed from any OS, and provide parity in documentation for Linux and macOS users.
Reference automation options such as ARM templates, Bicep, or Terraform, with examples for Linux environments.
Ensure troubleshooting and prerequisites sections include notes relevant to Linux users (e.g., required tools, environment setup).

Create pull request

Bias Types:

⚠️ windows_note

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform, using Azure CLI commands and referencing Docker and Helm, which are available on both Windows and Linux. However, there is a Windows-specific note stating that Docker Desktop must be running during the publish step if you are using Windows, but there is no equivalent note or guidance for Linux users (e.g., Docker daemon requirements or troubleshooting). No explicit Linux or macOS examples, troubleshooting, or environment-specific notes are provided, which could leave Linux users uncertain about platform-specific requirements.

Recommendations:

Add a note for Linux users clarifying any requirements for Docker (e.g., Docker daemon must be running, or how to check Docker status).
Include troubleshooting tips or common issues for both Windows and Linux environments.
Explicitly state that all commands are cross-platform and provide any necessary platform-specific instructions (such as file path conventions or Docker setup differences).
If mentioning Docker Desktop for Windows, mention the equivalent (e.g., Docker Engine) for Linux.
Consider adding a short section or callout confirming that the workflow has been tested on both Windows and Linux, and highlight any differences if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any platform-specific examples or instructions, but it implicitly assumes use of the Azure portal and Azure tools without mentioning or providing parity for Linux command-line workflows or tools. There are no explicit Windows-only tools mentioned, but the lack of Linux-specific guidance or examples (such as CLI commands or shell scripts) may disadvantage Linux users. The documentation also references the Azure portal and Azure APIs/SDKs generically, which may be more familiar to Windows users.

Recommendations:

Add explicit examples for Linux users, such as using Azure CLI or Terraform from a Linux shell.
Include sample command-line workflows for provisioning and managing Oracle Database@Azure from Linux environments.
Clarify that all Azure APIs, SDKs, and Terraform tools are cross-platform, and provide links or examples for Linux installation and usage.
If mentioning the Azure portal, also mention that it is web-based and platform-agnostic to reassure Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows/Azure bias by exclusively referencing Microsoft Azure VMs and networking concepts, without mentioning or providing examples for Linux-based environments or tools. All examples and scenarios are framed in terms of Microsoft Azure constructs (such as VNets, NSGs, and Azure VMs), with no mention of Linux-specific troubleshooting steps, tools, or cross-platform considerations.

Recommendations:

Include troubleshooting steps and examples that are relevant to Linux-based VMs or environments, such as using Linux command-line tools (e.g., ip, ifconfig, netstat, dig) for network diagnostics.
Provide parity in examples by referencing both Windows and Linux VMs when discussing connectivity, configuration, or troubleshooting.
Mention Linux-native tools or scripts for managing network rules and DNS settings, alongside Azure/Windows-centric instructions.
Clarify whether the procedures apply equally to both Windows and Linux VMs, or note any differences.
Add a section or callout for Linux administrators, highlighting any unique considerations or steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence to the CLI example, and both are presented as primary options. There is no explicit Linux shell (bash) example, and the CLI example uses generic 'console' syntax, which may not be fully Linux-specific. The documentation does not mention or show Linux-specific tools or patterns, and PowerShell (a Windows-centric tool) is given a dedicated section.

Recommendations:

Explicitly provide Linux shell (bash) examples for all command-line steps, especially for verification and resource management.
Clearly indicate which commands are cross-platform and which are Windows-specific.
If PowerShell is included, ensure that bash/Linux shell examples are given equal or greater prominence, ideally listed first.
Mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary notes for Linux users (e.g., differences in environment variable syntax).
Consider adding a 'Linux/macOS' tab or section for verification steps, demonstrating the same workflow in a Linux-native environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents the PowerShell example before the Azure CLI example, which may suggest a Windows-first approach. The PowerShell section is more detailed, and there is no explicit mention of Linux or Bash environments, even though Azure CLI is cross-platform. There are no Linux-specific instructions or clarifications.

Recommendations:

Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
Add Bash-specific context or examples if there are any differences or prerequisites for Linux users.
Balance the level of detail between PowerShell and CLI sections to avoid favoring Windows users.
Consider including a short note or section for Linux users, especially if there are environment-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation shows a mild Windows bias by referencing Windows resources first and linking only to Windows-specific VM creation guides. While both PowerShell and Azure CLI examples are provided (ensuring cross-platform command-line parity), the prerequisite section and example ordering prioritize Windows tools and patterns.

Recommendations:

In the prerequisites, provide links to both Windows and Linux VM creation guides, not just Windows.
When referencing PowerShell and Azure CLI, clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
Consider alternating the order of PowerShell and CLI examples or explicitly noting that both are supported on all platforms.
Add a note or section for Linux administrators, highlighting that all features and steps are equally applicable to Linux-based NVAs and VMs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page exhibits a mild Windows bias. In the section describing how to create a private endpoint using an alias, the PowerShell cmdlet (New-AzPrivateEndpoint) is mentioned before the Azure CLI equivalent (az network private-endpoint create). No Linux-specific tools or examples are provided, and the documentation does not mention or link to Bash or Linux shell scripting. However, the overall content is mostly platform-neutral, with the only notable bias being the order of tool references and the use of PowerShell cmdlets.

Recommendations:

When referencing command-line tools, list Azure CLI (az) examples before or alongside PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux.
Include explicit Linux/Bash shell examples where relevant, especially in sections that mention command-line operations.
Where possible, clarify that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide links to platform-specific installation guides.
Review other related articles (such as quickstarts and tutorials) to ensure Linux parity in examples and screenshots.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses .NET Core CLI commands (dotnet build/run), which are cross-platform, but the code blocks are tagged as 'dos', implying a Windows command prompt context. There are no explicit Linux or macOS shell examples, nor is there mention of running the sample on non-Windows platforms. The instructions for editing configuration files reference 'Web.config' (a Windows/IIS convention) in one section, which may confuse Linux users. There is no mention of Linux-specific considerations or parity.

Recommendations:

Use neutral code block tags (e.g., 'bash', 'shell', or no tag) for dotnet CLI commands to indicate cross-platform compatibility.
Explicitly mention that the sample and commands work on Windows, Linux, and macOS.
Provide Linux/macOS shell command examples where appropriate, or clarify that the commands are the same across platforms.
Avoid references to 'Web.config' unless specifically targeting ASP.NET on Windows; use 'appsettings.json' or other cross-platform configuration files.
Add a note or section on any platform-specific steps or troubleshooting for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently refers to 'command prompt' and uses Windows-centric terminology and command examples (e.g., 'cmd' code blocks, references to 'command prompt'), without providing equivalent instructions or terminal commands for Linux or macOS users. There are no bash/zsh shell examples, and no mention of Linux-specific considerations, despite .NET Core and Visual Studio Code being cross-platform.

Recommendations:

Include Linux/macOS terminal instructions alongside Windows examples, using 'bash' code blocks where appropriate.
Refer to the terminal generically (e.g., 'open a terminal or command prompt') rather than only 'command prompt'.
Show both Windows and Linux/macOS commands for common tasks (e.g., directory creation, running dotnet commands, opening VS Code).
Explicitly state that the instructions apply to all supported platforms, and highlight any OS-specific differences if they exist.
Consider adding a platform selector or tabs for Windows, Linux, and macOS instructions where commands or steps differ.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation only describes how to delete a resource group using the Azure portal (a web UI), with no mention of command-line alternatives. There are no examples for deleting resource groups using CLI tools such as Azure CLI or PowerShell. While the portal is cross-platform, the lack of CLI examples may disadvantage Linux users, who often prefer or require command-line instructions. Historically, Azure documentation sometimes defaults to PowerShell or Windows-centric tools, and the omission of Azure CLI (which is cross-platform and popular on Linux) is a subtle form of Windows-first bias.

Recommendations:

Add instructions and examples for deleting a resource group using the Azure CLI (az group delete ...), which works on all platforms.
If PowerShell examples are included, ensure Azure CLI examples are presented first or equally, to avoid Windows-first ordering.
Explicitly mention that the Azure portal is accessible from any OS, but provide parity with command-line instructions for Linux users.
Consider including Bash script examples for automation scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions and command-line examples that are platform-neutral in wording, but the use of 'command window' and the 'dos' code block hints at a Windows-first approach. There are no explicit Linux/macOS terminal instructions or screenshots, and no mention of platform-specific differences, which may leave Linux users without clear guidance.

Recommendations:

Explicitly mention that the .NET CLI commands (dotnet build, dotnet run) work on Windows, Linux, and macOS.
Replace 'command window' with 'terminal' or 'command prompt or terminal' to be inclusive of all platforms.
Use the 'bash' code block for CLI commands, or provide both 'dos' and 'bash' code blocks where appropriate.
Add a note or section for Linux/macOS users, including any OS-specific steps (such as installing .NET SDK or running the app).
Include screenshots or terminal output examples from Linux/macOS environments, or clarify that the instructions are cross-platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation only provides instructions for cleaning up resources via the Azure Portal (web UI), with no mention of command-line alternatives. There are no examples for using CLI tools such as Azure CLI or PowerShell. While this avoids explicit Windows-only tools, the lack of CLI examples implicitly favors Windows users, as Linux users often expect or prefer CLI instructions.

Recommendations:

Add Azure CLI examples for deleting resource groups, as the Azure CLI is cross-platform and widely used on Linux.
If mentioning PowerShell, ensure Azure CLI instructions are presented first or alongside, to avoid Windows-first bias.
Explicitly state that the Azure Portal method works on all platforms, but provide CLI alternatives for users who prefer command-line operations.
Include sample commands for both Azure CLI and, optionally, PowerShell, to ensure parity for Linux and Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the 'Page Faults/Sec' performance counter, which is a Windows-specific monitoring metric, without mentioning equivalent Linux tools or metrics. There are no Linux-specific examples or guidance for monitoring memory pressure or other client-side issues.

Recommendations:

Include Linux equivalents for monitoring memory pressure, such as using 'vmstat', 'top', 'free', or checking '/proc/meminfo'.
Mention Linux-specific metrics or commands (e.g., 'vmstat -s', 'sar -B', or 'ps') alongside Windows performance counters.
Provide example commands or scripts for both Windows (Performance Monitor, PowerShell) and Linux (shell commands) to ensure parity.
Use platform-neutral language where possible, or explicitly address both Windows and Linux environments in troubleshooting steps.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references Windows as the supported operating system and requires the .NET Framework, which is primarily a Windows technology. There is no mention of Linux or macOS support, nor are there any instructions or examples for non-Windows platforms. This indicates a strong Windows bias and a lack of cross-platform consideration.

Recommendations:

Clearly state platform support, and if Linux/macOS are not supported, provide a roadmap or alternatives for those users.
If possible, provide instructions for running the tool on Linux (e.g., via Wine or .NET Core/Mono, if feasible).
Include information about any cross-platform plans or open-source alternatives for non-Windows users.
Ensure future documentation includes parity in examples and instructions for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. In several sections, PowerShell (a Windows-centric tool) is listed before Azure CLI (which is cross-platform and often preferred by Linux users). For example, in the prerequisites for checking VM SKU availability, PowerShell is mentioned before Azure CLI. Similarly, in migration instructions, PowerShell is listed after CLI, but both are present. There are no sections where only Windows or PowerShell examples are given, and Linux-specific guidance is present where appropriate. However, the ordering and occasional emphasis on PowerShell can be perceived as a mild Windows-first bias.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
Where both PowerShell and Azure CLI are mentioned, clarify that both are fully supported and provide equal prominence.
Ensure that all command-line examples are provided for both Windows (PowerShell) and Linux (Azure CLI/Bash) where applicable.
Consider adding explicit Linux/Bash examples in addition to Azure CLI, especially for tasks commonly performed on Linux.
Review linked pages to ensure Linux parity is maintained in referenced documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The only potential evidence of Windows bias in this documentation is in the introductory paragraph, where the PowerShell cmdlet (Get-AzProviderOperation) is mentioned before the Azure CLI equivalent (az provider operation list). No other examples, tools, or patterns specific to Windows or PowerShell are present in the rest of the page, which is otherwise a neutral, tabular listing of Azure resource providers and their permissions. There are no command-line examples, screenshots, or tool references that are Windows-specific elsewhere in the document.

Recommendations:

When listing ways to retrieve permissions, mention Azure CLI (az provider operation list) before or alongside PowerShell (Get-AzProviderOperation), or present them in parallel to avoid implying a preference.
If possible, provide REST API or ARM template options as well, for full cross-platform parity.
Continue to avoid Windows- or PowerShell-specific examples elsewhere in the documentation, maintaining the current neutral approach.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Windows-centric monitoring tools (Microsoft Monitoring Agent and System Center Operations Manager) as examples of 'active monitoring tools' without mentioning Linux-native or cross-platform alternatives. There are no Linux-specific examples or equivalent tools provided, which may suggest a Windows bias.

Recommendations:

Include Linux-native or cross-platform monitoring tools (e.g., collectd, Nagios, Zabbix, or Azure Monitor Agent, which supports Linux) alongside Windows tools.
Provide examples or references for configuring monitoring and vulnerability scanning on Linux-based systems.
Explicitly state that Azure supports both Windows and Linux environments, and link to relevant Linux documentation where appropriate.
Balance tool mentions by listing Linux and Windows options together, or by focusing on cross-platform Azure-native solutions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by providing a detailed Azure PowerShell example before mentioning Azure CLI or REST API alternatives. The PowerShell example is presented first and in more detail, which may implicitly prioritize Windows tooling. There are no explicit Linux or cross-platform command-line examples, and the PowerShell example may not be as accessible to Linux users.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Clearly indicate which examples are platform-specific and which are cross-platform.
Balance the order of examples so that cross-platform tools like Azure CLI are not always presented after Windows-centric tools.
Include explicit Linux/macOS usage notes or examples where relevant, especially for command-line operations.
Consider adding a table or section summarizing equivalent commands in PowerShell, Azure CLI, and REST API for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a Windows-centric example for downloading and extracting SAP HANA installation packages, specifically stating that the jump box is a Windows VM and showing screenshots of Windows file extraction. There are no equivalent instructions or examples for Linux-based jump boxes, despite the overall context being SAP HANA on Linux. This may confuse or disadvantage users who are using a Linux jump box, which is common in SAP HANA environments.

Recommendations:

Provide parallel Linux-based instructions and examples for downloading and extracting SAP HANA installation packages on a Linux jump box.
Include Linux command-line examples (e.g., using wget/curl for download, tar for extraction) alongside or before Windows examples.
Clarify that both Windows and Linux jump boxes are supported, and structure the documentation to address both use cases equally.
Add screenshots or terminal output for Linux-based extraction and file management steps.
Review the prerequisites and initial setup sections to ensure they do not implicitly assume a Windows environment.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references the Microsoft Threat Modeling Tool, which is a Windows-only application, without mentioning Linux support or alternatives. There are no Linux installation instructions, examples, or references to cross-platform usage. The focus is entirely on Windows tooling, implicitly excluding Linux users.

Recommendations:

Explicitly state the platform support (e.g., Windows-only) early in the documentation.
If possible, provide information about running the tool on Linux (e.g., via Wine or virtualization) or mention any available cross-platform alternatives.
Include a section addressing Linux and macOS users, suggesting workarounds or equivalent open-source tools for threat modeling.
Ensure that future documentation includes parity in examples, installation instructions, and tool recommendations for non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references the Azure portal and provides a quickstart link for both the Azure portal and PowerShell, but does not mention or provide any Linux/CLI (such as Azure CLI or Bash) examples. There is a subtle Windows-first bias by listing PowerShell as the only command-line alternative, with no equivalent Linux-native tooling or instructions. No Linux-specific tools, commands, or patterns are mentioned, and there are no examples for Linux users.

Recommendations:

Add instructions and examples for creating the IBM Db2 provider using the Azure CLI, which is cross-platform and commonly used on Linux.
Where PowerShell is referenced, also provide Bash or shell script equivalents for Linux users.
Ensure that all quickstart links and command-line instructions have both Windows (PowerShell) and Linux (Bash/Azure CLI) options, presented with equal prominence.
Explicitly mention that the steps are applicable to both Windows and Linux environments, or clarify any OS-specific requirements.
If any scripts or tools are required, provide platform-agnostic or dual-platform guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Azure Kubernetes Service (AKS) and Azure ARC, both of which are cross-platform but are presented from a Microsoft/Azure-centric perspective. There are no explicit Windows-only tools or PowerShell examples, but there is a lack of Linux-specific guidance, examples, or parity in tooling references. The documentation assumes the use of Azure-managed services and does not mention or provide examples for deploying on non-Azure Kubernetes distributions or using Linux-native tools, which may be relevant for SAP Edge Integration Cell deployments in hybrid or on-premises Linux environments.

Recommendations:

Include explicit Linux-native deployment examples or references, such as using kubectl on Linux, or integrating with Linux-based Kubernetes distributions outside Azure.
Provide parity in tooling instructions, e.g., mention both Azure CLI (which is cross-platform) and Linux shell commands where appropriate.
Add a section or note on considerations for Linux administrators, such as SELinux/AppArmor, systemd integration, or Linux networking specifics.
Reference or link to SAP Edge Integration Cell documentation for Linux environments, if available.
Clarify that AKS and Azure ARC can be managed from both Windows and Linux environments, and provide examples for both.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Microsoft cloud services and tools (Dataverse, Power Platform, Dynamics 365, Microsoft Entra, SharePoint, Office 365, Microsoft Defender, Microsoft Teams, Outlook, etc.), with all examples and playbooks referencing only Microsoft-centric and Windows ecosystem technologies. There are no mentions of Linux tools, cross-platform command-line examples, or integration with non-Microsoft environments. The documentation assumes the use of Microsoft Sentinel and related services, which are primarily managed via web portals or PowerShell, but does not provide any Linux-specific guidance or parity.

Recommendations:

Add examples or guidance for integrating Microsoft Sentinel with Linux-based log sources, such as syslog, auditd, or Linux agents.
Include sample queries or playbooks that demonstrate detection or response for Linux endpoints (e.g., Linux file access, process creation, SSH logins).
Document how to automate responses or notifications using cross-platform tools (such as Python scripts, curl, or Linux mail utilities) in addition to Microsoft Teams and Outlook.
Clarify whether the solution supports Linux-based environments and, if so, provide explicit instructions or references for Linux users.
If PowerShell or Windows-specific tools are required, note this explicitly and suggest alternatives or workarounds for Linux-only environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation uses AzureCliCredential from the azure.identity Python library, which relies on the Azure CLI for authentication. While Azure CLI is cross-platform, the documentation does not mention this, nor does it provide any guidance for Linux or macOS users. There are no explicit Windows-only commands, but the lack of platform-specific notes or alternative authentication methods (such as environment variables or managed identity) may implicitly favor users familiar with Windows or the Azure CLI, which is more commonly pre-installed or documented for Windows environments.

Recommendations:

Explicitly state that Azure CLI is cross-platform and provide installation instructions or a link for Linux/macOS users.
Mention alternative authentication methods (e.g., DefaultAzureCredential, environment variables, managed identity) that work across platforms.
Add a note clarifying that the Python code works on Windows, Linux, and macOS as long as the Azure CLI is installed and authenticated.
Include troubleshooting tips for common Linux/macOS issues with Azure CLI authentication.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page shows a moderate Windows bias by referencing Azure PowerShell (AzPowershell) for authentication in the GitHub Actions workflow, without mentioning or providing alternatives for Linux-native tools (such as Azure CLI). The only authentication example uses PowerShell, which is more commonly associated with Windows environments, even though the runner is set to 'ubuntu-latest'. No explicit Linux shell or cross-platform authentication alternatives are shown.

Recommendations:

Provide an example using Azure CLI (az login) for authentication, which is cross-platform and commonly used in Linux environments.
Mention that both AzPowershell and Azure CLI can be used, and link to documentation for both.
If showing a PowerShell-based example, also show a Bash/shell-based equivalent for parity.
Clarify that the authentication method is not limited to Windows or PowerShell, and recommend the most cross-platform approach by default.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes authentication and configuration steps using the Azure portal and Logic Apps designer, both of which are web-based or GUI tools commonly accessed via Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell) for Linux users, nor are there references to Linux-native tools or workflows. All instructions assume use of the Azure portal UI, which may be more familiar or accessible to Windows users.

Recommendations:

Add equivalent command-line instructions using Azure CLI (az) for all authentication and role assignment steps, which can be run on Linux, macOS, or Windows.
Include examples of how to perform authentication and role assignments using Bash scripts or via REST API calls.
Explicitly mention that all steps can be performed from any OS using the Azure portal, and provide parity in CLI examples.
Where screenshots are provided, consider including CLI output or terminal screenshots to illustrate cross-platform usage.
Clarify that Logic Apps and Microsoft Sentinel are cloud-based and accessible from any OS, but provide Linux-friendly automation examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing Windows VM creation before Linux, and by providing a direct link to Windows agent installation instructions while only offering a troubleshooting link for Linux. There are no explicit Linux onboarding or installation steps, nor are Linux-specific examples or guidance provided for the extension installation process.

Recommendations:

Provide parallel Linux onboarding instructions, including a direct link to the Linux agent installation documentation (not just troubleshooting).
Ensure that both Windows and Linux VM creation links are presented together or in a neutral order.
Include Linux-specific notes or screenshots where relevant, especially if the extension installation process differs.
Add a section or callout for Linux users explaining any unique steps or considerations.
Review all references to ensure Linux and Windows are treated with equal prominence and detail.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on Microsoft Sentinel and Microsoft security solutions, with all examples and instructions centered around the Azure portal UI and Microsoft-specific tools. There are no references to Linux tools, command-line interfaces, or cross-platform automation methods. The documentation implicitly assumes a Windows-centric environment by only mentioning Microsoft products and workflows, without addressing how users on Linux or other platforms might interact with Sentinel or automate incident creation.

Recommendations:

Include examples of how to interact with Microsoft Sentinel using cross-platform tools such as the Azure CLI or REST API, which are available on Linux, macOS, and Windows.
Provide sample scripts for automating incident creation using Bash or Python, in addition to (or instead of) PowerShell.
Explicitly mention that the UI and automation options are accessible from any OS with a web browser, and clarify any platform-specific limitations.
Reference relevant documentation for Linux users, such as installing and using the Azure CLI on Linux, or integrating Sentinel with non-Microsoft security solutions.
If automation is discussed, show both PowerShell and Bash (or Python) equivalents for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation refers to opening a 'command prompt' without specifying platform, which is a Windows-centric term. No explicit mention is made of Linux or macOS terminals, nor are there any platform-specific instructions or clarifications. All command-line examples use curl, which is cross-platform, but the language and context assume a Windows environment by default and do not address Linux users directly.

Recommendations:

Replace or supplement the phrase 'open a command prompt' with 'open a terminal or command prompt,' and clarify that the instructions apply to Windows, Linux, and macOS.
Add a note confirming that curl commands work on all major platforms, and provide installation guidance or references for curl on Windows, Linux, and macOS if necessary.
Where file paths are referenced (e.g., <enter_path_to_file>.json), provide examples for both Windows (C:\path\to\file.json) and Linux/macOS (/path/to/file.json) to avoid ambiguity.
Explicitly state that the instructions are platform-agnostic, or provide any necessary platform-specific caveats (such as quoting or escaping differences).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/Azure portal-centric bias by exclusively describing integration steps using the Azure portal GUI, with no mention of command-line alternatives (such as Azure CLI, PowerShell, or Bash scripts) that would be relevant for Linux users. There are no examples or instructions for performing these tasks from Linux environments, nor is there any reference to cross-platform tooling or automation approaches.

Recommendations:

Add equivalent instructions for configuring diagnostic settings and data connectors using Azure CLI, which is cross-platform and commonly used on Linux.
Provide sample scripts or commands for running Microsoft Purview scans and managing Sentinel analytics rules via CLI or REST API.
Explicitly mention that all portal-based steps can be performed from any OS with a web browser, but highlight automation options for Linux users.
Include references or links to documentation on using Azure CLI and REST APIs for relevant tasks.
Where screenshots are shown, clarify that the UI is accessible from any platform, and supplement with text-based alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a subtle Windows bias by referencing Windows-specific concepts and links before or instead of Linux equivalents. For example, the 'Availability set' link points to a Windows VM tutorial, and the instructions for connecting to failed-over VMs mention RDP (Windows) before SSH (Linux) without providing explicit Linux connection examples or links. There are no Linux-specific instructions or examples, despite mentioning Linux VMs in the context of failover times.

Recommendations:

Provide parallel Linux examples and links where Windows-specific instructions or links are given (e.g., link to both Windows and Linux VM availability set documentation).
When discussing connecting to failed-over VMs, include explicit SSH instructions and a link to the Azure Linux VM SSH connection documentation alongside the RDP/Windows link.
Where relevant, clarify any differences in failover or recovery steps for Linux VMs, especially since Linux VMs are mentioned as potentially having longer failover times.
Ensure that terminology and instructions are platform-neutral unless a step is truly Windows-specific, in which case, provide a Linux alternative or note.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation repeatedly references CSV formatting differences between files created in Microsoft Excel and those created in a 'text editor', but does not mention Linux-specific tools or editors (such as LibreOffice, nano, vim, or Linux command-line CSV creation). Microsoft Excel is mentioned by name, while the alternative is generically described, implicitly centering the Windows/Office experience. No Linux or cross-platform tools are named, and no Linux-specific examples are provided.

Recommendations:

Explicitly mention cross-platform and Linux-friendly tools for creating CSV files, such as LibreOffice Calc, Google Sheets, or command-line utilities (e.g., csvkit, awk, sed).
Provide examples of CSV formatting/output from Linux tools or editors (e.g., show how to create a compatible CSV using nano, vim, or command-line tools).
When describing CSV differences, avoid centering Microsoft Excel; instead, use neutral language or list multiple tools (e.g., 'for CSV files created in Microsoft Excel, LibreOffice Calc, or other spreadsheet editors...').
Consider adding a section or note on ensuring CSV compatibility across different operating systems and editors, including common pitfalls on Linux.
If relevant, provide sample commands for generating or validating CSVs on Linux (e.g., using cat, echo, or csvkit).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still most common on Windows). There are no Linux shell or Bash-specific examples, and the order of examples (CLI before PowerShell) is good, but the PowerShell section could be seen as Windows-focused. No explicit Windows-only tools or patterns are used, but the lack of Linux/Bash-specific guidance or troubleshooting tips may disadvantage Linux users.

Recommendations:

Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
Add Bash shell scripting examples or notes for Linux users, especially for automation scenarios.
Mention that PowerShell is available cross-platform, but note its prevalence on Windows.
Provide troubleshooting tips or common issues for both Windows and Linux environments.
Consider adding a table comparing CLI and PowerShell usage scenarios for different OSes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is focused exclusively on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. There are no examples or mentions of Linux or cross-platform usage, and all configuration and usage patterns assume a Windows/.NET environment. No Linux-specific instructions, tools, or parity considerations are provided.

Recommendations:

Add explicit notes about cross-platform support or limitations, clarifying whether the library can be used on Linux via Mono or .NET Core/5+.
Provide examples or guidance for using the newer Azure.Messaging.ServiceBus package in cross-platform (Linux, macOS) environments, especially since it is recommended for new development.
Include instructions or references for setting up the development environment and running .NET-based Service Bus clients on Linux.
Mention any differences or caveats when using the library on non-Windows platforms, if supported.
If the legacy library is Windows-only, state this clearly and direct Linux users to supported alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but lists PowerShell after Azure CLI. However, the PowerShell example is given equal prominence, and there are no explicit Linux-specific instructions or examples. The use of PowerShell (a Windows-centric tool, though now cross-platform) may still be seen as Windows-biased, especially since no Bash or Linux-native scripting examples are provided. There are no references to Windows-only tools, but the absence of explicit Linux/Bash examples or notes on cross-platform compatibility could be improved.

Recommendations:

Add explicit Bash/Linux shell examples for all command-line instructions, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
Mention that PowerShell Core is cross-platform, or provide Bash equivalents for PowerShell examples.
Where possible, avoid presenting PowerShell as the only scripting alternative to Azure CLI; consider including Python or REST API examples for broader platform parity.
Add a note clarifying the cross-platform compatibility of the Azure CLI and PowerShell modules.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias by referencing Windows-centric connection methods (RDP) before Linux (SSH), and by linking only to Windows VM connection instructions. There are no explicit Linux-specific examples or guidance, and troubleshooting or validation steps do not mention Linux VMs or tools. The only mention of Linux is in the context of longer failover times, not in usage instructions.

Recommendations:

Provide equal prominence to Linux and Windows in connection instructions. For example, mention SSH for Linux VMs before or alongside RDP for Windows VMs.
Include links to both Windows and Linux VM connection guides (e.g., /azure/virtual-machines/linux/ssh-from-windows).
Add Linux-specific validation and troubleshooting steps, such as verifying SSH access, checking Linux services, or using Linux command-line tools.
Where examples or screenshots are provided, ensure both Windows and Linux scenarios are covered.
Explicitly mention any differences in failover or post-failover steps for Linux VMs, not just in performance notes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page lists both Azure CLI and PowerShell commands for managing Service Bus rules, but the PowerShell cmdlet (New-AzServiceBusRule) is mentioned in the 'Next steps' section after the CLI, and there are no explicit OS-specific examples. However, the only SDKs linked are .NET, Java, and JavaScript, with .NET (a Microsoft/Windows-centric technology) listed first. There are no Linux-specific tools or shell examples, and the documentation references .NET types and methods (e.g., System.Char.IsLetter, System.Guid.NewGuid()), which may be more familiar to Windows/.NET developers.

Recommendations:

Add explicit Linux shell (bash) examples alongside Azure CLI commands, demonstrating parity with PowerShell.
Include references to cross-platform SDKs (such as Python) and provide usage examples.
When referencing types or methods, provide language-agnostic explanations or equivalents in other languages (e.g., Python, Java).
Ensure that examples and tool references are balanced between Windows and Linux environments.
Consider listing cross-platform tools and SDKs before Windows-specific ones to avoid perceived prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation does not show overt Windows or PowerShell bias in terms of explicit command-line examples, but it does exhibit 'windows_first' and 'missing_linux_example' bias in a few subtle ways. For example, the only command-line example for checking the current primary region uses the 'ping' command, which is available on both Windows and Linux, but the documentation does not clarify this cross-platform applicability or provide Linux-specific context. Additionally, all screenshots and portal instructions are platform-agnostic, but the sample code references only .NET (commonly associated with Windows), and there are no explicit Linux or cross-platform SDK/sample references. There are no PowerShell-specific or Windows tool-specific instructions, but the lack of explicit Linux parity in examples and sample references is a form of bias.

Recommendations:

When providing command-line instructions (e.g., 'ping'), clarify that the command works on both Windows and Linux, or provide equivalent Linux shell commands if differences exist.
Include sample references or code snippets in languages and SDKs commonly used on Linux (e.g., Python, Java, Node.js), not just .NET.
If referencing the Azure CLI, note that it is cross-platform and provide any necessary shell syntax for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
Add explicit statements or sections confirming that all features and management tasks are supported equally on Linux and Windows, especially for automation and scripting.
Where screenshots are used, consider including at least one from a Linux environment or clarify that the portal experience is identical across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup, but consistently lists PowerShell as the second option and highlights PowerShell-specific management resources in the 'Next steps' section. There is a slight Windows bias in the prominence of PowerShell, and the 'Manage Service Bus with PowerShell' article is specifically called out, while equivalent Linux/bash management resources are not.

Recommendations:

Ensure parity by including links to Linux/bash management guides in the 'Next steps' section, such as 'Manage Service Bus with Azure CLI' or scripting with bash.
When listing tools or examples, alternate the order (e.g., sometimes show CLI first, sometimes PowerShell) or clarify that both are cross-platform, with CLI being natively available on Linux/macOS.
Add explicit notes that Azure CLI commands work on Windows, Linux, and macOS, and consider including bash script examples where appropriate.
If mentioning PowerShell, also mention that PowerShell Core is cross-platform, or provide bash alternatives for scripting scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by providing explicit, detailed instructions for updating root certificates on Windows VMs, while the guidance for Linux VMs is less specific and refers users to external vendor documentation. No command-line or step-by-step examples are given for Linux, and Windows is mentioned first in the prerequisites section.

Recommendations:

Provide equally detailed, step-by-step instructions for updating root certificates on common Linux distributions (e.g., Ubuntu, CentOS, RHEL), including example commands.
Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid the perception of prioritizing Windows.
Include troubleshooting tips or common issues for Linux VMs, similar to those provided for Windows.
Where relevant, link to official Linux documentation or Azure-specific Linux guidance, not just generic distributor advice.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides troubleshooting steps for both Windows and Linux VMs but tends to offer more detailed or favorable solutions for Windows. For example, when discussing static IPs after failback, it notes that Windows VMs can reacquire their static IPs automatically, while Linux users are told to manually reconfigure the IP, with no command-line example provided. There are no PowerShell-specific commands or Windows-only tools, but Linux-specific troubleshooting is less detailed and lacks parity in guidance.

Recommendations:

Provide explicit Linux command-line examples (e.g., how to set a static IP on common distributions) alongside Windows guidance.
Clarify any differences in process between Windows and Linux VMs, and ensure both are covered equally in troubleshooting steps.
Where Windows behavior is described as automatic, explain if and how similar automation can be achieved for Linux (e.g., via cloud-init or network manager scripts).
Include references to Linux tools (e.g., nmcli, ifconfig, systemctl) where relevant, not just generic instructions.
Review all troubleshooting steps to ensure Linux users are not left with manual, less-detailed, or less-automated solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by linking to the Windows-specific VM creation guide in the prerequisites section and not mentioning or linking to equivalent Linux VM documentation. There are no examples or instructions tailored for Linux VMs, nor are Linux-specific considerations discussed. All instructions are generic, but the only explicit reference is to Windows.

Recommendations:

In the prerequisites section, provide links to both Windows and Linux VM creation guides (e.g., /azure/virtual-machines/linux/quick-create-portal).
Explicitly mention that the process applies to both Windows and Linux VMs, and highlight any differences if applicable.
Include Linux-specific notes or troubleshooting tips where relevant (e.g., extension removal, OS-specific replication considerations).
Ensure that screenshots and terminology are OS-neutral or provide both Windows and Linux examples where interface or process differs.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is mostly cross-platform in its instructions and code samples, but there is a subtle Windows bias in the references to development tools and supporting documentation. Specifically, the only explicit mention of a platform-specific tool is 'Windows PowerShell' in the context of deploying a Node.js app, and the phrase 'command prompt' is used throughout, which is more commonly associated with Windows than with Linux or macOS. There are no Linux- or macOS-specific instructions or examples, and the documentation does not clarify that all steps work equally well on non-Windows systems.

Recommendations:

Replace or supplement references to 'command prompt' with 'terminal' or 'shell', and clarify that the instructions apply to Windows, Linux, and macOS.
When referencing supporting documentation (such as deploying Node.js apps), include links or notes for Linux/macOS equivalents alongside Windows/PowerShell instructions.
Explicitly state that all commands and code samples are cross-platform, or provide platform-specific notes where minor differences exist.
Mention popular Linux/macOS editors (such as Vim, nano, or Sublime Text) alongside Visual Studio Code, or simply refer to 'your preferred code editor'.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on Azure portal and graphical workflows, which are typically more familiar to Windows users. There are no command-line examples (such as Azure CLI or PowerShell), and there is no mention of Linux-specific tools, workflows, or considerations. The step-by-step instructions and screenshots are all based on the Azure portal, which is platform-agnostic but often associated with Windows-centric usage patterns. There is no guidance for users who prefer or require Linux-based automation or command-line approaches.

Recommendations:

Add equivalent Azure CLI examples for each migration step, including commands to enable managed identities, assign roles, and update authentication types. This will help Linux users who rely on CLI tools.
Explicitly mention that all steps can be performed from any OS using the Azure CLI or ARM templates, and provide links to relevant documentation.
Include a section or callout for Linux administrators, highlighting any differences or additional considerations when performing these tasks from a Linux environment.
Provide PowerShell examples as well, but ensure they are presented alongside (not before) Azure CLI examples to avoid Windows-first bias.
Where screenshots are used, clarify that the Azure portal is accessible from any OS and that no Windows-specific tools are required.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently references Microsoft SQL Server and its associated drivers (e.g., ODBC Driver 18 for SQL Server, mssql-jdbc), which are primarily Microsoft technologies. There is no explicit mention of Linux-specific instructions, such as how to install the required ODBC driver on Linux, nor are there any examples or troubleshooting notes for Linux environments. The documentation implicitly assumes the reader is familiar with Microsoft-centric tooling, and omits Linux-specific caveats or installation steps.

Recommendations:

Add explicit instructions for installing ODBC Driver 18 for SQL Server on Linux distributions (e.g., Ubuntu, CentOS), including package manager commands.
Mention any platform-specific configuration or troubleshooting steps for Linux (e.g., required libraries, environment variable differences, permissions).
Where relevant, clarify that the code samples are cross-platform, or provide notes if any sample is Windows-specific.
Include links to official Microsoft documentation for installing SQL Server drivers on Linux.
If there are known issues or differences in behavior on Linux, document them or provide workarounds.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses the Azure Portal UI for all instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, the only code sample provided is in .NET (C#), which is more commonly associated with Windows environments. There is no mention of Linux-specific tools, shell commands, or parity in scripting. The documentation assumes use of the Azure Portal, which is cross-platform, but the lack of CLI or Linux-oriented examples may disadvantage Linux users or those preferring automation.

Recommendations:

Add equivalent Azure CLI examples for all portal-based steps, showing how to create service connections and configure App Configuration from the command line. Use Bash syntax for Linux parity.
Include at least one example in a language commonly used on Linux (such as Python or Node.js) in addition to .NET/C#.
Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
If PowerShell or Windows-specific tools are referenced in future updates, ensure Linux equivalents are presented side-by-side or first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Visual Studio and the F5 keybinding for running/debugging, which are strongly associated with Windows development environments. There are no explicit Linux or macOS-specific instructions or examples, and the deployment section refers to Visual Studio (not cross-platform) without mentioning alternatives. The troubleshooting and clean-up sections also lack Linux/macOS-specific guidance.

Recommendations:

Explicitly mention that Visual Studio Code is cross-platform and provide alternative instructions for macOS/Linux users where keybindings or UI elements differ.
When referencing Visual Studio for deployment, also mention cross-platform deployment methods (e.g., Azure CLI, VS Code) and provide links or steps.
Include notes or examples for running/debugging the function on Linux/macOS, especially where keybindings or UI may differ.
In troubleshooting and clean-up sections, clarify that the Azure CLI commands work on all platforms and highlight any OS-specific considerations if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but consistently lists PowerShell examples after CLI, and does not include any Linux- or Bash-specific guidance or context. While Azure CLI is cross-platform, the explicit inclusion of PowerShell (a Windows-centric tool, despite its recent cross-platform support) and the lack of any mention of Bash scripting or Linux shell environments may create a subtle Windows bias. There are no Linux-specific tools, patterns, or troubleshooting notes, and no explicit mention that all steps work identically on Linux/macOS.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and can be run from Bash or other Unix shells.
Add a short section or note confirming that all steps are cross-platform, and that PowerShell is optional.
Consider including Bash-specific examples or notes for users who may be scripting in Bash.
Where PowerShell is mentioned, clarify that it is available cross-platform, but not required for Linux/macOS users.
If possible, provide troubleshooting tips or links for common issues encountered on Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Visual Studio Code and Visual Studio, but does not provide any Linux-specific instructions or examples. While Visual Studio Code is cross-platform, the workflow and terminology (e.g., right-click, F5, workspace view) are more familiar to Windows users. There are no explicit Linux command-line or editor alternatives, and no mention of Linux-specific troubleshooting or deployment steps. The guide also references Visual Studio (not Code) for deployment, which is primarily a Windows tool, without offering alternatives for Linux users.

Recommendations:

Explicitly mention that Visual Studio Code instructions apply to Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., keyboard shortcuts, file paths).
Offer alternative instructions for deploying without Visual Studio (e.g., using Azure CLI only, or via VS Code on Linux).
Include Linux/macOS-specific troubleshooting tips, especially for common issues like file permissions or environment setup.
Clarify that Visual Studio (not Code) is not available on Linux, and provide equivalent steps for Linux users (e.g., using VS Code or CLI for deployment).
Where possible, use neutral terminology (e.g., 'select' instead of 'right-click') and provide keyboard shortcuts for all platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias by referencing Windows-specific resources before their Linux equivalents and mentioning Windows tools (such as SQL Server Always On) without Linux alternatives. For example, the link for availability sets points to a Windows VM tutorial, and the multi-tier architecture example uses SQL Server, which is traditionally associated with Windows environments.

Recommendations:

Provide equal prominence to Linux in documentation links, such as linking to both Windows and Linux VM availability set tutorials.
Include examples or references to Linux-based database solutions (e.g., MySQL, PostgreSQL) alongside SQL Server in architecture diagrams and descriptions.
Ensure that any tool or technology mentioned (such as SQL Server Always On) is accompanied by Linux-compatible alternatives or a note about Linux support.
Review all example commands, screenshots, and walkthroughs to ensure they are not Windows-centric and, where possible, provide Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates Windows bias by providing explicit, step-by-step instructions and links for Windows virtual machines (e.g., converting unmanaged to managed disks, updating root certificates), while Linux guidance is minimal and generic (e.g., 'follow the guidance provided by your Linux distributor'). There are no Linux-specific examples or links, and Windows is mentioned first and in more detail.

Recommendations:

Provide equivalent, detailed instructions and official documentation links for Linux virtual machines, such as converting unmanaged to managed disks and updating root certificates.
Include Linux-specific examples or references alongside Windows instructions, not just generic statements.
When listing steps or requirements, alternate the order or present Windows and Linux guidance in parallel to avoid 'Windows first' bias.
Reference official Azure documentation for Linux VM management tasks where possible, similar to the Windows links provided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions or workloads. All examples, prerequisites, and process steps assume a Windows environment, with no mention of Linux clusters, tools, or parity in supported scenarios.

Recommendations:

Explicitly state if Linux-based clusters (such as Pacemaker/Corosync) are supported or not. If not supported, clarify this early in the documentation.
If Linux shared disk clustering is supported, add equivalent guidance, prerequisites, and step-by-step instructions for setting up disaster recovery for Linux clusters.
Include Linux-specific examples, screenshots, and troubleshooting steps where applicable.
If only Windows is supported, consider renaming the article or adding a prominent note to clarify the Windows-only scope to avoid misleading Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes the analysis of the Deployment Planner report for VMware disaster recovery to Azure, focusing on report fields and recommendations. While the content is generally platform-neutral, there are subtle signs of Windows bias: Windows Server EFI virtual machines are specifically mentioned as supported for EFI boot type, with explicit OS version details, while Linux EFI support is not mentioned. Additionally, there are no Linux-specific examples, notes, or parity details for features like EFI support or failover/failback, and no Linux command-line or tool usage is referenced.

Recommendations:

Explicitly state the support status for Linux EFI virtual machines, including any limitations or requirements, to match the detail given for Windows Server.
Provide examples or notes relevant to both Windows and Linux VMs where applicable, especially in sections discussing OS types, boot types, and compatibility.
If there are differences in failover/failback support or tooling for Linux VMs, document them clearly.
Include Linux-specific considerations or troubleshooting steps where relevant, such as for the mobility service or agent versions.
Ensure that any command-line or scripting examples (if added in future) include both Windows (PowerShell) and Linux (bash/CLI) equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not specify or provide examples for Linux-based process servers, nor does it mention Linux administration patterns or tools. It implicitly assumes a Windows environment by referencing 'User name' and 'Password' for Admin permissions and does not clarify whether Linux-based process servers are supported or how to set them up. No Linux-specific instructions, commands, or screenshots are provided.

Recommendations:

Explicitly state whether Linux-based process servers are supported or not. If supported, provide equivalent setup instructions for deploying and configuring a Linux process server VM in Azure.
Include Linux-specific examples for credential setup (e.g., SSH key authentication), package installation, and registration steps.
Mention any differences in process server requirements or capabilities between Windows and Linux.
Provide screenshots or command-line examples relevant to Linux environments where applicable.
Clarify any prerequisites or limitations for Linux process servers in the 'Before you start' section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally presents file paths for both Linux and Windows, but in error logs and troubleshooting steps, Windows-specific paths, hostnames, and service names are mentioned first or exclusively. Error logs reference Windows-style paths (e.g., C:\...), and service names use Windows conventions (e.g., 'Microsoft Azure RCM Proxy Agent'). There are no Linux-specific troubleshooting commands, service names, or examples, and Linux is only mentioned in the context of log file locations.

Recommendations:

Provide Linux-specific troubleshooting steps, including relevant service names and commands (e.g., systemctl commands for restarting services).
Include Linux log examples and error messages, not just Windows-style logs.
When listing file paths or instructions, alternate the order or present Linux examples first in some sections.
Mention Linux equivalents for all Windows tools and services referenced.
Clarify if certain steps or services are only applicable to Windows, and provide Linux alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation instructs users to use the Azure portal (a web-based GUI) to delete a resource group, which is a method commonly associated with Windows workflows. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or PowerShell, which would be more platform-agnostic and accessible to Linux users.

Recommendations:

Add instructions for deleting a resource group using Azure CLI, which works on both Windows and Linux.
Provide PowerShell examples as an alternative, but ensure CLI examples are given equal or higher prominence.
Explicitly mention that the Azure portal is accessible from any OS, but supplement with command-line options for users who prefer or require them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows/Azure portal-centric approach, with all instructions and UI navigation steps tailored to the Azure portal interface. There are no command-line examples (neither PowerShell nor CLI), but also no Linux-specific or cross-platform instructions. The documentation assumes use of the Azure portal, which is platform-agnostic in theory, but in practice, this approach often aligns with Windows-centric workflows and omits Linux CLI or automation alternatives.

Recommendations:

Provide Azure CLI examples for all steps that can be performed via command line (e.g., app registration, adding redirect URIs, creating client secrets), ensuring parity for users on Linux, macOS, and Windows.
Include references to automation or scripting options (such as Azure CLI or REST API) alongside portal instructions.
Explicitly mention that all steps can be performed on any OS using the Azure portal, but highlight CLI alternatives for users who prefer or require non-GUI workflows.
Add a section or callout for Linux users, pointing to relevant CLI documentation or scripts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently provides command-line examples using Azure CLI and bash-style syntax (e.g., export, $(...), jq), which are compatible with Linux/macOS and Windows with WSL or Git Bash. However, there are no explicit examples or notes for Windows users using native Command Prompt or PowerShell, nor are there instructions for installing required tools (like jq) on Windows. The documentation implicitly assumes a Unix-like shell environment, which may disadvantage Windows users who do not use WSL or similar tools.

Recommendations:

Add explicit notes or sections for Windows users, clarifying how to run the commands in PowerShell or Command Prompt, or recommend using WSL or Git Bash.
Provide Windows-native equivalents for commands that use Unix utilities (e.g., using jq, export, $(...), and piping). For example, show how to set environment variables and parse JSON in PowerShell.
Include installation instructions for required tools (like jq and Azure CLI) specifically for Windows, with links to Windows installers.
Where possible, provide both bash and PowerShell command examples side-by-side, or indicate which shell is required for each example.
Add a 'Platform compatibility' note in the prerequisites, clarifying the expected shell environment and alternatives for Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation presents configuration steps and CLI examples only in the context of the Azure portal and Azure CLI, without specifying or demonstrating any OS-specific commands. However, there is an implicit Windows bias: the Azure CLI installation and usage instructions do not mention Linux or macOS environments, nor do they provide any shell-specific guidance (e.g., Bash vs. PowerShell). There are no Linux-specific examples, troubleshooting tips, or references to Linux tools or shell environments, which may leave Linux users without clear guidance.

Recommendations:

Explicitly mention that Azure CLI commands are cross-platform and provide links or instructions for installing and using Azure CLI on Linux and macOS.
Include example commands using both Bash (for Linux/macOS) and PowerShell (for Windows), or clarify that the given commands work in all supported shells.
Add troubleshooting tips or notes for common issues on Linux (e.g., permissions, environment variables, dependency installation).
Where UI navigation is described, clarify that the Azure portal is web-based and OS-agnostic.
Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page on Azure Blob snapshots does not provide any OS-specific command-line examples, but in the 'Next steps' section, it links only to a Windows-specific guide for backing up Azure unmanaged VM disks with incremental snapshots. There are no Linux or cross-platform equivalents mentioned or linked. Additionally, the mention of VHD files and VM disk detachment is presented in a way that implicitly assumes a Windows-centric context, as VHD is a format primarily associated with Windows environments.

Recommendations:

Add links to Linux-focused or cross-platform guides for managing blob snapshots and backing up VM disks, such as documentation for Azure Linux VMs or using AzCopy/CLI tools on Linux.
When referencing VM disk formats, clarify support for both Windows (VHD) and Linux (VHD, VHDX, or other formats as appropriate), and provide examples relevant to both environments.
In the 'Next steps' section, include parallel documentation for Linux users, such as 'Back up Azure unmanaged VM disks with incremental snapshots (Linux)' if available.
Ensure that any best practices or operational guidance is not implicitly Windows-centric, and explicitly mention cross-platform tools (e.g., Azure CLI, AzCopy) with usage examples for both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio Code UI navigation patterns (e.g., 'File > Open Folder') and omitting any mention of Linux-specific instructions or terminal-based workflows. There are no examples or notes for Linux users, nor are there alternative instructions for common Linux environments. The reliance on GUI-based steps and lack of parity for Linux users may hinder accessibility for non-Windows developers.

Recommendations:

Add explicit instructions or notes for Linux (and macOS) users, especially where UI navigation or keyboard shortcuts may differ.
Include terminal-based alternatives for key steps (e.g., opening folders, installing extensions) that are common in Linux workflows.
Where possible, provide screenshots or examples from Linux environments in addition to Windows.
Clarify that Visual Studio Code and the Azure extension are cross-platform, and link to platform-specific installation guides.
Review all steps for assumptions about the user's operating system and add parity for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation is generally cross-platform and avoids explicit Windows bias in most areas. However, in the section on decoding SAS token signatures, the PowerShell example is presented first, with the Linux/bash/python alternative only mentioned after. This ordering and inclusion of PowerShell as the primary example demonstrates a subtle 'windows_first' and 'powershell_heavy' bias.

Recommendations:

When providing code examples for tasks like decoding or hashing, present both Windows (PowerShell) and Linux (bash/python) examples together, or explicitly state that both are supported.
Consider presenting the Linux/bash example first, or in parallel with the PowerShell example, to avoid the perception of Windows being the default environment.
Where possible, use platform-agnostic tools or SDKs in examples (e.g., Azure CLI, Python scripts) that work equally well on Windows, Linux, and macOS.
Add a note clarifying that all tasks can be performed on both Windows and Linux, and provide links to relevant cross-platform tooling documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references AzCopy as the primary example utility for data transfer cost estimation, but does not mention or provide examples for Linux-native tools or cross-platform command-line usage. There are no PowerShell-specific examples, but the exclusive focus on AzCopy (which is cross-platform but often associated with Windows) and lack of explicit Linux/Unix tool references or examples (such as Azure CLI, REST API with curl, or scripting in bash) indicates a subtle Windows bias.

Recommendations:

Explicitly mention that AzCopy is available on Windows, Linux, and macOS, and provide installation instructions or links for all platforms.
Include examples using Azure CLI (az storage blob ...), which is widely used on Linux and macOS, alongside AzCopy examples.
Provide sample commands for common Linux tools (e.g., curl for REST API calls) to estimate or interact with Blob Storage.
Clarify in each example that the commands and tools are cross-platform, and where relevant, show both Windows (cmd/PowerShell) and Linux (bash) command syntax.
Add a section or note highlighting cross-platform options for cost estimation and data transfer, ensuring Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation instructs users to 'open a command prompt window' and provides AzCopy CLI commands without specifying or illustrating that these commands work identically on Linux/macOS terminals. There are no explicit Linux (bash) or macOS terminal references, nor are there alternative instructions or screenshots for non-Windows environments. The phrase 'command prompt window' is a Windows-centric term, and the lack of cross-platform clarification may lead Linux/macOS users to feel excluded or uncertain.

Recommendations:

Replace 'command prompt window' with 'terminal window' or specify 'open a command prompt (Windows) or terminal (Linux/macOS) window'.
Explicitly state that AzCopy is cross-platform and works on Windows, Linux, and macOS.
Add a note or section confirming that the provided AzCopy commands are valid in bash/zsh shells on Linux/macOS, and that no syntax changes are required.
If there are any platform-specific differences (e.g., path formats), highlight them with examples for both Windows and Linux/macOS.
Consider including screenshots or terminal prompts (e.g., C:\> for Windows, $ for bash) to visually reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence to the CLI, and there is no explicit mention of Linux or Bash shell usage. The CLI example uses generic shell syntax, but the PowerShell example is specifically called out, which may suggest a slight Windows bias. However, there are no overtly Windows-specific tools or missing Linux examples, as Terraform and Azure CLI are cross-platform.

Recommendations:

Explicitly mention that the Azure CLI example works on Linux, macOS, and Windows (in Bash or compatible shells), to reassure non-Windows users.
Consider labeling the CLI tab as 'Bash or Azure CLI' to clarify its cross-platform nature.
If possible, add a short note or example for macOS/Linux users to highlight parity and inclusivity.
Ensure that any references to PowerShell are balanced by references to Bash or other common Linux shells, especially in multi-tabbed instruction sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by featuring a video specifically about mounting Azure file shares in Windows, while lacking any equivalent video or mention for mounting on Linux or macOS. Additionally, SMB workloads (commonly associated with Windows) are highlighted, but there is only a brief mention of NFS 4.1 (a Linux/UNIX protocol) without a corresponding 'how-to' video for Linux users. There are no explicit Linux examples or parity in the video topics.

Recommendations:

Add videos or documentation links that demonstrate how to mount Azure file shares on Linux and macOS, using both SMB and NFS protocols.
Ensure that for every Windows-specific instructional video (e.g., mounting in Windows), there is a Linux (and optionally macOS) equivalent.
Highlight Linux tools and command-line examples (such as mount.cifs, mount.nfs, or Azure CLI usage on Linux) alongside Windows/PowerShell examples.
Balance the focus on SMB (Windows-centric) with more content on NFS and Linux/UNIX integration scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and Azure CLI examples for checking the Last Sync Time property. However, the PowerShell example is presented first, which may suggest a Windows-first or PowerShell-preferred workflow. There are no explicit Linux-specific examples or notes, and the CLI example is generic but not tailored for Linux environments.

Recommendations:

Alternate the order of examples, sometimes presenting Azure CLI first, especially since Azure CLI is cross-platform and commonly used on Linux.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant (e.g., shell syntax differences).
Consider adding a Bash shell example or clarifying that the Azure CLI example is suitable for Linux/macOS terminals.
If PowerShell is included, clarify that PowerShell Core is also available on Linux and macOS, or provide a note about cross-platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation references both PowerShell and Azure CLI for migration, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in both the main migration options and in the links to further instructions. There are no explicit Linux-specific examples, and the documentation does not mention Bash, shell scripts, or Linux-native tools. This ordering and emphasis subtly prioritizes Windows/PowerShell users, which may make Linux users feel secondary.

Recommendations:

Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first in some sections to balance perceived priority.
Explicitly mention that both PowerShell and Azure CLI are cross-platform, and provide examples or links for both Windows and Linux environments.
Include at least one example command or workflow using Azure CLI (preferably in Bash syntax) directly in the documentation, not just as a link.
Add a note or section clarifying that all migration steps can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats if relevant.
Where possible, avoid phrasing that implies PowerShell is the default or primary method for migration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a Windows-first bias, particularly in the local Azurite setup instructions. The npm installation example uses Windows-style paths (e.g., c:\azurite) and does not provide equivalent Linux/macOS commands or path examples. There is no explicit Linux/macOS example for creating directories or launching Azurite with appropriate paths. While the Docker example is cross-platform, the primary non-Docker instructions assume a Windows environment. The Azure Pipelines section does use bash and Linux-style commands, but the local setup is Windows-centric.

Recommendations:

Provide parallel Linux/macOS command examples for installing and running Azurite, including directory creation and path usage (e.g., mkdir ~/azurite and --location ~/azurite).
Clearly label which code blocks are for Windows and which are for Linux/macOS, or present both side by side.
Avoid using only Windows-style paths in documentation; include POSIX-style paths where appropriate.
Mention that Azure Storage Explorer is available on multiple platforms, and clarify any platform-specific steps if necessary.
Ensure all steps (such as creating virtual environments and running commands) are shown with both Windows and Linux/macOS syntax where they differ.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and Azure CLI examples, but presents PowerShell (a Windows-centric tool) before Azure CLI, which is cross-platform. There are no explicit Linux shell or scripting examples, and the CLI example uses Bash syntax but is not labeled as such. There is a slight preference for Windows tooling and ordering.

Recommendations:

Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
Explicitly label the CLI example as Bash/Linux compatible, and consider providing a Windows Command Prompt/Batch variant if needed.
Add a note clarifying that Azure CLI commands work natively on Linux, macOS, and Windows.
Where possible, include examples using native Linux tools or scripting (e.g., Bash), or clarify that the steps are platform-agnostic.
Review all screenshots and UI instructions to ensure they are not Windows-specific, or provide Linux/macOS equivalents if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing Windows-specific authentication mechanisms (authentication broker) before Linux/macOS equivalents and recommending them primarily for Windows users. The 'authentication broker' is described as the default and recommended for Windows, while Linux and macOS are grouped together as using the default web browser. No Linux-specific troubleshooting or examples are provided, and the language and ordering subtly prioritize Windows patterns.

Recommendations:

Present sign-in methods for all platforms in parallel, rather than listing Windows first.
Provide Linux-specific troubleshooting steps or notes if there are known issues or differences.
Clarify whether all features (such as 'authentication broker' or 'integrated sign-in') are equally available and supported on Linux, and note any limitations.
Include explicit Linux examples or screenshots where relevant to ensure parity.
Avoid language that recommends or defaults to Windows-specific tools unless there is a technical requirement, and always provide Linux alternatives with equal prominence.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the use of Azure File Sync, which is only supported on Windows servers, and all monitoring instructions reference the Azure portal or Azure Monitor without any mention of Linux-based tools or environments. There are no Linux-specific examples or guidance, and the documentation implicitly assumes a Windows Server environment.

Recommendations:

Explicitly state that Azure File Sync and its monitoring features are only supported on Windows Server, to clarify the platform limitation.
If any monitoring or reporting can be done from Linux (e.g., via Azure CLI, REST API, or cross-platform tools), provide equivalent Linux command-line examples.
Where possible, reference cross-platform Azure management tools (such as Azure CLI or REST API) alongside portal instructions.
If Linux support is not available, add a clear note about the Windows-only nature of the feature to set expectations for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both PowerShell and Azure CLI examples for all operations, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in every code tab and example. There are no Linux-specific shell examples (e.g., Bash scripts), and the CLI examples are generic, but the ordering and emphasis may suggest a preference for Windows/PowerShell users.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or place Azure CLI first, as it is cross-platform and widely used on Linux.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific variable syntax in CLI examples where appropriate.
Consider adding Bash script examples or notes for Linux users, especially for variable assignment and scripting differences.
Clarify in introductory sections that both PowerShell and Azure CLI are supported on all major platforms, but that PowerShell examples use Windows-style syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists Microsoft client tools for Azure Storage, but it prioritizes Windows-specific tools (e.g., Visual Studio Cloud Explorer is Windows-only) and does not provide Linux-specific examples or mention Linux-native tools. While Azure Storage Explorer is cross-platform, the only other detailed client tool (Visual Studio Cloud Explorer) is exclusive to Windows, and there is no discussion of command-line or native Linux alternatives.

Recommendations:

Include command-line tools such as Azure CLI and AzCopy, both of which are cross-platform and widely used on Linux.
Add explicit Linux usage examples or screenshots where possible.
Mention Linux-native or open-source tools (even if third-party) that are commonly used to interact with Azure Storage.
Reorder the presentation so that cross-platform tools are highlighted first, and Windows-only tools are clearly marked as such.
Provide parity in documentation by including instructions or references for Linux users alongside Windows instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any OS-specific proxy configuration examples or guidance, but implicitly assumes a Windows-centric perspective by referencing 'system proxy' and OS proxy settings without clarifying differences across platforms. There are no examples or instructions for configuring proxies on Linux or macOS, nor are there references to Linux-specific tools or patterns. The recommendation to use 'system proxy' is made without noting that proxy configuration methods differ significantly between Windows, Linux, and macOS.

Recommendations:

Add explicit instructions or references for configuring system proxy settings on Linux (e.g., using environment variables, GNOME/KDE network settings, or /etc/environment) and macOS (e.g., System Preferences > Network > Proxies).
Include example commands or screenshots for setting environment variables on Linux and macOS, not just Windows.
Clarify that the method for setting system proxy varies by OS, and provide links to relevant documentation for each platform.
If mentioning NTLM or Negotiate authentication, note that these are primarily Windows technologies and may not be available or work differently on Linux/macOS.
Ensure parity in troubleshooting steps and proxy authentication support notes for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits mild Windows bias by referencing Windows-specific tools and patterns, such as comparing Azure Storage encryption to BitLocker (a Windows technology) and linking to the Windows Cryptography API: Next Generation (CNG) documentation. These references are made without mentioning Linux equivalents or cross-platform alternatives. However, the rest of the content is largely platform-neutral and does not provide command-line or code examples that are Windows- or PowerShell-specific.

Recommendations:

When drawing analogies, include Linux equivalents (e.g., compare Azure Storage encryption to both BitLocker on Windows and LUKS/dm-crypt on Linux).
When referencing cryptographic APIs, mention cross-platform standards or Linux alternatives (e.g., OpenSSL, GnuPG, or Linux kernel crypto modules) alongside Windows CNG.
Ensure that any future code or command-line examples are provided for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI), or use platform-agnostic Azure CLI examples.
Explicitly state that Azure Storage encryption is platform-agnostic and does not require specific OS-level tools, to reassure Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a subtle Windows bias, particularly in its use of Windows-style file paths (e.g., 'C:/path/to/directory') in code examples and the absence of explicit Linux/macOS examples or notes. While the Data Movement library is cross-platform and the .NET SDK is available for multiple operating systems, the documentation does not provide Linux or macOS-specific guidance, examples, or file path conventions. There is also no mention of platform-specific considerations or differences, which may leave Linux users without clear guidance.

Recommendations:

Provide code examples that use Linux/macOS-style file paths (e.g., '/home/user/path/to/directory') alongside or instead of Windows paths.
Explicitly state that the Data Movement library and examples work on Linux and macOS, and mention any platform-specific considerations if applicable.
Add a note or section in 'Set up your environment' clarifying cross-platform compatibility and how to adapt file paths for different operating systems.
Wherever file paths are shown, use a variable or placeholder (e.g., '<local-directory-path>') and provide both Windows and Linux/macOS examples.
If there are any known issues or differences in behavior on Linux/macOS, document them or link to relevant resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples, with no Linux or macOS path examples provided. While there are repeated notes about quoting differences between shells, every example defaults to Windows paths and syntax, and there are no explicit Linux (e.g., '/home/user/myDirectory/myTextFile.txt') or macOS examples. This may make the documentation less accessible or immediately usable for Linux/macOS users.

Recommendations:

For each example using a Windows path, provide a parallel example using a Linux/macOS path (e.g., '/home/user/myDirectory/myTextFile.txt').
In each section, alternate the order of examples or explicitly show both Windows and Linux/macOS command lines.
Add a dedicated section or callout early in the document that summarizes path and quoting differences, with concrete Linux/macOS examples.
Where relevant, mention any OS-specific considerations (such as file permissions or environment variables) that may differ between Windows and Linux/macOS.
Consider using environment variables or placeholders (e.g., <local-directory-path>) in examples, and then show both a Windows and a Linux/macOS instantiation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias in its examples and guidance for mounting and accessing Azure Files with .NET. While it mentions both Windows and Linux in the context of mounting SMB/NFS shares, all code examples and file path conventions use Windows-style paths (e.g., Z:\file-share), and there are no Linux-specific examples or file path formats. The mounting section references both OSes, but the practical, step-by-step code and usage scenarios are exclusively Windows-centric.

Recommendations:

Provide parallel Linux examples alongside Windows examples, especially for mounting file shares and accessing them via System.IO.
Include Linux-style file paths (e.g., "/mnt/file-share") in code samples and explanations.
Explicitly show how to enumerate directories, write files, and handle file locks on Linux-mounted shares, noting any differences or caveats.
When referencing mounting instructions, give equal prominence to Linux and Windows, or present them in a neutral order.
Add notes or callouts about cross-platform differences in file system permissions, locking, and path handling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myDirectory/myTextFile.txt'). While there are notes about quoting differences between shells, all concrete examples use Windows paths, which may confuse or alienate Linux/macOS users. No PowerShell-specific commands are present, but the documentation implicitly prioritizes Windows environments.

Recommendations:

For each example, provide both Windows and Linux/macOS path variants (e.g., show both 'C:\myDirectory\myTextFile.txt' and '/home/user/myDirectory/myTextFile.txt').
Alternate or parallelize examples so that Linux/macOS paths are shown first in some sections, or at least equally.
Add a section or table summarizing path and quoting conventions for Windows cmd, PowerShell, Linux bash, and macOS zsh.
Explicitly state that AzCopy is cross-platform and provide links or tips for Linux/macOS installation and usage.
Ensure that any references to file locations (such as the list-of-versions.txt) include both Windows and Linux-style paths.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation consistently lists the Azure portal, PowerShell, and Azure CLI as the primary methods for changing redundancy, always in that order. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, appears before it. While Azure CLI is cross-platform, the ordering and emphasis may suggest a Windows-first approach. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell scripting patterns. The documentation does not provide parity for Linux users beyond the Azure CLI, and PowerShell is not explicitly marked as cross-platform (even though it can be).

Recommendations:

Alternate the order of PowerShell and Azure CLI in instructions and tables, or list Azure CLI first to reflect its cross-platform nature.
Explicitly note that PowerShell Core is available cross-platform, or clarify when instructions are Windows-specific.
Add Bash shell scripting examples or highlight Linux-native usage patterns where appropriate.
Where possible, include references to Linux-native tools (e.g., AzCopy usage from Bash) or provide sample scripts for Linux environments.
Ensure screenshots and UI walkthroughs are not Windows-centric (e.g., avoid only showing Windows-style UI elements if possible).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform parity but exhibits subtle Windows bias in a few areas. In the project setup section, Windows tools like Visual Studio Code ('code .') are referenced without mentioning alternatives. In authentication instructions, Windows-centric tools (PowerShell) are listed alongside cross-platform options, but Windows is often mentioned first. When setting environment variables, Windows instructions precede Linux, and the Windows-specific 'setx' command is shown before the Linux 'export' command.

Recommendations:

When referencing code editors, mention alternatives to Visual Studio Code or clarify that 'code .' is optional and VS Code is cross-platform.
For environment variable instructions, present Linux/macOS and Windows commands side by side or in separate tabs, without always listing Windows first.
In authentication sections, avoid listing PowerShell before cross-platform tools, or group instructions by OS with equal prominence.
Explicitly state that all commands and steps work on Linux, macOS, and Windows, and provide Bash or zsh examples where relevant.
Where possible, use neutral language like 'terminal' or 'shell' instead of 'console window (such as cmd, PowerShell, or Bash)'.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page lists several migration tools that are Windows-centric (e.g., Robocopy, Storage Migration Service, Azure File Sync) without mentioning Linux-native equivalents or providing Linux usage examples. There are no explicit Linux command-line examples or references to Linux tools, despite both services supporting NFS and Linux workloads.

Recommendations:

Include Linux-native migration tools (e.g., rsync, NFS copy, scp, or Linux-based data movers) in the migration tools lists.
Provide example commands or workflows for both Windows (e.g., Robocopy, AzCopy) and Linux (e.g., rsync, cp, mount) environments.
Mention Linux authentication and integration options (e.g., LDAP, Kerberos for NFS) more explicitly and provide links to relevant Linux setup guides.
Ensure that documentation and linked resources cover both SMB (Windows) and NFS (Linux/UNIX) scenarios equally, including setup and troubleshooting.
Where tools are cross-platform (e.g., AzCopy), clarify their usage on both Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides detailed instructions and examples for both PowerShell and Azure CLI, but the PowerShell (Windows-centric) section is presented before the Azure CLI (cross-platform) section. There are no Linux-specific examples or references to Linux tools, but Azure CLI is inherently cross-platform. No explicit Windows-only tools are mentioned, but the ordering and emphasis on PowerShell may signal a Windows-first bias.

Recommendations:

Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux and macOS users.
Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide installation links for each platform.
Consider adding a short section or note highlighting that all examples work on Linux and macOS, not just Windows.
If possible, provide bash shell examples or clarify that Azure CLI commands are intended for use in bash/zsh as well as Windows command prompt or PowerShell.
Review other documentation pages for similar ordering and ensure parity in example prominence for cross-platform tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias in its examples and guidance for mounting Azure file shares and using file paths. Specifically, the only concrete file path examples use Windows-style paths (e.g., 'Z:\\file-share'), and all code samples for file I/O reference these Windows paths. While links to both Windows and Linux mounting instructions are provided, there are no Linux or cross-platform code examples or file path usages. This may make it less approachable for Linux developers or those working in cross-platform environments.

Recommendations:

Provide Linux-specific or cross-platform file path examples alongside Windows examples (e.g., '/mnt/file-share' for Linux).
Include at least one code example using a Linux-style mounted path, or demonstrate how to write code that works on both platforms (e.g., using os.path.join and platform detection).
When referencing mounting instructions, alternate the order or present both Windows and Linux options equally, rather than listing Windows first.
Add notes or code comments clarifying how to adapt examples for Linux environments.
Consider including a section or callout on cross-platform compatibility and best practices for supporting both Windows and Linux in Python applications using Azure Files.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild 'Windows-first' bias by linking to Windows-specific Azure VM quickstart and overview pages before or instead of Linux equivalents. While the main migration example uses a Linux source host and Linux commands (e.g., iostat), there are no explicit Linux-focused Azure VM setup links or parity in 'Next steps' resources. There are no PowerShell-heavy sections or exclusive use of Windows tools, but Linux users may find the guidance less discoverable.

Recommendations:

In the 'Implementation guide', provide links to both Windows and Linux Azure VM quickstart guides, or a neutral landing page that covers both.
In the 'Next steps' section, include links to both Windows and Linux Azure VM overview pages.
Wherever VM setup is referenced, clarify that the process applies to both Windows and Linux, and provide OS-agnostic or parallel instructions.
Consider adding a brief section or callout for Linux users, summarizing any OS-specific considerations or linking to relevant Azure Linux documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates bias by omitting Linux support for screen readers and not providing any Linux-specific accessibility guidance or keyboard shortcuts. Windows is listed first in the screen reader table, and only Windows and Mac are mentioned as supported platforms. All shortcut keys use Windows-style notation, with no mention of Linux alternatives or differences.

Recommendations:

Clarify whether Linux support is planned or possible for screen readers, and provide updates if/when it becomes available.
If Storage Explorer is available on Linux, explicitly state the accessibility limitations and suggest any possible workarounds (e.g., using Wine with Windows screen readers, or community-supported tools).
Include Linux-specific instructions or notes for keyboard shortcuts, especially if they differ from Windows/Mac.
List platforms in a neutral order (e.g., alphabetical: Linux, Mac, Windows) to avoid implicit prioritization.
Provide parity in documentation by mentioning accessibility features or limitations for all supported platforms, not just Windows and Mac.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on using Visual Studio Code for creating and managing Azure Stream Analytics jobs, without mentioning platform-specific instructions or examples. However, all workflow steps and references are centered around Visual Studio Code, which, while cross-platform, is often associated with Windows in Azure documentation. There are no explicit Linux or macOS instructions, nor are there examples or notes about platform-specific considerations, which may leave Linux users without guidance on potential differences or requirements.

Recommendations:

Explicitly mention that Visual Studio Code is available on Windows, Linux, and macOS, and that the instructions apply to all platforms.
Add notes or sections highlighting any platform-specific steps, such as command-line differences, file path conventions, or prerequisites for Linux/macOS users.
Provide example commands or screenshots from both Windows and Linux environments where relevant.
Include troubleshooting tips for common issues encountered on Linux (e.g., permissions, dependency installation).
Reference alternative editors or tools that Linux users may prefer, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes using the Azure Portal GUI for configuration and verification, with all screenshots and navigation instructions reflecting the Windows-centric Azure Portal interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux tools or workflows. The documentation implicitly assumes a graphical, Windows-like environment and does not address how to perform these tasks from Linux or cross-platform command-line environments.

Recommendations:

Add equivalent instructions for performing these operations using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include sample commands for creating Event Hubs, Data Lake Storage accounts, and configuring Stream Analytics jobs using CLI or ARM templates.
Provide guidance on how to verify output files using Azure CLI (e.g., az storage blob list) or other cross-platform tools, not just through the Azure Portal.
Explicitly mention that all steps can be performed from any OS using the Azure Portal, but highlight and document command-line alternatives for automation and Linux users.
Where screenshots are used, consider including text-based equivalents or references for users who may not have access to a GUI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally covers Windows, macOS, and Linux in parallel, especially in the prerequisites and installation sections. However, there is evidence of Windows bias: Windows is consistently presented first in tabbed sections, and the legacy Azure Storage Emulator (which is Windows-only) is mentioned before Azurite (cross-platform) in the local emulator section. There are no PowerShell-heavy examples or missing Linux examples, but the ordering and some tool references prioritize Windows.

Recommendations:

Rotate or randomize the order of OS tabs (Windows, macOS, Linux) or use alphabetical order to avoid always listing Windows first.
In the local storage emulator section, mention Azurite (cross-platform) before the legacy Azure Storage Emulator (Windows-only), and clarify Azurite as the recommended emulator.
Where possible, ensure that any tool or workflow mentioned for Windows has an equivalent or alternative for Linux/macOS, and present them with equal prominence.
Explicitly state when a feature or tool is Windows-only to help set user expectations.
Consider adding more Linux/macOS-specific troubleshooting or usage tips to further balance the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the 'Create the project' section, where Windows shells (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code (a Microsoft tool) is suggested as the editor without mentioning alternatives. However, most commands and instructions are cross-platform, and Linux is not excluded, but Windows environments are prioritized in the order of mention.

Recommendations:

When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') or simply say 'in a terminal' to avoid prioritizing Windows shells.
When suggesting editors, mention alternatives to Visual Studio Code (e.g., 'Open the project in your preferred code editor, such as Visual Studio Code, Atom, or Sublime Text').
Explicitly state that all commands are cross-platform and work on Windows, Linux, and macOS.
Where environment variable instructions are given, clarify any OS-specific differences (e.g., how to set environment variables in Bash vs. PowerShell/cmd).
Include example output or screenshots from both Windows and Linux terminals, if possible, to reinforce cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page assumes the use of Visual Studio Code with the ASA Tools extension for development and local runs, but does not mention or provide guidance for Linux users. All setup and workflow instructions are written generically, but the only development environment referenced is VS Code, which is cross-platform, yet the documentation does not explicitly address Linux or macOS users, nor does it provide any Linux-specific instructions or troubleshooting. There are no references to Windows-only tools, but the lack of Linux parity in examples and environment setup is a subtle bias.

Recommendations:

Explicitly state that Visual Studio Code and the ASA Tools extension are supported on Windows, Linux, and macOS.
Provide any Linux-specific setup steps or troubleshooting tips, especially for installing the ASA Tools extension and running local jobs.
Include example terminal commands for both Windows (PowerShell/CMD) and Linux/macOS (bash) when referencing file creation, navigation, or running local jobs.
Mention any known limitations or differences when running ASA local jobs on Linux/macOS, if applicable.
Add a note or section for Linux/macOS users to ensure they have a smooth experience following the tutorial.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page is generally cross-platform and does not provide OS-specific command-line examples, but it does exhibit Windows bias in its references to time zone names and date/time formatting. Specifically, it refers exclusively to 'Microsoft Windows Default Time Zones' for time zone names and uses .NET and Windows-centric date/time format strings. There is no mention of IANA/Olson time zone names or Unix/Linux equivalents, and the documentation does not clarify how Linux users should map or use time zones in Logic Apps. Additionally, all links and references for time zone handling point to Windows documentation, and the default examples and explanations assume a Windows/.NET environment.

Recommendations:

Add information about IANA/Olson time zone names and clarify whether they are supported or how to map them to Windows time zone names.
Explicitly state that time zone names must use the Windows format and provide a mapping table or reference for Linux/Mac users.
Where .NET or Windows-specific format strings are referenced, clarify that these are required regardless of the user's OS, and provide guidance for users coming from Linux or other environments.
Consider including a note or section on cross-platform considerations for users who may be more familiar with Linux/Unix conventions (e.g., time zone naming, date/time formatting).
Where possible, provide links to cross-platform resources or explain the rationale for Windows-centric requirements in Azure Logic Apps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page displays a subtle Windows bias by referencing Windows in the authentication link (../quickstarts/identity/access-tokens.md?tabs=windows&pivots=platform-azportal) as the default or first tab, rather than providing a cross-platform or Linux example. However, there are no explicit PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples in the main content. The documentation is otherwise platform-neutral and covers web, iOS, and Android parity.

Recommendations:

Ensure that authentication and other platform-neutral features provide Linux and macOS examples or tabs alongside Windows, or default to a cross-platform approach.
Wherever a link or tab is provided (such as for authentication), offer parity for Linux (e.g., Bash, CLI) and macOS, not just Windows.
Review all quickstart and how-to links to confirm that Linux users are not required to adapt Windows-specific instructions.
Explicitly mention cross-platform compatibility in sections that are not inherently OS-specific.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific configuration or command-line examples. However, it also does not include any Windows- or PowerShell-specific instructions, nor does it mention Windows tools or patterns. The absence of any CLI or scripting examples means there is no explicit Windows bias, but there is also a missed opportunity to provide parity for Linux users (e.g., Azure CLI or Bash examples).

Recommendations:

Add examples for configuring the minimum TLS version using cross-platform tools such as Azure CLI, which works on both Windows and Linux.
If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided alongside.
Explicitly mention that the configuration steps can be performed from any OS using supported tools (Azure Portal, Azure CLI, REST API, etc.).
Include troubleshooting steps or verification commands that can be run from both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a 'windows_first' bias in the section on setting environment variables, where Windows PowerShell syntax is presented before the Bash/Linux equivalent. However, the remainder of the documentation uses cross-platform Azure CLI and Bash commands, and does not otherwise prioritize or exclusively reference Windows tools or patterns.

Recommendations:

Present Linux/Bash environment variable examples before or alongside Windows PowerShell examples, as Linux is the primary platform for containerized workloads.
Explicitly state that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows (with WSL or native Bash).
Wherever platform-specific instructions are needed, provide both Windows and Linux/macOS variants in parallel, or link to platform-specific setup guides.
Consider removing the PowerShell example unless there is a clear user need, or move it to an appendix or a 'Windows users' note.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page is generally platform-neutral, but in the section on Azure Key Vault soft-delete, the PowerShell example is mentioned before the CLI example. This ordering subtly prioritizes Windows tooling, as PowerShell is more closely associated with Windows environments, while the Azure CLI is cross-platform and more commonly used on Linux and macOS.

Recommendations:

When listing platform-specific tools or examples, alternate the order in which they are presented (e.g., mention CLI before PowerShell in some places, especially in cross-platform documentation).
Explicitly state that both PowerShell and CLI are supported, and provide parity in examples and references.
Where possible, provide code snippets or links for both PowerShell and CLI together, or use the Azure CLI as the primary example since it is cross-platform.
Consider adding a note clarifying that both Windows and Linux users are supported equally, and link to relevant documentation for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a mild 'windows_first' bias by listing 'Azure portal, Azure PowerShell, or command-line interface' in that order when describing how to scale out worker nodes. PowerShell is a Windows-centric tool, and its mention before more cross-platform or Linux-native tools (such as Azure CLI or Bash) subtly prioritizes Windows workflows. However, the rest of the article is platform-neutral, focusing on Hive, Tez, and general Hadoop concepts, and does not provide OS-specific examples or instructions.

Recommendations:

When listing tools or interfaces, mention cross-platform or Linux-native tools (such as Azure CLI or Bash) before or alongside Windows-specific tools like PowerShell.
Provide explicit Linux command-line examples (e.g., using Azure CLI in Bash) where relevant, especially in sections discussing cluster management.
If mentioning PowerShell, clarify that equivalent commands are available for Linux/macOS users via Azure CLI or Bash.
Consider adding a brief section or note on managing HDInsight clusters from Linux environments to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page contains a subtle Windows bias in the section discussing the 'mode' property. It mentions PowerShell before Azure CLI when describing how to specify the 'mode' parameter, and provides default behavior for both, but lists Azure PowerShell first. No explicit Windows-only tools, PowerShell-heavy examples, or missing Linux examples are present, but the ordering suggests a slight preference for Windows-centric tooling.

Recommendations:

When referencing cross-platform tools such as PowerShell and Azure CLI, alternate the order in which they are mentioned or explicitly state that both are supported equally.
Provide example commands for both Azure PowerShell and Azure CLI when discussing actions that can be performed with either tool.
Consider including a note that both Azure CLI and PowerShell are cross-platform and available on Windows, Linux, and macOS.
Review documentation for other subtle ordering or phrasing that may imply a preference for Windows tools, and adjust for neutrality.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display explicit Windows bias, as it avoids mentioning any OS-specific tools or commands. However, it also lacks any platform-specific guidance or examples, including for Linux, which could leave Linux users without clarity on whether the instructions are applicable to their environment.

Recommendations:

Clarify if the instructions are platform-agnostic or specify any OS-specific steps if needed.
If there are differences in accessing the 'Log stream' feature or generating log messages on Linux vs. Windows, provide examples for both platforms.
Explicitly state that the steps apply to all supported platforms, or add notes for Linux users if there are unique considerations.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or commands, but it also omits any mention of how to perform the steps via command line or scripts (such as Azure CLI, PowerShell, or Bash). This lack of parity is a subtle form of bias, as it assumes users will use the Azure Portal UI, which is more common among Windows users. There are no explicit Windows tools or PowerShell commands, but the absence of Linux/CLI alternatives is a gap.

Recommendations:

Add step-by-step instructions for creating private endpoints and configuring DNS using Azure CLI commands, which are cross-platform and commonly used on Linux.
Include examples for both Azure CLI and PowerShell (if relevant), and present them side-by-side or with clear tabs.
Mention that these operations can be performed via the Azure Portal, Azure CLI, or PowerShell, and provide links to relevant documentation for each method.
Ensure that any screenshots or UI references are supplemented with equivalent command-line instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only portal-based (GUI) instructions for managing Azure NetApp Files billing tags and downloading cost data. There are no command-line examples or references for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash). However, the lack of any CLI examples means Linux users are not shown how to perform these tasks from the command line, which is a common workflow for Linux environments.

Recommendations:

Add Azure CLI examples for adding, editing, and viewing tags on capacity pools, as well as for downloading cost data, to ensure Linux users have clear, platform-agnostic instructions.
If PowerShell examples are added in the future, ensure Azure CLI (cross-platform) equivalents are provided alongside.
Explicitly mention that these tasks can be performed via both the Azure Portal and command-line tools, and provide links to relevant CLI documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific instructions or examples, but it also does not include any Windows- or PowerShell-specific commands, tools, or patterns. However, there is a lack of explicit Linux (or cross-platform) command-line examples or instructions, which could leave Linux users unsure about how to perform certain actions, such as loading sample data or interacting with the API.

Recommendations:

Add explicit instructions or examples for loading sample data using cross-platform tools such as curl or HTTPie, with command-line snippets that work on both Windows and Linux.
If any sample .http files are intended for use with a specific tool (e.g., VS Code REST Client, Postman), clarify this and provide cross-platform usage notes.
Include a section or callout noting that all examples are platform-agnostic and can be run from any OS with appropriate tools.
If there are any scripts or automation steps, provide both PowerShell and Bash (or generic shell) equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides navigation instructions that are platform-neutral in this excerpt, but it lacks any mention of Linux-specific considerations or alternative interfaces (such as CLI or configuration files) that Linux users might use, especially since App Service can be managed via both the Azure Portal and command-line tools on different platforms.

Recommendations:

Add equivalent instructions for managing configuration using the Azure CLI, which is cross-platform and commonly used on Linux.
Mention that the Azure Portal UI is the same across platforms, but provide links or notes for users who prefer command-line or automation approaches.
If there are any Linux-specific configuration differences, highlight them or provide a link to relevant documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only a C# example for accessing DICOM Change Feed logs, with no mention of Linux-specific tools, patterns, or alternative languages/platforms (such as Python or Bash) that are commonly used on Linux. There is no explicit Windows bias in terms of tools or PowerShell, but the lack of Linux-oriented examples or cross-platform guidance may disadvantage Linux users.

Recommendations:

Add code examples in additional languages popular on Linux, such as Python (using requests or pydicom) or Bash (using curl).
Explicitly mention that the REST API can be accessed from any platform, and provide generic HTTP request examples.
Include instructions or notes on how to run the C# example on Linux (e.g., using .NET Core/SDK on Linux).
Where possible, provide parity in tooling and setup instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes managing Azure resource groups using the Azure portal, with no mention of command-line tools or scripts. There are no examples or references to Windows-specific tools (such as PowerShell), but there is also a complete absence of CLI-based instructions (e.g., Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission results in a bias by not providing parity for users who prefer or require non-portal, scriptable, or Linux-friendly workflows.

Recommendations:

Add parallel instructions for managing resource groups using the Azure CLI (az group ...) with example commands.
Include both Windows (PowerShell) and Linux/macOS (Bash) command-line examples where appropriate.
Reference cross-platform tools (such as Azure CLI) early and equally alongside portal-based instructions.
Provide links to documentation for managing resource groups via command-line interfaces and automation scripts.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a generic dialog interface without specifying platform-specific steps. However, it does not mention or provide examples for Linux environments, such as setting environment variables via the command line or configuration files, which are common on Linux.

Recommendations:

Add Linux-specific instructions, such as how to set SCM_DO_BUILD_DURING_DEPLOYMENT using the export command in bash or by editing configuration files.
Include examples for both Windows (e.g., using set in Command Prompt or PowerShell) and Linux (e.g., using export or editing .env files).
Clarify if the dialog is available on all platforms or provide alternative methods for platforms where it is not.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a generic dialog interface without specifying any platform-specific tools. However, it does not mention or provide examples for setting this configuration via Linux command-line tools or scripts, which may be relevant for cross-platform users.

Recommendations:

Add examples for setting SCM_DO_BUILD_DURING_DEPLOYMENT using Linux shell commands (e.g., export, echo, or editing configuration files).
Clarify whether the dialog is available on all platforms or provide alternative instructions for Linux users.
Include parity in documentation by showing both Windows (e.g., PowerShell, GUI) and Linux (e.g., Bash, CLI) methods for setting environment variables.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally uses cross-platform tools (Git, Node.js, npm, Azure CLI) and avoids OS-specific commands. However, in Step 6, the instructions for uploading static files explicitly mention 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not mentioning Linux or macOS shells by name. No Linux- or macOS-specific examples or shell references are provided, and there is no explicit guidance for non-Windows users.

Recommendations:

Use neutral, cross-platform language when referring to command shells. For example: 'Open a terminal or command shell (such as Windows Command Prompt, PowerShell, Bash, or Terminal on macOS/Linux)'.
Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS, and provide example shell commands for both Windows and Bash (Linux/macOS) where relevant.
If there are any OS-specific considerations (such as path separators or environment variable syntax), document them for both Windows and Linux/macOS.
Consider adding a short note in the prerequisites or first command section clarifying that all commands are cross-platform unless otherwise noted.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for obtaining Git credentials but does not include any platform-specific examples or commands. However, it implicitly assumes a generic workflow and does not mention Linux or provide Linux-specific guidance, which may leave Linux users uncertain about steps such as credential usage in their environment.

Recommendations:

Add explicit instructions or examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash) for cloning and pushing to the repository.
Clarify that the instructions are platform-agnostic if that is the intent, or provide side-by-side examples for each major platform.
Mention any differences in credential handling or command syntax between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides generic instructions for accessing deployment credentials but does not include any platform-specific examples. There are no explicit Windows or Linux command-line examples, but the lack of Linux (or any OS-specific) guidance may leave Linux users without clear next steps for using these credentials.

Recommendations:

Add explicit examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux (e.g., using Bash) to demonstrate how to use the credentials when pushing code.
Include sample git commands for both platforms, showing how to input the credentials.
Clarify any platform-specific differences in credential storage or usage, if applicable.
Ensure parity in the order and depth of examples for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation describes accessing SSH via the Azure portal's web interface, which is platform-agnostic. However, it does not provide any command-line examples (e.g., using native SSH clients on Linux or Windows), nor does it mention platform-specific tools or workflows. There is a lack of parity for users who may prefer or require CLI-based access, especially common in Linux environments.

Recommendations:

Add examples for accessing the App Service container via SSH from a terminal using the standard ssh command, including any prerequisites or authentication steps.
Clarify whether the web-based SSH interface works identically across all platforms, and mention any platform-specific considerations if they exist.
If there are PowerShell or Windows-specific methods, ensure equivalent Linux (bash) examples are provided.
Explicitly mention that the instructions are platform-agnostic if that is the case, or provide links to platform-specific guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also does not mention or illustrate Linux tools, commands, or workflows. This omission may lead to a lack of clarity for Linux users if platform-specific steps are required.

Recommendations:

If there are platform-specific steps, provide examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash).
Explicitly state if the instructions are platform-agnostic.
Include screenshots or command-line snippets for both Windows and Linux environments if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific instructions or examples, but it also does not mention or illustrate any Linux-specific workflows, tools, or commands. There is no explicit Windows bias, but the absence of Linux (or macOS) examples or guidance could be seen as a lack of parity.

Recommendations:

Add explicit instructions or notes for Linux/macOS users, such as how to use the credentials with common Git clients on those platforms.
Include example Git commands for both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash).
Mention any platform-specific considerations, such as where to store credentials securely on different operating systems.
Clarify that the instructions are cross-platform if that is the case, or provide links to platform-specific documentation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally presents information in a cross-platform manner, but in the section 'Configure name resolution behavior', the property table lists 'Windows default value' before 'Linux default value', which may subtly prioritize Windows. There are no explicit Windows-only examples, tools, or commands; all configuration is shown using the Azure CLI, which is cross-platform. There are no missing Linux examples, and Linux-specific limitations or features are mentioned where relevant.

Recommendations:

In property tables or comparative sections, consider listing Linux and Windows in alphabetical order or using neutral phrasing (e.g., 'Default value (Windows)', 'Default value (Linux)') to avoid subtle prioritization.
If there are platform-specific behaviors or limitations, ensure both Windows and Linux are discussed with equal prominence and detail.
Continue using cross-platform tools like Azure CLI for examples, and avoid introducing Windows-specific tools (e.g., PowerShell) unless Linux equivalents are also provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific troubleshooting commands or examples, but in the one instance where it describes exporting a certificate, it only mentions using a browser to export the certificate in Base-64 encoded CER format. There are no instructions or examples for performing this task using command-line tools, such as PowerShell (Windows) or OpenSSL (Linux), nor is there any mention of Linux-specific tools or workflows. This omission may disadvantage Linux users who commonly use OpenSSL or similar utilities for certificate management.

Recommendations:

Add step-by-step instructions for exporting the ILB certificate using OpenSSL on Linux, e.g., using 'openssl s_client' to retrieve the certificate and 'openssl x509' to convert it to Base-64 encoded CER format.
If providing browser-based export instructions, clarify that this method is OS-agnostic, or provide alternative CLI-based methods for both Windows (PowerShell) and Linux (OpenSSL).
Include explicit examples for both Windows and Linux environments when describing certificate retrieval and upload processes.
Review the documentation for other potential OS-specific assumptions and ensure parity in troubleshooting steps for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids OS-specific instructions, but in the section on HTTP-to-HTTPS redirection, the PowerShell (Windows-centric) example is listed before the Azure CLI (cross-platform) example. This ordering subtly prioritizes Windows tooling. However, Linux parity is largely maintained elsewhere, and CLI examples are present.

Recommendations:

List Azure CLI (cross-platform) instructions before PowerShell (Windows-centric) instructions to avoid implying a Windows-first workflow.
Ensure that all referenced guides (such as those for redirection and external site redirection) provide both PowerShell and CLI examples, and that both are equally visible.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
Consider adding Bash or shell script examples where relevant, especially in sections that reference automation or scripting.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific troubleshooting steps or examples, but it also does not mention or demonstrate any Linux tools, commands, or workflows. This omission may leave Linux users without clear guidance, especially if there are platform-specific considerations for Azure Import/Export operations.

Recommendations:

Add explicit troubleshooting steps for both Windows and Linux environments, including relevant command-line examples for each.
Mention any differences in handling journal files, drive preparation, or error recovery on Linux systems.
Reference Linux-compatible tools (such as dd, lsblk, or fdisk) where appropriate, alongside any Windows tools.
Include links to platform-specific guides or documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions PowerShell cmdlets before Azure CLI and REST API when describing programmatic scaling, which may suggest a Windows-first bias. However, no explicit PowerShell-only examples or exclusive references to Windows tools are present, and Azure CLI (cross-platform) is mentioned. There are no command-line examples at all, so Linux parity is not directly compromised, but the ordering could imply preference.

Recommendations:

When listing programmatic options, mention Azure CLI before or alongside PowerShell to reflect cross-platform parity (e.g., 'using Azure CLI, PowerShell cmdlets, or REST API').
Provide explicit examples for both Azure CLI and PowerShell where possible, ensuring Linux users have clear guidance.
Avoid language that prioritizes Windows tools unless there is a technical reason to do so.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions only for disabling Azure Automanage via the Azure portal and does not include any command-line examples or scripts. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but there is also no coverage of Linux CLI tools or cross-platform automation methods. The absence of CLI or automation examples (such as Azure CLI, which is cross-platform) may disadvantage Linux users who often prefer or require non-GUI workflows.

Recommendations:

Add step-by-step instructions for disabling Automanage using the Azure CLI, which works on both Windows and Linux.
If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided.
Explicitly mention that the portal method is platform-agnostic, but highlight automation options for users who may not use the GUI.
Include links to relevant Azure CLI documentation for managing Automanage profiles and VM onboarding/offboarding.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides only Azure Portal (GUI) instructions for delegating a subnet to Azure NetApp Files and does not include any command-line examples. There is no explicit Windows bias (such as PowerShell or Windows tool references), but there is a lack of parity for users who prefer or require CLI-based workflows, which are common in Linux environments.

Recommendations:

Add Azure CLI examples for subnet delegation, as Azure CLI is cross-platform and widely used on Linux.
If relevant, include Azure PowerShell examples as well, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
Explicitly mention that the steps can be performed via CLI or automation tools, and provide links or references to relevant documentation for both Linux and Windows users.
Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions in the order: Windows Command Prompt (setx), PowerShell, then macOS/Linux (export). This ordering prioritizes Windows users by listing their instructions first, which may subtly reinforce a Windows-centric perspective. However, all major platforms are represented and no platform is omitted.

Recommendations:

Rotate or randomize the order of platform-specific instructions, or list Linux/macOS first to balance exposure.
Consider grouping all environment variable commands in a table with columns for each OS/shell, so no platform is visually prioritized.
Explicitly state that the instructions apply equally to all platforms, and that the order does not imply preference.
Where possible, use cross-platform commands or tools, or highlight them if available.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes recovery and purge operations using the Azure Portal UI, with no mention of command-line tools or scripts. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, nor are there any PowerShell examples. However, the absence of CLI examples means Linux and macOS users are not provided with parity for automation or non-GUI workflows.

Recommendations:

Add Azure CLI examples for all major operations (setting retention policy, enabling purge protection, listing/recovering/purging stores) to ensure Linux and macOS users can follow along.
If PowerShell examples are added, ensure Azure CLI equivalents are always included and presented either first or side-by-side.
Explicitly mention that all operations can be performed via CLI and provide links to relevant Azure CLI documentation.
Consider including bash script snippets for common automation scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to modify a Compute Fleet using the Azure portal UI, without providing any command-line examples or automation guidance. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or PowerShell instructions are given, which may disadvantage users who prefer or require command-line or scriptable solutions, especially on Linux.

Recommendations:

Add step-by-step instructions for modifying Compute Fleets using the Azure CLI, including example commands for both target capacity and VM size changes.
Include Bash script examples for automating common modification tasks.
If relevant, provide PowerShell examples as well, but ensure they are presented alongside (not before) Linux-friendly CLI/Bash examples.
Clearly indicate which methods are cross-platform and highlight any differences in behavior or prerequisites between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the macOS/Linux equivalent, but does include all major platforms. No Linux examples or tools are missing, and the rest of the tutorial uses cross-platform Node.js and bash commands.

Recommendations:

Present platform-specific instructions in parallel (side-by-side or in a table), rather than listing Windows first.
Consider listing Linux/macOS instructions before Windows, or at least alternating the order in different tutorials to avoid implicit prioritization.
Explicitly state that all platforms are supported and tested, to reinforce parity.
Where possible, use cross-platform commands (e.g., via npm scripts or dotenv files) to minimize platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. All other code and instructions are cross-platform and do not show a Windows or PowerShell bias.

Recommendations:

Present Linux/macOS and Windows instructions in parallel (side-by-side or in a tabbed format) rather than listing Windows first.
Consider listing Linux/macOS commands first, as Node.js development is common on those platforms.
Explicitly state that all commands and code samples are cross-platform, except where noted.
Where possible, use platform-agnostic instructions or provide clear parity for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation refers to running npm install from a 'Node command prompt', which is a Windows-centric term and may imply a Windows-first approach. However, the rest of the instructions and code samples are cross-platform and do not show explicit bias towards Windows or PowerShell. There are no Windows-only tools, commands, or examples, but the terminology could be more inclusive.

Recommendations:

Replace 'Node command prompt' with 'terminal' or 'command line' to ensure the instructions are clearly applicable to both Windows and Linux users.
Explicitly mention that the instructions and code samples work on all major platforms (Windows, Linux, macOS).
If there are any platform-specific considerations (such as environment variable syntax), add notes or examples for both Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation provides language-specific examples for C#, JavaScript, Python, PowerShell, and Java. While PowerShell is included as a first-class language, there is no explicit Windows bias in terms of tools, shell commands, or patterns that would exclude or disadvantage Linux users. However, the inclusion of PowerShell as a primary example language (rather than, for example, Bash or a Linux-native shell) may be seen as a subtle bias toward Windows environments, since PowerShell is more commonly associated with Windows, even though it is now cross-platform.

Recommendations:

Clarify that PowerShell examples are cross-platform and not Windows-specific, or provide equivalent Bash/shell script examples where relevant.
Explicitly mention that all code examples (including PowerShell) are intended to work on both Windows and Linux environments, or provide notes about any platform-specific considerations.
If possible, add a Bash or Linux shell scripting tab for parity with PowerShell, especially if scripting is a common use case for Durable Functions.
Continue to ensure that all tooling and patterns described are platform-agnostic, and avoid references to Windows-only tools or workflows.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally provides cross-platform instructions, but in the 'Prerequisites' and 'Configure an environment variable' sections, Windows-specific instructions (Windows command prompt and PowerShell) are listed before Linux/macOS equivalents. The Node.js installation link also prioritizes Windows and WSL. However, Linux/macOS instructions are present and complete, and there are no sections that are Windows-only or missing Linux examples.

Recommendations:

Present platform-specific instructions in a neutral or rotating order (e.g., start with Linux/macOS in some sections, or use tabbed content with no clear priority).
In the 'Prerequisites' section, provide a more balanced Node.js installation reference, such as linking to the official Node.js site or including Linux/macOS installation resources alongside Windows.
Consider using tabbed or side-by-side layouts for environment variable setup, so no platform is visually prioritized.
Explicitly state that all examples are cross-platform unless otherwise noted, to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only C# code samples and file storage patterns that implicitly assume a Windows or .NET environment, with no mention of Linux-specific considerations, tools, or code examples. There are no references to Linux shell commands, Linux file paths, or cross-platform SDK usage. The use of .NET APIs for file access and environment variables is not explained for Linux users, and there is no guidance on adapting the examples for Linux-based IoT devices.

Recommendations:

Provide equivalent code samples in a cross-platform language such as Python or C, or explicitly show how the C#/.NET code can be run on Linux (e.g., using .NET Core on Linux).
Include Linux-specific instructions for setting environment variables and file paths (e.g., using $HOME or /var/lib for data directories).
Mention and demonstrate how to run the provided code on both Windows and Linux, including any prerequisites (such as installing .NET on Linux).
Add shell script (Bash) examples for provisioning and monitoring tasks where appropriate.
Clarify that the patterns and APIs used are cross-platform, or provide alternatives for Linux-only environments.
Reference Linux-native tools (such as systemd for background work, or Linux logging mechanisms) where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of how to set the AzureWebJobsStorage app setting from Linux environments (e.g., using Azure CLI or bash), which could be helpful for non-Windows users.

Recommendations:

Add explicit examples for setting the AzureWebJobsStorage app setting using cross-platform tools such as Azure CLI or bash scripts.
If relevant, mention both Windows (e.g., PowerShell, Azure Portal) and Linux (e.g., bash, Azure CLI) methods for configuring app settings.
Ensure that links to further documentation include Linux-friendly instructions or note any platform-specific differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of Linux or cross-platform considerations. This could be seen as a missed opportunity to clarify parity or platform-specific behavior.

Recommendations:

Explicitly state if the instructions apply equally to both Windows and Linux platforms.
If there are platform-specific differences in the 'Save' operation or UI, provide examples or notes for both Windows and Linux users.
Include screenshots or clarifications if the interface differs between platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation references the VS Code Output window for viewing logs but does not mention alternative methods or tools for viewing logs on Linux or other platforms outside of VS Code.

Recommendations:

Include instructions or examples for viewing logs using platform-agnostic tools (e.g., terminal commands like tail or cat for log files).
Mention that logs can also be accessed via standard output or log files, and provide examples for Linux/macOS environments.
Clarify that while VS Code Output is one option, users on other platforms or using different editors can use alternative methods.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also does not mention Linux or cross-platform workflows. There are no Windows-specific tools or commands, but the lack of Linux (or general cross-platform) command-line examples or instructions may leave Linux users without clear guidance.

Recommendations:

Add explicit examples for setting the FUNCTIONS_WORKER_RUNTIME variable using both Windows (e.g., PowerShell, Azure CLI on Windows) and Linux (e.g., Bash, Azure CLI on Linux).
Include notes or sections that clarify how to update application settings on different platforms, such as Linux, macOS, and Windows.
Provide sample commands for editing local.settings.json using common cross-platform editors or command-line tools.
Ensure parity in troubleshooting steps and instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation describes both Windows and Linux/container architectures for the authentication and authorization module, but the Windows (IIS module) architecture is presented first and in more detail. There are no explicit PowerShell or Windows-only command-line examples, and the only CLI examples use the cross-platform 'az' CLI. No Windows-specific tools or patterns are promoted elsewhere, and Linux/container deployment is covered, but always after Windows.

Recommendations:

Present Linux/container architecture before or alongside Windows, or use a neutral ordering (e.g., 'On Windows...' and 'On Linux/containers...').
Ensure parity in technical detail for both Windows and Linux/container sections.
If possible, provide explicit Linux-native examples or references (e.g., mention that the az CLI commands work on all platforms).
Consider adding a table or diagram comparing Windows and Linux/container behaviors side by side for clarity and neutrality.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation provides language-specific examples for C#, Java, JavaScript, TypeScript, PowerShell, and Python. While PowerShell is included as a first-class language alongside others, there is no evidence of exclusive Windows bias: there are no Windows-only tools, no Windows-first ordering, and no missing Linux equivalents. However, the inclusion of PowerShell as a primary example language (rather than, for example, Bash or shell scripting) may be seen as a mild bias towards Windows environments, since PowerShell is most commonly associated with Windows, even though it is now cross-platform.

Recommendations:

Consider adding Bash or shell scripting examples, especially in sections where PowerShell is used, to provide parity for Linux users.
Explicitly note that PowerShell Core is cross-platform, or provide guidance for Linux/macOS users where PowerShell is referenced.
Ensure that any references to tools, file paths, or environment variables are platform-agnostic or provide both Windows and Linux/macOS variants.
If possible, include a section or note on how to use the binding in a Linux environment, or link to Linux-specific setup guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or commands, but it also lacks any practical configuration examples for either Windows or Linux. This omission can be considered a subtle bias, as users on Linux (or any OS) do not receive guidance on how to configure their backend servers for SSE, such as example commands or configuration snippets for popular web servers (e.g., Nginx, Apache, IIS). The absence of Linux-specific examples is a missed opportunity for parity.

Recommendations:

Add practical configuration examples for both Linux and Windows environments. For Linux, include sample Nginx and Apache configurations showing the required headers for SSE.
If mentioning Windows/IIS, ensure Linux examples are provided first or alongside.
Include example shell commands (e.g., curl) for testing SSE endpoints on both Linux and Windows.
Explicitly mention that the guidance applies to all backend platforms and provide links or references to platform-specific documentation where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides code samples for C#, JavaScript, and Python, with explicit notes that PowerShell and Java samples are pending. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the Python examples assume a generic cross-platform environment but do not provide explicit Linux-specific instructions or terminal commands. There are no references to Windows-only tools or patterns, but the lack of Linux-specific guidance (such as bash commands or Linux environment notes) may leave Linux users without full parity.

Recommendations:

Add explicit Linux shell/terminal instructions where relevant, such as for creating folders or deploying functions.
Include notes or examples for running and testing Azure Functions on Linux (e.g., using Azure Functions Core Tools in bash).
Ensure parity in sample completeness for all supported languages, including PowerShell and Java, and clarify if any samples are Windows-only.
If any steps differ between Windows and Linux (such as file paths or environment variable syntax), document both variants.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page only mentions the retirement of Azure Automation DSC for Linux, without providing any examples, tools, or migration guidance for Linux users. There is no mention of Windows equivalents, but the lack of Linux-specific guidance or alternatives creates a gap for Linux users.

Recommendations:

Provide clear migration steps or alternatives for Linux users affected by the retirement.
Include examples or references for configuring guest configuration or policy management on Linux.
Ensure parity by mentioning both Windows and Linux options for configuration management where relevant.
Link to documentation or tools that help Linux users transition to supported solutions.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation is generally cross-platform and browser/JavaScript focused, but there is a subtle Windows bias in the example proxy service implementation, which uses an .ashx handler (ASP.NET), a Windows/IIS technology. There are no explicit PowerShell or Windows command-line examples, and no overt prioritization of Windows tools or patterns elsewhere. However, the proxy example may be confusing or less directly applicable to Linux or non-Windows developers.

Recommendations:

Provide proxy service examples using cross-platform technologies (e.g., Node.js/Express, Python/Flask, or a generic HTTP server) alongside or instead of .ashx/ASP.NET.
Clarify that the proxy service can be implemented in any web technology, and provide links or code snippets for Linux-friendly implementations.
Avoid referencing technology-specific file extensions (like .ashx) without alternatives or explanation.
Explicitly state that all JavaScript examples are platform-agnostic and can be used on any OS with a compatible browser.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides instructions and examples exclusively through the Azure Portal UI, with no mention of platform-specific tools or command-line interfaces. However, it lacks any CLI-based examples (such as Azure CLI, Bash, or PowerShell), which could be important for users on Linux or macOS who may prefer or require non-GUI workflows. There is no explicit Windows bias in terms of tools or order, but the absence of Linux-friendly (CLI) examples may implicitly disadvantage non-Windows users.

Recommendations:

Add Azure CLI examples for creating and managing test profiles, running load tests, and viewing results, ensuring these examples work cross-platform (Linux, macOS, Windows).
If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided and presented in parallel.
Explicitly mention that all portal-based steps are platform-agnostic, and provide links to CLI documentation for users who prefer or require command-line workflows.
Consider including a section on automating performance optimization using scripts, with examples for both Bash (Linux/macOS) and PowerShell (Windows).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not show explicit Windows bias in terms of command-line examples, tools, or instructions, but it also does not provide any platform-specific guidance or examples. There are no references to Windows-only tools (such as PowerShell), nor are there instructions or screenshots that are specific to Windows. However, the documentation lacks any mention of Linux or cross-platform considerations, such as file path formats, agent OS compatibility, or differences in running pipelines on Linux versus Windows agents. This absence may lead to implicit bias by not addressing the needs of Linux users.

Recommendations:

Add a section clarifying that the Azure Pipelines agent and the App Configuration Import task are supported on both Windows and Linux agents, and note any OS-specific considerations.
Include examples or notes about specifying file paths in a cross-platform way (e.g., using forward slashes for Linux, backslashes for Windows, or using environment variables).
If there are any differences in behavior or requirements between Windows and Linux agents (such as permissions, file system case sensitivity, or Node.js installation), document these explicitly.
Provide at least one example or screenshot showing the task being configured or run on a Linux agent, or clarify that the UI and steps are the same across platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids platform-specific bias in its examples and explanations, focusing on ARM template JSON syntax. However, in the 'Copy limits' section, when discussing support for zero count, Azure PowerShell is listed before Azure CLI, and the 'Next steps' section links only to a PowerShell deployment guide, not to an Azure CLI or cross-platform deployment guide. This ordering and linking subtly prioritize Windows/PowerShell over Linux/Azure CLI.

Recommendations:

In the 'Copy limits' section, list Azure CLI before Azure PowerShell, or mention both together to avoid implying a platform preference.
In the 'Next steps' section, add a link to a tutorial or guide for deploying ARM templates with Azure CLI, ensuring Linux users have clear guidance.
Wherever deployment tooling is mentioned, ensure parity by referencing both Azure CLI and PowerShell, or by providing a neutral/cross-platform deployment guide.
Consider adding a short note clarifying that both Azure CLI and PowerShell are cross-platform, and that all examples are applicable regardless of operating system.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation references both Azure CLI and Azure PowerShell for deploying Bicep files, but lists Azure PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). No explicit Linux or Bash examples are provided, but the content is otherwise platform-neutral. There are no PowerShell-specific code samples or Windows-only tools mentioned, but the ordering subtly prioritizes Windows tooling.

Recommendations:

List Azure CLI before Azure PowerShell when mentioning deployment tools, as Azure CLI is cross-platform and more inclusive for Linux users.
Explicitly mention that Azure CLI works on Linux, macOS, and Windows to reinforce cross-platform support.
Consider providing example deployment commands for both Azure CLI (bash) and Azure PowerShell, or at least for Azure CLI.
Avoid implying a Windows-first workflow by balancing references to tools and environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Azure PowerShell before Azure CLI when discussing supported versions for zero-count copy loops. This ordering may subtly prioritize Windows tooling, as PowerShell is more closely associated with Windows environments, even though Azure CLI is cross-platform. No explicit PowerShell or Windows-only examples are given, and all code samples are in ARM template JSON, which is platform-agnostic.

Recommendations:

When listing supported tooling (e.g., Azure PowerShell, Azure CLI, REST API), alternate or randomize the order, or list Azure CLI first to reflect its cross-platform nature.
Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to reinforce cross-platform parity.
Where possible, provide example commands for both Azure CLI and PowerShell, or at least mention that all examples are platform-agnostic.
Consider including a brief note or table clarifying the cross-platform availability of all mentioned tools.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for retrieving supported locations for a resource type. However, the PowerShell example is presented first, which may suggest a subtle preference for Windows tooling. There are no missing Linux examples, and both command-line interfaces are cross-platform, but the ordering could be perceived as Windows-first.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples throughout the documentation to avoid a consistent Windows-first impression.
Explicitly mention that both Azure CLI and Azure PowerShell are cross-platform, and provide links to installation instructions for each on Windows, Linux, and macOS.
Where possible, include Bash shell examples (for scripting) alongside PowerShell, especially for common tasks.
Consider using tabbed sections labeled 'Azure CLI (cross-platform)' and 'PowerShell' to reinforce parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides platform-specific instructions for setting environment variables, listing Windows first, followed by Linux and macOS. All other code examples are Python and cross-platform, and there are no PowerShell-specific or Windows-only tools used. However, the ordering of Windows instructions before Linux and macOS may subtly suggest a Windows-first perspective.

Recommendations:

Rotate the order of platform-specific instructions so that Linux or macOS is sometimes listed first, or use a neutral order (e.g., alphabetical: Linux, macOS, Windows).
Consider using tabbed or collapsible sections for platform-specific instructions, with no default selected or with the most common developer platform (often Linux for Python) first.
Explicitly state that all Python code examples are cross-platform and work equally on Windows, Linux, and macOS.
Where possible, provide parity in notes and troubleshooting tips for all platforms (e.g., mention restarting the terminal/editor for all OSes, not just Windows/Visual Studio).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation references 'Azure CLI or Azure PowerShell' as the means to run examples, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and links to a Visual Studio Code quickstart for deployment. While Azure CLI is cross-platform, the mention of Azure PowerShell and Visual Studio Code (which is cross-platform but often associated with Windows) before any explicit mention of Linux-native workflows or tools may suggest a subtle Windows-first bias. However, the Bicep code examples themselves are platform-agnostic, and there are no explicit PowerShell scripts, Windows-only tools, or missing Linux examples.

Recommendations:

Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
If mentioning Azure PowerShell, also mention that it is available cross-platform, or provide a Linux-native alternative (such as Bash scripts using Azure CLI).
Consider providing explicit example commands for deploying Bicep files using Azure CLI on Linux (e.g., Bash shell), not just referencing the Visual Studio Code workflow.
Add a note or section on running Bicep deployments from Linux environments, possibly linking to relevant documentation.
Ensure that any future examples or tooling references are balanced between Windows and Linux workflows.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild 'windows_first' bias by listing the Windows quickstart link before the Linux equivalent in the prerequisites. However, the rest of the tutorial is platform-neutral, with no PowerShell- or Windows-specific commands, tools, or screenshots. All command-line examples use cross-platform commands (iotedge), and both Linux and Windows are acknowledged as supported platforms.

Recommendations:

List Linux and Windows quickstart links in the same order or in parallel (e.g., 'for Linux or Windows devices'), or list Linux first to avoid implicit prioritization.
Where possible, provide explicit notes or links for both Linux and Windows users in setup and troubleshooting sections.
Continue to use cross-platform tools and commands, and avoid platform-specific screenshots or instructions unless both are provided.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page presents the Azure portal (a GUI, often associated with Windows environments) as the primary method for role assignment, with Azure PowerShell listed before Azure CLI in the 'To learn more' section. This ordering may subtly prioritize Windows-centric tools and workflows over cross-platform or Linux-native options.

Recommendations:

When listing command-line tools, mention Azure CLI before or alongside Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Include explicit examples or references for both Azure PowerShell and Azure CLI in the main instructions, not just in the 'To learn more' section.
Clarify that the Azure portal and all listed tools are cross-platform where applicable, to avoid the impression that the instructions are Windows-specific.
If screenshots or step-by-step instructions are provided for PowerShell or the portal, consider also providing equivalent CLI or Linux terminal examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or scripting). While this avoids explicit Windows or PowerShell bias, it also omits Linux-friendly approaches, such as using the Azure CLI, which is cross-platform and preferred by many Linux users. The lack of CLI or scripting examples can be seen as a bias of omission, as it does not address the needs of users who prefer or require non-GUI, scriptable, or automated workflows—common in Linux environments.

Recommendations:

Add Azure CLI examples for exporting, editing, and redeploying Event Grid custom topics, covering all major steps (export, modify, deploy, delete).
Include sample commands for deleting resources and resource groups using Azure CLI.
Explicitly mention that all steps can be performed via the Azure CLI, and provide links to relevant CLI documentation.
If PowerShell examples are ever added, ensure Azure CLI equivalents are always provided and presented with equal prominence.
Consider adding a section or callout for automation/scripting approaches, highlighting cross-platform tools.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but presents the Windows instructions first. All other examples are cross-platform (Python code), and there is no exclusive use of Windows tools or missing Linux examples.

Recommendations:

Present environment setup instructions in a neutral or rotating order (e.g., Linux first, or alphabetical order) to avoid implicit prioritization of Windows.
Explicitly state that all Python code examples are cross-platform and work on Windows, Linux, and macOS.
Ensure parity in any future sections that might introduce platform-specific tooling or shell commands.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or instructions, but it also does not mention or reference any Windows-specific tools, commands, or patterns. However, there is a lack of explicit Linux (or cross-platform) guidance or examples, which may leave Linux administrators without clear instructions for their environment.

Recommendations:

Add explicit instructions or references for both Windows and Linux environments where relevant, such as configuring VPN or ExpressRoute connections from on-premises Linux systems.
Include links to Azure documentation that covers cross-platform (Windows and Linux) connectivity setup.
If any command-line examples are added in the future, ensure parity by providing both PowerShell (Windows) and Bash/CLI (Linux) examples.
Clarify in the prerequisites or notes that the guidance applies to both Windows and Linux on-premises environments, or provide separate sections if steps differ.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents PowerShell (commonly associated with Windows) examples before Azure CLI examples when demonstrating how to get available locations. Both tools are covered, and the CLI example is present, but the ordering may subtly prioritize Windows users.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples across documentation pages, or present Azure CLI examples first, as it is cross-platform.
Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS to avoid implying platform exclusivity.
Where possible, provide Bash shell examples (for Linux/macOS) in addition to CLI commands, especially for scripting scenarios.
Add a brief note clarifying that Azure CLI commands work natively on Linux/macOS terminals.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids OS-specific bias, presenting most steps as Azure Portal UI instructions and providing both PowerShell and Bash examples for command-line operations. However, in the 'Verify a custom domain' section, the PowerShell (Windows) example is presented before the Bash (Linux) example, which is a subtle instance of 'windows_first' ordering. There are no exclusive Windows tools, missing Linux examples, or PowerShell-heavy sections.

Recommendations:

Present Bash (Linux) and PowerShell (Windows) examples in parallel tabs or alternate their order across documentation to avoid implicit prioritization.
When showing command-line examples, consider listing Bash first or providing a neutral ordering (e.g., alphabetical or based on global usage statistics).
Continue to ensure that all command-line examples are available for both Windows and Linux environments.
Explicitly mention cross-platform compatibility where relevant, especially for tools like curl.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a mild 'windows_first' bias. In the prerequisites section, the link to creating an Azure Communication Services resource uses a URL parameter '?tabs=windows', suggesting Windows as the default or primary platform. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the content (Java, Maven, terminal usage) is generally platform-agnostic.

Recommendations:

Ensure that links to Azure documentation use neutral or cross-platform tabs by default (e.g., '?tabs=linux' or no tab parameter).
Explicitly mention that the steps work on both Windows and Linux, or provide notes for any platform-specific differences.
If there are platform-specific quickstart pivots (e.g., for creating resources), provide both Windows and Linux options or clarify that the instructions are cross-platform.
Review all linked quickstarts to ensure Linux parity and avoid defaulting to Windows in tabbed instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or commands, but it implicitly assumes the use of generic DNS server management without mentioning or providing examples for either Windows (such as Windows Server DNS or PowerShell) or Linux (such as BIND or Linux CLI tools). However, it does reference 'on-premises DNS server' and 'conditional forwarder'—terms commonly associated with Windows DNS—but does not clarify or provide parity for Linux-based DNS solutions. There are no explicit Windows-only tools or commands, but the lack of Linux-specific guidance or examples constitutes a subtle bias.

Recommendations:

Explicitly mention both Windows and Linux DNS server options when referring to on-premises DNS servers (e.g., Windows Server DNS, BIND, dnsmasq).
Provide example configurations or links for setting up conditional forwarders in both Windows DNS Manager and popular Linux DNS servers (such as BIND).
Clarify that the guidance applies to both Windows and Linux environments, and add OS-agnostic or dual-platform instructions where possible.
Include sample commands or configuration snippets for Linux-based DNS servers to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation does not explicitly show Windows bias in terms of tools, PowerShell, or Windows-specific commands. However, there is a subtle 'windows_first' bias: the default time zone in several examples is 'Pacific Standard Time', which is a Windows time zone identifier and not a standard IANA time zone (used in Linux/Unix environments). Additionally, the documentation does not clarify time zone compatibility or provide guidance for Linux users who may expect IANA time zones. No explicit Linux examples or parity notes are present.

Recommendations:

Clarify in the documentation whether the 'timeZone' property accepts IANA time zone identifiers (e.g., 'America/Los_Angeles') or only Windows time zone IDs (e.g., 'Pacific Standard Time').
Add a note or table mapping common Windows time zones to IANA equivalents for cross-platform clarity.
Provide examples using both Windows and IANA time zone formats, if supported.
Explicitly state any platform limitations or requirements for time zone values.
Consider including a Linux-focused example or guidance for users managing backup policies from Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally provides cross-platform instructions, but in the section on setting environment variables for the connection string, the Windows (cmd) example is presented after the Linux/macOS (bash) example. No other significant Windows bias is present: all installation and usage instructions use cross-platform Node.js/npm commands, and there is no exclusive mention of Windows tools or PowerShell.

Recommendations:

Ensure that all platform-specific instructions are presented with equal prominence. Consider using tabbed sections with consistent ordering (e.g., Linux/macOS first, Windows second, or vice versa) and clear labeling.
Where possible, provide PowerShell examples for Windows users in addition to cmd, as PowerShell is increasingly common.
Explicitly state that all commands are cross-platform unless otherwise noted, to reassure Linux users.
Audit future documentation for any accidental omission of Linux or macOS instructions, especially for environment variable setup and tool usage.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on .NET SDK usage, with all code examples in C# and installation instructions using the dotnet CLI. There are no explicit references to Windows-specific tools or PowerShell, nor are there any mentions of Windows or Linux platforms. However, there is a lack of Linux-specific guidance or examples, such as shell commands or notes on cross-platform usage, which may implicitly bias the documentation towards Windows users who are more likely to use .NET and related tooling.

Recommendations:

Add explicit notes clarifying that the .NET SDK and dotnet CLI are cross-platform and can be used on Linux, macOS, and Windows.
Include example commands for installing the .NET SDK on Linux (e.g., using apt, yum, or snap).
Provide sample shell commands (bash/zsh) for common tasks, such as setting environment variables or running the application, to complement the C# code.
Mention any platform-specific considerations, if applicable, for Linux users (e.g., file permissions, dependency installation).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains OS neutrality by focusing on the Azure Portal UI for backup operations, which is cross-platform. However, in the 'Install the VM agent' section, instructions for Windows appear first, with more explicit step-by-step guidance and direct download links, while Linux instructions are less detailed and refer users to external package repositories. This ordering and level of detail indicate a subtle 'windows_first' bias.

Recommendations:

Present Linux and Windows instructions in parallel or alternate their order in different sections to avoid always listing Windows first.
Provide equally detailed, step-by-step instructions for installing the Azure Linux agent, including example commands for popular distributions (e.g., apt, yum, zypper).
Include direct links to official documentation for both Windows and Linux agent installation and update procedures.
Explicitly state that all portal-based operations are OS-agnostic to reinforce cross-platform applicability.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to configure Azure Policy for Managed Disks backup using the Azure Portal UI, without providing any command-line examples. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or PowerShell examples are given, and no mention of automation or scripting approaches that are platform-neutral. This omission may disadvantage Linux-first users or those who prefer non-GUI workflows.

Recommendations:

Add examples using Azure CLI commands to assign and manage backup policies for Managed Disks, ensuring Linux and cross-platform users have clear guidance.
If relevant, provide PowerShell examples as well, but ensure Azure CLI or REST API examples are given equal or higher prominence.
Include a section on automating policy assignment using scripts (Bash, Python, etc.) for users who manage resources programmatically.
Explicitly mention that all steps can be performed via CLI or REST API, and link to relevant documentation for those workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples, commands, or tooling references (such as Windows, PowerShell, Linux, or CLI). However, it also does not include any Linux-specific guidance or parity examples, and the 'Next steps' and 'Related content' sections only reference REST API documentation, with no mention of command-line tools or scripts for either Windows or Linux. This absence of platform-specific examples may disadvantage Linux users who often rely on CLI or scripting guidance.

Recommendations:

Add example workflows for both Windows (PowerShell, Azure CLI in Windows) and Linux (Bash, Azure CLI in Linux) for common backup and restore operations.
Include references to cross-platform tools such as Azure CLI and show example commands for both operating systems.
If any platform-specific limitations exist, explicitly document them for both Windows and Linux.
Provide links to documentation or quickstarts for both PowerShell and Bash/CLI usage to ensure parity.
Consider adding a section on automating blob backup and restore using scripts, with examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains parity between Windows and Linux, but in the prerequisites section, the link to the Windows VM quickstart is listed before the Linux VM quickstart. This subtle ordering preference is a form of 'windows_first' bias. However, both platforms are otherwise mentioned equally, and connection instructions reference both RDP (Windows) and SSH (Linux) without favoring one. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples.

Recommendations:

List Linux and Windows VM quickstart links in alphabetical order or randomize their order to avoid implicit prioritization.
Wherever possible, ensure that examples and instructions mention both Windows and Linux platforms in parallel, or use neutral phrasing.
Periodically review documentation for subtle ordering or phrasing that may suggest platform preference, even if both are supported.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all configuration and restore steps, with no command-line examples provided for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, there is an implicit bias due to the absence of any Linux-specific guidance or CLI examples, which are common for cross-platform parity. There is no mention of PowerShell, Windows tools, or Windows-first ordering, but the lack of Linux/CLI examples may disadvantage Linux users who prefer or require automation or non-GUI workflows.

Recommendations:

Add Azure CLI (az) command examples for each step, ensuring they work on both Windows and Linux shells.
Explicitly mention that all steps can be performed via CLI or provide links to CLI documentation.
Include Bash shell scripts or command snippets for Linux users where appropriate.
If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided alongside.
Clarify any platform-specific differences in backup/restore workflows, if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation discusses RDP and SSH connectivity but does not provide any OS-specific examples or mention tools or workflows unique to either Windows or Linux. However, there is a subtle bias in that RDP (primarily a Windows protocol) is mentioned before SSH (primarily used for Linux), and there are no explicit Linux-specific examples or references to Linux-native tools or workflows. The documentation does not provide parity in illustrating Linux scenarios, such as connecting to Linux VMs via SSH from Linux/macOS clients or using Linux command-line tools.

Recommendations:

Include explicit examples or references for connecting to Linux VMs using SSH from Linux/macOS clients.
Mention Linux-native tools (such as OpenSSH) and workflows alongside any references to RDP or Windows tools.
Ensure that any future configuration or usage examples provide parity between Windows and Linux environments.
Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux) equally, and provide links to relevant documentation for both operating systems.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page describes how to rotate Batch account shared keys, but only provides instructions for using the Azure portal and does not include any command-line examples. There is no mention of platform-specific tools, but the absence of CLI (such as Azure CLI or PowerShell) examples means there is no parity for users who may prefer or require Linux-based workflows.

Recommendations:

Add Azure CLI examples for key rotation, as the Azure CLI is cross-platform and commonly used on Linux.
If PowerShell examples are added, ensure they are accompanied by equivalent Azure CLI commands.
Explicitly mention that the procedure can be performed from any OS using the Azure CLI, and provide sample commands.
Consider including REST API examples for advanced users or automation scenarios, which are also platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples before Linux/SSH examples in each section. Both platforms are covered with equivalent code samples and explanations, and there are no missing Linux examples or exclusive references to Windows tools or PowerShell. However, the ordering may subtly prioritize Windows scenarios.

Recommendations:

Alternate the order of examples in each section, sometimes presenting Linux/SSH first.
Add a short statement at the beginning clarifying that both Windows and Linux pools are equally supported, and that examples are provided for both.
Ensure parity in the depth and detail of examples for both platforms.
Consider grouping examples by scenario (e.g., 'Allow remote access', 'Deny remote access') and presenting both Windows and Linux code side by side for each scenario.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples for connecting to a storage account using a private endpoint. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission can be considered a bias by omission, as it does not address the needs of users who prefer or require Linux or command-line workflows.

Recommendations:

Add Azure CLI (az) command-line examples for each major step, such as disabling public access, creating the private endpoint, and configuring DNS.
Ensure that any scripts or commands provided are cross-platform (work on both Windows and Linux shells).
Include Bash shell examples where relevant, especially for Cloud Shell users who may be using the Bash environment.
Explicitly mention that the steps can be performed via CLI as well as the portal, and provide links to relevant CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform neutrality, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No exclusive Windows tools or PowerShell-heavy content is present, and Linux is not omitted from examples. The ordering in the keyboard shortcuts section may subtly prioritize Windows users.

Recommendations:

Rotate or randomize the order of platform-specific instructions (e.g., sometimes list Linux first, or group by usage context).
Consider grouping all OS instructions together under a neutral heading, or use a table for parity.
Review other sections for similar ordering and ensure Linux is not consistently listed last.
Explicitly state that Cloud Shell is cross-platform and that all features are available regardless of the underlying OS.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides sample log data where the only explicit desktop OS mentioned is Windows ("osVersion": "Windows 10.0.17763 Arch: x64"). Other examples include Darwin (macOS) and Android, but there are no Linux examples. Windows is the only desktop OS shown in the P2P call sample, and Linux is not mentioned anywhere. There are no command-line or tool usage examples, so no PowerShell or Windows tool bias is present, but the log samples show a subtle preference for Windows as a desktop environment.

Recommendations:

Include at least one sample log entry where 'osVersion' reflects a Linux distribution (e.g., 'Ubuntu 20.04', 'Linux 5.15.0-60-generic').
In the data definitions, clarify that 'osVersion' can include Linux, macOS, Windows, Android, and iOS, and provide representative values for each.
If possible, add a FAQ or note about how logs appear for Linux clients/endpoints.
Review future documentation and samples to ensure Linux is represented equally alongside Windows and macOS in both log samples and descriptive text.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a mild 'windows_first' bias in the prerequisites section, where the link to creating an Azure Communication Services resource includes a '?tabs=windows' parameter and the word 'windows' in the URL. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the guide is platform-neutral and focused on JavaScript/Node.js, which is inherently cross-platform.

Recommendations:

Ensure that links to Azure resource creation guides either default to a neutral tab or explicitly mention both Windows and Linux options.
If platform-specific steps exist (e.g., environment setup, file hosting, or CLI usage), provide parallel instructions or notes for Linux/macOS users.
Review and update any quickstart or referenced documentation to avoid defaulting to Windows tabs or terminology unless necessary.
Consider adding a note in the prerequisites clarifying that all steps and examples are cross-platform unless otherwise stated.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by referencing Windows first in the link to creating an Azure Communication Services resource, using a URL parameter (?tabs=windows&pivots=platform-azp) that suggests a Windows-centric quickstart. However, the rest of the page uses Java and Maven, which are cross-platform, and does not provide any OS-specific instructions or examples. There are no explicit PowerShell commands, Windows-only tools, or missing Linux equivalents in the main content.

Recommendations:

Update prerequisite links to either be OS-neutral or provide both Windows and Linux/macOS tabs equally, rather than defaulting to Windows.
Review linked quickstarts to ensure Linux and macOS instructions are as prominent and accessible as Windows instructions.
Explicitly state that the Java and Maven steps are cross-platform and can be run on Windows, Linux, or macOS.
If there are any platform-specific steps (e.g., environment variables, file paths), provide examples for both Windows and Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias by presenting Windows-specific instructions (virtual environment activation) before Unix/Linux equivalents. Additionally, some linked quickstarts default to Windows tabs. However, Linux/Unix commands are present where relevant, and the main content is otherwise platform-neutral.

Recommendations:

Present Unix/Linux and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
Ensure that all linked resources and quickstarts do not default to Windows tabs, or clearly indicate how to switch to Linux/Mac instructions.
Where possible, use platform-agnostic language and examples, or provide equal prominence to both Windows and Linux commands.
Consider explicitly stating that all features and examples are cross-platform unless otherwise noted.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a C# example for configuring Azure blob storage for call recording, but does not include any platform-specific commands or references. However, there are no examples or notes addressing Linux or cross-platform considerations, nor is there any mention of Windows-specific tools or patterns.

Recommendations:

Add explicit notes about cross-platform compatibility, clarifying whether the example applies equally to Windows, Linux, and macOS.
If there are any platform-specific steps (e.g., authentication with Azure CLI, environment variable setup), provide both Windows (PowerShell/CMD) and Linux (bash) command examples.
Include a section or note on any dependencies or configurations that may differ between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides terminal/command window instructions and virtual environment activation commands only in the Windows format (e.g., .\Scripts\activate), with no equivalent Linux/macOS commands (e.g., source ./bin/activate). This may confuse or hinder users on non-Windows platforms. No explicit Windows tools or PowerShell commands are used, but the lack of Linux/macOS parity is a notable bias.

Recommendations:

For every command-line instruction, provide both Windows and Linux/macOS versions, especially for virtual environment activation (e.g., '.\Scripts\activate' for Windows, 'source ./bin/activate' for Linux/macOS).
Use tabbed or side-by-side code blocks to show platform-specific commands where they differ.
Explicitly mention that the instructions apply to both Windows and Linux/macOS, and clarify any platform-specific steps.
Review the documentation for other subtle Windows-first assumptions, such as path separators or references to 'command window' instead of 'terminal'.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only C#/.NET code examples and does not include any OS-specific command-line instructions or tooling. However, it references environment variables and authentication via the Azure SDK, which can have OS-specific nuances, but does not clarify or provide examples for Linux/macOS users. There is no explicit Windows bias (e.g., PowerShell, Windows tools, or Windows-first ordering), but Linux parity is lacking in terms of environment variable setup and authentication instructions.

Recommendations:

Add explicit instructions or examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside any Windows (set AZURE_SUBSCRIPTION_ID=...) examples.
Clarify that the .NET Core SDK and Azure SDK are cross-platform and provide links or notes for Linux/macOS installation guides.
If referencing command-line authentication (e.g., az login), provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples.
Include a note or section confirming that all code samples are cross-platform and highlight any OS-specific considerations, if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of tools or command-line instructions, but it lacks explicit Linux parity in its examples and guidance. All code samples are in C# and .NET, which are cross-platform, but there are no shell or environment variable examples for Linux/macOS, nor are there any references to Linux-specific workflows or tools. The instructions for setting environment variables and acquiring the subscription ID are generic and do not mention platform-specific steps.

Recommendations:

Add explicit examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside any Windows (set AZURE_SUBSCRIPTION_ID=...) instructions.
When referencing the Azure CLI or authentication, provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples.
Clarify that .NET Core SDK and the code samples are cross-platform, and provide links or notes for Linux/macOS users where appropriate.
If referencing file paths or shell commands, include both Windows and Linux/macOS formats.
Consider including a short section or callout for Linux/macOS users to ensure they can follow along without ambiguity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation uses platform-specific pivots for web, Windows, Android, and iOS, but does not mention or provide examples for Linux. Additionally, in the 'Clean up resources' section, the link includes a 'tabs=windows' parameter, suggesting Windows is the default or primary example, with no mention of Linux alternatives.

Recommendations:

Add explicit Linux support or examples if the SDK or service is available for Linux.
In the 'Clean up resources' section, provide instructions or links for Linux users (e.g., using Azure CLI on Linux, or Bash examples).
Avoid defaulting to Windows tabs in links; use a neutral or platform-agnostic default, or provide clear options for all supported platforms.
If Linux is not supported, clearly state this in the documentation to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by linking to the Windows-specific Azure CLI installation instructions in the prerequisites, without mentioning or linking to Linux or macOS installation guides. However, all command-line examples use the cross-platform Azure CLI and are not inherently Windows-specific.

Recommendations:

In the prerequisites, provide links to Azure CLI installation instructions for all supported platforms (Windows, Linux, macOS), or link to the general installation page that covers all platforms.
Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS to reassure non-Windows users.
Consider including a brief note or section for platform-specific considerations, if any, to improve inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias by listing Windows command-line environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. No explicit Linux or cross-platform examples are missing, but the ordering implicitly prioritizes Windows environments.

Recommendations:

List Bash before or alongside cmd and PowerShell when mentioning console windows, e.g., 'In a console window (such as Bash, cmd, or PowerShell)...'
Explicitly state that all commands and code samples work identically on Linux, macOS, and Windows.
Consider adding a short section or note confirming cross-platform compatibility, especially for Linux users.
Where relevant, provide example terminal commands using both Windows and Linux conventions (e.g., path separators, environment variable syntax) if differences exist.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform parity, but in the environment variable setup section, Windows instructions are presented first, followed by macOS and Linux. There are no missing Linux examples or exclusive use of Windows tools, but the ordering may subtly prioritize Windows users.

Recommendations:

Rotate or randomize the order of OS-specific tabs (Windows, macOS, Linux) to avoid always listing Windows first.
Explicitly state that all examples are cross-platform unless otherwise noted.
Ensure that Linux and macOS instructions are as detailed and visible as Windows instructions.
Consider grouping macOS and Linux together as 'Unix-like' systems where appropriate to reduce repetition and highlight parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides parity between Windows, macOS, and Linux for environment variable setup, but consistently lists Windows instructions and tabs before macOS and Linux. All CLI examples use Azure CLI, which is cross-platform, and there are no PowerShell-specific or Windows-only tools used. However, the ordering of OS instructions may subtly prioritize Windows users.

Recommendations:

Rotate the order of OS tabs or list Linux/macOS first in some sections to avoid implicit prioritization of Windows.
Explicitly state that all CLI commands work identically across Windows, macOS, and Linux.
Consider combining macOS and Linux instructions when they are identical, or clarify any differences.
Ensure that any references to editors (e.g., Visual Studio) are accompanied by cross-platform alternatives (e.g., VS Code, JetBrains Rider) where relevant.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation refers to opening 'PowerShell, Windows Terminal, Command Prompt, or equivalent' when instructing users to open a terminal, listing Windows-specific tools first and not naming any Linux or macOS terminals. No explicit Linux or macOS examples or tools are mentioned, but the instructions are otherwise cross-platform (Node.js, npm, git, Azure CLI).

Recommendations:

Explicitly mention Linux and macOS terminal options (e.g., 'Terminal (macOS), GNOME Terminal (Linux), PowerShell, Windows Terminal, Command Prompt, or equivalent').
Provide assurance that all commands (git, npm, Azure CLI) work on Linux/macOS as well as Windows.
Consider adding a short section or note confirming cross-platform compatibility and calling out any OS-specific considerations.
If screenshots or file paths are shown, include examples for both Windows and Linux/macOS where they differ.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides platform-specific instructions for Windows, Android, and iOS, but does not mention or provide guidance for Linux or other desktop platforms. This omission may leave Linux users without clear instructions or support for the feature.

Recommendations:

Add a Linux-specific section or clarify Linux support status for local preview mirroring.
If the feature is not available on Linux, explicitly state this to inform users.
If parity is possible, provide instructions or code samples for Linux desktop environments (e.g., using Electron, web, or native Linux clients).
Ensure future documentation includes Linux alongside Windows, Android, and iOS in platform pivots.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash when describing how to run commands, which may suggest a Windows-first perspective. However, all command-line and code examples are cross-platform (Java, Maven) and do not rely on Windows-only tools or patterns. There are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples.

Recommendations:

When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') to avoid implying a Windows-first workflow.
Explicitly state that all commands work on Windows, Linux, and macOS, and provide any OS-specific notes if needed.
Consider including a short section or note confirming cross-platform compatibility for the setup and execution steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a mild 'windows_first' bias in the prerequisites section, where the link for creating an Azure Communication Services resource includes a '?tabs=windows' query parameter and references 'platform-azp', suggesting a default or primary focus on Windows. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the documentation is platform-neutral JavaScript/TypeScript code.

Recommendations:

Ensure that prerequisite links and quickstart guides reference both Windows and Linux (and macOS) tabs or provide a neutral/default tab.
Explicitly mention that the JavaScript SDK and code samples are cross-platform and can be used on Windows, Linux, and macOS environments.
Where platform-specific setup is referenced (such as resource creation), provide equivalent instructions or links for Linux and macOS users.
Audit all quickstart and resource links to avoid defaulting to Windows-specific tabs or instructions.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run commands, which subtly prioritizes Windows environments. However, all command-line instructions use cross-platform tools (Maven, Java), and no OS-specific commands or tools are used. There are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples.

Recommendations:

List Bash (or 'terminal') before cmd/PowerShell when mentioning consoles, or simply state 'in a terminal or command prompt' to avoid OS prioritization.
Explicitly state that all commands work on Windows, Linux, and macOS.
If possible, provide example outputs or troubleshooting notes for both Windows and Linux/macOS environments.
Ensure that any future instructions involving environment variables, file paths, or scripts include both Windows and Linux/macOS syntax.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, commands, or tooling references. However, it also does not provide any code snippets or command-line instructions at all—neither for Windows (e.g., PowerShell) nor for Linux (e.g., Bash/cURL). This absence means there is no explicit Windows bias, but there is a lack of parity in that Linux users are not shown how to interact with the API using common Linux tools.

Recommendations:

Add example API calls using cross-platform tools such as curl or HTTPie, which are available on both Linux and Windows.
If authentication steps require command-line interaction, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
Explicitly mention that the API can be accessed from any OS and provide guidance for both Windows and Linux environments.
If referencing Azure CLI or other tools, ensure instructions are OS-agnostic or provide OS-specific notes where necessary.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate Linux-specific tools, commands, or workflows. There are no explicit Windows or PowerShell examples, but the lack of any Linux examples or references may leave Linux users without clear guidance.

Recommendations:

Add explicit examples or references for both Windows and Linux environments, especially for common attestation workflows.
Include sample commands or scripts for Linux (e.g., using bash, curl, or OpenSSL) where relevant.
Mention any platform-specific requirements or differences in the attestation process for Linux users.
Provide links to Linux-focused resources or documentation if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation is generally cross-platform, focusing on the Azure Portal and Azure CLI, both of which are available on Windows, Linux, and macOS. However, there are multiple explicit tips for PowerShell users regarding escaping double quotes, but no equivalent guidance for Linux/macOS shells (e.g., Bash). This may cause confusion for non-Windows users and suggests a subtle PowerShell/Windows bias.

Recommendations:

Add equivalent shell escaping tips for Bash (Linux/macOS) users wherever PowerShell-specific tips are given. For example, show how to escape quotes in Bash: --tags '{"country":"US"}' or --tags '{"country":"US"}' (as appropriate).
Wherever PowerShell-specific instructions are provided, include a parallel note for Bash users.
Consider a short section or callout on cross-platform shell differences when using Azure CLI, especially for JSON arguments.
Review all CLI examples to ensure they work as-is in Bash and PowerShell, or provide both variants if needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific troubleshooting steps or examples, but it also omits any mention of Linux tools, commands, or patterns. While it avoids explicit Windows bias (no Windows/Powershell examples or tools are given), it also fails to address Linux users or provide parity for Linux troubleshooting approaches.

Recommendations:

Add examples of how to troubleshoot storage mount failures from within a Linux-based container, such as using 'ls', 'mount', or 'df' commands to verify mount points.
Include sample error messages or logs that might be seen in Linux environments (e.g., from /var/log or container stdout/stderr).
If relevant, mention how to use Linux-native tools (e.g., bash, sh, cat, tail) to inspect mount status or debug issues.
Clarify whether the troubleshooting steps apply equally to both Windows and Linux containers, or provide separate guidance if there are differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes cost analysis tasks using the Azure portal UI, with all navigation and examples tailored to the web interface. There are no command-line examples, scripts, or references to platform-specific tools (such as PowerShell, Azure CLI, or Bash). However, the absence of any CLI examples means that Linux users (who may prefer Azure CLI or Bash) are not served, while Windows users (who may prefer PowerShell) are also not directly addressed. The lack of parity is most evident in the omission of Azure CLI/Bash examples, which are commonly used in Linux environments.

Recommendations:

Add Azure CLI examples for each major cost analysis task, showing equivalent commands for Linux/macOS users.
Where relevant, provide PowerShell examples for Windows users, but ensure Azure CLI/Bash examples are always present and given equal prominence.
Explicitly mention that all tasks can be performed via the Azure CLI or REST API, and link to relevant cross-platform documentation.
Include notes or callouts highlighting any differences in experience or capabilities between the portal, CLI, and PowerShell.
Consider adding a 'Command-line alternatives' section for each scenario, with both Azure CLI and PowerShell scripts.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions, but it references only the Azure portal and support request process without mentioning command-line alternatives such as Azure CLI, PowerShell, or Bash. This omission may disadvantage Linux users who prefer or require CLI-based workflows, as no Linux-friendly (or cross-platform) instructions are provided.

Recommendations:

Include instructions for unblocking subscriptions using Azure CLI, which is cross-platform and widely used on Linux.
If PowerShell examples are relevant, ensure equivalent Azure CLI or Bash examples are provided.
Mention that the Azure portal is accessible from any modern browser, including those on Linux, to clarify platform neutrality.
Provide links to documentation for both GUI and CLI-based support request creation, ensuring Linux users have clear guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to create a Microsoft Customer Agreement subscription using the Azure portal UI, with no mention of command-line tools or platform-specific instructions. There are no examples or references to Windows-specific tools (such as PowerShell), nor are there any Linux-specific examples (such as Azure CLI commands). However, the absence of any command-line examples at all means Linux users do not see parity with Windows users who might expect PowerShell guidance. This constitutes a 'missing_linux_example' bias, as Linux users are not shown how to perform these actions outside the portal.

Recommendations:

Add examples for creating subscriptions using Azure CLI, which is cross-platform and commonly used on Linux.
If relevant, provide PowerShell examples alongside Azure CLI, but ensure Azure CLI appears first or is given equal prominence.
Explicitly mention that the Azure portal is platform-agnostic, but provide links or sections for users who prefer automation or command-line approaches.
Include a table or section comparing different methods (Portal, Azure CLI, PowerShell, REST API) for creating subscriptions, with links to relevant documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any examples or instructions for disabling or enabling autoscaling, and there is no mention of Linux or cross-platform considerations. The absence of examples, especially Linux-specific ones, suggests a lack of parity.

Recommendations:

Add step-by-step instructions for disabling and enabling autoscaling on both Windows and Linux platforms.
Include command-line examples for both PowerShell (Windows) and Bash (Linux).
Explicitly mention any platform-specific differences or requirements.
Ensure that Linux tools and workflows are given equal prominence to Windows equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples or tooling, but it also does not mention or demonstrate how to upload files to Azure Blob Storage from Linux or macOS environments. The only upload reference points to a portal-based guide, which is platform-agnostic but omits parity for CLI-based workflows common on Linux.

Recommendations:

Add examples for uploading DAG files to Azure Blob Storage using cross-platform tools such as Azure CLI (az storage blob upload) and/or Python SDK, with explicit command-line examples that work on Linux, macOS, and Windows.
Include a section or note highlighting that the upload process can be performed from any OS, and provide links or code snippets for both GUI (portal) and CLI methods.
If screenshots or UI steps are shown, clarify that the process is not limited to Windows and that Linux users can follow equivalent steps using the Azure CLI or other supported tools.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for configuring network settings on 'the server' or 'the Ethernet adapter of the laptop' but does not specify or provide examples for either Windows or Linux systems. There are no explicit references to Windows tools or PowerShell, but the language and phrasing (e.g., 'Ethernet adapter of the laptop') may implicitly assume a Windows environment. Critically, there are no Linux-specific instructions or examples for setting static IP addresses or network configuration, which could leave Linux users without clear guidance.

Recommendations:

Add explicit step-by-step instructions or command-line examples for configuring network settings on both Windows and Linux systems (e.g., using 'netsh' for Windows and 'ip' or 'nmcli' for Linux).
Wherever the documentation refers to 'the server' or 'Ethernet adapter,' clarify with examples for both operating systems.
Include screenshots or terminal output for Linux network configuration alongside any Windows examples.
Ensure that references to 'Supported OS' are accompanied by links or notes about where to find OS-specific setup instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples, but it also does not mention or demonstrate any Windows-specific tools, commands, or patterns. However, it lacks parity for Linux users by not providing any CLI-based instructions (such as using Bash, PowerShell, or other shells) for verifying network connectivity or interacting with the deployed module. All interactions are described via the web UI or browser, which is platform-agnostic, but the absence of CLI examples may disadvantage Linux users who often prefer or require terminal-based workflows.

Recommendations:

Add CLI-based examples for verifying module connectivity, such as using curl or wget from a Linux shell.
Include instructions for both Windows (PowerShell/cmd) and Linux (Bash) users where applicable, especially for network verification steps.
Explicitly mention that the steps are platform-agnostic if no OS-specific commands are needed, to reassure users of all platforms.
Provide troubleshooting steps or commands for both Windows and Linux in case the module is not reachable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not display overt Windows bias in terms of command-line examples, tool references, or platform-specific instructions. However, it lacks any OS-specific troubleshooting steps, CLI commands, or examples—neither Windows (e.g., PowerShell) nor Linux (e.g., Bash) are mentioned. All troubleshooting is described via the Azure portal or the device's local web UI, with no parity or guidance for users who may prefer or require CLI-based (Linux or Windows) management. This omission may disadvantage Linux users who expect parity with Windows-centric documentation that often provides PowerShell or Command Prompt examples.

Recommendations:

Add CLI-based troubleshooting steps where applicable, using both Azure CLI (cross-platform) and PowerShell examples.
Where device management can be performed via SSH or command line, provide both Linux (Bash) and Windows (PowerShell) command examples.
Explicitly mention if certain troubleshooting or management actions are only available via the web UI or portal, and clarify OS requirements if any exist.
If the device supports direct OS-level access (e.g., SSH for Linux), include relevant commands for common alert remediation.
Ensure that any future additions of command-line instructions or scripts include both Windows and Linux variants, or use cross-platform tools.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-specific patterns. However, it lacks parity by omitting any explicit Linux or cross-platform instructions or examples for network configuration, adapter setup, or web UI access. The only mention of configuring a 'laptop' or 'host computer' is generic and does not specify how to set a static IP on different operating systems, which can disadvantage Linux or Mac users.

Recommendations:

Add explicit instructions or links for configuring a static IP address on Linux and Mac, alongside Windows.
Where 'laptop' or 'host computer' is referenced, clarify that the steps apply to all major operating systems and provide OS-specific guidance as needed.
If screenshots or command-line steps are included in related pages, ensure Linux and Mac equivalents are present.
Mention supported operating systems more prominently and provide parity in troubleshooting steps for non-Windows environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display explicit Windows bias in terms of command-line examples, tools, or patterns, but it also does not provide any platform-specific guidance or examples at all. There are no instructions, screenshots, or references to either Windows or Linux environments, command lines, or tools. However, the absence of any mention of Linux (or Windows) means Linux users are not given parity in terms of environment preparation, troubleshooting, or command-line usage, which could be relevant for IT admins working in heterogeneous environments.

Recommendations:

Explicitly mention supported operating systems for device management and portal access (e.g., Windows, Linux, macOS).
If any command-line or scripting steps are required in later tutorials, provide both Windows (PowerShell/Command Prompt) and Linux (Bash) examples.
Include notes or links for Linux users on how to access the Azure portal, manage Azure resources, or interact with the device if there are any differences.
Add troubleshooting tips or prerequisites relevant to Linux environments (e.g., browser compatibility, required packages, or network configuration commands).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly show Windows bias through the use of Windows-specific tools, PowerShell commands, or Windows-first ordering. However, it lacks any mention of Linux-specific instructions, tools, or examples for configuring the LogRhythm collector, which is a common scenario in cross-platform environments. The absence of Linux guidance may disadvantage Linux users.

Recommendations:

Add explicit instructions or references for configuring LogRhythm collectors on Linux systems, including any relevant commands or configuration file locations.
Include examples or screenshots that demonstrate both Windows and Linux environments where applicable.
Clarify that the instructions are platform-agnostic if that is the case, or specify any platform-specific steps required.
Provide troubleshooting tips for both Windows and Linux collectors, if differences exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for creating Generation 2 VMs in Azure DevTest Labs exclusively through the Azure portal UI, with no mention of OS-specific tools, commands, or examples. However, it omits any discussion or examples of connecting to or managing Linux-based VMs, such as SSH access, Linux username conventions, or Linux-specific post-deployment steps. The documentation is neutral in terms of not explicitly favoring Windows, but it lacks Linux parity in connection and usage guidance.

Recommendations:

Include explicit examples for connecting to both Windows (using RDP) and Linux (using SSH) VMs after deployment.
Mention Linux username conventions and any differences in credential requirements.
Provide guidance or links for post-deployment configuration steps for Linux VMs, such as installing packages or configuring SSH keys.
Add screenshots or instructions that show Linux VM options and settings where they differ from Windows.
Clarify that the process applies equally to both Windows and Linux images, and highlight any OS-specific considerations.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on configuring SPAN ports on Cisco switches using Cisco CLI and GUI, with no mention of Windows, Powershell, or Windows-specific tools. However, there is a notable absence of Linux-specific guidance or examples, such as how to verify mirrored traffic on a Linux-based Defender for IoT sensor or using Linux tools to validate the configuration.

Recommendations:

Add examples or references for verifying SPAN/mirrored traffic on Linux-based Defender for IoT sensors (e.g., using tcpdump, Wireshark, or similar tools).
Include troubleshooting steps or commands for both Windows and Linux environments to ensure parity.
Explicitly mention that Defender for IoT sensors may run on Linux and provide guidance for common Linux network monitoring/validation tasks.
If relevant, provide sample configuration or verification steps for other operating systems/platforms where Defender for IoT sensors may be deployed.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Windows DNS as a source for zone files before mentioning BIND (the most common DNS server on Linux/Unix). The Windows DNS file path is described in detail, while the BIND example is more generic. No PowerShell or Windows-specific command-line tools are used, and the main workflow is through the Azure portal, which is cross-platform. However, the ordering and detail given to Windows DNS is evidence of a subtle 'windows_first' bias.

Recommendations:

List BIND (Linux/Unix) as a source for zone files before or alongside Windows DNS, and provide an example BIND zone file path (e.g., '/etc/bind/zones/db.example.com').
Offer more detail for BIND users, such as how to locate the zone file using 'named.conf' or typical Linux file locations.
Ensure that all references to obtaining zone files are platform-neutral, or provide equal detail for both Windows and Linux/Unix environments.
Consider including a note or link for MacOS users, if relevant.
Review future documentation for ordering and depth of platform-specific instructions to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to create activity log alerts using the Azure Portal GUI, with no mention of command-line or scripting alternatives. There are no examples using PowerShell, Azure CLI, or any platform-specific tools. However, the lack of Azure CLI (cross-platform) or Linux-specific instructions means Linux users do not see parity with Windows users who may be more accustomed to GUI or PowerShell workflows.

Recommendations:

Add step-by-step instructions for creating activity log alerts using the Azure CLI, which is cross-platform and widely used on Linux.
Include example scripts for automating alert creation, highlighting both PowerShell (for Windows) and Bash (for Linux/macOS) usage.
Explicitly mention that the Azure Portal is accessible from any OS, but provide parity by showing how to accomplish the same tasks from the command line.
Link to documentation on using Azure CLI and ARM templates for alert rule creation, to support automation and Linux-first workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only Azure Portal (GUI) instructions and screenshots, with no command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, it implicitly favors Windows by referencing Visual Studio Code as the code editor and omitting any mention of Linux tools, CLI commands, or cross-platform workflows. There are no examples or guidance for users who prefer or require Linux-based automation or scripting.

Recommendations:

Add Azure CLI examples for enabling diagnostic settings and downloading logs, as Azure CLI is cross-platform and widely used on Linux.
Include sample Bash commands for downloading blobs from Azure Storage (e.g., using az storage blob download or tools like wget/curl with SAS URLs).
Mention and provide examples for opening JSON logs with common Linux editors (e.g., nano, vim, less, jq) in addition to Visual Studio Code.
Explicitly state that all steps can be performed on Linux, macOS, or Windows, and provide parity in instructions where possible.
Where screenshots are used, consider including CLI output or terminal screenshots to complement GUI steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Windows DNS as a source for zone files before BIND (the most common Linux DNS server), and provides the Windows DNS file path explicitly, while only referencing BIND's configuration file generically. There are no command-line or tool-specific examples for either platform, but the ordering and detail favor Windows.

Recommendations:

List BIND (Linux/Unix) as a source for zone files before or alongside Windows DNS, reflecting its prevalence in non-Windows environments.
Provide the typical BIND zone file path (e.g., /etc/bind/zones/) as an example, similar to the explicit Windows path.
Add a brief note or example for exporting a zone file from BIND (e.g., using 'cp' or 'cat' to copy the file), to match the specificity given for Windows.
Ensure parity in detail and ordering when describing both Windows and Linux/Unix DNS systems.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a mild 'windows_first' bias in the 'Next steps' section, where Azure PowerShell (primarily associated with Windows environments) is mentioned before Azure CLI (which is cross-platform and widely used on Linux). There are no explicit examples or instructions that are Windows- or PowerShell-specific in the main content, and Linux tools or patterns are not omitted, but the ordering subtly prioritizes Windows tooling.

Recommendations:

List Azure CLI before Azure PowerShell in the 'Next steps' section, as CLI is cross-platform and more familiar to Linux users.
Wherever possible, provide parallel examples or links for both PowerShell and CLI, and clarify the cross-platform nature of Azure CLI.
Review other related documentation to ensure Linux and macOS users are equally supported and addressed, especially in introductory or 'getting started' materials.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples for configuring IP firewall settings. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users, as no CLI (Azure CLI, PowerShell, Bash) examples are provided. This omission can disadvantage users who prefer or require command-line automation, especially on Linux.

Recommendations:

Add Azure CLI examples for configuring IP firewall settings, as Azure CLI is cross-platform and widely used on Linux.
If relevant, include PowerShell examples as well, but ensure Azure CLI or Bash examples are presented first or alongside them.
Explicitly mention that the steps can be performed via command-line tools and provide links or references to those instructions.
Ensure screenshots and instructions are not overly focused on the Windows GUI experience, and consider including terminal screenshots or code snippets where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or command-line instructions (such as PowerShell or CLI), but it also does not include any Linux-specific guidance or examples. The absence of both Windows and Linux examples means there is no explicit Windows bias, but the lack of Linux parity in practical examples is notable.

Recommendations:

Add concrete examples for configuring the minimum TLS version using cross-platform tools such as Azure CLI, which works on both Windows and Linux.
If including PowerShell examples, ensure equivalent Bash/Azure CLI examples are provided.
Explicitly mention that the configuration steps are platform-agnostic or highlight any platform-specific considerations if they exist.
Provide troubleshooting steps or verification commands for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to enable managed identity on Azure Event Grid system topics using the Azure Portal (GUI), with no mention of command-line methods. There are no examples or instructions for performing these tasks using CLI tools such as Azure CLI (cross-platform) or PowerShell (Windows-centric). This omission results in a bias by not providing parity for users on Linux or those preferring command-line automation.

Recommendations:

Add step-by-step instructions for enabling managed identity using Azure CLI commands, which are cross-platform and widely used on Linux.
If PowerShell examples are included, ensure Azure CLI equivalents are provided and presented first or side-by-side.
Explicitly mention that the Azure Portal is platform-agnostic, but also provide automation-friendly alternatives for users who do not use the GUI.
Include links to relevant Azure CLI documentation for managing identities on Event Grid system topics.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a C# code example for retrieving HTTP headers but does not include any equivalent examples for Linux/Unix command-line tools (such as curl or jq), shell scripting, or other cross-platform languages. There are no references to Windows-specific tools, but the lack of Linux/CLI examples may disadvantage users on non-Windows platforms.

Recommendations:

Add examples using curl to demonstrate how to retrieve HTTP headers and parse response bodies from the command line.
Include sample scripts in Bash or other cross-platform scripting languages to show how to poll for operation status.
Provide code snippets in additional languages commonly used on Linux (such as Python or Node.js) for retrieving and processing HTTP headers.
Ensure that any code examples are balanced between Windows and Linux environments, or are explicitly cross-platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only portal-based, GUI instructions for setting up alerts in Azure Event Grid, with no mention of command-line tools or scripts. There are no examples using Windows-specific tools (like PowerShell), 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 may disadvantage Linux users or those who prefer automation and scripting.

Recommendations:

Add equivalent instructions for setting up alerts using the Azure CLI, including example commands.
If relevant, provide sample scripts in Bash and PowerShell to ensure parity between platforms.
Explicitly mention that the portal-based steps are platform-agnostic, but offer links or sections for command-line and automation approaches.
Ensure that any referenced screenshots or UI elements are not Windows-specific, or clarify if they are universal across platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a mild 'windows_first' bias by consistently referring to 'command prompt' and recommending Visual Studio Code, both of which are more closely associated with Windows environments. However, all code and CLI instructions are cross-platform, and there are no PowerShell-specific commands or Windows-only tools. No Linux-specific examples or terminal references are provided, and the language assumes a Windows-centric workflow.

Recommendations:

Replace references to 'command prompt' with 'terminal' or 'command-line interface' to be more platform-neutral.
When instructing users to open a shell, mention both 'Command Prompt/PowerShell (Windows)' and 'Terminal (Linux/macOS)'.
Recommend Visual Studio Code as a cross-platform editor, but also mention other popular editors (e.g., PyCharm, Sublime Text, vim) without platform preference.
Explicitly state that all CLI and Python commands work on Windows, Linux, and macOS.
Consider including screenshots or terminal output from both Windows and Linux environments, or at least clarify that the instructions are platform-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (GUI) for configuration steps and does not provide any command-line examples for either Windows (PowerShell) or Linux (CLI). However, the absence of Azure CLI (cross-platform, Linux-friendly) examples means Linux users do not have parity with Windows users who might be more accustomed to GUI or PowerShell workflows.

Recommendations:

Add Azure CLI examples for each configuration step to ensure Linux and cross-platform users can follow along without relying on the portal.
Explicitly mention that all steps can be performed using Azure CLI or ARM templates, and provide links or code snippets.
If PowerShell examples are added in the future, ensure Azure CLI equivalents are also provided and presented with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation contains a subtle Windows bias in the section discussing supported cipher suites. It specifically references Windows operating systems (Windows 10, 8.1, 8, and 7) when recommending cipher suite compatibility, without mentioning Linux or macOS equivalents. There are no command-line examples or tool references, but the only OS-specific advice is Windows-centric.

Recommendations:

Include information about cipher suite compatibility for popular Linux distributions and macOS, not just Windows.
Provide guidance or references for how to check or configure TLS cipher suites on Linux (e.g., using OpenSSL or system configuration files).
If mentioning OS compatibility, ensure parity by listing both Windows and Linux/macOS considerations, or link to relevant documentation for those platforms.
Consider adding example commands or configuration snippets for both Windows (e.g., PowerShell) and Linux (e.g., OpenSSL, update-alternatives, or systemd-tls settings) where relevant.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists Azure management tools in the order: Portal, Azure CLI, Azure PowerShell, REST API, and ARM template. Azure PowerShell is mentioned before REST API and ARM template, which can be interpreted as a subtle 'windows_first' bias. However, there are no explicit PowerShell-only examples, nor are Windows-specific tools or patterns promoted exclusively. Azure CLI is mentioned, which is cross-platform, and no examples are given that are specific to Windows or Linux.

Recommendations:

When listing management tools or methods, alternate the order or explicitly state that all methods are cross-platform where applicable.
Provide explicit command examples for both Azure CLI and Azure PowerShell, ensuring parity, or clarify that both are supported equally.
If possible, add a note that Azure CLI is available on Windows, Linux, and macOS to reinforce cross-platform support.
Avoid consistently listing PowerShell before CLI or REST unless there is a technical reason.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any command-line examples or troubleshooting steps for either Windows or Linux. However, it exclusively references the Azure portal UI for all verification and configuration steps, and does not mention or provide examples for Linux CLI tools (such as Azure CLI, kubectl, or YAML editing via command line). This omission may disadvantage Linux users or those working in non-GUI environments, as it lacks parity for command-line workflows commonly used on Linux.

Recommendations:

Add equivalent Azure CLI and/or PowerShell command examples for each portal-based step, ensuring both Linux and Windows users are supported.
Include kubectl command-line examples for verifying and editing AKS service and load balancer configurations, as these are standard for Linux users.
Provide YAML editing and application instructions using command-line tools (e.g., 'kubectl apply -f ...'), not just referencing the Azure portal.
Explicitly mention both GUI and CLI approaches in each troubleshooting step to ensure cross-platform usability.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a general overview of Azure Migrate assessment types and prerequisites, but it does not mention or provide examples specific to Linux workloads, tools, or discovery methods. The focus is on general concepts and on-premises environments (VMware, Hyper-V, physical servers), with no explicit Windows bias in terms of tools or commands, but there is a lack of Linux-specific guidance or parity.

Recommendations:

Include explicit references to Linux workloads in assessment types and discovery sources, clarifying support and any special considerations.
Add examples or notes about assessing Linux servers, including any differences in data collection, prerequisites, or agent requirements.
Mention Linux-specific tools or commands where relevant, or clarify that the Azure Migrate appliance supports both Windows and Linux equally.
Provide links to Linux-focused tutorials or documentation for assessing and migrating Linux workloads.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate Linux tools, commands, or scenarios. This omission could lead to a perception of bias if future content only includes Windows-centric information or omits Linux-specific guidance.

Recommendations:

Ensure that future documentation includes explicit Linux migration scenarios and examples alongside Windows ones.
Provide parity in tooling and command-line examples (e.g., include both PowerShell and Bash/CLI instructions where applicable).
Reference Linux-specific considerations or tools (such as SSH, rsync, or Linux VM migration best practices) in addition to Windows tools.
Clearly indicate when instructions are platform-agnostic, and call out any platform-specific steps for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific examples, commands, or tooling references. However, it also does not mention or provide parity for Linux environments, such as CLI commands or troubleshooting steps that might be relevant for Linux users. The focus is entirely on the Azure portal UI, with no examples for either Windows or Linux command-line environments.

Recommendations:

Add examples using Azure CLI and/or Azure PowerShell to retrieve effective security rules, ensuring both Windows and Linux users are supported.
Explicitly mention that the Azure CLI commands work cross-platform (Windows, Linux, macOS).
Provide sample scripts or command lines for common Linux shells (e.g., Bash) to download or process the CSV output.
If relevant, include troubleshooting steps or references for both Windows and Linux VM network interfaces.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell or Windows command-line patterns, but there is also a complete absence of CLI examples (such as Azure CLI or Bash scripts) that would be relevant for Linux or cross-platform users. This omission creates a bias by not addressing the needs of users who prefer or require command-line automation, which is common in Linux environments.

Recommendations:

Add Azure CLI examples alongside portal instructions for each major step (resource creation, deletion, configuration).
Ensure CLI examples are presented in Bash syntax to maximize Linux compatibility.
Where relevant, mention both Azure CLI and PowerShell options, but do not prioritize Windows tooling.
Include links to documentation for automating NAT Gateway configuration using CLI tools.
Explicitly state that all steps can be performed via CLI and provide a parity table or section for command-line equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only .NET SDK (C#) and REST API examples, which are platform-agnostic but most commonly associated with Windows development. There are no examples or references for Linux-specific tools, SDKs, or workflows, nor is there guidance for developers working outside the .NET ecosystem.

Recommendations:

Add code samples in other popular cross-platform languages (e.g., Python, Node.js, Java) that are commonly used on Linux.
Include REST API examples using curl or HTTPie, which are standard tools on Linux.
Explicitly mention that the REST API approach is platform-independent and can be used from any OS.
Provide guidance or links for setting up Notification Hubs integration on Linux-based environments.
If relevant, mention any Azure CLI commands or scripts that can be run from Linux terminals.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of mentioning Windows-specific tools or PowerShell commands. However, it lacks explicit Linux examples or references, especially in command-line usage, and does not clarify OS compatibility for the Azure CLI commands provided. This omission may implicitly favor Windows users by not addressing Linux usage or parity.

Recommendations:

Explicitly state that the Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide any OS-specific notes if relevant.
Include example command-line usage on both Windows (e.g., PowerShell or Command Prompt) and Linux (e.g., Bash), especially if there are differences in syntax or prerequisites.
Mention any required dependencies or setup steps for Linux environments, such as package installation or authentication methods.
If file paths or environment variables are referenced, provide both Windows and Linux formats.
Add a section or note highlighting that the NPB features and Azure CLI commands are fully supported on Linux, and link to relevant Linux-specific Azure CLI documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides generic installation and uninstallation steps without specifying any platform, but it uses terms like 'Install Extension' and 'Uninstall Extension' that are more commonly associated with Windows GUIs. There are no command-line examples or references to Linux-specific tools or procedures, and no mention of Linux package managers or shell commands.

Recommendations:

Add explicit Linux installation and uninstallation instructions, including command-line examples (e.g., using apt, yum, or shell scripts).
Clarify whether the steps apply to both Windows and Linux, or provide separate sections for each platform.
Include screenshots or command snippets for Linux environments to ensure parity.
Avoid using GUI-centric terminology unless it applies equally to Linux desktop environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only GUI-based instructions without mentioning command-line alternatives. There is no reference to platform-specific tools, but the lack of CLI examples (such as Bash or PowerShell) may disadvantage Linux users who often prefer or require command-line instructions.

Recommendations:

Add command-line instructions for deleting the resource using both PowerShell (for Windows users) and Bash/CLI (for Linux/macOS users).
Explicitly mention cross-platform tools such as Azure CLI and provide examples for each supported OS.
Clarify whether the GUI instructions apply equally to all platforms or if there are platform-specific differences.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page lists 'Create a private link service using Azure PowerShell' before 'Create a private link service using Azure CLI' in the 'Next steps' section. Azure PowerShell is primarily associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux. No explicit Windows-only tools, commands, or examples are present in the main content, and there are no missing Linux examples. However, the ordering in 'Next steps' subtly prioritizes the Windows-centric tool.

Recommendations:

List Azure CLI instructions before Azure PowerShell in the 'Next steps' section, as CLI is cross-platform and more widely used in Linux environments.
Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, if applicable.
Where possible, provide example commands for both Azure CLI and PowerShell within the main documentation body, or link to both equally.
Review other related documentation to ensure Linux parity in examples and tool recommendations.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific troubleshooting commands or examples, but it also does not mention or demonstrate any Windows- or Linux-specific tools, commands, or patterns. However, it implicitly assumes use of the Azure Portal and Azure-provided tools without addressing command-line troubleshooting (e.g., PowerShell, CMD, Bash, or Linux tools like dig, nslookup, traceroute, etc.), resulting in a lack of parity for Linux users who may prefer or require CLI-based diagnostics.

Recommendations:

Add explicit troubleshooting steps using both Windows and Linux command-line tools (e.g., show how to use PowerShell, CMD, and Bash to test connectivity, DNS resolution, and routing).
Include examples of using common Linux tools such as dig, nslookup, curl, traceroute, and ip route to diagnose private endpoint connectivity.
Where Azure Portal steps are described, provide equivalent Azure CLI or Azure PowerShell commands, and clarify which commands work on both Windows and Linux.
Add a section or callout noting that all steps can be performed from either Windows or Linux VMs, and provide links to relevant OS-specific documentation where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows or PowerShell bias, it also omits Azure CLI or scripting examples, which are commonly used on Linux and cross-platform environments. There is an implicit bias in not providing parity for users who prefer or require command-line automation, especially on Linux.

Recommendations:

Add Azure CLI examples for each step (e.g., registering resource providers, creating resource groups, obtaining resource IDs, creating private endpoints, approving connections).
Ensure that CLI examples are cross-platform and do not rely on PowerShell-specific syntax.
Clearly indicate that all steps can be performed via the Azure CLI on Windows, Linux, or macOS.
Consider including Bash script snippets for automation scenarios.
If PowerShell examples are added, always provide equivalent Azure CLI examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions, but it also omits any mention of command-line tools or steps for either Windows or Linux. However, the absence of Linux-specific instructions or parity checks (such as CLI commands, shell scripts, or Linux tooling) can be considered a subtle bias, as many Azure quickstarts often default to Windows-centric tools or examples elsewhere. In this case, the page is neutral but lacks explicit Linux guidance.

Recommendations:

Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash, Azure CLI on Linux) when showing how to create or manage a Redis instance.
Include sample commands for common Linux shells (bash, zsh) alongside any Windows examples.
If using downloadable scripts or templates, provide both .ps1 (PowerShell) and .sh (Bash) versions.
Reference Linux-specific tools or workflows (such as using Azure CLI on Linux) in the prerequisites or creation steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains parity between Windows and Linux, but in the 'Prepare VMs' section, instructions for updating certificates are presented with Windows guidance first, followed by Linux. No command-line examples are given for either OS, and no PowerShell or Windows-specific tooling is used elsewhere. However, the order of presentation subtly prioritizes Windows.

Recommendations:

Present Windows and Linux instructions in parallel or alternate the order in which they are mentioned to avoid implicit prioritization.
Where possible, provide explicit, concrete examples for both Windows (e.g., using Windows Update) and Linux (e.g., using apt, yum, or update-ca-certificates) to ensure clarity and parity.
Review all sections to ensure that Linux is not consistently mentioned after Windows, and that both platforms receive equal prominence in prerequisites and procedural steps.
If screenshots or UI elements are OS-specific, include examples for both Windows and Linux VMs where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to delegate Azure role assignment management using the Azure Portal GUI, with no mention of command-line tools or scripts. There are no examples or references to Windows-specific tools (such as PowerShell), 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 results in an implicit bias toward GUI-based workflows, which are often more familiar to Windows users, and does not address the needs of Linux users or those preferring automation and scripting.

Recommendations:

Add equivalent step-by-step instructions using Azure CLI commands for all major tasks described (e.g., assigning roles with conditions, editing conditions).
Provide sample scripts for both Bash (Linux/macOS) and PowerShell (Windows) where applicable.
Explicitly mention that all operations can be performed via the Azure CLI or REST API, and link to relevant documentation.
Ensure that screenshots and examples are balanced between GUI and CLI approaches to support both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions PowerShell before Azure CLI and REST API when listing tools for adding the Exists operator to ABAC attributes. This ordering may suggest a preference for Windows-centric tooling, as PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. No exclusive Windows-only tools or missing Linux examples are present, but the ordering could imply a subtle bias.

Recommendations:

List Azure CLI before PowerShell when mentioning cross-platform tools, as Azure CLI is natively cross-platform and more familiar to Linux users.
Explicitly state that both PowerShell and Azure CLI are available on Windows, Linux, and macOS to reinforce cross-platform parity.
Where possible, provide example commands for both Azure CLI and PowerShell, or link to equivalent documentation for each.
Avoid defaulting to Windows-associated tools or terminology when describing general workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there are also no CLI examples (such as Azure CLI or Bash scripts) that would support Linux or cross-platform users. This omission can be considered a bias of omission, as Linux users often prefer or require CLI-based instructions.

Recommendations:

Add equivalent Azure CLI (az) command examples for each major step, alongside or after the portal instructions.
Explicitly mention that all steps can be performed using the Azure CLI or PowerShell, and provide links to relevant documentation.
Ensure that any scripts or automation examples are provided in both PowerShell and Bash where appropriate.
Include a section or callout for 'Command-line alternative' for users who prefer not to use the portal.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation avoids explicit Windows bias by not mentioning Windows-specific tools or PowerShell. However, it also does not provide any OS-specific command-line examples or considerations. The only CLI instructions use Azure CLI, which is cross-platform, but there are no examples or notes about running these commands on Linux or macOS, nor are there screenshots or troubleshooting steps for non-Windows environments. This could lead to a subtle bias by omission, as Linux users may not feel fully supported.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
Add a note or example showing how to install Azure CLI on Linux (e.g., using apt, yum, or Homebrew).
Include screenshots or terminal examples from a Linux shell (e.g., bash) in addition to or instead of GUI screenshots.
Mention any OS-specific considerations (such as shell differences, permissions, or environment variables) if relevant.
Ensure troubleshooting steps are inclusive of both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples or tool references, but it lacks any mention of the operating system used for the self-hosted agent or the pipelines. There are no examples or guidance for Linux users, nor is there clarification on whether the steps are OS-agnostic. This omission may leave Linux users uncertain about compatibility or required setup.

Recommendations:

Explicitly state which operating systems are supported for the self-hosted agent and pipelines (e.g., Windows, Linux, macOS).
Provide setup instructions or references for both Windows and Linux self-hosted agents.
Include example commands or screenshots for both Windows and Linux environments where relevant (e.g., agent installation, file paths).
Clarify any OS-specific requirements or differences in the deployment process.
If the process is OS-agnostic, explicitly state this to reassure users on all platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or commands, but it also does not include any Linux-specific guidance, scripts, or CLI instructions, despite being tagged for both Linux and Windows. The instructions are generic and do not reference Windows tools or PowerShell, but the lack of explicit Linux (or cross-platform) command-line examples may disadvantage Linux users.

Recommendations:

Add explicit Azure CLI examples for each step, as Azure CLI is cross-platform and commonly used on Linux.
Include sample shell (bash) commands for Linux environments, especially for steps like registering applications and assigning roles.
If any PowerShell or Windows-specific steps are relevant, ensure equivalent Linux/bash instructions are provided and presented with equal prominence.
Clarify in each step whether the instructions are platform-agnostic or if there are differences between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page lists Windows-specific tools (PowerShell) before cross-platform alternatives (CLI, Resource Manager template) when describing how to enable message sessions. No explicit Linux or Bash examples are provided, and the ordering of tools may suggest a Windows-first approach, though the page does mention cross-platform options.

Recommendations:

Reorder tool mentions to list cross-platform options (e.g., Azure CLI) before Windows-specific tools (e.g., PowerShell).
Explicitly mention that Azure CLI and Resource Manager templates are cross-platform and suitable for Linux/macOS users.
Provide example commands for both PowerShell and Bash/Azure CLI where relevant.
Consider adding a short section or note highlighting Linux/macOS parity and linking to platform-specific guidance if available.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page describes Azure SQL Database security features in a platform-neutral manner, without explicit Windows or PowerShell examples. However, it lacks any mention of Linux-specific tools, commands, or configuration patterns, and does not provide Linux-oriented guidance or parity in examples. The only indirect Windows reference is the mention of 'WinFabric platform' in configuration management, but this is in the context of Azure's internal infrastructure, not customer-facing instructions. The absence of Linux examples or references constitutes a 'missing_linux_example' bias.

Recommendations:

Add examples or references for configuring firewalls and network ACLs from both Windows and Linux environments (e.g., using iptables, ufw, or Azure CLI on Linux).
Include sample commands for connecting to Azure SQL Database from Linux-based tools (e.g., sqlcmd on Linux, Azure Data Studio, or ODBC drivers for Linux).
Mention Linux-compatible management tools and clarify that all described security features are accessible and manageable from Linux systems.
If referencing internal Azure infrastructure tools (like WinFabric), briefly clarify their relevance or provide Linux analogs if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or commands, but it does mention that Azure Storage is foundational for both Windows and Linux VMs. However, there are no code snippets, CLI commands, or tooling instructions for either Windows (e.g., PowerShell) or Linux (e.g., Bash, CLI), resulting in a lack of practical guidance for Linux users. The only client libraries mentioned for client-side encryption are Java and .NET, which are cross-platform but may be perceived as more common in Windows environments. There are no explicit Windows-only tools or patterns, but the absence of Linux-specific examples or references could be seen as a subtle bias.

Recommendations:

Add practical examples using Azure CLI commands, which are cross-platform and commonly used on Linux.
Include code snippets or walkthroughs for both PowerShell (Windows) and Bash (Linux) where relevant.
Mention and link to Python or Node.js client libraries for encryption, which are widely used on Linux.
Explicitly state that all features and best practices apply equally to both Windows and Linux environments.
Where possible, provide parity in documentation for both Windows and Linux workflows, especially for key management and automation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples, tools, or patterns, but it lacks any mention of Linux or cross-platform considerations. There are no examples or instructions that reference Windows-specific tools (like PowerShell) or workflows, but equally, there is no information about Linux compatibility, deployment, or usage, which may leave Linux users uncertain about support or required steps.

Recommendations:

Explicitly state whether the Microsoft Sentinel solution for MS Business Apps is supported on both Windows and Linux environments.
If relevant, provide examples or notes for both Windows and Linux administrators (e.g., how to configure connectors or access logs from Linux-based systems).
Mention any platform-specific requirements, limitations, or best practices for Linux environments.
Include references or links to cross-platform documentation or troubleshooting guides.
Clarify if any features (such as Playbooks or Parsers) have different behaviors or setup steps on Linux versus Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples or tool recommendations. However, it lacks parity by not providing any Linux-specific examples or instructions, especially in the section where cURL is mentioned. The only command-line tool referenced (cURL) is cross-platform, but no explicit Linux or macOS usage is shown, nor are there any screenshots or steps that acknowledge Linux environments. The documentation is focused on the Microsoft Sentinel web interface, which is platform-agnostic, but it misses opportunities to address Linux users directly.

Recommendations:

When mentioning cURL, provide explicit examples for both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., bash shell).
Include notes or sections that clarify that all steps can be performed from any OS with a supported browser, and highlight any OS-specific considerations if they exist.
If screenshots or instructions reference file paths or command-line usage, ensure both Windows and Linux formats are shown.
Consider adding a brief section or FAQ addressing common Linux/macOS user questions, such as authentication or network troubleshooting.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not display overt Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-specific patterns. However, it lacks any mention of Linux-specific tools, workflows, or examples, and does not address cross-platform considerations. All examples and instructions are platform-neutral but implicitly assume the use of Azure Logic Apps and Microsoft Sentinel interfaces, which are web-based and not OS-specific. The absence of Linux-specific guidance or parity checks constitutes a 'missing_linux_example' bias.

Recommendations:

Explicitly mention that Microsoft Sentinel and Logic Apps are accessible and manageable from Linux, macOS, and Windows environments.
Provide example workflows or command-line interactions (e.g., using Azure CLI) from a Linux shell, especially for tasks like exporting/importing ARM templates or managing playbooks.
Include references to cross-platform tools (such as Azure CLI, REST API usage) and clarify that PowerShell is not required.
Add a section or note on how to perform common migration or operational tasks from Linux systems, ensuring parity with any Windows-based instructions.
If any automation or scripting is discussed, provide both Bash and PowerShell examples where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Splunk-to-Microsoft Sentinel migration and provides step-by-step instructions for exporting data from Splunk using Splunk Web, but does not mention or provide examples for Linux command-line tools, shell scripts, or non-GUI workflows. There are no references to Windows-specific tools or PowerShell, but the lack of Linux/CLI parity in the export/upload process and absence of cross-platform considerations indicate a subtle bias toward GUI-based (often Windows-centric) workflows.

Recommendations:

Add instructions for exporting Splunk detections using the Splunk CLI or REST API, with example commands for Linux environments.
Include sample shell scripts or curl commands for users who prefer or require command-line workflows, especially on Linux systems.
Clarify that the export and upload process can be performed from any OS, and provide OS-agnostic guidance.
Where screenshots are shown, consider including both GUI and CLI alternatives, or at least mention that CLI options exist.
Explicitly state platform requirements or lack thereof, to reassure Linux users that the process is not Windows-specific.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or tooling references (such as PowerShell or Windows tools), but it also does not provide any command-line or code examples at all. This omission means there is no explicit Windows bias, but there is also a lack of Linux parity, as users on any platform are not shown how to enforce the minimum TLS version using CLI tools (e.g., Azure CLI, which is cross-platform).

Recommendations:

Add step-by-step examples using Azure CLI commands to configure the minimum TLS version, as Azure CLI is cross-platform and works on both Windows and Linux.
If PowerShell or Azure Portal instructions are added in the future, ensure equivalent Azure CLI (or REST API) examples are provided and presented first or alongside to avoid Windows-first bias.
Explicitly mention that the configuration can be performed from any platform using Azure CLI or REST API, not just from Windows environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides step-by-step instructions for enabling replication for private endpoints in Azure Site Recovery, but all operational guidance is given exclusively through the Azure Portal UI and Azure PowerShell references. There are no CLI (az CLI) or Linux-native command examples, nor is there mention of Linux-specific considerations or tooling. This may disadvantage users who prefer or require Linux-based automation or command-line workflows.

Recommendations:

Add equivalent Azure CLI (az CLI) commands for all major steps, such as creating private endpoints, configuring managed identities, and managing DNS zones and records. The Azure CLI is cross-platform and commonly used on Linux.
Where PowerShell is referenced, provide parallel az CLI examples, or at least mention that the same actions can be performed via CLI with a link to relevant documentation.
Explicitly state that all steps can be performed from Linux environments using the Azure CLI, and provide links to relevant Linux/CLI documentation.
Include a section or note on Linux compatibility, especially for automation scenarios, and clarify any differences or caveats for Linux users.
If screenshots are only from the Azure Portal, consider adding CLI output examples or terminal screenshots to support Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a step-by-step tutorial for setting up disaster recovery using the Azure portal UI, but does not include any command-line examples or references for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, it implicitly assumes a GUI workflow, which is more familiar to Windows users, and does not mention or provide parity for Linux-centric workflows (such as using the Azure CLI in Bash). There is no explicit Windows bias in terms of tools or examples, but the lack of Linux command-line guidance represents a gap.

Recommendations:

Add Azure CLI (az) command-line examples for enabling VM replication, suitable for both Linux and Windows users.
Include references or links to documentation on how to perform the same disaster recovery setup using Bash or other Linux shells.
Clarify that the process can be completed via both the Azure portal and command-line tools, and provide parity in instructions.
If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are also provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display explicit Windows bias (such as PowerShell or Windows-only tools), but it also does not provide any OS-specific examples or instructions. All command-line examples use Azure CLI and bash-style commands, which are cross-platform but may be more familiar to Linux/macOS users. There are no references to Windows-specific tools, PowerShell, or Windows-first patterns. However, there is a lack of explicit Linux parity guidance or troubleshooting for Linux environments, and no mention of OS-specific considerations.

Recommendations:

Explicitly state that the Azure CLI and bash commands work on Linux, macOS, and Windows (with WSL or Azure CLI for Windows).
If there are any OS-specific considerations (such as file path formats, environment variable syntax, or CLI installation steps), provide guidance for both Windows and Linux users.
Add a note or section on how to run the Azure CLI commands in PowerShell or Command Prompt for Windows users, if relevant.
Include troubleshooting tips for common issues that may differ between Linux and Windows environments (e.g., file permissions, line endings, etc.).
Ensure that any screenshots or UI references are not Windows-centric and clarify if the experience differs on other platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples or tooling, but it also does not mention or show any Linux-specific workflows, commands, or screenshots. All instructions are GUI-based and platform-agnostic, but there is a lack of parity for users who may prefer or require command-line or Linux-native approaches.

Recommendations:

Add CLI-based instructions for resetting and updating deployment tokens using Azure CLI, PowerShell, and Bash, ensuring both Windows and Linux users are supported.
Include examples of how to update GitHub secrets using the GitHub CLI (gh) or via scripts, with both Windows (PowerShell) and Linux (Bash) syntax.
Provide screenshots or terminal output from both Windows and Linux environments where relevant.
Explicitly mention that the process can be performed on any OS, and link to cross-platform tools or documentation where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented around the Azure Portal graphical interface and AWS Console, with all instructions and screenshots based on web UI workflows. There are no command-line examples provided for any platform (Windows, Linux, or macOS), nor are there references to platform-specific tools such as PowerShell, Windows Command Prompt, Bash, or Linux CLI utilities. As a result, there is no explicit Windows bias in terms of tools, commands, or ordering. However, the absence of any CLI or automation examples (such as Azure CLI, AWS CLI, or scripting) means that Linux users—who often prefer or require command-line workflows—are not served. This constitutes a 'missing_linux_example' bias, as the documentation does not provide parity for users who operate outside of graphical interfaces.

Recommendations:

Add step-by-step instructions for performing each major operation (connector creation, endpoint configuration, job creation, monitoring) using Azure CLI and, where applicable, AWS CLI.
Provide example scripts or command sequences for Linux/macOS environments, including authentication and resource management.
Include notes or sections on how to automate the migration process using shell scripts or cross-platform tools.
Ensure that any references to automation or scripting are not limited to PowerShell or Windows tools, but include Bash and other common Linux shells.
Where UI-only features exist, explicitly state their limitations and provide workarounds or alternatives for CLI users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively provides .NET (C#) code samples and instructions without any reference to platform-specific tools or shell environments. However, it does not provide any command-line examples (such as PowerShell, Windows CMD, Bash, or Linux CLI), nor does it mention any platform-specific tools. The content is neutral in terms of Windows vs. Linux, but it lacks parity for users who might want to perform these operations using cross-platform command-line tools or scripts (e.g., Azure CLI, Bash).

Recommendations:

Add equivalent examples using Azure CLI commands for creating, managing, and deleting blob snapshots. Azure CLI is cross-platform and works on both Windows and Linux.
If referencing command-line operations, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are provided, or use Azure CLI syntax which is consistent across platforms.
Explicitly mention that the .NET code samples are platform-agnostic and can be run on Windows, Linux, or macOS, provided the .NET SDK is installed.
Provide links or references to documentation for performing the same tasks using other languages or tools (e.g., Azure CLI, REST API, Python SDK) to improve accessibility for non-Windows and non-.NET users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation is focused exclusively on .NET and C# code examples, with no mention of platform-specific tools or shell environments (such as Windows PowerShell or Linux Bash). However, it does not provide any Linux-specific examples or guidance, nor does it address cross-platform usage scenarios (e.g., running .NET code on Linux or Mac). The lack of Linux- or cross-platform-specific instructions or considerations may make the documentation less accessible to developers working outside of Windows environments.

Recommendations:

Explicitly mention that the .NET client library and code samples can be used on Linux and macOS as well as Windows.
Provide setup instructions or notes for .NET development on Linux (e.g., using the .NET SDK on Ubuntu, installing dependencies, running code from the terminal).
Include example commands for running the code on Linux/macOS terminals (e.g., using 'dotnet run' in Bash).
If there are any platform-specific considerations (such as file paths, authentication methods, or environment variables), document these for Linux/macOS users.
Consider linking to cross-platform .NET documentation or guides for Linux/macOS developers.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation references the 'Cryptography API: Next Generation' (CNG), which is a Windows-specific cryptographic module, as the source for more information about Azure data encryption. No equivalent Linux or cross-platform cryptographic modules or standards are mentioned. There are no command-line examples, so there is no bias in example commands, but the reference to Windows cryptography tools is a subtle form of Windows bias.

Recommendations:

When referencing cryptographic modules or APIs, include cross-platform or Linux-relevant standards (e.g., OpenSSL, Linux kernel crypto modules) alongside Windows-specific ones.
Provide links or references to general cryptographic standards (such as FIPS 140-2, NIST publications) that are not tied to a specific operating system.
If mentioning Windows-specific tools or APIs, add a note or section about equivalent Linux or open-source cryptographic libraries and how they relate to Azure's encryption implementation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides AzCopy command-line examples that are cross-platform, but in every section where shell quoting is discussed, it refers to Windows Command Shell (cmd.exe) first and Linux/Unix shells second. The guidance is phrased as 'use single quotes except for Windows Command Shell (cmd.exe), use double quotes,' which subtly centers Windows as the primary or default environment. No PowerShell-specific or Windows-only tools are used, and Linux/Unix usage is acknowledged, but always as the alternative.

Recommendations:

Rephrase quoting guidance to be neutral or Linux-first, e.g., 'Use single quotes in Bash or other Unix shells. In Windows Command Shell (cmd.exe), use double quotes.'
Add explicit mention of PowerShell if relevant, or clarify quoting rules for PowerShell, as it differs from both Bash and cmd.exe.
Consider providing examples with both single and double quotes side by side, labeled for each shell, to make Linux/Unix users feel equally supported.
Where possible, avoid phrasing that positions Windows as the default or primary environment.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists both Azure PowerShell and Azure CLI as options for obtaining volume information, but PowerShell is mentioned first in both the prerequisites and the example commands. No exclusive Windows tools or patterns are present, and all other instructions use cross-platform tools (kubectl, bash, yaml). There are no missing Linux examples, but the ordering gives slight preference to Windows/PowerShell.

Recommendations:

List Azure CLI before Azure PowerShell in prerequisites and example commands, as Azure CLI is cross-platform and more commonly used on Linux.
Explicitly note that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS to avoid implying PowerShell is Windows-only.
Where possible, provide examples for both tools side-by-side or clarify that either can be used, with CLI first.
Consider including a short note about installing and using Azure CLI on Linux, if relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it lacks explicit examples or guidance for Linux users, such as Linux command-line usage, shell scripting, or references to Linux environments. The tools mentioned (AzCopy, REST APIs, Data Factory, Data Box) are cross-platform, but the absence of Linux-specific instructions or examples may leave Linux users underserved.

Recommendations:

Add explicit examples or references for using AzCopy and other tools on Linux (e.g., bash command-line usage, installation instructions for Linux).
Include notes or sections clarifying cross-platform compatibility for each tool.
Provide sample scripts or automation patterns for both Windows (PowerShell) and Linux (bash/shell).
Mention any Linux-specific considerations or troubleshooting tips where relevant.
Ensure parity in documentation structure by presenting Linux and Windows usage equally, or in parallel, where applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild 'windows_first' bias by suggesting the use of the 'code' command to create YAML files (which is most commonly associated with Visual Studio Code on Windows) and by mentioning 'administrative privileges' for running commands locally, a concept more prominent in Windows environments. However, all command-line examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific or Windows-only commands. There are no Linux-specific instructions or examples, and Linux tools/editors are not mentioned.

Recommendations:

Explicitly mention that all CLI commands work on Linux, macOS, and Windows.
When suggesting to create/edit files, recommend cross-platform editors (e.g., 'nano', 'vim', 'vi', or 'code') or use neutral language like 'use your preferred text editor'.
Clarify that 'administrative privileges' may mean 'sudo' on Linux/macOS and 'Run as Administrator' on Windows.
Add a note or section confirming that the instructions are valid for Linux, macOS, and Windows, and provide any OS-specific caveats if necessary.
Where relevant, provide examples of common Linux workflows (e.g., using 'touch' and 'nano' to create/edit files).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally presents cross-platform information, but in the few places where OS-specific instructions are given (such as setting environment variables), Windows is listed first. There is a minor bias in the ordering of instructions, but Linux and macOS equivalents are always provided. The only other OS-specific note is a tip about quoting in shells, which does mention Windows separately but does not omit Linux guidance.

Recommendations:

Alternate the order of operating systems in tables and instructions, or list Linux/macOS first in some sections to avoid always privileging Windows.
Where OS-specific instructions are given, ensure that Linux and macOS are not always listed after Windows.
Consider adding explicit Linux/macOS command-line examples in addition to the syntax, especially in sections where only the Windows command shell is called out.
Highlight any Linux-specific optimizations (such as concurrent scanning) more prominently, possibly with examples.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a .NET project. However, all commands and instructions are cross-platform, and there are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples. The documentation otherwise maintains good parity for Linux and macOS users.

Recommendations:

List Bash (or 'Bash, cmd, or PowerShell') first or equally when mentioning console environments to avoid implying Windows is primary.
Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform support.
Where relevant, provide any OS-specific notes (e.g., environment variable setup differences) to ensure clarity for Linux/macOS users.
Consider including a brief section or note on running the sample on Linux/macOS to further demonstrate parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples, commands, or tooling references. However, it also does not include any examples or instructions for either Windows (e.g., PowerShell, Windows tools) or Linux (e.g., Bash, CLI). The absence of examples means there is no explicit Windows bias, but there is also a lack of Linux parity in practical guidance, which could be considered a missed opportunity for inclusivity.

Recommendations:

Add practical examples for both Windows (PowerShell) and Linux (Bash/CLI) environments for common tasks such as assigning roles or obtaining tokens.
Explicitly mention cross-platform tools (such as Azure CLI) and provide usage examples for both operating systems.
If referencing scripts or automation, ensure both PowerShell and Bash examples are included.
Clarify that the instructions are platform-agnostic if no OS-specific steps are required, to reassure users on all platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a mild 'windows_first' bias in its instructions for creating the project directory. It lists 'cmd, PowerShell, or Bash' as example console windows, with Windows shells mentioned before Bash (the common Linux shell). However, all code examples and instructions are otherwise cross-platform and do not rely on Windows-specific tools or patterns. There are no PowerShell-specific commands, no exclusive use of Windows tools, and Linux users are not omitted from any step.

Recommendations:

When listing console windows or shells, alternate the order or explicitly state cross-platform compatibility, e.g., 'such as Bash, PowerShell, or cmd'.
Where possible, provide explicit notes that all commands work on both Windows and Linux/macOS, or call out any OS-specific differences if they exist.
Consider including a brief section or callout confirming that the quickstart is fully cross-platform, to reassure non-Windows users.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧